Database Users

[Q] Is nuke & pave the only way to update a rooted s4?

Hi,
I have OUDHS-Recovery-jfltespr-1.0.3.3 and CF-Auto-Root-jfltespr-jfltespr-sphl720 flashed on my SPH-L720, on what was stock 4.2.2
My question is, do I HAVE to nuke & pave (factory reset) to get this to 4.3 and then re-root it?
If so, why? I thought one of the big advantages to rooting an Android was the ease with which you could un-root and return to stock.. I remember having to do factory resets to update iPhones before re-jailbreaking them, what a joy! I was hoping to avoid that here, especially as I'm behind a restrictive data cap for internet (~10GB/mo, which is about 300MB/day, combined up & down).
So... any ideas?

0x6A7232 said:
Hi,
I have OUDHS-Recovery-jfltespr-1.0.3.3 and CF-Auto-Root-jfltespr-jfltespr-sphl720 flashed on my SPH-L720, on what was stock 4.2.2
My question is, do I HAVE to nuke & pave (factory reset) to get this to 4.3 and then re-root it?
If so, why? I thought one of the big advantages to rooting an Android was the ease with which you could un-root and return to stock.. I remember having to do factory resets to update iPhones before re-jailbreaking them, what a joy! I was hoping to avoid that here, especially as I'm behind a restrictive data cap for internet (~10GB/mo, which is about 300MB/day, combined up & down).
So... any ideas?
Click to expand...
Click to collapse
You have to be on a totally stock firmware to apply these firmware updates.So you can be rooted and update, as long as you have no mods applied, like the hotspot mod, etc.
Seems the easiest path if you do have any mods applied (which would be most rooted users, I'm sure) is do a full nandroid backup and TiBu or Helium backup. Also backup anything else from internal memory that might be lost, like Nova settings, etc. Then load the MF9 stock tar via Odin. To do that, follow the directions in the following thread in the section labled "Reverting to Unmodified Stock MDL to update to Stock MF9". Just use the MF9 tar instead of the MDL one:
http://forum.xda-developers.com/showthread.php?t=2277480
Use triangle away to clear your "custom" settings on the Download screen. May even have to do a 2nd factory reset to get there.
Then root using CF Auto Root and let TiBu restore all your apps. Then use the stock recovery to load the 4.3 update. If all goes well, that should give you 4.3 on a rooted phone w/o tripping the knox bit.

oops
Ironically, I had just rooted the day before 4.3 came out. The only 'mod' I have is the CWM custom recovery.. I'm guessing that's what's tripping it up?
When I try to apply the update .zip in CWM, it says,
Code:
-- Installing: /sdcard/0/Download/update_SPH-L720_MDL_CSB_user_RP_to_MF9_CSB_user_RP.zip
Finding update package...
Opening update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check(" /system/app/AllSharePlay15.apk", "dae9b84dd3cb4810371f2a6136a0536cac926af5", "37b87ff87a955c98258cef2145b4b7b913eb0752")
E:Error in /sdcard/0/Download/update_SPH-L720_MDL_CSB_user_RP_to_MF9_CSB_user_RP.zip
(Status 7)
Installation aborted.
Aaaaand, I found the problem. MF9 is 4.2.2, yes? I've already got that, I need to be trying to flash MJA/4.3 :silly: For some reason I thought MF9 was 4.3, until I realized I had it already and I'm on 4.2.2. Sorry for the confusion. Now to find the 4.3/MJA download... :cyclops:
You have to be on a totally stock firmware to apply these firmware updates.So you can be rooted and update, as long as you have no mods applied, like the hotspot mod, etc.
Seems the easiest path if you do have any mods applied (which would be most rooted users, I'm sure) is do a full nandroid backup and TiBu ='Titanium Backup', I'm assuming?or Helium backup. Also backup anything else from internal memory that might be lost, like Nova settings, etc. Then load the MF9 stock tar via Odin. To do that, follow the directions in the following thread in the section labled "Reverting to Unmodified Stock MDL to update to Stock MF9". Just use the MF9 tar instead of the MDL one:
http://forum.xda-developers.com/show....php?t=2277480
Use triangle away to clear your "custom" settings on the Download screen. May even have to do a 2nd factory reset to get there.
Then root using CF Auto Root and let TiBu restore all your apps. Then use the stock recovery to load the 4.3 update. If all goes well, that should give you 4.3 on a rooted phone w/o tripping the knox bit.
Click to expand...
Click to collapse

You will need to install the stock recovery, the MJA update will not install with a custom recovery.
Sent from my GT-N5110 using Tapatalk 4

cruise350 said:
You will need to install the stock recovery, the MJA update will not install with a custom recovery.
Click to expand...
Click to collapse
Correct. And you can get the MF9 one here:
http://forum.xda-developers.com/showthread.php?t=2357471

Camera MJA firmware manual update - possible?
jejb said:
You have to be on a totally stock firmware to apply these firmware updates.So you can be rooted and update, as long as you have no mods applied, like the hotspot mod, etc.
Seems the easiest path if you do have any mods applied (which would be most rooted users, I'm sure) is do a full nandroid backup and TiBu or Helium backup. Also backup anything else from internal memory that might be lost, like Nova settings, etc. Then load the MF9 stock tar via Odin. To do that, follow the directions in the following thread in the section labled "Reverting to Unmodified Stock MDL to update to Stock MF9". Just use the MF9 tar instead of the MDL one:
http://forum.xda-developers.com/showthread.php?t=2277480
Use triangle away to clear your "custom" settings on the Download screen. May even have to do a 2nd factory reset to get there.
Then root using CF Auto Root and let TiBu restore all your apps. Then use the stock recovery to load the 4.3 update. If all goes well, that should give you 4.3 on a rooted phone w/o tripping the knox bit.
Click to expand...
Click to collapse
cruise350 said:
You will need to install the stock recovery, the MJA update will not install with a custom recovery.
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
jejb said:
Correct. And you can get the MF9 one here:
http://forum.xda-developers.com/showthread.php?t=2357471
Click to expand...
Click to collapse
Thanks guys. I ended up installing SAC's 4.1 (based on Android 4.3), after manually flashing the MJA modem firmware.
(Because even after flashing stock recovery, I was getting error 7 or something like that, no clue why, I tried searching a few days, but no dice. The recommendation was to flash non-destructive MF9 stock update over first and then update, so I just downloaded Sac's while I had 4G on the way back from work).
NEW QUESTION: How do I get the updated camera firmware, as Sac's modded stock camera seems not to have it. (although, maybe Sac's camera is in error and the firmware is already updated it just doesn't realize).
I can get a patched camera to not do the popup, but I want the firmware. Any way to extract it from the stock MJA OTA file and flash just that?

0x6A7232 said:
Thanks guys. I ended up installing SAC's 4.1 (based on Android 4.3), after manually flashing the MJA modem firmware.
(Because even after flashing stock recovery, I was getting error 7 or something like that, no clue why, I tried searching a few days, but no dice. The recommendation was to flash non-destructive MF9 stock update over first and then update, so I just downloaded Sac's while I had 4G on the way back from work).
NEW QUESTION: How do I get the updated camera firmware, as Sac's modded stock camera seems not to have it. (although, maybe Sac's camera is in error and the firmware is already updated it just doesn't realize).
I can get a patched camera to not do the popup, but I want the firmware. Any way to extract it from the stock MJA OTA file and flash just that?
Click to expand...
Click to collapse
Error 7 is normally when your recovery pics up that you are rooted. Or when there is a problem with the updater script in the zip file.
If sacs used the MJA camera as a base for his nodded camera then he should have the latest camera firmware.
If you worry this much about Tue camera you can download a stock rooted MJA ROM and go into system/apps with a root explorer and extract the camera apk. Then go to where the camera apk is extracted to and move it to your internal memory under system apps. Then set permissions and reboot.
Sent from my SPH-L720 using Tapatalk

daniel4653 said:
Error 7 is normally when your recovery pics up that you are rooted. Or when there is a problem with the updater script in the zip file.
If sacs used the MJA camera as a base for his nodded camera then he should have the latest camera firmware.
If you worry this much about Tue camera you can download a stock rooted MJA ROM and go into system/apps with a root explorer and extract the camera apk. Then go to where the camera apk is extracted to and move it to your internal memory under system apps. Then set permissions and reboot.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
The camera supposedly had some improvements, that's why I'm trying to find out. I'd ask in Sac's thread, but I don't have enough posts yet. And, I used SuperSU's uninstall to unroot the phone before trying the MJA OTA... although I did put stock recovery first, IIRC. Perhaps the root uninstall needed custom recovery to work? Anyways.
Under cce8d8a155a0602c83356e00311a1695e9a9383f.USER_L720_SPT_MF9_CSB_user_RP_to_MJA_CSB_user_RP_Update_FWD.zip\patch\system\cameradata\ there are a few items:
secimaging\PIP\rear_polaroid.png.p
RS_M10MO_OS.bin.p
RS_M10MO_SL.bin.p
RS_M10MO_SS.bin.p
I'll have to find someone who is knowledgeable about this and pick their brain if they'll let me.

[Q] Deleted Stock Recovery?

Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!

DarthVayda said:
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
Click to expand...
Click to collapse
If you don't mind losing your user data (back up anything you want from internal storage) just flash the MK2 full ODIN. Otherwise, there is a thread somewhere with just the MF3 recovery image and if you have root you could use an app to manually flash that (don't remember the app).

DeadlySin9 said:
If you don't mind losing your user data (back up anything you want from internal storage) just flash the MK2 full ODIN. Otherwise, there is a thread somewhere with just the MF3 recovery image and if you have root you could use an app to manually flash that (don't remember the app).
Click to expand...
Click to collapse
The app is flashify
Sent from my Nexus 5 using XDA Free mobile app

Possible to restore stock recovery?
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!

pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
I would flash in Odin the stock mf3 tar file, but out will wipe the device. All his apps and data. If you can find the mf3 recovery image file you could try to flash that in flashify, if you're rooted
Edit, found this. I didn't download the file but I'm guessing it's a .img file. You could flash that in flashify or use the dd command
Sent from my Nexus 5 using XDA Free mobile app

pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
In addition to the above post from jd, the CM installer will not work on our device as our bootloader is locked. There is no way to run any AOSP based ROM once your phone is on MF3 firmware or higher.

DarthVayda said:
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
Click to expand...
Click to collapse
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
Here is the MF3 stock recovery, flash in PDA slot in Odin(AP in Odin v3.09+): https://mega.co.nz/#!klcz1B4J!BVAno0CcaJ7aXc9tHgUtpQ0vy_NF5ceh7RogLR6JBTU

muniz_ri said:
Here is the MF3 stock recovery, flash in PDA slot in Odin(AP in Odin v3.09+): https://mega.co.nz/#!klcz1B4J!BVAno0CcaJ7aXc9tHgUtpQ0vy_NF5ceh7RogLR6JBTU
Click to expand...
Click to collapse
Thanks to everyone for all the information, and thank you especially for sharing the link. I am staying with my parents short-term in a very rural area with awful internet and I was dreading downloading the 2+GB stock firmware file just to get recovery back. This is perfect. Thanks again!

Problems with ODIN'ing stock recovery

I am currently on the unlocked MDL bootloader, and I am running KANGAKAT 7.0, which is a KitKat 4.4 ROM. My phone is also encrypted, which means that I cannot flash updates due to CWM/TWRP not supporting encryption.
The solution proposed by other users has been to ODIN the stock MK2 recovery onto my phone, use the stock recovery to factory reset my device, then re-flash TWRP and then my new ROM.
However I'm having a problem with these steps. I am able to successfully ODIN the stock MK2 recovery to my device, however whenever I try to boot into recovery, I get the yellow triangle screen stating that I'm running software that is not authorized by AT&T, and stating something to do with my kernel in the top left of the screen.
Is there a step that I am missing? I followed the instructions @ http://forum.xda-developers.com/showthread.php?t=1506697

It looks like that file is for the s2 skyrocket, not the s4. You'll probably have to flash the complete mdl firmware in Odin
Edit, if you're still rooted try flashing twrp 2.8.3.0 image file in flashify from the play store. http://techerrata.com/browse/twrp2/jflteatt
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
It looks like that file is for the s2 skyrocket, not the s4. You'll probably have to flash the complete mdl firmware in Odin
Edit, if you're still rooted try flashing twrp 2.8.3.0 image file in flashify from the play store. http://techerrata.com/browse/twrp2/jflteatt
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, they're instructions for the S2 Skyrocket, but I just used the general procedure and not the file, I used the stock recovery listed here http://forum.xda-developers.com/showpost.php?p=49687791&postcount=3
You make an interesting point though, if I ODIN the entire stock MDL ROM, that could work. I'm just going to write over it with another ROM anyways, so what I restore to shouldn't matter. I know this is probably a dumb question, but flashing the stock MDL ROM isn't going to affect my MDL bootloader is it?
I can get TWRP 2.8.3.0 with or without Flashify, but that app is very convenient, thank you for the tip =)

ChrisG683 said:
Yeah, they're instructions for the S2 Skyrocket, but I just used the general procedure and not the file, I used the stock recovery listed here http://forum.xda-developers.com/showpost.php?p=49687791&postcount=3
You make an interesting point though, if I ODIN the entire stock MDL ROM, that could work. I'm just going to write over it with another ROM anyways, so what I restore to shouldn't matter. I know this is probably a dumb question, but flashing the stock MDL ROM isn't going to affect my MDL bootloader is it?
I can get TWRP 2.8.3.0 with or without Flashify, but that app is very convenient, thank you for the tip =)
Click to expand...
Click to collapse
Flashing the mdl firmware in Odin will still give you the mdl bootloader. But it'll want to update after you flash so flash another custom rom or freeze the update files before it does so.
Sent from my Nexus 5 using XDA Free mobile app

@ChrisG683 Be sure to turn your wi-fi off and remove your SIM card, that way it can't update. You can put any apps you think you might need on an SD card and install them without having to go to the play store. Once you get things frozen or removed then you'll be good to go. :good:

Thanks guys, I'll be sure to keep that in mind once I get things sorted out.
The newest thing I've figured out is that the MDL stock recovery does not give me the "yellow triangle" error, and it presents me with the option to wipe my device. (I grabbed it from here http://forum.xda-developers.com/showthread.php?t=2429406)
Now I'm just making sure I have a stock MDL ROM ready to ODIN in case I screw up my device =). Hopefully this all works out.
Edit:
Looks like everything went beautifully. The MDL stock recovery wiped my /data partition perfectly, and I was able to reboot into a fresh and clean copy of KANGAKAT 6.0. Then I was able to use a terminal to flash TWRP, did a factory reset, flashed KANGAPOP 1.4, and now you can add me to the list of proud Lollipop users =)

Xposed and Safestrap on Lollipop?

I recently upgraded today from 4.4.2 to 5.0 OC4 and kept root using this method: http://forum.xda-developers.com/ver...0-keeproot-t3068546/post59791648#post59791648
However, I had no Idea it would be so hard (impossible?) to get xposed back. Is there any way in which I could install xposed ARM without having a custom recovery on my verizon G900V running lollipop?
I also read an article on another website that said you can flash safestrap with odin, go into safestrap, install anything necessary, and then reflash current ROM? I am not TOO knowledgable with all of this, however I have found my way around all this enough to ensure myself root and all needed features. Any help or information would be amazing.
Article: http://www.droidforums.net/threads/galaxy-s5-safestrap-after-the-lollipop-update.279867/
I was considering flashing the xposed ARM file with flashfire, however I read someone else was stuck in a bootloop who tried this. Would this not work? Is there any method? I was also looking into flash gordon which lets you flash .zip files without requiring custom recovery. Thanks!
EDIT: Just did some more research and found this thread: http://forum.xda-developers.com/galaxy-s4-att/general/nc1-flasher-odin-to-safestrap-t3082620
It seems as if its possible, however this thread is for the OC3 version, while I flashed the OC4... Anyone out there done anything like this before, or knows how to provide the needed steps? Thanks again.

Go to the xposed thread and read any comment at all. It doesn't work on touchwiz based lollipop architecture. PERIOD. you didn't need a new thread in this forum to learn that...

I see, is there some way that I could downgrade. I've been looking into that for awhile now to go back to my 4.4.2 but there's a ton of methods and I am not sure which is required for my device. I canno't seem to find a specific method for my g900v s5. Thanks for you're reply, and I hope I can downgrade.

synkro1 said:
I see, is there some way that I could downgrade. I've been looking into that for awhile now to go back to my 4.4.2 but there's a ton of methods and I am not sure which is required for my device. I canno't seem to find a specific method for my g900v s5. Thanks for you're reply, and I hope I can downgrade.
Click to expand...
Click to collapse
You can use this guide: http://forum.xda-developers.com/showthread.php?t=3088571 it might need some modification for 4.4.2, however.

synkro1 said:
I see, is there some way that I could downgrade.j I've been looking into that for awhile now to go back to my 4.4.2 but there's a ton of methods and I am not sure which is required for my device. I canno't seem to find a specific method for my g900v s5. Thanks for you're reply, and I hope I can downgrade.
Click to expand...
Click to collapse
You can go up and down as often as you like. I would Odin the NCG tar from the link below and reroot.
You probably still have safestrap. You could try this first. Go to download mode and Odin the NE9 kernel. When your phone starts booting up you should see the safestrap option to boot into recovery. Boot into recovery, install a rooted NE9 ROM of your choice. Boot back into download mode via safestrap and Odin the NE9 firmware. Let your phone boot all the way up and you should be good to go. Use NCG kernels and firmware-roms if you would rather be on NGC.
http://forum.xda-developers.com/ver...ment/stock-collection-kernels-modems-t2842069
If safestrap doesn't show up, Odin the full NCG tar file and reroot your phone.

Thanks so much for your help, the only problem is I never installed safestrap on my phone. So I do not currently have safe strap, or any custom recovery. So i can just use the odin method then, correct?

[PHP[/PHP]
synkro1 said:
Thanks so much for your help, the only problem is I never installed safestrap on my phone. So I do not currently have safe strap, or any custom recovery. So i can just use the odin method then, correct?
Click to expand...
Click to collapse
Yes, sir. That would be correct. Since you are rooted, there is an app called Flashfire you could use that doesn't even require a computer but if you are familiar with Odin that is a good way to go as well.

I have flashfire installed, in fact I used it to upgrade to lollipop. What settings should I use with flashfire to downgrade to lollipop? Do i have to clear cache or anything? And will the file from the notes #4 from here work?: http://forum.xda-developers.com/ver...0-keeproot-t3068546/post59791648#post59791648

synkro1 said:
I have flashfire installed, in factj I used it to upgrade to lollipop. What settings should I use with flashfire to downgrade to lollipop? Do i have to clear cache or anything? And will the file from the notes #4 from here work?: http://forum.xda-developers.com/ver...0-keeproot-t3068546/post59791648#post59791648
Click to expand...
Click to collapse
What ROM do you want to have on your phone?

Just a normal stock 4.4.2 ROM works fine for me.

synkro1 said:
Just a normal stock 4.4.2 ROM works fine for me.
Click to expand...
Click to collapse
Download this ROM onto your SD card. I prefer deodex
http://forum.xda-developers.com/showthread.php?t=2793931
Download the NGC retail firmware from here.
http://forum.xda-developers.com/ver...ment/stock-collection-kernels-modems-t2842069
In Flashfire, select firmware and navigate to your firmware. Just check boot and recovery
Next select zip-ota, navigate to your ROM. Leave auto mount unchecked.
Select firmware again. This time check boot, recovery, modem, and firmware. Flashfire will ask if you want them in separate zips. Click yes
Now select wipe. Check everything but SD card.
Now arrange everything in this order
Wipe
Firmware-boot recovery
Zip-rom
Firmware modem firmware
Firmware-boot recovery
Ever root- inject supersu
Boot normal
That should do it. You should be rooted on 4.4.2

Tulsadiver said:
Download this ROM onto your SD card. I prefer deodex
http://forum.xda-developers.com/showthread.php?t=2793931
Download the NGC retail firmware from here.
http://forum.xda-developers.com/ver...ment/stock-collection-kernels-modems-t2842069
In Flashfire, select firmware and navigate to your firmware. Just check boot and recovery
Next select zip-ota, navigate to your ROM. Leave auto mount unchecked.
Select firmware again. This time check boot, recovery, modem, and firmware. Flashfire will ask if you want them in separate zips. Click yes
Now select wipe. Check everything but SD card.
Now arrange everything in this order
Wipe
Firmware-boot recovery
Zip-rom
Firmware modem firmware
Firmware-boot recovery
Ever root- inject supersu
Boot normal
That should do it. You should be rooted on 4.4.2
Click to expand...
Click to collapse
Ur amazing. I'll try it and let you know. Thanks so much for your help.

Thanks so much! It worked perfectly! I had a problem initially after installing towelroot and xposed and got an error when rebooting the phone called "Process system isn't responding". My phone kept freezing and was super slow because of this. I believe it was due to me restoring contacts from titanium backup. I restored the contacts system app as a whole. I didn't realize that at the time however, and just system restored my phone again, and did everything the same yet didn't restore my contacts, and the message is now gone. I am not running root with xposed on 4.4.2. Your amazing!

I need help with installing the Alliance ROM PLEASE.

EDIT: I have successfully installed the Alliance ROM. Here's how i did it.
Prerequisites:
Your phone at at least 50% battery
A charge cable
MicroSD card that you can plug into your computer
Odin 3.09
SafeStrap, version 3.75 APK on your MicroSD card
Alliance ROM on your MicroSD card
NCG tar.md5 (the big file, not the kernel)
I started off on a rooted 5.0 VZW Galaxy S5. After some confusion, I downgraded to NCG (4.4.2) using Odin. After doing that, I went to Towelroot, got the APK, rooted, downloaded SuperSU from the play store (I had to sign into google at this point), installed it's binaries (NORMALLY! Don't choose the TWRP method), rebooted when it asked me to. From there, I installed BusyBox from the play store and installed it within the app. Then I installed Safestrap (version 3.75), which I had on my MicroSD card. I used the app My Files to navigate to my MicroSD and installed the APK. Then I installed it within the app, and when the "reboot to recovery" button worked, I rebooted into SafeStrap recovery mode. At this point, the Alliance ROM zip file should ALREADY BE ON YOUR MICROSD CARD, WHICH SHOULD BE IN YOUR PHONE. Now, you're going to press the INSTALL button to the top right in Safestrap recovery, and you're going to navigate to your MicroSD card. It might be already opened to that. Then you're gonna select the Alliance ROM and flash it. After it successfully flashes, reboot into download mode (if for some reason you aren't able to do it immediately, you get into download mode by holding volume down, home button, and power button at the same time). Now, using Odin, you're gonna flash the firmware that the instructions in the Alliance thread tells you to (here's the thread: http://forum.xda-developers.com/ver.../rom-alliancerom-build-3-rom-control-t2818632). If everything works, it's gonna take a couple of minutes, optimize apps, and boot.
Huge thanks to Beans and his team for creating the Alliance mod, and huge thanks to Tulsadiver for helping me get through the process during my confusion.
Original thread below
Hi. I'll cut to the chase. I was an idiot and thought I could just flash the Alliance ROM from my SD card, but my phone is currently a factory restored 5.0. So, after unsuccessfully flashing Alliance ROM, I thought, well, I probably need to be on 4.4.2 to do this. So, what I'm wondering is, do I need to go back down to 4.4.2 to install Alliance ROM? And do I need Safestrap recovery to do it, or can I do it from stock recovery (home button+volUp+Power)? I did a lot of digging in the Alliance ROM post and there were no posts regarding my problem/question, probably because they're all experienced and I'm not (this is my first time trying to flash a custom ROM).
It SOUNDS like I need to flash a full stock tar using Odin, is that correct? Once I do that, I would be on stock wiped 4.4.2, I assume. From there, could I flash the Alliance ROM and continue with the instructions? Or do I need to root first and get safestrap and all that crap? I feel like Beans was really vague with his instructions on installing ROMs, but whatever. Please help though, I'm kind of stuck in the middle of this with a softbricked phone.
Thank you so much in advance, I appreciate it.
~isra
EDIT: Also, I was on ROOTED 5.0 Lollipop just before this. I just got so sick of lollipop, I was ready for something different. So here we are. To confirm, my phone is the standard retail SM-G900VZW model.
EDIT2: Apparently App Ops and SuperSU survived the wipe and, after downloading Root Checker, I can confirm that I'm still rooted... Huh.

israphial said:
Hi. I'll cut to the chase. I was an idiot and thought I could just flash the Alliance ROM from my SD card, but my phone is currently a factory restored 5.0. So, after unsuccessfully flashing Alliance ROM, I thought, well, I probably need to be on 4.4.2 to do this. So, what I'm wondering is, do I need to go back down to 4.4.2 to install Alliance ROM? And do I need Safestrap recovery to do it, or can I do it from stock recovery (home button+volUp+Power)? I did a lot of digging in the Alliance ROM post and there were no posts regarding my problem/question, probably because they're all experienced and I'm not (this is my first time trying to flash a custom ROM).
It SOUNDS like I need to flash a full stock tar using Odin, is that correct? Once I do that, I would be on stock wiped 4.4.2, I assume. From there, could I flash the Alliance ROM and continue with the instructions? Or do I need to root first and get safestrap and all that crap? I feel like Beans was really vague with his instructions on installing ROMs, but whatever. Please help though, I'm kind of stuck in the middle of this with a softbricked phone.
Thank you so much in advance, I appreciate it.
~isra
EDIT: Also, I was on ROOTED 5.0 Lollipop just before this. I just got so sick of lollipop, I was ready for something different. So here we are. To confirm, my phone is the standard retail SM-G900VZW model.
EDIT2: Apparently App Ops and SuperSU survived the wipe and, after downloading Root Checker, I can confirm that I'm still rooted... Huh.
Click to expand...
Click to collapse
Download busybox from play store. Install it. Install safestrap. Once recovery is installed, go into recovery, install alliance, from within safestrap, boot into download mode and flash the full firmware Odin tar.

Tulsadiver said:
Download busybox from play store. Install it. Install safestrap. Once recovery is installed, go into recovery, install alliance, from within safestrap, boot into download mode and flash the full firmware Odin tar.
Click to expand...
Click to collapse
Wait, so I don't need to downgrade my phone? Keep in mind I'm on stock rooted 5.0, which just got factory reset so I got nothing except for the root. Also, what full firmware odin tar are you referring to? NE9? This one: https://www.androidfilehost.com/?fid=23610159112652201
Or this one: https://www.androidfilehost.com/?fid=23622183712472727
I'm getting these links from here: http://forum.xda-developers.com/ver...ment/stock-collection-kernels-modems-t2842069
I really appreciate you replying. Thank you.

The first one. That firmware will downgrade you to NE9.

Tulsadiver said:
The first one. That firmware will downgrade you to NE9.
Click to expand...
Click to collapse
Ok, so I don't need to downgrade to install the ROM. Got it. Thank you. Is there anything else I should know?

Not that I know of. ROM installations are different so always refer to their installation instructions. Some will say to flash the firmware first. The op knows best. Alliance NE9 says to do a full wipe (everything but SD card). Install the ROM, reboot to download mode ( don't hit reboot system). Once in download mode, flash the firmware tar and let your phone reboot.

Tulsadiver said:
Not that I know of. ROM installations are different so always refer to their installation instructions. Some will say to flash the firmware first. The op knows best. Alliance NE9 says to do a full wipe (everything but SD card). Install the ROM, reboot to download mode ( don't hit reboot system). Once in download mode, flash the firmware tar and let your phone reboot.
Click to expand...
Click to collapse
So, I installed Safestrap and did all that, but when I press the reboot into recovery button, it just reboots the phone normally. It doesn't go into safestrap recovery. Am I supposed to hold some buttons or something?

Did safestrap ask for SuperSU permissions? Did you install busy box? You can't just download the app.

Tulsadiver said:
Did safestrap ask for SuperSU permissions? Did you install busy box? You can't just download the app.
Click to expand...
Click to collapse
Yes, I've installed BusyBox and given SS root permissions. I installed the APK 3.75 Safestrap that I used to get into SS recovery when I was getting to rooted 5.0 a while back, so I know that the APK isn't corrupt or anything like that.

I forgot. You are on lollipop. You need to flash the NE9 kernel first ( via Odin). You already have safestrap but it doesn't work on lollipop. After you flash the NE9 kernel you will have the option to boot into recovery. Have alliance on your SD card ready to install.

Tulsadiver said:
I forgot. You are on lollipop. You need to flash the NE9 kernel first ( via Odin). You already have safestrap but it doesn't work on lollipop. After you flash the NE9 kernel you will have the option to boot into recovery. Have alliance on your SD card ready to install.
Click to expand...
Click to collapse
Found a "NE9 Stock tar.md5". Does that sound right? DL is here: https://www.androidfilehost.com/?fid=23578570567721275

Found a "NE9 Stock tar.md5". Does that sound right? DL is here: https://www.androidfilehost.com/?fid=23578570567721275

israphial said:
Found a "NE9 Stock tar.md5". Does that sound right? DL is here: https://www.androidfilehost.com/?fid=23578570567721275
Click to expand...
Click to collapse
That is it.

Tulsadiver said:
That is it.
Click to expand...
Click to collapse
Thank you. I'm going to flash the kernel then, then I'll get back to you if anything comes up. Again, I really appreciate you helping me. Thank you.

Tulsadiver said:
That is it.
Click to expand...
Click to collapse
It booted into stock recovery mode after odin successfully flashed NE9. Now do I install the ROM from stock recovery, or do I boot the phone and get to Safestrap to install the ROM from Safestrap recovery? I am currently in recovery mode.

You must not have had safestrap on your phone after all. Can you get back to download mode? You probably need to flash your lollipop kernel to get back to lollipop.

Tulsadiver said:
You must not have had safestrap on your phone after all. Can you get back to download mode? You probably need to flash your lollipop kernel to get back to lollipop.
Click to expand...
Click to collapse
I definitely had safestrap. Though, here's something: Everyone talks about a menu that pops up during boot that allows you to enter either safestrap recovery, or boot, and I've never had/seen that menu, even when I was rooting 5.0. Yes, my BusyBox worked and was properly installed, and yes, I had Safestrap recovery installed.
I just tried rebooting and it after sitting at the first screen for a while, it rebooted quickly and went back into recovery mode. What if I try installing Alliance from recovery mode? Will it work?

israphial said:
I definitely had safestrap. Though, here's something: Everyone talks about a menu that pops up during boot that allows you to enter either safestrap recovery, or boot, and I've never had/seen that menu, even when I was rooting 5.0. Yes, my BusyBox worked and was properly installed, and yes, I had Safestrap recovery installed.
I just tried rebooting and it after sitting at the first screen for a while, it rebooted quickly and went back into recovery mode. What if I try installing Alliance from recovery mode? Will it work?
Click to expand...
Click to collapse
I've never been on stock recovery before. I think it has to be a custom recovery. You might need to pull your battery and let it set for a bit and see if you can get into download mode.

Tulsadiver said:
I've never been on stock recovery before. I think it has to be a custom recovery. You might need to pull your battery and let it set for a bit and see if you can get into download mode.
Click to expand...
Click to collapse
I can get into download mode perfectly fine. I'm going to kernel back to 5.0 then...
But what do I do now? Should I downgrade to 4.4.2 with the stock firmware once I successfully boot 5.0?
EDIT: Yup, booted 5.0 perfectly fine. Now what? Downgrade to 4.4.2 and flash the NE9 Kernel?

Proof that Safestrap is on my phone:
http://imgur.com/cGa1v1n