Anyone tried and confirmed working the old adb backup method that doesn't require root?
http://forum.xda-developers.com/showthread.php?t=1420351
Was hoping to use this method to backup before unlocking. I got into the usual problem of not wanting to unlock right away (in case issues etc.) then once I was comfortable with the unit too lazy to want to set up all up again from scratch....
Use helium. Backup each app individually. There are some apps that will Bork restore.
Sent from my Nexus 7 using XDA Premium HD app
bummer screw that for a joke then LOL
it will be awhile before I unlock as I'm waiting for the next OTA to deal with the multitouch/gps etc. (hopefully!) I'm hoping it includes some firmware fixes too that we may not be able to flash like a normal ROM.
wintermute000 said:
it will be awhile before I unlock as I'm waiting for the next OTA to deal with the multitouch/gps etc. (hopefully!) I'm hoping it includes some firmware fixes too that we may not be able to flash like a normal ROM.
Click to expand...
Click to collapse
Unlocking doesn't prevent you from getting the OTAs.
If you want root to be compatible with OTAs, see this post:
http://forum.xda-developers.com/showthread.php?p=44597339#post44597339
yeah I know that, I know I can reflash stock recovery and unroot etc. just too lazy to be bothered setting up all my apps losing saves etc. at this point short of mucking around with carbon. TBH if the multitouch issue is fixed or at least toned down there's not a lot of incentive to root for me aside from adblock.
I've got a hunch that the next OTA will involve firmware etc. so just reluctant to tinker until the stock base is 100%. Its not directly applicable as its a Nexus but in the past some other components e.g. HTC hboot, Moto (forgot the name) would get in the way of OTA if you unlocked the BL early.
wintermute000 said:
yeah I know that, I know I can reflash stock recovery and unroot etc.
Click to expand...
Click to collapse
My point is you don't need to unroot nor flash stock recovery (though it is safest to flash stock recovery)
The JSS15J OTA update will flash fine with root and twrp with just the small fix I referenced.
wintermute000 said:
I've got a hunch that the next OTA will involve firmware etc. so just reluctant to tinker until the stock base is 100%. Its not directly applicable as its a Nexus but in the past some other components e.g. HTC hboot, Moto (forgot the name) would get in the way of OTA if you unlocked the BL early.
Click to expand...
Click to collapse
JSS15J already included firmware updates, it updated aboot, sbl, tz, and rpm. Bootloader went from 3.05 to 3.14 and it flashed ok with root and twrp (though again, personally I suggest using stock recovery)
Also you don't need to install twrp persistently to root. I just boot into twrp one-time by using fastboot boot twrp.img to install the root files and leave stock recovery on the tablet.
With the one simple fix referenced above, you can have stock recovery, root, and be totally compatible with future OTAs, no need to revert anything. Of course after the OTA is successful, just re-run the SuperSU zip and the fix to set yourself up with root and await the next OTA.
On this nexus, you need to unlock even to do the official factory restore google published. The official images don't come with signatures.
To answer the question re adb bu, yes it works just fine.
Sent from my Nexus 7 using Tapatalk 4
Just like the title says, I'm requesting a stock 4.4.2 rooted backup from someone who has an unlocked bootloader, and as much as I read the forums I know that's several of you. Please help us achieve root on locked bootloaders still running 9.30.1... We'd all like to have the option of upgrading with root, so please give back to the community a little bit... Don't forget I was the first to post links to the KitKat OTAS for you all. This is highly frustrating for someone like me who used to be unlocked and then had to receive a replacement locked device. All you have to do is install safe strap and make a backup of your system for us... Safestrap will not replace your custom recovery but work alongside it. Also if anyone can post a kernel for us, that would be great as well. You can make a twrp backup of your rooted system and pull the kernel from that, but unfortunately safe strap doesn't back up the kernel so we would need both the kernel and the safestrap backup separately. We can get the baseband later on when the FXZ is released. I know the RAZR M baseband for 4.4.2 runs just fine on 9.30.1 so I'm I'm assuming we can run the old baseband with no issues. I've posted several requests for a safestrap backup on several threads the past couple of days to no avail. Please someone step up and get us that backup and that kernel. Here is a link to the safe strap APK. http://hosting.crackflasher.com/get...f/vanquish/safestrap/Safestrap-XT926-3.60.apk
zachariahpope said:
Just like the title says, I'm requesting a stock 4.4.2 rooted backup from someone who has an unlocked bootloader, and as much as I read the forums I know that's several of you. Please help us achieve root on locked bootloaders still running 9.30.1... We'd all like to have the option of upgrading with root, so please give back to the community a little bit... Don't forget I was the first to post links to the KitKat OTAS for you all. This is highly frustrating for someone like me who used to be unlocked and then had to receive a replacement locked device. All you have to do is install safe strap and make a backup of your system for us... Safestrap will not replace your custom recovery but work alongside it. Also if anyone can post a kernel for us, that would be great as well. You can make a twrp backup of your rooted system and pull the kernel from that, but unfortunately safe strap doesn't back up the kernel so we would need both the kernel and the safestrap backup separately. We can get the baseband later on when the FXZ is released. I know the RAZR M baseband for 4.4.2 runs just fine on 9.30.1 so I'm I'm assuming we can run the old baseband with no issues. I've posted several requests for a safestrap backup on several threads the past couple of days to no avail. Please someone step up and get us that backup and that kernel. Here is a link to the safe strap APK. http://hosting.crackflasher.com/get...f/vanquish/safestrap/Safestrap-XT926-3.60.apk
Click to expand...
Click to collapse
I think you should provide a "how-to" for those people who want to help with this issue, something like
"Step 1: Make sure you are on stock OTA or reflash FXZ"
"Step 2: Root your phone with the method described (link to the root method for unlocked xt926)"
"Step 3: Install Safestrap (link to Safestrap)"
"Step 4: Reboot into Safestrap recovery and make back up of a /system"
And please, all of the above is just an EXAMPLE, DO NOT FOLLOW THESE STEPS, wait for someone who is really respectable in the rooting scene, like SamuriHL or the OP, someone who knows what he needs from unlocked rooted stock and what he can do with that.
All I am saying, just provide a user-friendly how-to-do and you might have more dumps than you need ^^
Flayzor said:
I think you should provide a "how-to" for those people who want to help with this issue, something like
"Step 1: Make sure you are on stock OTA or reflash FXZ"
"Step 2: Root your phone with the method described (link to the root method for unlocked xt926)"
"Step 3: Install Safestrap (link to Safestrap)"
"Step 4: Reboot into Safestrap recovery and make back up of a /system"
And please, all of the above is just an EXAMPLE, DO NOT FOLLOW THESE STEPS, wait for someone who is really respectable in the rooting scene, like SamuriHL or the OP, someone who knows what he needs from unlocked rooted stock and what he can do with that.
All I am saying, just provide a user-friendly how-to-do and you might have more dumps than you need ^^
Click to expand...
Click to collapse
Um, First of all you do realize I AM the OP that you quoted... but you may have a point nonetheless.
1. Make sure your boot loader is unlocked and you're running a stock rooted 4.4.2 system.
2. Install the safestrap APK provided above.
3. Open the APK. Press Install Recovery. Reboot phone.
4. After boot logo, you should see a safe strap splash screen. Press the bottom left button to enter recovery.
5. Once in recovery, backup your current system to either internal or external storage. It will be placed in a TWRP/Backups folder
6. Upload the backup here to XDA for myself or Sammy @SamuriHL to disect & perform experiments on.
zachariahpope said:
Just like the title says, I'm requesting a stock 4.4.2 rooted backup from someone who has an unlocked bootloader, and as much as I read the forums I know that's several of you. Please help us achieve root on locked bootloaders still running 9.30.1... We'd all like to have the option of upgrading with root, so please give back to the community a little bit... Don't forget I was the first to post links to the KitKat OTAS for you all. This is highly frustrating for someone like me who used to be unlocked and then had to receive a replacement locked device. All you have to do is install safe strap and make a backup of your system for us... Safestrap will not replace your custom recovery but work alongside it. Also if anyone can post a kernel for us, that would be great as well. You can make a twrp backup of your rooted system and pull the kernel from that, but unfortunately safe strap doesn't back up the kernel so we would need both the kernel and the safestrap backup separately. We can get the baseband later on when the FXZ is released. I know the RAZR M baseband for 4.4.2 runs just fine on 9.30.1 so I'm I'm assuming we can run the old baseband with no issues. I've posted several requests for a safestrap backup on several threads the past couple of days to no avail. Please someone step up and get us that backup and that kernel.
Click to expand...
Click to collapse
Zach will you be the one working on getting the locked bootloader rooted, or are you just requesting the files that would help someone get the root working? If you will be working on it, "I'll be watching you with great interest"
There being no root for 4.4.2 is the only thing holding me back from upgrading. Thanks and good luck!!!
Safestrap is not working on 4.4.2, at least not on my HD
HarleyDood said:
Safestrap is not working on 4.4.2, at least not on my HD
Click to expand...
Click to collapse
Yeah, I was going to say, has it even been updated? I haven't tried it yet but I wouldn't expect it to work either.
HarleyDood said:
Safestrap is not working on 4.4.2, at least not on my HD
Click to expand...
Click to collapse
I thought I had stated this before, or maybe I was just thinking it? That's why I didn't respond, but now someone has definitely verified it and that's what I was thinking.
Safestrap, like CWM and TWRP, was compiled to run against the JB kernel, so I felt if CWM and TWRP didn't run, why would Safestrap?
And, I don't know if anyone is working on updating Safestrap since that dev community is very small compared to the dev community for unlocked bootloaders for the XT926.
i confirmed ss not working yesterday but didnt post it, sorry.
we are exploring other options now and will post progress, if any, as it becomes available.
I was perusing the Droid Razr HD area because I have a Razr HD with an unlocked bootloader I plan to put up for sell.
Before that though, what can I do to help you out?
I forget what Version of software it's running.
It does have TWRP flashed so I know it'can't take the OTA unless I remove the custom recovery and go back to stock.
Anyway, if there is something I can do PM me.
tech_head said:
I was perusing the Droid Razr HD area because I have a Razr HD with an unlocked bootloader I plan to put up for sell.
Before that though, what can I do to help you out?
I forget what Version of software it's running.
It does have TWRP flashed so I know it'can't take the OTA unless I remove the custom recovery and go back to stock.
Anyway, if there is something I can do PM me.
Click to expand...
Click to collapse
Enviado desde mi HTC Explorer A310e mediante Tapatalk
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.
Recently I rooted my G5 plus and it worked really well for me. I didn't use SuperSU, instead, have Magisk installed. Unfortunately, now my phone isn't updating. What should I do to unroot it without much problem and without losing any data on my phone? And will it update if I unroot it?
It's a little more complicated than that... to bad there isn't a guide to doing it here somewhere... Hmmm....
https://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175
acejavelin said:
It's a little more complicated than that... to bad there isn't a guide to doing it here somewhere... Hmmm....
https://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175
Click to expand...
Click to collapse
So like can't I simply unroot my phone and install the updates? Isn't there any easy way of uprooting?
dt.dragonborn said:
So like can't I simply unroot my phone and install the updates? Isn't there any easy way of uprooting?
Click to expand...
Click to collapse
Root is only part of the problem, TWRP is another big one.
OTA updates can only be installed on a purely stock device, the install script will check multiple things to verify the device is unmodified and in the correct state before applying, then it applies changes to specific files or partitions, they must be at a known starting condition before changes can be applied.
So, can you simply "unroot and install updates"? No, you must undo all changes to the device that are system related... Return the recovery, boot, and system partitions to their original state or any update will fail. Unrooting does not undo any changes, adds, or deletions you performed with root access, those actions are permanent.
Isn't there an easy way of unrooting? Sure, Magisk and SuperSU both have methods of removal, but that doesn't gain you what is needed to apply an OTA update.
I provided a link previously, that is what you need to do.
dt.dragonborn said:
Recently I rooted my G5 plus and it worked really well for me. I didn't use SuperSU, instead, have Magisk installed. Unfortunately, now my phone isn't updating. What should I do to unroot it without much problem and without losing any data on my phone? And will it update if I unroot it?
Click to expand...
Click to collapse
Which OTA(s) isn't installing?
Sent from my Moto G Plus (5th Gen) using XDA Labs
cdysthe said:
Which OTA(s) isn't installing?
Click to expand...
Click to collapse
I am not much of a tech guy but the update says
New Version-NPN25.1 37-67
Improved audio in Video Capture
Data traffic improvements
acejavelin said:
Root is only part of the problem, TWRP is another big one.
OTA updates can only be installed on a purely stock device, the install script will check multiple things to verify the device is unmodified and in the correct state before applying, then it applies changes to specific files or partitions, they must be at a known starting condition before changes can be applied.
So, can you simply "unroot and install updates"? No, you must undo all changes to the device that are system related... Return the recovery, boot, and system partitions to their original state or any update will fail. Unrooting does not undo any changes, adds, or deletions you performed with root access, those actions are permanent.
Isn't there an easy way of unrooting? Sure, Magisk and SuperSU both have methods of removal, but that doesn't gain you what is needed to apply an OTA update.
I provided a link previously, that is what you need to do.
Click to expand...
Click to collapse
Thank you for this. I unlocked the bootloader, and installed TWRP and Magisk to gain root. This worked fine. However, I decided I wanted to go back to complete stock yesterday. So I uninstalled Magisk and flashed stock firmware using ADB. My phone is now unrooted, has a locked bootloader, and is running stock firmware which is what I wanted. Once I get the phone to boot, almost everything functions normally. However, it seems as though I now do not have any recovery whatsoever (and I assume that's because I did not specifically replace TWRP with stock recovery). So when I boot my phone, it goes to the bootloader and stops. If I then hit "start" on the bootloader, the ROM loads up normally after that. f that were the only issue, I could live with it. But not being able to get to recovery is concerning. And I am not able to get OTAs at the moment.
So, I'll check the other thread you mentioned. I assume I will need to flash stock recovery in order to get where I need to be.
Thank you for the post!