Database Users

How can I just root and not unlock

Is it possible to just root my phone?
if so how do i do it?
All the posts I have seen go into unlocking and then rooting

gjjh25 said:
Is it possible to just root my phone?
if so how do i do it?
All the posts I have seen go into unlocking and then rooting
Click to expand...
Click to collapse
you will need to unlock to flash custom zip, but u can relock after

gjjh25 said:
Is it possible to just root my phone?
if so how do i do it?
All the posts I have seen go into unlocking and then rooting
Click to expand...
Click to collapse
Question - why? What do you want to root your phone for if not to use the wonderful tools of root. Why do you think fully rooting your phone will harm something. Locked or unlocked bootloader is not going to affect your phone. Rooted stock rom with recovery will not make it act funny.... Sorry not putting you out there but just asking why? Feel free to ignore me if you must...
Edit: Sorry to answer your question like the post above said you can root and then lock it right back up if that is your preference

playya said:
Question - why? What do you want to root your phone for if not to use the wonderful tools of root. Why do you think fully rooting your phone will harm something. Locked or unlocked bootloader is not going to affect your phone. Rooted stock rom with recovery will not make it act funny.... Sorry not putting you out there but just asking why? Feel free to ignore me if you must...
Edit: Sorry to answer your question like the post above said you can root and then lock it right back up if that is your preference
Click to expand...
Click to collapse
I have come from an HTC Desire, which I rooted and had a custom rom (Cyganonmod) on and was very happy with it.
I am still not sure of what I would gain by doing the same with my Nexus 4 ?
any advice is much appreciated.
Is this new Cyganonmod installer the best way to go?

gjjh25 said:
I have come from an HTC Desire, which I rooted and had a custom rom (Cyganonmod) on and was very happy with it.
I am still not sure of what I would gain by doing the same with my Nexus 4 ?
any advice is much appreciated.
Is this new Cyganonmod installer the best way to go?
Click to expand...
Click to collapse
This phone is built for rooting and modding. You wont know what benefit you have until you either read up and see if the mods are ones you want or actually flash a rom. Sure try the CM installer but if you dont toolkits or just basic knowledge of android can get this phone roooted in minutes.
the CM rom on your HTC will give you the same benefits on your Nexus 4

playya said:
This phone is built for rooting and modding. You wont know what benefit you have until you either read up and see if the mods are ones you want or actually flash a rom. Sure try the CM installer but if you dont toolkits or just basic knowledge of android can get this phone roooted in minutes.
the CM rom on your HTC will give you the same benefits on your Nexus 4
Click to expand...
Click to collapse
Thanks, what do you recommend for the easiest way to unlock and root then?

gjjh25 said:
Thanks, what do you recommend for the easiest way to unlock and root then?
Click to expand...
Click to collapse
I used a toolkit but honestly you can unlock manually by just booting into bootloader mode. Go into development and try Wugs Toolkit.... Rooting the phone is easy and all methods are relatively the same.
I do not see anything wrong with giving CM a try as well

gjjh25 said:
Is it possible to just root my phone?
if so how do i do it?
All the posts I have seen go into unlocking and then rooting
Click to expand...
Click to collapse
I recommend you to stick to your original plan, its your phone, do what you like, you don't need to flash custom roms if you don't want to. I am using stock kernel and stock KitKat right now and the performance is excellent.
Follow these instructions to unlock bootloader, install latest kitkat factory image, install custom TWRP recovery, and root. http://forum.xda-developers.com/showthread.php?t=2010312
The links to fastboot package and driver required is in my signature.
Link to download factory image: https://developers.google.com/android/nexus/images
Link for latest TWRP: TWRP recovery
Link for latest SuperSU package: SuperSU package
After you do all that, in bootloader menu, you can flash back the stock recovery (recovery.img), which is location in the "image-occam-******.zip" of the factory image. (fastboot flash recovery recovery.img)
Then lock your bootloader by "fastboot oem lock". You can also use BootUnlocker to lock and unlock your bootloader on the fly while in the phone, without losing your data, since everytime you do fastboot oem unlock, it will wipe the entire device.
By using stock rom, stock recovery, stock kernel and temporarily unroot (SuperSU) or hide root (SuperSU paid version), it allows you to receive future OTA updates from Google. If you want to modify your phones more while staying with stock, read up on Xposed Framework and its module Gravity Box, which is not yet compatible with Android 4.4 but will be eventually.
Just remember if you don't have custom recovery, once something goes wrong and your phone can't boot, its very hard to save the data inside. Once you have custom recovery like TWRP, you can make a backup of your stock image (which also backup your stock kernel) and try out other custom roms and easily go back to stock, then you can flash stock recovery again to receive OTA updates.

Thanks for advice everyone.
I rooted and unlocked with Wugfresh over the weekend. A lot easier than I thought it would be

[Q] Do I have to unroot 4.3 to get the OTA?

I have a rooted (no CWM changed) and unlocked Nexus 4 with JB 4.3.
I did not get the OTA yet and I wondered if it is because the phone is rooted. In addition, I read some problems with people who tried to update to 4.4 with rooted phones and are getting infinite bootloops.
Do I have to unroot my 4.3 for getting the OTA and achieving a successful installation?
Thank you all on advance

gosku26 said:
I have a rooted (no CWM changed) and unlocked Nexus 4 with JB 4.3.
I did not get the OTA yet and I wondered if it is because the phone is rooted. In addition, I read some problems with people who tried to update to 4.4 with rooted phones and are getting infinite bootloops.
Do I have to unroot my 4.3 for getting the OTA and achieving a successful installation?
Thank you all on advance
Click to expand...
Click to collapse
Why do you need OTA update when you can get the stock ROM in flashable zip file? All features are remain the same for stock ROM. Search and download it in the Development sections.

gosku26 said:
I have a rooted (no CWM changed) and unlocked Nexus 4 with JB 4.3.
I did not get the OTA yet and I wondered if it is because the phone is rooted. In addition, I read some problems with people who tried to update to 4.4 with rooted phones and are getting infinite bootloops.
Do I have to unroot my 4.3 for getting the OTA and achieving a successful installation?
Thank you all on advance
Click to expand...
Click to collapse
I am rooted and received the OTA notification yesterday. You 'SHOULD' be able to install if ALL you did was root. However, if you applied any mods that made changes to the system, the OTA will fail.
taodan said:
Why do you need OTA update when you can get the stock ROM in flashable zip file? All features are remain the same for stock ROM. Search and download it in the Development sections.
Click to expand...
Click to collapse
This is your best bet if you want to run 4.4. You'll need to install a custom recovery to flash the zip files. All the files and instructions are here:
http://forum.xda-developers.com/showthread.php?t=2527806

gbarayah said:
I am rooted and received the OTA notification yesterday. You 'SHOULD' be able to install if ALL you did was root. However, if you applied any mods that made changes to the system, the OTA will fail.
This is your best bet if you want to run 4.4. You'll need to install a custom recovery to flash the zip files. All the files and instructions are here:
http://forum.xda-developers.com/showthread.php?t=2527806
Click to expand...
Click to collapse
Will flashing the stock 4.4 wipe my data, or it is like getting the OTA, that I keep my settings...?

gosku26 said:
Will flashing the stock 4.4 wipe my data, or it is like getting the OTA, that I keep my settings...?
Click to expand...
Click to collapse
Did you read the linked post?
First step after installing custom recovery is to wipe data/factory reset, so yes, you will lose your settings.

taodan said:
Why do you need OTA update when you can get the stock ROM in flashable zip file? All features are remain the same for stock ROM. Search and download it in the Development sections.
Click to expand...
Click to collapse
I would like to keep my settings if it's possible.

gbarayah said:
Did you read the linked post?
First step after installing custom recovery is to wipe data/factory reset, so yes, you will lose your settings.
Click to expand...
Click to collapse
What I would like is to update to kitkat without losing my data.
I have the bootloader unlocked and the phone rooted, but when I go to recovery mode I get "No command" screen (is that normal?).
I was thinking of getting the phone unrooted, then update through the OTA, then root it again, just for making sure I don't break anything, but the "No command" screen does not look very good...
On the other hand, Would I lose my data if I "unroot" the phone?

gosku26 said:
What I would like is to update to kitkat without losing my data.
I have the bootloader unlocked and the phone rooted, but when I go to recovery mode I get "No command" screen (is that normal?).
I was thinking of getting the phone unrooted, then update through the OTA, then root it again, just for making sure I don't break anything, but the "No command" screen does not look very good...
On the other hand, Would I lose my data if I "unroot" the phone?
Click to expand...
Click to collapse
To unroot, all you need to do is go into SuperSu, disable root, uninstall the app and then reboot the phone.
If all you have done is root the phone, and didn't modify anything else, then the OTA update 'SHOULD' install without a problem.
You can go to Android Police and download the OTA files and flash them via ADB, or you can just wait for the OTA to be pushed to your device.
If you decide to do it the manual way, there is one additional step you must take to ensure to keep your data I believe.

gbarayah said:
To unroot, all you need to do is go into SuperSu, disable root, uninstall the app and then reboot the phone.
If all you have done is root the phone, and didn't modify anything else, then the OTA update 'SHOULD' install without a problem.
You can go to Android Police and download the OTA files and flash them via ADB, or you can just wait for the OTA to be pushed to your device.
If you decide to do it the manual way, there is one additional step you must take to ensure to keep your data I believe.
Click to expand...
Click to collapse
Thank you for your help gbarayah, I really appreciate it.
One last thing: I'm not pretty sure the only thing I modified was the rooting. I did not install any zip to modify my stock version, but there is something weird. I will explain:
At first I had 4.2.2, then I rooted and installed CWM. When 4.3 was released I got the OTA update correctly but I lost the root, so I rooted it again, this time without CWM.
Is the "No command" screen what is supposed to appear when I go to the recovery mode from fastboot menu? Or I would get a default recovery mode program?
If everything is right I will unroot for getting the OTA, but if not, I'm afraid I will have to flash CWM and the stock version, loosing my settings...
EDIT: Ok, I've just realized to get into stock system recovery I have to press VolUp and Power buttons once I'm in the 'No Command' screen, so I'm pretty sure I don't have problems installing the OTA update. Thank You!!!

gosku26 said:
Thank you for your help gbarayah, I really appreciate it.
One last thing: I'm not pretty sure the only thing I modified was the rooting. I did not install any zip to modify my stock version, but there is something weird. I will explain:
At first I had 4.2.2, then I rooted and installed CWM. When 4.3 was released I got the OTA update correctly but I lost the root, so I rooted it again, this time without CWM.
Is the "No command" screen what is supposed to appear when I go to the recovery mode from fastboot menu? Or I would get a default recovery mode program?
If everything is right I will unroot for getting the OTA, but if not, I'm afraid I will have to flash CWM and the stock version, loosing my settings...
EDIT: Ok, I've just realized to get into stock system recovery I have to press VolUp and Power buttons once I'm in the 'No Command' screen, so I'm pretty sure I don't have problems installing the OTA update. Thank You!!!
Click to expand...
Click to collapse
Glad I could help. In the future, as long as you don't modify the system by flashing any modifications, you should be able to get the OTA update to install. Root doesn't affect this, and if you're worried about it, you can always uninstall it.
I opted to update using the stock zip files that were posted above and it worked just fine for me.

2 questions kit kat

am i sol if i'mr rooted on the att g2 and have stock recovery?? also i'm on scotts clean rom and i don't see the option to update the phone........

paniro187 said:
am i sol if i'mr rooted on the att g2 and have stock recovery?? also i'm on scotts clean rom and i don't see the option to update the phone........
Click to expand...
Click to collapse
You'll probably be better off if you wait for a flashable zip to be available for your phone. With people are having stability issues and the risk of losing root, there's should be no rush to update yet. I'd suggest just flashing TWRP and making backups at this point. Try FreeGee on the play store. If you really want the KitKat experience, try out some of the ROMs already available - they are getting more stable every week.

paniro187 said:
am i sol if i'mr rooted on the att g2 and have stock recovery?? also i'm on scotts clean rom and i don't see the option to update the phone........
Click to expand...
Click to collapse
You are going to have to revert to stock, either D80010d or D80010o software package.
This is how I did it and remained rooted, although you will loose root in the first step but you get it right back.
Revert to stock software package D80010d using LG Flash Tools. (see the thread on this in this forum or check youtube for directions)
You can skip this step if you revert to the D80010o software package instead of the D80010d package.
Revert to stock software package D80010o using LG Flash Tools. (see the thread on this in this forum or check youtube for directions)
Once you have the D80010o installed, you need to root using the ioroot22 package. (search for ioroot22 on this forum. Some use ioroot23)
Once you are rooted, you need to contact AT&T through chat and ask them to push the D80010q or the "q" update to you.
Install the "q" update and check that you kept root.
Pull the D80020c KitKat update off of the AT&T server (though wifi) and install it.
Check for root again.
You are done. Reverting to stock will reflash the phone so you will loose everything on it so make sure you have backups of the important files. You will also loose the custom recovery TWRP if you have it installed and you will not be able to reinstall it as there is no way as of now to exploit the KITKAT software for a custom recovery.

T-Mobile FOG->FOJ Root

Hey guys,
I just rooted yesterday (G900T..FOG) using the TrapKernel method and everything is working just fine. Today I got a prompt for a new security update (FOJ). I haven't installed it yet and was curious -- if I do, will that remove my root? I'm assuming yes. Say I do install it -- is there anything I can do to get back my root aside from downgrading and re-applying TrapKernel?
Secondly, would I be able to flash a rooted FOJ ROM over the top of my FOG and still keep my root or will the update from J to G ? What steps would I need to do to accomplish this other than find the ROM and flash & wipe cache/davlik. Would I be able to dirty flash this or would a full wipe be required?
Last question (for now), if I choose to flash a CM ROM like Fusion would that keep my root as well? Again, I'm pretty sure the answer is yes I just don't want to make bad things happen that could be avoided.

1. if you take the OTA, root will be lost. You will have to downgrade, root, then upgrade using a prerooted rom to get it back.
2. Prerooted stock ROMs are the way to go. Just download Muniz_ri's prerooted stock OJ4 rom and flash it, you'll update to OJ4 and keep root.
http://forum.xda-developers.com/tmobile-galaxy-s5/development/how-to-update-to-g900tof6-5-1-1-pc-t3141404
Straight from that page:
- No need to wipe, the ROM will perform a factory data reset during the flash. Backup your User Data prior to flashing.
Click to expand...
Click to collapse
The ROM will wipe itself, you'll need to back up your stuff before the update.
3. The vast majority of custom ROMs are prerooted. Cyanogen based ones require you to enable root in the developer settings, FYI

Help!!! I have read too much!! S5 root and rom issues!

Hello all! I am newly signed up but i have been lurking in here for quite a while now. I am like that I usually try not to post and just figure out what I need to do by research and trial and error! But lately I think i may have too much research. I have spent the last week looking up and trying to figure out what I need to do to get what I want lol.
I have a Verizon SM-G900V which has been rooted with towel root, using the flash back to NCG method. I have installed SuperSU, Flashfire, and, BusyBox.
I want to upgrade my OS to the newest version,(5.1 Lollipop I believe?) while retaining root and allowing me to wi-fi tether. What I am not sure about is how to go about this properly. I was about to install Safestrap but I am not sure it is compatible with my build which somehow magically changed to NE when I looked at my About Phone in Settings. I am actually not even sure I need Safestrap either because I have read many conflicting tutorials and info in the past week of research. I am totally new to Safestrap and have never used a custom rom before. I have however rooted my S5 and gotten it to tether fine but then I made sure never to OTA update. Recently was forced to factory restore because if what I assume where Touchwiz problems(The problems have been gone since I reset) and now I would like to see if I can upgrade my OS .
Any help would be awesome and some points in the right direction much appreciated.

SafeStrap is a little inconvenient to use in Lollipop, but it's a great safety net to keep in place. It allows you to take a snapshot of your system and restore it later. If you lack this safety net and something goes wrong with your OS, you have no choice but to start from scratch.
All you have to do to use SafeStrap with Lollipop: flash a KitKat kernel (you can do this with the NL1 flasher app) from the phone while it's running Lollipop, reboot into SafeStrap, and do what you have to do. You then must re-flash a "safestrap-flashable" Lollipop kernel from within SafeStrap before you leave it, or your operating system won't be able to boot.
As for upgrading, see this thread and links within it: http://forum.xda-developers.com/verizon-galaxy-s5/help/help-upgrading-rooted-nk7-verizon-s5-t3302438
Your firmware version is different but it's still KitKat, so all of the same advice applies.

So I would definitely have to flash back to NCG in order to install safestrap right? because I am NE right now

Mrephunk said:
So I would definitely have to flash back to NCG in order to install safestrap right? because I am NE right now
Click to expand...
Click to collapse
Have you try this? you will have root on the latest factory firmware and able to install Safestrap.
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370

buhohitr said:
Have you try this? you will have root on the latest factory firmware and able to install Safestrap.
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
Click to expand...
Click to collapse
I just want to be clear. I should go through all the steps listed in that thread to achieve what I want? Even tho I am on a 4.4.2 build and not a 5.0?

Mrephunk said:
I just want to be clear. I should go through all the steps listed in that thread to achieve what I want? Even tho I am on a 4.4.2 build and not a 5.0?
Click to expand...
Click to collapse
That would work, as it involves flashing a BOK3 factory image and then rooting it.
You could do that, or you could just do the "keep root" method, which I had linked to in the thread I sent you to for explanation. http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784

painiac said:
That would work, as it involves flashing a BOK3 factory image and then rooting it.
You could do that, or you could just do the "keep root" method, which I had linked to in the thread I sent you to for explanation. http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
Click to expand...
Click to collapse
So the method you are linking above would be the better route to go, correct? Because the other method would update my bootloader to BOK3 which wont let me downgrade to NCG if I want to easy root again, right?
Sorry for all the questions here I just wanna make sure I get it right.

Mrephunk said:
So the method you are linking above would be the better route to go, correct? Because the other method would update my bootloader to BOK3 which wont let me downgrade to NCG if I want to easy root again, right?
Sorry for all the questions here I just wanna make sure I get it right.
Click to expand...
Click to collapse
Both root methods will work for you. The advantage of the "Keep Root" method I linked to is that you would still be able to downgrade later. As long as you don't flash anything with a BOE or newer bootloader, you can downgrade. So BOD is safe, BOE1, BOG5, and BOK3 can not be downgraded.

painiac said:
Both root methods will work for you. The advantage of the "Keep Root" method I linked to is that you would still be able to downgrade later. As long as you don't flash anything with a BOE or newer bootloader, you can downgrade. So BOD is safe, BOE1, BOG5, and BOK3 can not be downgraded.
Click to expand...
Click to collapse
OK so I am gonna go with your linked method. I dont wanna get stuck with one of those bootloaders. I should still be able to use safestrap with your method right? And tho I have never done it before I was entertaining the idea of flashing a custom ROM. That should still be possible with your method, correct?

Mrephunk said:
OK so I am gonna go with your linked method. I dont wanna get stuck with one of those bootloaders. I should still be able to use safestrap with your method right? And tho I have never done it before I was entertaining the idea of flashing a custom ROM. That should still be possible with your method, correct?
Click to expand...
Click to collapse
You can use SafeStrap with either method. But when you're on Lollipop, you must flash a kitkat kernel to boot into safestrap, then you must re-flash your lollipop kernel BEFORE leaving SafeStrap or you won't be able to boot into Lollipop. It's not as complicated as it sounds.

painiac said:
You can use SafeStrap with either method. But when you're on Lollipop, you must flash a kitkat kernel to boot into safestrap, then you must re-flash your lollipop kernel BEFORE leaving SafeStrap or you won't be able to boot into Lollipop. It's not as complicated as it sounds.
Click to expand...
Click to collapse
Yea I know, all of this sounds complicated but I understand it lol. But would I still be able to use a custom ROM using your method, I dont see why I couldnt, I just want to make sure I am ok?

Mrephunk said:
Yea I know, all of this sounds complicated but I understand it lol. But would I still be able to use a custom ROM using your method, I dont see why I couldnt, I just want to make sure I am ok?
Click to expand...
Click to collapse
Yes. You can use any TouchWiz-based ROM, all of which can be found in the "Verizon Galaxy S 5 Android Development" section of the forum, and no other section.
ROMs can be flashed using SafeStrap or with Flashfire.

painiac said:
Yes. You can use any TouchWiz-based ROM, all of which can be found in the "Verizon Galaxy S 5 Android Development" section of the forum, and no other section.
ROMs can be flashed using SafeStrap or with Flashfire.
Click to expand...
Click to collapse
Im just barely familiar with SafeStrap, and have never ever used FlashFire. Which of the 2 would you say is better to use?

I also wanted to thank you for all this help and answering my constant questions. Thank you very much!

Mrephunk said:
Im just barely familiar with SafeStrap, and have never ever used FlashFire. Which of the 2 would you say is better to use?
Click to expand...
Click to collapse
I have a slight preference for SafeStrap because I am accustomed to using custom recovery environments on previous phones (ClockworkMod Recovery, and later TWRP). SafeStrap is a modified TWRP environment, customized to work within the limitations imposed by the Verizon S5's locked bootloader.
FlashFire can do nearly everything that SafeStrap can do, the difference being is that it functions like an app. It's also more convenient to flash zips if you're on lollipop, because you don't have to **** around with flashing different kernels to boot into it, you just open the app, select the zip, and flash it. The downside to this is that if your OS is completely screwed up and won't boot, you can't access FlashFire.
But if that happens and you have SafeStrap recovery environment installed, you can flash a kitkat kernel with Odin and boot into SafeStrap to restore your nandroid backup, then flash a lollipop kernel and boot into your now-working phone.
For those reasons, I find it advantageous to use both.
---------- Post added at 08:18 AM ---------- Previous post was at 08:18 AM ----------
Mrephunk said:
I also wanted to thank you for all this help and answering my constant questions. Thank you very much!
Click to expand...
Click to collapse
You're quite welcome

painiac said:
I have a slight preference for SafeStrap because I am accustomed to using custom recovery environments on previous phones (ClockworkMod Recovery, and later TWRP). SafeStrap is a modified TWRP environment, customized to work within the limitations imposed by the Verizon S5's locked bootloader.
FlashFire can do nearly everything that SafeStrap can do, the difference being is that it functions like an app. It's also more convenient to flash zips if you're on lollipop, because you don't have to **** around with flashing different kernels to boot into it, you just open the app, select the zip, and flash it. The downside to this is that if your OS is completely screwed up and won't boot, you can't access FlashFire.
But if that happens and you have SafeStrap recovery environment installed, you can flash a kitkat kernel with Odin and boot into SafeStrap to restore your nandroid backup, then flash a lollipop kernel and boot into your now-working phone.
For those reasons, I find it advantageous to use both.
---------- Post added at 08:18 AM ---------- Previous post was at 08:18 AM ----------
You're quite welcome
Click to expand...
Click to collapse
OK so both it is lol. I see in the link to the thread which has the keep root tutorial it has 2 extra files a tether file and a batch de-bloater. I understand what the tether is but what exactly is the de-bloater? Also how do I install them, cause I definitely want the tether? Also, I noticed that my phone has some gone to a NE9 kitkat build, I would have to reflash to NCG, reroot and then install safestrap correct?

Mrephunk said:
OK so both it is lol. I see in the link to the thread which has the keep root tutorial it has 2 extra files a tether file and a batch de-bloater. I understand what the tether is but what exactly is the de-bloater? Also how do I install them, cause I definitely want the tether? Also, I noticed that my phone has some gone to a NE9 kitkat build, I would have to reflash to NCG, reroot and then install safestrap correct?
Click to expand...
Click to collapse
The de-bloater is just a script that deletes unnecessary apps that came pre-installed on the phone. You use it by flashing the debloater zip in either SafeStrap or FlashFire. Personally, I prefer to use Titanium Backup to "freeze" the unwanted apps, because they can be easily reactivated if necessary. Once those apps are deleted by the debloater, you can't retrieve them. Probably everything in the script needs to die anyway, but if you actually like any of the extra stuff that came on your phone you'll want to avoid using that method.
The tether patch is installed the same way, by flashing it, but you only need it if you're staying with the stock OS. If you're installing a custom ROM, don't bother because they will have already implemented it.
If your phone says NE9 but it is rooted, don't worry about it. You'd only need to flash the NCG kernel if you have to use towelroot to regain root access. So just install SafeStrap and/or FlashFire.
Then do a nandroid backup in SafeStrap of your current setup. That way, if something goes catastrophically wrong with your Lollipop upgrade adventure you can, with a little work, get back to where you are now with all of your apps and settings intact.
Then flash the rooted Lollipop image in the "Keep Root" method thread.

painiac said:
The de-bloater is just a script that deletes unnecessary apps that came pre-installed on the phone. You use it by flashing the debloater zip in either SafeStrap or FlashFire. Personally, I prefer to use Titanium Backup to "freeze" the unwanted apps, because they can be easily reactivated if necessary. Once those apps are deleted by the debloater, you can't retrieve them. Probably everything in the script needs to die anyway, but if you actually like any of the extra stuff that came on your phone you'll want to avoid using that method.
The tether patch is installed the same way, by flashing it, but you only need it if you're staying with the stock OS. If you're installing a custom ROM, don't bother because they will have already implemented it.
If your phone says NE9 but it is rooted, don't worry about it. You'd only need to flash the NCG kernel if you have to use towelroot to regain root access. So just install SafeStrap and/or FlashFire.
Then do a nandroid backup in SafeStrap of your current setup. That way, if something goes catastrophically wrong with your Lollipop upgrade adventure you can, with a little work, get back to where you are now with all of your apps and settings intact.
Then flash the rooted Lollipop image in the "Keep Root" method thread.
Click to expand...
Click to collapse
Cool, awesome thank you. So if I am running lollipop, I would have to use Odin to flash a kitkat kernel if I wanted to access to safestrap, right? It would need to be a rooted kernel too, right? Also was wondering if you could point me in the direction of the proper kernels I need. I have seen so many different NCG and other build kernels I am not sure which I should DL.

Mrephunk said:
Cool, awesome thank you. So if I am running lollipop, I would have to use Odin to flash a kitkat kernel if I wanted to access to safestrap, right? It would need to be a rooted kernel too, right? Also was wondering if you could point me in the direction of the proper kernels I need. I have seen so many different NCG and other build kernels I am not sure which I should DL.
Click to expand...
Click to collapse
Yes, flash a KitKat kernel to get into SafeStrap from Lollipop. I don't think it matters which version.
NCG, NE9, NHA, NI2, and NK2 are all KitKat.
OA8, OC4, OD5, OE1, OG5, and OK3 are all Lollipop.
You can use the NI2flasher.apk (but I've seen reports that it doesn't always work), or you can flash it with Odin (which is a little less convenient, but does work well). You should keep an NCG kernel around for re-rooting in case you have to start over, and that one should work for booting into SafeStrap.
Flashing any "kernel only" file won't change your root status. Basically, the kernel is the layer that allows the hardware and the operating system (firmware and such) to communicate with each other. Root access lies entirely within the configuration of the operating system: flashing a kernel will not affect it, but flashing a different firmware will overwrite it.
KERNELS themselves are always safe to flash, but if the operating system can't use it that kernel it will simply get stuck early in the boot sequence. This is always reversible by flashing the proper kernel.
However, be very cautious about FIRMWARE zips, unless they specifically say they're safe for newer bootloaders. Firmware files also contain bootloaders, and flashing the wrong newer (BOE and up) bootloader will burn your bridge back to BOD5 and below, and if you're already on BOE or newer then flashing an older bootloader over it will brick your phone. Stick with jrkruse's "firmware only no bootloaders" files. Currently, his "BOK3 firmware with BOD5 bootloader" is the latest safe version: http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527. So, to be clear: Flashing an OE1 or newer bootloader trips a qfuse that makes it impossible to downgrade the bootloader.
For the KitKat kernels, the ones posted here work fine: http://forum.xda-developers.com/showthread.php?t=2784880
For the Lollipop kernels, stick with jrkruse's updated ones that he has in the second post of this thread: http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
I've found with previous phones that it is advantageous to download and keep such files as soon as I find them, because experience has taught me that they're typically only posted in one place and they tend to disappear as the posters later lose interest in that model.

painiac said:
Yes, flash a KitKat kernel to get into SafeStrap from Lollipop. I don't think it matters which version.
NCG, NE9, NHA, NI2, and NK2 are all KitKat.
OA8, OC4, OD5, OE1, OG5, and OK3 are all Lollipop.
You can use the NI2flasher.apk (but I've seen reports that it doesn't always work), or you can flash it with Odin (which is a little less convenient, but does work well). You should keep an NCG kernel around for re-rooting in case you have to start over, and that one should work for booting into SafeStrap.
Flashing any "kernel only" file won't change your root status. Basically, the kernel is the layer that allows the hardware and the operating system (firmware and such) to communicate with each other. Root access lies entirely within the configuration of the operating system: flashing a kernel will not affect it, but flashing a different firmware will overwrite it.
KERNELS themselves are always safe to flash, but if the operating system can't use it that kernel it will simply get stuck early in the boot sequence. This is always reversible by flashing the proper kernel.
However, be very cautious about FIRMWARE zips, unless they specifically say they're safe for newer bootloaders. Firmware files also contain bootloaders, and flashing the wrong newer (BOE and up) bootloader will burn your bridge back to BOD5 and below, and if you're already on BOE or newer then flashing an older bootloader over it will brick your phone. Stick with jrkruse's "firmware only no bootloaders" files. Currently, his "BOK3 firmware with BOD5 bootloader" is the latest safe version: http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527. So, to be clear: Flashing an OE1 or newer bootloader trips a qfuse that makes it impossible to downgrade the bootloader.
For the KitKat kernels, the ones posted here work fine: http://forum.xda-developers.com/showthread.php?t=2784880
For the Lollipop kernels, stick with jrkruse's updated ones that he has in the second post of this thread: http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
I've found with previous phones that it is advantageous to download and keep such files as soon as I find them, because experience has taught me that they're typically only posted in one place and they tend to disappear as the posters later lose interest in that model.
Click to expand...
Click to collapse
OK rooted phone all went well. Installed Tether patch and now when I connect to wifi it doesnt work. I get a DNS error message in my browser and play store wont work, basically nothing will work when I am connected to wifi. Any thoughts on what to do? Was thinking maybe of going to jkruse's custom rom but not sure if that will help. If I do go to that rom will I need to go back to Kitkat or can I just use a flashfire and flash as is?
Update: The DNS error I seem to have fixed, but my question still stands for the jkruse's ROM. Also is it better to use a custom ROM? I have never really used one, so I am curious.
Ohh and you have been so much help painiac I really appreciate you answering all my questions. I was really at a standstill for a while there. You are truly a helpful person and I thank you.