TWRP wont stick keep going to stock - Nexus 6P Q&A, Help & Troubleshooting

was trying to do a systemless root to use android pay and unrooted my device from the SU app and selected to keep my custom recovery, tried to go into recovery and gave me the stock recovery. Used fastboot to reinstall twrp but after reboot it reverts back to stock, what am i doing wrong.
stock 7.0

Look for a system file called recovery from boot.p (boot.p). Might be your culprit. It's a file , if I recall correctly, that on initial boot overwrites twrp. Puts you back on stock.

You don't need the twrp installed. Just boot to the bootloader and type: fastboot boot twrp-filename.img from your command prompt on your pc.

In order to make sure that custom recovery overwrites twrp, when you have finished flashing twrp, reboot into bootloader immediately. Then flash latest SuperSU. This modifies boot.img so it doesn't overwrite twrp.

so ill fastboot install twrp then i will not reboot into system because if i do the recovery will be overwriten with the old stock recovery. Trying to use a systemless root with magisk

blueyes said:
Look for a system file called recovery from boot.p (boot.p). Might be your culprit. It's a file , if I recall correctly, that on initial boot overwrites twrp. Puts you back on stock.
Click to expand...
Click to collapse
where is the file located, should i replace that file or just delete it. Thank you

Toxin715 said:
where is the file located, should i replace that file or just delete it. Thank you
Click to expand...
Click to collapse
No no no. Try like I mentioned. Flash TWRP then reboot recovery immediately. Then flash SU. This will prevent TWRP from being overwritten
Sent from my Nexus 6P using XDA-Developers mobile app

dratsablive said:
No no no. Try like I mentioned. Flash TWRP then reboot recovery immediately. Then flash SU. This will prevent TWRP from being overwritten
Click to expand...
Click to collapse
OK will do, well give results soon

dratsablive said:
No no no. Try like I mentioned. Flash TWRP then reboot recovery immediately. Then flash SU. This will prevent TWRP from being overwritten
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
ok systemless root with magisk works fine along with twrp sticking now. Things to know is when twrp is booting it still says unable to mount system but everything works fine if that matters. Thank you

Toxin715 said:
ok systemless root with magisk works fine along with twrp sticking now. Things to know is when twrp is booting it still says unable to mount system but everything works fine if that matters. Thank you
Click to expand...
Click to collapse
What version of TWRP are you flashing?
Sent from my Nexus 6P using XDA-Developers mobile app

Related

4.2.2 Update / TWRP problem

Hello. I just received my OTA notification, but when I clicked it, it rebooted and landed my on the TWRP recovery screen. Not knowing what to do, I just told it to reboot to the system.
Once rebooted, I was still on 4.2.1, and there was no update.
Any ideas why it booted to TWRP?
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
MacHackz said:
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
Click to expand...
Click to collapse
Maybe before you even answer, I'm sure I'll find a link on here to show me how?
One issue I have though, is that when I manually updated to 4.2.1 on my Nexus 7, I still got an OTA update a few days later, that actually ran.
I don't ever plan on flashing roms to any of my devices. Do I need to keep a custom recovery on my Nexus 4 or 7? If not, how to I revert back to the stock recovery?
If you saved the offical stock 4.2.1 images, to revert back to stock recovery, just use the 'fastboot flash recovery recovery.**************.img' command. If you haven't, you might have to flash the whole 4.2.2 rom which you can find on the google dev website. After this, if you only want to root then you don't need to flash a custom recovery, just use the 'boot' command instead of the 'flash' one.
MacHackz said:
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
Click to expand...
Click to collapse
I flashed the OTA sideload file through TWRP and it installed succesfully.
jvbferrer said:
I flashed the OTA sideload file through TWRP and it installed succesfully.
Click to expand...
Click to collapse
How did you do that? Did you sideload wrinkle's file from this thread: http://forum.xda-developers.com/showthread.php?t=2145848?
I should let you know, that while I'm not afraid to install via the custom recovery, it doesn't mean I've done it via commands. I've always used toolkits, or one click methods of rooting and installing custom recoveries.
Well, this is crazy (weird?). I tried to flash it via TWRP by downloading the zip file in the thread referenced above, and it failed. By flashing, I mean, I chose 'Install' and pointed to the zip after moving it to my phone. After failing, I wiped the Dalvik cache and rebooted, and it's telling me 'Android is upgrading'. If it means it updated, so be it. But can anyone explain? Feeling a little confused here.
Edit: Ok, so it said it was upgrading, but it's still 4.2.1.
wvcadle said:
Well, this is crazy (weird?). I tried to flash it via TWRP by downloading the zip file in the thread referenced above, and it failed. By flashing, I mean, I chose 'Install' and pointed to the zip after moving it to my phone. After failing, I wiped the Dalvik cache and rebooted, and it's telling me 'Android is upgrading'. If it means it updated, so be it. But can anyone explain? Feeling a little confused here.
Edit: Ok, so it said it was upgrading, but it's still 4.2.1.
Click to expand...
Click to collapse
It 'upgrades' when you wipe the cache. It just means it's rebuilding the cache. Are you running an unmodified stock rom? Custom kernel?
MacHackz said:
It 'upgrades' when you wipe the cache. It just means it's rebuilding the cache. Are you running an unmodified stock rom? Custom kernel?
Click to expand...
Click to collapse
Yes, stock rom, rooted and unlocked. I did install Beats today. Could this be the problem? If so, I found a revert zip that I'm assuming is supposed to revert me back to stock audio codecs.
I don't think added files matter, but I'm guessing the Beats mod has overwritten something in system, so flash the revert zip, then try again.
MacHackz said:
I don't think added files matter, but I'm guessing the Beats mod has overwritten something in system, so flash the revert zip, then try again.
Click to expand...
Click to collapse
Flashing the revert zip failed. I'm starting to think that flashing anything with TWRP will fail.
How about this. I made a backup of all system data + apps with Titanium earlier today. Could I just reset my phone back to factory defaults, restore my apps + some system data, then re-root (*without a custom recovery*) and wait for the update again? Or will it come again?
Also, I've used Wugfresh's Nexus Toolkit. I don't remember checking the custom recovery button, but ended up with TWRP anyway. What's the easiest way to root without installing a custom recovery?
You could try that, and the update will come straiht away. You can root without flashing a custom recovery, just use the 'boot recovery' instead of 'flash recovery'
MacHackz said:
flash cwm and see if there's any difference
Click to expand...
Click to collapse
How do I do that with TWRP? Can I do it with Wug's Nexus toolkit?
wvcadle said:
How do I do that with TWRP? Can I do it with Wug's Nexus toolkit?
Click to expand...
Click to collapse
I'm not familiar with any toolkits, I would recommend flashing cwm using fast boot
MacHackz said:
I'm not familiar with any toolkits, I would recommend flashing cwm using fast boot
Click to expand...
Click to collapse
Ok, I'm surely not afraid to use the command prompt. Any tutorials you can point me to? I probably already have all of the drivers I need, as the toolkit had to download install them.
wvcadle said:
Ok, I'm surely not afraid to use the command prompt. Any tutorials you can point me to? I probably already have all of the drivers I need, as the toolkit had to download install them.
Click to expand...
Click to collapse
Check out this thread. Use flash to flash and overwrite TWRP, or boot just to test. http://forum.xda-developers.com/showthread.php?t=1995440
MacHackz said:
Check out this thread. Use flash to flash and overwrite TWRP, or boot just to test. http://forum.xda-developers.com/showthread.php?t=1995440
Click to expand...
Click to collapse
Where in that thread does it show me how to flash the stock recovery back onto my device?
wvcadle said:
Hello. I just received my OTA notification, but when I clicked it, it rebooted and landed my on the TWRP recovery screen. Not knowing what to do, I just told it to reboot to the system.
Once rebooted, I was still on 4.2.1, and there was no update.
Any ideas why it booted to TWRP?
Click to expand...
Click to collapse
The same thing happened to me. I was rooted running stock ROM with TWRP recovery (used wugfresh toolkit). The problem was I forgot I was using a modified kernel (for color correction) by molesarecoming. I flashed the stock kernel back, downloaded and flashed the OTA file from the help desk thread (http://forum.xda-developers.com/showthread.php?t=2145848&highlight=beats), and it worked. Oh, and I flashed the Superuser file immediately after the OTA did it's thing (while still in TWRP) to regain root. I didn't really like how after the initial failed install of the OTA, it took my into TWRP with no error message showing or anything.
I don't think TWRP is your problem -- I think beats is your problem. It may have modified something. Try searching the above-linked thread for answers. Honestly, there's no rush to get 4.2.2, so take your time finding the answer. It's better than wiping the phone just to install a small android update and having to redo everything on your phone again.
Ok, it must have been the Beats audio drivers. I restored a Nandroid backup from right before installing the beats audio drivers, then flashed the zip and it worked. Now running 4.2.2.
I would like to know, however, how to use fastboot via commands, so that I can learn how to flash TWRP, CWM, Stock recovery, etc.
wvcadle said:
Ok, it must have been the Beats audio drivers. I restored a Nandroid backup from right before installing the beats audio drivers, then flashed the zip and it worked. Now running 4.2.2.
I would like to know, however, how to use fastboot via commands, so that I can learn how to flash TWRP, CWM, Stock recovery, etc.
Click to expand...
Click to collapse
I need some help here - I have nexus 7 with 3G and Google (takju) with 4.2.1 installed.
I had it 'rooted" and installed TWRP .
AT the time I followed instructions to chand extension of some file to .bak - to prevent 'unrooting"
I do not remember which file I unfortunately changed.
Now I cannot install the 4.2.2 upgrade - the OTA fails because it boots into TWRP and after that I rrid several selections from TWRP screen (flash, reboot, etc) - but all attempts failed.
I have the upgrade files (bot .tar and .zip) on /sdcard directory but have no idea how to update to 4.2.2.
Tried manual flashing using adb command - all fails.
I do not have beats drivers installed
Can someone tell me how to uninstall TWRP? If the CWM recovery works with this upgrade, I would like to change from TWRP to CWM.
Or any other suggestion wold be appreciated.
I am really struggling with Android operating system the way it configured on Nexus 7 by Google - any simplest is a major pain!
Hope I can get out of this and operate the device instead of continuously meddling with operating system.
Thanks in advance
[email protected]

CWM and TWRP

Hi,
It seems that I have CWM and recovery installed on my Nexus 4. I was on TWRP previously and switched to CWM, now it seems that it is stucked.
I erased recovery in command prompt and flash it with CWM after installing stock ROM but ROM Manager still detected TWRP. How do I get rid of TWRP?
Zouk18 said:
Hi,
It seems that I have CWM and recovery installed on my Nexus 4. I was on TWRP previously and switched to CWM, now it seems that it is stucked.
I erased recovery in command prompt and flash it with CWM after installing stock ROM but ROM Manager still detected TWRP. How do I get rid of TWRP?
Click to expand...
Click to collapse
try flashing stock recovery via adb
If you reboot into recovery does CWM come up or TWRP? If it's CWM then ignore ROM Manager and continue as normal
ijustzeke said:
try flashing stock recovery via adb
Click to expand...
Click to collapse
So you are suggesting that I erase and flash to stock recovery via adb and then flash custom recovery again?
EddyOS said:
If you reboot into recovery does CWM come up or TWRP? If it's CWM then ignore ROM Manager and continue as normal
Click to expand...
Click to collapse
CWM comes up as the recovery because it's the latest one I flash. I know it might now matter but this really bugs me.
Dunno why you're using ROM Manager anyway, pointless piece of software IMO. Just flash everything manually
Mine was gone when i unrooting the device
Sent from my Nexus 4
EddyOS said:
Dunno why you're using ROM Manager anyway, pointless piece of software IMO. Just flash everything manually
Click to expand...
Click to collapse
I was just checking out the app, don't really use it. That was when I saw two recoveries. I erased and flashed everything via adb previously. Just really wanna know the cause and how to get rid of it.
curtzxion said:
Mine was gone when i unrooting the device
Sent from my Nexus 4
Click to expand...
Click to collapse
Is there a way just to unroot but keep my ROM, kernel and data intact?
Zouk18 said:
I was just checking out the app, don't really use it. That was when I saw two recoveries. I erased and flashed everything via adb previously. Just really wanna know the cause and how to get rid of it.
Is there a way just to unroot but keep my ROM, kernel and data intact?
Click to expand...
Click to collapse
My rom, kernel, and data doesn't change, when i was unrooting the device(as i remember)
Sent from my Nexus 4
That's normal. I have it too. Just choose cwm on recovery already installed and leave it like that.
Sent from my Nexus 4 using xda premium

Reflashing system partition?

I'm trying to upgrade my SuperSu to the latest beta so I can install Viper4Android for Angler. However, the instructions for SuperSu Beta states "If you are coming from any SuperSU install in /system, you must re-flash the stock system (and vendor and oem, if present) partition contents prior to installing this."
I was wondering if I could get some Nexus 6P specific instructions for doing that without screwing everything up. I assume this doesn't wipe my user apps. Thanks.
If you are comfortable with using ADB and fastboot, follow Section 10 of this guide. All you need to do is "fastboot flash system," just download the factory image that matches your current rom.
http://forum.xda-developers.com/showthread.php?t=3206928
Flashing just the system partition does not wipe app data.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
If you are comfortable with using ADB and fastboot, follow Section 10 of this guide. All you need to do is "fastboot flash system," just download the factory image that matches your current rom.
http://forum.xda-developers.com/showthread.php?t=3206928
Flashing just the system partition does not wipe app data.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yeah, I'm pretty comfortable using adb and fastboot. I'll try it out. Thanks!.
Quick question, can I keep the TWRP recovery or do I need to flash stock recovery too? Thanks again.
hull22 said:
Yeah, I'm pretty comfortable using adb and fastboot. I'll try it out. Thanks!.
Quick question, can I keep the TWRP recovery or do I need to flash stock recovery too? Thanks again.
Click to expand...
Click to collapse
Cool! There is no need to touch the recovery partition. Just fastboot the system and vendor img's then boot right into TWRP and install SuperSU
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Cool! There is no need to touch the recovery partition. Just fastboot the system and vendor img's then boot right into TWRP and install SuperSU
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I screwed it up. Flashed everything just fine. Didn't have the SuperSu beta on the phone yet, booted to system. It tried to re-encrypt the device. I interrupted it because it seemed to be stuck. Now, I have to factory reset and lose all of my data. Not sure where I have to restart now, root, etc...
hull22 said:
I screwed it up. Flashed everything just fine. Didn't have the SuperSu beta on the phone yet, booted to system. It tried to re-encrypt the device. I interrupted it because it seemed to be stuck. Now, I have to factory reset and lose all of my data. Not sure where I have to restart now, root, etc...
Click to expand...
Click to collapse
Ahh dang, were your able to get set up? If the rom is messed up, you'll likely have to fastboot flash system, boot, and vendor IMG's for the 6.0.1 OTA you already downloaded.
I wasn't aware that you were decrypted, I would have been more expressive about not booting until things were flashed in recovery. SuperSU removes "force encrypt" from the stock boot.img so that would not have occurred.
Sent from my Nexus 5X using Tapatalk

Root N Dev Preview 5

Can anyone here point in the right direction to guide me through DP5 root? TWRP hangs on splash screen when attempting to install. Thanks!
Sent from my Nexus 6P using XDA-Developers mobile app
TWRP can't decrypt the N system right now. So it will stay stuck on the splash screen.
The most common way around here, is to decrypt your device's storage. Once, you have decrypted, you will be able to access the recovery, and flash the latest SuperSU zip for root.
DJBhardwaj said:
TWRP can't decrypt the N system right now. So it will stay stuck on the splash screen.
The most common way around here, is to decrypt your device's storage. Once, you have decrypted, you will be able to access the recovery, and flash the latest SuperSU zip for root.
Click to expand...
Click to collapse
Thanks! What's the best way of doing that!?
DLloyd said:
Thanks! What's the best way of doing that!?
Click to expand...
Click to collapse
Be advised that decrypting will wipe off your complete data, including that on the internal storage. So, backup first.
The first step would be to download the modified boot image for DP5: http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684 (Make sure that you download the correct file).
Next, reboot your device into bootloader mode and flash the boot image using the following command:
Code:
fastboot flash boot boot.img
Once that is done, you will need to decrypt using the following command (Do not mix "fastboot erase" command with "fastboot format"):
Code:
fastboot format userdata
Finally, reboot your device. Now, you will be able to access TWRP and flash SuperSU: http://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
This is great but unfortunately no joy - I'm still stuck on the TWRP splash screen when trying to enter recovery, after flashing the modified boot.img - in security it still show's encrypted?
DLloyd said:
This is great but unfortunately no joy - I'm still stuck on the TWRP splash screen when trying to enter recovery, after flashing the modified boot.img
Click to expand...
Click to collapse
Have you formatted the userdata after flashing the boot.img?
DJBhardwaj said:
Have you formatted the userdata after flashing the boot.img?
Click to expand...
Click to collapse
Yeah, exactly as advised... re-downloaded boot.img to try again, no luck
DLloyd said:
Yeah, exactly as advised... re-downloaded boot.img to try again, no luck
Click to expand...
Click to collapse
Go to Settings > Security and see if Encrypt phone option is available or greyed out. Also try reflashing TWRP.
DJBhardwaj said:
Go to Settings > Security and see if Encrypt phone option is available or greyed out. Also try reflashing TWRP.
Click to expand...
Click to collapse
It show's Encrypted, with no option to change, have tried re-flashing TWRP but nothing. How do I make sure format userdata has worked correctly? Appreciate your help!
DLloyd said:
It show's Encrypted, with no option to change, have tried re-flashing TWRP but nothing
Click to expand...
Click to collapse
Then the decryption process didn't work at all.
Download this specific boot.img: https://www.androidfilehost.com/?fid=24591023225178833
Flash it via fastboot. And then, "fastboot format userdata" and "fastboot format cache".
Finally, reboot.
DJBhardwaj said:
Then the decryption process didn't work at all.
Download this specific boot.img: https://www.androidfilehost.com/?fid=24591023225178833
Flash it via fastboot. And then, "fastboot format userdata" and "fastboot format cache".
Finally, reboot.
Click to expand...
Click to collapse
Yeah, still no joy... I'll revert to previous dev preview for root. Thanks anyway!
DLloyd said:
Yeah, still no joy... I'll revert to previous dev preview for root. Thanks anyway!
Click to expand...
Click to collapse
I rooted my Nexus 6P successfully with that specific boot.img and flash TWRP for many times.
1.flash specific boot.img
2.flash TWRP 3.0.0.0
3.get into TWRP-Wipe-format data and type "yes"
4.reboot to bootloader, flash TWRP 3.0.0.0 again.
5.get into TWRP and flash supersu
6.do not reboot or clean cache, get into wipe, and format data
7.reboot to bootloader, flash TWRP 3.0.2.0
7.get into TWRP and flash supersu
8.done
Since it seems ridiculous, it works.
DLloyd said:
Yeah, still no joy... I'll revert to previous dev preview for root. Thanks anyway!
Click to expand...
Click to collapse
Weird. I have followed the same drill about 2-3 times on DP5, and it works perfectly.
using CF Auto root works with Android N DP5. Don't need custom recovery.
XRaptor29 said:
using CF Auto root works with Android N DP5. Don't need custom recovery.
Click to expand...
Click to collapse
How did you pull that off, I recently did that and it bootloop on the cf auto root screen
jussaren said:
How did you pull that off, I recently did that and it bootloop on the cf auto root screen
Click to expand...
Click to collapse
Make sure boot loader is unlocked. I never had the CF Auto Root screen boot loop, it does boot loop a few times when booting afterwards but that's it finishing it up.
Last night I unencrypted my phone and twrp works fully so I could flash a custom kernel. It's sad that NP5 forces encryption and you have to flash the stock kernel with encryption disabled to unencrypted. I can provide a link if you're interested in that. It provides the kernel and step by step process.
Edit: didn't realize that one guy with the Droid Origin signature had the link also, I Googled and found it but this is how I unencrypted and everything last night. http://www.droidorigin.com/decrypt-nexus-6p/ Props go out to that team.
Sent from my Nexus 6P using Tapatalk

My N6P Android O couldn't flash twrp-3.1.1-0-angler.img

After I reboot my recovery, the TWRP would lost.
Try flashing it again. Failed the first time for me as well.
usually, losing twrp after boot is due to the lack of root on your system.
Are you rooted?
TWRP>IMG and supersu android O NXP6
I had the same issue i have the twrp.img you need the one your using will not stick after reboot. i tried uploading it but it exceeds the file size that's allowed on here. And i can't remeber where i got it so i can't post the link. i have that twrp file and supersu you need and they work perfect. Go to facebook and look for DroiderX that's my page i just posted the files. flash the TWRP via ADB fastboot flash recovery then drag the file into the CMD air page. Then reboot from fastboot to recovery before it reboots using the phone it'll go into TWRP then copy and paste the supersu to the phone and simply flash SU using TWRP. works perfect and it will stay after reboot i was using them but i'm still updating. The files you need are at DroiderX via FB. your welcome.
fastjohnson said:
I had the same issue i have the twrp.img you need the one your using will not stick after reboot. i tried uploading it but it exceeds the file size that's allowed on here. And i can't remeber where i got it so i can't post the link. i have that twrp file and supersu you need and they work perfect. Go to facebook and look for DroiderX that's my page i just posted the files. flash the TWRP via ADB fastboot flash recovery then drag the file into the CMD air page. Then reboot from fastboot to recovery before it reboots using the phone it'll go into TWRP then copy and paste the supersu to the phone and simply flash SU using TWRP. works perfect and it will stay after reboot i was using them but i'm still updating. The files you need are at DroiderX via FB. your welcome.
Click to expand...
Click to collapse
Ok. Here's a issue there's a storage issue and it is with TWRP that is looking for a SD so it's showing no storage so your camera will not work and you cannot download any files due it trying to place them into the SD card. So all I see is the storage issue I tried to figure it out with no success.
After flashing twrp you need to flash supersu. If you don't do it you will loose recovery
Sent from my Nexus 6P using XDA-Developers Legacy app
pister said:
After flashing twrp you need to flash supersu. If you don't do it you will loose recovery
Click to expand...
Click to collapse
You shouldn't lose recovery because that's flashed to to the recovery partition, you don't need root to keep twrp. I'd like to see if someone else could try it and the storage no be looking for a SD card I couldn't DL nothing from Android file host or anywhere except the play store it would.

Categories

Resources