my nexus 6p is not booting into rom, recovery (stock and custom).
i have a unlocked bootloader, flashed custom recovery(twrp) by fastboot but can't get in to twrp as i wanted to flash blod patch to use 4cores to work.
i tried flashing stock images of MM, Nougat, Oreo using platform tools by google but getting an error like see in the attachment:crying:.
i tried it with fastboot by manually entering commands it will flash but not use still bootlooping.
i tried toolkits like NRT & all in one toolkit by XDA member this toolkits can flash stock rom successfully but cant get boot into system, stock recovery.
help me with your answers. my status is "unlocked bootloader, fastboot working, can access bootloader but can't get into recovery from it".
getting couldn't parse partition size 0x when booting boot img through platform tools.
tell me if i did any mistake. Thank you.
You tried stock images. Does that include factory images? That erases and reflashes quite literally everything (bootloader, recovery, system, etc.)
Find them here for 6P: https://developers.google.com/android/images#angler
Santhosh Jangamgari said:
my nexus 6p is not booting into rom, recovery (stock and custom).
i have a unlocked bootloader, flashed custom recovery(twrp) by fastboot but can't get in to twrp as i wanted to flash blod patch to use 4cores to work.
i tried flashing stock images of MM, Nougat, Oreo using platform tools by google but getting an error like see in the attachment:crying:.
i tried it with fastboot by manually entering commands it will flash but not use still bootlooping.
i tried toolkits like NRT & all in one toolkit by XDA member this toolkits can flash stock rom successfully but cant get boot into system, stock recovery.
help me with your answers. my status is "unlocked bootloader, fastboot working, can access bootloader but can't get into recovery from it".
getting couldn't parse partition size 0x when booting boot img through platform tools.
tell me if i did any mistake. Thank you.
Click to expand...
Click to collapse
You didn't mention which custom recovery you flashed. Did you try the one in this thread? https://forum.xda-developers.com/t/...-death-blod-workaround-flashable-zip.3819515/
If you did and you still can't get into it, your device is likely dead from the BLOD. But to make sure you have the BLOD, flash the latest factory image first (Dec. 2018) with the latest platform tools to see if it boots... https://developer.android.com/studio/releases/platform-tools
Lughnasadh said:
You didn't mention which custom recovery you flashed. Did you try the one in this thread? https://forum.xda-developers.com/t/...-death-blod-workaround-flashable-zip.3819515/
If you did and you still can't get into it, your device is likely dead from the BLOD. But to make sure you have the BLOD, flash the latest factory image first (Dec. 2018) with the latest platform tools to see if it boots... https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
firstly i already cant boot into stock recovery from my bootloader i'm on stock os 8.1.
and now i've flashed twrp for angler from twrp website but cant boot into custom recovery too.
now i've flashed twrp image of 4cores but still can't get into recovery.
so what's the problem of this phone if my mobile cant get even into twrp i can't do blod patch if we think my device is suffering from blod issue.
do you think it may be the problem of hardware like ram,emmc, or the SD 810?
Santhosh Jangamgari said:
firstly i already cant boot into stock recovery from my bootloader i'm on stock os 8.1.
and now i've flashed twrp for angler from twrp website but cant boot into custom recovery too.
now i've flashed twrp image of 4cores but still can't get into recovery.
so what's the problem of this phone if my mobile cant get even into twrp i can't do blod patch if we think my device is suffering from blod issue.
do you think it may be the problem of hardware like ram,emmc, or the SD 810?
Click to expand...
Click to collapse
As I said in my previous post, if you can't boot into the 4core custom recovery, your device is likely dead because of the BLOD, unfortunately. If you are on stock with nothing else on your phone that might be preventing you from booting (e.g. mods, Substratum overlays, etc.) there's not much else you can do.
Is your device recognized in fastboot?
marianodelfino said:
Is your device recognized in fastboot?
Click to expand...
Click to collapse
Hi, I am havin same problem as the user above....I am on stock 7.1.2 right now. Unable to boot into TWRP, i flashed twrp-3.2.1-0-fbe-4core-angler.img and then entered recovery from bootloader screen. nothing! i also tried to do a temporary boot to my recovery via fastboot command. didn't work! I dont think my phone is that dead...but I don't see why it isnt booting into twrp...i did the flash all of stock firmware from the Google website. Any assistance? Currently I have a Pixel 2 thats not working, so i thought I would try to revive the 6P, but no luck so far.
DaKoin said:
Hi, I am havin same problem as the user above....I am on stock 7.1.2 right now. Unable to boot into TWRP, i flashed twrp-3.2.1-0-fbe-4core-angler.img and then entered recovery from bootloader screen. nothing! i also tried to do a temporary boot to my recovery via fastboot command. didn't work! I dont think my phone is that dead...but I don't see why it isnt booting into twrp...i did the flash all of stock firmware from the Google website. Any assistance? Currently I have a Pixel 2 thats not working, so i thought I would try to revive the 6P, but no luck so far.
Click to expand...
Click to collapse
thanks but no assistance required as i have sold it to another nexus 6p user for using it's spare parts.
Related
Not really sure what happened, a while ago I had an issue with a game and restored my tablet back to factory settings to fix it, but now I discover that while trying to boot into recovery mode it's not there?
I'm trying to manually install the Android 4.4 Kitkat update, got sick of waiting for the OTA since I haven't gotten it yet and really want to use 4.4, but while trying to go into recovery mode to check everything is working because I'm paranoid like that and while I was successful into booting to the bootloader, trying to go into recovery mode resulted in seeing the little android guy with the red triangle saying no command underneath it, so I'm assuming somehow my recovery is missing?
I then tried to flash stock recovery onto my tablet using the Nexus 7 Toolkit and it told me there was an error in flashing the files and that it was because my device's bootloader was locked.
All I want to do is update to Android 4.4, but how am I supposed to do that when I can't boot into recovery? I've followed all the right steps to do it, did I do something wrong by locking my bootloader and unrooting my device?
JohnathanKatz said:
Not really sure what happened, a while ago I had an issue with a game and restored my tablet back to factory settings to fix it, but now I discover that while trying to boot into recovery mode it's not there?
I'm trying to manually install the Android 4.4 Kitkat update, got sick of waiting for the OTA since I haven't gotten it yet and really want to use 4.4, but while trying to go into recovery mode to check everything is working because I'm paranoid like that and while I was successful into booting to the bootloader, trying to go into recovery mode resulted in seeing the little android guy with the red triangle saying no command underneath it, so I'm assuming somehow my recovery is missing?
I then tried to flash stock recovery onto my tablet using the Nexus 7 Toolkit and it told me there was an error in flashing the files and that it was because my device's bootloader was locked.
All I want to do is update to Android 4.4, but how am I supposed to do that when I can't boot into recovery? I've followed all the right steps to do it, did I do something wrong by locking my bootloader and unrooting my device?
Click to expand...
Click to collapse
Hi, JohnathanKatz...
Unrooting isn't the issue... it's locking the bootloader that's the problem.
If the bootloader of your device is locked, you won't be able to flash anything.
I don't use toolkits myself, but it's pretty straightforward to flash a recovery (stock or custom) using the fastboot tool...
* Unlock the bootloader with fastboot oem unlock
* Fastboot flash the recovery with fastboot flash recovery recovery.img
(...where 'recovery.img' is the name of the recovery image file to be fastboot flashed.)
Maybe there is an option in your toolkit that will unlock the bootloader again... however you do it (toolkit or fastboot), you MUST have an unlocked bootloader before you can flash a recovery.
Rgrds,
Ged.
JohnathanKatz said:
Not really sure what happened, a while ago I had an issue with a game and restored my tablet back to factory settings to fix it, but now I discover that while trying to boot into recovery mode it's not there?
I'm trying to manually install the Android 4.4 Kitkat update, got sick of waiting for the OTA since I haven't gotten it yet and really want to use 4.4, but while trying to go into recovery mode to check everything is working because I'm paranoid like that and while I was successful into booting to the bootloader, trying to go into recovery mode resulted in seeing the little android guy with the red triangle saying no command underneath it, so I'm assuming somehow my recovery is missing?
I then tried to flash stock recovery onto my tablet using the Nexus 7 Toolkit and it told me there was an error in flashing the files and that it was because my device's bootloader was locked.
All I want to do is update to Android 4.4, but how am I supposed to do that when I can't boot into recovery? I've followed all the right steps to do it, did I do something wrong by locking my bootloader and unrooting my device?
Click to expand...
Click to collapse
GedBlake said:
Hi, JohnathanKatz...
Unrooting isn't the issue... it's locking the bootloader that's the problem.
If the bootloader of your device is locked, you won't be able to flash anything.
I don't use toolkits myself, but it's pretty straightforward to flash a recovery (stock or custom) using the fastboot tool...
* Unlock the bootloader with fastboot oem unlock
* Fastboot flash the recovery with fastboot flash recovery recovery.img
(...where 'recovery.img' is the name of the recovery image file to be fastboot flashed.)
Maybe there is an option in your toolkit that will unlock the bootloader again... however you do it (toolkit or fastboot), you MUST have an unlocked bootloader before you can flash a recovery.
Rgrds,
Ged.
Click to expand...
Click to collapse
Hi guys, I actually encountered this problem a minute ago when I attempt to flash a new version of TWRP recovery on my grouper. Whenever I go to the recovery, it just shows 'No command' with a red alert of Android on it (I started to panic when I found that there's an unusual error that prevents me from entering the recovery and this is the first time that I saw this error on my flashaholic experience *btw my previous recovery was CWM) I'm currently on stock 4.4.2 with an unlocked bootloader. I have no idea what problem is causing to display that issue when attempting to enter recovery but then I left it for like 5-10mins while it's displaying that error and after that the device reboots then it just quickly enter TWRP recovery normally as is :silly: sick of that haha, silly ol grouper jesus -_-
EDIT
After entering recovery, I got stuck forever on bootloader and recovery! whenever I reboot, I always get directly enter to the recovery and it forces me to not to enter the ROM oh my god at least I can still configure the recovery so I can backup and flash another ROM :|
Hey XDA, Recently installed Paranoid Android coming from Chroma and it's not stuck in a boot loop. I can boot just fine every time besides the annoying corruption google warning, but no matter how many times I try to install TWRP it just won't let me boot into recovery. I'm using WugFresh's NRT kit. Can't seem to figure it out. Any suggestions?
carterl96 said:
Hey XDA, Recently installed Paranoid Android coming from Chroma and it's not stuck in a boot loop. I can boot just fine every time besides the annoying corruption google warning, but no matter how many times I try to install TWRP it just won't let me boot into recovery. I'm using WugFresh's NRT kit. Can't seem to figure it out. Any suggestions?
Click to expand...
Click to collapse
My suggestion is for you to fastboot flash the TWRP recovery image instead of using a toolkit. You cant see the inner workings of a toolkit and have no idea of what it is doing. The toolkit could be using the wrong commands to install a recovery image to your 6P. Go to www.twrp.me and search for the recovery image for your specific device and download the file. Next, rename the file to recovery.img Then, on your PC, navigate to the folder where you downloaded the TWRP image. Open a command prompt in that folder by pressing and holding the SHIFT KEY + RIGHT CLICK on your mouse and select OPEN A COMMAND WINDOW HERE. Boot to the bootloader on your device and connect it to your PC. Then type this:
fastboot flash recovery recovery.img
Then type this:
fastboot reboot bootloader
fastboot reboot recovery
Here is the link to download TWRP for your Nexus 6P
This will reboot your device to TWRP
All of this is based on the assumption that you have a working ADB installation and unlocked the bootloader and have USB Debugging turned on in DEVELOPER OPTIONS.
Sent from my Nexus 6 using XDA-Developers mobile app
Same thing, successful install and it won't open. Just shows the dead android when going to recovery.
carterl96 said:
Same thing, successful install and it won't open. Just shows the dead android when going to recovery.
Click to expand...
Click to collapse
You get the same results after fastboot flashing the TWRP image? I'd say your next step is to start fresh by fastboot flashing the factory images to return to a fully stock state. Then fastboot flash TWRP again.
Sent from my Nexus 6 using XDA-Developers mobile app
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
tech_head said:
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
Click to expand...
Click to collapse
I thought about that too. What is probably happening is his custom recovery is being patched by the ROM each time he boots into recovery. Thanks for picking up on that. I forgot to include that in my last post.
Sent from my Nexus 6 using XDA-Developers mobile app
tech_head said:
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
Click to expand...
Click to collapse
That's correct. After flashing TWRP the next step is reboot into the bootloader using the volume keys and power key , then from there boot into recovery using the volume keys and power key, then the phone can be rebooted from TWRP into Android and then after that TWRP should stick.
If the boot image is not patched, the ROM will overwrite TWRP once you reboot. flashing latest SU from TWRP will prevent this.
Thanks for all the replies guys! All the advice combined got it to work. I did some more research and found that Paranoid doesn't actually come preprooted like all the other roms I've been used to. So using the tool kit I just had it root it with the latest SuperSu and also flash a custom recovery. It has booted into TWRP no problems now a few times. Hopefully it will stay like this. Will keep everyone posted and appreciate the advice. Thanks XDA!
so i feel like Ive tried everything.
tried to flash a rom and gapps in twrp and phone booted to warning screen with the yellow triangle.
passes that and then goes to google splash screen with unlock icon. and then repeats to the cycle.
i have tried multiple 6.x.x builds using skipsoft toolkit with no change.
i have installed twrp and tried to flash 6.x.x rom and 7.0.0 rom.
i have tried to flash stock NBD90X 7.0.0 using nexus root toolkit.
i have tried going into stock recovery and wipe data/factory reset
i have tried minimal ABD fastboot and running the commands manually.
All have failed to change the boot looping i experience.
my phone is unlocked.
computer can see it as fastboot devices
computer CANNOT see it under abd devices
i am able to install and get into TWRP using skipsoft tookkit.
i feel like i am running out of things to flash onto the device haha
any help is appreciated.
barrackOBAMA said:
i have tried multiple 6.x.x builds using skipsoft toolkit with no change.
i have installed twrp and tried to flash 6.x.x rom and 7.0.0 rom.
i have tried to flash stock NBD90X 7.0.0 using nexus root toolkit.
i have tried going into stock recovery and wipe data/factory reset
i have tried minimal ABD fastboot and running the commands manually.
All have failed to change the boot looping i experience.
Click to expand...
Click to collapse
First, I'd recommend staying away from Toolkits, as you can't really see what's happening and diagnose issues. Since you've used fastboot/ADB commands, you know they are faster anyway. When you say your PC can't recognize your device in ADB, was your device in recovery? Make sure you're in recovery and you're ready to receive ADB commands. If you CAN see your phone with fastboot that means you're in the bootloader, whereas you have to boot into recovery to see your device via ADB.
Also, you didn't outline anything else you may have done. Did you restore from a nandroid with a buggy version of TWRP? Your issue sounds like the TWRP EFS restore bug (3.0.2-2). It effectively bricks your device, but there is a thread here that discusses it. Effectively you need to be recovery ADB mode and run a couple commands to delete your EFS partition and that will fix the issue.
More info here: http://forum.xda-developers.com/nexus-6p/help/im-stuck-google-logo-stop-reboots-twrp-t3452842
Make sure you've also installed the updated 3.0.2-3 TWRP as it will work with encrypted data and doesn't have the EFS bug.
I installed TWRP custom recovery on my Nexus 6P. I was able to boot into it ONCE. When i next tried to enter Recovery, i get a screen showing the Android Robot and the following statement: NO COMMAND
I tried to re-install TWRP using adb twice, but the result is the same.
How can i either fix TWRP, or re-install the stock recovery
I am basically a beginner here, so any help would be appreciated
If you installed the stock system image and then booted into it, it likely automatically reinstalled stock recovery also. I don't know why it does that, but it does. This is why I usually just reinstall TWRP again after each monthly update is completed.
You should use fastboot to install the images, not adb. The command should look like:
fastboot flash recovery twrp.img
I think i just worded it wrong - I used the above command (fastboot flash recovery twrp.img) to install twrp, and then, when i couldn't get back into recovery (Power - Volume Up combo just lest to screen that stated "No Command".), i used the fastboot flash recovery twrp.imp twice to try to re-install TWRP, but it didn't work
I also downloaded the latest stock Oreo ROM, copied the recovery.img file, and used fastboot.flash.recovery.img to try to re-install the stock recovery, but that didn't work either
The once time that TWRP work, it asked it I wanted to use TWRP is read only, to twice i selected NO (don't know if this matters)
Any other suggestions to fix TWPR, or re-install the stock recovery image???
When you say it didn't work, can you expand on that? Was there an error or anything?
hmodiano said:
I think i just worded it wrong - I used the above command (fastboot flash recovery twrp.img) to install twrp, and then, when i couldn't get back into recovery (Power - Volume Up combo just lest to screen that stated "No Command".), i used the fastboot flash recovery twrp.imp twice to try to re-install TWRP, but it didn't work
I also downloaded the latest stock Oreo ROM, copied the recovery.img file, and used fastboot.flash.recovery.img to try to re-install the stock recovery, but that didn't work either
The once time that TWRP work, it asked it I wanted to use TWRP is read only, to twice i selected NO (don't know if this matters)
Any other suggestions to fix TWPR, or re-install the stock recovery image???
Click to expand...
Click to collapse
If you want TWRP to stick, you need to flash either SuperSU or magisk. The Android with the exclamation mark is what stock recovery looks like.
Once you have TWRP installed and wish to keep it, you don't need to flash stock recovery in the monthly update. Just boot into TWRP after flashing update and root again.
chaoticyeshua said:
When you say it didn't work, can you expand on that? Was there an error or anything?
Click to expand...
Click to collapse
When the phone is turned on, it never progresses beyond the first screen. No error codes, it just does not proceed to boot up.
I had to buy a new phone (need it for business, but i given up on trying to install Resurrection Remix on the Nexus 6P, which was the reason I was trying to install TWPR and SuperSU. So far, I have only accomplished turning the phone into a brick door stop!!!
hmodiano said:
When the phone is turned on, it never progresses beyond the first screen. No error codes, it just does not proceed to boot up.
I had to buy a new phone (need it for business, but i given up on trying to install Resurrection Remix on the Nexus 6P, which was the reason I was trying to install TWPR and SuperSU. So far, I have only accomplished turning the phone into a brick door stop!!!
Click to expand...
Click to collapse
Use Magisk it's the better solution for root. Never had boot up issues with it just stock you have to boot once through before flashing. Custom ROMs you can flash right away.
So here is what happened. I decided to take a crack at twrp and rooting my essential phone. its fully updated to aprils patch
unlocked my bootloader. HOWEVER i never used the command fastboot flashing unlock_critical. how ever it still said my boot loaders unlocked.
installed twrp no issue (other then touch but i figured that out) installed elementalx kernal. made a backup in twrp just in case.
booted into android fine no problems. found out my wifi does not work. ok now im just giving up. found out flashing the boot img will fix it. well i flashed it via twrp and when it asked where i said to the boot.
now my phone boot loops. i cant get into twrp. only a default recovery mode for android. i can get into the boot loader but im scared because ADB cant find my device anymore. trying to wipe deivce makes it reboot and boot loop again.
am i screwed? i dont care about the data but its 3am and i think i really messed up my phone
xhakz said:
So here is what happened. I decided to take a crack at twrp and rooting my essential phone. its fully updated to aprils patch
unlocked my bootloader. HOWEVER i never used the command fastboot flashing unlock_critical. how ever it still said my boot loaders unlocked.
installed twrp no issue (other then touch but i figured that out) installed elementalx kernal. made a backup in twrp just in case.
booted into android fine no problems. found out my wifi does not work. ok now im just giving up. found out flashing the boot img will fix it. well i flashed it via twrp and when it asked where i said to the boot.
now my phone boot loops. i cant get into twrp. only a default recovery mode for android. i can get into the boot loader but im scared because ADB cant find my device anymore. trying to wipe deivce makes it reboot and boot loop again.
am i screwed? i dont care about the data but its 3am and i think i really messed up my phone
Click to expand...
Click to collapse
Are you still bootloader unlocked?? Can flash files via fastboot? If you can run the command "fastboot flashing unlock_critical" and then flash bts from this thread https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Tech_Savvy said:
Are you still bootloader unlocked?? Can flash files via fastboot? If you can run the command "fastboot flashing unlock_critical" and then flash bts from this thread https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Click to expand...
Click to collapse
hey hope all is well im sorry for the late reply. i was able to figure everything out i flash the wrong boot.img and twrp its not perm on my device. I saw a threat that lets you go back to stock and has aprils build. thanks for your help tho!!!!!