Related
Hey guys, i've a big problem.
Yesterday, suddently my nexus s didn't boot. It was stucked on Google logo.
It's rooted and it has the cm7 rom.
I tryed to reflash with cw recovery but i have an issue.
I cannot copy nothing on the sdcard partition.
I mount it with recovery and correctly copy the img from my pc. After i sync and dismount but if i remount the sdcard i cannot see the file that i've copied before.
It seems strange because if i try to format sdcard from recovery it says "done" but the data still remain.
After that i tried to lock and reunlock my phone but it fail.
I launch the command fastboot oem unlock, correctly the two-choices window appear, i select yes but on my pc i see (erase fail) and bootload remain unlocked.
Please give me some advice to resurrect my phone.
Thanks for the support, and sorry for my bad english.
Emiliano
fastboot oem unlock wont lock it, use fastboot oem lock.
i need to unlock it. i've locked now i need to unlock.
But the procedure
fastboot oem unlock
fail with erase fail errore.
I had almost the exact same problem yesterday. Tried literally everything and nothing worked. In fact it kept getting a little worse with every battery pull/reboot.
I purposely re locked the boot loader, right before I went to Sprint and paid $38 for a working replacement.
Probably be a good long while before I root another phone.
Sent from my Nexus S 4G using Tapatalk
After 4.0.4 OTA update device is bricked.
I have experienced the same issue you are discussing here.
A couple of days ago I received an OTA update to android 4.0.4 for my Nexus S device, vodafone UK. My phone is NOT rooted or OEM unlocked. The update downloaded but fails to install on reboot. The phone just returns to the original state, with the update waiting to install.
Any app or software will not work on the device, force closes error. If I attempt to restore to any factory settings or wipe / format the phone by any method you can come up with in a google search!, once the device reboots this change is ignored. If I copy any file on the Mass storage via usb, after the phone reboots the file is gone.
I've attempted to unlock the oem to flash the device in an attempt to resolve this, however when using ./fastboot oem unlock I get the following error:
... FAILED (remote: Erase Fail)
It seems the device has been screwed some how after receiving this update. It can only be a hardware error now....
Who is now responsible to fix this? i have had this Nexus S over 1 year now, can I take to Samsung or Vodafone for these guys to get repaired?
Sounds like hardware issue. Have you tried formatting the sdcard in windows or running chkdsk /F.
I Have Same Problem how can i fix it?
LeeVidor said:
I have experienced the same issue you are discussing here.
A couple of days ago I received an OTA update to android 4.0.4 for my Nexus S device, vodafone UK. My phone is NOT rooted or OEM unlocked. The update downloaded but fails to install on reboot. The phone just returns to the original state, with the update waiting to install.
Any app or software will not work on the device, force closes error. If I attempt to restore to any factory settings or wipe / format the phone by any method you can come up with in a google search!, once the device reboots this change is ignored. If I copy any file on the Mass storage via usb, after the phone reboots the file is gone.
I've attempted to unlock the oem to flash the device in an attempt to resolve this, however when using ./fastboot oem unlock I get the following error:
... FAILED (remote: Erase Fail)
It seems the device has been screwed some how after receiving this update. It can only be a hardware error now....
Who is now responsible to fix this? i have had this Nexus S over 1 year now, can I take to Samsung or Vodafone for these guys to get repaired?
Click to expand...
Click to collapse
please anyone can help me how can i fix my mobile ...
You can't. It's a hardware common issue without any solution. Better sent it to repair. My two cents
Sent from my
( •_•)
( •_•)>⌐■-■
Nexus S
(⌐■_■)
YYYYYYYEEEEEAAAAAAAAAAHHHHHHHHHHHH
sammme problem har you fix it?
benazhack said:
i need to unlock it. i've locked now i need to unlock.
But the procedure
fastboot oem unlock
fail with erase fail errore.
Click to expand...
Click to collapse
please help me if u get the solution plz
zaherrrr said:
please help me if u get the solution plz
Click to expand...
Click to collapse
Already been posted, you can't, warranty repair or you need to replace the main board(guessing £100-200?)
Sent from my ice cream powered Nexus S
DarkhShadow said:
Already been posted, you can't, warranty repair or you need to replace the main board(guessing £100-200?)
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Just figured something out, i had the same issues as described above, could only boot the phone with a hair dryer
The new update Jelly Bean 4.1.1 is more forgiving when it comes to booting (probably voltages of the internal SD!! I'm still testing, but as far as i can see now, the phone boots normally again now (no more stuck on the google logo)
My problems:
- Not able to unlock bootloader (erase failed).
- Not possible to boot normally due to faulty internal SD card (only able to boot with the 'hairdryer' trick).
What did i do:
- Just tried the same as the trick on booting: use the hairdryer when fastbooting!!!
- Have everything ready; cmd, fastboot files, drivers etc, phone connected to computer with USB.
- Try to boot it first after heating the phone with the hairdryer (get past the google logo) and then immediately remove the battery.
- Then boot into fastboot mode (power and vol. up).
- Immediately execute the 'fastboot oem unlock' command.
Voila, that did the trick for me. Status OKAY and my bootloader was unlocked.
Then ROOT and update the phone to 4.1.1 with the following instructions:
(not able to unclude link, see webtrickz dot com/guide-to-manually-update-nexus-s-i9020ti9023-to-android-4-1-1-jelly-bean)
That did the trick for me!
NO MORE HAIRDRYER FOR ME!!
OEM unlock FAILED (remote: Erase Fail)
Hi
I'm replying to this message to share my experience about the same issu i had.
I bought a broken nexus s on google, auction described the phone as messed up during some software update. When cell got here:
- Bootloader was loading and locked
- Bootloader was reporting no boot image and no recovery
- Recovery was flashed with cwm 6.0.1.0
When trying to oem unlock, I was getting "FAILED (remote: Erase Fail)" no matter what I try. My config was good i've unlocked many nexus s with the same setup.
In recovery I was not able to mount sdcard, system, boot, nothing was working as it should.
After many frustrating hours, i saw this post.. What a stupid idea.. But I have nothing to loose at this point.
I don't have a hair dryer but I do have an oven. I figured the idea was to get the phone really hot..
Set the oven to 170, convection on and cooked the phone without the battery and cover for about 5 minutes until it was really hot but not melting.
Did the oem unlock and guess what.. It worked on first try.
After that I was able to update bootloader, radio, recovery and installed latest cm10. I've wipped the phone a couple of time, tried everything I could think of to test if something is not working, but everything does..
No hair dryer?
Just cook you phone at 170 for 5 minutes.
Worked for me.. go figure..
hetile
TimeClypse said:
Just figured something out, i had the same issues as described above, could only boot the phone with a hair dryer
The new update Jelly Bean 4.1.1 is more forgiving when it comes to booting (probably voltages of the internal SD!! I'm still testing, but as far as i can see now, the phone boots normally again now (no more stuck on the google logo)
My problems:
- Not able to unlock bootloader (erase failed).
- Not possible to boot normally due to faulty internal SD card (only able to boot with the 'hairdryer' trick).
What did i do:
- Just tried the same as the trick on booting: use the hairdryer when fastbooting!!!
- Have everything ready; cmd, fastboot files, drivers etc, phone connected to computer with USB.
- Try to boot it first after heating the phone with the hairdryer (get past the google logo) and then immediately remove the battery.
- Then boot into fastboot mode (power and vol. up).
- Immediately execute the 'fastboot oem unlock' command.
Voila, that did the trick for me. Status OKAY and my bootloader was unlocked.
Then ROOT and update the phone to 4.1.1 with the following instructions:
(not able to unclude link, see webtrickz dot com/guide-to-manually-update-nexus-s-i9020ti9023-to-android-4-1-1-jelly-bean)
That did the trick for me!
NO MORE HAIRDRYER FOR ME!!
Click to expand...
Click to collapse
hetile said:
Hi
I'm replying to this message to share my experience about the same issu i had.
I bought a broken nexus s on google, auction described the phone as messed up during some software update. When cell got here:
- Bootloader was loading and locked
- Bootloader was reporting no boot image and no recovery
- Recovery was flashed with cwm 6.0.1.0
When trying to oem unlock, I was getting "FAILED (remote: Erase Fail)" no matter what I try. My config was good i've unlocked many nexus s with the same setup.
In recovery I was not able to mount sdcard, system, boot, nothing was working as it should.
After many frustrating hours, i saw this post.. What a stupid idea.. But I have nothing to loose at this point.
I don't have a hair dryer but I do have an oven. I figured the idea was to get the phone really hot..
Set the oven to 170, convection on and cooked the phone without the battery and cover for about 5 minutes until it was really hot but not melting.
Did the oem unlock and guess what.. It worked on first try.
After that I was able to update bootloader, radio, recovery and installed latest cm10. I've wipped the phone a couple of time, tried everything I could think of to test if something is not working, but everything does..
No hair dryer?
Just cook you phone at 170 for 5 minutes.
Worked for me.. go figure..
hetile
Click to expand...
Click to collapse
I'm speechless..hair dryer works for me too!!! THANK YOU GUYS!
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
Okay, so I have never had any problems with this phone....until now. It suddenly fell into a crash/reboot cycle for about 8 hours until it finally crashed entirely. When I try to turn it on, it simply says "Google" on it. Then it stays on until the battery is dead. I tried to do a hard reset, and this is all that comes up...
christianpowell said:
Okay, so I have never had any problems with this phone....until now. It suddenly fell into a crash/reboot cycle for about 8 hours until it finally crashed entirely. When I try to turn it on, it simply says "Google" on it. Then it stays on until the battery is dead. I tried to do a hard reset, and this is all that comes up...
Click to expand...
Click to collapse
Well looks like it was unable to mount your sd card. For this, you have a fix. Please use the search button and i guess you will have to flash the stock factory image once again. Hope this helps.
christianpowell said:
Okay, so I have never had any problems with this phone....until now. It suddenly fell into a crash/reboot cycle for about 8 hours until it finally crashed entirely. When I try to turn it on, it simply says "Google" on it. Then it stays on until the battery is dead. I tried to do a hard reset, and this is all that comes up...
Click to expand...
Click to collapse
Try formatting cache a couple of times. This is caused due to a messed up /cache partition. If the bootloader is unlocked, you can manually flash the cache.img via fastboot. It will most probably fix it
vin4yak said:
If the bootloader is unlocked, you can manually flash the cache.img via fastboot. It will most probably fix it
Click to expand...
Click to collapse
I'm guessing he may be running completely stock.
OP, if attempting formatting of your cache doesn't work, you may have to bite the bullet and unlock your bootloader. That means you will lose everything on the phone.
This line: "e: failed to mount .../misc No such file or directory" is bothers me. That should not be missing.
Probably you have faulty emmc.
I assume you are on 100% stockt.
I wish I could have a device like yours to take a closer look on the gpt header partition.
Try do factory reset it could take 6 minutes or more. Be patient
. If that not solved your problem theb do a test. Try to unlock your bootloader. Then restart your device then check lock status again. If it goes back to locked then your problem is that the emmc is broken.
If that is the case can you allow me to take a look at your phone through teamviewer? If you are in then contact me on hangouts: [email protected] then we could arrange a time which good for both of us.
Wipe your cache partition.
It appears you did:
fastboot erase cache
Rather than:
fastboot format cache
Find a cache.img for your system version and push it through fastboot. Been there.
You guys are right, I am running completely stock. I am on Tmo and they have a replacement phone coming my way...Perhaps a better question is, should I be concerned about sending this thing in with all of my info still on it, or does it appear to be gone? I hesitate sending it in as a broken device with all of my stuff still on it. Thanks for your responses and you time.
christianpowell said:
You guys are right, I am running completely stock. I am on Tmo and they have a replacement phone coming my way...Perhaps a better question is, should I be concerned about sending this thing in with all of my info still on it, or does it appear to be gone? I hesitate sending it in as a broken device with all of my stuff still on it. Thanks for your responses and you time.
Click to expand...
Click to collapse
To wipe it completely, run fastboot oem unlock (google it if that doesn't mean anything to you) then fastboot oem lock
The phone will be back to factory state and ALL of your personal information will be scrubbed
Same thing happened to my phone it's easily fixable. Don't take my lack of posts as lack of knowledge. You need to fastboot push cache.IMG.
SilkyJohnson said:
Same thing happened to my phone it's easily fixable. Don't take my lack of posts as lack of knowledge. You need to fastboot push cache.IMG.
Click to expand...
Click to collapse
Considering you push in ADB and flash in fastboot I'd be suspect about your knowledge.
theesotericone said:
Considering you push in ADB and flash in fastboot I'd be suspect about your knowledge.
Click to expand...
Click to collapse
I literally mean push the file to the phone, but here's the command since you want to be an ass:
fastboot flash cache cache.img
(assuming image file is named cache)
SilkyJohnson said:
I literally mean push the file to the phone, but here's the command since you want to be an ass:
fastboot flash cache cache.img
(assuming image file is named cache)
Click to expand...
Click to collapse
I wasn't trying to be an ass. You just need to be a little more specific when dealing with things. That last command is the correct one. But your first post would have had some poor noob pulling his hair out after trying to push with fastboot.
hi - i have in my nexus 5 only the google logo and the unlocked key is on the screen;
when i get to fast boot it does see the device.
when ienter " fastboot oem device-info
igot device tampered true
device unlock true
off mode charge - true
when i try to write twrp recovery it says sending recovery okay and writing recovery okay.
but ucant enter to the recovery of twrp.
when i try to flash an image it says:
writing bootloader
failed (remoteflash write failure)
rebooting into bootloader okay
writing radio - failed remoteflash write failure
target reported max size of 1073741824bytes
is there any way to save my phone?
i can enter adb its says on the phone "now send the package you want to apply to the device with "adb sideload filename"..
how do i can send an image?
thank u
re
i try to flash with the lg flash rool - i did everything ok and it stuck in 6% and says"user data erase fail" what can i do?
You're using the batch commands included with the stock ROM to re-flash?
Hi my Nexus 5 also suddenly die too. And I have the same exact problem that you have when trying to flash it. I looked for hours on the internet tried formatting, erasing and many other alternatives and nothing. There are some people experiencing this same problem like us. For no reason the memory is getting corrupt or died. I get mant errors on the cache when I boot to regular recovery. The only recovery that I have manage to boot to (except for the original one) is Clockworkmod using fastboot boot "therecoveryname.img". With clockworkmod I have adb working but still can get the phone to boot or accept factory images. I can't lock the bootloader either.
I think this error was cause by the software. There was a very similar problem that never got fixed for the nexus 7 when lollipop came out.
Do you need to lock the bootloader? Once locked, you cannot flash anything via fastboot commands, not even a stock ROM.
No I don't need to. I tried just to see if the phone will relock itself. I read somewhere in the internet that if you can't relock/unlock the device the nand if fried.
If you look for these errors there are people with LG G2 and LG G3 that are having something similar happen. I think LG hardware is partly behind the problem. I call Google and told them about it and the put me through LG which want me to send the phone for repairs but not free. My guess is that it will be way to expensive to repair and that is not worthy.
Hopefully someone with real repair skill can give us light if this is something fixable by software.
audit13 said:
Do you need to lock the bootloader? Once locked, you cannot flash anything via fastboot commands, not even a stock ROM.
Click to expand...
Click to collapse
I had two different Nexus 5 phones that were stuck in a bootloop with the spinning coloured KK animation.
Every time I unlocked the bootloader, the bootloader would always re-lock itself when rebooting. Even when I managed to unlock the bootloader, I could not re-flash a stock ROM because the bootloader kept relocking itself.
Whenever I unlocked the bootloader, the phone would only take 2 ot 3 seconds to wipe the phone which is too fast.
In the end, I purchased a nexus 5 with a smashed screen to use its motherboard in my defective N5.
I have never come across a post where someone was able to solve the problem unless they had LG replace the motherboard with a new imei.
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.