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
Related
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.
Hello all i have a galaxy s4 atat and i need help flashing twrp . It use to be sooo much easier. But now when i download gooim it wont install the custom open recovery script.
I tried to flash my gs4 with odin using the stock firmware i found here at this thread and it says fail AUTH. i used this thread for the stock firmware
http://forum.xda-developers.com/showthread.php?t=2261573
when i put my phone into download mode nothing is wrong. then i insert the md5 file into the PDA slot try and flash and odin says fail auth
.
so im stuck. and i am trying to flash my phone back to stock because i want to install twrp over gooim since on my current crappy stock rom wont let me do it. please help
What firmware are you? If MF3, stop! MF3 only has root. If MDL, there are guides
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
mf3 yes. so basically we havent cracked mf3? nor can i downgrade...
wait a second this whole root recovery situation is sooo hypocritical
..
so we can get root on mf3 and twrp says if you have root you can install a custom recovery. but now your saying i cant...
the whole point of getting root is to be able to install a custom recovery using gooim.....
ummmm'
.....
Root access does lead to custom recoveries but on unlocked bootloaders. Ours is locked tight by AT&T therefore no custom recoveries yet. Developers are working hard on getting there. With root you do have root access, so you can freeze bloatware and still do root access stuff but be careful if you mess up, at this moment there is no way going back on kies or Odin.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
DiscusAquarium said:
mf3 yes. so basically we havent cracked mf3? nor can i downgrade...
wait a second this whole root recovery situation is sooo hypocritical
..
so we can get root on mf3 and twrp says if you have root you can install a custom recovery. but now your saying i cant...
the whole point of getting root is to be able to install a custom recovery using gooim.....
ummmm'
.....
Click to expand...
Click to collapse
The boot loader is locked on the s4. If you have mf3 firmware you can root it but there's no way to put on a custom recovery. Do some more reading and research before you brick your device
okay.. sounds good. any idea or threads that have updates... with the progress.
DiscusAquarium said:
okay.. sounds good. any idea or threads that have updates... with the progress.
Click to expand...
Click to collapse
Start on the general forum. Particularly the stickies, pinned threads.
What if you rooted MF3 and can access stock recovery. Is there any consequences if you try and do a factory reset?
PimpDaddyInc said:
What if you rooted MF3 and can access stock recovery. Is there any consequences if you try and do a factory reset?
Click to expand...
Click to collapse
Shouldn't be.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
NOTE: AT&T variant. Phone is running 4.2.2 with MF3 baseband
So I'm helping a friend root his phone and run a custom ROM. The root went successfully (motochopper) and we installed SafeStrap and then we did a backup and wipe and then installed a 4.3 Google Play edition ROM (first mistake as we meant to download the 4.2 version)
I have the stock firmware zip for the phone and figured that that was the way to fix it, but I can't figure out how to get it to install. Through ADB it gives me an error after starting DAEMON. I converted the zip to a .tar and tried to use ODIN but ODIN stops working as soon as I tell it to run. I made sure I had the most current, correct drivers and am running ODIN3 v1.85. I thought maybe if I put it on the SD card I could install it though that method via the stock recovery but it says there is an invalid arguement.
What am I doing wrong?
Help
h_smith said:
NOTE: AT&T variant. Phone is running 4.2.2 with MF3 baseband
So I'm helping a friend root his phone and run a custom ROM. The root went successfully (motochopper) and we installed SafeStrap and then we did a backup and wipe and then installed a 4.3 Google Play edition ROM (first mistake as we meant to download the 4.2 version)
I have the stock firmware zip for the phone and figured that that was the way to fix it, but I can't figure out how to get it to install. Through ADB it gives me an error after starting DAEMON. I converted the zip to a .tar and tried to use ODIN but ODIN stops working as soon as I tell it to run. I made sure I had the most current, correct drivers and am running ODIN3 v1.85. I thought maybe if I put it on the SD card I could install it though that method via the stock recovery but it says there is an invalid arguement.
What am I doing wrong?
Help
Click to expand...
Click to collapse
What stock firmware zip do you have? You have to have the mf3 .tar.md5 file if you're trying to use odin
How does he have mf3 and motochopper works? It shouldn't. Also you have to have a custom recovery to flash the gpe rom and we don't. The closest thing we have is safestrap.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
HiTideBlastoise said:
How does he have mf3 and motochopper works? It shouldn't. Also you have to have a custom recovery to flash the gpe rom and we don't. The closest thing we have is safestrap.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure. I just used the first method I found and it worked. Then when it came to the recovery part that's when I found out about his baseband
jd1639 said:
What stock firmware zip do you have? You have to have the mf3 .tar.md5 file if you're trying to use odin
Click to expand...
Click to collapse
I'm on the SamMobile site trying to find the firmware and it says that they don't have it. I find that weird that such a popular model doesn't have the firmware needed to do this. I put in the correct model and country
EDIT: nevermind.
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 am currently on the unlocked MDL bootloader, and I am running KANGAKAT 7.0, which is a KitKat 4.4 ROM. My phone is also encrypted, which means that I cannot flash updates due to CWM/TWRP not supporting encryption.
The solution proposed by other users has been to ODIN the stock MK2 recovery onto my phone, use the stock recovery to factory reset my device, then re-flash TWRP and then my new ROM.
However I'm having a problem with these steps. I am able to successfully ODIN the stock MK2 recovery to my device, however whenever I try to boot into recovery, I get the yellow triangle screen stating that I'm running software that is not authorized by AT&T, and stating something to do with my kernel in the top left of the screen.
Is there a step that I am missing? I followed the instructions @ http://forum.xda-developers.com/showthread.php?t=1506697
It looks like that file is for the s2 skyrocket, not the s4. You'll probably have to flash the complete mdl firmware in Odin
Edit, if you're still rooted try flashing twrp 2.8.3.0 image file in flashify from the play store. http://techerrata.com/browse/twrp2/jflteatt
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
It looks like that file is for the s2 skyrocket, not the s4. You'll probably have to flash the complete mdl firmware in Odin
Edit, if you're still rooted try flashing twrp 2.8.3.0 image file in flashify from the play store. http://techerrata.com/browse/twrp2/jflteatt
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, they're instructions for the S2 Skyrocket, but I just used the general procedure and not the file, I used the stock recovery listed here http://forum.xda-developers.com/showpost.php?p=49687791&postcount=3
You make an interesting point though, if I ODIN the entire stock MDL ROM, that could work. I'm just going to write over it with another ROM anyways, so what I restore to shouldn't matter. I know this is probably a dumb question, but flashing the stock MDL ROM isn't going to affect my MDL bootloader is it?
I can get TWRP 2.8.3.0 with or without Flashify, but that app is very convenient, thank you for the tip =)
ChrisG683 said:
Yeah, they're instructions for the S2 Skyrocket, but I just used the general procedure and not the file, I used the stock recovery listed here http://forum.xda-developers.com/showpost.php?p=49687791&postcount=3
You make an interesting point though, if I ODIN the entire stock MDL ROM, that could work. I'm just going to write over it with another ROM anyways, so what I restore to shouldn't matter. I know this is probably a dumb question, but flashing the stock MDL ROM isn't going to affect my MDL bootloader is it?
I can get TWRP 2.8.3.0 with or without Flashify, but that app is very convenient, thank you for the tip =)
Click to expand...
Click to collapse
Flashing the mdl firmware in Odin will still give you the mdl bootloader. But it'll want to update after you flash so flash another custom rom or freeze the update files before it does so.
Sent from my Nexus 5 using XDA Free mobile app
@ChrisG683 Be sure to turn your wi-fi off and remove your SIM card, that way it can't update. You can put any apps you think you might need on an SD card and install them without having to go to the play store. Once you get things frozen or removed then you'll be good to go. :good:
Thanks guys, I'll be sure to keep that in mind once I get things sorted out.
The newest thing I've figured out is that the MDL stock recovery does not give me the "yellow triangle" error, and it presents me with the option to wipe my device. (I grabbed it from here http://forum.xda-developers.com/showthread.php?t=2429406)
Now I'm just making sure I have a stock MDL ROM ready to ODIN in case I screw up my device =). Hopefully this all works out.
Edit:
Looks like everything went beautifully. The MDL stock recovery wiped my /data partition perfectly, and I was able to reboot into a fresh and clean copy of KANGAKAT 6.0. Then I was able to use a terminal to flash TWRP, did a factory reset, flashed KANGAPOP 1.4, and now you can add me to the list of proud Lollipop users =)