My Nexus 6 was on Android N. Then I rooted it using twrp to install supersu 2.71. This afternoon, I got a notification for Android N update ota, and I allowed it. It downloaded the software and boot up into twrp. What I am supposed to do next? I tried to reboot, but it always came back to twrp. This is my first rooted phone and I have no idea what is going on. Please help!!!
In twrp, I tried to Restore to the mashmallow back up (MOB30I), but it failed.
SPR10 said:
In twrp, I tried to Restore to the mashmallow back up (MOB30I), but it failed.
Click to expand...
Click to collapse
Reboot to bootloader in TWRP then reboot from there. This will end the loop.
Thank you for your response. I reboot into bootloader , then select :"power off". But when I turn on phone, it came back to twrp. I reboot back to bootloader, then select "start". It boot up to twrp again. Anything else I can try?
I tried again, reboot into bootloader and then select start again. It went through the same process, but it was able to boot again. Now I got notification of system update, like before. I need to unroot it to allow for android N update?
Thank you. You are a life saver.
SPR10 said:
I need to unroot it to allow for android N update?
Thank you.
Click to expand...
Click to collapse
Installing a stock N recovery in fastboot should be enough to allow you to take the update. You will likely need to install TWRP and then root again afterward.
Thank you Durgis. Can I have more instruction on how to install stock N recovery in fastboot. I guess have to download file for stock N recovery, boot the phone to bootloader, then use some command to install it.
ok.. you CAN NOT install an ota via twrp recovery. you have to have stock recovery if you want to install an ota, period. next time, search and read.
Could he use flashfire to update to the new N he's being asked to install?
yankeesfan714 said:
Could he use flashfire to update to the new N he's being asked to install?
Click to expand...
Click to collapse
no idea
I know I use it to flash the monthly updates.
twrp cant flash updates, you neef the stock recovery for that. seems as you wiped your phones rom off the phone. so, youre going to have to push a rom to your phone and flash it.
yankeesfan714 said:
Could he use flashfire to update to the new N he's being asked to install?
Click to expand...
Click to collapse
There is an option to flash an OTA in flash fire. I personally used it to flash the n image from mm
chapelfreak said:
There is an option to flash an OTA in flash fire. I personally used it to flash the n image from mm
Click to expand...
Click to collapse
I use it to flash full images since my system is modified.
converge12 said:
Reboot to bootloader in TWRP then reboot from there. This will end the loop.
Click to expand...
Click to collapse
Hi converge12, I completed registration in this forum only to say you thank you.
Go to TWRP then select restart as "bootloader" and select start to go into system.
Related
I have a rooted XT1068 and there is an official OTA update to 5.0.2, should I install it? Do I lose my root access?
egwktm said:
I have a rooted XT1068 and there is an official OTA update to 5.0.2, should I install it? Do I lose my root access?
Click to expand...
Click to collapse
You have to "Full unroot" in SuperSU settings and restore the stock recovery. Otherwise OTA will fail. After the OTA is installed, You can easily return to TWRP and flash SuperSU.
okay thanks! also instead of twrp could I use chainfire again?
Unfortunately, i tried to install OTA and now every time i turn on my phone it reboots and tries to install 5.02 only to get an error and it stays at twrp menu. So what can i do now?
lol after many reboots phone decided to tell me that update was unsuccessful so it works again.
more details pls for a beginner
I made the same mistake trying to flash OTA 5.02 over rooted device 4.4.4 . I got out of the loop by moving the download zip from system/cache to external sd...
just wanting to make sure I do all the right things and in order:
so in Super SU I go the FULL UNROOT
how do I then restore stock recovery?
Once I I have restored it what are the steps for the zip and install via stock recovery?
sorry about the boring questions - it's still a bit of a jungle for a beginner
egwktm said:
okay thanks! also instead of twrp could I use chainfire again?
Click to expand...
Click to collapse
Sure. But why? Twrp is superior in every aspect. It's like deliberately crippling your toaster so that only one slice fits.
Will I be able to install ota updates with stock recovery and after unroot if I do changes to /system?
dpdp73 said:
Will I be able to install ota updates with stock recovery and after unroot if I do changes to /system?
Click to expand...
Click to collapse
No
doppelhelix said:
Sure. But why? Twrp is superior in every aspect. It's like deliberately crippling your toaster so that only one slice fits.
Click to expand...
Click to collapse
Nice imagination.
But why do I often read that TWRP will be overwritten by Lollipop with custom recovery when rebooting the phone? Some people therefore recommend the Chainfire CF-Auto-Root instead.
So after unlocking bootloader can I flash TWRP in fastboot mode and superSU afterwards without those kind of problems?
Wolfcity said:
Nice imagination.
But why do I often read that TWRP will be overwritten by Lollipop with custom recovery when rebooting the phone?
Click to expand...
Click to collapse
It's a "feature" introduced by google for their nexus. I will quote the twrp website:
The stock ROM will automatically replace TWRP with the stock recovery. To prevent the stock ROM from replacing TWRP, boot TWRP, go to the mount menu and mount system, press the home button, then press Advanced ->File Manager. Browse to /system and select the file named recovery-from-boot.p then choose to rename the file to recovery-from-boot.bak
Or you flash the SuperSU.zip. That will prevent the override too.
doppelhelix said:
It's a "feature" introduced by google for their nexus. I will quote the twrp website:
The stock ROM will automatically replace TWRP with the stock recovery. To prevent the stock ROM from replacing TWRP, boot TWRP, go to the mount menu and mount system, press the home button, then press Advanced ->File Manager. Browse to /system and select the file named recovery-from-boot.p then choose to rename the file to recovery-from-boot.bak
Or you flash the SuperSU.zip. That will prevent the override too.
Click to expand...
Click to collapse
Thx a lot for your explantion.
This was one of the things that irritated me right from the start when I was checking out the possibilities of custom recovery/root within 5.0.
I heard about the file-renaming thing but didn´t realize that superSu will do the job too and that it is a Nexus "feature" at all.
Helped me very much!
I recently followed this guide to root my XT1095. All I did was unlock my bootloader and boot the image...I did not (intentionally) alter my recovery, nor did I install a custom ROM. Will I still receive OTA update notifications and, if so, are they safe to apply?
Dan Again said:
I recently followed this guide to root my XT1095. All I did was unlock my bootloader and boot the image...I did not (intentionally) alter my recovery, nor did I install a custom ROM. Will I still receive OTA update notifications and, if so, are they safe to apply?
Click to expand...
Click to collapse
If you are running a custom recovery TWRP for example, I doubt that you will get OTA updates. I believe you need the stock recovery to be able to install OTA updates.
grneyez said:
If you are running a custom recovery TWRP for example, I doubt that you will get OTA updates. I believe you need the stock recovery to be able to install OTA updates.
Click to expand...
Click to collapse
I'm a little confused by your response. As I said in my original question, I did not (intentionally) alter my recovery. Did the method that I used achieve root alter my recovery for me?
If you did not install a custom recovery than you should be able to get OTA updates. Check to see what recovery you have.
Dan Again said:
I'm a little confused by your response. As I said in my original question, I did not (intentionally) alter my recovery. Did the method that I used achieve root alter my recovery for me?
Click to expand...
Click to collapse
As long as you don't make any changes to /system, you *should* be good to go for updates. If you didn't intentionally flash a custom recovery then you still have the stock one.
If you're rooted OTAs won't work. In KitKat and lower they just performed checksums on each file before updating, so the altered root files were left untouched and the update installed. In Lollipop and up (at least for Nexus devices), it does a total checksum and if /system has been altered in any way (including for root) OTA's won't install.
grneyez said:
If you did not install a custom recovery than you should be able to get OTA updates. Check to see what recovery you have.
Click to expand...
Click to collapse
Thanks for all the responses, guys. I booted into recovery and saw this, so I think my recovery is still stock. One quick question: when I boot into fastboot and select "Recovery", I get a dead Android and a "No Command" prompt - I had to follow these steps to actually get there. Why is that?
I'd like to try out Xposed now that it's available for my device, and I see that requires a custom recovery. If I install a custom recovery (TWRP, for instance) and use it to flash Xposed, can I then revert back to stock recovery and continue to receive OTA updates?
Dan Again said:
Thanks for all the responses, guys. I booted into recovery and saw this, so I think my recovery is still stock. One quick question: when I boot into fastboot and select "Recovery", I get a dead Android and a "No Command" prompt - I had to follow these steps to actually get there. Why is that?
I'd like to try out Xposed now that it's available for my device, and I see that requires a custom recovery. If I install a custom recovery (TWRP, for instance) and use it to flash Xposed, can I then revert back to stock recovery and continue to receive OTA updates?
Click to expand...
Click to collapse
If you modified your system with Xposed you won't be able to install OTA updates. Even if you return yo stock recovery.
To install an OTA you need three things. 1. Unaltered system, 2.no root and 3. stock recovery
juliospinoza said:
If you modified your system with Xposed you won't be able to install OTA updates. Even if you return yo stock recovery.
To install an OTA you need three things. 1. Unaltered system, 2.no root and 3. stock recovery
Click to expand...
Click to collapse
Fair enough. So let's say that I install a custom recovery and then Xposed. Will there be a way that I can manually upgrade to new stock OS versions as they come out for my phone?
Dan Again said:
Fair enough. So let's say that I install a custom recovery and then Xposed. Will there be a way that I can manually upgrade to new stock OS versions as they come out for my phone?
Click to expand...
Click to collapse
You can always flash a ROM or custom ROM via fast boot, but you will loss all your settings, apps etc because you are flashing an entire new system... The OTA only patches
The only way back is to flash your stock ROM if you can get a hold of it.
floepie said:
The only way back is to flash your stock ROM if you can get a hold of it.
Click to expand...
Click to collapse
So, funny story - this weekend I accidentally wiped my OS and had to flash stock ROM to get back up and running. See: here. Good resource for others who might be looking for Moto X 2014 stock Lollipop firmware...definitely saved that on my computer
juliospinoza said:
If you modified your system with Xposed you won't be able to install OTA updates. Even if you return yo stock recovery.
To install an OTA you need three things. 1. Unaltered system, 2.no root and 3. stock recovery
Click to expand...
Click to collapse
Isn't there any way to uninstall Xposed, revert back to original recovery and remove root--all in order to install OTA without completely loosing user data and apps installed?
yurkennis said:
Isn't there any way to uninstall Xposed, revert back to original recovery and remove root--all in order to install OTA without completely loosing user data and apps installed?
Click to expand...
Click to collapse
yes
just flash via fastboot
1. recovery (stock)
2. system
if your phone is 5.0 xt1095 and you didn't flash modems you should be able to receive OTA.
Repeat of Question
I'm not sure I completely understand what I need to do to get updated to 5.1. I have an XT1095 that I only rooted, no custom recovery. I downloaded the OTA for 5.1 last night and tried to update. Got an error and it did not update. A quick google search seems to state, as well as earlier in this thread, that I can not update if I am rooted. I would prefer not completely start over on my phone (wipe) and would like to just apply the update. Can I just "unroot" my phone and apply the update or do I have to go back to the beginning (with a stock recovery) before the update will take?
I know enough about all this to have followed the directions to accomplish the root about 7 months ago. Since then not played with any system files! The only reason I rooted was so I could use the full capabilities of Greenify. Any opinions on that would be appreciated as well. Thanks!
jhworth8 said:
I'm not sure I completely understand what I need to do to get updated to 5.1. I have an XT1095 that I only rooted, no custom recovery. I downloaded the OTA for 5.1 last night and tried to update. Got an error and it did not update. A quick google search seems to state, as well as earlier in this thread, that I can not update if I am rooted. I would prefer not completely start over on my phone (wipe) and would like to just apply the update. Can I just "unroot" my phone and apply the update or do I have to go back to the beginning (with a stock recovery) before the update will take?
I know enough about all this to have followed the directions to accomplish the root about 7 months ago. Since then not played with any system files! The only reason I rooted was so I could use the full capabilities of Greenify. Any opinions on that would be appreciated as well. Thanks!
Click to expand...
Click to collapse
Try reading, the post literally before yours tells you what to do, lol.
Sent from my XT1095 using Tapatalk
AGISCI said:
Try reading, the post literally before yours tells you what to do, lol.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I take it that flashing the recovery and the system.img files to the phone will not erase all the apps, photos, music, etc.?
summit15 said:
I take it that flashing the recovery and the system.img files to the phone will not erase all the apps, photos, music, etc.?
Click to expand...
Click to collapse
Correct, it won't erase those things.
Sent from my XT1095 using Tapatalk
so if i am just rooted, and custom recovery, could I unroot (via supersu app) and flash stock recovery and be good to go? or am i missing something?
yamahakid said:
so if i am just rooted, and custom recovery, could I unroot (via supersu app) and flash stock recovery and be good to go? or am i missing something?
Click to expand...
Click to collapse
It's more difficult with Lollipop: updates now "look for" a completely stock unmodified unrooted system. So you'll have to flash a stock image of the current build and then take the OTA.
i need to do OTA update , already with twrp and root , so in order to do ota update i need to fastboot stock recovery !
upload a stock recovery.img if anybody having it.
download shamu image , extract to get the recovery.IMG
It's a Nexus load what you wish. Images here :
https://developers.google.com/android/nexus/images#shamu
Sent from my Google N6 on VZ
yes i know that , i thought rather downloading whole image if somebody could provide me the recovery image only well thanks. ill do it.
ashupulse said:
yes i know that , i thought rather downloading whole image if somebody could provide me the recovery image only well thanks. ill do it.
Click to expand...
Click to collapse
It needs to be more than just "stock recovery". It needs to be the exact version the ota will expect. So you'll have to download the matching image to your version you're on now...
Which if you're doing that, hadn't you just as well download the latest 5.1 image and just flash all that?
I would just flash the factory image..... less chance of a mess....
Never done an official OTA on my old N5, N10, or N6. I just fastboot the update radio, bootloader, system, and twrp recovery. Boot into recovery, reboot and install su when prompted. Always on the latest android version without losing data
mymusicathome said:
Never done an official OTA on my old N5, N10, or N6. I just fastboot the update radio, bootloader, system, and twrp recovery. Boot into recovery, reboot and install su when prompted. Always on the latest android version without losing data
Click to expand...
Click to collapse
I hear you. if anything, back in the days, we used to avoid the OTA. I'm not sure why everybody has such a hard on for it.
Sent from my Google N6 on VZ
Only ota I took was when my n5 forced one on me out of the box. Never intentionally took one since android 1.5
recovery from 5.0.1
rootSU said:
It needs to be more than just "stock recovery". It needs to be the exact version the ota will expect. So you'll have to download the matching image to your version you're on now...
Which if you're doing that, hadn't you just as well download the latest 5.1 image and just flash all that?
Click to expand...
Click to collapse
yes you are right actually i downloaded 5.1 exctracted recovery , flashed via fastboot.... and i hit error.
so lesson is recovery from 5.0.1 is needed.
ashupulse said:
yes you are right actually i downloaded 5.1 exctracted recovery , flashed via fastboot.... and i hit error.
so lesson is recovery from 5.0.1 is needed.
Click to expand...
Click to collapse
How are you flashing?
mymusicathome said:
Never done an official OTA on my old N5, N10, or N6. I just fastboot the update radio, bootloader, system, and twrp recovery. Boot into recovery, reboot and install su when prompted. Always on the latest android version without losing data
Click to expand...
Click to collapse
When updated to 5.1 from 5.0.1 -- I had to do Factory Data Reset, since after update N6 was showing 32GB instead of 64GB.
Was there a way to avoid Factory Data Reset ? Thank you!
Hello guys,
now i'm sure, i'm unlucky with rooted phone..
this morning i accidentally update my rooted phone ( system update ).
after instalation of update, i see only the screen " WARNING BOOTLOADER UNLOCKED ".
fastboot it's work.
when i select recovery mod, i can see the android at the floor with a danger panel ( ://www.android.gs/wp-content/uploads/2013/08/CRgew.jpg add http )
I don't want to do a mistake, so i need your help..
thank for your answer
I did the same thing, please help!
Okay guys i'm so happy ! i flash a new rom
sorry for this small post..
PadreToio do this http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
REDScrat said:
Hello guys,
now i'm sure, i'm unlucky with rooted phone..
this morning i accidentally update my rooted phone ( system update ).
after instalation of update, i see only the screen " WARNING BOOTLOADER UNLOCKED ".
fastboot it's work.
when i select recovery mod, i can see the android at the floor with a danger panel ( ://www.android.gs/wp-content/uploads/2013/08/CRgew.jpg add http )
I don't want to do a mistake, so i need your help..
thank for your answer
Click to expand...
Click to collapse
If u have fastboot working install twrp recovry
Then flash a custom rom like cm
I did exactly the same mistake today. After the update my phone booted, everything looked fine but after a couple of seconds rebooted into recovery. Always the same scenario.
My solution was to flash SuperSU in recovery, delete cache and dalvik and reboot the phone. The phone reverted the update and everything looks fine for now. Now it prompts me again for the ota update.
RobaL4 said:
I did exactly the same mistake today. After the update my phone booted, everything looked fine but after a couple of seconds rebooted into recovery. Always the same scenario.
My solution was to flash SuperSU in recovery, delete cache and dalvik and reboot the phone. The phone reverted the update and everything looks fine for now. Now it prompts me again for the ota update.
Click to expand...
Click to collapse
If you're still stock recovery, then just use the Super SU app to full unroot and then you can update.
Tel864 said:
If you're still stock recovery, then just use the Super SU app to full unroot and then you can update.
Click to expand...
Click to collapse
Is there a way to have stock recovery and root? When I rooted my Moto G (2 months agoo?) I didn't find a way to just root the smartphone without changing recovery
RobaL4 said:
Is there a way to have stock recovery and root? When I rooted my Moto G (2 months agoo?) I didn't find a way to just root the smartphone without changing recovery
Click to expand...
Click to collapse
Sure, it's easy. Just boot into TWRP without flashing it. In stock recovery
Fastboot boot TWRP.img (or whatever you name it)
Flash SuperSU.zip in TWRP then boot to system and you're rooted.
I had TWRP installed and enrolled in the beta program. I just downloaded the official 7.0 through the push notification and clicked, "Restart and Install." Now, my phone boots automatically into TWRP. I've turned it off, then back on and same thing. Any ideas how to get out of this?
Boot into bootloader from recovery and select start.
prestige777 said:
Boot into bootloader from recovery and select start.
Click to expand...
Click to collapse
Yeah but it still can't install the update,any way fix it?
Boot to bootloader and flash the stock recovery from factory image. Then boot into stock recovery and the update should start.
The same happened to me. Disappointing, since the previews all worked (for me) in TWRP.
I just downloaded the OTA and sideloaded it, flashed TWRP, rebooted into TWRP and installed SuperSU 2.78. Worked fine.
https://developers.google.com/android/nexus/ota#shamu
dahawthorne said:
The same happened to me. Disappointing, since the previews all worked (for me) in TWRP.
I just downloaded the OTA and sideloaded it, flashed TWRP, rebooted into TWRP and installed SuperSU 2.78. Worked fine.
https://developers.google.com/android/nexus/ota#shamu
Click to expand...
Click to collapse
May I ask which version of TWRP did you use?
twrp-3.0.2-0-shamu.img
you cant flash an official factory image in twrp..this is a known fact...
Is that comment aimed at me? Did you actually read my post? Can you point me at the relevant part where I get it wrong?
Feel free to apologise any time.
dahawthorne said:
Is that comment aimed at me? Did you actually read my post? Can you point me at the relevant part where I get it wrong?
Feel free to apologise any time.
Click to expand...
Click to collapse
You are side loaded ota then flash twrp . But in op he was flashed ota via twrp and now os corrupted and he is not able to boot into system. All ota can flashed via stock recovery , i think. He have to flash firmware now via fast boot. Am i correct . If anything wrong ,you can correct.
Everybody should be friends in XDA.
It seems that people don't read posts before writing. The OP clearly said that he had applied the OTA. I clearly said that this was exactly what I did with the same result. I also clearly explained what I did to fix it. The next comment should be from the OP saying what he's doing to recover. If he does what I did he'll be fine.
drmuruga said:
You are side loaded ota then flash twrp . But in op he was flashed ota via twrp and now os corrupted and he is not able to boot into system. All ota can flashed via stock recovery , i think. He have to flash firmware now via fast boot. Am i correct . If anything wrong ,you can correct.
Everybody should be friends in XDA.
Click to expand...
Click to collapse
He can reinstall stock recovery and side load from there
Either flash the stock recovery.img through twrp or
Flash stock recovery through fastboot or
Install factory image through fastboot
Edit: oops didn't read the entire thread
itsagood said:
I had TWRP installed and enrolled in the beta program. I just downloaded the official 7.0 through the push notification and clicked, "Restart and Install." Now, my phone boots automatically into TWRP. I've turned it off, then back on and same thing. Any ideas how to get out of this?
Click to expand...
Click to collapse
To avoid issues, I'd say make sure you're 100% stock, recovery and all before installing an official update. Like I said, just to be sure it won't fail.
I got the the OTA notification before work yesterday. All day at work I was itching to install it but with no PC I couldn't risk it. I was on the DP5 with TWRP, no root, and unlocked. I couldn't wait. I flashed the OTA with TWRP after I restored a backup of when I first installed DP5. TWRP throw a couple of errors but after about 10 minutes of hanging on the boot animation it finally booted. My phone was encrypted but other then that it was fine. I was gonna root it afterwards but I was on stock recovery after flashing the OTA so I couldn't do anything until I got home. Made a noforc-nonverify boot IMG throw on TWRP reformatted. Running great now.
Edit: My DP5 boot.img was also noforc-nonverify.
Sent from my Nexus 6