Database Info

[Q] Odin can't flash stock, boot hangs at logo

Good morning...
Right now, my phone (Galaxy S III on Verizon) will not boot past the "Galaxy S III" logo. Odin will not flash a stock Jelly Bean ROM from StockRoms.net. It gets stuck on the first .img, boot.img. I am downloading a new stock ROM right now and will try a full wipe.
Being silly and ambitious, I do not have a nandroid before it wouldn't boot. On Monday (two days ago) I rooted it. I flashed the VRALEC boot chain, rebooted, flashed ClockworkMod recovery, and installed the SuperSU bootloader and root patch through recovery. I rebooted, allowing CWM to disable the automatic re-flashing of the recovery. With my newly rooted phone, I jumped at trying to install Google Wallet. I went with the route of using Wallet Installer as found on the app store. And, being silly, I checked all three OS options (JB, ICS, and one other). After authorizing the superuser request, my phone almost immediately shut off. I think I made a nandroid through CWM after that, but not one that would run.
I thought it was going to be just build.prop having issues, so I went on a wild quest trying to find a working one online and get it on the device. I worked it into the updater script of my SuperSU patch. Nonetheless, nothing there fixed it. I've tried a bunch of things, including (get this) extracting the stock system.img.ext4 image, mounting it, tarring the device, creating an MD5 for it, and wrapping it up like a nandroid to "restore" with CWM.
I'm thinking I'm going to try and wipe the entire device, maybe leave /recovery, and flash a new I-535 ROM with Odin, see if that works. I don't know if it will. Any advice?
My flash counter is at about 5 after many attempts to get back to something that will boot, so warranty is not an option. Not that they've ever been a whole lot of help anyways.

Sounds like you can still enter recovery. If so adb push a custom ROM to your phone to flash.
Sent from my SCH-I535 using Tapatalk 2

What I have done in the past when flashing a completely stock unrooted ROM through Odin is remove the battery, replace it, boot to stock recovery, and do a factory reset plus wipe cache! This will make my phone boot every time, because flashing a stock makes it boot loop!
Sent from my SCH-I535 using xda app-developers app

joaquinla1 said:
What I have done in the past when flashing a completely stock unrooted ROM through Odin is remove the battery, replace it, boot to stock recovery, and do a factory reset plus wipe cache! This will make my phone boot every time, because flashing a stock makes it boot loop!
Click to expand...
Click to collapse
My phone has CWM recovery on it, but I don't see any reason CWM's factory reset and cache wipe would be any different. I'll give it a shot.
mentose457 said:
Sounds like you can still enter recovery. If so adb push a custom ROM to your phone to flash.
Click to expand...
Click to collapse
I may try this if I can't upload one through Odin after a complete wipe, like above. Also, I've only used adb push to upload individual files. How would I use it to push a ROM?
Thanks for all your help. The ROM I'm going to try and flash now is the official stock from stockroms.net. I can't post the link as I'm new but it's I535BLK_nowipe.zip. I'll keep this updated.

sworld said:
I may try this if I can't upload one through Odin after a complete wipe, like above. Also, I've only used adb push to upload individual files. How would I use it to push a ROM?
Click to expand...
Click to collapse
When you download a ROM, say Beans 11, it will be a zip file. Push that single file to the internal storage. Do not unzip it. Then boot into recovery and flash the zip.
Sent from my SCH-I535 using Tapatalk 2

mentose457 said:
When you download a ROM, say Beans 11, it will be a zip file. Push that single file to the internal storage. Do not unzip it. Then boot into recovery and flash the zip.
Click to expand...
Click to collapse
That makes more sense.
UPDATE: I "factory reset" the data partition and formatted /system and /cache through ClockworkMod. Turned it off, flashed VRALEC through Odin, rebooted, flashed the stock ROM, and then CWM. I'm restoring my nandroid of /data right now, and I'm awaiting an OTA firmware update to bring it up to the latest VZW JB. Then I'll root.. finally.

The thing with Odin is that after you reset you have to do a factory reset through stock recovery to finish the process. Otherwise you will get stuck in a boot loop like you did.
Sent from my GeeEssThree

z06mike said:
The thing with Odin is that after you reset you have to do a factory reset through stock recovery to finish the process. Otherwise you will get stuck in a boot loop like you did.
Sent from my GeeEssThree
Click to expand...
Click to collapse
Really? I've only odined once on the s3 and didn't have to wipe. On the fascinate and an older version of Odin after the flash before it booted it would automatically wipe.
Sent from my SCH-I535 using Tapatalk 2

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

So, the phone is functioning now. Of course, I am running a slightly older version and once I connect to a solid Wi-Fi network I'll request the newest update again.
However, I did already try to download the software update from Verizon, and it seemed to work fine. It rebooted into recovery and CWM seemed to handle it okay, although it claimed the signature was bad. It installed though, rebooted, and updated some app databases. And then, it said the update failed with "Code 401."
Right now I'm not too worried. Hopefully I can apply the update properly soon. It is worth noting that simply using CWM "advanced restore" on only the /data partition, without exactly matching the ROM build, has seemed to leave it hanging at the "4G LTE" logo.
Thanks for all of your help!

The phone will not install a Verizon update with a custom recovery installed.

[ROM/GUIDE] 4.4.2 [LG Stock Rom] [Custom Recovery - Kernels - Root]

First off huge thanks to every dev in this thread. At the time my G2 was being repaired so I didn't get to help out
By following the steps below, you can run the new 4.4.2 kitkat rom from LG (and 4.4.2 stock modified roms to come) with our old partitions which are fully loki-able
DO THIS ENTIRE PROCESS AT YOUR OWN RISK - IF YOU DO NOT UNDERSTAND THESE DIRECTIONS, THEY ARE NOT FOR YOU. I TRIED TO MAKE THEM AS SIMPLE AS POSSIBLE. THIS WILL WIPE YOUR WHOLE PHONE. THIS IS FOR D801 ONLY.
Also please no stupid questions, I will not answer. I will try to help with legitimate problems.
If you upgraded to 4.4.2 through the KDZ or flashed the 4.4.2 stock rom from smiley on this forum (since he included the new partitions) you must follow every step here. If you are still on 4.2.2 partitions (You have these if you currently are using an aosp / cm rom with a custom recovery) - Then you may go straight to step 5.
1. You must revert to stock 4.2.2 using this guide. You must restore to the C version. DO NOT USE G. You can find the link to 801C here.
2. Once you successfully flash this, your phone should boot loop on the T-Mobile screen. Boot into recovery (which is now LG's stock recovery) once you are in press power twice to data reset. Remove the USB cable from the phone when trying to boot to recovery, it makes it much easier for some reason. After data reset your phone should now boot into stock LG 4.2.2
3. Root your phone with this.
4. Install a custom recovery with this guide. The TWRP listed in this guide is old and you must this one instead. Method 1 works fine for this if anyone is wondering.
5. At this point you should have 4.2.2 partitions with root and custom recovery. Bet you wish you didn't update to 4.4.2 Stock at this point :good:
6. Boot into recovery. FULL WIPE EVERYTHING (Except for internal storage. This mean you wipe System Data Cache and Dalvik. Very Important.) Flash this Rom in recovery that I put together (And here is a Mirror). It contains the 4.4.2 KDZ system image with the 4.4.2 modem. Make sure you backup your EFS. The kernel inside this rom is stock LG 4.4.2 with a minor change to allow it to boot on the 4.2.2 bootloader. Thanks to the dev's in that thread who worked on it.
7. Flash SuperSU for root.
8. You are now on 4.4.2 Stock rom with recovery, root, loki and the ability to flash custom 4.4.2 stock kernels when they are released (soon)
At this point you will be able to flash any rom you want, including aosp stuff. Do not flash any other kernel on the included LG 4.4.2 stock rom. I will be making a custom kernel / 4.4 stock roms for this soon anyway - WHEN FLASHING 4.4.2 STOCK ROMS PLEASE MAKE SURE THEY DONT HAVE PARTITIONS BESIDES SYSTEM/MODEM/RPM/TZ INSIDE!!!! JUST OPEN THE ZIP AND CHECK INSIDE. ANYTHING EXTRA YOU WILL HAVE TO REDO THIS ENTIRE PROCESS !!!!!!!! I really hope devs stop putting up roms with the new partitions included.

Excellent. Thank you

Awesome great job Doc.
Sent from my LG-D801 using XDA Premium 4 mobile app

Excellent! Thank you!
One question, will this work for the D800? J/K :laugh:

Just what I've been looking for. Thanks.

Niceeeeee !!!!!!
Finally, Thanks to everyone involved in making this possible. :good:

Can't get the download to finish, mirror?
Sent from my LG-D801 using xda app-developers app

Smokeey said:
Can't get the download to finish, mirror?
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
I'll put up a mirror for the stock rom zip, its going to take a little bit to upload. Guessing 25 mins from now expect the link.
Edit: Mirror up under Step 6

Thanks man.

I love you full homo lol
Sent from my LG-D801 using XDA Premium 4 mobile app

Super happy about this. I've been crack-refreshing this forum waiting to see this happen. Now, any way to do this on a Mac since the LG tool doesn't work?

adampdx said:
Super happy about this. I've been crack-refreshing this forum waiting to see this happen. Now, any way to do this on a Mac since the LG tool doesn't work?
Click to expand...
Click to collapse
no clue, you need to search around. Never had a mac Maybe you can get access to a laptop or something

dr87 said:
no clue, you need to search around. Never had a mac Maybe you can get access to a laptop or something
Click to expand...
Click to collapse
I have searched into the depths of Google. To my knowledge, besides the LG tool there is no way to flash a .kdz file on a Mac. I have a Windows desktop and even a VM on the Mac, but my desktop keeps blowing power supplies and I haven't set up Windows on the VM. Oh, well! Looks like I know what I'm doing this weekend.

OK. I am currently on Mahdi 2.5 with TWRP 2.6.3.5. I have a backup of stock 801c from just after I rooted. Can I revert to that backup and then just flash this?

Project X-Ray said:
OK. I am currently on Mahdi 2.5 with TWRP 2.6.3.5. I have a backup of stock 801c from just after I rooted. Can I revert to that backup and then just flash this?
Click to expand...
Click to collapse
"If you are still on 4.2.2 partitions with a custom recovery / aosp you may go straight to step 5."
I just made it more clear in the OP what 4.2.2 partitions are

Is someone going to be a beast and make a video tutorial for this?? Need me a video tutorial to really grasp it for me to feel completely safe. Lol. Really want custom recovery. Anyways THANK YOU to those who whipped this up!
Sent from my LG-D801 using xda app-developers app

Flashing supersu fails for me. Cant figure out how to get around it. Also seems i lost root. any ideas?

davidgq said:
Flashing supersu fails for me. Cant figure out how to get around it. Also seems i lost root. any ideas?
Click to expand...
Click to collapse
Well with no SU you won't have root of course. What does the error say. I completed this whole process twice and never ran into this issue.

dr87 said:
Well with no SU you won't have root of course. What does the error say. I completed this whole process twice and never ran into this issue.
Click to expand...
Click to collapse
During the flash it says it is unable to open the zip file

Everything running Smooth
Did the whole proccess with no problem, Been running on KK for a couple of hours with no issues except for Gmail bookmarks not syncing on LG's stock browser. Battery looks pretty decent, should get better after a few cycles.

[How-To] I installed a custom Lollipop ROM on my AT&T Galaxy S4 and it was easy!

EASY... relatively speaking.
I read XDA forums for hours and hours... and hours. Seriously. I spent about 20 hours reading XDA just for this. All the info is out there, but it is spread out across a dozen different threads, and multiple posts within those threads.
When I actually went through the process, I had (no lie) eighteen windows open, each with a relevant thread/post.
Sheesh, and people think this is complicated... [/s]
But in the end - I have a custom Lollipop ROM on my phone (Goldeneye v53) and it is working beautifully. And I had NO issues with the process, it all went smoothly.
The phone (which previously was starting to run out of space, lag, and just all-around felt "old") is now like new. And, dare I say... better than a stock S6? It is certainly leaner and meaner than a stock system (that's a good thing - I despise all the bloat on stock systems)
So, to make it easier for all those who come behind me, here is how to do it. In 39 easy steps.
One post.
One list.
Bullet points.
Links.
EASY.
Do this EXACTLY - and you will have a custom ROM on your S4.
Do something "just a little" different... Or miss a step... I'm pretty sure your device will explode, or at least catch on fire.
Either way, there is no express or implied warranty on this process I have collected and posted here. Anything you choose to do to your device is on you, and if something goes wrong, I accept no liability.
For risk mitigation in my case (as I'm an overly anal type) - I made sure that I dug my previous phone out of the closet, charged the battery, installed my SIM, and confirmed that I could use the old phone to at least make calls/texts in the event that "something" happened to my S4 during the upgrade process and I had to go to work the next day without my S4. Everything went smoothly, but IMO you should definitely have a contingency plan just in case.
Note - this is only for those NOT on MDB or MDL bootloaders. You guys have it easy. Don't do all the crap below - you don't need to, and if you DO do it, you are locked into this "complicated" method FOREVER (mwa-ha-haaa!!!)
1. Preparation
1.1 READ THROUGH THIS POST 27 TIMES (NO LESS, NO MORE) AND MAKE SURE YOU "GET IT". IF NECESSARY, READ THE THREADS LINKED THROUGHOUT THIS POST. <<< THIS IS THE SINGLE MOST IMPORTANT PART OF THE PROCESS. IF YOU JUST READ THE FIRST FEW STEPS AND START FLASHING CRAP, YOU ARE GOING TO F SOMETHING UP. READ IT ALL, UNDERSTAND IT, THEN DO IT. I CAN'T EMPHASIZE THIS ENOUGH.
1.2 Backup. Back your stuff up. Back it all up - ALL of it. Understand that whatever you do not back up now, YOU WILL LOSE. This process is going to wipe your device clean. Anything you want to save, you need to back it up now.
1.2.1 Do not use Titanium Backup - for anything. It will F your stuff up. Which is unfortunate, because TB is a great app that is incredibly useful - just not this time. Apparently TB has issues when migrating form one version of Android to another (i.e. 4.x.x to 5.x.x). Sorry, but you gotta do it manually.
1.2.2 Copy your pics/vids to your PC
1.2.3 Use "SMS Backup& Restore" from the Play store
1.2.4 Let Google sync your contacts and calendar.
1.2.5 Any apps that store your data locally (not sync'd to their server) - manually find it (I like ES File Explorer) and copy it to your PC if you care about it.
All of that said - I found that wiping my device and migrating to Lollipop was a GREAT way to clean a bunch of useless crap I no longer needed off of my phone.
2. Rooting and Flashing STOCK KitKat (4.4.2) ROM (relevant thread - see post #2, under the "NB1 - KitKat 4.4.2 > Option 2" section.
Note: The reason you have to do this is because you must have rooted Lollipop on your device in order to flash custom Lollipop ROMS. If you just want stock, non-rooted Lollipop maybe you COULD just use Odin to flash Lollipop directly? But there is no way to get root on Lollipop directly - and you must be rooted if you want to wind up with a custom ROM. So you have to do this intermediate step of flashing and rooting a 4.4.x or higher OS. This version of NB1 is easiest because you can use Odin to flash a ROOTABLE ROM which makes the root process simple with Towelroot.
2.1 Download Odin v3.09 here. Place on PC.
2.2 Download ROOTABLE NB1 ROM here. Place on PC.
2.3 Download towelroot v3 here. Place on PC and copy to device (likely your SD card).
2.4 Use Odin to flash ROOTABLE NB1 ROM to your device. When the phone boots up, just speed through the "initial setup" screens, it doesn't matter since you're going to install a couple more ROMs before the finished product.
2.5 Go to settings>more>security and check "unknown apps", and uncheck "verify sources".
2.5 Navigate to towelroot v3, and install it.
2.6 Open towelroot and click the "make it rain" button.
Congrats, you are now rooted on KitKat NB1.
3. Upgrading to ROOTED STOCK OC3 (Lollipop) using "keep root" method (relevant thread)
As mentioned, this process takes you from ROOTED NB1 (KitKat, 4.4.x) to OC3 (Lollipop, 5.x.x). The only way to get rooted OC3 is to first get root in any 4.4.x version or higher and then upgrade to OC3 using the "keep root" method. There is (as of this writing) no way to root OC3 Lollipop directly. "keep root" reference thread - post #1
3.1 Download Flashfire app using below steps. (no direct link available).
3.1.1 Join the G+ community using the same Google account as you're using for Play on your phone/tablet Here.
3.1.2 Sign up to receive the BETA versions from Play Here.
3.1.3 Use the link provided after sign-up to download the app. Note - the link was not immediately available for me, and apparently that is normal. (There was a link, but it told me something like "link not found" when I tried to access it at first.) I had to sign up, and then 30 minutes later I went back and had access to the Flashfire file.
3.2 Download I337_OC3_Stock_Rooted_ROM here.
3.3 Place ROM on SD card.
3.4 Use Flashfire to flash ROM (see "keep root" reference thread from above for specific details of using Flashfire)
Congrats, you are now on rooted (stock) Lollipop.
4. Install your CUSTOM Lollipop ROM
4.1 Download ROM and prepare Safestrap recovery
4.1.1 Download your chosen ROM. I chose Goldeneye v53 here. (I chose Goldeneye because after brief reading, Goldeneye seemed to be one of the more stable options, and stability is what I wanted when going through this the first time.) Place it on your SD card. Here are other options for Lollipop custom ROMs on AT&T GS4. If you happen to wander into the development section and see all the shiny, new, intriguing ROMs floating around, keep in mind that most of them won't work for the AT&T GS4. Any custom ROM on this device must be based on Touchwiz and setup to be compatible with safestrap - only a handful meet those criteria.
4.1.2 Download Safestrap v3.75 here. Place it on your SD card. Do not install it at this point, Safestrap is currently not compatible with Lollipop - you are going to flash a different Kernel in Step 4.2 to work around this.
4.1.3 Download BusyBox from Play store
4.1.4 Install BusyBox on your device.
4.1.5 Install Safestap 3.75
4.1.6 Open Safestrap
4.1.7 I did not do this step because I did not start this process with any previous version of SS on my phone. But if you did have a previous SS recovery installed, use the Safestrap to "uninstall" the previous recovery version. It is my understanding that you can't install v3.75 on top of another version, you need to first remove the old version before installing the new version. The "uninstall" option is done from within the SS app, not the Android application manager - you are uninstalling the custom recovery, not the SS app.
4.1.8 "Install Recovery" (from within Safestrap). NOTE: this only INSTALLS safestrap, it does not boot you into safestrap recovery. There is no need to go into safestrap recovery yet. That's later.
4.2 Flash NC1 Kernel
As mentioned above, you need to flash the NC1 Kernel so that you can do your thing in Safestrap. But then you MUST remember to reflash the OC3 Kernel after using Safestrap to install the ROM, or else your phone will explode (probably).
4.2.1 Download NC1 flasher app from here. Place it on your SD card.
4.2.2 Download I337_stock_OC3_kernel_recovery_flashable from here. Place it on your SD card.
4.2.3 Download OC3 modules from here. Place it on your SD card.
4.2.4 Open NC1 flasher app and press "flash" (it's the only button)
4.2.5 Wait for completion and press reboot. NOW you will get automatically rebooted into safestrap recovery.
4.3 Install your custom ROM!!!
(note: all the below is done in safestrap recovery)
4.3.1 Go to "Wipe" and perform factory reset (will wipe system data, cache, and dalvik)
4.3.2 Flash your ROM. For Goldeneye ROM, it uses the AROMA installer. Choose the options that you like, but make sure to READ THEM ALL BEFORE SELECTING ANYTHING - IF ONE OF THE OPTIONS MENTIONS AT&T/SAFESTRAP, YOU MUST CHOOSE THAT OPTION. HELLFIRE, BRIMSTONE, AND ETERNAL DAMNATION WILL AWAIT YOU IF YOU CHOOSE ANOTHER OPTION.
4.3.3 At the end of the ROM installation, uncheck the "reboot now" option and continue - it will send you back to safestrap.
4.3.4 From within SS, install the OC3 modules from your SD card.
4.3.5 From within SS, install the I337_Stock_OC3_kernel_recovery_flashable from your SD card.
4.3.6 Reboot > system
4.3.7 Keep hitting "continue" when you get the safestrap recovery screen. This is a symptom of Lollipop not being compatible with Safestrap. Hit "continue" repeatedly (like 4 or 5 times) and eventually you will get into your ROM.
4.3.8 (Optional) Install safestrap.apk (that you d/l to your SD card) to your phone, and then use it to UNINSTALL recovery. This will avoid the above step 4.3.7 happening every time you reboot your phone.
Congrats, you now have a custom Lollipop ROM running on your device.
Note: SuperSU is finicky on Lollipop. See this thread for how to manipulate SuperSU to get your root apps working.
.
.
.
.
See? EASY.

Safestrap never works. I always select recovery when its powering on and it just powers up normally and takes me to my lockscreen. I installed safestrap using the apk, im already rooted on stock lollipop.

Israelsalinas19 said:
Safestrap never works. I always select recovery when its powering on and it just powers up normally and takes me to my lockscreen. I installed safestrap using the apk, im already rooted on stock lollipop.
Click to expand...
Click to collapse
You probably missed the step where he said to flash the nc1 kernel.

Yup, safestrap is known to be not fully compatible with OC3, that's why you have to flash the NC1 kernel in order to be able to use SS to flash your custom ROM. Don't forget to flash back to the OC3 kernel though, as stated in step 4.3.4.

Bootloops everytime. Flash kernels and modules after rom..reboot, samsumg custom screen then safestrap then 10 seconds later back to custom screen. After flashing kernels and modules I'm still able to get into recovery, nc1 should be gone in order for ss to work. I'm so sick of odin... :what:
Sent from my sghi337 on oc3

robot_head said:
Bootloops everytime. Flash kernels and modules after rom..reboot, samsumg custom screen then safestrap then 10 seconds later back to custom screen. After flashing kernels and modules I'm still able to get into recovery, nc1 should be gone in order for ss to work. I'm so sick of odin... :what:
Sent from my sghi337 on oc3
Click to expand...
Click to collapse
So you got all the way to step 4.3.6 successfully, it sounds like? And now you are just getting the Safestrap screen - where you can either "continue" or "recovery"? How many times did you hit "continue" and go through the "bootloop" (if any)?
After step 4.3.6, when you boot into your custom ROM, you will have the Safestrap screen pop up several times (like, at least four or five) - keep hitting "continue" and you will eventually get into the ROM. This is another symptom of Lollipop not being fully compatible with Safestrap.
I did not put that detail in the writeup. Very sorry it caused you issues. I am updating with that info now.

I must of not been patient enough, with so many failed rom installs with this locked bootloader i just odin'd back to nb1 to get to oc3... Any custom recovery would be such a relief as ss acts wonkey in lollipop, and flashfire isn't accessible if you're caught in a bootloop or the radical "att unauthorized software". Thanks for the help
Sent from my sghi337 on oc3

Update:
So once again I follow the instructions completely to the t
After I flash the ROM and the kernel and the modules and I reboot I get the Samsung custom screen then to safe strap then 20 seconds reboots to Samsung Galaxy s4 screen then safestrap then again to the Samsung Galaxy s4 screen with reboot to recovery again and this time it puts me into stock recovery no safestrap after rebooting system each time from recovery. It does the same thing and eventually i end up at the system recovery... I've tried this about 11 times, with no success to boot into the ROM
Sent from my sghi337 on oc3

robot_head said:
Update:
So once again I follow the instructions completely to the t
After I flash the ROM and the kernel and the modules and I reboot I get the Samsung custom screen then to safe strap then 20 seconds reboots to Samsung Galaxy s4 screen then safestrap then again to the Samsung Galaxy s4 screen with reboot to recovery again and this time it puts me into stock recovery no safestrap after rebooting system each time from recovery. It does the same thing and eventually i end up at the system recovery... I've tried this about 11 times, with no success to boot into the ROM
Sent from my sghi337 on oc3
Click to expand...
Click to collapse
Did you try wiping data/cache in the stock system recovery?

Yes wiped with system recovery and safestrap. This is an issue of flashing the oc3 kernels and modules with safestrap. I think.....
sent from my sghi337 on oc3

Read through your tutorial, very nice. ?The only thing I noticed is you flash the kernel before the modules. I think flashing the kernel should be the very last step before rebooting, I'm not sure it matters, but it might. Also when the phone is booting I never touch any buttons (continue or recovery) just let it work through the screens on it's own.

Thanks, Cats_PJs - I will edit the OP to indicate flashing the modules before the kernel. I didn't see such a recommendation to flash one or the other first in my research, and I honestly can't remember now which I flashed first. But I will update the OP to recommend flashing the kernel last, just in case.

If I'm safestrap'd and rooted on a custom 4.x.x ROM, should I flash to rootable NB1 per step 2.2 then start here with step 3? Thanks for compiling all this, I chuckled at the 18 pages open comment. I know that pain.

What version are you running now? If you already have root on a KitKat 4.4.x or higher ROM, you should be able to go straight to rooted Lollipop using the muniz_ri keep root method method here. (see the very first line of the linked reference post.) So if you meet that criteria, you could start in Step 3.
If you're on a lower build, you'll want to just start with step 2 and flash NB1 via Odin. I believe that you will need to uninstall your current version of safestrap at some point to be able to install the required v3.75.

So I have an update I finally found that sometimes safestrap won't flash the kernel so you have to Odin it even if its downgrading the kernel or upgrading. I've been able to flash any lollipop rom since I've been doing the Odin method for the kernels you still have to safestrap your ROM though. In another thread it said to flash the OC3 partition which I didn't find necessary and when I did try to flash them Odin kept failing therefore it wasn't required you must also flash the module with safestrap right after you do your rom unless you have your modules in a tar file then just do it via Odin. So to go over it one more time... you have to be able to use safestrap so if you were on lollipop you must downgrade your kernel (via odin or nc1 flasher) then you can use safestrap to flash your ROM and flash your oc3 modules then reboot into download mode and use Odin to flash your oc3 kernel(sometimes it will fail,just try again, i hold my phone gently to comfort it through the process) and it boots up going through the safestrap screen at least 4 to 5 times.
Confirmed to work. ..
Goldeneye
Imperium
Car hd
I'll be testing all the compatible lollipop roms for my device it's exciting I can finally flash roms thank you for this tutorial for heading me in the right direction.
:thumbup::thumbup:
Sent from my GT-I9505 using XDA Free mobile app

robot_head said:
So I have an update
I finally found that sometimes safestrap won't flash the kernel so you have to Odin it even if its downgrading the kernel or upgrading.
I've been able to flash any lollipop rom since I've been doing the Odin method for the kernels - you still have to safestrap your ROM though.
In another thread it said to flash the OC3 partition which I didn't find necessary and when I did try to flash them Odin kept failing therefore it wasn't required
You must also flash the module with safestrap right after you do your rom unless you have your modules in a tar file then just do it via Odin.
So to go over it one more time... you have to be able to use safestrap so if you were on lollipop you must:
downgrade your kernel (via odin or nc1 flasher)
then you can use safestrap to flash your ROM and flash your oc3 modules
then reboot into download mode and use Odin to flash your oc3 kernel (sometimes it will fail, just try again, i hold my phone gently to comfort it through the process)
and it boots up going through the safestrap screen at least 4 to 5 times.
Confirmed to work. ..
Goldeneye
Imperium
Car hd
I'll be testing all the compatible lollipop roms for my device it's exciting I can finally flash roms thank you for this tutorial for heading me in the right direction.
:thumbup::thumbup:
Click to expand...
Click to collapse
robot_head, glad to hear you got the custom ROMs working on your device! I will add a note in the OP regarding your experience so it helps others that might have the same issue.
Sorry, but stupid question - you did only try to install flashable ".zip" files from within safestrap, and ".tar" files using Odin? Your word choice in your above post seems to indicate that you do recognize the difference. But I ask that because I did not realize the difference at one point, until I tried to load a .zip into Odin and encountered issues. (and also I wanted to make this distinction for any others reading this thread)
Question for you – when you are swapping between custom ROMs, are you backing up your system settings and apps/data, then restoring them to each ROM (or are you just “sampling” each ROM for limited time and not worrying about your apps)? Based on advice I read in several places, I didn’t use Titanium Backup when I upgraded from 4.x.x to 5.0.1, but I figured I could use it to swap between ROMs now that I’m on Lollipop. But I just wanted to be sure I could easily move between ROMs without requiring so much time manually downloading apps like I did for the upgrade.

@sac02 yes I do have backups of all of my firmware and roms and yes I am just sampling through all of the roms and any apps that I need backed up are on my SD card and Google Play backs up the ones from them automatically. Yes when I'm flashing with safestrap obviously it has to be a zip file and Odin has to be a tar. And if you search the site there are downloads for your kernel in a tar format I actually got half of the help I needed from this thread and the other half from the Goldeneye thread when someone was having an issue with safestrap they had to Odin everything.
Sent from my GT-I9505 using XDA Free mobile app

The instructions are good. You may have a bad download of kernel file. Note that the instructions call for the "reflashable kernel zip file" which can also be found on the NC1 flasher thread.

My main problem is i couldnt flash kernels with safestrap after the rom. Tried a different download, same thing. Either said unauthorized att software
Or firmware update failed, use kies
Or bootloop into system recovery.
Finally. ..just odining kernels solved my issue.
Sent from my GT-I9505 using XDA Free mobile app

I have root on a base NJ4 4.4.4 ROM. I couldn't get the google play edition working on my i337 (dimming sensor worked poorly during calls) so I went to something basic. I'll try your recommendation, thanks again.

P5113 root, recovery, rom questions

Hello community,
I was given the device last year and had been fairly satisfied with the performance of it. However, it has gotten laggy over the past couple weeks and a friend suggested to root and flash a rom on it. So, without any prior knowledge, I have been doing some research and browsing through the threads on this forum. I can see that there are guides but was very unsure if the methods would still work because I have noticed that most of them were last updated/edit a while ago. I know I shouldn't use the word 'latest' for doing this to a tablet that is fairly old in the market. However, it would be very helpful if someone can point me to some 'proven to work' or 'trust-worthy' guides of rooting, flashing recovery, and rom.
Also, just out of curiosity, please recommend which recovery and rom a first-timer should use if possible

try these roms.
rocketfans14 said:
Hello community,
I was given the device last year and had been fairly satisfied with the performance of it. However, it has gotten laggy over the past couple weeks and a friend suggested to root and flash a rom on it. So, without any prior knowledge, I have been doing some research and browsing through the threads on this forum. I can see that there are guides but was very unsure if the methods would still work because I have noticed that most of them were last updated/edit a while ago. I know I shouldn't use the word 'latest' for doing this to a tablet that is fairly old in the market. However, it would be very helpful if someone can point me to some 'proven to work' or 'trust-worthy' guides of rooting, flashing recovery, and rom.
Also, just out of curiosity, please recommend which recovery and rom a first-timer should use if possible
Click to expand...
Click to collapse
hello ,
these are the things you need to do before flashing a ROM.
note: -the following things may void your warranty.
-do this on your own risk.
1. HOW TO ROOT
-First install kingo root on your windows PC. Then check USB debugging .
( settings. < about device < touch build number 7times < go back and select developer options < check USB debugging.)
-Open kingo root on the PC and connect your device and connect your device to the PC. Start root and do not remove the USB cable until it says finish.
-Now you have successfully rooted your device.
2.HOW TO INSTALL A CUSTOM RECOVERY
- Go to the following link and download CLOCK WORK MOD(CWM)
LINK: https://www.clockworkmod.com/rommanager
Select your device and install the recovery.
go into the app and install recovery .
3.BACK UP
download rom manager from playstore and do a backup( do a backup using this ap only if you are using CWM recovery.
link for ROM manager: https://play.google.com/store/apps/d...mmanager&hl=en
Now the first thing you need to do is download this rom.
https://www.androidfilehost.com/?fid=95916177934533333
(note: you can flash the rom of p5110 for p5113)
now to flash the rom follow the following steps.
1. Go to recovery mode
2. (have the rom in your sd card)flash it there .
use this link to know how to flash a rom.
https://www.youtube.com/watch?v=tJfPwWjnWGY
now you can reboot after flashing.
to get inbuilt google apps and play store you need to install something called GAPPS (Google apps) download from this link.
http://opengapps.org/?api=5.1&variant=nano
now you flash this zip the same way you flashed the rom.
any problems plz notoce me.

Zte blade l said:
hello ,
these are the things you need to do before flashing a ROM.
note: -the following things may void your warranty.
-do this on your own risk.
1. HOW TO ROOT
-First install kingo root on your windows PC. Then check USB debugging .
( settings. < about device < touch build number 7times < go back and select developer options < check USB debugging.)
-Open kingo root on the PC and connect your device and connect your device to the PC. Start root and do not remove the USB cable until it says finish.
-Now you have successfully rooted your device.
2.HOW TO INSTALL A CUSTOM RECOVERY
- Go to the following link and download CLOCK WORK MOD(CWM)
LINK: https://www.clockworkmod.com/rommanager
Select your device and install the recovery.
go into the app and install recovery .
3.BACK UP
download rom manager from playstore and do a backup( do a backup using this ap only if you are using CWM recovery.
link for ROM manager: https://play.google.com/store/apps/d...mmanager&hl=en
Now the first thing you need to do is download this rom.
https://www.androidfilehost.com/?fid=95916177934533333
(note: you can flash the rom of p5110 for p5113)
now to flash the rom follow the following steps.
1. Go to recovery mode
2. (have the rom in your sd card)flash it there .
use this link to know how to flash a rom.
https://www.youtube.com/watch?v=tJfPwWjnWGY
now you can reboot after flashing.
to get inbuilt google apps and play store you need to install something called GAPPS (Google apps) download from this link.
http://opengapps.org/?api=5.1&variant=nano
now you flash this zip the same way you flashed the rom.
any problems plz notoce me.
Click to expand...
Click to collapse
I was looking in the forum and someone said that I would also need to unlock the bootloader? If so, how do I do that?
Also, is there a difference between kingroot and towelroot? I saw a post in the forum here saying towelroot is fast and easy to root the tablet.

Not much difference.
Actually there is not much difference between kings root and towel root....towel root doesn't need a PC...but I have never used it so I can't assure you that it is safe.
And coming to the boot loader I don't know much about it but I didn't do anything like that before flashing a rom or rooting my tab2....
If you want further assistance about the boot loader I can help you with that..

rocketfans14 said:
I was looking in the forum and someone said that I would also need to unlock the bootloader? If so, how do I do that?
Also, is there a difference between kingroot and towelroot? I saw a post in the forum here saying towelroot is fast and easy to root the tablet.
Click to expand...
Click to collapse
it is not necessary to unloack bootloader for tab 2 as it comes with a unlocked bootloader from stock.

Zte blade l said:
Actually there is not much difference between kings root and towel root....towel root doesn't need a PC...but I have never used it so I can't assure you that it is safe.
And coming to the boot loader I don't know much about it but I didn't do anything like that before flashing a rom or rooting my tab2....
If you want further assistance about the boot loader I can help you with that..
Click to expand...
Click to collapse
Hey, it's been a while. Honestly speaking, when I first posted this thread, I didn't really have enough time to do the things so now I am finally back and trying to do it. So far, I know what recovery and rom I'm going to use with all the files downloaded and ready. Though, currently, I am still at the pre-root stage. I have read up things about kingoroot and not sure if I wanted to use it. So I looked around on the forum and wonder if Odin is still a working solution. Reading on the steps and guides, I was wondering if I need to have Kies installed?

rocketfans14 said:
Hey, it's been a while. Honestly speaking, when I first posted this thread, I didn't really have enough time to do the things so now I am finally back and trying to do it. So far, I know what recovery and rom I'm going to use with all the files downloaded and ready. Though, currently, I am still at the pre-root stage. I have read up things about kingoroot and not sure if I wanted to use it. So I looked around on the forum and wonder if Odin is still a working solution. Reading on the steps and guides, I was wondering if I need to have Kies installed?
Click to expand...
Click to collapse
Kies is not needed as it never helped.
You can depend on odin it is your only saviour when you are in trouble.
I think rooting with kingroot is easy as it is just connecting to your PC and cick the start button.
So just notice me when your ready.
And there is also one good news...?
Tab 2 has got marshmallow.

Zte blade l said:
Kies is not needed as it never helped.
You can depend on odin it is your only saviour when you are in trouble.
I think rooting with kingroot is easy as it is just connecting to your PC and cick the start button.
So just notice me when your ready.
And there is also one good news...��
Tab 2 has got marshmallow.
Click to expand...
Click to collapse
I have rooted the tablet. I did it with odin and twrp with flashing the updatedSuperSU zip folder.
I have tried flashing the CM12.1 rom yesterday but resulted in a boot loop. So for now, I'm just rooted and on stock rom until I or someone can find out what was the problem. I have read about the discussion with marshmallow but it seems to me that the project isn't really stable yet. From what I have researched lately, can I assume there's issue with the p51xx line of tablets? Because I saw many people having problems with p51xx and most people with the other tablets aren't having any.

rocketfans14 said:
I have rooted the tablet. I did it with odin and twrp with flashing the updatedSuperSU zip folder.
I have tried flashing the CM12.1 rom yesterday but resulted in a boot loop. So for now, I'm just rooted and on stock rom until I or someone can find out what was the problem. I have read about the discussion with marshmallow but it seems to me that the project isn't really stable yet. From what I have researched lately, can I assume there's issue with the p51xx line of tablets? Because I saw many people having problems with p51xx and most people with the other tablets aren't having any.
Click to expand...
Click to collapse
You first must update your tab to jelly bean bootloader, before trying out newer roms.
Or perhaps flash stock jb firmware with odin
Whatever you choose, both is ok.
http://forum.xda-developers.com/showthread.php?t=2642005
Read here
The first thing you do, is take a nandroid backup, it's very important at every step, unless you are really ready to risk. It's better to have it.
Next Read through the rom threads, clear your mind and your tab too. You must format data.
Stay on twrp 2.8.7.2. Don't go to the latest one yet.
Flash rom, wait, it will boot up.
Every tab behave differently with every rom, sure you are going to face soft reboots, on some roms it will be a lot, on some it will be less. I would suggest you try both LP and kk first.
Remember, it's better to keep this tab updated than to stay on stock. This tab 2 series has a emmc bug and staying on stock or jumping back is a risk too. I have been on kk and lp. They both have kept this tab running great and away from that bug.

billysam said:
You first must update your tab to jelly bean bootloader, before trying out newer roms.
Or perhaps flash stock jb firmware with odin
Whatever you choose, both is ok.
http://forum.xda-developers.com/showthread.php?t=2642005
Read here
The first thing you do, is take a nandroid backup, it's very important at every step, unless you are really ready to risk. It's better to have it.
Next Read through the rom threads, clear your mind and your tab too. You must format data.
Stay on twrp 2.8.7.2. Don't go to the latest one yet.
Flash rom, wait, it will boot up.
Every tab behave differently with every rom, sure you are going to face soft reboots, on some roms it will be a lot, on some it will be less. I would suggest you try both LP and kk first.
Remember, it's better to keep this tab updated than to stay on stock. This tab 2 series has a emmc bug and staying on stock or jumping back is a risk too. I have been on kk and lp. They both have kept this tab running great and away from that bug.
Click to expand...
Click to collapse
Do I have to unroot first? Do you have a link to making a nandroid backup?
Edit: Oh, I looked at the link you included and it said that if I am on stock jb (4.2.2), I can skip the update bootloader part..

When you flashed the new rom, did you do a factory reset (wipe data)?
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app

rocketfans14 said:
Do I have to unroot first? Do you have a link to making a nandroid backup?
Edit: Oh, I looked at the link you included and it said that if I am on stock jb (4.2.2), I can skip the update bootloader part..
Click to expand...
Click to collapse
Yes, that's what I meant too, if you're on jb already, you are fine. You don't have to unroot. For making a nandroid backup, use twrp recovery, there is an option for backup, select and backup all from there, if you get into bootloop or any other problem, as long as you can get back to recovery, you can restore from there. Most rom comes pre rooted.

rocketfans14 said:
I have rooted the tablet. I did it with odin and twrp with flashing the updatedSuperSU zip folder.
I have tried flashing the CM12.1 rom yesterday but resulted in a boot loop. So for now, I'm just rooted and on stock rom until I or someone can find out what was the problem. I have read about the discussion with marshmallow but it seems to me that the project isn't really stable yet. From what I have researched lately, can I assume there's issue with the p51xx line of tablets? Because I saw many people having problems with p51xx and most people with the other tablets aren't having any.
Click to expand...
Click to collapse
Did you clear dalvik cache in recovery before flashing rom?

Zte blade l said:
Did you clear dalvik cache in recovery before flashing rom?
Click to expand...
Click to collapse
Yes, I cleared the top four options in recovery, and formatted data before flashing.
billysam said:
Yes, that's what I meant too, if you're on jb already, you are fine. You don't have to unroot. For making a nandroid backup, use twrp recovery, there is an option for backup, select and backup all from there, if you get into bootloop or any other problem, as long as you can get back to recovery, you can restore from there. Most rom comes pre rooted.
Click to expand...
Click to collapse
That's what I did. Let me just briefly summarize what I have done:
used odin with twrp
booted into recovery and made back up
cleared dalvik, cache, system, and data, formatted data
flashed update supersu, booted into system and checked root with root checker
rebooted into recovery, cleared dalvik, cache, system, and data, formatted data again
flashed cm12.1 and gapps, rebooted but ran into bootloop at splash screen
rebooted into recovery and restored back up
So I'm rooted and on stock 4.2.2 currently.
champ1919 said:
When you flashed the new rom, did you do a factory reset (wipe data)?
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Click to expand...
Click to collapse
I did.

Try flashing blisspop or slimLP.

The [Almost] All in One Guide to the MDL Bootloader

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