Related
A long time ago I rooted my phone and put CM9 on it. I decided I wanted to go back and try Jelly Bean (from factory then go outwards).
I had a difficult time with the CM flash and found one that worked, and thought I was good to go.
My phone: gt-i9020a nexus s
Product name: Herring
HW version 16
boot loader: i 9020xxkl
carrier att
fastboot enabled
unlocked state.
I can launch the official 2.3.6 (Build GRK39F), from google
then the OTA updated kicks in and the phone is stuck at 'boot' Google logo on the screen.
I have done the information below and the same keeps happening...
link: http://forum.xda-developers.com/showthread.php?t=1586845
first of all, the VQ8PQk is a patch file, not a full rom. So flashing that on something else than 2.3.6 will never work. Get into clockworkmod recovery wipe wverything from the mounts and storage menu, and then flash this file : http://android.clients.google.com/pa...o/ZD3PyN0t.zip and THEN this : http://android.clients.google.com/pa...o/hR7QFEtn.zip
and other steps I could try to work around, none of them seem to work.
Am I missing anything?
Thanks!
Use the full factory rom images (sojuaxxxx) from Google.
https://developers.google.com/android/nexus/images#sojua
Follow the instruction on that page (scroll up). If using Windows, use 7zip (or similar util) to expand the .tgz file, open content of "flashall.sh" and execute the commands one at a time.
Code:
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-jro03e.zip
The last command will wipe all data and install new 4.1.1 rom.
Edit: install CYGWIN to have linux-like commands (works with tar, adb, fastboot) in windows.
Do you have a backup (preferrably CWM backup) that you have prior to trying to get JB working? If so keep that handy, and preferrably store it on the PC. Titanium backup can ease migrating apps after a wipe and is highly recommended, so do one of these too if you havn't already.
After you make sure you have a solid backup with the information that you want/need on the phone, i would just start fresh. The best way to do this is to do a factory image flash (note: you want sojua if you have the 850MHz variant which is from AT&T). Flashing these will wipe all user data and the /system partition, the sdcard won't be touched. Basically you download it, extract it, then hook up your phone in fastboot mode and do the commands as written in the text file (or run it as a script if you know how). I've described it in more detail elsewhere as have others, doing a search should give results pretty quickly
This will become a factory install of android as given by google, in your chosen version. I'd go straight ot JB and then you can see how much you like it. CWM backup data can be extracted if you lost some crucial information in the flashing and all your apps and their data can be easily restored with titanium backup.
morning update
_android_ said:
Use the full factory rom images (sojuaxxxx) from Google.
Follow the instruction on that page (scroll up). If using Windows, use 7zip (or similar util) to expand the .tgz file, open content of "flashall.sh" and execute the commands one at a time.
Code:
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-jro03e.zip
The last command will wipe all data and install new 4.1.1 rom.
Click to expand...
Click to collapse
running linux, no cygwin needed
did this again this morning..and i'm stuck on the google boot screen with the unlocked padlock on the bottom.
how long should this run (20 minutes now)
I have tried the roms from that page, the 2.3.6 is the only rom that I was able to get working..
lost_man said:
running linux, no cygwin needed
did this again this morning..and i'm stuck on the google boot screen with the unlocked padlock on the bottom.
how long should this run (20 minutes now)
I have tried the roms from that page, the 2.3.6 is the only rom that I was able to get working..
Click to expand...
Click to collapse
Make sure you use the sojua versions.
Do you mean you finish all the steps and upon reboot, it's stuck on Google boot screen?
What do you mean by you can only get 2.3.6 working? It went past Google boot screen?
** ran 'flash-all.sh" see if that changes anything, nothing like a script to rule out human error.***
**** that was a mistake...now phone is not turning on, the screen is dead...when i plug in USB chord, nothing is detected no state change on the phone. When I press buttons no state change nothing changes on the screen. I actually think my phone is a true brick, not a software glitch that is fixable....any suggestions now? ****
lost_man said:
** ran 'flash-all.sh" see if that changes anything, nothing like a script to rule out human error.***
**** that was a mistake...now phone is not turning on, the screen is dead...when i plug in USB chord, nothing is detected no state change on the phone. When I press buttons no state change nothing changes on the screen. I actually think my phone is a true brick, not a software glitch that is fixable....any suggestions now? ****
Click to expand...
Click to collapse
Some (quite a few) Nexus S seemed to be vulnerable to Jelly Bean/CM10 update in that the mainboard is toast. I think the only option is to send back for warranty repair. There are some threads on rigging some kind of adapter cable but that will definitely void your warranty (physical mod).
Doesn't sound good, there have been instances where the flash storage has given up and ends up needing a new SoC (the whole mainboard) and similar issues. Some more information would be good to diagnose this better though.
-Take the battery out for 5 minutes, place back in, can you get into fastboot?
-Can you flash recovery and radio? Can you enter recovery?
-After the "fastboot -w update ...." command, what messages do you see on the phone (at the bottom)?
If you can't get the phone to turn on at all after a good 5 minutes without the battery inserted, give AdamOutlers resurrector a shot. A nice phone call to samsung might be a good idea if you're still within 12 months of purchasing. Hopefully it all turns out okay.
-Take the battery out for 5 minutes, place back in, can you get into fastboot?
-Can you flash recovery and radio? Can you enter recovery?
-After the "fastboot -w update ...." command, what messages do you see on the phone (at the bottom)?
If you can't get the phone to turn on at all after a good 5 minutes without the battery inserted, give AdamOutlers resurrector a shot. A nice phone call to samsung might be a good idea if you're still within 12 months of purchasing. Hopefully it all turns out okay.
Click to expand...
Click to collapse
Did all of the above, nothing. adamoutliers does not see a device connected.
lsusb shows nothing
dmesg shows my device disconnect, after the failed boot, no reconnect.
I'm headed out for a few hours, I will leave battery out, and phone disconnected but i'm thinking it's toast. Att will send an RMA phone to me, they gave me a choice of samsung focus (I asked how a windows phone was similar to an android?) or a samsung galaxcy II skyrocket...I'll try samsung next..
Thanks for all the help!
lost_man said:
Did all of the above, nothing. adamoutliers does not see a device connected.
lsusb shows nothing
dmesg shows my device disconnect, after the failed boot, no reconnect.
I'm headed out for a few hours, I will leave battery out, and phone disconnected but i'm thinking it's toast. Att will send an RMA phone to me, they gave me a choice of samsung focus (I asked how a windows phone was similar to an android?) or a samsung galaxcy II skyrocket...I'll try samsung next..
Thanks for all the help!
Click to expand...
Click to collapse
How do i close this thread? It's done, the phone is dead...rma...
I used motochop and got the phone rooted successfully but then my inexperience got the best of me when I tried to use safestrap to flash a 4.3 ROM. Looking back, I realize this was a terrible idea. I am now stuck at fastboot. This is the screen I get
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-05-25 01:04:26)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
I've scoured just about every thread in every forum I can find by searching, unless I'm missing something. I've tried flashing recovery and 4.1.2 using Razr HD Utility and I keep getting stuck right back here. I've tried pwr+volup, pwr+voldwn, and all 3. I've tried so many things, I'm honestly losing track of what I've done. Most threads end in something that requires USB Debugging but I can't even get into android. I'm just stuck at fastboot. I apologize in advance for possibly needing my hand held. I've rooted devices before, but I've never tried any motorolas so I'm not used to having things not go smoothly.
How can I get out of fastboot so I can use my phone again?!
same problem
zsarazan said:
I used motochop and got the phone rooted successfully but then my inexperience got the best of me when I tried to use safestrap to flash a 4.3 ROM. Looking back, I realize this was a terrible idea. I am now stuck at fastboot. This is the screen I get
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-05-25 01:04:26)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
I've scoured just about every thread in every forum I can find by searching, unless I'm missing something. I've tried flashing recovery and 4.1.2 using Razr HD Utility and I keep getting stuck right back here. I've tried pwr+volup, pwr+voldwn, and all 3. I've tried so many things, I'm honestly losing track of what I've done. Most threads end in something that requires USB Debugging but I can't even get into android. I'm just stuck at fastboot. I apologize in advance for possibly needing my hand held. I've rooted devices before, but I've never tried any motorolas so I'm not used to having things not go smoothly.
How can I get out of fastboot so I can use my phone again?!
Click to expand...
Click to collapse
I am having the same problem but i didn't root phone, just tried to flash stock rom after root failed, and says battery ok. Otherwise i've been bricked
zsarazan said:
I used motochop and got the phone rooted successfully but then my inexperience got the best of me when I tried to use safestrap to flash a 4.3 ROM. Looking back, I realize this was a terrible idea. I am now stuck at fastboot. This is the screen I get
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-05-25 01:04:26)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
I've scoured just about every thread in every forum I can find by searching, unless I'm missing something. I've tried flashing recovery and 4.1.2 using Razr HD Utility and I keep getting stuck right back here. I've tried pwr+volup, pwr+voldwn, and all 3. I've tried so many things, I'm honestly losing track of what I've done. Most threads end in something that requires USB Debugging but I can't even get into android. I'm just stuck at fastboot. I apologize in advance for possibly needing my hand held. I've rooted devices before, but I've never tried any motorolas so I'm not used to having things not go smoothly.
How can I get out of fastboot so I can use my phone again?!
Click to expand...
Click to collapse
Did you figure out the solution? Pretty simple... can just hold vol down and power for 10+ seconds and release
STuGGG said:
I am having the same problem but i didn't root phone, just tried to flash stock rom after root failed, and says battery ok. Otherwise i've been bricked
Click to expand...
Click to collapse
sooo... with the phone plugged in ... i repeat plugged in .. hold both volumes and power buttons at the same time until you get the boot menu.. then select either recovery or bp tools.. the tools option will let it charge at least.. recovery will get you going to where you really need to flash a rom or wipe data/cache so you can fix the bootloop hopfully .. good luck
i am in this exact same situation and have tried using rsd lite to flash the stock boot but the xml file has the "get-var" line in it and if i edit out then it says im in the wrong format...im a flash tool operator for a local shop here and i work on everyones phones in this area and now i have ppl messagin me thru email because my OWN PERSONAL phone is bricked haha this is not a good thing for me im sure i lose business because im missing something minor im sure
Topic Starter message have a Battery Low message
It may lock a firmware uploading process ))
hi I'm gaurang patel from Surat india, and I'm face this same pro b but Im findione
zsarazan said:
I used motochop and got the phone rooted successfully but then my inexperience got the best of me when I tried to use safestrap to flash a 4.3 ROM. Looking back, I realize this was a terrible idea. I am now stuck at fastboot. This is the screen I get
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-05-25 01:04:26)
etMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
I've scoured just about every thread in every forum I can find by searching, unless I'm missing something. I've tried flashing recovery and 4.1.2 using Razr HD Utility and I keep getting stuck right back here. I've tried pwr+volup, pwr+voldwn, and all 3. I've tried so many things, I'm honestly losing track of what I've done. Most threads end in something that requires USB Debugging but I can't even get into android. I'm just stuck at fastboot. I apologize in advance for possibly needing my hand held. I've rooted devices before, but I've never tried any motorolas so I'm not used to having things not go smoothly.
How can I get out of fastboot so I can use my phone again?!
Click to expand...
Click to collapse
Hi I'm gaurang patel from Surat in india,
And I face same prob than I'm trying to finding master of it after 4 month Im findout that man and now my droid RAZR start good
But in that case in my RAZR when I power on it it will going in fastbootmenu
But than run boot menu and normal restart
So if u HV prob than reply me on my gmail account
AP Fastboot, locked bootloader, Flash Failure
Hi all,
I am experiencing similar problem.
I have a Droid Razr Maxx HD from Verizon.
When i power on normally by pressing the power button, phone comes up into the AP Fastboot Flash Mode
Device is LOCKED. Status Code: 0
Batter OK
...
Fastboot Reason: Flash Failure
I can start the phone by powering up into the boot menu, then selecting Normal Powerup.
Phone power's up just fine after that.
Anybody know how to fix this problem?
Some info on my system:
System Version: 182.46.15.Verizon.en.US
Model: DROID RAZR MAXX HD
Android Version: 4.4.2
Baseband Verson: VANQUISH_bp_100731.020.64.21p
Kernel Version: 3.4.42-gdb361ac
Build Number: KDA20.62-15
If i could get a dump of firmware same version and try to flash, would that fix the problem?
Anybody have that?
I am noob to this site and hope I am in the right place, please excuse if not.
kjob said:
Hi all,
I am experiencing similar problem.
I have a Droid Razr Maxx HD from Verizon.
When i power on normally by pressing the power button, phone comes up into the AP Fastboot Flash Mode
Device is LOCKED. Status Code: 0
Batter OK
...
Fastboot Reason: Flash Failure
I can start the phone by powering up into the boot menu, then selecting Normal Powerup.
Phone power's up just fine after that.
Anybody know how to fix this problem?
Some info on my system:
System Version: 182.46.15.Verizon.en.US
Model: DROID RAZR MAXX HD
Android Version: 4.4.2
Baseband Verson: VANQUISH_bp_100731.020.64.21p
Kernel Version: 3.4.42-gdb361ac
Build Number: KDA20.62-15
If i could get a dump of firmware same version and try to flash, would that fix the problem?
Anybody have that?
I am noob to this site and hope I am in the right place, please excuse if not.
Click to expand...
Click to collapse
flash anything with fastboot and it will go away. grab your firmware from sbf droid devs if need be and just flash one part (or all if you want).
bweN diorD said:
flash anything with fastboot and it will go away. grab your firmware from sbf droid devs if need be and just flash one part (or all if you want).
Click to expand...
Click to collapse
Thanks for the reply.
The problem i am having is that my phone is not rooted, so I can't just flash any prior version rom onto it. I have not been able to find the matching firmware version to reflash exactly the same version (182.46.15...) i have back onto my phone. Would you know where I could find the matching ROM? Someone had suggested getting a dump of the ROMS from an existing phone. Is that possible?
kjob said:
Thanks for the reply.
The problem i am having is that my phone is not rooted, so I can't just flash any prior version rom onto it. I have not been able to find the matching firmware version to reflash exactly the same version (182.46.15...) i have back onto my phone. Would you know where I could find the matching ROM? Someone had suggested getting a dump of the ROMS from an existing phone. Is that possible?
Click to expand...
Click to collapse
i didnt realize the sbf want out yet, just looked, its not, sorry.
oops, just looked some more and remembered @SamuriHL posted it here.
just grab one of the img files out of the sbf and flash it.
We're lucky it's back at all. It was down for a few days. Hasn't been updated in quite a while which is depressing cause there's an FXZ I'd like to get my hands on.
To get out of the fastboot screen after a failed flashing attempt (several actually) i only had to use fastboot app (that came with motopocalypse) on my computer and write in console "fastboot continue", then the phone rebooted and started normally.
I still had the locked bootloader then.
gaurangpatel39 said:
Hi I'm gaurang patel from Surat in india,
And I face same prob than I'm trying to finding master of it after 4 month Im findout that man and now my droid RAZR start good
But in that case in my RAZR when I power on it it will going in fastbootmenu
But than run boot menu and normal restart
So if u HV prob than reply me on my gmail account
Click to expand...
Click to collapse
I was looking for the solution for my phone, but after reading this post in english I broke my phone. I didn't understand a single word and he want us to contact him for solution.
Motorola droid razr hd model xt 926
how i fix this problem plz help any body
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-05-25 01:04:26)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
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.
I experienced the exact same problem stated here (sorry can't link due to being a newb): forums.androidcentral.com/google-pixel-2-pixel-2-xl/872399-pixel-2-xl-stuck-boot-screen.html
I had maxed out the storage capacity to my device, the phone started acting funky and then it forced a reboot on its own. During the reboot, it got stuck at the 'G' logo with white background and it never got past it.
I tried to apply a Rescue OTA of my Pixel 2 following guide: drive.google.com/file/d/0Bz6x7k-VkpUJMlZ1aEliVnhMOHM/view (my build # OPM1.171019.019) but I still get stuck at the Google 'G' logo with white background on the reboot after the adb sideload step. I am completely lost on what to do next. I am new to Android and my Google skills are being tested so I appreciate any guidance.
I assume you have everything important backed up. (If you don't, you will after this.)
(As for a computer not booting because there was too much on it, ask anyone familiar with the AS/400. You can't IPL [boot] if there's too much running when you shut down.)
Try https://developers.google.com/android/images. Download 019 if you want to stay on the February update or 021 if you want to end up updated to March. Unnzip the file to some handy folder on the PC. Open the flash-all.bat file (in a text editor), go to the last "fastboot" line (it's line 23 if your editor gives you line numbers) and remove the "-w " part (remove the dash, the w and either the leading or the trailing space). Save the file. Drop to a command prompt. Boot the phone to recovery. Connect it to the PC. Run the flash-all file. It should restore the phone.
If that fails, put back the -w (fastboot -w update image-walleye-opm1.171019.019.zip 0r fastboot -w update image-walleye-opm1.171019.021.zip), reboot to fastboot again and try. (This will wipe all your stuff, which is why everything important should always be backed up. That, and a truck driving over the phone you just dropped.)
If the full flash fails, contact Google. My first one was in even worse shape - the only things I could do from fastboot were get the barcodes, power off or restart fastboot. They stand behind their phones. They replaced mine. (You can send yours back and wait for the new one or get the new one and use the same carton to send the old one back, which is what I chose [if the postal service messes up - and I've seen it happen - it could be a while before getting a new phone]. They email you verifying the conversation and there are 2 attachments - an RMA [Return Material Authorization] that you include in the box and a shipping label. Cover the entire shipping label with tape, just in case it rains on the box. (It's USPS if you're in the US, so just stick it in your mailbox.)
And back up anything you don't want to lose from now on.
Hello,
I have the exact same problem. Thing is, my Pixel ( first edition ) is not recognized by any device ( Mac/Windows ) when I plug it in. So I can't adb / fast boot it at all. Any suggestions? Thanks
DagiDashi said:
Hello,
I have the exact same problem. Thing is, my Pixel ( first edition ) is not recognized by any device ( Mac/Windows ) when I plug it in. So I can't adb / fast boot it at all. Any suggestions? Thanks
Click to expand...
Click to collapse
Do you have the proper drivers installed? In usb options, have you selected file transfer, as it defaults to charging when connected? Android debugging ticked? As long as all of these are "yes", you should be good as far as ADB.
For fastboot, hold power+volume down to get into bootloader mode. Connect your phone and type 'fastboot devices'. If you see the s/n of your phone, you're good to go.
Any help one this topic? I am having the same issue and there is no BAT file for newer builds, I am, trying to install anything past August 19th 2019 because that is the current version the pixel is stuck on
*hangs head in shame*
Ok, I'm stumped and I need help.
Last time I rooted a phone, it was our old HTC Thunderbolts... Things have changed significantly since then, or so it would appear.
Trying to fix my wife's phone after a Verizon OTA update seems to have jumped her phone from Android 10 to 11, and in the process nerfed the hotspot (which we need, as we're rural with no landline broadband available)
I'm working on a Moto G Power (sofia XT2041-4), bought late last year off the shelf from Best Buy.
Home PC is a Windows 10 box. I do not have a linux environment available to me.
I am \ was trying to put LinageOS on it, but honestly don't care what OS it is as long as we can turn the hotspot on ourselves, regardless of what Verizon wants. Over a decade ago, I rooted our phones with ICS image, so I have some outdated experience here. CalyxOS looks nice but I don't think it'll work on Moto G Power.
So, here's where I'm at in the last 48 hours.
I have gone in and gotten the unlock key from motorola, and successfully undone the OEM Lock. (I know this is the case because it tells me I'm an idiot and I should lock it, every time it boots up now). This also managed to wipe the phone, which, oops, read to the end of the paragraph BEFORE unlocking and deleting pictures of the grandkids which came in since the last backup.
Somehow last night, I managed to get it to be a brick, but used LMSA to unbrick it, but that version is still the OTA updated Android 11, so same problem with the hotspot.
I have installed the Android SDK, newest motorola drivers, and also the standalone 'Minimal ADB and Fastboot' on my PC
I've managed to get TWRP installed in the recovery portion of the phone. (note: may have been wiped now, but I can get it back on I believe)
Following this video, I managed to bring TWRP up, wiped the device, then copied the Lineage OS image to the microSD card, as well as Open GApps. The only thing I couldn't get to work, other than, you know, the new OS, is I didn't see a place to enable advanced boot options, so I have to get back to the bootloader via Volume Down and Power from a full shutdown state.
When I try to install the LinageOS (17.1), it looks like it's installing, goes through steps 1 and 2, then a slew of error messages in the log.
I've got the 4 image files I pulled out of one of the LineageOS zip files (Boot, Product, System, VBMeta) in the 'Minimal ADB and Fastboot' directory.
I can run 'fastboot flash boot boot.img' from the 'Minimal ADB and Fastboot' directory and it succeeds.
When I try to run Product, System or VBMeta in the same way (cmdline = fastboot flash product product.img), all of them fail the Preflash Validation and it comes back with 'FAILED (remote failure)'
During this process, somehow I bricked my wife's phone AGAIN, but just got it reset with LMSA for the second time. So, I may have wiped out everything I've done previously on the phone, which may or may not be a good thing. But, I believe everything I've done up to this point is repeatable (which is somewhat why I wrote all of the above details out)
Edit: Progress is Made! - Ok, now that I've got FASTBOOTD figured out, I was able to flash the Boot, Product, System and VBMeta into active partition A. But when I use the command 'flashboot reboot' it just keeps coming back to the fastboot flashload screen with the green android with it's access panel open. I tried to get back into TWRP via entering 'Recovery Mode' at the loader, but apparently it got wiped. I'm guessing I should flash it back into the recovery slot ("fastboot flash recovery twrp-3.4.0-0-sofia-test9") and then maybe try to recover from Partition A via TWRP?
Things I'm not sure about
First, I'm pretty sure I'm not in FastbootD. I don't see a big red FASTBOOTD at the top, and according to this thread, means I'm not in it.
Update: Ok, I realized I didn't have the 'platform tools', which I have now downloaded, and once I was back in fastboot, I was able to run 'Flashboot reboot flashboot' and now I know I'm in FlashbootD. Not sure what I'm supposed to do in here at this point, but hey, I've now got the correct interface.
I think FASTBOOTD should be something I'm interacting with on the Moto G Power, but for the life of me, I can't figure out how to get to it.
Update on this, see above.
I feel like I've got to be CLOSE to getting this thing working, but damned if I can seem to cross the finish line.
Help?
Further Edit: So, I tried another OS, ResurrectionOS, just to see if it was an issue with the image.
Started with another reset with LMSA (I love that tool... It zeroes out all the stupid things I'm doing on the Moto G Power during this process)
Rebooted into FastBootD mode (with the nice red at the top)
Flashed all four of the images. No errors noted during the process
Wiped the Data
Rebooted... And right back to the bootloader. Cannot seem to get out of the boot loader to get the new OS to initialize.
Again, Help?
Did you ever solve this riddle?