Database Info

[GUIDE]Updating to 4.22.651.2 OTA WITHOUT flashing a new ROM or wiping your Phone

This assumes you:
- Have the latest FROYO OTA installed 3.70.651.1
- Have some experience working with flashing things in recovery
- Have NOT deleted/uninstalled ANYTHING in /system
- Have defrosted any bloat you froze with Bloat Freezer or Ti Backup Pro
- Have S-OFF (Used Unrevoked Forever or a version of Unrevoked3 that includes Forever)
OK now let us get to it.
1. Go ahead and download the OTA like normal on your phone, but DO NOT install it.
2. Using a file manager copy the OTA zip file from /cache to /sdcard
3. Using Rom Manager, flash Amon RA Recovery 2.3 (Down at the bottom)
4. In Rom Manager, click the Reboot into Recovery button.
5. Select apply zip from SD Card and flash the OTA zip file that you put in /sdcard
--10 Minutes later.....you now have the UNROOTED OTA installed just as if you installed it normally--
6. Download the 2.6.0.1 ClockWorkMod Recovery zip from here and place it in the root of your SD card
7. Under settings > applications > disable FastBoot (re-enable this when you are done with the whole process)
8. Power off and reboot holding Volume down. The bootloader will scan and then will and ask you to press Volume up to install. Reboot.
9. Delete the PC36IMG.zip file from your SD card and place the attachment below in the root of the SD card.
10. Power off and reboot holding Volume down and then select recovery to start CWM recovery.
11. Choose apply zip from sd card. Choose select zip on sd card. You will see the SU file on the list, flash it to root your phone. Reboot.
You should now be rooted and can upgrade the recovery now to whatever style and version you want!
Enjoy! Please click the THANKS button if it worked for you!
----------------------------------------
Developer of Bloat Freezer - Freeze Your Pre Installed System Apps in One Click
Bloat Freezer - Android Market Link

Very cool!!

Great info ..hey if I follow these steps and skip the last part will my phone be stock / uprooted and good to go.for a trade in or repair? I've been trying to figure out the best way to unrest when.e3d comes out

I never updated to 3.70. I'm assuming I can do that the same way, root again, download the gingerbread, and root again?
I'm thinking it might just be easier to flash the rooted ROM and radios, but I'm not sure what's best.

if you have amon ra recovery (and a stock rom), you can simply download and click install.
I clicked install, amonra booted up, detected and ran update, click reboot, then the stock recovery will be active and updates the radios, once back in to sense, you can reinstall amonra or clockwork, then SU
worked for me.
http://forum.xda-developers.com/showthread.php?t=1109230

im curious why the title says "WITHOUT flashing a new ROM" yet you are clearly flashing the rom in amon ra. sorry just got to nit pick

what happens if you have deleted some system apps. Such as nova and blockbuster. I saved the APKS on the SD card however but I did delete them?

JMQUINT00 said:
what happens if you have deleted some system apps. Such as nova and blockbuster. I saved the APKS on the SD card however but I did delete them?
Click to expand...
Click to collapse
Well I wouldn't want to try it unless your prepared to do a full ruu reset if it fails.
the OTA is like a patcher, it deletes unneeded files, adds new files, and updates existing files... if its not completely stock it may (or may not) cause an error which the updater can't handle, and then you may be left with a half upgraded system.
if you nandroid *before* downloading the ota, you should always be able to go back, assuming you have perm soff from unrevoked forever.

it should run whether you have removed files or not. if it tries to delete a file that does not exist the script will just skip it. op i think you have bit of confusion going on though. you were only able to reattain root because you are s-off from unrevoked forever. if you are not s-off and do your method, which is no different then just excepting the ota and letting it do its thing btw, you will loose root until this new ota is cracked. just fwi, there was no "magic" from you flashing manually, the same script is ran and the same files are moved and patches are made regardless.

cant I reinstall the apps and put the apks in their original system folder?

DomSim said:
it should run whether you have removed files or not. if it tries to delete a file that does not exist the script will just skip it. op i think you have bit of confusion going on though. you were only able to reattain root because you are s-off from unrevoked forever. if you are not s-off and do your method, which is no different then just excepting the ota and letting it do its thing btw, you will loose root until this new ota is cracked. just fwi, there was no "magic" from you flashing manually, the same script is ran and the same files are moved and patches are made regardless.
Click to expand...
Click to collapse
Lol OK so which one is it? Can n just accept the ota and run? I'm rooted on stock rom, but I deleted nova and blockbuster from the system? I know I will loose root which I got by using unrevoked 3, but I just want to know if I can do it without bricking the phone. Ty

JMQUINT00 said:
Lol OK so which one is it? Can n just accept the ota and run? I'm rooted on stock rom, but I deleted nova and blockbuster from the system? I know I will loose root which I got by using unrevoked 3, but I just want to know if I can do it without bricking the phone. Ty
Click to expand...
Click to collapse
shouldn't be any worry about bricking but make 100% sure you are s-off from unrevoked forever and you should be able to re-root pretty much how the op outlined.

im currently running cm7. if i go back to a rooted stock froyo rom, will this work???

confused. I just don't understand why you wouldn't download the rooted version of the ROM from here on XDA and just flash it like a normal rom. Maybe I'm overtired and missing the point.
To me, its like this. If you're rooted, and want an OTA update, just wait for the devs at XDA to go through it and root it, and make it available for download. Then just download it and flash it. You get the same exact update that way, as if you took the OTA from sprint. Except this way you don't risk losing root, and your good to go.
If you're not rooted and your phone is stock, accept OTA like normal.
I don't understand why all this extra stuff needs to be done, and add more to the confusion. If your rooted, updating to the latest is simple. Download it and flash it in recovery.

DaEXfactoR said:
im currently running cm7. if i go back to a rooted stock froyo rom, will this work???
Click to expand...
Click to collapse
Just download the update from here http://forum.xda-developers.com/showthread.php?t=1038701
Do a full wipe and flash like any other rom you've ever flashed before. You'll then be on the latest and greatest . (you'll probably be going right back to CM)
EDIT: and to the OP, sorry that I don't agree with you. I just find it more confusing that way, and I guess that whatever the point of doing it that way is, is sailing miles above my head.

k2buckley said:
confused. I just don't understand why you wouldn't download the rooted version of the ROM from here on XDA and just flash it like a normal rom. Maybe I'm overtired and missing the point.
To me, its like this. If you're rooted, and want an OTA update, just wait for the devs at XDA to go through it and root it, and make it available for download. Then just download it and flash it. You get the same exact update that way, as if you took the OTA from sprint. Except this way you don't risk losing root, and your good to go.
If you're not rooted and your phone is stock, accept OTA like normal.
I don't understand why all this extra stuff needs to be done, and add more to the confusion. If your rooted, updating to the latest is simple. Download it and flash it in recovery.
Click to expand...
Click to collapse
I see your point. I guess I am anxious. So there will be a stock ROM that is rooted, thats what I was wondering. I wasnt sure if every ROM would be customized somewhat...Thanks

DaEXfactoR said:
I see your point. I guess I am anxious. So there will be a stock ROM that is rooted, thats what I was wondering. I wasnt sure if every ROM would be customized somewhat...Thanks
Click to expand...
Click to collapse
That link I supplied a couple posts up is a completely 100% stock and rooted version of the OTA update.
This is from the first paragraph of the first post of that thread.
"Stock 4.22.651.2 ROM, rooted and ready for your flashing pleasures. This is a completely stock ROM that has had nothing done to it outside of rooting & deodexing, it's not even zip aligned yet (sorry DrMacinyasha)
As always make sure your wipe your dalvik and create a nandroid before flashing."

k2buckley said:
That link I supplied a couple posts up is a completely 100% stock and rooted version of the OTA update.
This is from the first paragraph of the first post of that thread.
"Stock 4.22.651.2 ROM, rooted and ready for your flashing pleasures. This is a completely stock ROM that has had nothing done to it outside of rooting & deodexing, it's not even zip aligned yet (sorry DrMacinyasha)
As always make sure your wipe your dalvik and create a nandroid before flashing."
Click to expand...
Click to collapse
thanks for your insight. only thing I am confused on at this point is why there are kernels listed to flash from May just below it? wouldnt the htc stock kernel from the ota be in this rom already? seems like alot of folks are looking for newer kernels to flash after flashing xhaus rom. Any insight would be great. thanks again!

rileyd5 said:
thanks for your insight. only thing I am confused on at this point is why there are kernels listed to flash from May just below it? wouldnt the htc stock kernel from the ota be in this rom already? seems like alot of folks are looking for newer kernels to flash after flashing xhaus rom. Any insight would be great. thanks again!
Click to expand...
Click to collapse
I was a little curious about why those kernels were linked there too. I honestly haven't really kept up with thread, because I don't have an interest in flashing the update to begin with. I noticed those kernels are from May 4th, so it doesn't seem like they'd be the most current one. Without reading that thread, I first would've presumed that the kernel that comes with the rom would be the one to use. So, you've read through the thread and you're seeing that people are having trouble with the kernel that the rom comes with?? I'll take a gander over in the thread in a few minutes and see what I make out of it.

Well I f'd up and installed the latest update straight from sprint, instead of waiting for the rooted version to come out. I guess I thought I would find something exciting, but now I would realize it was kind of worthless and want to go back to a different rom like miui or vaelpak. I am s-off with unrevoked. Is there some combination of the steps listed I can use to back out of this?
Let me take a guess...did this update my radios and hboot to a version that would be incompatible with these roms?

Update Rooted Nexus

I am new to this. I have a rooted nexus 5. It is stock rooted with TRWP recovery. I don't have a custom ROM. When the newest update is available, am I safe to update?

ILowry282 said:
I am new to this. I have a rooted nexus 5. It is stock rooted with TRWP recovery. I don't have a custom ROM. When the newest update is available, am I safe to update?
Click to expand...
Click to collapse
Since your post was made today, and the update was released yesterday I'm assuming you are thinking that you will be getting the update over the air? You won't. When you have a custom recovery (TWRP) you won't get OTA's.
But don't be disheartened, not in the LEAST. Unless you've removed or altered the default system apps (you would know if you did) all you have to do is download the update to your phone, boot into TWRP, flash the update, and let the phone reboot.
Due to how the OTA updates are rolled out, even if you had not loaded a custom recovery onto your phone, you might not have had it pushed to you for a couple of weeks.
Read this thread:
http://forum.xda-developers.com/showthread.php?t=2523217
From what you have described you are "scenario 2". Proceed directly to step B. Like many people, I was also step B. It is easier than making toast.

So if I update that way will I lose my data and root? Also do I unzip the file or flash the zip file?

ILowry282 said:
So if I update that way will I lose my data and root? Also do I unzip the file or flash the zip file?
Click to expand...
Click to collapse
1. If you flash a custom ROM via TWRP it is generally recommended you do a clean wipe beforehand (and before doing that, obviously create a backup). There are cases where you can go straight to flashing without wiping, which is called a dirty flash. Although this is used when you're flashing an updated version of the ROM you're currently running. Following instructions under Section B won't cause you to lose data.
2. You won't lose root because ROMs will generally take this into account. However, if you do happen to lose root, just download and flash SuperSU and you're back on track.
3. Just flash the zip file.

ILowry282 said:
So if I update that way will I lose my data and root? Also do I unzip the file or flash the zip file?
Click to expand...
Click to collapse
The first part of the reply above is certainly correct, (the rest is also, but I'm just speaking to the first part of it) but I feel it is just going to confuse you.
You did not flash a custom ROM, you flashed a custom RECOVERY. Two different things. When you copy the update onto your phone, in the form that exists in the thread I linked earlier, it is not an entire image. It is an UPDATE to the stock image, which you are already using. As for your concern of losing root, it shouldn't be a concern. As was mentioned in the reply above mentioned, while you are in recovery you can simply just flash SU again.
In fact, I'd be willing to bet the file to flash SU is still on your phone.
As for me personally, I happened to have unlocked the pro version of SU (because why not...it's only $2.50 and I like the app) and just toggled the "survival mode" option. But even if I had not, it would have been a very small thing to loading SU again.
In short, don't worry about losing root. When you first rooted this phone, most of the steps involved were not in rooting the phone, but in unlocking the bootloader. Loading this update has nothing to do with that, so in your case, since you didn't flash a custom ROM (Such as CyanogenMod) and you didn't make any modifications to the system apps...quite literally all you have to do is copy the stuff onto your phone, load into TWRP, fire up the update, and either fire up SU, or have survival mode already enabled, and reboot the phone.
(and no, you don't have to unzip the file pasted in the thread, just copy it directly) The instructions in that thread are really simple, and that's probably giving you a bit of pause, but seriously, it really is that simple in your case, as it was mine.

So I updated but lost root. How do I flash SU?

ILowry282 said:
So I updated but lost root. How do I flash SU?
Click to expand...
Click to collapse
Do you still have custom recovery cwm or twrp? If so download su zip from either of those posts and flash in recovery if not you can flash recovery with adb or flashify and then flash su zip.
Sent from my Nexus 5 using Tapatalk

Worked perfect. Thanks

[Q] Unrooting problem

So i did something stupid right after rooting my Relay. I deleted basic stock files that are necessary for the phone to function properly. I was able to copy them from my current phone (rooted T-Mobile G2/Desire Z) onto an SD card and in turn push them back onto my Relay. My problem is that I still get error messages constantly after boot up and the simplest tasks can take hours (not to mention I can't use phone, contacts, messaging). I have seen all over the web (and XDA) about unrooting the phone and retuning it to stock. I was thinking that I could unroot, then reroot my Relay and that will solve my problem.
I was all set to unroot when I encountered yet another issue. Samsung-updates.com and sammobile both direct you to download the firmware files from hotfile. Hotfile has been shut down due to copyright infringement. Where I can find the stock firmware files now that hotfile has been shut down?
Please help me as I anxiously await using my new phone without the extra bloatware!
Thank you,
RockinRita

RockinRita said:
I was all set to unroot when I encountered yet another issue. Samsung-updates.com and sammobile both direct you to download the firmware files from hotfile. Hotfile has been shut down due to copyright infringement. Where I can find the stock firmware files now that hotfile has been shut down?
Click to expand...
Click to collapse
Would Samsung's Kies software be able to restore it to stock, or is it too far gone for Kies to work?

Bobby Tables said:
Would Samsung's Kies software be able to restore it to stock, or is it too far gone for Kies to work?
Click to expand...
Click to collapse
Without the stock files wouldn't Kies be pointless?

The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.

Pushing on a Relay
RockinRita said:
So i did something stupid right after rooting my Relay. I deleted basic stock files that are necessary for the phone to function properly. I was able to copy them from my current phone (rooted T-Mobile G2/Desire Z) onto an SD card and in turn push them back onto my Relay.
Click to expand...
Click to collapse
I did a very similar thing to my Relay and I can only get it boot off of the SD card. I am curious how you performed the push. I assumed that you
used adb push, but how?
Thanks,
Lou

scopedial said:
I did a very similar thing to my Relay and I can only get it boot off of the SD card. I am curious how you performed the push. I assumed that you used adb push, but how?
Thanks,
Lou
Click to expand...
Click to collapse
I copied the files from my rooted HTC Desire Z/ T-Mobile G2 to a spare SD card I have and then I inserted that card into my Relay and started it up. It took me a few hours to get passed all the error messages that constantly pop up. And then I went into my files, external SD and moved the files over to the system folder on the Relay. After several reboots, the error messages still are coming up which I why I need to unroot it and reroot it.

Magamo said:
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Click to expand...
Click to collapse
You may have just saved me, Magamo! Thank you for saving them to Drive! Once I get on my old slow Dell laptop (i'm on my Chromebook now- which unfortunately doesn't support most things) I'll try to flash your files and update you here since I cannot comment on your post as I have not posted enough myself.

Stock ROM Restore Method I Used
Magamo said:
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Click to expand...
Click to collapse
You could also use Odin to flash a md5 sum of T699UVBMC5_HOME using the download mode of the Relay. Place in PDA, and tick off the Auto Reboot and F. Reset Time and hit start. Make sure you have the drivers required to do this. I think they're included with Kies. In my case, I used CWM to format /system, then I used download mode. However, I had to reset my device. AND CWM (plus root access) was erased after the stock restore. I didn't miss an important detail, did I?

furboom1240 said:
You could also use Odin to flash a md5 sum of T699UVBMC5_HOME using the download mode of the Relay. Place in PDA, and tick off the Auto Reboot and F. Reset Time and hit start. Make sure you have the drivers required to do this. I think they're included with Kies. In my case, I used CWM to format /system, then I used download mode. However, I had to reset my device. AND CWM (plus root access) was erased after the stock restore. I didn't miss an important detail, did I?
Click to expand...
Click to collapse
I'll be honest, you've got me on this one. I've never used ODIN, and am not well versed in its use. But yes, this is sounds like a more technical way of doing it without the CWM flashables I've mentioned. -- Impossible in some situations. For example, my fiancee's phone's USB port has died for all purposes other than charging, So if I'm to send it in for a warranty repair, I'll have to use the method I posted.

Confused here
Magamo said:
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Click to expand...
Click to collapse
Magamo,
I'm sorry, but I'm still totally confused here. Not sure how to flash the files in. I downloaded Kies and both of the zip files from your post. Successfully updated the firmware and my error messages are gone, but I don't have CWM on it. I extracted your files, but now what? I'm not very technologically inclined so this is all Greek to me.
furboom1240 said:
You could also use Odin to flash a md5 sum of T699UVBMC5_HOME using the download mode of the Relay. Place in PDA, and tick off the Auto Reboot and F. Reset Time and hit start. Make sure you have the drivers required to do this. I think they're included with Kies. In my case, I used CWM to format /system, then I used download mode. However, I had to reset my device. AND CWM (plus root access) was erased after the stock restore. I didn't miss an important detail, did I?
Click to expand...
Click to collapse
furboom,
What is T699UVBMC5_HOME? How do I get the md5 sum of it? How do I use CWM to format /system? How do I get to stock restore? Again, I'm sorry for asking so many questions, i just have no clue what I'm doing here.
Thanks,
Rockin Rita

RockinRita said:
Magamo,
I'm sorry, but I'm still totally confused here. Not sure how to flash the files in. I downloaded Kies and both of the zip files from your post. Successfully updated the firmware and my error messages are gone, but I don't have CWM on it. I extracted your files, but now what? I'm not very technologically inclined so this is all Greek to me.
furboom,
What is T699UVBMC5_HOME? How do I get the md5 sum of it? How do I use CWM to format /system? How do I get to stock restore? Again, I'm sorry for asking so many questions, i just have no clue what I'm doing here.
Thanks,
Rockin Rita
Click to expand...
Click to collapse
If you don't have CWM, or some other custom recovery running on this, how did you get root in the first place? The easiest way to get root is to use heimdall or ODIN to flash CWM or another custom recovery, then flash Superuser or SuperSU using your new custom recovery.
The .zip files I linked are only meant to be flashed through recovery. Not Kies, not ODIN, not any other method.

Got it!!
With the help of this site (http://www.celldekho.com/how-to-unroot-samsung-galaxy-s-relay-4g/) and the file it linked to on rapidshare, along with your tip Magamo, I was able to unroot my Relay successfully. I'll reroot it later when I have the time and make sure not to delete important files LOL Thanks so much for the help!

[Q] Trouble installing CWM after OTA 4.3 Update

Hi guys,
Looking for some advice.
I previously had my phone rooted on 4.2 and everything was working great. For some reason I decided to install the OTA 4.3 update before reading here what it did. Before that though, I did a full backup through CWM.
Anyway, I'm now having trouble re-installing CWM to get back into recovery mode and go back to my backup.
When I try flashing it through Odin, it says Failed, and it seems like the phone blocked it because it is a recovery system.
Currently, when I boot up, I get the Custom logo, and when I try to go into recovery mode, it gets blocked and says it's unauthorized software, so I don't think I really installed the update right.
So, is there anyway to get CWM back on the phone to revert to my backup, or is there a way to flash the whole backup from a PC? The file is still intact on my SD card.
Thanks!

phlass said:
Hi guys,
Looking for some advice.
I previously had my phone rooted on 4.2 and everything was working great. For some reason I decided to install the OTA 4.3 update before reading here what it did. Before that though, I did a full backup through CWM.
Anyway, I'm now having trouble re-installing CWM to get back into recovery mode and go back to my backup.
When I try flashing it through Odin, it says Failed, and it seems like the phone blocked it because it is a recovery system.
Currently, when I boot up, I get the Custom logo, and when I try to go into recovery mode, it gets blocked and says it's unauthorized software, so I don't think I really installed the update right.
So, is there anyway to get CWM back on the phone to revert to my backup, or is there a way to flash the whole backup from a PC? The file is still intact on my SD card.
Thanks!
Click to expand...
Click to collapse
There is currently no way for you to flash CWM onto your S3 now that you have TW 4.3 VRUMCL1 update. If you want root, you will need to use Saferoot. If you wish to flash custom roms, you are currently only able to flash custom TW 4.3 roms via the use of SafeStrap. With Safestrap installed, you will be using a customized version of TWRP. Any and all of your CWM backups are incompatible and wasting storage space. Links to everything I just mentioned are contained in our TW 4.3 discussion thread.
Note that when you use Saferoot to gain root access, the tool is in the S4 section however it states that there is nothing in the tool itself that is S4 specific and that it should work on other 4.3 devices. It does work. Search in the discussion thread or in Saferoot thread to see confirmation.
Edit: to work around the Yellow triangle issue, you'll want to use ThePagel's soft brick thread.
Edit #2: Also, being that you are on TW 4.3 update, you absolutely can not downgrade your firmware using pre-existing Odin stock images. You can only use the official, VRUCML1 tar that is about 1 GB.

SlimSnoopOS said:
There is currently no way for you to flash CWM onto your S3 now that you have TW 4.3 VRUMCL1 update. If you want root, you will need to use Saferoot. If you wish to flash custom roms, you are currently only able to flash custom TW 4.3 roms via the use of SafeStrap. With Safestrap installed, you will be using a customized version of TWRP. Any and all of your CWM backups are incompatible and wasting storage space. Links to everything I just mentioned are contained in our TW 4.3 discussion thread.
Note that when you use Saferoot to gain root access, the tool is in the S4 section however it states that there is nothing in the tool itself that is S4 specific and that it should work on other 4.3 devices. It does work. Search in the discussion thread or in Saferoot thread to see confirmation.
Edit: to work around the Yellow triangle issue, you'll want to use ThePagel's soft brick thread.
Edit #2: Also, being that you are on TW 4.3 update, you absolutely can not downgrade your firmware using pre-existing Odin stock images. You can only use the official, VRUCML1 tar that is about 1 GB.
Click to expand...
Click to collapse
Ok great. Thanks for the help.

phlass said:
Ok great. Thanks for the help.
Click to expand...
Click to collapse
Don't hesitate to post back if you're stuck or need a little more clarification

[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.