[Q] Help! Can't boot after updating TWRP - Nexus 10 Q&A, Help & Troubleshooting

so, my tablet hadn' tbeen used or turned on for a couple years and i decided to update it, get it working again on the latest rom.
my tablet is rooted/unlocked. when i boot up the lock icon is unlocked "lock state: unlocked", bootloader version: MANTALJ12, h/w version: 8, product name: manta, reboot mode flag: recovery
i updated supersu, then flashed the latest twrp from the nexus 10 chroma rom twrp download link: twrp-2.8.7.1-shamu.img ... using flashify. there were no errors and said successful
i then rebooted and it will only boot to the download mode, every other option i try (start, recovery) only takes me to a black screen.
i don't understand what went wrong? what can i do to fix?
thanks

Hello! Shamu is the code name of the nexus 6. You have broken your recovery. But you can fix it with Odin through download mode.
Envoyé de mon One X en utilisant Tapatalk

Khaon said:
Hello! Shamu is the code name of the nexus 6. You have broken your recovery. But you can fix it with Odin through download mode.
Envoyé de mon One X en utilisant Tapatalk
Click to expand...
Click to collapse
thanks for the reply! how to fix with odin?
also... i saw that it was for nexus 6..... BUT i do not see a nexus 10 version? this is the rom i want to update to, it points to the nexus 6 file! http://forum.xda-developers.com/nexus-10/development/rom-chroma-04-05-2015-layers-t3074502 see "Instructions Pre-requisites: unlocked bootloader, latest TWRP recovery". Latest TWRP, goes to Shamu file. Why does it point to the nexus 6 file, if it's not correct??
Also, before i updated using flashify, i tried using TWRP Manager. I chose nexus 10 in the device area, and it downloaded the EXACT SAME Shamu twrp file...

ballgum said:
thanks for the reply! how to fix with odin?
also... i saw that it was for nexus 6..... BUT i do not see a nexus 10 version? this is the rom i want to update to, it points to the nexus 6 file! http://forum.xda-developers.com/nexus-10/development/rom-chroma-04-05-2015-layers-t3074502 see "Instructions Pre-requisites: unlocked bootloader, latest TWRP recovery". Latest TWRP, goes to Shamu file. Why does it point to the nexus 6 file, if it's not correct??
Also, before i updated using flashify, i tried using TWRP Manager. I chose nexus 10 in the device area, and it downloaded the EXACT SAME Shamu twrp file...
Click to expand...
Click to collapse
anyway, i got it fixed. i downloaded the MANTA recovery for nexus 10 and flashed using heimdall. its now booting to twrp.
but why do they all link to the wrong recovery file???! this is dangerous, no?? links should be fixed!!!

YOU are in charge of your device. Lesson learned my friend. Now go and alert people to update their links. You have my thanks.
Sent from my Nexus 5 using Tapatalk

Related

[Q] Can't flash stock rom into my Nexus

I have my Nexus 7 dead after an attempt to flash it with stock rom 4.1.2 using the latest version Nexus 7 Toolkit (the donor version)
Everything goes well until the Toolkit attemps to flash the bootloader Image. Using ADB, the toolkit recognizes my Nexus serial number, the toolkit indicated that it is in fastboot mode (the screen with the stomach-opened android figure) and with messages confirming that I am in fastboot mode with an unlocked lock state)..
After selecting to flash with the latest stock rom downloaded from google using the the toolkit, wipes are conducted and the toolkit can erase boot, cache, recovery, system and userdata..
So communications between my PC and the Nexus are going well
But at the moment to send the bootloader, it stops and I am not going further of this
Any hint?
I just flashed stock and relocked the boot loader on mine. I used the wugfresh toolkit. Very easy to use and worked great. It downloaded the 4.1.1 and flashed it. When I powered on the tablet it auto updated to 4.1.2 ota. Maybe give that toolkit a try.
Sent from my Nexus 7
http://forum.xda-developers.com/showthread.php?t=1907796
Travisdroidx2 said:
http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
+1
Sent from my BAKED Nexus
For whatever reason, none of the stock roms downloaded by Nexus Toolkit worked for me (neither the 4.1.1 nor the 4.1.2 versions)
However, the 4.1.2 file downloaded from the link shown within the above URL had a different size and worked nicely
My Nexus 7 is working again. Thank to all of you..
Enviado desde mi Nexus 7 usando Tapatalk 2

TWRP update - GooManager

im trying to use goomanager to update twrp to version openrecovery-twrp-2.6.3.1-grouper.img and it keeps timing out on the webpage (webpage not available).
i dont have access to a computer currently.. is there another way to upgrade twrp? is there a zip i can flash from recovery? (running a older ver of twrp)
joshag said:
im trying to use goomanager to update twrp to version openrecovery-twrp-2.6.3.1-grouper.img and it keeps timing out on the webpage (webpage not available).
i dont have access to a computer currently.. is there another way to upgrade twrp? is there a zip i can flash from recovery? (running a older ver of twrp)
Click to expand...
Click to collapse
Same here. Goo hasn't worked for me for several months now. Pretty much given up on it.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
joshag said:
im trying to use goomanager to update twrp to version openrecovery-twrp-2.6.3.1-grouper.img and it keeps timing out on the webpage (webpage not available).
i dont have access to a computer currently.. is there another way to upgrade twrp? is there a zip i can flash from recovery? (running a older ver of twrp)
Click to expand...
Click to collapse
Hi, joshag....
If your Nexus 7 is already rooted, you can use the apps, Flash Image GUI or Flashify to flash a Custom Recovery directly from the Nexus 7 itself.
Just install one of them (personally I prefer Flashify)... download the TWRP Recovery Image file appropriate to your particular Nexus 7 (links below)... and then use Flashify or Flash Image GUI... the on screen instructions are pretty self explanatory, just ensure you pick the FLASH RECOVERY option, and then navigate to the folder on your Nexus 7 where the TWRP recovery image downloaded to... (usually the /download folder).
So... no PC or fastboot required... just a rooted Nexus 7. (If you aren't already rooted, you're out of luck I'm afraid).
I use this method myself quite frequently, particularly when I can't be bothered booting up my laptop.
Links for TWRP Custom Recovery Images for Nexus 7 (2012)
For WiFi only model...
http://techerrata.com/browse/twrp2/grouper
For WiFi & 3G model...
http://techerrata.com/browse/twrp2/tilapia
Hope this helps.
Rgrds,
Ged.
That was easiest/most concise explanation.
Sent from my Nexus 7 using xda app-developers app

Updating TWRP via TWRP n recovery

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

... Now I can only boot to TWRP!

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

supersu - maybe these make bootloop?

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..

Categories

Resources