SCH-i545 Galaxy S4 (vz) I have a brand new towel-rooted 2 3 4 i545 . My initial goal was to try a modded rom, now its simply to get twrp or cwm installed and working, or to atleast get safestrap working from boot, and my stock rom back to working again. I cant find an answer yet, and backed into a corner now.
When i boot into recovery now it just straight shuts off. when i boot into download mode, this works (i have odin access). when i boot normally, it shuts off immediately.
The problem i feel that i am having is i am working with a locked boot loader. however it may not be locked anymore, im not sure, more on this later. I have done some of the following things that i feel that the bootloader doesn't get along with:
1) i tried to install twrp, twrp via goomanager, cwm, cwm with LOKI 2(patched) 3(file) (viaadb), all to to no avail. the only thing i managed to get working was safestrap
2) i tried to dd install a recovery image, i think it was an openrecovery it said success. (i think this is what caused the black screen im at now, see below). In the end i couldn't get this to load so i went back to trying safestrap method below.
3) the only way i could actually control safestrap was if i launched it via app menu (something like 'reboot to recovery'). If i tried to launch safestrap via its own launch menu at normal phone boot, i have NO CONTROL the screen, i have NO TOUCH/swipe control. This means i was only able to use safestrap if i load it via a working operating system.
even then, i was lame enough to go through with the following, thinking it had something miraculous and super-powerish that would override all this nonsense;
4) I followed doing something similar to the first portion of this page where you create a rom-slot and set it for boot. When i rebooted, I expected it to reboot to the safestrap screen, and either have touch issues again, or the touch miraculously works, but NEITHER happened, leading me here. it now SHUTS DOWN immediately after the white writing of the samsung bootloader screen. (i used to see a blue Samsung screen, followed by red vz screen after).
So, i CAN adb sideload, push, install, etc.., i can dd or flash a new recovery image. Personally i think my next move would be to shell into that and cut down some permissions so i can get cwm or twrp installed on there, but ill settle for the goomanager method. I would need someone who knew more about the opsys files before i can proceed.
i just want to either get into a nice recovery, so i can try a new rom on this phone, OR atleast have safestrap WORKING when launched from the recovery screen (i suspect i installed the wrong one, any suggestions on which one i need here?) whats all this touch-wiz, do i have touch-wiz, is that the problem?
p.s. i tried using LOKI 2 it doesnt work, i get the nand write access problem like others, it simply cant complete its operation. must be a fairly new update. also something i did to it in the past, possibly mentioned above, has caused my bootloader to always "Samsung Custom" with a padlock unlocked, so i dont know if this means i successfully managed to unlock it yet, or if thats just a screen from some tool mentioned/linked above. however, i still managed to get it stuck here.
resources (havent tried these yet)
fastboot
Auto LOKI
[S4 acctive/recovery locked] safestrap recovery v3.65/v3.73 KK BETA
xda s4 general
androidforums allthings root s4
mdk stuff - recovery, custom recovery,
tars
factory and nowipe tars
roms
JellyBeans B7
Hyperdrive KK RLS20
Bonestock v1.1.4
Foxhound DiamondDogs 3.65
Eclipse S4 Tw v4.0.2
When i boot into recovery now it just straight shuts off. when i boot into download mode, this works (i have odin access). when i boot normally, it shuts off immediately.
The problem i feel that i am having is i am working with a locked boot loader. however it may not be locked anymore, im not sure, more on this later. I have done some of the following things that i feel that the bootloader doesn't get along with:
1) i tried to install twrp, twrp via goomanager, cwm, cwm with LOKI 2(patched) 3(file) (viaadb), all to to no avail. the only thing i managed to get working was safestrap
2) i tried to dd install a recovery image, i think it was an openrecovery it said success. (i think this is what caused the black screen im at now, see below). In the end i couldn't get this to load so i went back to trying safestrap method below.
3) the only way i could actually control safestrap was if i launched it via app menu (something like 'reboot to recovery'). If i tried to launch safestrap via its own launch menu at normal phone boot, i have NO CONTROL the screen, i have NO TOUCH/swipe control. This means i was only able to use safestrap if i load it via a working operating system.
even then, i was lame enough to go through with the following, thinking it had something miraculous and super-powerish that would override all this nonsense;
4) I followed doing something similar to the first portion of this page where you create a rom-slot and set it for boot. When i rebooted, I expected it to reboot to the safestrap screen, and either have touch issues again, or the touch miraculously works, but NEITHER happened, leading me here. it now SHUTS DOWN immediately after the white writing of the samsung bootloader screen. (i used to see a blue Samsung screen, followed by red vz screen after).
So, i CAN adb sideload, push, install, etc.., i can dd or flash a new recovery image. Personally i think my next move would be to shell into that and cut down some permissions so i can get cwm or twrp installed on there, but ill settle for the goomanager method. I would need someone who knew more about the opsys files before i can proceed.
i just want to either get into a nice recovery, so i can try a new rom on this phone, OR atleast have safestrap WORKING when launched from the recovery screen (i suspect i installed the wrong one, any suggestions on which one i need here?) whats all this touch-wiz, do i have touch-wiz, is that the problem?
p.s. i tried using LOKI 2 it doesnt work, i get the nand write access problem like others, it simply cant complete its operation. must be a fairly new update. also something i did to it in the past, possibly mentioned above, has caused my bootloader to always "Samsung Custom" with a padlock unlocked, so i dont know if this means i successfully managed to unlock it yet, or if thats just a screen from some tool mentioned/linked above. however, i still managed to get it stuck here.
resources (havent tried these yet)
fastboot
Auto LOKI
[S4 acctive/recovery locked] safestrap recovery v3.65/v3.73 KK BETA
xda s4 general
androidforums allthings root s4
mdk stuff - recovery, custom recovery,
tars
factory and nowipe tars
roms
JellyBeans B7
Hyperdrive KK RLS20
Bonestock v1.1.4
Foxhound DiamondDogs 3.65
Eclipse S4 Tw v4.0.2
Last edited: