Related
For the Nexus 5, how can I install an OTA update without losing root?
I believe there are different ways to do this, Can some share what works? With or without a custom recovery installed. Thanks.
(For this who haven't heard, an update is rumored for 11/13, FWIW)
pseudoware said:
For the Nexus 5, how can I install an OTA update without losing root?
I believe there are different ways to do this, Can some share what works? With or without a custom recovery installed. Thanks.
(For this who haven't heard, an update is rumored for 11/13, FWIW)
Click to expand...
Click to collapse
Check if OTA Rootkeeper https://play.google.com/store/search?q=ota rootkeeper is 4.4 compatible or maybe a similar app. If it isn`t rerooting with CF Auto Root will take 2 minutes bro.
-Edit- enable root survival mode after installing a OTA if you use superSU in the superSU settings menu
.... i'm sorry, but i have to ask why bother with the OTA updates if one has a custom recovery installed? can almost bet money on someone having a flashable image here of the stock ROM within hours of one being released.
elementaldragon said:
.... i'm sorry, but i have to ask why bother with the OTA updates if one has a custom recovery installed? can almost bet money on someone having a flashable image here of the stock ROM within hours of one being released.
Click to expand...
Click to collapse
True, but some are still on the stock rom, recovery and kernel and only want root.
pseudoware said:
For the Nexus 5, how can I install an OTA update without losing root?
I believe there are different ways to do this, Can some share what works? With or without a custom recovery installed. Thanks.
(For this who haven't heard, an update is rumored for 11/13, FWIW)
Click to expand...
Click to collapse
Who cares when it's so easy to root.
Thanks for the replies. Which N5 sub-forum is the most likely place where someone would post the updated flashable stock image, when available?
pseudoware said:
Thanks for the replies. Which N5 sub-forum is the most likely place where someone would post the updated flashable stock image, when available?
Click to expand...
Click to collapse
Chuck this out in the general forum, it's stikied. http://forum.xda-developers.com/showthread.php?p=46290762
jd1639 said:
Who cares when it's so easy to root.
Click to expand...
Click to collapse
But wouldn't one lose their data if they used CF-Auto Root again?
When I did the process, it wiped my phone.
Or is it that once the bootloader is unlocked it never wipes the phone again? Meaning it's just a simple matter of running CF auto root after OTA update and nothing else will be changed?
Still have the doubt
I know this information has to be somewhere in this forum, but I have searched and haven't found it. The question is, if I install an update with TWRP, will I lose root as well? If so, is there a way to get it back without wiping everything?
I think the answer is in what the previous post says, that once the bootloader is unlocked, there is no forced wipe anymore. I'm not sure, though.
Actually, the only thing I want is to be able to update to stock unaltered ROMs without losing root (and without a full wipe, of course), I don't care if I have to flash it manually or if I have to install TWRP or if it's ok with OTAs.
Thanks.
Hi all,
I have searched the web, but haven't found an exact answer to my question.
I have a Nexus 5, currently on 4.4.2 (KOT49H). I am unlocked, rooted + Xposed and have TWRP. I want to update to 4.4.4 preferably OTA, officially. I would like to be able to use OTA updates from now on if possible.
Currently, if I disable Xposed, and use Suvival Mode in SuperSU and try to install the OTA update, TWRP intervenes and doesn't let me.
I would like to replace TWRP with the stock recovery so I can update OTA in the future. I don't want to wipe the phone to achieve this if possible. If this isn't possible, could someone step through how to update to 4.4.4 with TWRP installed — I'm on a mac also.
Flash the stock recovery image in fastboot
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Flash the stock recovery image in fastboot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Where can I find the stock recovery? Is that this: *w*w*w*.developers.google.com/android/nexus/images
providedbike said:
Where can I find the stock recovery? Is that this: *w*w*w*.developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Yes, extract the image and then the zip file
Sent from my Nexus 5 using XDA Free mobile app
OTA is the least compatible and hardest way to update. Why do you want to use this method? It's the worst option available to you.
rootSU said:
OTA is the least compatible and hardest way to update. Why do you want to use this method? It's the worst option available to you.
Click to expand...
Click to collapse
Because it would seem easier for me—AFAIK. Although this didn't work, this workflow sounds appealing to me every time an update comes out:
- Disable Xposed
- Enable Survival Mode in SuperSU
- Install OTA update
- Re-enable Xposed, done.
No USB, no computer, no terminal.
Is there another way to achieve this?
providedbike said:
Because it would seem easier for me—AFAIK. Although this didn't work, this workflow sounds appealing to me every time an update comes out:
- Disable Xposed
- Enable Survival Mode in SuperSU
- Install OTA update
- Re-enable Xposed, done.
No USB, no computer, no terminal.
Is there another way to achieve this?
Click to expand...
Click to collapse
Running a rooting rom without a custom recovery is dangerous IMHO.
Without having to lose custom recovery
1) Download latest rooted stock ROM
2) Flash
3) Enable Xposed
rootSU said:
Running a rooting rom without a custom recovery is dangerous IMHO.
Without having to lose custom recovery
1) Download latest rooted stock ROM
2) Flash
3) Enable Xposed
Click to expand...
Click to collapse
Does this apply for the stock rom? I'm rooted, but still stock...
providedbike said:
Does this apply for the stock rom? I'm rooted, but still stock...
Click to expand...
Click to collapse
Yes, whenever there is a new stock ROM, someone makes a rooted stock flashable zip of it. Also if you make any small changes to system, sometimes like adblocking, OTA will fail but flashable zip of rom will just override all that bs.
latest 4.4.4 rooted stock rom is in a thread which you can find i the resources section of the sticky-roll-up thread. You can get there via my signature.
That way, you can take a nandroid backup so if anything goes wrong after the update, you can do a full restore, where as with OTA you will not be able to with stock recovery.
rootSU said:
Yes, whenever there is a new stock ROM, someone makes a rooted stock flashable zip of it. Also if you make any small changes to system, sometimes like adblocking, OTA will fail but flashable zip of rom will just override all that bs.
latest 4.4.4 rooted stock rom is in a thread which you can find i the resources section of the sticky-roll-up thread. You can get there via my signature.
That way, you can take a nandroid backup so if anything goes wrong after the update, you can do a full restore, where as with OTA you will not be able to with stock recovery.
Click to expand...
Click to collapse
Ok great that's very helpful, thanks!
providedbike said:
Ok great that's very helpful, thanks!
Click to expand...
Click to collapse
No problem.
I just think that way is easier....I wouldn't want you putting extra work in, if you dont have to. It also gives you more freedom to work with mods in the future too, or kernels etc
rootSU said:
No problem.
I just think that way is easier....I wouldn't want you putting extra work in, if you dont have to. It also gives you more freedom to work with mods in the future too, or kernels etc
Click to expand...
Click to collapse
Yep it's all good. For some reason, I had this little fear of the fact it's an official stock rom, that's been "toyed" with. But of course that makes no sense really, considering I'm willing to install many third party apps and processes that could easily alter/mess my phone up.
Do the rooted stock roms get released fairly rapidly after the official one is released?
providedbike said:
Yep it's all good. For some reason, I had this little fear of the fact it's an official stock rom, that's been "toyed" with. But of course that makes no sense really, considering I'm willing to install many third party apps and processes that could easily alter/mess my phone up.
Do the rooted stock roms get released fairly rapidly after the official one is released?
Click to expand...
Click to collapse
Yeah. as soon as the factory image is released. Maybe a day or two. Which is before 99% of people even receive the OTA notification
rootSU said:
Yeah. as soon as the factory image is released. Maybe a day or two. Which is before 99% of people even receive the OTA notification
Click to expand...
Click to collapse
Perfect, thanks for clearing things up for me.
Just checking, I'll make a backup before I flash, but technically, will all my data still be there if all goes to plan?
providedbike said:
Perfect, thanks for clearing things up for me.
Just checking, I'll make a backup before I flash, but technically, will all my data still be there if all goes to plan?
Click to expand...
Click to collapse
Yep. the /data partition is not touched. Just /system and /boot (ROM and Kernel)
rootSU said:
Yep. the /data partition is not touched. Just /system and /boot (ROM and Kernel)
Click to expand...
Click to collapse
Great I'll do it tonight
hi !
few month ago i rooted my nexus5 and installed a custom rom (pure nexus), everything was OK. but today i tried to install the last version of "pure nexus", so i downloaded the zip file, pushed it on the device, launched a flash zip with nexus root toolkit (everything was ok on the screen) but then it restart, and get stuck during the boot (4 small circle rotating...)
maybe i've done something wrong? how can i fix it?
(sorry i'm a noob !)
thanks!
nel0 said:
hi !
few month ago i rooted my nexus5 and installed a custom rom (pure nexus), everything was OK. but today i tried to install the last version of "pure nexus", so i downloaded the zip file, pushed it on the device, launched a flash zip with nexus root toolkit (everything was ok on the screen) but then it restart, and get stuck during the boot (4 small circle rotating...)
maybe i've done something wrong? how can i fix it?
(sorry i'm a noob !)
thanks!
Click to expand...
Click to collapse
Hi!
Congratulations, this is your first bootloop. Nothing to worry about. I guess your problem is due to the fact that you were coming from a lollipop based custom rom. Before you install a marshmallow based custom rom you need to install the marshmallow factory image first. If you're using the nexus root toolkit you can always click on the magic "flash stock - unroot" button. This is the easiest way for you.
My suggestion is to flash the factory image manually with ADB. In this way you'll know the basics of modding and it will be very useful for you in future. If you want you can follow this guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
vorinc said:
Hi!
Congratulations, this is your first bootloop. Nothing to worry about. I guess your problem is due to the fact that you were coming from a lollipop based custom rom. Before you install a marshmallow based custom rom you need to install the marshmallow factory image first. If you're using the nexus root toolkit you can always click on the magic "flash stock - unroot" button. This is the easiest way for you.
My suggestion is to flash the factory image manually with ADB. In this way you'll know the basics of modding and it will be very useful for you in future. If you want you can follow this guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
thanks for your answer!
alright, after installing a marshmallow factory image, everything was OK \0/
so i was wondering : is it possible to "update" a custom rom without wiping everything? :/ (is that what people call a dirty flash?)
thanks again for your help
nel0 said:
is it possible to "update" a custom rom without wiping everything? :/ (is that what people call a dirty flash?)
Click to expand...
Click to collapse
Yes, that's what "dirty flash" means. It is possible as long as the update doesn't concern an android version. An example is your case: lollipop-->marshmallow.
In facts custom roms (differently from factory images) do not provide boot.img in their zips; they assume you already have installed in your device. The lack of the correct boot.img caused your bootloop
vorinc said:
Yes, that's what "dirty flash" means. It is possible as long as the update doesn't concern an android version. An example is your case: lollipop-->marshmallow.
In facts custom roms (differently from factory images) do not provide boot.img in their zips; they assume you already have installed in your device. The lack of the correct boot.img caused your bootloop
Click to expand...
Click to collapse
oh, ok, understood. Thanks for the precision !
The stock ROM has a feature called verity, which ensures that the system partition is not modified. It uses a cryptographic signature to verify each sector on the partition. If any sector is modified, it is treated as corrupt.
In other words, any changes to the system partition will render it unbootable. This includes mounting /system read-write in recovery, even once.
In order to modify your system partition or recover from accidentally mounting your system partition read-write, you must download and flash the correct boot image using tuliptool.
You can find stock boot images with verity removed here:
US model, version 7.1.1 b12
md5=71428e4957763858f47bc9540e848d5e
US model, version 7.1.1 b14
md5=c6a67411e81f27d798eea035ddf4261e
EU model, version 7.1.1 b09
md5=ba210d332d3527b81f652dd0d2ce962e
i tried to see what would happen if i adb sideload supersu and my results came out that the went to zte screen and went into a bootloop didnt boot up but i have root priv in twrp....hmm. so i re-edl boot to after that i was able to boot back in to my android without root or supersu and twrp went back to normal aswell i was in the mood to test thankfully i was able to fix what ever had any issues
What would we need to provide for you to make one for v1.0.0B06?
I can make one for any firmware version. I just need the following:
* any relevant regional or model info.
* firmware version (including android version).
* the backup boot image, eg. from tuliptool.
parawizard said:
What would we need to provide for you to make one for v1.0.0B06?
Click to expand...
Click to collapse
So if I were to want to stay on the current ZTE rom (for now) would I need to flash this in order to root or currently root is only supported on the incomplete rom you are working on?
Depends how you root. I don't run stock so someone else should answer with details.
fallen00sniper said:
So if I were to want to stay on the current ZTE rom (for now) would I need to flash this in order to root or currently root is only supported on the incomplete rom you are working on?
Click to expand...
Click to collapse
tdm said:
Depends how you root. I don't run stock so someone else should answer with details.
Click to expand...
Click to collapse
i'm not a fan of the stock image, i do like to keep features which the stock seems devoid other than atmos which used to be hit or miss lol
i am sure someone out there likes the stock look, i used nova launcher and made things smaller, neater and tried to make it look a little better.
Done some experiments with SuperSU 2.82 (unsuccessfully, got bootloop).
In other words, any changes to the system partition will render it unbootable. This includes mounting /system read-write in recovery, even once.
Click to expand...
Click to collapse
And was able restore phone to work only with this EU boot.
Thanks, for making and publishing it!
Hi tdm, my 7 mini is USA hardware version but with European 6.0.1 firmware (build number ZTE B2017G V1.0.0B12). I tried to go back to USA Nougat firmware but unsuccessfully. Basically my phone was turned into P852A11 from P852A12. Do I need a new boot image with verity removed so that I can flash USA firmware? If I have to use Tuliptool, can you build a Windows32 version? Thanks in advance.
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
bao_gg said:
Hi tdm, my 7 mini is USA hardware version but with European 6.0.1 firmware (build number ZTE B2017G V1.0.0B12). I tried to go back to USA Nougat firmware but unsuccessfully. Basically my phone was turned into P852A11 from P852A12. Do I need a new boot image with verity removed so that I can flash USA firmware? If I have to use Tuliptool, can you build a Windows32 version? Thanks in advance.
Click to expand...
Click to collapse
tdm said:
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
Click to expand...
Click to collapse
Thank you tdm. You are awsome. I will provide you the checksums tomorrow.
Hey @tdm
Wanted to ask if you just removed the "verify" option in the fstab file to strip the dm verity checks? I might have read something like this before
Yes that's exactly it.
TheSSJ said:
Hey @tdm
Wanted to ask if you just removed the "verify" option in the fstab file to strip the dm verity checks? I might have read something like this before
Click to expand...
Click to collapse
I had finally gotten around to unlocking the bootloader and flashing TWRP.
Would flashing one of your custom ROMs without flashing the verity-free boot images affect anything?
I would suggest flashing the no verity boot just to avoid the headache
The stock boot images are only for running stock. Custom ROMs all include their own boot images.
JoeGatto said:
I had finally gotten around to unlocking the bootloader and flashing TWRP.
Would flashing one of your custom ROMs without flashing the verity-free boot images affect anything?
Click to expand...
Click to collapse
tdm said:
The stock boot images are only for running stock. Custom ROMs all include their own boot images.
Click to expand...
Click to collapse
Great. Looks like I'll be trying AOKP soon.
JoeGatto said:
Great. Looks like I'll be trying AOKP soon.
Click to expand...
Click to collapse
I've been running it for a couple of days and so far its great. No issues here
MrWhite0429 said:
I've been running it for a couple of days and so far its great. No issues here
Click to expand...
Click to collapse
You weren't kidding. Feels much faster than ZTE's ROM, and so refreshing as long as I've been looking at that MiFavor UI.
EDIT: Battery drain during standby.
tdm said:
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
Click to expand...
Click to collapse
Hi tdm, my adb can not recognize the mini. And in order to get the partition info, I need to "boot into twrp" as the instruction says. But my recovery is STOCK not TWRP.
Anyway, if you can make a win32 Tuliptool, I can unlock the bootloader and flash the TWRP in. After that, I can flash any firmware that I want. Is it correct?
Will be an apple to android convert when my zenfone comes. Been reading around to educate myself but have some questions that could use some insight.
1. Once you unlock the bootloader and root your phone, can you still get monthly/yearly or new android version updates in system updates in settings and update from there? If not, do you have to pretty much reset everything to factory defaults and then update it like that? And root all over again? Or is there any other way?
2. Will the phone be pretty much be "stock" after the factory reset?Working OTA updates and all? (Minus the unlocked bootloader)
3 Which up to date rooting method seems best? There's 2 methods that I can see but I can't tell which one is better.
a) https://forum.xda-developers.com/ze...uide-how-to-root-asus-zenfone-6-twrp-t3940168
b) https://forum.xda-developers.com/zenfone-6-2019/how-to/simple-guide-to-root-device-twrp-t3956784
4. Is TWRP needed?
Thanks!
midnight3ow said:
Will be an apple to android convert when my zenfone comes. Been reading around to educate myself but have some questions that could use some insight.
1. Once you unlock the bootloader and root your phone, can you still get monthly/yearly or new android version updates in system updates in settings and update from there? If not, do you have to pretty much reset everything to factory defaults and then update it like that? And root all over again? Or is there any other way?
2. Will the phone be pretty much be "stock" after the factory reset?Working OTA updates and all? (Minus the unlocked bootloader)
3 Which up to date rooting method seems best? There's 2 methods that I can see but I can't tell which one is better.
a) https://forum.xda-developers.com/ze...uide-how-to-root-asus-zenfone-6-twrp-t3940168
b) https://forum.xda-developers.com/zenfone-6-2019/how-to/simple-guide-to-root-device-twrp-t3956784
4. Is TWRP needed?
Thanks!
Click to expand...
Click to collapse
1) No, once unlocked, no more OTAS. You can flash the update manually, no wipe needed, but you also need to flash Root and custom recovery again (2 minutes extra, no big deal).
2) Stock, no OTAS
3) They are pretty much the same, but the easiest (and safest) way is just to get a custom recovery and then flash the Magisk Zip
4) For normal method yes, for the ones you posted in 3), no.
papete said:
1) No, once unlocked, no more OTAS. You can flash the update manually, no wipe needed, but you also need to flash Root and custom recovery again (2 minutes extra, no big deal).
2) Stock, no OTAS
3) They are pretty much the same, but the easiest (and safest) way is just to get a custom recovery and then flash the Magisk Zip
4) For normal method yes, for the ones you posted in 3), no.
Click to expand...
Click to collapse
Thank you for your reply, but I need some clarification on a couple things.
1. I suppose I'll figure out once I get the phone but I'm anxious and don't know when the phone will arrive but how do you flash the update manually? I understand having to flashing root again but what do you mean flashing custom recovery again?
2. Where do you get a hold of the update for the phone? Is updating manually pretty much the same as resetting your phone to factory settings?
3. I can't seem to find the method you mention that is the easiest and safest way to root. Could you kindly lead me to that guide??
midnight3ow said:
Thank you for your reply, but I need some clarification on a couple things.
1. I suppose I'll figure out once I get the phone but I'm anxious and don't know when the phone will arrive but how do you flash the update manually? I understand having to flashing root again but what do you mean flashing custom recovery again?
2. Where do you get a hold of the update for the phone? Is updating manually pretty much the same as resetting your phone to factory settings?
3. I can't seem to find the method you mention that is the easiest and safest way to root. Could you kindly lead me to that guide??
Click to expand...
Click to collapse
1) To flash manually you download the firmware from the Asus site, and use a recovery (stock or custom) to flash it. If you want root, you need a custom recovery to flash it, as stock recovery only flashes Asus Firmware. Whenever you flash a stock firmware, it "overwrites" the custom recovery with the stock recovery, so if you want/need a custom recovery, you need to flash it again. The same with root, stock flashed boot partition again, so you need to flash Magisk zip again so it can make the patch to boot to make root work.
2) I personally don't update that much, but you can check every once in a while https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/
You can update without factory reset, just flash the new firmware (+root if needed) and you are done, it is just like an OTA but done by yourself.
3) Follow this: https://forum.xda-developers.com/ze...covery-unofficial-twrp-recovery-asus-t3937844
papete said:
1) To flash manually you download the firmware from the Asus site, and use a recovery (stock or custom) to flash it. If you want root, you need a custom recovery to flash it, as stock recovery only flashes Asus Firmware. Whenever you flash a stock firmware, it "overwrites" the custom recovery with the stock recovery, so if you want/need a custom recovery, you need to flash it again. The same with root, stock flashed boot partition again, so you need to flash Magisk zip again so it can make the patch to boot to make root work.
2) I personally don't update that much, but you can check every once in a while https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/
You can update without factory reset, just flash the new firmware (+root if needed) and you are done, it is just like an OTA but done by yourself.
3) Follow this: https://forum.xda-developers.com/ze...covery-unofficial-twrp-recovery-asus-t3937844
Click to expand...
Click to collapse
I'm grateful for all your thoughtful and clear responses.
When do you normally decide to update?
Do you lose any data from updating security update/firmware or rooting and installing custom recovery?
Also, I've been looking through that link you posted, and also seen another thread about another newer "official" TWRP version? What's the difference?Which one should I use?
https://forum.xda-developers.com/ze...nt/tool-utility-twrp-3-3-1-0-teamwin-t3963876
midnight3ow said:
Will be an apple to android convert when my zenfone comes.
Click to expand...
Click to collapse
So ZF6 will be your first Android phone ever?
_jis_ said:
So ZF6 will be your first Android phone ever?
Click to expand...
Click to collapse
Yes it will be! Excited and anxious at the same time.
midnight3ow said:
Yes it will be! Excited and anxious at the same time.
Click to expand...
Click to collapse
Then please do yourself a favor and forgot about unlocking the bootloader and rooting your new phone.
Just learn how to use nearly stock Android with lightweight Android skin in its user-friendly and widely configurable form called ZenUI.
Trust me, there is no need for tinkering with root as an Android newbie when using ZF6.
_jis_ said:
Then please do yourself a favor and forgot about unlocking the bootloader and rooting your new phone.
Just learn how to use nearly stock Android with lightweight Android skin in its user-friendly and widely configurable form called ZenUI.
Trust me, there is no need for tinkering with root as an Android newbie when using ZF6.
Click to expand...
Click to collapse
I agree with this, unless you want to achieve something specific that can only be done rooted, stay completely stock.
papete said:
unless you want to achieve something specific that can only be done rooted
Click to expand...
Click to collapse
But this hypothetical condition is impossible because Android newbie cannot even achieve basic Android tasks which doesn't require root at all so why complicate his upcoming long journey of gaining experience and knowledge yet by the rooting his device from the very beginning?