Bootloop and cannot boot into recovery - Nexus 6P Q&A, Help & Troubleshooting
Hi Guys,
My nexus 6p is running stock firmware with no root or any custom rom or recovery.
Suddenly, while i was browsing the internet on my phone, it restarted and went into bootloop through the google logo.
I tried to boot into bootloader and then tried to go to recovery mode from the bootloader but it went again into bootloop.
I then tried to download the latest image and tried to flash it but was surprised that i cannot unlock the bootloader except from inside phone settings (if it was working) which is very inconvenient.
Any thoughts as recovery mode is not working to be able to reset to factory settings and cannot flash any rom or original firmware as it's locked.
Are you saying that you did not have OEM Unlock turned on or have USB debugging enabled in developer options? Is your phone recognized by ADB when you are connected to your PC? When you enter the Bootloader, can you select ADB Sideload with bootlooping? I have been trying to help a couple of people with this issue for the past few days Also, when you enter the Bootloader does your 6P show DOWNLOAD MODE is Disabled?
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Are you saying that you did not have OEM Unlock turned on or have USB debugging enabled in developer options? Is your phone recognized by ADB when you are connected to your PC? When you enter the Bootloader, can you select ADB Sideload with bootlooping? I have been trying to help a couple of people with this issue for the past few days Also, when you enter the Bootloader does your 6P show DOWNLOAD MODE is Disabled?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, i never enabled it because i did not know it exists. My phone is not detected by ADB and download mode is disabled.
How can i can selected ADB sideload if i cannot enter recovery mode
met911 said:
Yes, i never enabled it because i did not know it exists. My phone is not detected by ADB and download mode is disabled.
How can i can selected ADB sideload if i cannot enter recovery mode
Click to expand...
Click to collapse
Try this:
Press and hold the POWER BUTTON + VOLUME UP and continue to hold them. Watch the screen. Does it still continue to bootloop or does a screen show up that says "NO COMMAND"? If the NO COMMAND screen is displayed, let your device sit without doing anything. There are some devices that have sat at this screen, rebooted on its own and booted back into the OS. Let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Try this:
Press and hold the POWER BUTTON + VOLUME UP and continue to hold them. Watch the screen. Does it still continue to bootloop or does a screen show up that says "NO COMMAND"? If the NO COMMAND screen is displayed, let your device sit without doing anything. There are some devices that have sat at this screen, rebooted on its own and booted back into the OS. Let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
It showed no command once and then rebooted into bootloop again.
Tried it again after and it did not show no command. just went into bootloop.
met911 said:
It showed no command once and then rebooted into bootloop again.
Tried it again after and it did not show no command. just went into bootloop.
Click to expand...
Click to collapse
Once the NO COMMAND showed up on the screen did you release the buttons or continue to hold them? I.should have clairified that before hand. Sorry.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Once the NO COMMAND showed up on the screen did you release the buttons or continue to hold them? I.should have clairified that before hand. Sorry.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I continued to hold them at the beginning but nothing happened. it was rebooting again and again without showing the no command. once i released them, then the no command showed up.
met911 said:
I continued to hold them at the beginning but nothing happened. it was rebooting again and again without showing the no command. once i released them, then the no command showed up.
Click to expand...
Click to collapse
After the No COMMAND showed up, did it continue to bootloop by itself after sitting at the No COMMAND screen?
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
After the No COMMAND showed up, did it continue to bootloop by itself after sitting at the No COMMAND screen?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes. i left it as you mentioned and it went into bootloop. Even the one time i managed to get it in recovery mode and made factory reset and wipe cache partition. I did not get it to be detected by ADB as debugging was not enabled in the setting menu.
This recovery mode is really useless if you cannot start the phone. Its supposed to be RECOVERY mode but its completely useless.
Previously, you could just unlock the bootloader and flash new image. Now it must be enabled in the setting in a phone that does not even work.
The only option you have with a locked Bootloader is to attempt to ADB sideload a zip or OTA and that's only if you could select adb sideload from recovery. When you open the Bootloader does your device show that DOWNLOAD MODE is DISABLED? Also, have you checked to see if you can issue any fastboot commands while in the Bootloader?
Sorry, I asked about the Download Mode showing disabled again. I've read so much about this and so many threads I forgot. Try this for me:
Open the Bootloader
Type this fastboot command:
Fastboot oem ramdump enable
Fastboot reboot Bootloader
Power down
Power up to the Bootloader
Try selecting adb sideload again and see what it does.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
The only option you have with a locked Bootloader is to attempt to ADB sideload a zip or OTA and that's only if you could select adb sideload from recovery. When you open the Bootloader does your device show that DOWNLOAD MODE is DISABLED? Also, have you checked to see if you can issue any fastboot commands while in the Bootloader?
Sorry, I asked about the Download Mode showing disabled again. I've read so much about this and so many threads I forgot. Try this for me:
Open the Bootloader
Type this fastboot command:
Fastboot oem ramdump enable
Fastboot reboot Bootloader
Power down
Power up to the Bootloader
Try selecting adb sideload again and see what it does.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
You are asking the same questions again. YES, download mode is disabled.
after the first command, it tells me "locked device to enable ramdump"
I tried adb sideload but did not work because its not enabled in the phone settings as i already mentioned before.
I apologize for asking the same questions. I got confused on which thread I was posting in. I have been trying to help someone else with the same issue.
Sent from my Nexus 6 using XDA-Developers mobile app
Adb sideload won't work in bootloader mode, only in recovery. The only thing that will work in bootloader mode is fastboot but seeing as the bootloader is locked (with no way to unlock it) you can't use fastboot. If you can't get into recovery there's nothing you can do except send the phone for repair.
But how can anyone troubleshoot any phone if the OS is not working. This new way of security is simply impossible.
So if the OS fails like my case, i am screwed.
met911 said:
But how can anyone troubleshoot any phone if the OS is not working. This new way of security is simply impossible.
So if the OS fails like my case, i am screwed.
Click to expand...
Click to collapse
I'm not sure what you mean by new security, this has been standard fare for some time now. I'm sure if your phone was stolen you'd be thanking this security feature because it'd mean that the thief couldn't possibly access your data.
People in the know usually go into the settings menu and tick the "allow oem unlocking" box even if they don't plan on unlocking the bootloader at that time, there's a slight security risk but it's insurance against situations like this.
And what you're saying isn't entirely true; even if the OS fails the phone can usually still boot into recovery which would mean being able to revive it via adb sideload. What you're experiencing is relatively unusual, not being able to boot into the recovery as well as the OS means you're basically screwed.
If there's anything to take away from this it's that electronic devices fail sometimes. If you can handle the security risk it's worth ticking that box in the settings menu, or even completely unlocking the bootloader, to give yourself some insurance against these rare situations.
Same problem
met911 said:
Hi Guys,
My nexus 6p is running stock firmware with no root or any custom rom or recovery.
Suddenly, while i was browsing the internet on my phone, it restarted and went into bootloop through the google logo.
I tried to boot into bootloader and then tried to go to recovery mode from the bootloader but it went again into bootloop.
I then tried to download the latest image and tried to flash it but was surprised that i cannot unlock the bootloader except from inside phone settings (if it was working) which is very inconvenient.
Any thoughts as recovery mode is not working to be able to reset to factory settings and cannot flash any rom or original firmware as it's locked.
Click to expand...
Click to collapse
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
ADEORA said:
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
Click to expand...
Click to collapse
My phone just did the same thing yesterday morning. I'm currently waiting for Hauwei support to get online because Google wont do anything for me since it's been about 13 months (Google only offers a 12 month warranty). Hoping for the best, but without being able to access Recovery makes me very doubtful.
ADEORA said:
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
Click to expand...
Click to collapse
uodii said:
My phone just did the same thing yesterday morning. I'm currently waiting for Hauwei support to get online because Google wont do anything for me since it's been about 13 months (Google only offers a 12 month warranty). Hoping for the best, but without being able to access Recovery makes me very doubtful.
Click to expand...
Click to collapse
You both might want to take a read of http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921 - it has many people who have experienced the issue you both have. tl;dr - you'll probably need to contact goog/huwaei for a replacement.
Had the exactly same issue the day before yesterday, tried every possible way to flash different versions of images, none worked. My warranty expired 2 weeks ago, so both google and huawei told me that I am on my own for this.
Wow.. I feel for you all. I've had the exact same thing happen some weeks ago, phone freezing, then reboot, then couple of days later bootloop, then able to flash and reinstall, then after one final bootloop with the phone unable to 'take' the flashing through recovery, etc, etc. I've been playing with xda since the days of Froyo and that was the first time I had to send a phone back under warranty.
I was just about to try to manually rebuild the whole partition system at the block level but I'm glad I could send it for repairs. You might have a chance if you go as low as that. Good luck
* edit * I got the TWRP to stick by flashing it in Fastboot a couple of times in a row at that time, then I was adapting a Linux guide on reformatting and repairing drives partitions and all that through an adb shell.I did not get it to work yet before sending it, though.
Related
Please help! Nexus 10 stuck on google X during failed root :(
Hey guys I tried the one-click root toolkit for mac from android rootz. Something apparently has gone wrong during the root and I got some error messages and it didn't proceed. Next thing I know the nexus is stuck on google X logo and that's it. It won't load. I tried to recover through the recovery mode a couple of times but now I get the red warning sign when I go into recovery mode. This is only the second day I've had the nexus for. I feel like crying. Please Help
When the red sign appears press the volup down buttons and power button randomly until you get into recovery then factory reset
My 7 and 10 both did that. Just hold power until it turns off, then boot a recovery, wipe everything except system and reboot. It'll come up ok. Sent from my Nexus 10 using Tapatalk HD
I'm having the same issue. However, the recovery I have installed is the non-functional CWM. So I can't factory reset. (I managed to once before CWM bombed, but it didn't change anything.) I've tried several options via the toolkit. After fighting with the app all day it's finally wound up just saying it can't find adb? (I have a growing dislike for this app and have since uninstalled it.) Adb is right where it belongs and seems to run fine from cmd. I also can't seem to flash anything via fastboot for some reason. The device throws "failinvaild id command" and fastboot immediately crashes on my laptop. I managed to get it unlocked. However, I'm unable to flash anything to straighten it out... Any help would be great.
scooterbaga said: I'm having the same issue. However, the recovery I have installed is the non-functional CWM. So I can't factory reset. (I managed to once before CWM bombed, but it didn't change anything.) I've tried several options via the toolkit. After fighting with the app all day it's finally wound up just saying it can't find adb? (I have a growing dislike for this app and have since uninstalled it.) Adb is right where it belongs and seems to run fine from cmd. I also can't seem to flash anything via fastboot for some reason. The device throws "failinvaild id command" and fastboot immediately crashes on my laptop. I managed to get it unlocked. However, I'm unable to flash anything to straighten it out... Any help would be great. Click to expand... Click to collapse Watch this video starting at the 6:30 mark. http://www.youtube.com/watch?v=YtLvlrUDB04
bg1906 said: Watch this video starting at the 6:30 mark. http://www.youtube.com/watch?v=YtLvlrUDB04 Click to expand... Click to collapse Thanks for the info. My situation wasn't quite the same as my CWM was the real issue, which wouldn't run long enough to allow for the factory reset boot-loop solution. Kept at it and managed to get CWM to finish the individual formats/resets one at a time. With a now bootable device, I'm off to replace the recovery... Thanks again.
locked bootloader wont unlock
Hi everyone. Here is the deal im having with my nexus 7 (not the 2013 model) with jop40d.zip. The person I purchased from didnt tell me it was soft bricked. It seems as though he tried to root it but failed while at the same time relocked the bootloader. So I've tried almost everything in my mind to get it back to normal. It wont let me adb sideload the stock rom it says "installation aborted" or any other rom. Also when i boot up it goes directly to the bootloader which gives me the options start, restart bootloader, recovery mode, power off. start obviously does nothing. restart bootloader just for some reason turns the device off, recovery mode takes me the caution sign where i can adb sideload or factory restore. factory restore hangs and doesn't do anything then shuts off. adb sideload always fails when loading up the zip files. i factory restored the cache. I'm not sure what to do anymore. I spent a fair amount of money on this device but now it all seems like a mistake. Can anyone who has fixed this issue help me out? I would deeply and greatfully appreciate it. -Cheers
truebattleaxe said: Hi everyone. Here is the deal im having with my nexus 7 (not the 2013 model) with jop40d.zip. The person I purchased from didnt tell me it was soft bricked. It seems as though he tried to root it but failed while at the same time relocked the bootloader. So I've tried almost everything in my mind to get it back to normal. It wont let me adb sideload the stock rom it says "installation aborted" or any other rom. Also when i boot up it goes directly to the bootloader which gives me the options start, restart bootloader, recovery mode, power off. start obviously does nothing. restart bootloader just for some reason turns the device off, recovery mode takes me the caution sign where i can adb sideload or factory restore. factory restore hangs and doesn't do anything then shuts off. adb sideload always fails when loading up the zip files. i factory restored the cache. I'm not sure what to do anymore. I spent a fair amount of money on this device but now it all seems like a mistake. Can anyone who has fixed this issue help me out? I would deeply and greatfully appreciate it. -Cheers Click to expand... Click to collapse also I wanted to add. I have the android sdk installed and all drivers installed properly. as well as adb/fastboot.
Stop trying to use adb, follow the sticky at the top that says flashing a factory rom using fastboot/return to stock. If you can't type fastboot devices and get a serial number return then the drivers are not installed properly. Sent from my Nexus 7(2012) that has zero issues.
SlowCobra96 said: Stop trying to use adb, follow the sticky at the top that says flashing a factory rom using fastboot/return to stock. If you can't type fastboot devices and get a serial number return then the drivers are not installed properly. Sent from my Nexus 7(2012) that has zero issues. Click to expand... Click to collapse hey slow cobra. yes fastboot does recognize the device. however fastboot oem unlock doesn't do anything.
[HELP PLEASE!] Forgot encryption password cannt recover!
Hello XDA First off let me tell you what im running. Nexus 4 running Cyanogenmod 11 with USB debugging turned off. So my I bought this phone used and allowed my brother to install a custom ROM on it. I also gave him the OK when he asked me if he can encrypt the phone. (No problem, what can go wrong right?) Well it turns out nothing did go wrong but the only thing is when I went to go change the password I only changed the SCREEN LOCK password not the encryption password thinking they were the same. When i went to go boot up my phone today it asked for the encryption password but wont accept the lock password. Went to ask my brother for the password and he said he forgot because he had already told it to me. Now im stuck with a possible broken phone =[ Steps I have tired: after painstaking hours on google and XDA looking for an answer - I have tired to download TWRP but cant install the zip file because i cant get the fastboot to show USB FASTBOOT - I have tired recovery mode with ClockworkMod Recovery v6.0.4.7 and tired the cwipe data/ factory reset with no luck Can someone please guide me in the right direction on what I should do to fix my phone? Many Thanks!!
Flash the factory image in fastboot. It'll wipe the device and return it to like new. If you don't have fastboot Google 15 second adb install xda Sent from my Nexus 5 using XDA Free mobile app
jd1639 said: Flash the factory image in fastboot. It'll wipe the device and return it to like new. If you don't have fastboot Google 15 second adb install xda Sent from my Nexus 5 using XDA Free mobile app Click to expand... Click to collapse I installed the 15 secs ADB but when i run the program, it quickly shows a DOS screen then auto closes. Would this still work with USB debugging turned off on my android? EDIT the phone doesnt even show up on my device manager, after typing "adb devices" no devices show up. I have tired to manually install the drivers but it wont show up on device manager
You can just factory reset the phone to remove encryption. Boot the phone into recovery mode. When you see the "no command" screen hol vol-up and tap power, then you can wipe the device.
[SOLVED] Bootloop. No recovery. Bootloader locked.
================================ Solution: http://forum.xda-developers.com/one...bootloader-locked-t3212187/page2#post63494201 ================================ Hello, This afternoon, I was preparing to flash Oxygen OS 2.1 through twrp but I wanted to make a backup first. Attempting to load up twrp by holding Vol- and Power, my OPT flashed the starting frame of the boot animation for half a second before turning off. This repeated every 5 seconds. I could still boot OOS normally at this stage. I decided to reflash twrp so as to make the backups, but on attempting to flash it, I saw that my bootloader was locked. So into fastboot mode I went, but trying to unlock it, it did the same as trying to get into recovery. As soon as I sent the command, "fastboot oem unlock", the screen went dark, flashed the starting frame for the boot animation, and promptly when dark again. I now can't boot up normally, nor can I enter recovery. I can access fastboot mode, but I can't seem to make any changes. I've attempted to use this solution as well as several other similar ones with no success. I've had my OPT since 17th of August with absolutely no signs of trouble until this afternoon. To me, it seems like it could be a hardware issue, but I'd hope it would last more than 40 days. Any suggestions? Thanks. ---- x-post: whirlpool, reddit
The same just happened to me, wtf
Makrilli said: The same just happened to me, wtf Click to expand... Click to collapse What were you doing before it occurred? Perhaps we can work out the cause.
GusGold said: What were you doing before it occurred? Perhaps we can work out the cause. Click to expand... Click to collapse I'm not sure what I was doing, I was going to flash different ak kernel as my wifi didn't work. HOWEVER I read someone suggesting if you still have bootloop after trying the qualcomm recovery tool, try booting to fastboot and use: fastboot continue my opt booted nicely to hydrogen os and after I shut it down it no longer bootlooped and I was able to get to recovery. I'll post this to your reddit thread too, maybe it might help somebody one day, hopefully this works for you too
Makrilli said: use: fastboot continue Click to expand... Click to collapse Mate! that worked for me too! However... It only seems to skip the bootloop for that power on. After power off, it returns to the boot loop. I also still can't unlock the bootloader and can't access recovery. But at least it can boot into OS with fastboot continue! Thank you.
Weird, after the first successful boot I rebooted and a chinese menu prompted me if I wanted to unlock the bootloader, and I did. Maybe you should try different recovery packages. But I'm glad to hear you at least got past the boot loop
Makrilli said: Maybe you should try different recovery packages. Click to expand... Click to collapse Can't flash a new one since the bootloader won't unlock :/ I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
GusGold said: Can't flash a new one since the bootloader won't unlock :/ I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me... Click to expand... Click to collapse Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Makrilli said: Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters Click to expand... Click to collapse Ahh, do you mind linking me to the one you used?
I think I used this: https://mega.nz/#!EsNQHKab!ifATzg4rxxBniPad0iyxANqlN8cZpUx2MVWaZgEhrD4 but it might have also been this: https://drive.google.com/file/d/0B14IjYN3PtxcSlJ5aGQxX3JERHM/view?usp=sharing It's also worth mentioning I flashed both a few times before I tried the fastboot continue command so try both a few times and see if that helps, also I replaced the stock recovery with twrp in both recovery packages before flashing. Edit: And best of luck, I'm rather confident your OPT is going to work properly again.
Boot Loop I got the same problem. Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it. The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd. If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec. Is there a solution for this? I've been searching 2 for two days now. I don't care if i have to reset the entire phone.
p3wb said: I got the same problem. Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it. The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd. If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec. Is there a solution for this? I've been searching 2 for two days now. I don't care if i have to reset the entire phone. Click to expand... Click to collapse And I'm guessing you have tried the qualcomm recovery tool?
And I'm guessing you have tried the qualcomm recovery tool?[/QUOTE] I got TWRP installed but its unreachable, volume- and power ends in boot loop. I can´t install anything when the phone is locked. I even tried a Factory reset, boot loop and no change when i got it up again.
p3wb said: And I'm guessing you have tried the qualcomm recovery tool? Click to expand... Click to collapse I got TWRP installed but its unreachable, volume- and power ends in boot loop. I can´t install anything when the phone is locked. I even tried a Factory reset, boot loop and no change when i got it up again.[/QUOTE] Yeah but the qualcomm recovery tool that we discussed on the first page? Sent from my OPT
Makrilli said: I got TWRP installed but its unreachable, volume- and power ends in boot loop. I can´t install anything when the phone is locked. I even tried a Factory reset, boot loop and no change when i got it up again. Click to expand... Click to collapse Yeah but the qualcomm recovery tool that we discussed on the first page? Sent from my OPT[/QUOTE] I finally got my OPT working again, tried Qualcomm recovery tool, wasn't able to complete the "MSM8994DownloadTool" So i downloaded "A2001_14_A.03_150805" in a guide from technobuzz.net/unbrick-oneplus-2/ A similar but it does a entire wipe of the phone, nothing left at all. WARNING! But i was okey with it. Well the phone was in Chinese when it was all done but to change language was no problem.
I finally managed to solve it on mine. I had been cautious over the past weeks to not let it run out of battery or get turned off while away from my computer as Code: fastboot continue was the only way I could get past the boot loop. My core issue to solve was that I couldn't get it recognised as the USB Diagnostic 9006 under Ports in Device Manager. I installed the driver from here manually by right clicking the /qcser/x64/qcser.inf file and selecting install from the context menu. Then, I powered off my OP2. While only holding Vol+ (not power or Vol-), I plugged in my OP2 to the computer and it was finally recognised as the 9006. Then using the recovery tool from the prior link, it installed and rebooted my OP2. The moment of truth was when it rebooted and didn't enter a boot loop! Then with the Chinese recovery prompt, I selected the top/first option and it brought me to the welcome/first setup screen of OOS. It wiped the internal memory, and installed OSS 2.0.2 (don't know if coincidence or not as that was my prior OS as well). Now to install twrp and update to the latest OOS hopefully without a hitch. Happy to finally know it wasn't a hardware issue like a failed eeprom or a dud nand controller as my prior phone (Samsung Note 10.1) died to a failed nand controller as well. Will update with news of twrp and OOS, but I feel that should go smoothly now. Thanks to the others that helped in this thread too!
Yeap, all good! Flashed official twrp through fastboot and batch installed OOS2 through 2.1.1 patches and SuperSU. Everything working like new! Phew.
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root best Martin
gamdiiii said: hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root best Martin Click to expand... Click to collapse Is it recognised as a USB Diagnostic 9006 in your device manager?
Hi GusGold No its 9008
Bootlooped Pixel 4 (locked Bootloader, can launch bootloader menu)
I have a Pixel 4 that failed to update. I have not made any modifications to this device and was using it in its stock environment, I guess that the battery ran out during the update. The device is in a bootloop state and I can invoke the bootloader menu, but the bootloader is locked and the fastboot command is not available. Recovery appears to be corrupted and when I try to open recovery get a bootloop. For these reasons, neither the method of using the fastboot command nor the method of using adb sideload to perform an OTA update can be used. Below is the device information. Product revision: flame MP1.0(JPN) Bootloader version: c2f2-0.3-7376653 Baseband version: g8150-00088-210507-B-7345963 I realize that this device is usually a non-recoverable scenario, but I would like to know if there is a way to recover it. Appreciate all support and suggestions. Thanks.
The only thing you might try is select Rescue Mode from the bootloader menu, then try the Pixel Repair Tool. However, I believe this depends on working recovery, so it's very possible you are out of options - the device is not recoverable.
Thanks for the reply. My Pixel does not allow me to start Rescue Mode and when I try to start Rescue Mode/Recovery Mode from the menu, it goes back to bootloop. I contacted Google Support yesterday and they told me to force reboot the device 7 times, which I did and the no Commands screen appeared. However, I release the button at the wrong time, it goes back to the boot loop. Also,it is difficult to distinguish between the boot loop and the forced restart by the button, and I have not been able to reproduce it since then. However, does the fact that the no Commands screen appears mean that recovery is partially working? I would appreciate your findings. Thanks again for your reply.
did u solve this? if u want, u can send me a DM
Khanov said: did u solve this? if u want, u can send me a DM Click to expand... Click to collapse Sorry for the delay in replying. The problem has not been resolved, I will send you a DM.