I rooted and installed wicked v4 on my att galaxy s4 and it can up with the att lock saying that att doesnt support the rom or some thing similar to that. So i booted into recovery and installed a att kernal for the rom. I rebooted it and it booted into the system perfect running the new rom. I heard that wicked v5.1 was released and i downloaded it and went into recovery to install. It came up the att lock not letting me get into recovery mode. I can boot into download mode and click cancel and it restarts and boots into system fine but cannot get into recovery. Help plz
nomad836 said:
I rooted and installed wicked v4 on my att galaxy s4 and it can up with the att lock saying that att doesnt support the rom or some thing similar to that. So i booted into recovery and installed a att kernal for the rom. I rebooted it and it booted into the system perfect running the new rom. I heard that wicked v5.1 was released and i downloaded it and went into recovery to install. It came up the att lock not letting me get into recovery mode. I can boot into download mode and click cancel and it restarts and boots into system fine but cannot get into recovery. Help plz
Click to expand...
Click to collapse
What firmware are you on? Please if you know how to flash ROMs you should know where to find it.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Sent from my SGH-M919 using xda app-developers app
If you can boot into OS, download Goo Manager from Market and install TWRP 2.5.0.2 recovery
If you get it working--do a lot of reading--many variants and our bootloader is locked. Get to know loki-doki too, if you don't--
I installed twrp and it still gives me the att lock when I go into recovery. Should I try to install Loki with Odin?
Sent from my SGH-M919 using xda app-developers app
loki doesn't install thru odin--it installs thru recovery as a zip
if you still can't get into revovery you may need to odin back to stock--i never used odin, haven't needed too and on an iMac
there are some threads on using it and someone may help with that
loki bypasses samsung's signature verification on recovery and kernels and lets you flash a kernel that hasn't already been loki'd by dev--
Are you getting a lock on the Samsung screen? Or are you getting the warning saying that software is detected that is not authorized by AT&T.
If you are getting the first. Let it boot.
If you are getting the second, loki-doki patch. Google it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Or u can in fact use ROM manager just to flash a recovery "CWM".after flashing cwm get rid of ROM manager and use cwm to flash any of the recoveries. I use philz touch recovery .Google is badass though
Sent from my SAMSUNG-SGH-I337 using xda premium
ODIN emergency restore fixes it.
Sent from my Nexus 7
here ya go
Step one. Install rom using goomanagers' twrp
step two. flash rom
step 3. flash the attached loki-doki.zip
it will make the phone think that the boot image is signed with at&t. it writes into the firmware, so you don't have to do it every boot. but you do have to do it everytime you flash a rom
vedantgp said:
Step one. Install rom using goomanagers' twrp
step two. flash rom
step 3. flash the attached loki-doki.zip
it will make the phone think that the boot image is signed with at&t. it writes into the firmware, so you don't have to do it every boot. but you do have to do it everytime you flash a rom
Click to expand...
Click to collapse
This is the correct procedure...
Related
Alright I have searched all day and can not seem to find a resolution to my problem. It is my fault I shouldn't fix something that isn't broke but it has resulted in issues and I would appreciate it if someone could help me.
I had twrp 2.5.0.2 installed running GE 4.2.2 ROM with MF3 radios installed and GE kernel v11. I saw twrp had a update to 2.6.0.0 and I decided to install it via goo manager it booted up in recovery with the "the software is unauthorized by att" screen and I can do volume down + power after that to reboot phone and not have issues as far as getting my phone booted and working on all the above. But the problem I am having now I have lost custom recovery. I have tried goo manger again as well as some on click root/recovery methods from these forums and all result in the same back to the unauthorized screen mentioned above its like it won't boot into a custom recovery. Any advice is greatly appreciated.
Sent from my Nexus 7 using xda app-developers app
Maybe try ROM manager and install cwm .it will pop up in ROM manager as the T-Mobile s4 but that's what I used to install the first recovery image,then I used that recovery to flash the auto Loki recovery.I have used the same plain auto Loki recovery since then.
Sent from my SAMSUNG-SGH-I337 using xda premium
Just tried that as well. Still not working. When I takes me to that unauthorized page top left it says "secure fail: kernel". But when I reboot the phone normal it comes up just fine....so that tells me its getting past with Loki to boot up my ROM and kernel but for some reason it will not take a custom recovery anymore when I have had one installed previously.
Sent from my SGH-I337 using xda app-developers app
If memory serves me right the Google Edition ROM will make TWRP / GooMananger think you have a 9505(G) and thus it will install that version. So you installed a non-loki'd recovery.
Use Odin, go back to AMDL firmware. (Take SIM out before doing so so it wont download the AMF3 update). Redo Root + Recovery. BEFORE you flash another rom, install GooManager and then update from there. You will be running stock firmware so it will identify the model correctly. Then flash your custom ROM.
Forgive me for being noob when it comes to Odin. But does this OTA the software or will I need to get Odin on my desktop?
Sent from my SGH-I337 using xda app-developers app
I tried flashing to the latest version of stock rom and found it had the new Samsung policy updates in place preventing me from rooting and using superuser things properly, so I went to do a full restore back (using clockworkmod).
Now my phone takes about 3 minutes to pass the logo screen before booting up to the home screen and my wifi won't switch on either... Anyone have any ideas why this may be?
I'm currently downloading an older stock firmware to flash using odin and then using titanium to restore all my apps and settings.
Is there a way I can have the latest stock firmware without the new policy updates?
Hi, you need to reinstall the stock up to date version via Odin. It may take two attempts. Your boot loader is locked. Once you have done this, flash a recovery via odin then you can root and flash a recovery. It happened to me. Any questions let me know.
Sent from my GT-I9505 using xda app-developers app
Watenaccio said:
Hi, you need to reinstall the stock up to date version via Odin. It may take two attempts. Your boot loader is locked. Once you have done this, flash a recovery via odin then you can root and flash a recovery. It happened to me. Any questions let me know.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
So I need to install the latest stock rom (even though it's got the new Samsung policy updates thing on?), to lock the boot loader, then root and flash CWM via Odin and then use CWM to restore a full backup?
I tried that and it doesn't work... and now when I flash the latest stock rom, the wifi doesn't even turn on... arggghhhhhhhhh!!!!
I installed the KOT49H GE ROM on my AT&T SGH-I337 and it runs great. I then decided to see if there was an update to TWRP and I found an updated one and flashed it via goo.im. I later read that this is not the way to do it. Anyway, when I boot into recovery a big yella triangle appears and at&t scolds me for running in authorized firmware. I can boot into download, cancel it and the ROM boots and runs fine.
Under the "about device" page on settings it says the baseband is MK2 (because I flashed that modem). If I look at the boot loader version via android terminal emulator it shows I'm still on MDL.
Any ideas how to get recovery working again?
I am trying to understand the reason why you flashed a recovery.
From your post, it looks like you are using safestrap and deadly venom tool to run GE.
You can flash the MLD files from the tool to get the recovery back.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I found an updated version of TWRP and thought it would be a good idea to update it. I think the problem might be that I didn't use Loki doki before I installed the twrp update. It can't get to the recovery now. Will I mess anything up if I use motochopper? I don't want safestrap because I like the Google Edition ROM and I'm still on the MDL boot loader.
I'm pretty much a newb with this S4. I had my S2 rooted with task650's ROM and understood that better because no locked bootloader
insaneretard said:
I found an updated version of TWRP and thought it would be a good idea to update it. I think the problem might be that I didn't use Loki doki before I installed the twrp update. It can't get to the recovery now. Will I mess anything up if I use motochopper? I don't want safestrap because I like the Google Edition ROM and I'm still on the MDL boot loader.
I'm pretty much a newb with this S4. I had my S2 rooted with task650's ROM and understood that better because no locked bootloader
Click to expand...
Click to collapse
My bad! I read that you had "MLD" bootloader instead of "MDL" and hence my comment. MLD is a leaked 4.4 firmware.
Motochopper is used to root and I am guessing you still have root. All you need to do is flash a recovery.
http://www.theandroidsoul.com/latest-twrp-recovery-for-att-galaxy-s4-android-4-4-compatible/
This link provides an Odin flashable TWRP.
jmjoyas said:
My bad! I read that you had "MLD" bootloader instead of "MDL" and hence my comment. MLD is a leaked 4.4 firmware.
Motochopper is used to root and I am guessing you still have root. All you need to do is flash a recovery.
http://www.theandroidsoul.com/latest-twrp-recovery-for-att-galaxy-s4-android-4-4-compatible/
This link provides an Odin flashable TWRP.
Click to expand...
Click to collapse
Thanks for helping me out. I tried this yesterday and today with the link you provided. When I try to flash it via odin, it comes up as failed. On my phone, it says "SECURE CHECK FAIL: recovery" in red letters on the download page. Any other ideas?
You could try grabbing the mdl package, an extracting the recovery from it and flash in Odin or Heimdall. Worst case you flash to mdl and then motochopper it again.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Red_81 said:
You could try grabbing the mdl package, an extracting the recovery from it and flash in Odin or Heimdall. Worst case you flash to mdl and then motochopper it again.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks. Do i need root to do this? I don't think I even have root any more. I'm running a custom ROM without root access. I tried to use CASUAL to root and install the recovery but it couldn't root it.
You will only need to root again if you go all the way back to stock.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Hey guys, I'm pretty new here and new to rooting devices. I recently just rooted my Samsung Galaxy S 4 SGH-1337 (At&t) with the new "TowelRoot" and then using Super SU to finish the root. I has a question when it came to installing the custom recovery Philz Touch. I have the 4 most recent versions of PT and using Odin v3.09 and v3.07 I am still unable to correctly install the recovery. When I try starting the process I get a "Leave CS" in the bottom left of the Odin window, and when I start the process fails? I've noticed when I go into download mode on my S 4 the phone tells me on the the official binary and official operating system. If I am rooted should that say something else? I have checked the Root Checker app and it says I am in fact rooted.
Other solutions I've already got advice and still unable:
- I'm using my out of box charging cable.
- I am pressing start after I ad the AP in Odin.
- The phone is in Download mode.
Can anyone help me out and assist me? This is super annoying and I would love to figure it out soon. Thank you in advance!
kelvin00 said:
Hey guys, I'm pretty new here and new to rooting devices. I recently just rooted my Samsung Galaxy S 4 SGH-1337 (At&t) with the new "TowelRoot" and then using Super SU to finish the root. I has a question when it came to installing the custom recovery Philz Touch. I have the 4 most recent versions of PT and using Odin v3.09 and v3.07 I am still unable to correctly install the recovery. When I try starting the process I get a "Leave CS" in the bottom left of the Odin window, and when I start the process fails? I've noticed when I go into download mode on my S 4 the phone tells me on the the official binary and official operating system. If I am rooted should that say something else? I have checked the Root Checker app and it says I am in fact rooted.
Other solutions I've already got advice and still unable:
- I'm using my out of box charging cable.
- I am pressing start after I ad the AP in Odin.
- The phone is in Download mode.
Can anyone help me out and assist me? This is super annoying and I would love to figure it out soon. Thank you in advance!
Click to expand...
Click to collapse
Since towel root worked in your phone I'm assuming you're on firmware nc1. This can not have a custom recovery installed. In fact you probably erased your stock recovery trying these other ones. I suggest using odin to flash nb1 then update back to nc1 and if you want a recovery yo install another rom (only touchwiz based roms) you'll to use safestrap. That is the only option at this time.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
drock212 said:
Since towel root worked in your phone I'm assuming you're on firmware nc1. This can not have a custom recovery installed. In fact you probably erased your stock recovery trying these other ones. I suggest using odin to flash nb1 then update back to nc1 and if you want a recovery yo install another rom (only touchwiz based roms) you'll to use safestrap. That is the only option at this time.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the response. I am on firmware NC1. After posting I have read that there is a new bootlocker (?) that was pushed on the 4.4.2 update preventing people from actually installing custom recovery and other things. There is a workaround going to an older version to then root and get a custom recovery, but I definitely don't have the knowledge of what to do.
I'm not sure what you mean by me probably erasing my stock recovery? Are you saying if I try and restore my device it will not work?
kelvin00 said:
Thanks for the response. I am on firmware NC1. After posting I have read that there is a new bootlocker (?) that was pushed on the 4.4.2 update preventing people from actually installing custom recovery and other things. There is a workaround going to an older version to then root and get a custom recovery, but I definitely don't have the knowledge of what to do.
I'm not sure what you mean by me probably erasing my stock recovery? Are you saying if I try and restore my device it will not work?
Click to expand...
Click to collapse
When you tried to install the custom recovery it more than likely erased your stock recovery and the only way to get it back is to flash nb1. And going to an older version is no longer possible. Once you update and the bootloader is updated you're no longer able to revert to an older bootloader. Trying to do so could brick your phone
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
drock212 said:
When you tried to install the custom recovery it more than likely erased your stock recovery and the only way to get it back is to flash nb1. And going to an older version is no longer possible. Once you update and the bootloader is updated you're no longer able to revert to an older bootloader. Trying to do so could brick your phone
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Again, thank you for responding to me. I understand what you are saying now about me possibly deleting my stock recovery. I didn't go very far i the process and I'm fairly sure I didn't for the simple reason that it did not work. I can definitely be wrong and you are probably more right on this situation than I am.
Thank you for the heads up with the older version not possibly anymore.
Do you know any confirmed ways of rooting and flashing a custom recovery since 4.4.2? If not I guess I'm just going to wait a bit for a confirmed method.
kelvin00 said:
Again, thank you for responding to me. I understand what you are saying now about me possibly deleting my stock recovery. I didn't go very far i the process and I'm fairly sure I didn't for the simple reason that it did not work. I can definitely be wrong and you are probably more right on this situation than I am.
Thank you for the heads up with the older version not possibly anymore.
Do you know any confirmed ways of rooting and flashing a custom recovery since 4.4.2? If not I guess I'm just going to wait a bit for a confirmed method.
Click to expand...
Click to collapse
Before proceeding check to make sure your stock recovery is still intact (power phone off, wait 10 seconds, power on while holding volume up/home button/power if you boot into recovery you're fine and can proceed with towel root (just Google it it'll come up right away) download and install the apk on your phone and it'll root your phone for you. Next go here
http://forum.xda-developers.com/showthread.php?t=2680868
Closest thing to custom recovery that will let you only flash touchwiz based roms.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
I rooted samsung s4 at&t all went well, installed Rashr( read somewhere using rashr to install twrp) so I using rashr to install twrp.. now the phone stuck at downloading do not turn off target, I try to boot into recovery get same result, removed battery reboot same problem.... any help?
tonynguyenn said:
I rooted samsung s4 at&t all went well, installed Rashr( read somewhere using rashr to install twrp) so I using rashr to install twrp.. now the phone stuck at downloading do not turn off target, I try to boot into recovery get same result, removed battery reboot same problem.... any help?
Click to expand...
Click to collapse
What firmware / bootloader are you on?. I'm guessing it's not mdb or mdl. Twrp is not going to work on your device. Can you get into download mode? You're most likely going to have to flash the firmware in Odin, but I don't know what version you're currently on.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
What firmware / bootloader are you on?. I'm guessing it's not mdb or mdl. Twrp is not going to work on your device. Can you get into download mode? You're most likely going to have to flash the firmware in Odin, but I don't know what version you're currently on.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Phone version 4.4.4, security version MDF v1.0 if that what you were asking not sure what mdb or mdl mean sorry... I got the phone to boot normal by boot in download mode and hit cancel...
tonynguyenn said:
Phone version 4.4.4, security version MDF v1.0 if that what you were asking not sure what mdb or mdl mean sorry... I got the phone to boot normal by boot in download mode and hit cancel...
Click to expand...
Click to collapse
4.4.4 is the nj4 bootloader. Twrp will not work on your device. The bootloader is locked. Safestrap is the only custom recovery you can use and you can only flash touch wiz based roms. See this http://forum.xda-developers.com/showthread.php?p=56453100
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
4.4.4 is the nj4 bootloader. Twrp will not work on your device. The bootloader is locked. Safestrap is the only custom recovery you can use and you can only flash touch wiz based roms. See this http://forum.xda-developers.com/showthread.php?p=56453100
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for your help
If u get stuck at the. downloading screen and can't boot just remove battery then put back in and boot back I to download mode. Volume down power home... Then push down for cancel and you'll be back to normal
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app