Database Users

[Q] CMW success, SU fail :(

Hello, first time poster. I recently tried rooting my phone using CWM method. I'm running sph-l720 with software version vpaumf9 and android version 4.2.2. I installed CWM (this version SPH-L720 OUDHS Recovery) with odin with success. Then flashed SuperUser v.099. Everything went smooth until I opened up super user and tried to install binaries and it says "Install failed". I'm wondering if I didnt have the wrong beginning firmware and i needed to (but didnt) install that pre-kernel. I'm also wondering if I have to download the original firmware and have to flash to stock in order to "unroot" even though I didnt finish the SuperUser process, or is their a way to delete the super user app and try to install it again using the same CWM i have already on the phone. I hope this isn't confusing. I'm not a complete novice to rooting, but no expert. I rooted my galaxy s2 but went to Iphone for a while, but now I'm back and a little dissapointed with myself at this fail. Any suggestions? Do i have to go to stock first? Was I using the wrong files for my initial firm ware and need the pre kernel? Am I blabbering on? (yes) Thanks in advance.

jonraymond21 said:
Hello, first time poster. I recently tried rooting my phone using CWM method. I'm running sph-l720 with software version vpaumf9 and android version 4.2.2. I installed CWM (this version SPH-L720 OUDHS Recovery) with odin with success. Then flashed SuperUser v.099. Everything went smooth until I opened up super user and tried to install binaries and it says "Install failed". I'm wondering if I didnt have the wrong beginning firmware and i needed to (but didnt) install that pre-kernel. I'm also wondering if I have to download the original firmware and have to flash to stock in order to "unroot" even though I didnt finish the SuperUser process, or is their a way to delete the super user app and try to install it again using the same CWM i have already on the phone. I hope this isn't confusing. I'm not a complete novice to rooting, but no expert. I rooted my galaxy s2 but went to Iphone for a while, but now I'm back and a little dissapointed with myself at this fail. Any suggestions? Do i have to go to stock first? Was I using the wrong files for my initial firm ware and need the pre kernel? Am I blabbering on? (yes) Thanks in advance.
Click to expand...
Click to collapse
Grap CF-Autoroot from here
Follow the instructions here:
Boot back to phone. Open up SU and update binaries.
Then
Go to Playstore and download/install GooManager
Open GooManager and then press the 'menu' button (capicitive button next to Home Button) and choose to install recovery (I like TWRP).
Then let it do it's thing.
If you'd like a real easy way to get 'into recovery mode' from the phone I use the Quickboot app
Also make sure that if you are going to flash ANY ROMs you follow the instructions the developer suggests - many suggest specific recoveries be used

leaderbuilder said:
Grap CF-Autoroot from here
Follow the instructions here:
Boot back to phone. Open up SU and update binaries.
Then
Go to Playstore and download/install GooManager
Open GooManager and then press the 'menu' button (capicitive button next to Home Button) and choose to install recovery (I like TWRP).
Then let it do it's thing.
If you'd like a real easy way to get 'into recovery mode' from the phone I use the Quickboot app
Also make sure that if you are going to flash ANY ROMs you follow the instructions the developer suggests - many suggest specific recoveries be used
Click to expand...
Click to collapse
thank you! do i need to do anything before i do this? (Like using odin to revert back to stock?)
i ask because i already have CWM installed
I did the auto root, and open SuperSU and it doesnt ask to update binaries...does that mean it is already done. I didnt find the option in the settings.

jonraymond21 said:
thank you! do i need to do anything before i do this? (Like using odin to revert back to stock?)
i ask because i already have CWM installed
I did the auto root, and open SuperSU and it doesnt ask to update binaries...does that mean it is already done. I didnt find the option in the settings.
Click to expand...
Click to collapse
As long as your on some kind of TW/Stock based ROM you should be Okay.
However if you want to go back to straight (AND ROOTED) stock you can use one of rwhilco12's 'one-click' restores.
The one click downloads as a zip. decompress and then run the one -click. If you've never run a oneclick read here
It will give you a stock ROM, rooted, MF9 Modem, Stock recovedry, and Stock kernel. You'll then have to use GooManger method to get custom recovery.

leaderbuilder said:
As long as your on some kind of TW/Stock based ROM you should be Okay.
However if you want to go back to straight (AND ROOTED) stock you can use one of rwhilco12's 'one-click' restores.
The one click downloads as a zip. decompress and then run the one -click. If you've never run a oneclick read here
It will give you a stock ROM, rooted, MF9 Modem, Stock recovedry, and Stock kernel. You'll then have to use GooManger method to get custom recovery.
Click to expand...
Click to collapse
man thanks so much. so i definitly got super user access. I'm about to do the goo manager. since you suggested the twrp i think i'm going to try that. since i have CWM recovery installed, do u think that will create any issues if I go to install TWRP from goo manager

actually i googled and it seems that goo manager will seamlessly overwrite cwm. sorry for the questions before searching. appreciate the help. i almost didn't come on here, which would of lead me to reverting to stock, doing cwm again, then being upset that i needed twrm for most roms lmao. I owe u one. If u ever need to learn how to make bad decisions, just shoot me a pm. I got u covered.

No it will just replace it.
I actually (and many around here too) prefer TWRP 2.5.0.2.
You can download the zip for that here, boot to recovery you have now (CWM) and then install that. Or use Goo to install lates TWRP and boot to recovery and then install zip and choose the 2.5.02 you downloaded and then save to your sd card

scratch what i posted here. I ended up having to download ROMmanager and update CWM, then used CWM to install the zip you provided me. thanks so much man. Do you have a favorite stable ROM you recommend using TWRP. I value your advice

jonraymond21 said:
scratch what i posted here. I ended up having to download ROMmanager and update CWM, then used CWM to install the zip you provided me. thanks so much man. Do you have a favorite stable ROM you recommend using TWRP. I value your advice
Click to expand...
Click to collapse
Glad you got it.
As for ROMs you really have to try them out for yourself. There are some really great TW ROMs ; Sacs, negalite, triforce and others. For CM/AOSP there are a whole bunch to choose from. I mess with just about all of them. But my daily driver has to be one hundred percent working and reliable so for that I'm usually on a stock debloated and modified TW ROM. Take some time to read through the OPs of the devs and just as importantly through the follow up posts to see what works what doesn't ahs how to fix or get what you need.
Good luck
Sent from my SPH-L720 using XDA Premium 4 mobile app

leaderbuilder said:
Glad you got it.
As for ROMs you really have to try them out for yourself. There are some really great TW ROMs ; Sacs, negalite, triforce and others. For CM/AOSP there are a whole bunch to choose from. I mess with just about all of them. But my daily driver has to be one hundred percent working and reliable so for that I'm usually on a stock debloated and modified TW ROM. Take some time to read through the OPs of the devs and just as importantly through the follow up posts to see what works what doesn't ahs how to fix or get what you need.
Good luck
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try this Rom!
http://forum.xda-developers.com/showthread.php?t=2327692&page=43
works great!

[Q] OTA 4.4.3 update on rooted Nexus 4

i just got OTA update notification for 4.4.3 on my rooted ,stock,custom recovery Nexus 4 running on 4.4.2.
i use SuperSU,Xposed etc.
i have few questions hoping that someone will help me,
1. what happens if i update OTA normally , i lost data?root ? or there is possibility of softbrick while updating.
2. what is the best way of updating rooted phone with stock.
thanks in advance!!:good:

mrYogii said:
i just got OTA update notification for 4.4.3 on my rooted ,stock,custom recovery Nexus 4 running on 4.4.2.
i use SuperSU,Xposed etc.
i have few questions hoping that someone will help me,
1. what happens if i update OTA normally , i lost data?root ? or there is possibility of softbrick while updating.
2. what is the best way of updating rooted phone with stock.
thanks in advance!!:good:
Click to expand...
Click to collapse
Download and Install the OTA, you will loose your ROOT AND RECOVERY but not the data. That is the easiest way.

plz elaborate the process, i am new to it.
and one more question : what if i do OTA normally(over wifi).

with custom recovery and xposed OTA will fail and maybe soft brick.
please read here: http://forum.xda-developers.com/nexus-4/general/info-nexus-4-ota-help-desk-t2145848

carlosmg2 said:
with custom recovery and xposed OTA will fail and maybe soft brick.
please read here: http://forum.xda-developers.com/nexus-4/general/info-nexus-4-ota-help-desk-t2145848
Click to expand...
Click to collapse
thats what i am fearing , plz guide me for updating my rooted stock .

anyone in the same situation? OTA hit on device but not sure to update due to rooted and custom recovery, with Xposed and other modifications, plz help

mrYogii said:
anyone in the same situation? OTA hit on device but not sure to update due to rooted and custom recovery, with Xposed and other modifications, plz help
Click to expand...
Click to collapse
You have two (best I think) solutions:
1) Get back to stock and download OTA... before you do that, download Titanium Backup, backup your apks with it's cache so you won't have to set them up or start games from beggining... to backup messages etc you can use My Backup Pro, for calendar and contacts synchronize your Google account
2) Try to "get back to stock" as near as you can and try OTA... if it fails, it's not difficult to recover from softbrick

parkourz said:
You have two (best I think) solutions:
1) Get back to stock and download OTA... before you do that, download Titanium Backup, backup your apks with it's cache so you won't have to set them up or start games from beggining... to backup messages etc you can use My Backup Pro, for calendar and contacts synchronize your Google account
2) Try to "get back to stock" as near as you can and try OTA... if it fails, it's not difficult to recover from softbrick
Click to expand...
Click to collapse
i think 1 option i will try, what will be the process of
parkourz said:
Get back to stock
Click to expand...
Click to collapse
, if i am running stock but with custom recovery and xposed like modifications .

mrYogii said:
thats what i am fearing , plz guide me for updating my rooted stock .
Click to expand...
Click to collapse
in the link I posted OTA HELP DESK is all well explained.
I was in your same situation (stock + franco kernel+ TRWP recovery + Xposed) and i have just installed the OTA. This is what I did:
1- Uninstall Xposed (from inside the installer)
2- Uninstall Cerberus app (because in some cases it modifies system)
2- Flash stock kernel
3- Flash OTA in recovery
* It failed because Franco kernel modifies /system/lib/hw/power.msm8960.so --> so renamed power.msm8960.so.bak to power.msm8960.so
4- Flash OTA in recovery
5- Flash TRWP recovery
6- rooted

carlosmg2 said:
in the link I posted OTA HELP DESK is all well explained.
I was in your same situation (stock + franco kernel+ TRWP recovery + Xposed) and i have just installed the OTA. This is what I did:
1- Uninstall Xposed (from inside the installer)
2- Uninstall Cerberus app (because in some cases it modifies system)
2- Flash stock kernel
3- Flash OTA in recovery
* It failed because Franco kernel modifies /system/lib/hw/power.msm8960.so --> so renamed power.msm8960.so.bak to power.msm8960.so
4- Flash OTA in recovery
5- Flash TRWP recovery
6- rooted
Click to expand...
Click to collapse
i have stock kernel , i used xposed for ui tweaks and boot animation etc apart from that all other things are stock only, if i uninstall xposed m i good to go for OTA from wifi? or i have to flash it in recovery?if so then plz point me to 4.4.3 update download link.
thanks!

mrYogii said:
i have stock kernel , i used xposed for ui tweaks and boot animation etc apart from that all other things are stock only, if i uninstall xposed m i good to go for OTA from wifi? or i have to flash it in recovery?if so then plz point me to 4.4.3 update download link.
thanks!
Click to expand...
Click to collapse
read THIS http://forum.xda-developers.com/nexus-4/general/info-nexus-4-ota-help-desk-t2145848
I'm not sure, but your situation may need 'Scenario #2' (+ uninstalling Xposed)

can anyone else conform me on this:
i have stock kernel , i used xposed for ui tweaks and boot animation etc apart from that all other things are stock only.
suggested(http://forum.xda-developers.com/nexus-4/general/info-nexus-4-ota-help-desk-t2145848) :
Section B: Flashing in a custom recovery
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
i am not sure that xpose modifications come in this condition or not

mrYogii said:
can anyone else conform me on this:
i have stock kernel , i used xposed for ui tweaks and boot animation etc apart from that all other things are stock only.
suggested(http://forum.xda-developers.com/nexus-4/general/info-nexus-4-ota-help-desk-t2145848) :
Section B: Flashing in a custom recovery
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
i am not sure that xpose modifications come in this condition or not
Click to expand...
Click to collapse
yeah, you need to uninstall Xposed too (from within the app, not like uninstalling normal apps). Then you can reinstall and have all modules and config untouched.

carlosmg2 said:
yeah, you need to uninstall Xposed too (from within the app, not like uninstalling normal apps). Then you can reinstall and have all modules and config untouched.
Click to expand...
Click to collapse
i tried as you told, while installing OTA from zip i got following error:
/syaystem/priv-app/SystemUI.apk has unexpected contents.
installation aborted.
plz help

stock 4.4.2 nexus 4 SystemUI.apk
anyone has stock 4.4.2 nexus 4 SystemUI.apk? i have to revert back to install 4.4.3 update through recovery.

mrYogii said:
can anyone else conform me on this:
i have stock kernel , i used xposed for ui tweaks and boot animation etc apart from that all other things are stock only.
suggested(http://forum.xda-developers.com/nexus-4/general/info-nexus-4-ota-help-desk-t2145848) :
Section B: Flashing in a custom recovery
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
i am not sure that xpose modifications come in this condition or not
Click to expand...
Click to collapse
mrYogii said:
i tried as you told, while installing OTA from zip i got following error:
/syaystem/priv-app/SystemUI.apk has unexpected contents.
installation aborted.
plz help
Click to expand...
Click to collapse
Try this it'll work for you
http://forum.xda-developers.com/showthread.php?p=53176897
Sent from my Nexus 5 using XDA Free mobile app

Issue updating to Android 5.0

I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4

Your build.prop isn't standard, get the original one, or just use the factory image to update.

Rusty! said:
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Click to expand...
Click to collapse
what i need to install to correct his to the correct build.prop of 4.4.4?
ps. my last 4.4.4 was updated directly OTA..

Just download the 5.0 factory image, remove -w from the flash-all script and it will update you. Less dicking around that way.

inspiron41 said:
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Click to expand...
Click to collapse
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?

CBers said:
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
Click to expand...
Click to collapse
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app

inspiron41 said:
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?

CBers said:
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
Click to expand...
Click to collapse
Go to this website:
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It has detail instruction and jump down to step 3 regarding to -w
Sent from my Nexus 5 using XDA Free mobile app

I was having the same issue as the OP. So after reading this thread, I've performed the following:
Downloaded Android 5.0 factory image from: https://developers.google.com/android/nexus/images
Followed the instructions at this site, AND MADE SURE TO REMOVE '-w' AS INSTRUCTED, TO PRESERVE DATA: http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It was pretty easy. I've been waiting about 30 minutes looking at the boot graphic. Hope it turns out OK. But it is easier than playing with the OTA.

After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk

Darnell_Chat_TN said:
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?

[Lemmy] said:
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
Click to expand...
Click to collapse
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.

Darnell_Chat_TN said:
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Click to expand...
Click to collapse
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.

[Lemmy] said:
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
Click to expand...
Click to collapse
Why not just update using the 5.1 factory image? I run unlocked stock/rooted on my N10, and that's the method I always use to update. Would also do it this way on my N5 and now N6. Just fastboot flash all the images from the factory image manually (READ: EXCEPT USERDATA). You can also skip flashing the recovery if you run a custom recovery. However, for the sake of completion, I include flashing the stock recovery. Then I let it boot up normally. Then I'll boot back into the bootloader and flash TWRP and flash SuperSU. Updating this way is easier for me since I don't have to worry about the OTA failing due to customizations I may have made to the system (especially now with the new way Android updates after 5.0).

I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?

[Lemmy] said:
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
Click to expand...
Click to collapse
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.

charesa39 said:
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
Click to expand...
Click to collapse
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!

mj56gt said:
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
Click to expand...
Click to collapse
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.

charesa39 said:
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
Click to expand...
Click to collapse
Thanks a lot for the suggestions! Have a wonderful weekend...

Never mind

Installing Custom Roms On Newly Rooted Phones With BOK3,BOG5 and BOE1 Bootloader

Instruction for installing a custom rom using safestrap
1. Choose a Lollipop Rom from the Verizon Galaxy S 5 Android Development. OnlyLollipop 5.0 TW based roms will work
2. If you already got safestrap working skip to step 10. Otherwise install the apk's in this zip View attachment Safestrap_Apps.zip
3. Once all are installed Click On Busybox Grant Super User Access and click on install
4. Now open Lollipop Safestrap and click on Install SafeStrap Grant Super User Access
5. Click On Install Recovery Once Installed It will Say State: Installed
6. Click the Back Button to take you to Lollipop Safestrap Recovery Main Screen
7. Click On Recovery Reboot. Grant Super User Access.
8. On the next screen click FLASH then when dialog comes up asking CLICK HERE TO REBOOT TO SAFESTRAP click on that and your phone will reboot to safestrap. May take a few seconds for the Recovery Screen to come up
9 In Safestrap Under Boot Options LEAVE THIS ALONE Install everything to STOCK ROM SLOT
10. Now If you have not I would make a backup of your current Rom so if something happens you can get back to where you are at now.
11.. Click on Wipe You will see 3 options Advance Wipe, Format Data And Swipe To Factory Reset. If you dont see these and you see a dialog asking something about entering Yes just hit the back button
12 To Install a new rom click on Advance Wipe And Check Dalvick Cache,Data,Cache,System Then click Swipe To wipe.
13. Now Click The Home Button
14 Now Choose Install. Underneath the header on the next screen You will see a black box it will either say Storage: Micro SDcard or Storage: Internal Storage. You can switch between the 2 by clicking that black box
15 Locate the zip you want to install and click on it
16. In next screen Click Swipe To Confirm Flash and your install will begin
17. When Finished Do Not Click Reboot Now Or Reboot System. Click The Home Button. All Older Roms should run fine on latest BOK3 Firmware so if your on BOK3 firmware simply flash BOK3 kernel.
18. Once That is installed you can reboot to system
19. If you get some kind of warning about unauthorized software all you need to do is delete SecurityLogAgent folder from the system/app
20 Now If you want to select a different Firmware Zip you only need to do this once. It will remain that Firmware untill another Firmware Zip is flashed. If you flash A Firmware Zip There is no need to flash a Kernel Zip during the same installation.
21. Most Deodexed Lollipop Roms will Take Up to 10 Min to boot. If it seems longer than that simple pull the battery and restart phone.
22. If something goes wrong! If the rom fails to boot or bootloops you are not screwed if you flashed with safestrap.
23. To get back to safestrap from a bootloop. Pull the battery. Boot to download mode Power+Volume Down+Home
24. Plug into your computer.
24. Open Odin make sure phone is connect blue box saying comport whatever will be lit up. In the AP section locate the NI2_stock_kernel.tar.md5 and flash kernel.
25. When phone reboots watch screen and click on the Recovery Button when the SafeStrap Screen comes up. If you miss it pull the battery and try again.
26. Once in Safestrap you can restore a back up or what ever you need to do
Just a note. You can also use flashfire to flash rom. Flashfire is a great tool. Just know that if you flash a rom with flashfire and have safestrap installed you will loose your safestrap installation. So after you flash a rom with flashfire if you want to use safestrap you will have to reinstall it. If something goes wrong during the the install when flashing with flash fire you will not be able to get back to safestrap and your only method if your bootlooped is using odin and flashing full factory tar image and going through the root process again!

Install Kit Kat Roms On All Bootloaders
Edit: I updated the method and added new firmware zips ran into some hardware issues these fixed the problem
This method should work for All Bootloaders Without having to wipe data on Internal storage
Download This one NK2_Firmware_No_Bootloaders_V3.zip should work for all Kit Kat Roms. This is a 4.4.4 Version I tested it on 4.42 Version and it worked fine . If you want to use a differen versions, all Version listed below
Reboot To Safestrap Wipe cache, system, data, dalvik cache then flash above zip
Go back and Wipe cache, system, data
Install Kit Kat Rom
Reboot to system and go through setup.
Remember when using Kit Kat Roms there is no reason to flash kernel in safestrap as you are all ready running kit kat kernel. Also do not use Lollipop Safestrap on kit kat roms you can reach safestrap by simply rebooting rom and choosing safestrap recovery when dialog comes up
All Firmwares
NCG_Firmware_No_Bootloaders_V3.zip
NE9_Firmware_No_Bootloaders_V3.zip
NHA_Firmware_No_Bootloaders_V3.zip
NI2_Firmware_No_Bootloaders_V3.zip
NK2_Firmware_No_Bootloaders_V3.zip

can i use the Optimal Rom if i have BOK3?

coopmaster said:
can i use the Optimal Rom if i have BOK3?
Click to expand...
Click to collapse
Yes. I just added some instructions in OP that may be helpful

jrkruse said:
Yes. I just added some instructions in OP that may be helpful
Click to expand...
Click to collapse
Just a question so if i have BOK3 when i go to flash the firmware do i need to wait till that rom has a BOK3 firmware or can i flash any of them?

coopmaster said:
Just a question so if i have BOK3 when i go to flash the firmware do i need to wait till that rom has a BOK3 firmware or can i flash any of them?
Click to expand...
Click to collapse
. The BOK3 Firmware should be fine even on older roms. Just flash the rom and stay on the latest firmware. You may get a waring about unauthorized actions dialog warning just delete the SecurityLogAgent folder from the system/app folder, but all older roms should run fine on BOK3 firmware.

jrkruse said:
. The BOK3 Firmware should be fine even on older roms. Just flash the rom and stay on the latest firmware. You may get a waring about unauthorized actions dialog warning just delete the SecurityLogAgent folder from the system/app folder, but all older roms should run fine on BOK3 firmware.
Click to expand...
Click to collapse
sweet thank you.

Might be stupid question but I was wondering if Extreme Syndicate and Cyanogemod are compatible.

jrkruse said:
. The BOK3 Firmware should be fine even on older roms. Just flash the rom and stay on the latest firmware. You may get a waring about unauthorized actions dialog warning just delete the SecurityLogAgent folder from the system/app folder, but all older roms should run fine on BOK3 firmware.
Click to expand...
Click to collapse
Am I understanding you correctly that newer firmwares are backwards-compatible? Are you referring to only Lollipop ROMs, or does this also apply to older KitKat ROMs?
If I were to update past BOD, that does slam the door on downgrading to a KitKat bootloader as we have already discussed. I understood this to mean I wouldn't be able to use any KitKat ROMs.

painiac said:
Am I understanding you correctly that newer firmwares are backwards-compatible? Are you referring to only Lollipop ROMs, or does this also apply to older KitKat ROMs?
If I were to update past BOD, that does slam the door on downgrading to a KitKat bootloader as we have already discussed. I understood this to mean I wouldn't be able to use any KitKat ROMs.
Click to expand...
Click to collapse
You can get kitkat roms to boot just by flashing the rom the kernel and the NON_HLOS.bin but I dont know if your bootloaders will let the NON-HLOS.bin flash or not. You have to wipe data and internal storage also

Plasma ROM steer clear of, doesn't wanna play nice. However Optimal ROM works perfectly but hopefully the developer updates it to BOK3. Is anyone working on a debloat.bat for this firmware? or can someone?

DimitrieRetezatu said:
Might be stupid question but I was wondering if Extreme Syndicate and Cyanogemod are compatible.
Click to expand...
Click to collapse
Not sure about Extreme Syndicate. ROMs must be touchwiz based. No AOSP based ROMs, so Cyanogenmod is not compatible. You have to look for ROMs in the Verizon Galaxy S5 Android Development forum. Cannot flash anything in the Original Android Development forum. Also probably not any or possibly just a couple from the Unified Development forum.

landshark68 said:
Not sure about Extreme Syndicate. ROMs must be touchwiz based. No AOSP based ROMs, so Cyanogenmod is not compatible. You have to look for ROMs in the Verizon Galaxy S5 Android Development forum. Cannot flash anything in the Original Android Development forum. Also probably not any or possibly just a couple from the Unified Development forum.
Click to expand...
Click to collapse
Thanks for the response. Makes more sense when you put it like that. Hopefully people will see that the new root is available and update some ROMs!

secandRRe said:
Plasma ROM steer clear of, doesn't wanna play nice. However Optimal ROM works perfectly but hopefully the developer updates it to BOK3. Is anyone working on a debloat.bat for this firmware? or can someone?
Click to expand...
Click to collapse
There are several debloater zips I have made just check the OP on my rom threads

If you like a very debloated rom that is super fast and great on battery I recommend my BS Free Roms. @CVertigo1 made a new BOK3 version of my BS Free roms its only 800 mb in size thats half the size of normal roms. Check out his thread

Sticking to OptimalROM seems to be everything I need.

jrkruse said:
There are several debloater zips I have made just check the OP on my rom threads
Click to expand...
Click to collapse
I gave your zips a try on BOK3 with no luck?

secandRRe said:
I gave your zips a try on BOK3 with no luck?
Click to expand...
Click to collapse
You need to use the debloat script on a clean install of rom flash rom the flash debloat script. This way you haven't updated a bunch of apps

I'm tempted to try your ROMs I just like the S6 Keyboard on OptimalROM it's probably one of the best keyboards I have used.

My BOG5 BS Free Rom and BS Free Google Rom both have s6 keyboards

Safestrap Start Screen

I installed SafeStrap so I could install a custom ROM which I did (Goldeneye).
Now my start up time is very very long if I power off each time - first I get the Safestrap start screen which takes a while to get past, then I get the Samsung logo for what seems to be a very extended period of time (maybe thats related to something in the background)?
If I want to reduce my start up time (which I really would like to do - right now it takes a couple of minutes), can I just uninstall Safestrap?

Yes you can uninstall Safestrap, but it has to do with you not being on a NC1 bootloader. Its normal for i337s

Robert417919 said:
Yes you can uninstall Safestrap, but it has to do with you not being on a NC1 bootloader. Its normal for i337s
Click to expand...
Click to collapse
If I do have that bootloader can I uninstall without messing up root and my ROM usage?
Do I need it on there ONLY when I want to reflash things? Or do I need to keep it on at all times?

Yes you can uninstall it once you have your ROM all set. & Yes you will need it to flash zips and mods. I think you can use FlashZip if I am not mistaken to flash too, but I dont think it will work with LP ROMs because it requires you to flash a kernel back to boot.

Robert417919 said:
Yes you can uninstall it once you have your ROM all set. & Yes you will need it to flash zips and mods. I think you can use FlashZip if I am not mistaken to flash too, but I dont think it will work with LP ROMs because it requires you to flash a kernel back to boot.
Click to expand...
Click to collapse
So, is that mean, when I want install some apps from, for example Aroma Add-on, I need to flash kernel OC4 to normally boot ROM after install apps before I reboot the phone?