Related
After two weeks of forum crawling and surviving 2 soft-bricking incidents, I've finally decided to reach out for help from the experts :crying:
Currently I have an ATT HOX, unlocked/rooted/SuperCID - running stock ICS (4.0.4).
My goal is to get JB on it and then flash to Blade ROM (I tried flashing to Blade with ICS - OOPS!)
Even though the info is on the forums - it's not all together in a streamlined format for me to follow - I feel I could get lost and screw it up (again)
From what I gathered from reading - here is what I "think" I need to do from my current phone state:
1. Facepalm S-Off
2. Install OTA Rootkeeper then backup root
3. Flash stock recovery
4. Re-Lock Bootloader
5. Flash OTA ATT JB.zip using stock recovery
6. Unlock Bootloader
7. Flash TWRP
8. Restore backup root with OTA RK
9. Flash Blade ROM
Can someone please check my thinking and make sure I'm not missing something?
Or any recommendation of an easier process? I feel I'm going to get lost somewhere in those steps and end up in Oz.
Or maybe a recommendation on an awesome ICS Rom? (so I can avoid confusing myself)
I'm terrified of another 3AM morning and a bricked-out HOX.
Thanks in advance!
Do you mean this rom: http://forum.xda-developers.com/showthread.php?t=2134328?
Because that's a rom for the quad-core Tegra One X. If you've been doing that, it's no wonder you got bricked.
You don't need OTA Rootkeeper. You can just flash a rooted rom.
2 major points:
1) As already mentioned, Blade is not for our phone, its for the quad core One X. Stay within this forum section. If you are looking at any XDA thread that just says "HTC One X" (no mention of "AT&T, Rogers" etc.) near the top of the screen, you are in the wrong section. Stick to the forum section that mentions AT&T. Flashing a ROM for the quad core version won't work, and might also hard brick your phone.
2) Aside from S-Off which is a good idea) you don't need to mess with any of the stuff you mentioned (Rootkeeper, stock recovery, OTA zip) in order to flash a JB based custom ROM if you are already bootloader unlocked and have TWRP. With S-off, just flash the ROM. If S-on, just flash the ROM, then flash the boot.img with fastboot (if hboot 1.14 or higher).
I'm not sure how you got the notion that you need to do all these other steps (maybe some process for the quad core forum?).
redpoint73 said:
I'm not sure how you got the notion that you need to do all these other steps (maybe some process for the quad core forum?).
Click to expand...
Click to collapse
<---- desperate noob
...and I also came from the original Samsung Vibrant. With that phone, I also had the idea that I could only use a ROM based of the current android version. Hence the carry over of thought from that side.
I can't believe I lost sleep over the simplicity of it all.
But.... just to make sure I understand this correctly - Even if I have ICS currently installed, I can flash a JB based ROM without issues?
Thanks a ton guys!
razorc03 said:
But.... just to make sure I understand this correctly - Even if I have ICS currently installed, I can flash a JB based ROM without issues?
Click to expand...
Click to collapse
Correct you can flash it.
But some people have been having issues on JB coming from older firmware. If you have problems later, then ruu'ing and updating is warranted. Right now it's overkill.
iElvis said:
Correct you can flash it.
But some people have been having issues on JB coming from older firmware. If you have problems later, then ruu'ing and updating is warranted. Right now it's overkill.
Click to expand...
Click to collapse
Would I be able to RUU to a stock JB? Or would I have to start from stock ICS again?
razorc03 said:
Would I be able to RUU to a stock JB? Or would I have to start from stock ICS again?
Click to expand...
Click to collapse
There are no JB ruu's as far as I know. But you can run the 2.20 ruu and then flash the 3.18 ota, then unlock again and reflash everything. That's what I did. Whole process took about half an hour and wasn't complicated. Just be sure you're s-off.
iElvis said:
There are no JB ruu's as far as I know. But you can run the 2.20 ruu and then flash the 3.18 ota, then unlock again and reflash everything. That's what I did. Whole process took about half an hour and wasn't complicated. Just be sure you're s-off.
Click to expand...
Click to collapse
Thanks for the info. But I need to bug you again.:angel:
A few questions about the ruu method. After you ruu, does that remove root, lock bootloader, and goes back to s-on?
And since I love numbered steps, here is how I am viewing it with my inexperienced understanding with question marks:
1. Check for S-off
2. Lock bootloader? (I guess not with S-off)
3. Run ruu 2.20 exe
4. Flash 3.18 ota
5. Rerun superCID (X-Factor xploit)?
6. Unlock bootloader
7. Flash TWRP
8. Flash ROM (Assuming S-off wasn't changed during the ruu)
I would love to be at your confidence level to run it it 30 minutes. One day I guess....
Before you run a ruu, you have to relock. When you run it, it wipes your entire phone and returns it to stock-out-of-the-box (except for s-off). So you need to back up anything you want to keep.
Here's a corrected list:
1. S-off
2. Relock in fastboot
3. Run ruu
4. Copy OTA update.zip to internal storage
5. Flash in stock recovery
6. Unlock
7. Flash custom recovery
8. Flash rooted rom
None of this affects s-off. AFAIK, the only way to be s-on again is manually change it in fastboot.
I wouldn't do all this unless you have a reason to, as there are spots in here where you can get tripped up if you're a complete noob.
iElvis said:
Before you run a ruu, you have to relock. When you run it, it wipes your entire phone and returns it to stock-out-of-the-box (except for s-off). So you need to back up anything you want to keep.
Here's a corrected list:
1. S-off
2. Relock in fastboot
3. Run ruu
4. Copy OTA update.zip to internal storage
5. Flash in stock recovery
6. Unlock
7. Flash custom recovery
8. Flash rooted rom
None of this affects s-off. AFAIK, the only way to be s-on again is manually change it in fastboot.
I wouldn't do all this unless you have a reason to, as there are spots in here where you can get tripped up if you're a complete noob.
Click to expand...
Click to collapse
Thanks for the checklist! It makes me feel safer to know an exit strategy so I don't panic if/when stuff goes bad.
I noticed you didn't list a step to re-root through custom recovery after step 7. Is the previous root still in place?
razorc03 said:
...and I also came from the original Samsung Vibrant. With that phone, I also had the idea that I could only use a ROM based of the current android version. Hence the carry over of thought from that side.
Click to expand...
Click to collapse
This varies completely by device, and firmware versions. Never assume that something you learned on another Android device applies to a different device.
razorc03 said:
I noticed you didn't list a step to re-root through custom recovery after step 7. Is the previous root still in place?
Click to expand...
Click to collapse
No, it's that once you're unlocked, you can re-root just by flashing a rooted rom.
What are my alternatives now?
Previously I was running CleanRom7 – but somehow must taken enough of update to somehow have locked the bootloader:
I’m currently running a “official Samsung” version that is 4.1.2.
I can do the following:
• Flash Root
• Flash a new recovery – used the latest CWM version 2.6.3.1
• Any attempt to either flash the latest ML1 or old CleanRom7 don’t successfully boot.
• At that point I can ODIN back to the 4.1.2 official Samsung version
The download screen looks like this:
Product Name: ICH-I535
Custom Binary Download: Yes (2 count)
Current Binary: Samsung Official
System Status: Official
Qualcom Secureboot: Enable
I’m constantly getting asked by some app if I want to do the OTA upgrade, I have been postponing for 1 hour
Question is given these 2 alternatives, what are the opinions to these two questions:
At this point should I just either ODIN or flash the latest ML1 upgrade and then root?
Or
Stay on 4.1.2?
bgbird said:
What are my alternatives now?
Previously I was running CleanRom7 – but somehow must taken enough of update to somehow have locked the bootloader:
I’m currently running a “official Samsung” version that is 4.1.2.
I can do the following:
• Flash Root
• Flash a new recovery – used the latest CWM version 2.6.3.1
• Any attempt to either flash the latest ML1 or old CleanRom7 don’t successfully boot.
• At that point I can ODIN back to the 4.1.2 official Samsung version
The download screen looks like this:
Product Name: ICH-I535
Custom Binary Download: Yes (2 count)
Current Binary: Samsung Official
System Status: Official
Qualcom Secureboot: Enable
I’m constantly getting asked by some app if I want to do the OTA upgrade, I have been postponing for 1 hour
Question is given these 2 alternatives, what are the opinions to these two questions:
At this point should I just either ODIN or flash the latest ML1 upgrade and then root?
Or
Stay on 4.1.2?
Click to expand...
Click to collapse
Ok, The question is, do you still want to flash custom rom/kernel?? If you do and since you're still on 4.1.2 you still can unlock the bootloader and flash custom 4.3 rom (with unlocked bootloader) for the 4.3 experience/look & feel.
More info
buhohitr said:
Ok, The question is, do you still want to flash custom rom/kernel?? If you do and since you're still on 4.1.2 you still can unlock the bootloader and flash custom 4.3 rom (with unlocked bootloader) for the 4.3 experience/look & feel.
Click to expand...
Click to collapse
I'd like a custom rom - but when I tried to flash the ML4.3 offered on this site - or even tried to reflash my old Cleanrom7 that i still had on my external flash memory that previously worked I couldn't boot.
I flashed VRUCML1_Stock_Root_Deodex (12.31.13 downloaded from the link. MD5 checked OK) this would try to boot - then just go back into recovery (I used the latest version of TWRP and used EZ-Unlock). Of course I wiped the device before I started. I flashed the rom and observed all of the successful messages during the flash. I never caught the really little blue message that flashed at the beginning of the boot cycle before it went black and rebooted to recovery. At that point I wiped again and flashed Cleanrom 7. It flashed, then started the installer that let me pick all sorts of apps. When I tried to boot - it just hung on the Samsung SIII banner that appears shortly after boot. I let it sit there for about an hour before pulling the battery. Then I ODINed back the the 4.1.2 version that I'm running now.
I tried this several times - even going as far as installing CRP recovery - same result.
So I'm about our of ideas...
bgbird said:
I'd like a custom rom - but when I tried to flash the ML4.3 offered on this site - or even tried to reflash my old Cleanrom7 that i still had on my external flash memory that previously worked I couldn't boot.
I flashed VRUCML1_Stock_Root_Deodex (12.31.13 downloaded from the link. MD5 checked OK) this would try to boot - then just go back into recovery (I used the latest version of TWRP and used EZ-Unlock). Of course I wiped the device before I started. I flashed the rom and observed all of the successful messages during the flash. I never caught the really little blue message that flashed at the beginning of the boot cycle before it went black and rebooted to recovery. At that point I wiped again and flashed Cleanrom 7. It flashed, then started the installer that let me pick all sorts of apps. When I tried to boot - it just hung on the Samsung SIII banner that appears shortly after boot. I let it sit there for about an hour before pulling the battery. Then I ODINed back the the 4.1.2 version that I'm running now.
I tried this several times - even going as far as installing CRP recovery - same result.
So I'm about our of ideas...
Click to expand...
Click to collapse
When you flashed back to 4.1.2 and it's working fine, at this point check to see if your bootloader is unlocked (even unlock tool said unlocked, you need to verify that it's unlocked). If it's not what ever you flash will not work.
buhohitr said:
When you flashed back to 4.1.2 and it's working fine, at this point check to see if your bootloader is unlocked (even unlock tool said unlocked, you need to verify that it's unlocked). If it's not what ever you flash will not work.
Click to expand...
Click to collapse
I never "flash" back. I have an ODIN image (KIES_HOME_I535VRBMF1_1152558_REV09_user_low_ship.tar.md5 ) that I use. At that point everything is replaced and I'm back to a stock bootloader (at least that's how it looks to me). When I root - then use EZ-Unlock at this point, the bootloader is locked. I suppose that it would be interesting to try to "flash" a 4.1.2 original and see what would happen.
bgbird said:
I never "flash" back. I have an ODIN image (KIES_HOME_I535VRBMF1_1152558_REV09_user_low_ship.tar.md5 ) that I use. At that point everything is replaced and I'm back to a stock bootloader (at least that's how it looks to me). When I root - then use EZ-Unlock at this point, the bootloader is locked. I suppose that it would be interesting to try to "flash" a 4.1.2 original and see what would happen.
Click to expand...
Click to collapse
I believe your image is fine. The key I want to point out is make sure your bootloader is unlocked. After you unlock with EZ-Unlock, boot into download mode and verify that the bootloader is actually unlock, before you proceed to flash anything else.
buhohitr said:
I believe your image is fine. The key I want to point out is make sure your bootloader is unlocked. After you unlock with EZ-Unlock, boot into download mode and verify that the bootloader is actually unlock, before you proceed to flash anything else.
Click to expand...
Click to collapse
OK - I'll try that. What do I look for in download mode that would indicate (or what should I try to do) that would prove that I'm "unlocked"?
boot into Odin mode (download mode) and you shoud see.
buhohitr said:
boot into Odin mode (download mode) and you shoud see.
Click to expand...
Click to collapse
I don't see anything about "unlocked"
when i press the down volume, home and power button I start into ODIN mode.
if i press the down arrow the phone will just re-boot
then i press the up arrow to continue into ODIN (download mode) I get:
:
Product Name: ICH-I535
Custom Binary Download: Yes (3 count)
Current Binary: Customl
System Status: Customl
Qualcom Secureboot: Enable
I still don't see anything about the unlocked bootloader
bgbird said:
I don't see anything about "unlocked"
when i press the down volume, home and power button I start into ODIN mode.
if i press the down arrow the phone will just re-boot
then i press the up arrow to continue into ODIN (download mode) I get:
:
Product Name: ICH-I535
Custom Binary Download: Yes (3 count)
Current Binary: Customl
System Status: Customl
Qualcom Secureboot: Enable
I still don't see anything about the unlocked bootloader
Click to expand...
Click to collapse
This Qualcom Secureboot: Enable - meaning bootloader is locked
buhohitr said:
This Qualcom Secureboot: Enable - meaning bootloader is locked
Click to expand...
Click to collapse
Just as a matter of curiosity, EZ-Unlock reports the bootloader to be “unlocked”. Wonder what’s wrong with that?
So pretty much at this point it appears that the only thing that I can do is to ODIN the official 4.3 tar file or stay on the 4.1.2 file that I ODINed previously.
bgbird said:
Just as a matter of curiosity, EZ-Unlock reports the bootloader to be “unlocked”. Wonder what’s wrong with that?
So pretty much at this point it appears that the only thing that I can do is to ODIN the official 4.3 tar file or stay on the 4.1.2 file that I ODINed previously.
Click to expand...
Click to collapse
Are you rooted? if not it's not going to work.
buhohitr said:
This Qualcom Secureboot: Enable - meaning bootloader is locked
Click to expand...
Click to collapse
I am rooted - I'm sure of that...
I'm also running the latest TWRP recovery.
EZ-Unlock still lets me lock and unlock the bootloader.
I'm also thinking of flashing VRLE6.bootloader.zip, rebooting, doing an EZ-Unlock and seeing what happens.
If that doesn't work - I'll have to decide
1. do I f staying where I'm at - running 4.1.2 ?
or
2. Do I give up and take the softbrick tar file and lock everything up ?
I'm not sure of what are the pros and cons of either alternative
bgbird said:
EZ-Unlock still lets me lock and unlock the bootloader. I'm also thinking of flashing VRLE6.bootloader.zip, rebooting, doing an EZ-Unlock and seeing what happens.
If that doesn't work - I'll have to decide
1. do I f staying where I'm at - running 4.1.2 ?
or
2. Do I give up and take the softbrick tar file and lock everything up ?
I'm not sure of what are the pros and cons of either alternative
Click to expand...
Click to collapse
If you're not rooted, EZ unlock just report false results.
If you like to play with custom rom/kernel, meaning not bug free and become a flashcoholic then stay with 4.1.2
If you want a stable, no headache trouble free then upgrade to 4.3
I upgraded my wife to 4.3 and very happy with the results. Everything just work, performance is very good and smooth, gps locked in seconds...enough said.
buhohitr said:
If you're not rooted, EZ unlock just report false results.
If you like to play with custom rom/kernel, meaning not bug free and become a flashcoholic then stay with 4.1.2
If you want a stable, no headache trouble free then upgrade to 4.3
I upgraded my wife to 4.3 and very happy with the results. Everything just work, performance is very good and smooth, gps locked in seconds...enough said.
Click to expand...
Click to collapse
Even if I had to stay on 4.1.2 I'd want CleanRom7 at least. I used that since July when it came out. I liked the features and customizations. I'd like to continue to flash - however every time that I try ( and you can see the results earlier in the thread) the phone wouldn't boot. I think that some part of the OTA got on the phone. For a period of time, I was constantly nagged to take the upgrade. I think that my son answered "yes" and some part updated - until stopped Cleanrom.
Anyway I tried to reflash CleanRom as well as the non-locked ML1 item. Each time, Samsung flashes, then the ornamental Samsung SIII graphic just sits there. In a normal boot, that only lasts a second. Maybe I'll try it again and let sit there for an hour or two and see if something changes.
bgbird said:
Even if I had to stay on 4.1.2 I'd want CleanRom7 at least. I used that since July when it came out. I liked the features and customizations. I'd like to continue to flash - however every time that I try ( and you can see the results earlier in the thread) the phone wouldn't boot. I think that some part of the OTA got on the phone. For a period of time, I was constantly nagged to take the upgrade. I think that my son answered "yes" and some part updated - until stopped Cleanrom.
Anyway I tried to reflash CleanRom as well as the non-locked ML1 item. Each time, Samsung flashes, then the ornamental Samsung SIII graphic just sits there. In a normal boot, that only lasts a second. Maybe I'll try it again and let sit there for an hour or two and see if something changes.
Click to expand...
Click to collapse
If you are switch from rom to rom, you may have trash residuals. I would wipe cache/dalvik cache/data/system before I flash another rom (clean install), saved me a lot of little issues here and there...
buhohitr said:
If you are switch from rom to rom, you may have trash residuals. I would wipe cache/dalvik cache/data/system before I flash another rom (clean install), saved me a lot of little issues here and there...
Click to expand...
Click to collapse
Formatting your internal SD may also be needed, because 4.3 creates a 0/ folder that 4.1 doesn't have.
Alternatively, philz touch recovery has a 0/folder migration that will clear out that folder when switching.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Formatting your internal SD may also be needed, because 4.3 creates a 0/ folder that 4.1 doesn't have.
Alternatively, philz touch recovery has a 0/folder migration that will clear out that folder when switching.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
two questions?
1. Do you have a link for philz touch recovery?
2. If I format the internal SD - will an nandroid backup still work? I thought that that had to back into an identical file structure...
Also I do a factory reset each time that I flash.
I know that I'm root because EZ-Unlock requires it. If root isn't enabled - it terminates. When Root is enabled, SuperSU asks permission to do the unlock
bgbird said:
two questions?
1. Do you have a link for philz touch recovery?
2. If I format the internal SD - will an nandroid backup still work? I thought that that had to back into an identical file structure...
Click to expand...
Click to collapse
1.
http://forum.xda-developers.com/showthread.php?t=2588639
2. No, The file structure gets completely replaced because a nandroid copies your internal sd card. It'll remake the folder structure.
Sent from my SCH-I535 using Tapatalk 2
Just a quick question to cover all the bases. Which version of EZ Unlock are you using? Version 1.2 is the only one that actually works to unlock your bootloader.
Im having a problem getting to the recovery screen of safestrap.
I just installed safestrap from this link here http://forum.xda-developers.com/showthread.php?t=2605648
and it said it was successful. When I clicked Boot into Recovery, the phone restarts and just hangs at the Samsung Galaxy SIII Screen.
pressing any of the keys, or trying to power it off does not work. I have to pull the battery.
Upon pulling the battery, I do get the safestrap overlay where it says safestrap is disabled. I click the menu button that says recovery and it just hangs on a black screen. And I need to pull the battery again. When i get back to the safestrap screen again, i can get my phone to boot as normal by clicking continue as oppopsed to recovery, but I still can not get safestrap to boot into the recovery screen to install a rom (I want to install a 4.3 Rom).
Does anyone have any advice? Im currently running on a rooted 4.1.2.
PS: Is there a rooted stock 4.3 rom? I dont have alot of experience with custom roms. I just want the latest stock rom, but have root access. If there is one, can someone please point me in the direction of it?
Safestrap is intended for people that took the 4.3 ota, so I'm not sure if it will work on 4.1.2. You should make sure your bootloader is unlocked and install a custom recovery. There are several threads that explain the process.
Sent from my SCH-I535
roaddog665 said:
Safestrap is intended for people that took the 4.3 ota, so I'm not sure if it will work on 4.1.2. You should make sure your bootloader is unlocked and install a custom recovery. There are several threads that explain the process.
Sent from my SCH-I535
Click to expand...
Click to collapse
Safestrap should work fine for any other versions of jellybean, (im assuming) he intends to install a custom rom while at the same time having a live back up of the stock one. Also safestrap is meant for people with locked bootloaders and even though you can unlock the bootloader (on 4.1.2) you really don't need to in order to install safestrap.
Mtsprite said:
Safestrap should work fine for any other versions of jellybean, (im assuming) he intends to install a custom rom while at the same time having a live back up of the stock one. Also safestrap is meant for people with locked bootloaders and even though you can unlock the bootloader (on 4.1.2) you really don't need to in order to install safestrap.
Click to expand...
Click to collapse
OK, I wasn't sure if it would or not. Thanks.
Sent from my SCH-I535
rslthara very
So wait... Do I even need safestrap then? or is there a way to install 4.3 without having my bootloader become locked. I thought that was the whole point of installing safestrap was to create a partion of the update before you actually update to it.
MattDusza said:
So wait... Do I even need safestrap then? or is there a way to install 4.3 without having my bootloader become locked. I thought that was the whole point of installing safestrap was to create a partion of the update before you actually update to it.
Click to expand...
Click to collapse
Safestrap is only for people who already updated to 4.3 rom with LOCKED bootloader. In your case, NO you don't need safestrap. You could install 4.3 for unlocked bootloader (in your case) here are a few:
http://forum.xda-developers.com/showthread.php?t=1904329
http://forum.xda-developers.com/showthread.php?t=2591895
http://forum.xda-developers.com/showthread.php?t=2608639
Gturvis mingled
Thank You. I guess I missed something when I was reading on how to avoid getting your bootloader locked in the process.
Hi all,
I apologize if this has been answered before, but I had trouble finding it here. I am currently rooted on a stock backup, but I am running a custom recovery. I am not sure where to find the stock recovery image for my device. I am using the HTC One M8 through Verizon, and I know that the new firmware update is coming out soon, and I'd like to be able to just OTA update my phone so that I can reflash a custom recovery and install the newest VenomROM. I have flashed a custom recovery before (obviously), but I didn't know if it mattered which firmware base you are running. I read somewhere that the recovery is totally separate from the OS, and it is meant to be an alternative to booting into the OS in case of a problem, but I want to be sure. If there is a specific recovery I need to use and someone here knows where I can find it, that'd be great. I found the collection of stock recoveries, but I'm having trouble figuring out which one I need to use. Any and all help is appreciated, thanks.
EDIT: My CID is VZW__001
My VERSION-MAIN is nothing. There's is just nothing next to this label.
I tried locating it on the collection of stock recoveries, but couldn't find it. I'm not sure why this is.
It takes more than stock recovery to take the OTA. The /system has to be essentially stock. Some mods (e. g. enabling powersave) may also csuse the OTA install to fail. There is a thread with a pseudo RUU. You ought to be able to get stock recovery there.
My name is Harold and I'm a flashaholic....
hgoldner said:
It takes more than stock recovery to take the OTA. The /system has to be essentially stock. Some mods (e. g. enabling powersave) may also csuse the OTA install to fail. There is a thread with a pseudo RUU. You ought to be able to get stock recovery there.
My name is Harold and I'm a flashaholic....
Click to expand...
Click to collapse
Hi there,
I actually just used the psuedo RUU tool (I assume this is the one you are talking about? http://forum.xda-developers.com/showthread.php?t=2727831)
I just finished using this tool, but when I went to check the recovery, all I get is a big red triangle with an exclamation point in the middle. Nothing else. So, I'm guessing that recovery didn't flash properly? But I'm honestly not completely sure. I would screenshot it, but I can't do that. Any help is appreciated.
EDIT: I found out that pressing volume up and power gives more options. I assume I am all good to go now? I am still rooted, and I'm not sure if that is a problem. I am stock, s-off and rooted, but I don't have any mods installed.
You can't do anything in stock recovery except take an OTA, assuming everything else is stock. You can't do Nandroids, flash zips, etc. Looks like you have stock recovery.
My name is Harold and I'm a flashaholic....
hgoldner said:
You can't do anything in stock recovery except take an OTA, assuming everything else is stock. You can't do Nandroids, flash zips, etc. Looks like you have stock recovery.
My name is Harold and I'm a flashaholic....
Click to expand...
Click to collapse
Yeah I just figured out how the more options appear. I assume I'm good to go for the OTA now? I've got stock recovery, running a stock backup, s-off and I'm still rooted, but I think those are not a problem. I am not running any mods.
ChuckFinley1992 said:
Yeah I just figured out how the more options appear. I assume I'm good to go for the OTA now? I've got stock recovery, running a stock backup, s-off and I'm still rooted, but I think those are not a problem. I am not running any mods.
Click to expand...
Click to collapse
You should be good to go. A cautionary note, however, is that if you are rooted (even if S-OFF), it's not always advisable to take the OTA because frequently OTA's plug exploits used to secure root, etc. There was a definite difference between the original stock Verizon M8 ROM releated 3/25/14 and the minor update which followed, and some were unable (myself included) to secure stable root and/or S-OFF with weaksauce, having to acquire a license to Sunshine instead.
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.
hgoldner said:
You should be good to go. A cautionary note, however, is that if you are rooted (even if S-OFF), it's not always advisable to take the OTA because frequently OTA's plug exploits used to secure root, etc. There was a definite difference between the original stock Verizon M8 ROM releated 3/25/14 and the minor update which followed, and some were unable (myself included) to secure stable root and/or S-OFF with weaksauce, having to acquire a license to Sunshine instead.
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.
Click to expand...
Click to collapse
That does sound pretty appealing. I've never flashed firmware before though, and I wouldn't want to mess anything up. I remember seeing on the VenomROM firmware section, the easiest way to flash new firmware is to just grab the OTA update. The other way involved using some other program that I have not used before. I am overestimating how difficult installing new firmware is?
ChuckFinley1992 said:
That does sound pretty appealing. I've never flashed firmware before though, and I wouldn't want to mess anything up. I remember seeing on the VenomROM firmware section, the easiest way to flash new firmware is to just grab the OTA update. The other way involved using some other program that I have not used before. I am overestimating how difficult installing new firmware is?
Click to expand...
Click to collapse
Firmware (splash screen, radios, hboot, recovery) are "flashed" with an S-OFF handset via fastboot from the bootloader, while connected to PC. I believe (again, based upon the RUU thread I mentioned previously which you seem to have found) that it may also be possible to flash from hboot using an update.zip file (I think the M8 file is called PB06IMG.zip, but don't hold me to that --- every phone has its own such file format/name.)
ROMs and mods are typically flashed via recovery.
hgoldner said:
Firmware (splash screen, radios, hboot, recovery) are "flashed" with an S-OFF handset via fastboot from the bootloader, while connected to PC. I believe (again, based upon the RUU thread I mentioned previously which you seem to have found) that it may also be possible to flash from hboot using an update.zip file (I think the M8 file is called PB06IMG.zip, but don't hold me to that --- every phone has its own such file format/name.)
ROMs and mods are typically flashed via recovery.
Click to expand...
Click to collapse
Okay, I may look into that. I've only seen an RUU flashed via hboot, so I'd have to look into it. At the very least though, I'd imagine someone will post the instructions on how to flash the firmware when it comes out.
Thanks so much for your help!
hgoldner said:
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.
Click to expand...
Click to collapse
+100 for this!
I am reading dozens of posts in all kinds of threads of people just dying to take that OTA...
Why???
I would not touch that new firmware with a 100 foot pole until the devs have figured out what it breaks!!!
I predict a flood of posts in the line of:
"I flashed back to stock to take the OTA and now weaksauce is not working - how do I get root back?"
What's the hurry?????
FAQ section in the 2nd post.
BEWARE OF EVERYTHING! I AM NOT RESPONSIBLE if your phone implodes, aliens take over Mars, don trump starts WW3 and WW4, or your dish washer starts working again from using this guide. Remember: just because it worked for me, does not mean it will work for you, but it might! I recommend having an ODIN copy (.tar file) of the MDL bootloader so in case anything goes south, you can get back to stock and start over from scratch.
IMPORTANT! This guide will show you how to (easily) maneuver around the At&t sgh-i337 on the MDL bootloader as far as root and other things are concerned. This guide is NOT for any other bootloader! Once you have updated past jelly bean 4.2.2 then you will not be able to use this guide!
Now for the good stuff...
So you've just taken your new At&t GS4 out of the box and discovered that you're on the MDL bootloader (like I did)! First you're going to want to root it. You can do this by grabbing a good 'ol copy of towel root (just search the forums here or Google for it). Next, you're going to want to freeze the OTA update so the phone won't update off the MDL bootloader (after installing SuperSU of course). You can do this via the Titanium Backup app or the MyBackup Root app (now called just MyBackup I think).
Let's recap...you will need a copy of the towel root app, then SuperSU, then TB or MyBackup Root app. SuperSU will kill the evil KNOX for you.
Next you may want to install a custom recovery. To do this, you will need to use an exploit file called Loki Doki. Follow this video to take the needed steps to get loki'ed and a recovery installed: https://www.youtube.com/watch?v=VmkL9atpVHw
Yes, I know it installs CWM which is way out of date, if you want to use TWRP go ahead. However, this guide deals with CWM so if you use TWRP you're using it at your own risk and going against the guide! GO WITH THE GUIDE!
However, if you want to update to TWRP recovery then this video by the same guy as in the last video should do it: https://galaxys4root.com/galaxy-s4-...or-verizon-galaxy-s4-with-twrp-v-2-8-4-0/amp/
Once you've got loki lurking around your phone's memory, you're good to install a custom ROM! TA-DA! Awesome how all that worked out isn't it?
How to install a custom (TW) ROM
If and only if you followed the ZedoMax video, you should now have OUDhs CWM Touch Req0very v1.0.3.4 installed. Now would be a great time to boot into it so power off your phone then hold power, home, and volume up at the same time. Hold it! Hold it! Hold it! Release when you see the CWM menu. Now let's Nandroid this hush puppy!
Goto backup and restore and hit backup. It will most likely save it to your internal memory, but you can copy it to SD card later, or just reboot now and move it. We now have a working backup in case your dog eats your homework. After that's done, make sure the ROM .zip file you are going to boot is on your SD card. Now go to wipe cache partition and select yes. Go to Advanced and wipe dalvik cache. Go to wipe data/factory reset and select yes. Goto mounts and storage and select format cache, then select format /system.
NOTE: If you want to keep all your personal data (pics, videos, etc.) then stop here! If you want to completely nuke your phone and start from scratch then select format /data from the mounts and storage menu.
Once you've formatted /system (or did a complete wipe by formatting /data too so now you have nothing), you're ready to install a ROM. Select install zip from SD card from the main menu. Find your ROM .zip file and select it. I used the latest GoldenEye ROM because it has an Aroma installer built in so it pretty much does everything for you once you tell it what you want. Easy!
ROM should now be installed and everything should work ok once your phone reboots out of CWM recovery.
How to boot a custom (AOSP/CM) ROM
WARNING! THIS IS EXPERIMENTAL! Following this may get your ROM booted or not. Do so at your phone's own risk! You could erase stuff on accident!
Place the ROM file on your SD card. Boot into recovery and select wipe cache partition. Then select wipe dalvik cache. Now select wipe data/factory reset. Once all that's done, you will need to format /system and /data. Now goto install .zip from SD card. Select your ROM file and pray to whatever higher power yourbelieve in that it worked. Next you're going to (maybe) need a kernel.
Kernels and Modems
Download a compatible kernel for the ROM you want to use. Boot into recovery and flash the .zip file for the kernel from your internal memory or external SD card. Be sure if you are booting a TW ROM that you use a TW kernel. Same goes for CM and AOSP.
Modems are pretty much universal on the MDL firmware and possibly on others as well. To flash a modem just select the .zip file and flash in recovery from your SD card or internal memory. You can use any baseband modem...MDB, MK3, NB1, OC3, etc.
FAQ Section
What is the MDL bootloader? It's the jelly bean 4.2.2 firmware for the at&t galaxy s4. It's a locked bootloader, however it has a flaw in it that can be exploited by Loki Doki to allow a custom recovery to be installed.
What is Loki Doki? It's something that exploits the flaw in the MDL bootloader allowing you to do things an unlocked bootloader can do. To my best of knowledge, it acts similar to a PlayStation modchip by tricking the bootloader into thinking that whatever you feed it, is authorized to boot.
Can I downgrade my bootloader to MDL if I took the OTA? Only if you're a Samsung or at&t smartphone hardware tech.
Why can't I use Loki on other bootloaders? Because the flaw that loki exploited was patched in the MF3 firmware. With the exception of the MDB bootloader which was the bootloader before MDL.
Do I need motochopper to root my at&t s4? Nope, towel root works just fine to get root on the MDL bootloader.
Why does OUDhs CWM recovery tell me root or recovery may be lost on reboot and want to fix it? I have no idea, I think it's a bug. Just select "go back" until your phone reboots and all should be fine.
Why does your guide say "experimental" for AOSP or CM based ROMs? Mainly because I haven't messed around with any and am basing on how to boot them off my time using the galaxy s2.
Why can't I use TWRP recovery instead of CWM? You can, as I pasted a link to get TWRP installed in my guide. It's just I based my guide around CWM because that's what I have always used. Do note that TWRP is different, so you'll have to figure out how to wipe and install the ROM property.
What's the difference between CWM recovery and TWRP recovery? Nothing really, except the UI and how they handle files and things. Due note that CWM recovery has been discontinued, while TWRP still thrives today with updates.
So I am on MDL and have OctOS 7.1.1 flashed but no root. I have tried towelroot with no success. I do however have TWRP 3.0 on my phone but SuperSU won't flash. Do you have any ideas?
Tubifex said:
So I am on MDL and have OctOS 7.1.1 flashed but no root. I have tried towelroot with no success. I do however have TWRP 3.0 on my phone but SuperSU won't flash. Do you have any ideas?
Click to expand...
Click to collapse
OctOS has root disabled by default. You have to flash a root .zip file to activate root. Make sure you are loki'ed and that you have the right TWRP version as well as the right root .zip for your phone. Towel root only works on stock Android jelly bean 4.2.2, 4.3, and kit kat 4.4.2
StoneyJSG said:
OctOS has root disabled by default. You have to flash a root .zip file to activate root. Make sure you are loki'ed and that you have the right TWRP version as well as the right root .zip for your phone. Towel root only works on stock Android jelly bean 4.2.2, 4.3, and kit kat 4.4.2
Click to expand...
Click to collapse
Where do you suggest I find root.zip file?
Tubifex said:
Where do you suggest I find root.zip file?
Click to expand...
Click to collapse
I am not too sure, I haven't messed with OctOs at all. Try here:
https://forum.xda-developers.com/galaxy-s4-att/orig-development/rom-team-octos-oct-n-t3532663
Someone there in that thread will probably know.
Finished! This guide is done!
Bump....happy flashing!
Does this APK work anymore? It will not download to my phone. I had to download it to my pc then transfer it via usb to my phone. When I go to install it I get an error saying There is a problem parsing the package.
Can anyone please provide the ATT-I337UCUAMDL-20130430103714.zip file? All the mirrors are dead
NVMD,found something similar here:
https://androidfilehost.com/?fid=23203820527944165
and here:
https://server.samsung-firmware.org...de28764422/ATT-I337UCUAMDL-20130430103714.zip
jabulon said:
Can anyone please provide the ATT-I337UCUAMDL-20130430103714.zip file? All the mirrors are dead
NVMD,found something similar here:
https://androidfilehost.com/?fid=23203820527944165
and here:
https://server.samsung-firmware.org...de28764422/ATT-I337UCUAMDL-20130430103714.zip
Click to expand...
Click to collapse
You are needing the MDL ODIN .tar / zip file correct?
7ravler said:
Does this APK work anymore? It will not download to my phone. I had to download it to my pc then transfer it via usb to my phone. When I go to install it I get an error saying There is a problem parsing the package.
Click to expand...
Click to collapse
Which APK file are you referring to? Towel root or something else?
StoneyJSG said:
You are needing the MDL ODIN .tar / zip file correct?
Click to expand...
Click to collapse
yep, but I've already found it
Thank you!
jabulon said:
yep, but I've already found it
Thank you!
Click to expand...
Click to collapse
Hi,
I'm trying to find a way to install MDL to be able to get past my att bootloader lock. I have everything except the MDL Odin file. Can you please tell me the link to get it. I'm new on the site sorry if Im in the wrong section. I want to be able to install custom rom on my SAMSUNG-SGH-I337 Att. I have already downgraded all the way to NB1 and rooted and updated all the way back to OK2 without losing Root access. I went ahead and reflashed stock for fun however to see if I could do it. It worked. So now I'm unrooted back on OK3 official via OTA. I just tricked the time on the phone, changed the date, to bypass ATT's stupid ota 24 hour update wait period inbetween updates. . So I have no issue experimenting because I have the way to downgrade all the way back to NB1 no problem with Odin and then Ota update back to OC3 then OK2, Ok3 ext. Ext. So I just need to get to MDL so I can use loki from what I have read. I'mean only able to get to NB1 basically due to lack of .tar/Odin file for the exploitable mdl bootloader.
So if I can get the Odin file or zip to MDL I will know what to do.. Thank you ahead of time for all your hard work! This post is amazing.
-Scott
(Hopefully I did this right lol)
Scottie32583 said:
Hi,
I'm trying to find a way to install MDL to be able to get past my att bootloader lock. I have everything except the MDL Odin file. Can you please tell me the link to get it. I'm new on the site sorry if Im in the wrong section. I want to be able to install custom rom on my SAMSUNG-SGH-I337 Att. I have already downgraded all the way to NB1 and rooted and updated all the way back to OK2 without losing Root access. I went ahead and reflashed stock for fun however to see if I could do it. It worked. So now I'm unrooted back on OK3 official via OTA. I just tricked the time on the phone, changed the date, to bypass ATT's stupid ota 24 hour update wait period inbetween updates. . So I have no issue experimenting because I have the way to downgrade all the way back to NB1 no problem with Odin and then Ota update back to OC3 then OK2, Ok3 ext. Ext. So I just need to get to MDL so I can use loki from what I have read. I'mean only able to get to NB1 basically due to lack of .tar/Odin file for the exploitable mdl bootloader.
So if I can get the Odin file or zip to MDL I will know what to do.. Thank you ahead of time for all your hard work! This post is amazing.
-Scott
(Hopefully I did this right lol)
Click to expand...
Click to collapse
Once your phone has been updated past MDL, you cannot go back. NB1 is the farthest back you can go without bricking. You are stuck with safe strap recovery for kit kat and flash fire for lollipop. You can only boot custom touchwiz ROMs.
Thank you so much!! You saved me a lot of time with this information. I can quit trying to find a way to go back. I will stick with flash fire and safestrap.
Scott
No problem. Be careful as safe strap works only with kit kat to my knowledge. If you're on NB1 I think that's kit kat. Flash fire works with lollipop as safe strap doesn't. Flash fire may also work under kit kat, but I am not sure.
StoneyJSG said:
Which APK file are you referring to? Towel root or something else?
Click to expand...
Click to collapse
Sorry to leave you hanging here. I was referring to towel root and I did find a good file. Thanks. I see you posted that I cannot go back to mdl after updating to OC3? Bummer! I should have researched a little more before I did that
Nope, once you update past MDL which is MK3 I believe it patches the loki doki exploit so it can't be used and also makes it so if you try to downgrade back to MDL you can brick the phone.
good guide.
err on the side of kindness