So is there anyway to keep my recovery or root when I flash an ota update?
If there is no way. Then anyway to install cwm and root from just the phone?
I do my updates etc when I have down time and that's usually on lunch or when my laptop is not around so handling everything from the phone would be very nice.
Sent from my Nexus 5 using Tapatalk
rans0m00 said:
So is there anyway to keep my recovery or root when I flash an ota update?
If there is no way. Then anyway to install cwm and root from just the phone?
I do my updates etc when I have down time and that's usually on lunch or when my laptop is not around so handling everything from the phone would be very nice.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You will lose root when flashing an OTA, but it is just one extra step to flash the SuperSU (takes less than a minute) to regain root. I keep the SuperSU file on my phone and just flash it from there.
I use TWRP, and haven't lost my custom recovery while flashing 4.4.1 or 4.4.2 yet.
(I stay stock rooted - you can't safely take OTA if you aren't on the stock ROM)
jj14 said:
You will lose root when flashing an OTA, but it is just one extra step to flash the SuperSU (takes less than a minute) to regain root. I keep the SuperSU file on my phone and just flash it from there.
I use TWRP, and haven't lost my custom recovery while flashing 4.4.1 or 4.4.2 yet.
(I stay stock rooted - you can't safely take OTA if you aren't on the stock ROM)
Click to expand...
Click to collapse
I let it restart before I flashed root. And been using cwm just preference and its gone after the 4.4.1 flash and now the 4.4.2
Except root and recovery I am completely stock.
Sent from my Nexus 5 using Tapatalk
rans0m00 said:
I let it restart before I flashed root. And been using cwm just preference and its gone after the 4.4.1 flash and now the 4.4.2
Except root and recovery I am completely stock.
Click to expand...
Click to collapse
I haven't used CWM, so can't say. But with TWRP, I flashed the update, and let the phone start up fully. Then, when I saw that root was gone, I shut down and booted back into TWRP, and flashed SuperSU. and then, booted back up. TWRP is still there.
(I'm rooted, stock ROM with custom recovery as well)
I use TWRP also. I flash the OTA, then Flash the SuperSU and then I reboot. Have yet to lose root
So not really a way of keeping cwm or root... But this is how I did it without needing a computer with me.
Flashed updated in cwm... Then flashed root... Then reboot... Used ROM manager to reinstall cwm.... Everything is good to go.
Sent from my Nexus 5 using Tapatalk
Or do like I do wait a couple of hours for one of the great devs we have here to give us a fully working updated stock rom with su and busybox built in.
All you can ask for from a rooted stock rom.
Download the system images and use flashify to flash all the files you need.
Sent from my Nexus 5
rans0m00 said:
So is there anyway to keep my recovery or root when I flash an ota update?
If there is no way. Then anyway to install cwm and root from just the phone?
I do my updates etc when I have down time and that's usually on lunch or when my laptop is not around so handling everything from the phone would be very nice.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Get the pro version of SU by chainfire and check keep root
Valdeck said:
Get the pro version of SU by chainfire and check keep root
Click to expand...
Click to collapse
^^^^ This
Survival mode FTW
Have the pro version. Will check that but would still lose cwm.
Sent from my Nexus 5 using Tapatalk
Related
Hey guys, I've read a lot on updating after being rooted, but just need to confirm before I do mess up anything.
All I have done is Rooted Stock (I have TWRP on the phone), and have flashed volume mod, and also battery percent mod. (Other then that I am running Nova Launcher, Titanium Backup)
Guessing I need to flash the back to stock for volume and battery percent (Correct if I am wrong).
And then how exactly do I go about updating to 4.4.2 and preferably retaining root?
Sorry I know noob question, just making sure as I've always unrooted, and never had any mods when I have done updates in the past.
1) you have to flash back to stock system image since you modded your phone
2) once you either get the OTA or sideload it, you just flash cwm/twrp in fastboot and then flash the supersu.zip
thats all
so in other words go back and unroot completely, go completely back to stock, and redo everything from the beginning?
Just flash the 4.4.2 stock rooted rom in the dev section
sent from my HAMMERHEAD neXus
Or you can flash the Updated Super SU zip right?
Sent from my Nexus 5 using Tapatalk
AndroidRaven said:
so in other words go back and unroot completely, go completely back to stock, and redo everything from the beginning?
Click to expand...
Click to collapse
You are flashing back the stock ROM. If you want to keep data intact, flash only the boot.img, system.img
niv3d said:
Or you can flash the Updated Super SU zip right?
Click to expand...
Click to collapse
that won't help you get back to stock.
I guess I need a tutorial on what you guys are talking about because I still am not understanding..
Would flashing the rooted 4.4.2 work? And if so what do I need to do before I flash this?
How exactly do I go about only flashing only the boot.img and system.img?
Will I loose anything through this process?
Sent from my Nexus 5 using XDA Premium 4 mobile app
AndroidRaven said:
I guess I need a tutorial on what you guys are talking about because I still am not understanding..
Would flashing the rooted 4.4.2 work? And if so what do I need to do before I flash this?
How exactly do I go about only flashing only the boot.img and system.img?
Will I loose anything through this process?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Follow this guide --> http://forum.xda-developers.com/showthread.php?t=2523217
Best guide out there, with big thanks to El Daddy
AndroidRaven said:
I guess I need a tutorial on what you guys are talking about because I still am not understanding..
Would flashing the rooted 4.4.2 work? And if so what do I need to do before I flash this?
How exactly do I go about only flashing only the boot.img and system.img?
Will I loose anything through this process?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
One safe way to get the OTA, taking into account that you modded your phone, is:
i) flash system.img then flash stock recovery,
ii) once the OTA update is on your phone and you have accepted it (it installed itself) you are back to stock.
iii)flash your custom recovery and re-install your SuperSu to get back your root.
Good luck
I just got my m8 and want to s-off but I'm traveling and won't be able to figure that out until I'm back on my pc next week. The update keeps prompting me to take it. Is it safe to do so? Sorry if this was already answered trying to figure out the best way to browse with tapatalk.
I don't have root or anything yet...
Sent from my HTC6525LVW using Tapatalk
I used Firewater's method for permanent root, s-off and custom recovery. If I allow my phone to update will I mess things up or lose root?
Same boat here... s-off, permanent root, TWRP
The update to 1.55 downloaded but when I tried to let it install it just rebooted my phone into TWRP and that was it. Rebooted back to system and I'm still on the 1.12.605.11 software. Checking software update status shows "Result: Update Failed,410"
N00bs. Lol. You need a stock recovery to flash an OTA. Also, I am s-off and I had a flashback to a stock recovery to flash the OTA . Everything is still fine and then I flashed back to a custom recovery no problem
Sent from my HTC One M8
Totally a noob here, How do you flash to a stock recovery?
Sent from my HTC6525LVW using Tapatalk
You guys need the stock recovery in order to install the OTA. It won't work with a custom recovery, it'll just boot to the custom recovery and not do anything. You can install the OTA with s off and root but you still need the stock recovery. You install the stock recovery the same way as you did the custom. Adb -> flashboot flash recovery *path of recovery*.
http://www.megafileupload.com/en/file/520717/stockrecovery-img.html
There are also videos on YouTube on flashing recoveries to the m8 if you need more help.
Sent from my HTC6525LVW using Tapatalk
Justintoxicated said:
I just got my m8 and want to s-off but I'm traveling and won't be able to figure that out until I'm back on my pc next week. The update keeps prompting me to take it. Is it safe to do so? Sorry if this was already answered trying to figure out the best way to browse with tapatalk.
I don't have root or anything yet...
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
You can install the update, and when you have the chance you can s-off using the weaksauce/supersu/firewater method. I picked up a new M8 a couple nights ago and took the update, and afterwards did the temproot/firewater method and it worked just fine. Hope this helps.
I flashed stock recovery and tried the OTA and it failed twice. I can't seem to get it on my phone through any of the methods for some reason.
In order to install update, you need to have STOCK recovery and STOCK Rom....NOT debloated or with mods....STOCK.
Again, you need STOCK recovery using a STOCK Rom.
If you have modified the system in anyway, it WONT work until you put it back to STOCK.
Sent from my HTC6525LVW using xda app-developers app
^you can have bloatware frozen and it'll work, just can't be removed.
Sent from my HTC6525LVW
dadams312 said:
I flashed stock recovery and tried the OTA and it failed twice. I can't seem to get it on my phone through any of the methods for some reason.
Click to expand...
Click to collapse
z-man79 said:
Totally a noob here, How do you flash to a stock recovery?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
KnightDavid said:
Same boat here... s-off, permanent root, TWRP
The update to 1.55 downloaded but when I tried to let it install it just rebooted my phone into TWRP and that was it. Rebooted back to system and I'm still on the 1.12.605.11 software. Checking software update status shows "Result: Update Failed,410"
Click to expand...
Click to collapse
z-man79 said:
I used Firewater's method for permanent root, s-off and custom recovery. If I allow my phone to update will I mess things up or lose root?
Click to expand...
Click to collapse
No need to take ota. Ota us our enemy. Lol. The ota has been pulled an you can simply flash the firmware an that's half of the ota an then flash a stock Rom based off 1.55 or install the backup that was posted of a pure stock 1.55 Rom. After those 2 things you will have the full ota. New radios everything.. flashing a stock recovery taking ota flashing back is not needed.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Thanks guys it was annoying having that update keep popping up and no real computer to lookup info or soff. As for getting updates after roming the phone usually just wait for authors to incorporate the updates. But I did not realize you can't have two recoveries like you can on Motorola phones which is good to know.
Sent from my HTC6525LVW using Tapatalk
New to android here.
I rooted the device with WeakSauce and use Firewater for S-Off. I didn't flash any custom recoveries. I did freeze some apps with Titanium Backup. If I do the OTA, 1) will it work? and 2) will it remove my root and/or s-off?
NoFanboy said:
You guys need the stock recovery in order to install the OTA. It won't work with a custom recovery, it'll just boot to the custom recovery and not do anything. You can install the OTA with s off and root but you still need the stock recovery. You install the stock recovery the same way as you did the custom. Adb -> flashboot flash recovery *path of recovery*.
megafileupload.com/en/file/520717/stockrecovery-img.html
Click to expand...
Click to collapse
For clarification, after flashing the stockrecovery.img you posted and installing the update, there should be no problem flashing back to CWM recovery after the fact?
Thank you for your help and your time!
skivvies said:
For clarification, after flashing the stockrecovery.img you posted and installing the update, there should be no problem flashing back to CWM recovery after the fact?
Thank you for your help and your time!
Click to expand...
Click to collapse
Nope there will be no problem.
Sent from my HTC6525LVW using Tapatalk
richii0207 said:
In order to install update, you need to have STOCK recovery and STOCK Rom....NOT debloated or with mods....STOCK.
Again, you need STOCK recovery using a STOCK Rom.
If you have modified the system in anyway, it WONT work until you put it back to STOCK.
Sent from my HTC6525LVW using xda app-developers app
Click to expand...
Click to collapse
All your big words confuse me...will it work with custom rom's and recoveries?
I don't remember ever having to have stock recovery and stock rom for my old DNA to take an update. Normally devs would update their rom with the updates and all we had to do was fastboot flash the new radio.
NoFanboy said:
You guys need the stock recovery in order to install the OTA. It won't work with a custom recovery, it'll just boot to the custom recovery and not do anything. You can install the OTA with s off and root but you still need the stock recovery. You install the stock recovery the same way as you did the custom. Adb -> flashboot flash recovery *path of recovery*.
http://www.megafileupload.com/en/file/520717/stockrecovery-img.html
There are also videos on YouTube on flashing recoveries to the m8 if you need more help.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
So I flash the file you linked to, thank you but when I try to get into recovery I get a red triangle with an exclamation point in it. Seemed pretty straight forward.
sfreemanoh said:
All your big words confuse me...will it work with custom rom's and recoveries?
Click to expand...
Click to collapse
Lol, I had to. I just know someone is going to start a thread saying "update won't work, it just boots into twrp"
Sent from my HTC6525LVW using xda app-developers app
z-man79 said:
So I flash the file you linked to, thank you but when I try to get into recovery I get a red triangle with an exclamation point in it. Seemed pretty straight forward.
Click to expand...
Click to collapse
Hold the volume up button and pressed the power button to get to the recovery menu.
i am currently on 4.4.2 with root and xposed framework already uninstalled from within the app, philz recovery mode.
when i try to install the 4.4.3 update (about 92 MB) it gives me an error on a specific apk (cannot remember exactly which one).
what are my best options? flash a stock 4.4.3 image and re root?
It's failing because of xposed. Try this
http://forum.xda-developers.com/showthread.php?p=53109563
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
It's failing because of xposed. Try this
http://forum.xda-developers.com/showthread.php?p=53109563
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
i am thinking and maybe the best for me is to make a fresh install (never did this before).
i have a couple of apps that i will need to have root and i also like keep the philz custom recovery
i never did this so i would like to know if it is safe to follow this guide:
How to flash a factory image | Return to stock | Unroot your Nexus 5
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
i do not want to brick this. if i follow that, will i keep philz custom recovery? note that i am currently on 4.4.2.
and to get root again (after a fresh install of 4.4.3) will flash supersu.zip again be enough?
xposed is not needed for me and because of that i am havi all these troubles now, want to avoid that later.
edit: if i flash the file you posted, will it give me all the options i am asking right?
cesar.maranhao said:
i am thinking and maybe the best for me is to make a fresh install (never did this before).
i have a couple of apps that i will need to have root and i also like keep the philz custom recovery
i never did this so i would like to know if it is safe to follow this guide:
How to flash a factory image | Return to stock | Unroot your Nexus 5
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
i do not want to brick this. if i follow that, will i keep philz custom recovery? note that i am currently on 4.4.2.
and to get root again (after a fresh install of 4.4.3) will flash supersu.zip again be enough?
xposed is not needed for me and because of that i am havi all these troubles now, want to avoid that later.
edit: if i flash the file you posted, will it give me all the options i am asking right?
Click to expand...
Click to collapse
The link I gave you is the same as a clean install except you won't lose your data or custom recovery. You will lose root and will have to flash super su in your custom recovery. If you go with a complete clean install I'd use the link you posted. You'll have to flash a custom recovery via fastboot and then flash super su in it to root. My link will be simpler for you
Sent from my Nexus 5 using XDA Free mobile app
I recently upgraded to 4.4.3 myself. Everything you need is in the stickies my friend. Flash the stock 4.4.2 factory ROM through philz recovery. When you upgrade to 4.4.3 you will lose your custom recovery but the boot loader should still be unlocked (mine was). Its okay, there are two options to get philz recovery back. You can use fast boot commands with the phone in the boot loader menu connected to your PC. The command itself and how to set up android SDK is in the sticky called unlocking boot loader, rooting and flashing ROM (or something like that lol). Option two is to use the app flashify available from the playstore. It will back up your custom recovery and you can use that to reflash it after you upgrade. I have not used it myself as I prefer to just use the simple fastboot commands in the cmd menu.
EDIT
http://forum.xda-developers.com/showthread.php?t=2507905
Follow this tutorial on how to get your recovery back. Also the phone will no longer be rooted. There is a link in that tut to the superuser zip. Flash it through the custom recovery after you install it. You'll be rooted on 4.4.3 in less than 15 minutes from start to finish
Sent from my Nexus 5 using xda premium
I just flashed rastakat 4.4.2 then dirty flashed rastakat 4.4.3. Runs smooth and I lost nothing
Sent from my Nexus 5 using XDA Free mobile app
Tunderpimp said:
I just flashed rastakat 4.4.2 then dirty flashed rastakat 4.4.3. Runs smooth and I lost nothing
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
That's nice. What's the price of beans in India?
Is it possible to boot a recovery image from the phone without flashing? If not is it ok to reflash backups of stock recovery? Tnx
and313 said:
Is it possible to boot a recovery image from the phone without flashing? If not is it ok to reflash backups of stock recovery? Tnx
Click to expand...
Click to collapse
It is possible via android sdk. You can use command: fastboot boot twrp.img
where twrp.img is the name of the recovery that you downloaded and not twrp.img
Alexandar92zr said:
It is possible via android sdk. You can use command: fastboot boot twrp.img
where twrp.img is the name of the recovery that you downloaded and not twrp.img
Click to expand...
Click to collapse
Yes i know but i would like to do it from the phone... There are tons of flash recovery apps but no boot recovery apps
ROM manager used to do it years ago until people got into trouble with it and it was removed.
If you intend on flashing things AMD backing up, flash a recovery. If you're not willing to flash a recovery, don't modify your phone
Sent from my Nexus 5 using Tapatalk
and313 said:
Yes i know but i would like to do it from the phone... There are tons of flash recovery apps but no boot recovery apps
Click to expand...
Click to collapse
Try flashify
AndreIrawan97 said:
Try flashify
Click to expand...
Click to collapse
That flashes recovery. Clue is in the name.
Sent from my Nexus 5 using Tapatalk
rootSU said:
ROM manager used to do it years ago until people got into trouble with it and it was removed.
If you intend on flashing things AMD backing up, flash a recovery. If you're not willing to flash a recovery, don't modify your phone
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The problem with flashing is that you loose the ota update ability. That's why i would like to keep the stock recovery and just boot into cwm when i need it... But i guess i can restore the stock recovery via flashify before the ota is being installed so thats a solution... I just dont like flashing this stuff via apps
and313 said:
The problem with flashing is that you loose the ota update ability. That's why i would like to keep the stock recovery and just boot into cwm when i need it... But i guess i can restore the stock recovery via flashify before the ota is being installed so thats a solution... I just dont like flashing this stuff via apps
Click to expand...
Click to collapse
1) you do not lose OTA update ability with custom recovery. Read "OTA help-desk" available via my signature
2] what's the big deal about OTA? Its the worst way of updating available to everyone. Why bother? If you rely on OTA, remain unrooted, unmodified. Rooting is not for you.
Sent from my Nexus 5 using Tapatalk
Ugh lol OK, so worried about the ota? No worries, flash whatever recovery you want twrp,cwm,philz whatever floats your boat. Then when your ota comes out use Rashr to reflash stock recovery so you can update(you have to be on stock obviously).
I've done this numerous times, works every time.
Sent from my Nexus 5 using XDA Free mobile app
todorcim said:
Ugh lol OK, so worried about the ota? No worries, flash whatever recovery you want twrp,cwm,philz whatever floats your boat. Then when your ota comes out use Rashr to reflash stock recovery so you can update(you have to be on stock obviously).
I've done this numerous times, works every time.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
One of the problems with OTA is the slow delivery and partial nature.
If I wasn't rooted, i'd always update using factory images. But since I am, the best way is for flash a pre-rooted stock ROM via recovery. They're usually available within an hour of the factory image becoming available
Sent from my Nexus 5 using Tapatalk
rootSU said:
One of the problems with OTA is the slow delivery and partial nature.
If I wasn't rooted, i'd always update using factory images. But since I am, the best way is for flash a pre-rooted stock ROM via recovery. They're usually available within an hour of the factory image becoming available
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Agreed 100%, I normally stay rooted,this most recent preview though I'm staying stock. After running L for the last couple months its hard to go back to KitKat(I've tried several times). I have no intention of flashing another rom atm, I'll worry about root after the 3rd.
As for buddy worrying about the ota, really you have two choices.
#1 root and flash a recovery then wait for someone to post a root stock ROM
#2 wait for the ota
The only real benefit I see in waiting for the ota is you will probably get to keep all your apps on your phone. Me personally? I'd just fastboot the preview and wait till the 3rd.
Materialized From The DarkSide
Whenever superSu asks for permission to run a root app my screen becomes unresponsive. Timer runs out and i am not able to apply grant permission. Help. This didnt use to happen when i was earlier rooted with towelroot. Right now also i ised towelroot
Have you tried re-flashing the supersu zip?
jameson21 said:
Have you tried re-flashing the supersu zip?
Click to expand...
Click to collapse
Yes. Didnt work.
Btw by reflash the zip file you mean reinstall it from pkay store, right?
Pardon the ignorance. Just found out that flashing a zip file and installing apps from play store are 2 different things.
Well my bootloader is locked and neither do i have a custom recovery installed. So flashing doesnt seem to be an option right now.. If i am not missing anything.
Are you running 5.0? If so how the heck did you root with towelroot? AFAIK you can not root 5.0 that way. Maybe that is a problem.
Sent from my Nexus 5 using Tapatalk
frenziedfemale said:
Are you running 5.0? If so how the heck did you root with towelroot? AFAIK you can not root 5.0 that way. Maybe that is a problem.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
No no. I am on kitkat only
Tried reinstalling it. This is what came up. I am on android 4.4.4 btw
You need to flash the supersu zip using fastboot:
teamandroid. com/2014/06/19/root-nexus-5-android-444-ktu84p-kitkat/2/ (you're going to have to fix that link because I have under 10 posts so the forum won't let me post..)
Additionally you need to have an unlocked bootloader
jameson21 said:
You need to flash the supersu zip using fastboot:
teamandroid. com/2014/06/19/root-nexus-5-android-444-ktu84p-kitkat/2/ (you're going to have to fix that link because I have under 10 posts so the forum won't let me post..)
Additionally you need to have an unlocked bootloader
Click to expand...
Click to collapse
Why is it happening now? Didnt use to happen earlier..
You say you were rooted ...why did you re-root? It looks like you are no longer rooted. Did you do an update or anything?
Sent from my Nexus 5 using Tapatalk
frenziedfemale said:
You say you were rooted ...why did you re-root? It looks like you are no longer rooted. Did you do an update or anything?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I was rooted. I unrooted because i thought it was required to update to lollipop. But i dont have any intention to update to L for now.
rahul9five said:
I was rooted. I unrooted because i thought it was required to update to lollipop. But i dont have any intention to update to L for now.
Click to expand...
Click to collapse
To get root again either flash the latest CF Auto Root in fastboot or flash the latest superSU.zip in recovery or flash a pre-rooted custom rom in a custom recovery.