Database Users

Recovery Issues At&t S4

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

Possible Brick

I just got a replacement Galaxy S4 today. I didn't even bother to check what ROM it was on because I didn't think to pay attention. I flashed CWM with a tool (http://forum.xda-developers.com/showthread.php?t=2297033) and CWM booted fine. I went to install the Paranoid Android 4.3 beta, and all went as planned. I rebooted, and it just hung on the Paranoid Android boot screen. If I then turn the phone off and reboot, it get stuck on the Samsung locked screen. I'm praying I didn't brick this thing for good, but reading about the MF3 headaches, I'm not so sure. Can anyone offer some insight? I can't access USB in CWM either.
Edit: The box says SW-VER: 1337UCUAMDL; does that mean I'll be able to odin to stock?

geokhentix said:
I just got a replacement Galaxy S4 today. I didn't even bother to check what ROM it was on because I didn't think to pay attention. I flashed CWM with a tool (http://forum.xda-developers.com/showthread.php?t=2297033) and CWM booted fine. I went to install the Paranoid Android 4.3 beta, and all went as planned. I rebooted, and it just hung on the Paranoid Android boot screen. If I then turn the phone off and reboot, it get stuck on the Samsung locked screen. I'm praying I didn't brick this thing for good, but reading about the MF3 headaches, I'm not so sure. Can anyone offer some insight? I can't access USB in CWM either.
Edit: The box says SW-VER: 1337UCUAMDL; does that mean I'll be able to odin to stock?
Click to expand...
Click to collapse
If you are on AT&T MDL firmware you should be able to ODIN to stock, do a factory reset and take it from there. I suggest you do a lot more reading before you touch anything else. You can start by reading the "pinned" threads in the General section. Everything you need you will find there. Good luck

You need to flash Loki doki after each custom ROM if you're in CWM or any non auto loki'd recovery.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

djpharoah said:
You need to flash Loki doki after each custom ROM if you're in CWM or any non auto loki'd recovery.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
What he said...you are not on mf3 dont worry about that...if you were on mf3 you wouldny have been able to even get a recoveryjust odin to stock and start over...either find and use the "loki doki" zip (google can find it) and flash it after every rom flash or use the auto loki recovery which pretty much runs the loki doki script every rom rom flash for you right before it reboots
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

mg2195 said:
What he said...you are not on mf3 dont worry about that...if you were on mf3 you wouldny have been able to even get a recoveryjust odin to stock and start over...either find and use the "loki doki" zip (google can find it) and flash it after every rom flash or use the auto loki recovery which pretty much runs the loki doki script every rom rom flash for you right before it reboots
Click to expand...
Click to collapse
The tool he linked contains auto-loki CWM so I'm not sure that's his problem.
Definitely ODIN back to stock with this procedure:
http://forum.xda-developers.com/showthread.php?t=2261573
Using the MDL download you can find here:
http://forum.xda-developers.com/showthread.php?t=2263533
And try again! Make sure you read the stickies in the general forum too.

[Q] Not Booting Into Philz Recov

As the title says, I am currently unable to boot into Philz recovery. I bricked somehow trying to flash sacs 4.3 by stupidly restoring the wrong part of my nandroid backup. Flashed the stock OEM 4.3 MJA and did a factory reset right after. Anyway, when I try to boot into recovery it says "Recovery not seandroid enforcing" and "see warranty bit : recovery" then just reboots into the rom. Can anybody help me out?

Once you flashed stock MJA, you have to re flash Philz and reroot.
Sent from my SPH-L720 using Tapatalk

frostedunit said:
Once you flashed stock MJA, you have to re flash Philz and reroot.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I did both of those. I currently have root access and flashed the recovery twice to make sure I didn't do it wrong the first time. I am beginning to wonder if the bootloader changed from MF9 to MJA when I flashed the OEM, which won't allow Philz to boot properly.

Bump.
Still stuck without a working recovery...

l0udude said:
Bump.
Still stuck without a working recovery...
Click to expand...
Click to collapse
Odin the tar of philz
http://forum.xda-developers.com/showthread.php?t=2201860
Grab the tar and odin
Confused on how you flashed philz 2 times without a working recovery?

ParkerParker said:
Odin the tar of philz
http://forum.xda-developers.com/showthread.php?t=2201860
Grab the tar and odin
Confused on how you flashed philz 2 times without a working recovery?
Click to expand...
Click to collapse
I did use Odin... that's what I meant. I did get it to boot once after disabling the Knox bootloader with SuperSU and installing the binaries for CWM but when I tried to reboot back into recovery it starts booting then reboots normally again. I think I'm just going to have to wait for a MJA compatible custom recovery. Gonna stock it out for now.

l0udude said:
I did use Odin... that's what I meant. I did get it to boot once after disabling the Knox bootloader with SuperSU and installing the binaries for CWM but when I tried to reboot back into recovery it starts booting then reboots normally again. I think I'm just going to have to wait for a MJA compatible custom recovery. Gonna stock it out for now.
Click to expand...
Click to collapse
Im on MJA and using the latest philz with zero problems, also people are having success using twrp 6301, although I would use caution as its not 100% yet, what rom are you on? You can remove Knox with titanium backup, either way philz is rock solid on 4.3, also if making backups on 4.3 you need to go to Nandroid settings and check the selinux 4.3 box before making a backup in order to restore a 4.3 Rom. Also not sure why you are having to install binaries for cwm? Since you are staying stock cool but if you used cf auto root, which you stated you are rooted, you should be able to Odin philz, did you ota? Flash the modem from Unknownforce? @leaderbuilder you have any input man?
Sent from my SPH-L720 using Tapatalk

ParkerParker said:
Im on MJA and using the latest philz with zero problems, also people are having success using twrp 6301, although I would use caution as its not 100% yet, what rom are you on? You can remove Knox with titanium backup, either way philz is rock solid on 4.3, also if making backups on 4.3 you need to go to Nandroid settings and check the selinux 4.3 box before making a backup in order to restore a 4.3 Rom. Also not sure why you are having to install binaries for cwm? Since you are staying stock cool but if you used cf auto root, which you stated you are rooted, you should be able to Odin philz, did you ota? Flash the modem from Unknownforce?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
On the oem 4.3 rom still because I can't flash. Can't flash because custom recovery won't boot. I think it's because of knox. Where do I go in titanium backup to disable knox? Because I can't get supersu to do it again.

l0udude said:
On the oem 4.3 rom still because I can't flash. Can't flash because custom recovery won't boot. I think it's because of knox. Where do I go in titanium backup to disable knox? Because I can't get supersu to do it again.
Click to expand...
Click to collapse
I think you are possibly a little over your head. You must take some time and read through the Stickies, Howtos and original posts. Please.
You can easily root (using cf-autoroot - may have to install Superuser from playstore afterwards) and then put a custom recovery (also easily done by installing GooManager and then selecting install custom recovery CWM or TWRP etc) on stock 4.3 that has knox.
From there you can then change/install whatever recovery you want and whatever 4.3 ROM you choose.
BUT I'd highly suggest you take some time, slow down and read, read a little more then after that read some more before you turn your new phone into a shiny paper weight.

leaderbuilder said:
I think you are possibly a little over your head. You must take some time and read through the Stickies, Howtos and original posts. Please.
You can easily root (using cf-autoroot - may have to install Superuser from playstore afterwards) and then put a custom recovery (also easily done by installing GooManager and then selecting install custom recovery CWM or TWRP etc) on stock 4.3 that has knox.
From there you can then change/install whatever recovery you want and whatever 4.3 ROM you choose.
BUT I'd highly suggest you take some time, slow down and read, read a little more then after that read some more before you turn your new phone into a shiny paper weight.
Click to expand...
Click to collapse
Yeah I'll check around and see if I come up with anything. I'm not particularly new to this if you can't tell. I've rooted and customized 2 different phones, as well as jailbroke, themed, and flashed stuff to my ps3 back when it was possible. I rooted and flashed sacs v4 rom and ktoonsez kernel easily almost immediately after getting the phone a few months ago. I'm currently running a rooted, stable, stock 4.3 MJA everything so I guess I'm gonna wait and see if anything new surfaces. I have a suspicion that something is writing over CWM with the stock recovery when I boot into the rom but I don't know what to do about it. GooManager won't install openrecovery for some reason either, I already tried that. Just stalls at the download page. Thanks for the help anyway guys.

If you can get into download mode there is no reason that a custom recovery shouldn't install via PC Odin.
You can try this.
Grab the recovery .tar Launch Odin (make sure to 'Run As Administrator') place the .tar in the PDA slot and make sure you un-check "Auto Reboot".
Once it installs (Pass) take phone off PC, remove battery.
Put battery back in and then boot straight to recovery - Home button, Volume Up and Power button till you see the very little blue 'entering recovery' at the top left. If you get into recovery just choose the 'restart phone option. Or you might want to step through the Philz menus then back out to the Power Options then Reboot system and then 'fix root' and let it reboot.

[Q] TWRP 2.7 -- Lost Recovery GREAT

So, I installed TWRP 2.7 on my GS4 via mobile terminal. My device had the radio updated to MLD from @rockrat(which i thought was not effecting my recovery options how he extracted it) --upon updating to TWRP 2.7 i rebooted into recovery and got the "Software Not Supported by AT&T" locked bootloader message.
I have tried flashing .tar recoveries in Odin-- it fails auth
I have tried using mobile terminal to go back to older recoveries and all i end up with is the same not supported by AT&T.
Have i now fu#ked myself out of using a recovery besides Safestrap? I have a custom kernel on board, I have 4.4.2 and root is fine. I just _think_ from what I've read that I'm now trapped on a Galaxy with no recovery boat.
Crowd-- please say It ain't so

I think you forgot to flash loki again. Unless your recovery auto-loki, I believe you have to flash loki every time you flash something in recovery.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

If your firmware is MDB or MDL check out the post by dees_troy "TWRP 2.6.0 Recovery" in the development section and read the last couple of pages. This may help you. Good luck.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Thanks guys, I figured it out. TWRP team a) doesn't have a gs4 b) forgot to f'n Loki the recovery. c)I had never in all my flashing known the recovery sector needed Loki, also I was stumped because In using terminal emulator I thought if was reverting to a previous build but for some reason it wasn't. d)Flashify came in and saved the day.
Sent from my GT-I9505G using Tapatalk

[Q] Flashed new TWRP now no recovery.

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