Related
Greetings! First of all, I would like to thank anyone who takes the time to help me diagnose and resolve this issues, let alone anyone who takes the time to read this thread.
I've been having issues with my Xoom (ICS 4.0.0) for about 3 weeks now.
A brief history of the issue's occurrence:
-I unrooted the device and returned it to stock.
-Everything was fine and dandy until one day it spontaneously said something along the lines of 'Android is upgrading..', and then performed a reset.
-Since resetting, it bootloops.
The device only turns on when plugged into a charger and hard reset.
The device only turns off when allowed to boot loop for minutes and then hard reset (it simply does not reset, and just turns off).
I'm not the most technically-savvy person with android devices but here are some things I've done/noted.
When trying to use adb commands, it does not recognize the device or properly issue commands.
I've tried wiping data/clearing cache to no avail.
EDIT: I've tried fastbooting, but the bootloader will not unlock. When trying to unlock, it simply resets and then acts as though it was never unlocked.
I have no idea how to return it to a stock image. All I know is that I have a micro-SD and some spare time.
Could anyone help me understand what exactly is going on with my Xoom?
If I can provide you with any more information, please let me know.
Thanks again. (=
If it was stock and spontaneously upgraded it sounds like a bad OTA upgrade. I've been rooted from the start so never have taken an OTA upgrade...don't you need to accept it or can it just upgrade on it's own?
Anyway, can you get it into fastboot mode?
Volume up and power, then at dual core screen, press volume down...if you see something like "entering fastboot mode" you're not bricked. You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
If you haven't done so, just google 'recovering Xoom using fastboot' and you should get some good information.
Good luck!
Remember to grab the MZ604 files if you have the Wifi only version of the Xoom.
http://developer.motorola.com/products/software/ <------ Grab the files here. The files are for the US version of the Wifi Xoom only.
Instructions to return it to stock
1) First you need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
Should have these drivers installed if you have rooted your Xoom before.
2) Make sure you have the latest SDK - adb and fastboot should be in /platform-tools -
http://developer.android.com/sdk/index.html
Should have the android SDK if you have rooted your Xoom before.
3) Place all the downloaded stock image files into the SDK Tools folder.
4) If you are booting up from scratch, you can get the Xoom in fastboot mode by doing the following. Use command prompt to perform the rest of the steps
Hold VolDown and Power button will boot unit for fastboot mode
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
If you Xoom is booted up already follow the commands below using command prompt to perform the steps
adb reboot bootloader <---- reboots the Xoom into fastboot mode.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
As Always If This Was Helpful Hit the Thanks!
Yeah, what Mjamocha said...
okantomi said:
Yeah, what Mjamocha said...
Click to expand...
Click to collapse
LOL Thanks.
okantomi said:
Anyway, can you get it into fastboot mode?
Click to expand...
Click to collapse
Yes, I can. But so far nothing has been successful in terms of fastboot commands.
okantomi said:
You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
Click to expand...
Click to collapse
When I try to execute fastboot commands such as 'fastboot flash boot boot.img'.. it says the following:
Device still locked. Device must be unlocked first. Failed to process command error(0x8)
Whenever I try to unlock the bootloader, it appears to be successful at first and then the device reboots. But it just reboots to a bootloop, and the bootloader still says its locked. Perhaps I made a mistake in communication. The bootloader is currently locked and will not unlock, as just described.
When I try to unlock it and it reboots, even if I access the fastboot menu right away, it still says the device is still locked.
Thoughts?
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
slacka-vt said:
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
Click to expand...
Click to collapse
Yes, I can get into android recovery. However, within a second of switching into recovery mode, the robot falls down and there appears to be a red triangle caution sign containing an exclamation point.
When trying to do a factory reset, it says all data is wiped (as normal). Upon rebooting, it continues to bootloop. So essentially the factory reset and cache clear options in the Android Recovery menu do not produce the expected results.
Pretty odd. I didn't mess with the Xoom at all prior to this issue.
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
slacka-vt said:
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
Click to expand...
Click to collapse
Yeah, just tried it to no avail. Thanks so much for your help anyway. (=
I'm not sure what to do now.
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
slacka-vt said:
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
Click to expand...
Click to collapse
I hear ya. I've tried 2 different cords and 3 different computers. I'm using a Mac (10.6.8) right now, but have used 2 PCs (Vista + 7).
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
slacka-vt said:
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
Click to expand...
Click to collapse
I got the 'device still locked' error. Weird, huh?
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
slacka-vt said:
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
Click to expand...
Click to collapse
Yeah I tried that. Won't lock or unlock successfully. Locking produces no difference, and unlocking produces the same 'device still locked' error. This is getting out of hand! Thanks so much for your advice. You think I should open it up?
I hate to be so persistently annoying about this, but could anyone possibly suggest a method of working around the locked bootloader?
Is there anything I can do with an SD card to remedy the device's stubborn foolery?
I think you should give it a try, I have bricked my xoom a few times and have always been able to flash the stock imagine to recover. You really have nothing to lose by pulling the battery pin just be careful.
Sent from my Xoom using xda premium
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
cherlamperter said:
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
Click to expand...
Click to collapse
I have looking for a utube how to guide but no luck, I just might make one for you so you will know what to expect. Give me a few and I will get back to ya.
Sent from my Xoom using xda premium
Hey guys, how are you?
Well, I wished to root my Moto G, so I (tryed?) to unlock the bootloader. Alright, done it, but then I ran into some trouble...
After the booting up, everything started forceclosing and since then, when I try to boot it, I get a black screen after the Motorola logo.
Now, I am really really worried about my phone. I got it a month ago. I'm so afraid I really f****d up my phone right now that my hands are shaking.
I'm new to Android, so sorry if the solution is pretty obvious. And if it's not, could explain it very carefully to me? I don't know what to do.
My best wishes to you, guys.
I'm assuming you used superboot if so that would happen.
The logo sort of blured out right just press volume down and power and it would work
Or did this happen when you were just trying to unlock bootloader?
TomGlass1 said:
I'm assuming you used superboot if so that would happen.
The logo sort of blured out right just press volume down and power and it would work
Or did this happen when you were just trying to unlock bootloader?
Click to expand...
Click to collapse
Yeah, that happenned when I was trying to unlcok bootloader.
And well, my computer now doesn't even recognizes my phone.
EDIT: It appears as "Fastboot falcon S" in the Device Manager. Tried installing some drivers I found in the Internet, but it didn't work.
Explain exactly what happened please. Was the unlock successful and did you just bootup normally after or did u do anything else in fastboot mode? Why are you trying to install fastboot drivers again, as you already wouldve had them to unlock the bootloader. Did you try installing recovery or some root img from fastboot? You said its forceclosing, but it isnt starting at all now?
Some things you can do right now (if your bootloader is unlocked) is to flash a recovery (twrp,cwm) through fastboot and if you think most system files (or settings) are beyond repair, flash your firmware version though fastboot. Will point you to the guides for them, but post more info if you want help.
hemanthmahesh said:
Explain exactly what happened please. Was the unlock successful and did you just bootup normally after or did u do anything else in fastboot mode? Why are you trying to install fastboot drivers again, as you already wouldve had them to unlock the bootloader. Did you try installing recovery or some root img from fastboot? You said its forceclosing, but it isnt starting at all now?
Some things you can do right now (if your bootloader is unlocked) is to flash a recovery (twrp,cwm) through fastboot and if you think most system files (or settings) are beyond repair, flash your firmware version though fastboot. Will point you to the guides for them, but post more info if you want help.
Click to expand...
Click to collapse
Alright, just after I unlocked, when I was booting, I got a message saying that "xxxx has stopped working/failed to initialize/something like that". And then, when I rebooted, I got the usual message of the "bootlocker has been unlocked". After that, the Motorola logo started animating, but then I just got a black screen. I can't turn it off and the battery just got depleted (I'm charging right now).
When I try to connect it in my computer, the PC recognizes it as "MTP Device" or "Fastboot falcon S" when fastbooted. I can't install any drivers and the Motorola Device Manager doesn't recognizes it either.
Well, if there is some missing information, just ask me. I tried to describe my problem the best I could. Anyway, sorry for my bad English and thanks in advance for any effort trying to discover what's wrong.
Motorola Device Manager isn't helpful in this state as it doesn't handle things in fastboot. You already have all the required drivers (fastboot falcon S is the right driver afaik, falcon being motog codename) for flashing your stock firmware.
1. First, you can try the "Factory" option in bootloader (the third one, use volume down to move selector, volume up to select), though this might not really work for major issues.
2. When in fastboot mode, use "fastboot getvar all" to get the firmware details if you already didn't know about it.
3. Otherwise if yours is a standard gsm (non dualsim/non cdma), just download Blur_Version.174.44.9.falcon_umts.Retail.en.GB (UK stock for gsm, 4.4.2)
Download the mfastboot files to use rather than fastboot for flashing. You might need to modify your commands a bit for various firmwares.
http://forum.xda-developers.com/showthread.php?p=47820707 (refer this thread for flashing your stock firmware)
All the firmwares are in either of the links below (all around 400mb):
http://sbf.droid-developers.org/phone.php?device=14
(or)
http://www.filefactory.com/folder/c6cdedc45a775d27
I still don't get why many ppl are getting these errors after unlocking, very bad unlock method of moto if so ( I didnt get any such issues though).
When I use the "fastboot getvar all" command, it says "waiting for device". The phone is already connected, but the Moto G doesn't recognizes it's connected either.
I'm getting more and more afraid I really hardbricked it.
http://www.mymotocast.com/download/MDM?platform=windows
Tried installing these drivers? Your fastboot doesn't seem to be setup properly. How did you unlock without a working fastboot driver? You are trying that command in bootloader mode right?
Already installed it from the start. The message I got is always this:
"There aren't any updates for your device at the moment
Current Version: N/A"
My fastboot: Doesn't matter the operation I do, I always get this <waiting for device> and the phone is already connected into the computer. And the phone doesn't recognizes it is connected too.
And greeeeat news: my phone now doesn't charges either. I get stuck on a screen with a battery logo and 0%, when connected to the charger. Still, I still can access the fastboot mode. Well, am I lucky or not?
I'm pretty confused with this. How exactly did you unlock without a working fastboot (no waiting for device issue)? Did you change your pc drivers after unlock or trying this from a different pc? When you say "phone doesn't recognizes it is connected" you mean it says "Connect USB data cable" below "Device is UNLOCKED"? If so, maybe try another usb port cause it should normally say "Transfer Mode: USB Connected" regardless of proper drivers.
Your phone will chrarge no matter what though, no worry about that. It needs to say "Battery OK (Charging)" when connected to PC
No, as long as you have working your device isn't technically bricked in any sense. Don't worry, get that fastboot working again and anything can be fixed.
Also you didnt say whether or not you tried that "Factory" option in bootloader!
hemanthmahesh said:
I'm pretty confused with this. How exactly did you unlock without a working fastboot (no waiting for device issue)? Did you change your pc drivers after unlock or trying this from a different pc? When you say "phone doesn't recognizes it is connected" you mean it says "Connect USB data cable" below "Device is UNLOCKED"? If so, maybe try another usb port cause it should normally say "Transfer Mode: USB Connected" regardless of proper drivers.
Your phone will chrarge no matter what though, no worry about that. It needs to say "Battery OK (Charging)" when connected to PC
No, as long as you have working your device isn't technically bricked in any sense. Don't worry, get that fastboot working again and anything can be fixed.
Also you didnt say whether or not you tried that "Factory" option in bootloader!
Click to expand...
Click to collapse
OMG. I tried that "Factory" option before but it didn't work. Now I tried a second time and it worked. Thanks a lot! Really :laugh:
Anyway, now my phone is back again and rooted. Thanks for the help, guys!
Thaiane said:
Already installed it from the start. The message I got is always this:
"There aren't any updates for your device at the moment
Current Version: N/A"
My fastboot: Doesn't matter the operation I do, I always get this <waiting for device> and the phone is already connected into the computer. And the phone doesn't recognizes it is connected too.
And greeeeat news: my phone now doesn't charges either. I get stuck on a screen with a battery logo and 0%, when connected to the charger. Still, I still can access the fastboot mode. Well, am I lucky or not?
Click to expand...
Click to collapse
Guys the problem occurs due to corruption of /data folder. Even I had the same issue.
What you can do is
1. Connect your phone to PC in fastboot mode.
2. In fastboot, enter the command "adb erase userdata" and "adb erase cache" without quotes and reboot you phone. It will work for most of the devices, if it doesn't I have some other workaround too.
help
forgotter said:
Guys the problem occurs due to corruption of /data folder. Even I had the same issue.
What you can do is
1. Connect your phone to PC in fastboot mode.
2. In fastboot, enter the command "adb erase userdata" and "adb erase cache" without quotes and reboot you phone. It will work for most of the devices, if it doesn't I have some other workaround too.
Click to expand...
Click to collapse
I have the same problem. my phone stuck in blank screen after Unlock Bootloader. and then I try to do "adb erase userdata" and "adb erase cache". but my phone has no chenge, still stuck in.
I attach log when enter command adb above.
I'm sorry before. I can't spech English well
jidurrr said:
I have the same problem. my phone stuck in blank screen after Unlock Bootloader. and then I try to do "adb erase userdata" and "adb erase cache". but my phone has no chenge, still stuck in.
I attach log when enter command adb above.
I'm sorry before. I can't spech English well
Click to expand...
Click to collapse
The log you have posted contains only the help commands of adb and not the actual commands you gave.
Give a try to factory reset from fastboot mode on your phone. And do you a custom recovery installed in your phone?
forgotter said:
The log you have posted contains only the help commands of adb and not the actual commands you gave.
Give a try to factory reset from fastboot mode on your phone. And do you a custom recovery installed in your phone?
Click to expand...
Click to collapse
I've tried factory reset for several times, but no change as well.
yes, I get a CWM in my phone. and then, what have I do?
jidurrr said:
I've tried factory reset for several times, but no change as well.
yes, I get a CWM in my phone. and then, what have I do?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2704207
Go to the above forum.
Sorry for late reply was busy with studies.
I had flash stock firmware
through PC
I have a Moto G that has gotten "stuck", if that's a good description. If I start it, the initial Moto splash screens go fine and then it becomes a dark screen but backlight On and just stays stuck there for ever. (Is this what is called a boot loop? Not sure)
By using the Power + Down Vol key combo I did manage to get it to the boot menu. Unfortunately the Recovery Option there does not work. Shows a quick Moto bootup splash screen, then Says "Boot up failed" and falls to the boot menu again.
What's my best bet to recover from this?
I did install adb + fastboot on my laptop & then connected the Moto G with a USB Cable. fastboot seems to work. I could get the phone to reboot, and some other basic diagnostics. e.g. "fastboot oem get_unlock_data works". "fastboot devices" also shows my device Serial Number correctly. But I want to be careful before I issue any further erase or flash commands so I thought it best to post on here. What is the logical next step in the debug?
"adb devices" did not succeed.
The phone had the original Google / Motorola software so far and I'd never even attempted to flash it etc. Only whatever automatic updates got pushed by Google / Moto / Carrier over the network. Right before this happened I was in a call and got a bunch of pop ups saying Application xxx was being shut down.
The phone is out of warranty. It is still locked, but when I enter the details on the Moto Website it says it can be unlocked. So I can proceed to get the unlock codes etc. if that helps.
The exact SKU is XT1033. Boot menu says (Version 41.13; Battery OK; Device is locked; Status Code 0) if that is of any help. Was a Dual SIM phone on a GSM Carrier.
Tried issuing the commands
Code:
fastboot erase cache
fastboot erase userdata
Both don't seem to have helped at all.
Any other ideas?
To flash anything you first need to unlock bootloader. Doing that erases all your data including internal memory. Then you can flash a recovery & a custom rom.
legolas06 said:
To flash anything you first need to unlock bootloader. Doing that erases all your data including internal memory. Then you can flash a recovery & a custom rom.
Click to expand...
Click to collapse
Thanks @Legolas!
I did not realize that. So I guess if I just tried a flashboot flash command it would fail since my phone is not unlocked at the moment.
Luckily I can get the unlock code from the Motorola site. I will proceed to do that then first and subsequently try all the other steps needing flashing.
What happened? Did you manage to boot it up?
@carefulcat : i have a similar problem as a well.let me know if and how you managed to fix it
Lucariel said:
What happened? Did you manage to boot it up?
Click to expand...
Click to collapse
@Lucariel
Sadly not. It is still lying dead.
If you have any ideas let me know!
ravibhat said:
@carefulcat : i have a similar problem as a well.let me know if and how you managed to fix it
Click to expand...
Click to collapse
No luck yet. If you find any ideas let me know!
@carefulcat :
Check out my thread @ http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492
The only difference I find from what you've shared is that both of us have different bootloaders.
Let me know if this is true.
ravibhat said:
@carefulcat :
Check out my thread @ http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492
The only difference I find from what you've shared is that both of us have different bootloaders.
Let me know if this is true.
Click to expand...
Click to collapse
Indeed. Very similar problems. Could be identical.
I've, in fact, even erased via fastboot & unlocked via motorola's site. Hasn't helped so far.
I haven't had the stomach to download a 500 MB stock firmware yet.
Who do you think our bootloader is different?
@carefulcat :
Well,I am on an unlocked unrooted Android L 5.0.2 XT1033 Asia Retail Edition (upgraded via OTA) which has Bootloader version 41.18.
You've just cleared the ROM it seems.
Unlocking the bootloader will wipe off all the data from your device.
It seems yours is still locked,you have the unlock code but didn't use it.
Which OS did you have?Exact version,region and type of upgrade.
And which commands have you used till now?
If you're clear with the basics try stocking a Stock Flash ROM (depending on your bootloader and previous OS) or custom recovery like TWRP or CW.
carefulcat said:
Indeed. Very similar problems. Could be identical.
I've, in fact, even erased via fastboot & unlocked via motorola's site. Hasn't helped so far.
I haven't had the stomach to download a 500 MB stock firmware yet.
Who do you think our bootloader is different?
Click to expand...
Click to collapse
carefulcat said:
@Lucariel
Sadly not. It is still lying dead.
If you have any ideas let me know!
Click to expand...
Click to collapse
Took it to a repair shop, the said something was wrong with my mother, they fixed that and now the phone enters into recovery, what wont boot.
Will try the "qhsusb_dload" thing this week.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the "Deuces" script or to flash a new system image.
I have tried all of the basic stuff to get to my device to be recognized. I downloaded and installed the latest ADB & Fastboot and I have tried different cables and USB ports and still have no luck. I'm really worried and not sure what to do if I cannot get my device to accept fastboot commands so I can recover.
Please let me know if you have any ideas that may help me.
Jason
EDIT:
I still have no idea what I did, but I decided to use the Skipsoft Tool to see if it would work. Lucky for me it did and I was able to restore the factory image. Sorry for the fire-drill, I should have tried this before I posted. Thank you for the replies!!
Grab the latest Google platform tools and USB drivers. When your device is plugged in, do you see any unknown devices in your device manager? Or anything that looks like it could be your phone?
jascolli said:
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the "Deuces" script or to flash a new system image.
I have tried all of the basic stuff to get to my device to be recognized. I downloaded and installed the latest ADB & Fastboot and I have tried different cables and USB ports and still have no luck. I'm really worried and not sure what to do if I cannot get my device to accept fastboot commands so I can recover.
Please let me know if you have any ideas that may help me.
Jason
Click to expand...
Click to collapse
I've seen that before.
When you select reboot bootloader does that message go away?
Try it without the cable plugged in does it go away then?
I just want to know if you can actually get that message to go away or not at this point.
Also can you link the tools you are downloading
jascolli said:
I still have no idea what I did, but I decided to use the Skipsoft Tool to see if it would work. Lucky for me it did and I was able to restore the factory image. Sorry for the fire-drill, I should have tried this before I posted. Thank you for the replies!!
Click to expand...
Click to collapse
For future learning, I'd recommend you familiarize yourself with how to do this without toolkits. A toolkit is nice, but it really helps to understand what the toolkit is doing so that if you have an issue you know what to do next.
Telperion said:
For future learning, I'd recommend you familiarize yourself with how to do this without toolkits. A toolkit is nice, but it really helps to understand what the toolkit is doing so that if you have an issue you know what to do next.
Click to expand...
Click to collapse
Solid advice, thank you.
I did this same thing and solved it the same way. I think things just get funky and the tool you mentioned to fix it.
nolimit78 said:
I did this same thing and solved it the same way. I think things just get funky and the tool you mentioned to fix it.
Click to expand...
Click to collapse
Yeah I'm baffled. I could not for the life of me get fastboot to work. That Skipsoft tool is pretty impressive.
HELP!!!!
I have same problem, so which functions you use to fix it????
jascolli said:
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the "Deuces" script or to flash a new system image.
I have tried all of the basic stuff to get to my device to be recognized. I downloaded and installed the latest ADB & Fastboot and I have tried different cables and USB ports and still have no luck. I'm really worried and not sure what to do if I cannot get my device to accept fastboot commands so I can recover.
Please let me know if you have any ideas that may help me.
Jason
EDIT:
I still have no idea what I did, but I decided to use the Skipsoft Tool to see if it would work. Lucky for me it did and I was able to restore the factory image. Sorry for the fire-drill, I should have tried this before I posted. Thank you for the replies!!
Click to expand...
Click to collapse
Same thing happened to me. I need help. Please tell me how you unbricked your phone
same problem
i have the same problem already download skipsoft program but dont have results can you tell me the steps what you do please
---------- Post added at 07:48 AM ---------- Previous post was at 07:43 AM ----------
yuva_cool said:
Same thing happened to me. I need help. Please tell me how you unbricked your phone
Click to expand...
Click to collapse
do you already unbricked your phone?
my pixel still cant be detected by that toolkit, can u list the step by step procedure what u did to unbrick the device?
I was having the exact same issue as OP. I wound up fixing it by entering fastboot and making it display barcodes until the battery died. Then I put a rubber band over the power button so the red led would blink (I wanted to completely drain the battery). When it stopped blinking, I hooked my dead phone up to my PC via a USB 3 port and held Power + vol down to boot into fastboot (the battery was still too low for the phone to boot normally -- it would just show the battery icon). Surprisingly, my PC recognized my phone (made the little USB sound) and I was able to fastboot flash-all the newest factory image on it!! No toolkits required!
I'm so happy because this was a last ditch effort before I sent my original phone back to google and would have to live with the RMA they sent me which could not be bootloader unlocked (this is a whole other issue!)
I hope this helps!
EDIT: Info I provided in a PM
Unfortunately I didn't take any photos of the process... I didn't want to push my luck and things are working now. But The photo I've attached was exactly what I was seeing except I was on the December update (Now I'm on the January update) ... and:
UFS: 128 GB Hynix
DRAM: 4096MB Micron LPDDR4
Device State: unlocked (I had been unlocked since April 2018)
Until I had entirely drained my battery, I couldn't do anything. Download mode and recovery mode were impossible to access. I forgot the specific error, but it was the same as a lot of other people who have been having this problem.
The only thing I could do was to restart bootloader, which removed the error message until I tried to do anything. I couldn't boot at all or do anything conducive to fixing my phone until I drained the battery entirely. I couldn't get any PCs to even acknowledge the existance of my phone until after the battery was drained.
Keep in mind, I NEVER got my RMA phone to work. I was only able to fix my original NEW phone that I had purchased directly from google.
Until I had entirely drained my battery, I couldn't do anything. Download mode and recovery mode were impossible to access. I forgot the specific error, but it was the same as a lot of other people who have been having this problem.
The only thing I could do was to restart bootloader, which removed the error message until I tried to do anything. I couldn't boot at all or do anything conducive to fixing my phone until I drained the battery entirely. I couldn't get any PCs to even acknowledge the existance of my phone until after the battery was drained.
Click to expand...
Click to collapse
This is the correct resolution to this issue.
I had the same issue, no usb in bootloader. I drained the phone and rebooted into the Bootloader flash A and B side bootloader the Aug 2018 (previously working for me) and A and B side Radio, as well as the System image. After that everything booted fine.
Attempted to install the January update the same way and it worked as well.
Seems like they messed up A and B side flashing
My steps::: For Lurkers having this issue.
1. Drain battery DEAD!
2. Boot Bootloader (Vol Down + Power)
3. fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img (or whatever image)
3. fastboot set_active b (opposite of the one on screen)
4. fastboot reboot-bootloader
5. fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img (or whatever image) (Again)
6. fastboot reboot-bootloader
7. fastboot flash radio radio-walleye-g8998-00253-1809191716.img (or whatever image)
8. fastboot set_active a (opposite of the one on screen)
9. fastboot reboot-bootloader
10. fastboot flash radio radio-walleye-g8998-00253-1809191716.img (or whatever image)
11. fastboot reboot-bootloader
12. fastboot update image-walleye-pq1a.190105.004.zip (or whatever image)
Phone boots properly, and is updated.
thedude9821 said:
I was having the exact same issue as OP. I wound up fixing it by entering fastboot and making it display barcodes until the battery died. Then I put a rubber band over the power button so the red led would blink (I wanted to completely drain the battery). When it stopped blinking, I hooked my dead phone up to my PC via a USB 3 port and held Power + vol down to boot into fastboot (the battery was still too low for the phone to boot normally -- it would just show the battery icon). Surprisingly, my PC recognized my phone (made the little USB sound) and I was able to fastboot flash-all the newest factory image on it!! No toolkits required!
I'm so happy because this was a last ditch effort before I sent my original phone back to google and would have to live with the RMA they sent me which could not be bootloader unlocked (this is a whole other issue!)
I hope this helps!
EDIT: Info I provided in a PM
Unfortunately I didn't take any photos of the process... I didn't want to push my luck and things are working now. But The photo I've attached was exactly what I was seeing except I was on the December update (Now I'm on the January update) ... and:
UFS: 128 GB Hynix
DRAM: 4096MB Micron LPDDR4
Device State: unlocked (I had been unlocked since April 2018)
Until I had entirely drained my battery, I couldn't do anything. Download mode and recovery mode were impossible to access. I forgot the specific error, but it was the same as a lot of other people who have been having this problem.
The only thing I could do was to restart bootloader, which removed the error message until I tried to do anything. I couldn't boot at all or do anything conducive to fixing my phone until I drained the battery entirely. I couldn't get any PCs to even acknowledge the existance of my phone until after the battery was drained.
Keep in mind, I NEVER got my RMA phone to work. I was only able to fix my original NEW phone that I had purchased directly from google.
Click to expand...
Click to collapse
omg after months of figuring it out ,and almost opt for warranty,finally my pixel is aliveeeee, thanks alot for the fix im so glad.. and whats more important for me is the data is still intact! i cant thank you enough.. google messed up december update pretty bad.
I just received my 4th RMA and the bootloader wasn't able to unlock. So to my surprise Google is giving me a full refund? I purchased my Pixel 2 back in Nov 2017 ?
Dajax2 said:
3. fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img (or whatever image)
Click to expand...
Click to collapse
@Dajax2 Super new to this and it may be a total waste since my bootloader screen says "Device State: locked" but in trying to flash or even sideload ota, the command returns "error: cannot load (file location/name): no such file or directory found". Again, total noob and I don't even know if I'm supposed to unzip the folder or not but have tried both ways with the same error.
It returns the serial number for fastboot devices but nothing for adb devices. I obviously didn't have OEM or USB debugging enabled prior. Hoping I can at least get in to retrieve data before giving up all hope :/
Solved. Enter barcode mode. In this screen, check for devices from adb or fastboot. It should be there. You are now able to switch slots and do all the fastboot things.
Great workaround that I would never have thought - good info here, thanks everyone!
dianea said:
Solved. Enter barcode mode. In this screen, check for devices from adb or fastboot. It should be there. You are now able to switch slots and do all the fastboot things.
Click to expand...
Click to collapse
Edit - My phone wasn't detected when on the barcode screen, just like from the main bootloader screen.
HOWEVER... to my surprise.. the above method of draining the battery completely to 0% actually worked. I'm a little dumbfounded why this allowed the bootloader to connect via fastboot again, but it did. I was able to flash the latest factory image (without wipe) and boot back up like nothing ever happened. Thank you so much for the tip. I passed this along to Google support and they also said they appreciate the troubleshooting and asked me to just send back the replacement phone with the RMA package/label.
---------- Post added at 06:36 PM ---------- Previous post was at 06:18 PM ----------
thedude9821 said:
Keep in mind, I NEVER got my RMA phone to work. I was only able to fix my original NEW phone that I had purchased directly from google.
Click to expand...
Click to collapse
Did they accept the RMA phone back and remove the temp auth on your card?
thedude9821 said:
I was having the exact same issue as OP. I wound up fixing it by entering fastboot and making it display barcodes until the battery died. Then I put a rubber band over the power button so the red led would blink (I wanted to completely drain the battery). When it stopped blinking, I hooked my dead phone up to my PC via a USB 3 port and held Power + vol down to boot into fastboot (the battery was still too low for the phone to boot normally -- it would just show the battery icon). Surprisingly, my PC recognized my phone (made the little USB sound) and I was able to fastboot flash-all the newest factory image on it!! No toolkits required!
I'm so happy because this was a last ditch effort before I sent my original phone back to google and would have to live with the RMA they sent me which could not be bootloader unlocked (this is a whole other issue!)
I hope this helps!
EDIT: Info I provided in a PM
Unfortunately I didn't take any photos of the process... I didn't want to push my luck and things are working now. But The photo I've attached was exactly what I was seeing except I was on the December update (Now I'm on the January update) ... and:
UFS: 128 GB Hynix
DRAM: 4096MB Micron LPDDR4
Device State: unlocked (I had been unlocked since April 2018)
Until I had entirely drained my battery, I couldn't do anything. Download mode and recovery mode were impossible to access. I forgot the specific error, but it was the same as a lot of other people who have been having this problem.
The only thing I could do was to restart bootloader, which removed the error message until I tried to do anything. I couldn't boot at all or do anything conducive to fixing my phone until I drained the battery entirely. I couldn't get any PCs to even acknowledge the existance of my phone until after the battery was drained.
Keep in mind, I NEVER got my RMA phone to work. I was only able to fix my original NEW phone that I had purchased directly from google.
Click to expand...
Click to collapse
Dajax2 said:
This is the correct resolution to this issue.
I had the same issue, no usb in bootloader. I drained the phone and rebooted into the Bootloader flash A and B side bootloader the Aug 2018 (previously working for me) and A and B side Radio, as well as the System image. After that everything booted fine.
Attempted to install the January update the same way and it worked as well.
Seems like they messed up A and B side flashing
My steps::: For Lurkers having this issue.
1. Drain battery DEAD!
2. Boot Bootloader (Vol Down + Power)
3. fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img (or whatever image)
3. fastboot set_active b (opposite of the one on screen)
4. fastboot reboot-bootloader
5. fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img (or whatever image) (Again)
6. fastboot reboot-bootloader
7. fastboot flash radio radio-walleye-g8998-00253-1809191716.img (or whatever image)
8. fastboot set_active a (opposite of the one on screen)
9. fastboot reboot-bootloader
10. fastboot flash radio radio-walleye-g8998-00253-1809191716.img (or whatever image)
11. fastboot reboot-bootloader
12. fastboot update image-walleye-pq1a.190105.004.zip (or whatever image)
Phone boots properly, and is updated.
Click to expand...
Click to collapse
Gifted both of you Ad-Free for this.
You saved me $300 and the annoyance of having to wait for shipping for either RMA or another phone on Swappa.
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.