Related
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 was attempting to flash a factory image, and now am stuck in bootloader. I've attempted to flash the image via fastboot, but the terminal command gets stuck at waiting for device. I suspect something else is going on that is keeping me from communicating properly with the phone from the terminal commands but cant figure it out. I uninstalled and reinstalled adb/fastboot on my computer. When in terminal I am unable to find my device listed with adb devices command. This I think is the issue. How to do I get that to work?
Secure Boot is enabled Lock state is unlocked.
working with a mac
Also tried my wife's mac but nothing.
geekrd1 said:
I was attempting to flash a factory image, and now am stuck in bootloader. I've attempted to flash the image via fastboot, but the terminal command gets stuck at waiting for device. I suspect something else is going on that is keeping me from communicating properly with the phone from the terminal commands but cant figure it out. I uninstalled and reinstalled adb/fastboot on my computer. When in terminal I am unable to find my device listed with adb devices command. This I think is the issue. How to do I get that to work?
Secure Boot is enabled Lock state is unlocked.
working with a mac
Also tried my wife's mac but nothing.
Click to expand...
Click to collapse
ADB works in recovery. Fastboot works in bootloader. Macs shouldn't need any drivers as far as I remember.
Enter bootloader and type:
fastboot devices
With an s on the end
fastboot devices
rootSU said:
With an s on the end
fastboot devices
Click to expand...
Click to collapse
Yep that. Thanks man I haven't had my coffee yet.
no luck.
I get an error "could not get pipe properties"
I am at a loss since I can't get the phone to even be recognized by the computer. I just tried to reboot to recovery, and it shows me the twrp splash screen but then goes right to the opening google text with the unlocked padlock screen. Same as if I just try to boot the phone. I did have twrp flashed, but wanted a fresh start so I tried flashing in bootloader and got stuck.
geekrd1 said:
no luck.
I get an error "could not get pipe properties"
I am at a loss since I can't get the phone to even be recognized by the computer. I just tried to reboot to recovery, and it shows me the twrp splash screen but then goes right to the opening google text with the unlocked padlock screen. Same as if I just try to boot the phone. I did have twrp flashed, but wanted a fresh start so I tried flashing in bootloader and got stuck.
Click to expand...
Click to collapse
I'm gonna assume your on TWRP 2.8.2.0 It's a known issue that some are having with it. Try plugging your phone into your comp before you boot to recovery and see if it stays in revovery. Also try a different usb cable and a different port on the comp to try and solve the pipe error.
theesotericone said:
I'm gonna assume your on TWRP 2.8.2.0 It's a known issue that some are having with it. Try plugging your phone into your comp before you boot to recovery and see if it stays in revovery. Also try a different usb cable and a different port on the comp to try and solve the pipe error.
Click to expand...
Click to collapse
I've done all of those attempts. booting without being plugged in, booting while being plugged in, Trying 3 different cables.... still nothing.
geekrd1 said:
I've done all of those attempts. booting without being plugged in, booting while being plugged in, Trying 3 different cables.... still nothing.
Click to expand...
Click to collapse
Well I'm not a Mac guy but I found this that may or may not help:
http://forum.xda-developers.com/showthread.php?t=1129942
theesotericone said:
Well I'm not a Mac guy but I found this that may or may not help:
http://forum.xda-developers.com/showthread.php?t=1129942
Click to expand...
Click to collapse
Thanks, I think that helped. At least I've got the phone working now
theesotericone said:
Yep that. Thanks man I haven't had my coffee yet.
Click to expand...
Click to collapse
Hope you've had a chance to have your coffee by now. I've been sucking mine down all day while trying to fix the problem :good:
I'm stuck in Bootloader/hboot. When I try to get into recovery it reboots back into hboot. I reinstalled a RUU of the latest 4.4.4 and I have reinstalled the recovery a couple of times. I am not getting an error when installing TWRP or the RUU.
The thing that's weird is that when its rebooting the HTC white screen does NOT have the red warning writing on the bottom.
Hboot states all the usual: Software status modified, S-Off, hboot 3.19, Radio 1.09.20.0926
I'm really at a loss. Please Help :crying:
mentallo said:
I'm stuck in Bootloader/hboot. When I try to get into recovery it reboots back into hboot. I reinstalled a RUU of the latest 4.4.4 and I have reinstalled the recovery a couple of times. I am not getting an error when installing TWRP or the RUU.
The thing that's weird is that when its rebooting the HTC white screen does NOT have the red warning writing on the bottom.
Hboot states all the usual: Software status modified, S-Off, hboot 3.19, Radio 1.09.20.0926
I'm really at a loss. Please Help :crying:
Click to expand...
Click to collapse
You sure the ruu completed?
When I "fastboot oem rebootRUU" in cmd it reboots but goes back into the Bootloader and doesn't go into the Black screen/Transfer screen.
The way I did the RUU was by placing it on the sdcard. It finished installing.
BTW is it normal that it says "Software Status: Modified"? I see some Screenshots from people where it doesn say that.
(The weird thing about all this is that the phone was working fine up until it started doing this. I was running Viper with the occasional Black Screen issue that plagues the rom right now.)
mentallo said:
When I "fastboot oem rebootRUU" in cmd it reboots but goes back into the Bootloader and doesn't go into the Black screen/Transfer screen.
The way I did the RUU was by placing it on the sdcard. It finished installing.
BTW is it normal that it says "Software Status: Modified"? I see some Screenshots from people where it doesn say that.
(The weird thing about all this is that the phone was working fine up until it started doing this. I was running Viper with the occasional Black Screen issue that plagues the rom right now.)
Click to expand...
Click to collapse
Does your phone work at this point?
Nope, I am searching for the answer but I am coming up empty. I'm at a loss. Could it be that the internal memory is fried or something? But in that case I wouldn't be able to install the RUU right?
same thing happened to me yesterday. I tried for hours yesterday and today doing anything to get Some sort of response out of it, as all that it would do is boot into hboot. I could use fastboot commands but I was never able to flash anything, usually said not allowed... I was on Digital High 5.0.1 from like 12/11 or something like that. So strange. Everything was running so smoothly, then it's like it just imploded. I'd be interested if you find a solution, but I ended up ordering a replacement phone from Verizon. Looks like I'm starting over...
Apparently the internal flash memory. {emmc} just died and nothing can be flashed to it. Phone is dead. There is nothing you can do to fix it.
thanks for the update. I was holding on to my broken phone before returning it to vzw in hopes that I could restore it; I guess I'll send it back today.
lazyboy0172 said:
thanks for the update. I was holding on to my broken phone before returning it to vzw in hopes that I could restore it; I guess I'll send it back today.
Click to expand...
Click to collapse
What commands did you run on it after it broke?
dottat, you helped with it remember? lol
mentallo said:
dottat, you helped with it remember? lol
Click to expand...
Click to collapse
Across four devices and a couple carriers I start to lose my marbles some. Or perhaps lollipops
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 all
First post on here - I have inherited a working Moto G6+ and am attempting to put LineageOS on it
Only problem is, when it's supposed to be in fastboot mode, the screen backlight is on but nothing is on the screen.
>adb reboot bootloader
[wait for reboot]
>fastboot devices
^ the above shows that the phone is connected, but I have no menu and no way to interact with the phone directly on the screen.
I've used the Moto reset tool to reset the phone back to stock and behaviour is the same
Any ideas what's wrong? Is "some other chip" in charge of displaying the fastboot screen and it could be knackered perhaps? Might have to leave it stock if so, as I can't get Lineage on without a way to interact with it in fastboot/recovery I don't think, but any ideas welcome.
thanks in advnace!
Gitignoramus said:
Hello all
First post on here - I have inherited a working Moto G6+ and am attempting to put LineageOS on it
Only problem is, when it's supposed to be in fastboot mode, the screen backlight is on but nothing is on the screen.
>adb reboot bootloader
[wait for reboot]lineage OS thread
>fastboot devices
^ the above shows that the phone is connected, but I have no menu and no way to interact with the phone directly on the screen.
I've used the Moto reset tool to reset the phone back to stock and behaviour is the same
Any ideas what's wrong? Is "some other chip" in charge of displaying the fastboot screen and it could be knackered perhaps? Might have to leave it stock if so, as I can't get Lineage on without a way to interact with it in fastboot/recovery I don't think, but any ideas welcome.
thanks in advnace!
Click to expand...
Click to collapse
Go to your device's LOS thread and ask there. Also, what are you trying to achieve exactly? you usually don't need to do anything on the phone itself during the use of fastboot, you should use your PC for that. Are you saying you can't "unlock" the Bootloader or something?
Gitignoramus said:
Hello all
First post on here - I have inherited a working Moto G6+ and am attempting to put LineageOS on it
Only problem is, when it's supposed to be in fastboot mode, the screen backlight is on but nothing is on the screen.
>adb reboot bootloader
[wait for reboot]
>fastboot devices
^ the above shows that the phone is connected, but I have no menu and no way to interact with the phone directly on the screen.
I've used the Moto reset tool to reset the phone back to stock and behaviour is the same
Any ideas what's wrong? Is "some other chip" in charge of displaying the fastboot screen and it could be knackered perhaps? Might have to leave it stock if so, as I can't get Lineage on without a way to interact with it in fastboot/recovery I don't think, but any ideas welcome.
thanks in advnace!
Click to expand...
Click to collapse
When in Fastboot mode no menu is shown on a phone's screen: Fastboot is a sophisticated command line solution for dealing with a phone's bootloader.
Fastboot Commands List and Cheat Sheet with Explanation
Fastboot is a command-line tool for Android. You can execute Fastboot commands to flash and boot factory and TWRP recovery images.
technastic.com
Thanks for the responses both,
Slim K said:
Go to your device's LOS thread and ask there
Click to expand...
Click to collapse
So I found I had a problem by trying to install LOS, however I've now reset the phone to stock and confirmed the problem exists/ed without LOS being anywhere near it, so there's nothing for the LOS folks to answer ATM. I will try again with LOS though and at the point I need to interact with the phone (and can't because it's blank) I will raise it over there, but I'm 90% sure they'll say the phone is the problem not LOS. Thanks for the pointer though.
Slim K said:
Are you saying you can't "unlock" the Bootloader or something?
Click to expand...
Click to collapse
Sorry I wasn't clear. Bootloader unlocked fine. The issue is that the phone is not displaying anything when in (what I've called) fastboot mode. Maybe I mean "recovery" not "fastboot"...not entirely sure. The point is that in order to get a custom ROM on there I need to interact with the phone when in some bootloader/fastboot/recovery/pre-OS-booting state, and instead the screen is blank.
jwoegerbauer said:
When in Fastboot mode no menu is shown on a phone's screen: Fastboot is a sophisticated command line solution for dealing with a phone's bootloader.
Click to expand...
Click to collapse
So to be clear then it is perfectly normal for a phone to display nothing when connected via fastboot? This seems contrary to what I'm looking at on e.g. youtube tutorials. I can interact with the phone via command line (fastboot devices confirms it's connected) but I am sure the phone screen should not be blank e.g. something like:
(where the phone is clearly showing "fastboot flash mode", which is why I assumed the term "fastboot menu" would be clear, but if there's a better term for what that is, please let me know!)
Thanks in advance
Gitignoramus said:
So to be clear then it is perfectly normal for a phone to display nothing when connected via fastboot? This seems contrary to what I'm looking at on e.g. youtube tutorials. I can interact with the phone via command line (fastboot devices confirms it's connected) but I am sure the phone screen should not be blank e.g. something like:
(where the phone is clearly showing "fastboot flash mode", which is why I assumed the term "fastboot menu" would be clear, but if there's a better term for what that is, please let me know!)
Thanks in advance
Click to expand...
Click to collapse
The video linked to clearly demonstrates that on phone there isn't a Fastboot menu.
jwoegerbauer said:
The video linked to clearly demonstrates that on phone there isn't a Fastboot menu.
Click to expand...
Click to collapse
I don't mind what we call the display shown in the linked video, I assume @jwoegerbauer you would be happy with "fastboot flash mode" screen? My purpose of linking to the video is to demonstrate that there is *a* screen output showing when in fastboot mode.
The issue is that my phone screen displays nothing when it should (I believe) be showing the "fastboot flash mode" with-android-on-its-back- screen - whatever that is. I initially called it "fastboot menu" due to it being in fastboot mode and having a menu, but seems like the phrase "fastboot menu" is causing issues, so forget that.
Point is - phone screen empty. Shouldn't be.
This to me is a pretty good diagnostic that the phone has an issue. What might I try to diagnose even further/things to try? I've already used the Moto RSA tool on it, and that's happy...
Thanks in advance