Need some guidance on flashing NE5, so I can Towelroot. - Sprint Galaxy S 5 Q&A, Help & Troubleshooting

Alright, I'm sorry for this, but I've spent a good many hours reading and trying to figure this out, but I haven't come across anything that spells it out in a way I'm comfortable with. I'm trying to root and maintain my knox warranty, so I can tweak and use Xposed, and it seems the only way for me to do that is flash an older kernel, use towelroot, then flash back to the newer kernel.
Here's where I think I'm at: Stock Sprint S5 on 4.4.4. That means I have the NK4 kernel, and to use Towelroot, I have to flash the NE5 kernel, correct? Then once I get root, I can flash back to NK4, ending up with a rooted stock phone, with warranty still valid?
This is where I'm not sure how to proceed. I've downloaded ODIN 3.10, the samsung USB drivers, and the NE5 and NK4 kernel zip files (which both contain a boot.img file and META-INF folder). Once I install the USB drivers and ODIN, I'm not sure how to then use ODIN get the right kernel flashed.
A video, or nudges in the right direction would be greatly appreciated.

10Ring said:
Alright, I'm sorry for this, but I've spent a good many hours reading and trying to figure this out, but I haven't come across anything that spells it out in a way I'm comfortable with. I'm trying to root and maintain my knox warranty, so I can tweak and use Xposed, and it seems the only way for me to do that is flash an older kernel, use towelroot, then flash back to the newer kernel.
Here's where I think I'm at: Stock Sprint S5 on 4.4.4. That means I have the NK4 kernel, and to use Towelroot, I have to flash the NE5 kernel, correct? Then once I get root, I can flash back to NK4, ending up with a rooted stock phone, with warranty still valid?
This is where I'm not sure how to proceed. I've downloaded ODIN 3.10, the samsung USB drivers, and the NE5 and NK4 kernel zip files (which both contain a boot.img file and META-INF folder). Once I install the USB drivers and ODIN, I'm not sure how to then use ODIN get the right kernel flashed.
A video, or nudges in the right direction would be greatly appreciated.
Click to expand...
Click to collapse
The files you downloaded are for flashing in custom recovery, which will trip knox. (BTW, knox is overrated. I doubt you'd be denied warranty service because it's tripped).
Anyway, you want to download this file for NE5 and this one for NK4. Unzip them on your PC. Each one has a file that ends in .tar.md5.
Put your phone in download mode and hook it up to your PC. When you run Odin, you should have a blue COM button lit in the upper left side. If not, you don't have the drivers installed. Assuming you do have the blue light, tap the AP button and browse to the NE5 file and select it. Wait a bit as it takes maybe 30+ seconds to load it. Then click Start. Once finished, the phone will reboot.
After rebooting, run Towelroot. (I've never used that as I rooted on day one with CF Autoroot). Once rooted, you can follow the same instructions above to install NK4 again.
Hope this helps
FYI, what trips Knox is installing and running a custom recovery.

What Ramer said.
But honestly, MOAR Rom is pretty dang sweet. I was a huge xPosed fan, but MOAR and MOAR Mod Control make me forget about xPosed!

Related

[Q] Trying to install 4.3 OTA

My phone is rooted, and has TWRP custom recovery installed.
The phone automatically downloaded the OTA, and tried to install it. With TWRP, the update failed and my phone is working fine now.
I don't need the rooting anymore (was for teetering, but with new data plan it's now included). So I'm okay with losing the root and all.
Using SuperSU I deselected the rooting, and after reboot RootCheck tells me my phone is not rooted. I still have TWRP installed.
Now, I'm stock MF1/ 4.1.2. How do I install the 4.3 update and remove the TWRP recovery? I found in another thread the 4.3 Tar file. Do I simply use Odin on my PC and flash it on my phone? What about TWRP?
airtrons said:
My phone is rooted, and has TWRP custom recovery installed.
The phone automatically downloaded the OTA, and tried to install it. With TWRP, the update failed and my phone is working fine now.
I don't need the rooting anymore (was for teetering, but with new data plan it's now included). So I'm okay with losing the root and all.
Using SuperSU I deselected the rooting, and after reboot RootCheck tells me my phone is not rooted. I still have TWRP installed.
Now, I'm stock MF1/ 4.1.2. How do I install the 4.3 update and remove the TWRP recovery? I found in another thread the 4.3 Tar file. Do I simply use Odin on my PC and flash it on my phone? What about TWRP?
Click to expand...
Click to collapse
Are you sure you want the 4.3, this latest rom will lock your bootloader permanently, meaning you will NOT able to install CWM,TWRP, custom rom/kernel or downgrade the OS to the early version. The only thing you can do once updated is root. If you still decided to upgrade, just Odin the full rom MF1 here http://www.androidfilehost.com/?fid=23134718111254196 then after bootup your OS should auto update to the latest (OTA).
airtrons said:
My phone is rooted, and has TWRP custom recovery installed.
The phone automatically downloaded the OTA, and tried to install it. With TWRP, the update failed and my phone is working fine now.
I don't need the rooting anymore (was for teetering, but with new data plan it's now included). So I'm okay with losing the root and all.
Using SuperSU I deselected the rooting, and after reboot RootCheck tells me my phone is not rooted. I still have TWRP installed.
Now, I'm stock MF1/ 4.1.2. How do I install the 4.3 update and remove the TWRP recovery? I found in another thread the 4.3 Tar file. Do I simply use Odin on my PC and flash it on my phone? What about TWRP?
Click to expand...
Click to collapse
I had the same question myself, and have been proverbially "running around in circles" today (instead of working). Anybody have success flashing said Odin file and then upgrading via the OTA?
Ha! I came from a mytouch3g years ago, flashing incessantly. I got this phone so i could stop. Then rooted to take the ads away, and got a bit more than I bargained for... now I just want back on OTA stock.
Thanks for any suggestions.
Cheers
Kevvy1066 said:
I had the same question myself, and have been proverbially "running around in circles" today (instead of working). Anybody have success flashing said Odin file and then upgrading via the OTA?
Ha! I came from a mytouch3g years ago, flashing incessantly. I got this phone so i could stop. Then rooted to take the ads away, and got a bit more than I bargained for... now I just want back on OTA stock.
Thanks for any suggestions.
Cheers
Click to expand...
Click to collapse
if you download this full firmware http://www.androidfilehost.com/?fid=23134718111254196 unzip the file then use Odin to flash, this will bring you back to pure stock rom with stock recovery (no more twrp/cwm). After this you will be prompt for OTA and just take the upgrade. Once done you should be on the latest factory 4.3 with locked bootloader.
I ended up downloading the 4.3 files from another post here, and flashing it with Odin. Worked fine.
Of course, without a root, can't recover my apps from Titanium but oh well.
airtrons said:
I ended up downloading the 4.3 files from another post here, and flashing it with Odin. Worked fine.
Of course, without a root, can't recover my apps from Titanium but oh well.
Click to expand...
Click to collapse
Why don't you just root with saferoot found here?http://forum.xda-developers.com/showthread.php?t=2565758
I wish I would have found this thread before starting my own... woops. Anyway I would like to install 4.3 and I too rooted with twrp. I don't care anymore if I am rooted or not. I stopped flashing roms and such a while back and will be upgrading this next year to the s5 most likely.
Is there a way to install 4.3 w/out removing root? If not, since I never used odin, and used twrp what steps do/should I take to get back to where I can install 4.3?
Thank you.
Sithlyone said:
I wish I would have found this thread before starting my own... woops. Anyway I would like to install 4.3 and I too rooted with twrp. I don't care anymore if I am rooted or not. I stopped flashing roms and such a while back and will be upgrading this next year to the s5 most likely.
Is there a way to install 4.3 w/out removing root? If not, since I never used odin, and used twrp what steps do/should I take to get back to where I can install 4.3?
Thank you.
Click to expand...
Click to collapse
Since your life is too busy and you don't want to mess with your phone anymore, your best bet is go back to stock 4.3 which is very good by the way, very stable, smooth and bug free. After so many complaints from my wife I rolled it back to stock 4.3 and she's so happy now.
1. Flash stock MF1 here http://www.androidfilehost.com/?fid=23134718111254196 , just unzip the flash with Odin
2. Your phone should take the 4.3 OTA update and you're home free.

Bricked the S6 SM-920I. I'm at wits' end.

I got the Galaxy S6 yesterday and coming from Nexus 5, I wanted to remove the existing bloatware by flashing the XtrestoLite Deodexed ROM. This one here: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/rom-xtrestolite-deodexed-mod-edition-1-3-t3119968
I'm haven't had much experience in rooting and it's my first time flashing a custom ROM. The phone was running on Android 5.1.1.
Apparently I failed. I started with CF-Root but I wasn't sure if it was done correctly. This was followed by TWRP 2.8.7.1 . Then I tried booting up the phone and the boot logo just loops. I tried to wipe the cache as well as the Delvik-cache through TWRP but it's still the same. Then I tried to flash the stock ROM that I found online but I got the error "Nand Write Start" followed by "Fail". I seem to have tried everything and now I just want to get the phone to work again. It shouldn't be so hard.
Someone help me please :crying:
Have you tried to flash the stock rom via Smart Switch software? There's an option in the top of the window where it says "More" called Emergency Recovery. When my S6 bricked nothing but that did the trick, you should give it a try.
Gallitho said:
Have you tried to flash the stock rom via Smart Switch software? There's an option in the top of the window where it says "More" called Emergency Recovery. When my S6 bricked nothing but that did the trick, you should give it a try.
Click to expand...
Click to collapse
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Edit: I managed to do it through initialization. I'll update when it's done.
Edit 2: It worked! Thanks so much!
ztmj96 said:
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Click to expand...
Click to collapse
Your PC is recognizing your phone? If not maybe you shall update your drivers first. My S6 is the same model number as yours and it does appears in the Emergency Recovery list.
Another solution could be trying to flash using another version of Odin; I saw a similar problem on another forum and it was solved using Odin 3.10 to reflash the stock firmware.
Also remember that you can't downgrade your firmware once that you are on 5.1.1, no 5.02 or so allowed.
ztmj96 said:
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Click to expand...
Click to collapse
By the sounds of it you're able to boot into twrp? If so then simply boot into twrp, connect to your computer and copy a flashable rom to your phone and install it using twrp instead of odin
1qazwsx4 said:
By the sounds of it you're able to boot into twrp? If so then simply boot into twrp, connect to your computer and copy a flashable rom to your phone and install it using twrp instead of odin
Click to expand...
Click to collapse
How could I transfer the flashable ROM to the phone when I can't have it boot up to connect to my computer?
Gallitho said:
Your PC is recognizing your phone? If not maybe you shall update your drivers first. My S6 is the same model number as yours and it does appears in the Emergency Recovery list.
Another solution could be trying to flash using another version of Odin; I saw a similar problem on another forum and it was solved using Odin 3.10 to reflash the stock firmware.
Also remember that you can't downgrade your firmware once that you are on 5.1.1, no 5.02 or so allowed.
Click to expand...
Click to collapse
Since you're using the same model as mine, what are you running on your S6 right now? Are you able to root and flash a custom ROM like XtrestroLite onto Android 5.1.1?
Can you guys help me check if this post has the correct steps or is it missing anything like bootloader and root?
reddit.com/r/GalaxyS6/comments/39wwf6/should_i_install_xtrestolite_rom/cs7b7yq
ztmj96 said:
Since you're using the same model as mine, what are you running on your S6 right now? Are you able to root and flash a custom ROM like XtrestroLite onto Android 5.1.1?
Click to expand...
Click to collapse
Actually yeah. Earlier tonight I flashed XtreStoLite over stock 5.1.1, but I must confess it wasn't as easy as I thought, mainly because I didn't followed the steps in the right way and I ended up having to root my phone through installing UniKernel, which is pre-rooted and that did the trick for me, because I got stuck in the Samsung logo right after I tried to flash with CF-AutoRoot, needless to say I obviously couldn't root with that method and had to reflash stock 5.1.1 firmware to unbrick my phone, install UniKernel, and after that I was able to enter my phone config, uncheck the reactivation block under Find My Mobile settings (which was the reason for me to get stuck at the S-logo) and then flash through Odin XtreStoLite deodexed and Xposed FW too, so I can tell you for sure that SM-G920I can run XSL like a charm.
Gallitho said:
Actually yeah. Earlier tonight I flashed XtreStoLite over stock 5.1.1, but I must confess it wasn't as easy as I thought, mainly because I didn't followed the steps in the right way and I ended up having to root my phone through installing UniKernel, which is pre-rooted and that did the trick for me, because I got stuck in the Samsung logo right after I tried to flash with CF-AutoRoot, needless to say I obviously couldn't root with that method and had to reflash stock 5.1.1 firmware to unbrick my phone, install UniKernel, and after that I was able to enter my phone config, uncheck the reactivation block under Find My Mobile settings (which was the reason for me to get stuck at the S-logo) and then flash through Odin XtreStoLite deodexed and Xposed FW too, so I can tell you for sure that SM-G920I can run XSL like a charm.
Click to expand...
Click to collapse
1. So what is the correct order?
2. Did you have to manually unlock bootloader?
3. And is it a must to install uniKernel in order to root the device?
I have no idea how to proceed now.
This requires a lot more effort than I thought :fingers-crossed:
1. The correct order apparently WAS to flash 5.1.1 bootloader and modem over 5.0.2, then root, then TWRP, then flash XtreStoLite, or at least that was what I understood from Edgar's guide (as you can tell, I hurried myself too much and was to excited to flash XLS, so I didn't read properly).
Since I (and I think you did too) installed stock 5.1.1 first, there was no way to autoroot nor ping-pong root the device, that was the reason I got stuck in the Samsung logo screen after trying to autoroot, so I had to reflash stock 5.1.1 to regain access to the device settings/Find My Mobile as I explained before, after that I flashed UniKernel and that did the trick, no other steps were required to achieve root access beyond this point.
2. I didn't had to, but your carrier may have locked yours. My device is a SM-G920I (as yours) from Telcel carrier, so I can tell for sure.
3. There are several others way to root devices running over 5.0.2, but according to my personal research there aren't much options on 5.1.1 other than flash a pre-rooted kernel, but UniKernel isn't the only pre-rooted kernel, so you can choose whichever you like the most.
If I were you the first thing I'd try, as I said earlier, would be to switch to another Odin version or another firmware (as long as it is 5.1.1) and if that don't do the trick, then I'd update drivers and try via Smart Switch again.
Gallitho said:
1. The correct order apparently WAS to flash 5.1.1 bootloader and modem over 5.0.2, then root, then TWRP, then flash XtreStoLite, or at least that was what I understood from Edgar's guide (as you can tell, I hurried myself too much and was to excited to flash XLS, so I didn't read properly).
Since I (and I think you did too) installed stock 5.1.1 first, there was no way to autoroot nor ping-pong root the device, that was the reason I got stuck in the Samsung logo screen after trying to autoroot, so I had to reflash stock 5.1.1 to regain access to the device settings/Find My Mobile as I explained before, after that I flashed UniKernel and that did the trick, no other steps were required to achieve root access beyond this point.
2. I didn't had to, but your carrier may have locked yours. My device is a SM-G920I (as yours) from Telcel carrier, so I can tell for sure.
3. There are several others way to root devices running over 5.0.2, but according to my personal research there aren't much options on 5.1.1 other than flash a pre-rooted kernel, but UniKernel isn't the only pre-rooted kernel, so you can choose whichever you like the most.
If I were you the first thing I'd try, as I said earlier, would be to switch to another Odin version or another firmware (as long as it is 5.1.1) and if that don't do the trick, then I'd update drivers and try via Smart Switch again.
Click to expand...
Click to collapse
What did you use to root? May I ask for the link? I just tried flashing CF AutoRoot and now I think it's bricked again. (RECOVERY IS NOT SEANDROID ENFORCING) I'm thinking it might be due to incompatibility because I got it from here (https://autoroot.chainfire.eu/#odin) and the Android version states 5.0.2.
ztmj96 said:
What did you use to root? May I ask for the link? I just tried flashing CF AutoRoot and now I think it's bricked again. (RECOVERY IS NOT SEANDROID ENFORCING) I'm thinking it might be due to incompatibility because I got it from here (https://autoroot.chainfire.eu/#odin) and the Android version states 5.0.2.
Click to expand...
Click to collapse
Yep, that was the exact moment where mine got stuck too, as I stated before at that time I had to reflash stock firmware. The trouble is caused by CF-Autoroot, it won't work at all when you're on 5.1.1 (at least with SM-G920I) and if you try to root using this method, you'll get stuck with the message "RECOVERY IS NOT SEANDROID ENFORCING". You'll have to reflash to stock too, I'm affraid...
Flash UniKernel via Odin once you're on 5.1.1 stock again and see the magic happen. Once you have root access, gained by this kernel, you can install TWRP and flash XtreStoLite or any other rom you may want. Here is the direct link to the post: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
Hope you get lucky.
Gallitho said:
Yep, that was the exact moment where mine got stuck too, as I stated before at that time I had to reflash stock firmware. The trouble is caused by CF-Autoroot, it won't work at all when you're on 5.1.1 (at least with SM-G920I) and if you try to root using this method, you'll get stuck with the message "RECOVERY IS NOT SEANDROID ENFORCING". You'll have to reflash to stock too, I'm affraid...
Flash UniKernel via Odin once you're on 5.1.1 stock again and see the magic happen. Once you have root access, gained by this kernel, you can install TWRP and flash XtreStoLite or any other rom you may want. Here is the direct link to the post: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
Hope you get lucky.
Click to expand...
Click to collapse
I just did that before you suggested it and it worked! I was so elated! I love you bro (no homo). Our situations are identical. Now I have XtrestroLite running on the S6! Thank you so much!
Simply put:
1. Update bootloader and modem
2. Install TWRP without root via Odin
3. Install UniKernel via TWRP
4. Install ROMs!
ztmj96 said:
I just did that before you suggested it and it worked! I was so elated! I love you bro (no homo). Our situations are identical. Now I have XtrestroLite running on the S6! Thank you so much!
Simply put:
1. Update bootloader and modem
2. Install TWRP without root via Odin
3. Install UniKernel via TWRP
4. Install ROMs!
Click to expand...
Click to collapse
Glad to read that, dude!
Yep, our situations are identical and also happened at the same time haha.
Now's time to enjoy! :good:

What is the most stable stock OS? Kitkat or Lollipop?

What is the most stable stock android version? Kitkat or Lollipop?
My phone is currently on NE9 and want to optimize my phone to be the best with what's out now, especially since development will be dwindling. It seems that Lollipop does not run too well (high battery usage?), according to what I see on the threads. Without any input, I would update to NK2 and then towelroot. However, would anyone recommend me updating to BOK3 or BPB1?
GoodLooks550 said:
What is the most stable stock android version? Kitkat or Lollipop?
My phone is currently on NE9 and want to optimize my phone to be the best with what's out now, especially since development will be dwindling. It seems that Lollipop does not run too well (high battery usage?), according to what I see on the threads. Without any input, I would update to NK2 and then towelroot. However, would anyone recommend me updating to BOK3 or BPB1?
Click to expand...
Click to collapse
They're both stable, but we do see a lot of complaints about lollipop battery life.
Try it for yourself. Just stick with jrkruse's stock lollipop images that don't update the bootloader past BOD5, or any ROM that specifically does not update the bootloader. Then you can easily downgrade back to kitkat if you decide you don't like it.
painiac said:
They're both stable, but we do see a lot of complaints about lollipop battery life.
Try it for yourself. Just stick with jrkruse's stock lollipop images that don't update the bootloader past BOD5, or any ROM that specifically does not update the bootloader. Then you can easily downgrade back to kitkat if you decide you don't like it.
Click to expand...
Click to collapse
Thanks, painiac! I used your guide to get up to date with the S5, btw--things are very different from what I remember in the S4 world.
Anyway, after rooting and installing safestrap, if i were to flash jrkruse’s BPB1 Rom (http://forum.xda-developers.com/verizon-galaxy-s5/development/vzwstock-based-tw-rom-3-4-16-t3329029), I would install the rom, safestrap fix, patch (optional), and BPB1_Firmware_No_Bootloaders.zip. Anything else to add?
This set up would allow me to go back to kit kat by installing a jrkruse kit kat rom and related firmware w/o bootloader?
GoodLooks550 said:
Thanks, painiac! I used your guide to get up to date with the S5, btw--things are very different from what I remember in the S4 world.
Click to expand...
Click to collapse
Glad I could be of service. I came here just a few months ago from an S3. Imagine my disgust and shock... That was actually the impetus for writing that guide, because there's so much to have to learn and I'd just finished researching the crap out of it all for myself in a short amount of time.
GoodLooks550 said:
Anyway, after rooting and installing safestrap, if i were to flash jrkruse’s BPB1 Rom (http://forum.xda-developers.com/verizon-galaxy-s5/development/vzwstock-based-tw-rom-3-4-16-t3329029), I would install the rom, safestrap fix, patch (optional), and BPB1_Firmware_No_Bootloaders.zip. Anything else to add?
This set up would allow me to go back to kit kat by installing a jrkruse kit kat rom and related firmware w/o bootloader?
Click to expand...
Click to collapse
Nothing else to add, I think you got it. That no bootloaders firmware file you selected is the important one.
jrkruse says you can still run kitkat ROMs even if you're stuck with Lollipop, but I haven't tried it yet. Staying with the BOD5 or earlier bootloader actually allows you to flash KitKat stock image files with Odin, which you cannot do without bricking if you've updated your bootloader to BOE1 or later. I like this because the KitKat root process is a lot less problematic than the new Lollipop root method; but more importantly, you can freely upgrade to Lollipop with BOD5 bootloader (modified) stock Odin images, and then you can freely downgrade with stock KitKat Odin images.
painiac said:
Glad I could be of service. I came here just a few months ago from an S3. Imagine my disgust and shock... That was actually the impetus for writing that guide, because there's so much to have to learn and I'd just finished researching the crap out of it all for myself in a short amount of time.
Click to expand...
Click to collapse
I was lucky to have my an S4 MDK (unlocked bl), so things were much simpler back then--had an S3, as well. In the process of getting my S5 running the way I wanted, the use of safestrap was completely new to me. Thankfully, some heavy browsing of the forums got me through. I did not use flashfire, which would have been something else to learn!
painiac said:
Nothing else to add, I think you got it. That no bootloaders firmware file you selected is the important one.
jrkruse says you can still run kitkat ROMs even if you're stuck with Lollipop, but I haven't tried it yet. Staying with the BOD5 or earlier bootloader actually allows you to flash KitKat stock image files with Odin, which you cannot do without bricking if you've updated your bootloader to BOE1 or later. I like this because the KitKat root process is a lot less problematic than the new Lollipop root method; but more importantly, you can freely upgrade to Lollipop with BOD5 bootloader (modified) stock Odin images, and then you can freely downgrade with stock KitKat Odin images.
Click to expand...
Click to collapse
Thank you--your replies and guide were gold in terms of figuring it all out.
For onlookers of this thread, once you get to lollipop, it's hard to go back to kitkat. A lot of the small details really add up to an improved user experience. Also, having an s7 edge, the PB1 build on the S5 has 90% of the same functionality of the S7e--excluding edge-related features, of course.
To summarize my upgrade experience:
Root from any kitkat rom: Flash the NCG kernel in odin (AP/PDA), reboot and root with towelroot apk, and then install and update supersu; and lastly re-flash the NE9 kernel.
Install Hashcode's version of Safestrap: Install busybox apk. Install safestrap apk (version 3.75). Make sure to use a microsd card for installation, as recommended.
Install PB1 rom: (source: http://forum.xda-developers.com/verizon-galaxy-s5/development/vzwstock-based-tw-rom-3-4-16-t3329029). Reboot into SS. Flash G900V_Fix Safestrap.zip. Reboot into SS. Flash:
VZW_BPB1_ODEX_DEODEX_V9.zip,
Extra_toggles.zip (optional),
BPB1_Firmware_No_Bootloaders.zip , and
G900V_PB1_Stock_KERNEL_SafeStrap-Flashable.zip.
Flash all in a single queue. Reboot into download mode and flash G900V_OD5_Bootloader.tar.md5 in odin. Reboot. Wait. (NOTE: for more customization, before installing rom, unzip rom. Edit the options.prop in text editor to your likeing. Rezip original contents with updated options.prop. Flash this zip as the rom file)
To get back into safestrap/recovery: Make sure hashcode's version of safestrap is installed. A lollipop safestrap will be installed--don't use it. Also, install NI2Flasher.apk (this flashes a kitkat kernel, which will allow you to get back into the kitkat safestrap). Reboot into safestrap. IMPORTANT: When complete with whatever is being done in SS, flash G900V_PB1_Stock_KERNEL_SafeStrap-Flashable.zip to get back into lollipop rom.
Install xpose modules: This allows the essential greenify app (HIGHLY RECOMMENDED) to run to maximum potential. Gather following files:
1. APK: Xposed Installer 3.0 alpha4 (comes with some roms)
2. Flash in SS: Framework: xposed-v75-sdk21-arm-arter97-snapdragon.zip
3. Flash in SS: Uninstaller: xposed-uninstaller-arter97.zip
Since the rom I installed did not come with xposed installed. I flashed the framework in SS (look above to properly access and leave SS). Reboot. Install the APK. Reboot. Highly recommend installing Wanam's modules for lollipop--tons of modifications.
Unbrick: Get into download mode and flash: Full Wipe G900V_Downgrade_to_NCG.tar . (This helped me a ton until I realized that safestrap for the S5 does not work with rom-slots. Use the stock slot to do all flashing)
I gathered all this information from various threads, and hope this helps (highly recommend reviewing painiac's guide before starting anything - http://forum.xda-developers.com/verizon-galaxy-s5/general/guide-painiacs-essential-guide-to-t3319848). I am no expert, but this is what worked for me--please correct me if I'm wrong at any step. I believe the way I set this up, I should be able to get back to a kitkat rom, if I ever wanted to (easiest way to do this would be to flash the unbrick file). I hope this can help at least one person, since I know I'm not the only person to recently get an S5 due to someone else in the family upgrading to the S7.
Need some guidance in setting up root and Rom on my s5. Never done this before on a Verizon phone so if anyone can help I'd appreciate it

Flash Stock Recovery without Stock Firmware?

Hi,
hopefully this doens't belong in the noob-thread, wasn't really sure where to put it, to be honest
So what I'd like to do is flash the Stock-Recovery without flashing the Stock Firmware. I already exctracted the recovery.img from a Stock-Firmware and turned it into a *.tar - file.
What I would do next ist put it in Odin (as AP) and flash it.
I'm just not sure if this is safe. The phone is running a custom kernel and a custom ROM.
In case you're curious: I sold the phone to a friend who likes the ROM (Super-Stock) etc. the way it is, but doesn't want any other custom-stuff (recoveries, root, whatever) on the phone, since it's still knox free.
I already told him as long as knox is 0x0 it's safe, but he insists on getting a as-stock-as-possible phone.
Thanks!
mT

Trying to get my phone back to stock

Hello,
I rooted my s5 way back when it first came out but I haven't upgraded the firmware at all. From what I remember I had trouble installing a custom recovery so the phone is only rooted. I would like to bring it up to the most current version of android. What's the easiest way to do that? I'm on baseband version G900PVPUIAND2.
Thanks in advance.
Edit: I found this https://forum.xda-developers.com/showthread.php?t=2742994 which had a link to the stock factory image but sammobile doesn't seem to be hosting it anymore. Is there another reliable place that I can get it? Or would just doing a factory reset of my phone make it so I can start taking OTA's again?
The latest stock firmware for G900V is Marshmallow QC1. You can download it here and use ODIN to flash it:
https://www.androidfilehost.com/?fid=457095661767155677
If you want to root it you can use CF-Autoroot in ODIN. This will trip Knox if not already tripped (but probably doesn't matter on an older phone like this).
https://download.chainfire.eu/408/CF-Root/CF-Auto-Root/CF-Auto-Root-kltespr-kltespr-smg900p.zip
If you want to install TWRP you can use ODIN again:
https://twrp.me/devices/samsunggalaxys5qualcomm.html
Good luck.

Categories

Resources