So I see ALOT OF CONFUSION regarding Safestrap on the Verizon Galaxy S5, I think its about time to explain it to stop this nonsense
THIS IS MEANT FOR 11 eMMC Users, 15 eMMC Users should unlock their bootloader and use TWRP instead
What is safestrap?
Why thank-you for asking, Safestrap is essentially a second recovery written by member @Hashcode to be used for systems with locked bootloader. Safe strap IS NOT A REPLACEMENT FOR YOUR STOCK RECOVERY OR A CUSTOM RECOVERY. Safestrap on a locked bootloader cannot flash locked bootloaders, cannot flash TWRP, and cannot flash custom kernels,(well it can but it is gonna brick) all this requires a custom bootloader, in which you could flash those things but at that point, you'd be better using SafeStrap, Flashfire or Odin to flash TWRP first.
So then what can safestrap do? Well safestrap is capable of flashing system partitions, data, cache and taking backups and even restoring them. It also has a built in file manager to give you access to system allowing the deleting, moving, and changing of files
You could run some stock based ROMs with this and in some cases pre-rooted ROMs. If you are on MM and running a pre-rooted rom, you must flash the stock kernel everytime you leave. YOU WILL NOT HAVE ROOT, but it will allow booting.
How do I access or use safestrap
Well I'll tell you this much, you DO NOT use your hard keys to do such. Don't try any button combos it just won't work. Safestrap doesn't exist on your recovery partition, but instead it exisst on the system partition, meaning you have to use the kernel to load safestrap, not hardware recovery.
On Lollipop its very simple, you need root first which can be obtained here http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370 @jrkruse
In this thread it also includes instructions for installing safestrap
Once safestrap is installed, continue by opening lollipop safestrap and selecting reboot to recovery. To exit, you can simply reboot to system
Now the hardest part comes down to Marshmallow. @jrkruse has a thread here about it http://forum.xda-developers.com/ver...ow-to-flash-custom-6-0-1-roms-locked-t3393943
Unlike Lollipop you DO NOT HAVE ROOT. Sorry, just won't happen. But you can still flash some stuff. The worst part is "how do I get into safe strap?"
In the magical folder you downloaded and probably deleted when you rooted your galaxy S5, there was a Kernel file. NI2 or NK2. Either works, what you do is open up Odin on your PC and put your phone into download mode, when it boots into download mode, just flash it and it will reboot. When your phone starts up it will say "safe system not installed" or something. Press recovery. If you wait too long it'll freeze and need a battery pull. Now your in safe strap. to exit just reboot to system(possibly need to flash stock kernel via Odin for MM as safe strap flashes stock LP kernel. Again if you followed the directions in @jrkruse thread then it will manage to boot without any hassle
So why bother?
That! Is an excellent question.
For lollipop users you can flash prerooted stock based ROMs and such. You can use debloat scripts, Knox removal scripts, even modify system files and build.prop and boot and shutdown animations, change boot sounds, install xposed, use rooted apps, go crazy!!! And you can take system backups and restores. Its just awesome!
However, those on Marshmallow have a more sinister fate. Verizon doesn't like us so you CANNOT ROOT. Which means NO YOU CANNOT USE FLASHFIRE TO BOOT INTO SAFESTRAP, NOR SAESTRAP REBOOT OR SUCH. They all require root. So what can you do? Your in luck, you can flash debloat scripts to debloat some ROMs, Knox removal, take backups and do restores, you can still modify build.prop(I don't recommend it, take a backup), and even use Safestrap built-in file manager to edit the system partition, just remember, don't do anything without a backup. Also YES you can DOWNGRADE back to Lollipop if you read @jrkruse thread. You can flash custom ish stock based ROMs but you still CANNOT GET ROOT. DO NOT TRY TO FLASH A ROOTED ROM WITHOUT FLASHING A STOCK KERNEL BEFORE REBOOT.
Thanks to changes made by google you no longer can root MM+ without a custom kernel and you cannot get custom kernels without custom recovery which needs unlocked bootloaders. So sorry to those who want it but nothing we can do right now
So that's the majority of how to safestrap. Any comments or questions leave them below and I probably will answer them maybe kinda probably not.
GeTex said:
So that's the majority of how to safestrap.
Click to expand...
Click to collapse
How to safestrap? Do you even safestrap?
Nandr0idC0nsumer said:
How to safestrap? Do you even safestrap?
Click to expand...
Click to collapse
Instructions unclear, ended up with unlocked bootloader and TWRP
GeTex said:
Instructions unclear, ended up with unlocked bootloader and TWRP
Click to expand...
Click to collapse
Instructions unclear, ended up with my eMMC chip reaching terminal velocity on its ride to space
GeTex said:
So I see ALOT OF CONFUSION regarding Safestrap on the Verizon Galaxy S5, I think its about time to explain it to stop this nonsense
What is safestrap?
Why thankyou for asking, Safestrap is essentially a second recovery written by member @Hashcode to be used for systems with locked bootloader. Safe strap IS NOT A REPLACEMENT FOR YOUR STOCK RECOVERY OR A CUSTOM RECOVERY. Safestrap cannot flash locked bootloaders, cannot flash TWRP, and cannot flash custom kernels, all this requires a custom bootloader.
So then what can safestrap do? Well safestrap is capable of flashing system partitions, data, cache and taking backups and even restoring them. It also has a built in file manager to give you access to system allowing the deleting, moving, and changing of files
You could run some stock based ROMs with this and in some cases pre-rooted ROMs. If you are on MM YOU CANNOT NOT USE SAFESTRAP WITH A PRE ROOTED ROM. YOU WILL BRICK!!!
How do I access or use safestrap
Well I'll tell you this much, you DO NOT use your hard keys to do such. Don't try any button combos it just won't work
On Lollipop its very simple, you need root first which can be obtained here http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370 @jrkruse
In this thread it also includes instructions for installing safestrap
Once safestrap is installed, continue by opening lollipop safestrap and selecting reboot to recovery. To exit, you can simply reboot to system
Now the hardest part comes down to Marshmallow. @jrkruse has a thread here about it http://forum.xda-developers.com/ver...ow-to-flash-custom-6-0-1-roms-locked-t3393943
Unlike Lollipop you DO NOT HAVE ROOT. Sorry, just won't happen. But you can still flash some stuff. The worst part is "how do I get into safe strap?"
In the magical folder you downloaded and probably deleted when you rooted your galaxy S5, there was a Kernel file. NI2 or NK2. Either works, what you do is open up Odin on your PC and put your phone into download mode, when it boots into download mode, just flash it and it will reboot. When your phone starts up it will say "safe system not installed" or something. Press recovery. If you wait too long it'll freeze and need a battery pull. Now your in safe strap. Again if you followed the directions in @jrkruse thread then it will manage to boot without any hassle
So why bother?
That! Is an excellent question.
For lollipop users you can flash prerooted stock based ROMs and such. You can use debloat scripts, Knox removal scripts, even modify system files and build.prop and boot and shutdown animations, change boot sounds, install xposed, use rooted apps, go crazy!!! And you can take system backups and restores. Its just awesome!
However, those on Marshmallow have a more sinister fate. Verizon doesn't like us so you CANNOT ROOT. Which means NO YOU CANNOT USE FLASHFIRE TO BOOT INTO SAFESTRAP, NOR SAESTRAP REBOOT OR SUCH. They all require root. So what can you do? Your in luck, you can flash debloat scripts to debloat some ROMs, Knox removal, take backups and do restores, you can still modify build.prop(I don't recommend it, take a backup), and even use Safestrap built-in file manager to edit the system partition, just remember, don't do anything without a backup. Also YES you can DOWNGRADE back to Lollipop if you read @jrkruse thread. You can flash custom ish stock based ROMs but you still CANNOT GET ROOT. DO NOT TRY TO FLASH A ROOTED ROM UNLESS YOU WANT A BOOTLOOP.
Thanks to changes made by google you no longer can root MM+ without a custom kernel and you cannot get custom kernels without custom recovery which needs unlocked bootloaders. So sorry to those who want it but nothing we can do right now
So that's the majority of how to safestrap. Any comments or questions leave them ebloe and I probably will answer them maybe kinda probably not.
NOTE mods may move this thread as seen fit
NOTE2 anyone may correct, suggest content, or give me pointers, I wrote this while sick laying here in the doctors office
NOTE3 Notes will be deleted after a few days
Click to expand...
Click to collapse
Safestrap cannot flash locked bootloaders, cannot flash TWRP, and cannot flash custom kernels, all this requires a custom bootloader. Safestrap can flash bootloader and custom kernels and TWRP This is why you should not try to do so it has safety feature built in where normal script will not flash them but it can be made to like I did with the Bootloader update and downgrade zips
DO NOT TRY TO FLASH A ROOTED ROM UNLESS YOU WANT A BOOTLOOP. As long as you flash the stock kernel back after you flash the rom systemless root will be broken and you will not bootloop. So you can flash MM roms that have systemless root just always make sure to flash stock kernel when finished if you dont you wont even have time to bootloop you will be taken to that unauthorize software is detected on your device screen
jrkruse said:
Safestrap cannot flash locked bootloaders, cannot flash TWRP, and cannot flash custom kernels, all this requires a custom bootloader. Safestrap can flash bootloader and custom kernels and TWRP This is why you should not try to do so it has safety feature built in where normal script will not flash them but it can be made to like I did with the Bootloader update and downgrade zips
DO NOT TRY TO FLASH A ROOTED ROM UNLESS YOU WANT A BOOTLOOP. As long as you flash the stock kernel back after you flash the rom systemless root will be broken and you will not bootloop. So you can flash MM roms that have systemless root just always make sure to flash stock kernel when finished if you dont you wont even have time to bootloop you will be taken to that unauthorize software is detected on your device screen
Click to expand...
Click to collapse
I meant to say it cannot flash those on locked bootloaders
Can you reword what I should replace those with and I'll update the OP
Do you think this thread is even helpful?
GeTex said:
I meant to say it cannot flash those on locked bootloaders
Can you reword what I should replace those with and I'll update the OP
Do you think this thread is even helpful?
Click to expand...
Click to collapse
Well it can flash those on locked bootloaders but you wont like the outcome!
I need you to write my stuff your so much better at explaing stuff than me. I just had a rant on your bootloader unlock page. Nothing meant towards you!
Haha alright, just trying to not mess things up in translation, gonna attempt to reboot your root page now that MM is here and I think we can overhaul it completely, along with a few minor changes to the batch files to streamline everything. Your Rant is justified, I honestly wanted to myself but I've been holding back
My experience
Okay! I ABSOLUTELY had to add to this thread because it was so helpful and confusing at the same time. I wanted to put in some points that seriously helped me. It took me about 8.5 hours total to get this done and I think this can help save people a lot of time.
Phone, I bought an unlocked verizon samsung galaxy s5 off the web (used). 5.0 lollipop with OK base from what I could tell. I was a ten year iphone user so this was all new to me. But I've run a web company for years so I'm very familiar getting around networks and software.
The first recommendation I would have is to read, then re-read, then re-read, then re-read the initial instruction page. The original writer didn't make it Step 1, Step 2, but put multiple steps inside a sentence so you have to sometimes figure out what he's trying to say.
The first problem I ran into was flashing the NK kernel. This is confusing because the Samsung logo will freeze and no where did it say how long to wait, just be patient. This cost me HOURS. There are two things happening, the root.bat file is giving you information and then the phone is responding. I would get all the ##### notifications and then a cursor sitting at the bottom with no response. Samsung logo would freeze. To get it to work I had to install the Factory Tar BPB1 Full Restore Image.
G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip by unzipping and then using the Odin app to install. Once I did that the root.bat file would flash the kernel, I'd wait about 3-4 mins at the blinking cursor after the ### notices, then it said Root Installed and then I was off to the races. I would HIGHLY recommend doing this as from that point forward everything was soooo much smoother. I had about a dozen failures further down the process over about 4 hours because i never saw that Root Installed message at this stage. Once I did, everything was smooth.
I also did not opt out of buying Super Sume. I bought it and then removed kingroot with it and all the other steps were flawless.
For a new droid user one thing you may want to also need to know is that to move files over to the android download HandShaker, it's a much easier file transfer app to move those zip files in later stages over to the phone.
SO - If I am on Lollipop, I can load a custom ROM with Safestrap that is pre-rooted. Right? Would that allow me to load a ROM based on CM 14? What would or would not work. I have had a lot of prior experience with rooting and custom recovery, etc with my Razer M and an Xperia Play and the old LG Ally, but nothing with this S5 and no experience with Safestrap (that I can recall). Cut me a little slack - I'm 59 years old and a tech, but no experience with Samsung except ODIN a couple of times. Thanks.
netizenmt said:
SO - If I am on Lollipop, I can load a custom ROM with Safestrap that is pre-rooted. Right? Would that allow me to load a ROM based on CM 14? What would or would not work. I have had a lot of prior experience with rooting and custom recovery, etc with my Razer M and an Xperia Play and the old LG Ally, but nothing with this S5 and no experience with Safestrap (that I can recall). Cut me a little slack - I'm 59 years old and a tech, but no experience with Samsung except ODIN a couple of times. Thanks.
Click to expand...
Click to collapse
Only with an unlocked bootloader
Okay so I come from dos and Lynx area late 90s going to college and back then it was fun to sit down and code stuff and drink beer on the weekend can I just delete the hole OS out of my g900V cid 11 make my own somehow. It's been 23 yrs but sudo apt update still probably over rides a regular program saying no oh a and I barely got my first smartphone three or four months ago when I would consider smart I don't think the Samsung whatever it was was smart and just could text
averydiablo said:
Okay so I come from dos and Lynx area late 90s going to college and back then it was fun to sit down and code stuff and drink beer on the weekend can I just delete the hole OS out of my g900V cid 11 make my own somehow. It's been 23 yrs but sudo apt update still probably over rides a regular program saying no oh a and I barely got my first smartphone three or four months ago when I would consider smart I don't think the Samsung whatever it was was smart and just could text
Click to expand...
Click to collapse
No idea what you are trying to ask
CID 11 cannot run a custom OS.
Making your own OS is not anywhere near easy either
Inglis Second language is possible on rooted phone like LG spectrum 2 or g900v to get rid android just have kali or unbunt do you need bootloader unlock
averydiablo said:
Inglis Second language is possible on rooted phone like LG spectrum 2 or g900v to get rid android just have kali or unbunt do you need bootloader unlock
Click to expand...
Click to collapse
again, you cannot run anything but touchwiz based roms on a locked bootloader. you cannot use a custom kernel.
Thank you very much so now I went and traded for lg g2 and still have the vs93o old as dirt And the pixel 2 xl I don't want to mess with the other old ones I can root do they make os for lynux or Kali sorry I do understand I have hard time wording questions
GeTex said:
again, you cannot run anything but touchwiz based roms on a locked bootloader. you cannot use a custom kernel.
Click to expand...
Click to collapse
For now
ryanbg said:
For now
Click to expand...
Click to collapse
Indeed
Looking for a bit of help. I have a S5 with Emmc = 11. Know I cannot install TWRP. Have gone with all the steps from jrkruse here: http://https://forum.xda-developers.com/verizon-galaxy-s5/general/testers-required-easier-root-method-t3561529 I have no trouble getting into safestrap after rooting. The issue I have is once I flash a stock lollipop rom (either EMMC_11_PB1_LL_STOCK_SAFESTRAP_ONLY.zip or VZW_BPB1_ODEX_DEODEX_V9.zip), I can no longer access safestrap. I still have root (Super SU Pro) and busybox etc. However I can install, uninstall & re-install safestrap and when I click re-boot to recovery, it just reboots the system. I cannot figure out what the heck I am doing wrong. Is there a way to force a safestrap install that works? Or how am I destroying the SafeStrap that's part of the rom? Any suggestions would be greatly appreciated!
Thanks
John
Never mind. Installed LL_MM_SafeStrap.apk and that resolved the issue. Now have safestrap.
Thanks anyway!
Related
A while back, I always rooted and unrooted my Nexus S with no problems at all. Now whenever I try to root it, it just goes wrong. I've tried TWRP & CWM, CWM used to always work but now it just messes up. Both TWRP and CWM both give me an error that say Installation Aborted when I try to install a custom rom. I've redownloaded the rom from different browsers and even different PCs but nothing working, still that same error. Does anyone have a guide that is 100% to work without any errors during the process?
What guide are you using?
paul96 said:
What guide are you using?
Click to expand...
Click to collapse
I used this one: http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
1. Make sure you're running one the more recent versions of the custom recovery. You probably are but there are issues with older versions so just make sure.
2. Boot into what ever recovery you pick and do a full wipe. That is everything gets wiped but your SD card. Factory reset. Format /system etc.
3. Flash your ROM and gapps if they are seperate.
You should not get any errors. If your recovery is current and your flashing a new rom onto a fully wiped system and you still get a error either you're screwing something up or you may have a hardware problem.
To rule out a hw problem flash the factory images with fastboot. If those flash normally and everything works it is almost certainly user error.
albundy2010 said:
1. Make sure you're running one the more recent versions of the custom recovery. You probably are but there are issues with older versions so just make sure.
2. Boot into what ever recovery you pick and do a full wipe. That is everything gets wiped but your SD card. Factory reset. Format /system etc.
3. Flash your ROM and gapps if they are seperate.
You should not get any errors. If your recovery is current and your flashing a new rom onto a fully wiped system and you still get a error either you're screwing something up or you may have a hardware problem.
To rule out a hw problem flash the factory images with fastboot. If those flash normally and everything works it is almost certainly user error.
Click to expand...
Click to collapse
Alright, thanks Do you recommend that I root my Nexus S or should I wait for the Jelly Bean update? I've rooted before and I enjoyed it but now I don't see that many reasons to root, do you have any good reasons?
I have many. My reasons for root don't matter. If you don't have a reason for root then don't root. Its that simple really.
Make sure you're on a stock 4.0.4 rom. When the ota is out install it.
If you want just root on either os at any time just flash su.zip from custom recovery. Its that simple. Having root on a stock rom does not affect the ota process.
albundy2010 said:
I have many. My reasons for root don't matter. If you don't have a reason for root then don't root. Its that simple really.
Make sure you're on a stock 4.0.4 rom. When the ota is out install it.
If you want just root on either os at any time just flash su.zip from custom recovery. Its that simple. Having root on a stock rom does not affect the ota process.
Click to expand...
Click to collapse
What are your reasons for root? Please share?
Getting rid of stuff I don't want in a ROM.
Apps that do things that require root.Titanium backup/autoruns adaway ( ad blocker app alone could be its one point) etc
Changing kernel settings. Bid/bin clocks volts etc.
Being able to have a replacement launcher use the ICS style widget drawer.
Lastly , I simply just can't see having a computer that I don't have root/admin rights to. Its my damn device and I do what I want.
albundy2010 said:
Getting rid of stuff I don't want in a ROM.
Apps that do things that require root.Titanium backup/autoruns adaway ( ad blocker app alone could be its one point) etc
Changing kernel settings. Bid/bin clocks volts etc.
Being able to have a replacement launcher use the ICS style widget drawer.
Lastly , I simply just can't see having a computer that I don't have root/admin rights to. Its my damn device and I do what I want.
Click to expand...
Click to collapse
Oh cool. There is this project that some members from XDA are working on called Sense4All and they are porting Sense to many devices. Im probably going to wait until a fully functionable release is available for the Nexus S. I do like AOKP a lot, so that might be a reason for why I'll root.
You seem to be a little confused with some terms. Root is simply being able to grant superuser permission.
You don't need to root to flash a custom rom on a nexus. Just a unblocked bootloader. You could run aokp or any other rom without root if you wanted to.
albundy2010 said:
You seem to be a little confused with some terms. Root is simply being able to grant superuser permission.
You don't need to root to flash a custom rom on a nexus. Just a unblocked bootloader. You could run aokp or any other rom without root if you wanted to.
Click to expand...
Click to collapse
Oh, I never knew that, haha. Is it possible to flash a custom kernel with an unlocked bootloader or does that require root access?
m1l4droid said:
No you just need a custom recovery. But using that kernel's mods, like BLN, OC, UV, touchwake, etc, requires apps that need root, like NSTools, SetCPU, etc.
Click to expand...
Click to collapse
Oh alright. Now I really wanna root + install a custom rom. Do any of you have a full 100% fully working guide for rooting Nexus S and which rom should I flash first? I already know what kernel I want.
http://forums.acsyndicate.net/showthread.php?2024-ACS-Nexus-S-One-Click-Root-V4-0
leap_ahead said:
http://forums.acsyndicate.net/showthread.php?2024-ACS-Nexus-S-One-Click-Root-V4-0
Click to expand...
Click to collapse
Thank you so much! I rooted my phone with CWM recovery installed and Paranoid Android + gapps installed
I currently have S-Off and have it rooted through Weaksauce and SuperSu I believe. I have flashed ROMs through TWRP but did not like them, so I recovered back into my 4.4.2 stock. If I update to 4.4.4 by Verizon's OTA, will I lose my root and S-Off?
kinda a noob but...
steezy123 said:
I currently have S-Off and have it rooted through Weaksauce and SuperSu I believe. I have flashed ROMs through TWRP but did not like them, so I recovered back into my 4.4.2 stock. If I update to 4.4.4 by Verizon's OTA, will I lose my root and S-Off?
Click to expand...
Click to collapse
I'm not a hundred percent but I think the only way you lose it is if it upgrades the boot.img search for tigers posts because from the way it sounded to me if you flashed back to stock you'd have all ready lost your s-off.... Unless you've flashed one of the stock with the boot.img and recovery img removed. If so I'm pretty sure your good for the firmware upgrade if it'll ota without stock (or forged) boot.img file... Anyway man I'm slightly baked and never been accused of being smart enough to remember **** I read two weeks ago so search "tigerstown" posts and threads and read man and when you understand all a bit better than me then come message me and we'll discuss it a bit so it'll stick to my head a lil longer than last time man. Hope my rambleing might have shed some light on the subject or at least pointed you to the posts that know lol goodluck
The only way to "lose" s-off is to issue the fastboot command to set that flag which many smart people would never advise you do anyway. Nothing we are talking about here will do that automatically.
If you're s-off and on a custom Rom of any sort, I would recommend updating the firmware through tigerstown's method the previous poster referred to. If you're going to the trouble to flash everything necessary to take the ota, you may as well just flash his file and be done.
If you prefer stock, I would recommend you flash a stock-based Rom like CleanRom or NuSense. They come pre-rooted with some bloat removed and just a few tweaks added like write-protection removed, init-d support, etc.
If you really insist on running pure stock with root then you should at least root properly by uninstalling weak sauce and flashing the su binaries in recovery.
cntryby429 said:
The only way to "lose" s-off is to issue the fastboot command to set that flag which many smart people would never advise you do anyway. Nothing we are talking about here will do that automatically.
If you're s-off and on a custom Rom of any sort, I would recommend updating the firmware through tigerstown's method the previous poster referred to. If you're going to the trouble to flash everything necessary to take the ota, you may as well just flash his file and be done.
If you prefer stock, I would recommend you flash a stock-based Rom like CleanRom or NuSense. They come pre-rooted with some bloat removed and just a few tweaks added like write-protection removed, init-d support, etc.
If you really insist on running pure stock with root then you should at least root properly by uninstalling weak sauce and flashing the su binaries in recovery.
Click to expand...
Click to collapse
Thanks for all help, I'll start readin up. Just one question: let's say I update my firmware to 4.4.4 from Verizon's OTA, will I be able to flash this clean rom via TWRP? http://forum.xda-developers.com/showthread.php?t=2732877
The only reason I ask is because it says the user must be running 4.4.4 firmware to flash the rom and the only way I know how to get 4.4.4 is from Verizon's OTA
You can get everything you need from Verizon's 4.4.4 release by flashing the no boot no recovery file from the tigerstown thread mentioned earlier. It's the first file listed in his op. The rest of the ota contains the recovery (which you don't want since you need your custom recovery to flash custom ROMs) and the boot.img/kernel (which you don't need since every room comes with a kernel). It's not wrong till go back to stock to take an ota, it's just unnecessarily difficult when people like tigerstown make it so easy for us to accomplish the same thing.
This is going on my Mom's phone. It currently has 4.1 stock with root. Looking to upgrade the ROM to something newer that won't require any support from me. I believe the boot loader is unlocked.
Anyone? I am not sure which firmware version I can upgrade to, without it updating the boot loader and locking it again.
Jedis said:
Anyone? I am not sure which firmware version I can upgrade to, without it updating the boot loader and locking it again.
Click to expand...
Click to collapse
Are you sure your bootloader is unlocked? Just rooting the phone doesn't unlock the bootloader. I wrote the short guide below before I realized your bootloader may not be unlocked, so if it isn't, do that first. It's been quite a while since I unlocked mine so I'm not sure what the latest tools are to do that. The text below assumes your bootloader is unlocked.
The first thing you'll need to do is install the newest TWRP recovery to your phone. The easiest way to do that is with TWRP Manager on the Play store. Then you'll need to update your phone's firmware to version VRBMF1, you can download that ZIP file here: http://www.invisiblek.org/firmware/d2/. Save that ZIP file to your phone's SD card. You'll also need to save the ZIP file for your new ROM to the SD card, if you want something that will run trouble-free, I've been using CleanROM 8.2 for nearly a year now and it's been stable. It's basically the stock Verizon firmware for Android 4.3 with all the Verizon bloatware stripped out. You can grab that here. Copy the ZIP to your SD card.
Before you update, it would probably be a good idea to make a Nandroid backup, you can do that in TWRP as well. To access recovery mode if you're running stock 4.1, the easiest way is manually: turn the phone off, then start it up by holding down the Home and Volume Up keys, then holding the Power key. It should boot into TWRP. Make your backup first, then install the new firmware: tap "Install" and then navigate to the VRBMF1 ZIP file. Then do the same with the CleanROM ZIP.
Thanks for the instructions. I greatly appreciate it!
Yes, I remember unlocking the boot loader. Was it Samsung that used to do it several years ago? I distinctly remember getting an unlock file and flashing that.
I will try Clean ROM! I don't remember the ROM the phone is running now, but I believe it is just a Samsung stock ROM that came pre-rooted.
Thanks again!
Jedis said:
Thanks for the instructions. I greatly appreciate it!
Yes, I remember unlocking the boot loader. Was it Samsung that used to do it several years ago? I distinctly remember getting an unlock file and flashing that.
I will try Clean ROM! I don't remember the ROM the phone is running now, but I believe it is just a Samsung stock ROM that came pre-rooted.
Thanks again!
Click to expand...
Click to collapse
I'm nearly sure Samsung never provided unlock codes. It was Samsungs mistake that Odin got leaked and we are able to unlock the bootloaders and flash custom recoveries and roms. I know HTC does it but I'm nearly sure Samsung doesn't and didn't
Sent from my N5
It must have been Odin then that I used. I am probably remembering my HTC Evo 4G...
Jedis said:
This is going on my Mom's phone. It currently has 4.1 stock with root. Looking to upgrade the ROM to something newer that won't require any support from me. I believe the boot loader is unlocked.
Click to expand...
Click to collapse
I highly recommend liquidsmooth android 5.1.1 lollipop build or cm 11
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.
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