Related
Hello all,
sorry if this is a repeated question. I tried to read as much as I can in the Q&A and general sections, but could not find it.
I have a NS that was running CNA 1.4 for sometime. I got tired from the performance and I decided to give phone to my better half. Since my wife does not care much about custom roms, I decided to go back to stock so I can give her a care-free phone. She would be capable of doing the OTA updates on her own.
so, these are the steps I did to get to custom:
1. phone came with 2.3.4
2. unlock BL using ADB
3. root and install CWM
4. Nandroid backup
5. OTA update to 2.3.6
6. Nandroid backup
7. Custom ICS rom
when I tried to go back to stock I did a restore to step 6 above, the OTA was pushed automatically to my phone, but when I tried to install, the phone rebooted but did nothing and it seemed stuck at the android with an ! in a triangle.
I removed the battery, restored back to step 4 above and tried again and I got the same results.
I know I am probably forgetting something but I am not sure what is it.
Could someone please offer some direction?
thanks in advance.
Flash official factory images with fasttboot .
You cant get official OTAs when your device is rooted
thanks guys for your reply.
but what is the main cause for not being able to install OTA updates?
1. is it because the BL in unlocked?
2. or because of root?
if because of root, has anyone tried that app from the Market? could it be used to regain root after OTA?
https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper
thanks again.
You can get ota just fine on a stock (unmodified) rom with root. You will loose root when it updates. Then just reroot it.
Bootloader state is irrelevant.
albundy2010 said:
You can get ota just fine on a stock (unmodified) rom with root. You will loose root when it updates. Then just reroot it.
Bootloader state is irrelevant.
Click to expand...
Click to collapse
thanks for the info.
one last question, when I rooted my 2.3.4, it also installed CWM recovery.
Does CWM interfere with the OTA update or just the root?
if it interferes, I'll have to find a way to go back to stock recovery, right?
Yes and no.
For the OTA process to go as "normal' stock recovery needs to be there. Normal as in get the OTA notifcation/auto download reboot and install.
No as in if you manually download or place the ota zip file on your internal storage it will flash in cwm like any other zip.
Also since ICS you currently have to flash the ota zips with aftermarkt recoverys if you do it manually. The pick zip from sd card in stock recovery is broken now.
In the stock rom under /system/etc there is a script that overwrites custom recovery with the stock one on every boot. Rename that file to .bak or something instead of its default .sh If you want to stock recovery back just change the file extenstion back and reboot the phone fully. Next time you boot back into recovery it will be stock again.
Or you don t go to stock recovery and flash the updates by yourself on your phone. Downloaf them and then flash them through CWM. But i think u havent got CWM anymore after grtting an official update. You ll get the original recovery again
thanks again guys.
currently I can go back to either 2.3.4 or 2.3.6 stock roms but both have CWM and root.
ultimately what I want to do is:
1. be able to un-root (probably using this market app)
2. download OTA on phone, do normal "reboot and install"
3. boot up with updated OTA rom.
4. regain root (probably using the same market app)
so, what I understand from prev posts, that I must put back the stock recovery (which I do not mind) for my steps above to work.
can I use ADB and fastboot to push the stock "recovery.img"? and where to find it?
I'll do some searching in the forums, but if someone happens to have link to the thread, it would be fantastic.
thanks again
Why dont you keep the root and flash the official firmware that you downloaded per CWM. So you dont have to unroot and root again later. Or do a factory wipe.
ok guys, so whatever I tried to do I was not able to get the stock recovery back to go with the "normal OTA download on phone, reboot and install thing", so here is what I ended up doing.
1. I had 2.3.6 (GRK39F), rooted stock rom, cwm recovery.
2. Download/install "OTA Rootkeeper" free app from Google Play Market. link below
3. Using "OTA Rootkeeper" app, did a "backup root", then "temp un-root"
4. Download official signed Google ICS update package to upgrade from 2.3.6 (GRK39F) to 4.0.4 (IMM76D) and move it to sd card. link below
5. Reboot into cwm recovery
6. Install update from sd card and choose Zip from #4
7. Go back and reboot system
8. After upgrade to ICS is complete, use "OTA Rootkeeper" app, did a "restore root" and voila
9. So now I have rooted stock ICS rom, and cwm recovery.
notes:
these steps should also work on whatever stock GB rom you have as long as:
a. rooted
b. have cwm
c. download the proper update package in step 4 above.
links:
2. https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper
4. http://www.randomphantasmagoria.com/firmware/nexus-s/
thanks again guys, couldn't have done without your help
good luck for anyone trying to do the same.
1.Download appropriate rom for your phone
i9020T or i9023
http://downloadandroidrom.com/file/NexusS/roms/ota/2.3.6/i9020t_i9023.zip
and i9020a
http://downloadandroidrom.com/file/NexusS/roms/ota/2.3.6/i9020a.zip
2.Copy it to sdcard
3.Install it through recovery (CWM)
4.Restart system
5.Reboot phone into bootloader
6. Hit recovery and once you get the lil droidy and the !, Push Vol up + Power until you get blue menu
7. Go to wipe data/fact reset
8.Reboot to bootloader
9.then go into adb and type fastboot oem lock
By this time you shouldve completely returned your phone to stock and you are able to get ota updates and everything!!! YAY!!!!
http://www.randomphantasmagoria.com/firmware/nexus-s/
if you wanna go back to 100% stock unrooted, download any rom from that thread and install through cwm then reboot and you will be stock and unrooted with stock recovery and then just lock the boot loader and you will be 101% factory stock and ready to receive ota updates. I would recommend the 2.3.6 because it will give you the 4.0.4 ota right after you reboot.
So I just rooted my Verizon Galaxy S3 and unlocked the bootloader. I flashed Clockworkmod recovery using Rom Manager to update to the latest version. Made a nandroid, installed Titanium Backup, linked it to my Dropbox and uploaded. I downloaded the latest CM10 nightly to flash but the stock android recovery appeared instead of CWM. Found some info that I need to flash a clockwork compatible kernel first. The questions I have are: If I install the latest CM 10 nightly will it automatically install a clockwork compatable kernel? If not, where can I download it from? and if I do need to flash a kernel first can anyone give me detailed instructions how to do this as i'm relatively new to this stuff and don't want to brick my phone. Thanks, any info would help.
iwearthebelt said:
So I just rooted my Verizon Galaxy S3 and unlocked the bootloader. I flashed Clockworkmod recovery using Rom Manager to update to the latest version. Made a nandroid, installed Titanium Backup, linked it to my Dropbox and uploaded. I downloaded the latest CM10 nightly to flash but the stock android recovery appeared instead of CWM. Found some info that I need to flash a clockwork compatible kernel first. The questions I have are: If I install the latest CM 10 nightly will it automatically install a clockwork compatable kernel? If not, where can I download it from? and if I do need to flash a kernel first can anyone give me detailed instructions how to do this as i'm relatively new to this stuff and don't want to brick my phone. Thanks, any info would help.
Click to expand...
Click to collapse
Did you unlock your bootloader? for a custom recovery to stick you need to unlock your bootloader. Follow this guide
http://forum.xda-developers.com/showthread.php?t=1762709
darkhawk3383 said:
Did you unlock your bootloader? for a custom recovery to stick you need to unlock your bootloader. Follow this guide
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I did, had it unlocked and rooted. I guess there was some sort of issue with Rom Manager on the S3. I use it on my Galaxy Nexus and have no issues. I ended up abandoning what I was doing, uninstalling Rom Manager and going a different route. I have no prior experience with Odin but figured out how to install CWM . Downloaded I535vrblk1, flashed CWM, unlocked & rooted again. . Thanks anyway for the reply.
You can reinstall ROM Manager. It is something to do with some of the newer OTA's and the leaks. I have read a few posts in the forums about this in the GS3 and I really can't remember the fix but your recovery not sticking had nothing to do with ROM Manager. I think the fix was when you rebooted to recovery to flash a kernel right away, whether it be KT747, LK, or any of the other. Now that I typed this I'm about 99% sure that was the fix. Like I said above though, it has nothing to do.with ROM Manager, so if you're like me and find a lot of the tools in it handy you should be able to reinstall it. If you have a problem again just flash a kernel.
Sent from one of the many Anthropomorphic Personalities on the Disc
OK, so the MotoDev team advised me to return my phone to stock before installing JB, which will be pushed to my phone tomorrow morning...
What do I need to insure my system won't crash?
I have an unlocked bootloader, and am rooted. I already did a factory reset on my device. Some system apps are gone though, as I have deleted them (mostly Google stuff though, nothing crucial). Will I be good to go? (And yes, I will save the SBF and post it, no worries, have a Dev Host account and will upload).
In order to get official OTA updates from Sprint I've always needed to do 2 things:
-Remove Root (eith via OTA Rootkeeper or stock kernel)
-Flash Stock Recovery (OTA has never worked for me w/ custom recovery)
I'd recommend wiping and flashing both stock images in the thread below via fastboot to avoid bootloops and other hassles.
http://forum.xda-developers.com/showthread.php?t=1856456
hope things go well! :good:
hagforz said:
In order to get official OTA updates from Sprint I've always needed to do 2 things:
-Remove Root (eith via OTA Rootkeeper or stock kernel)
-Flash Stock Recovery (OTA has never worked for me w/ custom recovery)
I'd recommend wiping and flashing both stock images in the thread below via fastboot to avoid bootloops and other hassles.
http://forum.xda-developers.com/showthread.php?t=1856456
hope things go well! :good:
Click to expand...
Click to collapse
Thank you, I will do exactly as you directed...hope things go well also, it's about damn time for JB!
Moto Q stock with Arrrghhh's kernel v.0.10
galacticservant said:
Thank you, I will do exactly as you directed...hope things go well also, it's about damn time for JB!
Moto Q stock with Arrrghhh's kernel v.0.10
Click to expand...
Click to collapse
If you want to grab the update package and save it you should prevent it from being deleted. I know that twrp could not install asa14 OTA update when I got it so it was just hanging there in /cache along with md5 (or sha1, I can't remeber) checksum file.
I do not know if there are other ways of saving the update package nor if devs actually need it. But ASA14 got to my bootloader unlocked, gsm modded, rooted stock rom and after booting to recovery it just stayed there, no install happend (I installed it manually) because twrp did not pass the command properly or what ever the reason.
This update is coming from motorola directly, not sprint, right?
Anyway, perhaps someone can give you more accurate details. I personally would flash twrp and see if updated arrives. Because /cache is wiped by the update installer after installation. All automated process. After device boots to recovery it installs the package, wipes caches and reboots, if I am not mistaken.
I believe for the past updates we had the best luck by reverting the recovery back to stock as well. You have missing APKs that you removed so those will very likely be looked for by the update and will fail the update process if missing.
So if all goes well this should be the bare minimum I'd say for getting the update to work:
MAKE A BACKUP, don't want to have a bricked phone yeah? I mean you could have Jelly Bean on it finally... but still bricked...
Revert the recovery to stock if you installed TWRP or ClockworkMod, adb reboot bootloader | fastboot flash recovery recovery.img
Restore any and all apps you deleted from the stock image, either by restoring fully to stock or putting them back manually, wouldn't hurt to do another update check in the play store for them as well.
Temp unroot with OTA Rootkeeper
Download the update, reboot it, do a song and dance, ???, profit.
Now, you might try to restore root asap, it may or may not work, we won't know till we try.... I'm using Superuser 3.1.3 and on their website it claims its for arm devices 2.0-4.1 so maybe it'll work. Your bootloader should still be unlocked I'd imagine, so you can reflash your custom recovery and make a new backup.
Hi guys,
Looking for some advice.
I previously had my phone rooted on 4.2 and everything was working great. For some reason I decided to install the OTA 4.3 update before reading here what it did. Before that though, I did a full backup through CWM.
Anyway, I'm now having trouble re-installing CWM to get back into recovery mode and go back to my backup.
When I try flashing it through Odin, it says Failed, and it seems like the phone blocked it because it is a recovery system.
Currently, when I boot up, I get the Custom logo, and when I try to go into recovery mode, it gets blocked and says it's unauthorized software, so I don't think I really installed the update right.
So, is there anyway to get CWM back on the phone to revert to my backup, or is there a way to flash the whole backup from a PC? The file is still intact on my SD card.
Thanks!
phlass said:
Hi guys,
Looking for some advice.
I previously had my phone rooted on 4.2 and everything was working great. For some reason I decided to install the OTA 4.3 update before reading here what it did. Before that though, I did a full backup through CWM.
Anyway, I'm now having trouble re-installing CWM to get back into recovery mode and go back to my backup.
When I try flashing it through Odin, it says Failed, and it seems like the phone blocked it because it is a recovery system.
Currently, when I boot up, I get the Custom logo, and when I try to go into recovery mode, it gets blocked and says it's unauthorized software, so I don't think I really installed the update right.
So, is there anyway to get CWM back on the phone to revert to my backup, or is there a way to flash the whole backup from a PC? The file is still intact on my SD card.
Thanks!
Click to expand...
Click to collapse
There is currently no way for you to flash CWM onto your S3 now that you have TW 4.3 VRUMCL1 update. If you want root, you will need to use Saferoot. If you wish to flash custom roms, you are currently only able to flash custom TW 4.3 roms via the use of SafeStrap. With Safestrap installed, you will be using a customized version of TWRP. Any and all of your CWM backups are incompatible and wasting storage space. Links to everything I just mentioned are contained in our TW 4.3 discussion thread.
Note that when you use Saferoot to gain root access, the tool is in the S4 section however it states that there is nothing in the tool itself that is S4 specific and that it should work on other 4.3 devices. It does work. Search in the discussion thread or in Saferoot thread to see confirmation.
Edit: to work around the Yellow triangle issue, you'll want to use ThePagel's soft brick thread.
Edit #2: Also, being that you are on TW 4.3 update, you absolutely can not downgrade your firmware using pre-existing Odin stock images. You can only use the official, VRUCML1 tar that is about 1 GB.
SlimSnoopOS said:
There is currently no way for you to flash CWM onto your S3 now that you have TW 4.3 VRUMCL1 update. If you want root, you will need to use Saferoot. If you wish to flash custom roms, you are currently only able to flash custom TW 4.3 roms via the use of SafeStrap. With Safestrap installed, you will be using a customized version of TWRP. Any and all of your CWM backups are incompatible and wasting storage space. Links to everything I just mentioned are contained in our TW 4.3 discussion thread.
Note that when you use Saferoot to gain root access, the tool is in the S4 section however it states that there is nothing in the tool itself that is S4 specific and that it should work on other 4.3 devices. It does work. Search in the discussion thread or in Saferoot thread to see confirmation.
Edit: to work around the Yellow triangle issue, you'll want to use ThePagel's soft brick thread.
Edit #2: Also, being that you are on TW 4.3 update, you absolutely can not downgrade your firmware using pre-existing Odin stock images. You can only use the official, VRUCML1 tar that is about 1 GB.
Click to expand...
Click to collapse
Ok great. Thanks for the help.
phlass said:
Ok great. Thanks for the help.
Click to expand...
Click to collapse
Don't hesitate to post back if you're stuck or need a little more clarification
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