Keen to keep up-to-date,I upgraded my N10 to 3.1.0 TWRP. After wrongly choosing to update to 'boot', not to 'recovery' I find that I can only boot to TWRP, no matter what I do or choose.
One solution I'm about to try again is to adb put a TWRP 3.0.2 img into /scard/Downloads and hope it can be flashed and replace the upgrade. This failed last night with an error message I was to tired to note down. Something about DNS, I think...
Any sure-fire solutions to this quandary, folks ?
Sent from my Nexus 10 using Tapatalk
Never encountered this myself so just speculating.
Download the latest factory image from Google, extract the bootloader file and put it at /sdcard/
I think in TWRP you have the option to install an install an IMG file, select bootloader and install.
Sent from my YD201 using Tapatalk
Related
I am currently running stock 4.4 on my Nexus 4. FTP doesn't work with 4.4 and I don't like that, I use my FTP a lot. Now did I get a notification about half an hour ago that there was an update (4.4.2) available. I chose to update and pressed the restart an install updates button.
But my N4 didn't install the update, it simply booted into TWRP recovery. So I chose reboot > system and my phone just booted. Just not to 4.4.2, but to 4.4. When I check for updates in the settings it says that there are no updates available. Does anyone know how to fix this?
Sent from my Nexus 4 using xda app-developers app
thedjdoorn said:
I am currently running stock 4.4 on my Nexus 4. FTP doesn't work with 4.4 and I don't like that, I use my FTP a lot. Now did I get a notification about half an hour ago that there was an update (4.4.2) available. I chose to update and pressed the restart an install updates button.
But my N4 didn't install the update, it simply booted into TWRP recovery. So I chose reboot > system and my phone just booted. Just not to 4.4.2, but to 4.4. When I check for updates in the settings it says that there are no updates available. Does anyone know how to fix this?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Download the update to your pc from here. If you are running 4.4.1, then download from here.
Copy the update.zip to your phone
Boot into TWRP recovery. Choose install zip from sdcard, navigate and select the update.zip and flash. Re-flash the SuperSU/Superuser binaries if you want to keep root (not flashing this, might replace twrp with the stock recovery ). Reboot.
If you have modified ANY system file, then this won't work and you will have to revert to stock first.
Ibrahim.Rahman said:
Download the update to your pc from {I am not allowed to post links yet}.. If you are running 4.4.1, then download from {I am not allowed to post links yet}.
Copy the update.zip to your phone
Boot into TWRP recovery. Choose install zip from sdcard, navigate and select the update.zip and flash. Re-flash the SuperSU/Superuser binaries if you want to keep root (not flashing this, might replace twrp with the stock recovery ). Reboot.
If you have modified ANY system file, then this won't work and you will have to revert to stock first.
Click to expand...
Click to collapse
Didn't work but i've found a solution myself.
To update to 4.4, I've flashed the factory image without wiping the cache.
I used the following command lines
fastboot flash bootloader bootloader*.img
fastboot reboot-bootloader
fastboot flash radio radio-*.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Maybe that is the reason why it doesn't work. I've downloaded the 4.4.2 factory image now and flashed it like this, it worked.
I am relative new to Android and rooting so bear with me if I am saying the wrong things.
I've just gotten a Nexus 7 (2013, WiFi - "flo") and tried to root it on Marshmallow (MRA58V). I followed all the instructions - installed Google drivers, set up ADB/Fastboot using "Minimal ADB and Fastboot", unlocked bootloader, flashed custom boot.img, and then flashed TWRP (and CWMR) with Fastboot. When I then boot into TWRP, I cannot navigate to /sdcard where SuperSU is placed. When I check the log, it comes up with "cannot mount /boot, /system, /cache..." etc. The same thing happens in CWMR. I've tried to use NRT to root instead and the same problem happens. Am I missing something here? I've even downgraded to Lollipop with NRT and the same thing happened again. How can I not even get TWRP to work?! This is driving me insane!!!
Thanks for your help in advance.
yh248 said:
I am relative new to Android and rooting so bear with me if I am saying the wrong things.
I've just gotten a Nexus 7 (2013, WiFi - "flo") and tried to root it on Marshmallow (MRA58V). I followed all the instructions - installed Google drivers, set up ADB/Fastboot using "Minimal ADB and Fastboot", unlocked bootloader, flashed custom boot.img, and then flashed TWRP (and CWMR) with Fastboot. When I then boot into TWRP, I cannot navigate to /sdcard where SuperSU is placed. When I check the log, it comes up with "cannot mount /boot, /system, /cache..." etc. The same thing happens in CWMR. I've tried to use NRT to root instead and the same problem happens. Am I missing something here? I've even downgraded to Lollipop with NRT and the same thing happened again. How can I not even get TWRP to work?! This is driving me insane!!!
Thanks for your help in advance.
Click to expand...
Click to collapse
sounds like either one of two things:
1. maybe you are flashing the wrong twrp recovery (is the codename correct? )
2. have you a complete new model? maybe it has a new partition table (wich means you will need a new twrp)
Sent from my Xperia T using XDA Free mobile app
Thanks for your reply. It is a brand new model I guess (bought it a few days ago for black Friday). It came with Lollipop 5.0 out of the box. I did use the latest TWRP for Flo so I guess it must be #2 (new partition tables). Do you know if it is still being developed? Last update seemed to be in July. Also, are there any alternatives? Ive tried the new Cyanogen Recovery which could access /sdcard but wouldn’t recognise SuperSU Zip to install.
Thanks again.
I had TWRP 3.0.1 so I downloaded the latest TWRP 3.0.2 IMG file and booted to Recovery and selected the image and then selected Recovery as to where to flash and it flashed no errors so I backed out and went to reboot and selected Recovery and it rebooted to bootloader and when I stroll volume keys to Recovery then power to select it just hangs there I have to do a power long press to get it to reboot back to Android. Any ideas why Recovery will not load now ?
I'm on MHC19l
Stock rooted no mods
System rooted
Sent from my Nexus 6P using Tapatalk
A bad flash, perhaps? Have you checked the MD5 after downloading?
Possible bad download but at this point I can't reflash the recovery until I can fast boot .. I gotta order another Type C to USB to connect the phone to the computer for fast boot grrrrr...
Thx
Sent from my Nexus 6P using Tapatalk
Glad to help! Next time make sure you check MD5 before flashing (even then an occasional bad flash could still cause trouble, but hey, what's the choice here?) You can still boot to Android normally, no?
Sidenote: anyone knows if a micro B to C adaptor would work with fastboot?
Yeah I can still boot to Android fine jus when I select recovery n bootloader it hangs in bootloader. I have to hard reset to get out of bootloader mode lol....
Jus sucks BC now I gotta wait until friday to order a Type C to USB cable to use the computer to fast boot TWRP to recovery.. :/
I jus got this 6P 4 days ago coming from the HTC M9 Developer Edition I decided to go with the 6P over the M10 even though I would have gotten $100 off the M10 for not using my UhOh protection.
But I'm currently Stock w/ root until I figure out or understand this whole Vender thing when flashing Roms.. Jus being very cautious.
With HTC you jus flash the ROM you want but here some say jus flash the ROM and some say flash the Vender matching the ROM.. Lol,..
Sent from my Nexus 6P using Tapatalk
About the vendor img... Not too sure about the whole technical details behind them, but I just flash them every time Google updates them (think monthly security updates), at the very least to get rid of the 'vendor img outdated' popup. You don't need to flash a new vendor img everytime you update/switch ROMs, but only when there's a new vendor.
I usually just flash recovery with flashify. Never had an issue doing it that way. Or fastboot.
Sent from my Nexus 6P using XDA-Developers mobile app
scoot0073 said:
I had TWRP 3.0.1 so I downloaded the latest TWRP 3.0.2 IMG file and booted to Recovery and selected the image and then selected Recovery as to where to flash and it flashed no errors so I backed out and went to reboot and selected Recovery and it rebooted to bootloader and when I stroll volume keys to Recovery then power to select it just hangs there I have to do a power long press to get it to reboot back to Android. Any ideas why Recovery will not load now ?
I'm on MHC19l
Stock rooted no mods
System rooted
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
People have been facing the same issue all around. Even I did, last night after updating to N Preview. Anyhow, the only solution I know right now is to have a decrypted filesystem (disable encryption), for TWRP to boot and work properly.
Yeah disable encryption I believe I read requires booting into recovery and wiping User Data or something alone those line's.
Unless there's a option in Android settings to disable it idk yet as I jus had the phone a few day's.
But so far I happy with my decision to get the 6P over the M10 even if the 6P is 4 or 5 moths old...
Sent from my Nexus 6P using Tapatalk
OK I got the latest TWRP Recovery flash . I used Flashify app and it flashed the recovery and I got a working recovery now..
Sent from my Nexus 6P using Tapatalk
Pain-N-Panic said:
I usually just flash recovery with flashify. Never had an issue doing it that way. Or fastboot.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank u so much that fixed my borked recovery thank you again
Sent from my Nexus 6P using Tapatalk
Some files got corrupted on my bullhead and i tried flashing stock firmware but after flashing radio and bootloader it gave me "recovery.sig" cannot be found error.
I tried manually flashing too and it worked great but it didn't flash at all.
Then i tried nexus root toolkit and it flashed successfully. hence my problem was solved.
anyone having issues flashing stock firmware to their nexus should use nexus root toolkit.
Hassan_Elyas said:
Some files got corrupted on my bullhead and i tried flashing stock firmware but after flashing radio and bootloader it gave me "recovery.sig" cannot be found error.
I tried manually flashing too and it worked great but it didn't flash at all.
Then i tried nexus root toolkit and it flashed successfully. hence my problem was solved.
anyone having issues flashing stock firmware to their nexus should use nexus root toolkit.
Click to expand...
Click to collapse
What file did you download and notice these issues with? Were you using fastboot or ADB sideload?
Recovery.sig is only included in the full OTA image zip and the zip file is not meant to be unzipped and flashed. You install via ADB sideload. When flashing a factory image (not OTA image), the recovery.img would not produce that issue via fastboot.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
What file did you download and notice these issues with? Were you using fastboot or ADB sideload?
Recovery.sig is only included in the full OTA image zip and the zip file is not meant to be unzipped and flashed. You install via ADB sideload. When flashing a factory image (not OTA image), the recovery.img would not produce that issue via fastboot.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Stock firmware which i downloaded from google's site. i don't know why it gave me that error . Maybe something was wrong.
Hi
i saw something interest and maybe you can confirm these, i just upgrade my 6P - upgrade=install from scratch full image from dev site.
and just after instalation i install the supersu zip (originally from site)-after i have the TWRP, i got bootloop.
than i just run the flash all .bat, and like a magic everything is worked, so i tried to install again the zip of super SU and ...bootloop.
it's just leave me the option of install from the app store, is the way of instalation make something?
thanks
I7210I said:
Hi
i saw something interest and maybe you can confirm these, i just upgrade my 6P - upgrade=install from scratch full image from dev site.
and just after instalation i install the supersu zip (originally from site)-after i have the TWRP, i got bootloop.
than i just run the flash all .bat, and like a magic everything is worked, so i tried to install again the zip of super SU and ...bootloop.
it's just leave me the option of install from the app store, is the way of instalation make something?
thanks
Click to expand...
Click to collapse
I think your bootloop situation is more software-driven. Most of the people that talk about boot loops with the Nexus 6p have a hardware issue like I do.
Sent from my Nexus 6P using Tapatalk
funnel71 said:
I think your bootloop situation is more software-driven. Most of the people that talk about boot loops with the Nexus 6p have a hardware issue like I do.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
I7210I said:
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
Click to expand...
Click to collapse
Well keep in mind at the moment I am not rooted. As for updates when I used to be rooted I would flash the stock images for the system recovery bootloader and vendor partitions first. After that was done route would be erased and I could take the OTA update. I should also mention that I have not updated to Oreo. Given the hardware difficulties with my phone I've chosen to stay at 7.1.2
Sent from my Nexus 6P using Tapatalk
so...i'm in 8.1 and these is the conclusion in that state after few tests.
I7210I said:
so...i'm in 8.1 and these is the conclusion in that state after few tests.
Click to expand...
Click to collapse
I would tend to agree with you either you have a version that is not compatible with 8.1 or perhaps you just downloaded a corrupted zip file. I can't speak for root on 8.1 because I don't have that version but I think you've done enough testing to prove your theory that it's the zip that cause your boot loop
Sent from my Nexus 6P using Tapatalk
What SuperSU version did you use?
What version TWRP?
I have been on 8.1 Stock with SuperSU and I did not get bootloops whatsoever.
Sent from my Nexus 6P using Tapatalk
stankyou said:
What SuperSU version did you use?
What version TWRP?
I have been on 8.1 Stock with SuperSU and I did not get bootloops whatsoever.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Use Magisk it's latest greatest. Just install the Magisk app from apkmirror and it will prompt to download flaahable zip. As far as TWRP 3.2.1-0 I believe is latest.
I7210I said:
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
Click to expand...
Click to collapse
What are you trying to say? The bootloop you are talking about is different from hardware bootloop of death in nexus 6p.
Supersu works fine for everyone,if its bootlooping for you thn you are doing something wrong or flashing wrong supersu zip.
The most of the reported bootloop of death users are not rooted.
the twrp is 3.2.1 and i used now the Magisk and it works.
the way i used is :
fastboot format userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery <filename>.img
fastboot flash system system.img
Fastboot flash vendor vendor.img
ofcurse with the right names of files..