Backstory: I upgraded to android 10 a few weeks ago, aside from a few user apps breaking, there weren't any system issues. Recently, I received another update (seems like a patch ?) to android 10 and updated as well. I'm not sure if this recent update actually completed.
Last night, it seems like my phone went into a boot loop while I was sleeping. When I woke up the phone was hot, and each boot was so short that there was no opportunity to go into recovery mode. I pretty much had no choice other than to let the battery drain.
So I walked away and came back a while later to a peculiar recovery screen that said "Cannot load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device."
There's only 2 options: "Try again" and "Factory data reset". `adb devices` from the PC is unable to detect my pixel 3 here. "Try again" simply attempts to boot, and I just return to this same screen again (at least it doesn't loop now). I'm reluctant to factory reset as I want to at least have the chance to back up some data.
I am able to enter fastboot from this screen using Power + Volume Down. `fastboot devices` from the PC is able to detect the phone. However, because the bootloader is locked (haven't unlocked the bl since i started using nexus/pixel phones), I don't know if there's much i can do here.
My question is, is there anything that I can try at this point to boot into android 10, recover some data, then do a factory reset ?
From fastboot, what happens if you try entering recovery? If you can get into recovery, you could sideload the OTA. https://developers.google.com/android/ota
sliding_billy said:
From fastboot, what happens if you try entering recovery? If you can get into recovery, you could sideload the OTA. https://developers.google.com/android/ota
Click to expand...
Click to collapse
It's not the "normal" recovery mode. There was the message "Cannot load android system. Your data may be corrupt." Other only options are:
- "Try again" , basically a reboot, which eventually brings me back to this screen
- "Factory Data Reset"
adb is unable to detect the phone in this mode, so I am unable to sideload an OTA.
superc0w said:
It's not the "normal" recovery mode. There was the message "Cannot load android system. Your data may be corrupt." Other only options are:
- "Try again" , basically a reboot, which eventually brings me back to this screen
- "Factory Data Reset"
adb is unable to detect the phone in this mode, so I am unable to sideload an OTA.
Click to expand...
Click to collapse
Not knowing what is available with the BL locked... Is the new rescue mode option one of the power up/down choices from your BL/Fastboot screen? That rescue mode is supposed to allow ADB command to work. If not, you are going to have to do a factory reset and if that doesn't help contact Google and RMA. Ability to get out of bricks is the biggest reason to unlock your BL (if you purchased a Google unlockable BL phone) unless you purchased a Verizon phone and can't. In that case, back to the last comment about factory reset/RMA.
superc0w said:
It's not the "normal" recovery mode. There was the message "Cannot load android system. Your data may be corrupt." Other only options are:
- "Try again" , basically a reboot, which eventually brings me back to this screen
- "Factory Data Reset"
adb is unable to detect the phone in this mode, so I am unable to sideload an OTA.
Click to expand...
Click to collapse
Had this happen and I had to do a factory reset prior to unlocking bootloader ,which as was mentioned above is way easier to fix because you can reflash factory image without wiping all data
same thing happened to me; the previous comments gave me the outline of what was needed, so thank you. now for the op:
1. on the screen that offers try again or factory erase, choose "try again"
2. IMMEDIATELY press and hold volume down
3. when you reach the bootloader screen, you may release volume down
4. this is the standard bootloader screen for pixel 3. you should be able to cycle options do so to select 'recovery" (or whatever it says. I'm not going to reboot my phone to see exactly what it says, but I'm sure you get the idea)
Hi, I have encountered device corrupt error on my pixel 4Xl few days back, after reaching out to google support and waiting for 4hrs I haven't received any resolution. In few instances device worked normally for few hours but kept on switching off. I did factory reset once as suggested but currently issue is still persistent. I am out of warranty by few months so I cannot send it google support. Please help me in fixing this issue.
Prudhvi89 said:
Hi, I have encountered device corrupt error on my pixel 4Xl few days back, after reaching out to google support and waiting for 4hrs I haven't received any resolution. In few instances device worked normally for few hours but kept on switching off. I did factory reset once as suggested but currently issue is still persistent. I am out of warranty by few months so I cannot send it google support. Please help me in fixing this issue.
Click to expand...
Click to collapse
Sounds like this problem. https://forum.xda-developers.com/t/...xxxx_sn-xxxxxxxx.4205331/page-7#post-85981389
Prudhvi89 said:
Hi, I have encountered device corrupt error on my pixel 4Xl few days back, after reaching out to google support and waiting for 4hrs I haven't received any resolution. In few instances device worked normally for few hours but kept on switching off. I did factory reset once as suggested but currently issue is still persistent. I am out of warranty by few months so I cannot send it google support. Please help me in fixing this issue.
Click to expand...
Click to collapse
So we know you get the corrupt message, support isn't helping, that in a few instances it worked normally for short periods, a factory reset didn't help, and yer out of warranty.
But can u get to fastboot? Is OEM unlocking on? Can u turn oem unlocking on in one of the "few instances", if it's not on?
If u can do the above, i'd follow googles instructions to unlock the bootloader and use the flash-all script and flash the latest firmware.
AsItLies said:
So we know you get the corrupt message, support isn't helping, that in a few instances it worked normally for short periods, a factory reset didn't help, and yer out of warranty.
But can u get to fastboot? Is OEM unlocking on? Can u turn oem unlocking on in one of the "few instances", if it's not on?
If u can do the above, i'd follow googles instructions to unlock the bootloader and use the flash-all script and flash the latest firmware.
Click to expand...
Click to collapse
Hi, thanks for responding back. Yes OEM is enabled on my device. I did reach out to google forums as well for support, they redirected to XDA for support with respect to flashing device.
PS: I am not at all a tech person and have very limited understanding in this area, I am just trying to save my phone.
Prudhvi89 said:
Hi, thanks for responding back. Yes OEM is enabled on my device. I did reach out to google forums as well for support, they redirected to XDA for support with respect to flashing device.
PS: I am not at all a tech person and have very limited understanding in this area, I am just trying to save my phone.
Click to expand...
Click to collapse
so then first follow this link and choose which version of android you'd like to flash to your 4xl (probably the latest one).
On that site click 'link' next to the chosen version and it will download the firmware zip file (this is the latest generic version: SP1A.211105.002, Nov 2021 --- if you have verizon or other choose the latest for that carrier).
Then you'll need to follow the directions near the top of that page that starts with the following:
Flashing instructionsThe factory image downloaded from this page includes a script that flashes the device, typically named flash-all.sh (On Windows systems, use flash-all.bat instead).
etc etc etc.
If you have trouble, post back here and people will try to assist you.
cheers
AsItLies said:
so then first follow this link and choose which version of android you'd like to flash to your 4xl (probably the latest one).
On that site click 'link' next to the chosen version and it will download the firmware zip file (this is the latest generic version: SP1A.211105.002, Nov 2021 --- if you have verizon or other choose the latest for that carrier).
Then you'll need to follow the directions near the top of that page that starts with the following:
Flashing instructionsThe factory image downloaded from this page includes a script that flashes the device, typically named flash-all.sh (On Windows systems, use flash-all.bat instead).
etc etc etc.
If you have trouble, post back here and people will try to assist you.
cheers
Click to expand...
Click to collapse
Hi, thanks for quick response. I am getting below error, not sure how to correct it.
Prudhvi89 said:
Hi, thanks for quick response. I am getting below error, not sure how to correct it.
Click to expand...
Click to collapse
So you're getting an error indicating you're trying to do something but it can't do it because the boot loader is locked. Obvious.
but here's what's not obvious; what are u trying to do? and why are u trying to do it?
from the looks of the output, yer trying to switch slots? why? there's nothing in those instructions I referenced above that tells u to switch slots? All yer gonna do is first unlock the bootloader and then use the flash all script.
maybe yer reading the wrong directions? Look again what I posted, find those exact words in the directions, do what's under that heading, not any other heading.
Currently I am not able to switch on my phone !!!
AsItLies said:
So you're getting an error indicating you're trying to do something but it can't do it because the boot loader is locked. Obvious.
but here's what's not obvious; what are u trying to do? and why are u trying to do it?
from the looks of the output, yer trying to switch slots? why? there's nothing in those instructions I referenced above that tells u to switch slots? All yer gonna do is first unlock the bootloader and then use the flash all script.
maybe yer reading the wrong directions? Look again what I posted, find those exact words in the directions, do what's under that heading, not any other heading.
Click to expand...
Click to collapse
Currently I am not able to switch on the device !!
Prudhvi89 said:
Currently I am not able to switch on the device !!
Click to expand...
Click to collapse
That sounds ominous. You may now be afflicted with the pixel 'stuck in edl mode' problem, which unfortunately there's no solution for.
Try this; plug the device to pc using usb cable, then look in device manager, if you see the device connected with QUSB_BULK_CID (etc), that means it's in EDL mode.
if that's the case, follow this thread to learn more about that, but unfortunately there is no fix, as yet. And I've read just yesterday google is replacing devices with this issue for some.
Just an fyi, if your device is in this state, it's not anything you did, it's the fault of the device. Some believe it to be hardware failure, which seems the most plausible explanation.
AsItLies said:
That sounds ominous. You may now be afflicted with the pixel 'stuck in edl mode' problem, which unfortunately there's no solution for.
Try this; plug the device to pc using usb cable, then look in device manager, if you see the device connected with QUSB_BULK_CID (etc), that means it's in EDL mode.
if that's the case, follow this thread to learn more about that, but unfortunately there is no fix, as yet. And I've read just yesterday google is replacing devices with this issue for some.
Just an fyi, if your device is in this state, it's not anything you did, it's the fault of the device. Some believe it to be hardware failure, which seems the most plausible explanation.
Click to expand...
Click to collapse
Ok got it !! Thanks for your prompt response & support.
The "Cannot load Android system, Your data may be corrupt" error is known as Rescue Party. Fortunately, fixing it should be relatively simple.
Try dirty flashing the factory image. Do not attempt to flash a patched boot image; leave everything stock.
If that fails, select "Factory data reset". It will wipe your phone, but it should reboot into Android system.
That bootloader message "Your device is corrupt. It can't be trusted" means that the signed key for Verified Boot somehow got screwed up. In this case, I would also recommend reflashing the factory image.
In both cases, the easiest option is to use the Android Flash Tool. It's like a GUI for flashing the factory image.
Related
Alright have read the first 30 pages of comments on http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 and I starting to feel like I'm dumber then a brick.
Okay here is my problem: Just bought a used OPO with the classic boot logo loop error. I have tried to just simply Factory reset it (both Full and wipe cache) and it gives me E: failed to mount /cache (invalid argument) error. Then I googled it and most of the results said that I need to simply reinstall the software with adb. Okay got adb up and running and installed my phones drivers and booted into fastboot.
Then when I try to install it gave me "device not unlocked" error... Fine googled it tried "fastboot oem unlock" and it was still not unlocked.
Googled that and read the posts about tampered bits and after running the "fastboot oem device-info" It gives me "Device tampering: true" "Device unlocked: false" so damn.
Then I read the posts and tried to sideload OnePlusOne-BootUnlocker.zip (used the "apply update" in cyanogen recovery to get the ADB sideload) but it comes up with E: failed to mount /cache (invalid argument) and fails all the other things.
Have tried "fastboot boot recovery recovery.img" but that have the have a unlocked bootloader.
I'm abit lost ATM because I discovered that wile I can get fastboot and Sideload (from update) to show my device the normal adb can't see it when just being in the menu.
So if one of you could point me in the right way or if you got time guide me then I would be greatfull.
Regards Magnus/Mjallo
PS. Please don't burn me for asking
Can post pictures of the screen if it is needed
@Mjallo google "Bacon Toolkit."
Does literally all the things you are trying to do in a matter of a few clicks. Walks you through everything step by step.
h11wiscan said:
@Mjallo google "Bacon Toolkit."
Does literally all the things you are trying to do in a matter of a few clicks. Walks you through everything step by step.
Click to expand...
Click to collapse
Okay have played around with the program abit more and all it does is that same as me doing it in CMD.
I still have the problem with Device tampering and device unlock state. Where is the tools for fixing that?
Have tried to fix the cache but it still make the invalid argument.
might could fastboot flash official images to get the phone back to normal. you dont have to have bootloader unlocked to flash official boot images. you can go here https://cyngn.com/support and download the cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee.zip (scroll down to opo section) and/or go to http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and get the download and follow directions in that post to flash phone
Mjallo said:
Okay have played around with the program abit more and all it does is that same as me doing it in CMD.
I still have the problem with Device tampering and device unlock state. Where is the tools for fixing that?
Have tried to fix the cache but it still make the invalid argument.
Click to expand...
Click to collapse
Yeah idk then. Need more screenshots or info to help. Could be a million things.
-Are you using OEM USB cable?
-Did you install ALL drivers properly?
-Have you rebooted since installing ALL drivers?
-Have you tried using bacon toolkit on another computer? Sometimes simply switching computers can help.
-Did you try resetting phone to factory state using ABD/Bacon Toolkit?
-In Bacon Toolkit did you select the proper firmware and software version before attempting to use the program?
A few questions to ask yourself before we go further.
kenboyles72 said:
might could fastboot flash official images to get the phone back to normal. you dont have to have bootloader unlocked to flash official boot images. you can go here https://cyngn.com/support and download the cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee.zip (scroll down to opo section) and/or go to http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and get the download and follow directions in that post to flash phone
Click to expand...
Click to collapse
Have tried with both Normal Cyanogen and CyanogenMOD (that is what the bootlogo says on this phone) and both of them give the Device not unlocked error both on screen and in CMD
h11wiscan said:
Yeah idk then. Need more screenshots or info to help. Could be a million things.
-Are you using OEM USB cable?
-Did you install ALL drivers properly?
-Have you rebooted since installing ALL drivers?
-Have you tried using bacon toolkit on another computer? Sometimes simply switching computers can help.
-Did you try resetting phone to factory state using ABD/Bacon Toolkit?
-In Bacon Toolkit did you select the proper firmware and software version before attempting to use the program?
A few questions to ask yourself before we go further.
Click to expand...
Click to collapse
Okay I'm using the OEM cable (have tried both the one I got with this phone and the one I got with my Orginal OPO)
Have gone through the steps checking my drivers and they should be working and A OKAY, reboot and all.
Don't have access to another pc ATM but will look after the option.
Have tried all the option in Bacon toolkit to reset the phone to factory setting and non is working, tried to then use the recovery option to maybe get it to work that way but no dice. Have also tried sideloading both with Toolkit and with CMD and no luck their either. Took a picture of the screen when the sideload tries to work.
http://imgur.com/6L74N6J
The Firmware question is up in the air because I have never got it booted so I have no clue what firmware it has only hint that the boot screen is Cyanogen MOD READY and not just Cyanogen like on my other OPO
Hope it helps finding the problem
I super hard bricked my phone a while back, even lost a partition. I was finally able to get it back by flashing colorOS. took a few tries to get the program to recognize my phone, but finally got it flashed. The phone never booted all the way up with colorOs, but it fixed what needed fixed and I was then able to fastboot flash CM13, unlock bootloader and go from there. don't have that thread bookmarked, but it's here in the forums.
Edit: found thread http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
kenboyles72 said:
I super hard bricked my phone a while back, even lost a partition. I was finally able to get it back by flashing colorOS. took a few tries to get the program to recognize my phone, but finally got it flashed. The phone never booted all the way up with colorOs, but it fixed what needed fixed and I was then able to fastboot flash CM13, unlock bootloader and go from there. don't have that thread bookmarked, but it's here in the forums.
Edit: found thread http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
It sadly did not fix the problem it gives this problem and just stops working (need to close it in taskmanger) http://imgur.com/w1zOQFU.
Well the quest goes on
Mjallo said:
It sadly did not fix the problem it gives this problem and just stops working (need to close it in taskmanger) http://imgur.com/w1zOQFU.
Well the quest goes on
Click to expand...
Click to collapse
when you run the program, one of the columns should have a few random characters and "com" in it. if you dont see com in any of the columns, then the program is not seeing you phone. if you do see com, the click on that row and press start and it will show files being written in green showing progress. if phone is not being seen, follow that guide to the letter, specially if this is on a win7/8 machine. i will get my lappy out in a bit and give a few screenies on what it should look like, i wont actually flash my phone though.
kenboyles72 said:
when you run the program, one of the columns should have a few random characters and "com" in it. if you dont see com in any of the columns, then the program is not seeing you phone. if you do see com, the click on that row and press start and it will show files being written in green showing progress. if phone is not being seen, follow that guide to the letter, specially if this is on a win7/8 machine. i will get my lappy out in a bit and give a few screenies on what it should look like, i wont actually flash my phone though.
Click to expand...
Click to collapse
It sees it (you can see it in COM5 in the picture) and when the progress bar shows it just make a little green tip then just stops showing
are you running the program as administrator? right click on exe and select run as administrator? other than that, don't see why it's not flashing and I'm out of ideas, sorry.
So here is a string of steps I've already been through in trying to save my bricked Nexus 6: [Can't post outside link yet...]
Basically I got the 'your phone is corrupt' message from google and it kept forcibly shutting down. It would not boot up so someone suggested I side load a rescue OTA. At this point recovery existed and I went through all the steps and had it installing, only to fail mid-way through (~52%) and give me a 'read error' on my command prompt. I started the whole process over again just fine and it got to 73% before 'read error' failing again. I thought no big deal, I'll just keep doing this until it gets to 100%. Nope, recovery is gone. I cannot get there anymore. I start into Fastboot mode and scroll to recovery and hit power and it just goes to a new Fastboot screen and keeps flashing every time I try to select it. The Bootloader logs give me a 'failed to validate boot image: ret=-1' message and says 'Boot up failed.'
I can't find a single guide online that doesn't require recovery mode to work. At this point I don't care about my data and just want to get this phone working again before I throw in the towel and pay Motorola $175 for a refurb. I'm just barely over a year too. The Nexus 'expert' gave up and blamed the memory and maybe he is right but I wanted to run this by you guys first. This phone was completely stock and unrooted.
The only reason why I feel there is still a chance is because when I connect USB my computer reads it as an Android Device in Device Manager with 'Android Bootloader Interface' as a sub device. If the computer can read it, isn't there a chance that some kind of software exists that can forcibly load a new bootloader onto this phone without recovery? I'm 'competent' with computers and android phones but I haven't rooted or done any custom stuff in years so I'm at a loss for what's out there.
Thanks in advance for any help you can give me, even if it's to tell me I'm SOL.
Ok so far I have tried to load a custom recovery but that requires an unlocked bootloader. Then I tried using a toolkit to flash stock as a soft-bricked device but that also requires an unlocked bootloader and I can't unlock the damn bootloader. You know, I thought I was just playing it safe by leaving this phone as-is instead of playing around with it but it looks like I screwed myself by doing so.
Is this the wrong forum for this question?
JQ3 said:
Is this the wrong forum for this question?
Click to expand...
Click to collapse
Sorry for the delay
We have a dedicated help section for your device here
http://forum.xda-developers.com/nexus-6/help
Ask there to receive help
Good luck
Hi All,
First, thanks for clicking into my question! This is my first post, but I've been lurking here since I used to flash new roms on my original Nexus on a frequent basis, and a Gen1 Kindle Fire before that.
My fiancee is in a bind with her Pixel 2, so I'm hoping you all can help me out.
Her Pixel 2 threw a bunch of app errors over the course of two days, so she opted to reboot -- unfortunately it now locks up at the loading screen, with the Google 'G' and a loader bar (she's running the latest 8.1, pre-Pie) and hangs there, overheating until the battery runs out and we shut it down. We can get into the Recovery menu, but none of the reboot options there seem to help, and there is only the Factory Reset option remaining that we haven't tried.
This happened in the middle of a huge camping excursion as her Bachelorette, so there was limited WiFi and data access to back anything up -- so locked behind that endless boot sequence is a lot of irreplaceable images and video.
What are my options to pull the user data out of there before a factory reset? Is it possible on a (stock, non-root, Google sourced) phone to flash the Pie update? Would that restore functionality?
Can I get to the data somehow through ADB without the phone booting up and unlocked?
Maybe something crazy, like a take a full image of the phone that I then shove on the replacement Pixel 2 that Google is sending us?
Any guidance would be much appreciated!
You could try booting to TWRP with "fastboot boot <filename here>". Then copy the files from there. I'm not sure if this will work if she had the screen locked beforehand though. You could also try flashing the latest factory image but make sure your remove the "-w" from the flash-all.bat file before running the script so it will not wipe user data. Both of these options might not be possible though if you do not have the boot-loader unlocked.
cynnican said:
Hi All,
First, thanks for clicking into my question! This is my first post, but I've been lurking here since I used to flash new roms on my original Nexus on a frequent basis, and a Gen1 Kindle Fire before that.
My fiancee is in a bind with her Pixel 2, so I'm hoping you all can help me out.
Her Pixel 2 threw a bunch of app errors over the course of two days, so she opted to reboot -- unfortunately it now locks up at the loading screen, with the Google 'G' and a loader bar (she's running the latest 8.1, pre-Pie) and hangs there, overheating until the battery runs out and we shut it down. We can get into the Recovery menu, but none of the reboot options there seem to help, and there is only the Factory Reset option remaining that we haven't tried.
This happened in the middle of a huge camping excursion as her Bachelorette, so there was limited WiFi and data access to back anything up -- so locked behind that endless boot sequence is a lot of irreplaceable images and video.
What are my options to pull the user data out of there before a factory reset? Is it possible on a (stock, non-root, Google sourced) phone to flash the Pie update? Would that restore functionality?
Can I get to the data somehow through ADB without the phone booting up and unlocked?
Maybe something crazy, like a take a full image of the phone that I then shove on the replacement Pixel 2 that Google is sending us?
Any guidance would be much appreciated!
Click to expand...
Click to collapse
ADB sideload the latest OTA zip in stock recovery, that should get you up and running again without needing a wipe
crixley said:
ADB sideload the latest OTA zip in stock recovery, that should get you up and running again without needing a wipe
Click to expand...
Click to collapse
Thank you! I'll be giving this a try as soon as she's home on Monday.
Does recovery mode automatically enable the USB Debugging that ADB uses?
cynnican said:
Thank you! I'll be giving this a try as soon as she's home on Monday.
Does recovery mode automatically enable the USB Debugging that ADB uses?
Click to expand...
Click to collapse
Yep you can sideload without needing it toggled in developer mode
crixley said:
Yep you can sideload without needing it toggled in developer mode
Click to expand...
Click to collapse
This worked perfectly, thank you!
cynnican said:
This worked perfectly, thank you!
Click to expand...
Click to collapse
I'm glad to hear! Nothing worse than having to wipe and losing important things you can't get back. I've had that happen a few times. Happy to help.
I'm not very technical - please keep this in mind with my query below.
I have a Pixel 2 which overnight stopped working - my guess is that it rebooted due to an automated software update.
I now only get the page with the robot on it's back.
Options in green on this page are Barcodes, Power Off, and Start.
After reading a lot online I've tried all the usual key press combinations to no avail.
I've also downloaded ADB and FASTBOOT to my Mac.
ADB doesn't see the phone when plugged in via USB (ie. ADB DEVICES doesn't return anything)
FASTBOOT DEVICES does, however, show the serial number as listed on the page with the robot on it's back (and the -l option adds "usb:" plus an 8 digit number and the letter "X"
FASTBOOT REBOOT restarts the phone and brings me back to the robot on it's back page.
Other information on the Robot on it's back page include -
Product Revision: walleye MP1
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked
Advice online suggests I need to unlock the phone, so I've tried FASTBOOT FLASHING UNLOCK, and FASTBOOT OEM UNLOCK but neither work.
When I try these I get "FAILED (remote: Flashing Unlock is not allowed)"
An article on Android Police suggests this may have been a bug on the Pixel 2 originally and that it's now resolved.
Unfortunately, my cat 22 situation seems to be that I need to do a factory reset, but the steps I've found as to how to do a factory reset all lead back to the Robot on it's back page, so I can't see how to move forward to with recovering my phone?
Can anyone help please?
Really frustrated that my new phone can put itself into this state without me having done anything and that it's seemingly impossible to recover from this state now that it's in it.
At very least I'd like to wipe all data from the phone so I can send it off for repair.
Thanks in advance.
Hello.
I did something wrong while trying to flash TWRP on my pixel 2, I am now stuck at the bootloader, and I cannot boot System or Recovery. While at the bootloader screen, it says Device State : unlocked. If I try to get to download mode, it says "ERROR: Operation Denied". If I try to go into recovery, it says "ERROR: Slot Unbootable: Load Error". If I try "Start", I get the same error message.
Also, adb or fastboot don't seem to be able to "see" the pixel connected to the computer. I believe my cables are good since I was able to flash Magisk and reflash the whole system with them before bricking it.
Can anyone help?
Thanks!
stanelie said:
Hello.
I did something wrong while trying to flash TWRP on my pixel 2, I am now stuck at the bootloader, and I cannot boot System or Recovery. While at the bootloader screen, it says Device State : unlocked. If I try to get to download mode, it says "ERROR: Operation Denied". If I try to go into recovery, it says "ERROR: Slot Unbootable: Load Error". If I try "Start", I get the same error message.
Also, adb or fastboot don't seem to be able to "see" the pixel connected to the computer. I believe my cables are good since I was able to flash Magisk and reflash the whole system with them before bricking it.
Can anyone help?
Thanks!
Click to expand...
Click to collapse
happened to my walleye too , and managed to bring it back to life . check this thread for a possible solution. https://forum.xda-developers.com/pixel-2/help/december-factory-image-to-broken-t3875213
Thanks!
I missed that thread while researching this issue.
I will try these things when I get back from work next week.
Thanks again!
stanelie said:
Thanks!
I missed that thread while researching this issue.
I will try these things when I get back from work next week.
Thanks again!
Click to expand...
Click to collapse
Just as a reference for anyone else who needs the fix and can't be bothered opening another thread.
SOLUTION: At the menu where it is stuck and saying device fail etc, plug in your usb cable to the mobile, press and hold the POWER button for 10 seconds, it will now recognise your phone under fastboot.
Once that is cleared, it's pretty much straightforward flashing latest pixel 2 image via fastboot and problem solved.
sidenote: Issue came with anyone who tried to flash december security updates and above as of what I heard.
I will try that, thanks.
So, several things :
Holding down the power button had no effect other than restarting the boot menu, but Fastboot never became available.
Opening up the phone and disconnecting the battery and reconnecting it made Fastboot available again. This would be in line with other users that let the phone battery discharge completely before regaining fastboot access.
Sidenote : opening up this phone is not for the faint of heart. I managed to damage something on the motherboard doing so (probably a static electricity discharge), the screen ended up displaying gibberish. I was able to salvage my phone by replacing the motherboard. I had ordered a replacement motherboard when I thought all was lost with no fastboot, and I had it on hand. Expensive little sucker...
stanelie said:
Hello.
I did something wrong while trying to flash TWRP on my pixel 2, I am now stuck at the bootloader, and I cannot boot System or Recovery. While at the bootloader screen, it says Device State : unlocked. If I try to get to download mode, it says "ERROR: Operation Denied". If I try to go into recovery, it says "ERROR: Slot Unbootable: Load Error". If I try "Start", I get the same error message.
Also, adb or fastboot don't seem to be able to "see" the pixel connected to the computer. I believe my cables are good since I was able to flash Magisk and reflash the whole system with them before bricking it.
Can anyone help?
Thanks!
Click to expand...
Click to collapse
Same thing happened to me except I never even tried to root. Just pulled the phone out of my pocket, and the little Android dude was belly up. It's showing device locked - and although I had it in Dev. mode from weeks back (thought USB Debugging was enabled) it fails to respond to adb commands, boot-loader mode, etc.
...Looks like Google laid an egg with this one.
Pixel 2 - "ERROR: Slot Unbootable: Load Error"
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
ashokabs said:
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
Click to expand...
Click to collapse
I don't even know how to thank you. I almost had a heart attack watching my Pixel bricked. Thanks man!
Save my day! I just keep pressing power button and fastboot response finally!
Can this be done if the device is locked?
_Kalyan said:
I don't even know how to thank you. I almost had a heart attack watching my Pixel bricked. Thanks man!
Click to expand...
Click to collapse
Does ur bootloader locked or unlocked?
---------- Post added at 11:36 AM ---------- Previous post was at 11:36 AM ----------
ashokabs said:
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
Click to expand...
Click to collapse
Works on bootloader state locked or not?
SoKa1993 said:
Does ur bootloader locked or unlocked?
---------- Post added at 11:36 AM ---------- Previous post was at 11:36 AM ----------
Works on bootloader state locked or not?
Click to expand...
Click to collapse
If the boot loader is locked look for a script for unlocking the bootloader from recovery or bootloader state. I did find it but cannot remember. My bootloader was unlocked so I did not have to use it.
ashokabs said:
Pixel 2 - "ERROR: Slot Unbootable: Load Error"
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
Click to expand...
Click to collapse
I have same problem. I use Pixel 2 and Fedora. My question is, what i exactly should do? I mean the steps. I didn't get that beep from my laptop. But I got the vibration when I hold the power button when it's not connected to USB. Please Help me.
Sorry my english isn't that good.
I’ve been asked to restore data and repair bootlooping A51. I’ve tried basic steps and resorted to updating firmware with odin. Recovery mode failed and I couldn’t enter it or fastboot. I’ve used home_csc to hopefully keep user data. Odin shows it passed, left my phone for 10 mins but it still was stuck. Maybe I’ve given it too little time to setup the new firmware.
Anyways now it’s unresponsive, nothing shows up anymore, no button combination works, nothing detected by my PC. Tried disconnecting the battery.
Everything was stock, pretty sure I’ve used the correct system version.
What can I do at this point?
piotrekkrzewi said:
I’ve been asked to restore data and repair bootlooping A51. I’ve tried basic steps and resorted to updating firmware with odin. Recovery mode failed and I couldn’t enter it or fastboot. I’ve used home_csc to hopefully keep user data. Odin shows it passed, left my phone for 10 mins but it still was stuck. Maybe I’ve given it too little time to setup the new firmware.
Anyways now it’s unresponsive, nothing shows up anymore, no button combination works, nothing detected by my PC. Tried disconnecting the battery.
Everything was stock, pretty sure I’ve used the correct system version.
What can I do at this point?
Click to expand...
Click to collapse
Have it repaired. It sounds like something got corrupted and the bootloader won't start. The only way to fix this is with a board level flash, and Samsung/Qualcomm do not make the tools or the files available to do this. Most repair centers don't even have the ability to do this; they'll just replace the mainboard and program it with the original IMEI. Of course, this means that all user data will be lost.
V0latyle said:
Have it repaired. It sounds like something got corrupted and the bootloader won't start. The only way to fix this is with a board level flash, and Samsung/Qualcomm do not make the tools or the files available to do this. Most repair centers don't even have the ability to do this; they'll just replace the mainboard and program it with the original IMEI. Of course, this means that all user data will be lost.
Click to expand...
Click to collapse
Does it make a difference that after a while the phone responded and I can access download mode? I’m trying third firmware from a different source and still using home_csc to hopefully save the damn data.
Is there anything else I could try at this point? Still no access to recovery though.
What I am going to try now is to get twrp on the device and get the data off the phone this way. I don’t know if I can since I didn’t enable OEM Unlocking or whatever it’s called in the settings. Hoping for some tips, thanks!
piotrekkrzewi said:
Does it make a difference that after a while the phone responded and I can access download mode? I’m trying third firmware from a different source and still using home_csc to hopefully save the damn data.
Is there anything else I could try at this point? Still no access to recovery though.
Click to expand...
Click to collapse
If you're able to get into download mode, reflash the OEM firmware. You can try using HOME_CSC. Data wipe might be necessary if it bootloops.
piotrekkrzewi said:
What I am going to try now is to get twrp on the device and get the data off the phone this way. I don’t know if I can since I didn’t enable OEM Unlocking or whatever it’s called in the settings. Hoping for some tips, thanks!
Click to expand...
Click to collapse
If you didn't unlock the bootloader, this won't do you any good.
Are you seeing any error message on the download mode screen?
I forget if the A51 is a Mediatek device
Right now the device is dead again. I will be leaving it to charge and I hope it comes back alive, like it did before.
I’ve had bootloader errors on the download mode screen when I tried to install the firmware. At this point I am lost in what happened when, but I believe I got the bootloader errors when I tried to install the same firmware I’ve tried prior, so that doesn’t make sense.
I think the battery might be the problem here. It would turn off randomly before it bootlooped and it doesn’t hold charge now. The battery might’ve failed when an update was installing, but that’s just my detective work.
I will be replying with further tests when it turns on.
So, there is some weird behavior. After the phone charges for a few hours it tries to boot. If I hard reset it twice it dies. I need to hard reset it after it comes back and immadietly hold vol buttons to get it into download mode.
I can now experiment more. The original firmware version the phone came to me with is unable to install. Probably because I’ve already installed a newer version of android and it doesn’t allow me to go back. I’ve tried installing a newer bootloader and leave AP, CSC, CP. It fails harder, but I’m still able to try new firmware.
What do I try now? Data recovery is expensive, I’d love to try some stuff, but I don’t have enough time to do proper research and conduct experiments unfortunately.
Sounds like hardware problem if you can control temperature very precisely, you can try to remelt the solder if you know the temperature from the Service Manual. If not - leave to specialized service center who does this kind of thing all the time (ask them if they do).
In terms of flashing, to boot, maybe try Samsung Switch as it should be designed to preserve data however I am not vouching for it.
With Odin just skip the USERDATA and PIT
Doublecheck the exact model SM-Axxx ? Firmware files should be different per exact model.
Share pictures when you hit a problem.