Ok, so lets start with hello you wonderful smart people
I did something very stupid and I'm really hoping there is a solution to my foolishness.
I have an LG G3 LS990, I had previously rooted and all was well. However, I decided I would flash a custom ROM after staying up all night. And in doing so I managed to take the steps terribly wrong, and I formatted the phone completely.
Along with this, I didn't realize at that moment that the phone was being it's finicky self, and had decided not to register as connected through ADB, and only connect enough to charge...
So, I've looked at pretty much everything that has to do with unbricking an LG G3 and it seems that without USB connectivity, I am pretty much boned. But I still have hope.
Basically where I'm at now is, I can turn the phone on, but all I see is the LG loading screen and nothing else happens until the battery dies, if unplugged.
I can use the volume up + plug in micro USB to reach the firmware upgrade screen, but I am unable to make either of my computers (windows 8.1 laptop/windows 10 desktop) register that it's connected through USB.
From what I can tell, the volume down + power, release at loading screen, repress volume down + power method doesn't seem to do anything besides turn on the phone and freeze at the loading screen.
So what I'm asking, essentially, is: Is there a magic method of making my computer recognize my shell of a phone that I haven't seen? because once I can do that, the firmware upgrade stock flash option becomes viable.
Thanks in advance for any help you guys and gals can give.
xSandmanx59 said:
I have an LG G3 LS990, I had previously rooted and all was well. However, I decided I would flash a custom ROM after staying up all night. And in doing so I managed to take the steps terribly wrong, and I formatted the phone completely.
Along with this, I didn't realize at that moment that the phone was being it's finicky self, and had decided not to register as connected through ADB, and only connect enough to charge...
So, I've looked at pretty much everything that has to do with unbricking an LG G3 and it seems that without USB connectivity, I am pretty much boned. But I still have hope.
Basically where I'm at now is, I can turn the phone on, but all I see is the LG loading screen and nothing else happens until the battery dies, if unplugged.
I can use the volume up + plug in micro USB to reach the firmware upgrade screen, but I am unable to make either of my computers (windows 8.1 laptop/windows 10 desktop) register that it's connected through USB.
From what I can tell, the volume down + power, release at loading screen, repress volume down + power method doesn't seem to do anything besides turn on the phone and freeze at the loading screen.
So what I'm asking, essentially, is: Is there a magic method of making my computer recognize my shell of a phone that I haven't seen? because once I can do that, the firmware upgrade stock flash option becomes viable.
Thanks in advance for any help you guys and gals can give.
Click to expand...
Click to collapse
Hah! I did this once not too long ago on another LG device. Easy to make a mistake when you're tired.
You'll need to use the key combo to get to TWRP (should be Power + Down). TWRP is capable of transfer through ADB and it will also recognize an external SD card if you put one in it. That would eliminate a few steps with checking drivers and such. So you can then move the ROM and Gapps to the internal SD card and install from there.
epidenimus said:
Hah! I did this once not too long ago on another LG device. Easy to make a mistake when you're tired.
You'll need to use the key combo to get to TWRP (should be Power + Down). TWRP is capable of transfer through ADB and it will also recognize an external SD card if you put one in it. That would eliminate a few steps with checking drivers and such. So you can then move the ROM and Gapps to the internal SD card and install from there.
Click to expand...
Click to collapse
Thank you for the response. It's a surprisingly easy error indeed. Since I posted this, I figured out the key press you mentioned and have been trying ROM after ROM intended for my phone specifically, yet all of them will end one of 3 ways.
I get a black screen with itty bitty little text saying fastboot mode and restart.
I get everything ready and I boot up, it loads until about the wifi set up and then it will either freeze for a couple seconds and go to a black screen which requires a battery pull.
Or, I get a bsod with the options of volume up = dload and volume down = reboot.
So far I've tried candy5, CM 12.1/11, blisspop, paranoid android, cloudy, and dirty unicorn.
Not sure what I'm doing wrong with these. I use TWRP to wipe everything except external sd, install from there, reboot, and repeat.
I fixed it!! thanks to http://forum.xda-developers.com/sprint-lg-g3/development/rom-stock-zv6-base-odex-deodex-t2949087
this ROM is the only one I could find that worked. I'd still love to be able to upgrade to L but it seems like all of the 5.x roms crash during setup. Not sure what this is due to, but I have a working phone, so I'm not too upset by it.
If anyone has any info on why all the lollipop ROMs are having trouble on here I would appreciate it much.
Well it WAS fixed.... All was fine and well until there was a software update, I clicked install, it tried to reboot, and now I'm stuck in a custom recovery boot loop. I still can't connect to either of my PCs by USB and using my SD card to flash ROMs isn't doing anything now, just boots straight into TWRP every time, after full wiping and re-flashing several times now I'm really not sure how to fix this one.
Update:
Got past the bootloop from another thread on here which had a flashable fix. Now that I did that I'm actually able to use 5.x ROMs it seems. Currently working on Blisspop 3.5, once I get GAPPS to flash correctly, I think I aughta have a working Lollipop phone
Make sure you are using the correct TWRP for your device, having Bumped, as needed. Also, make sure you use the correct version of Gapps; it matters based on the version of Android your ROM is based upon.
Good luck and enjoy!
Good points. From what I can tell I have gotten everything to remain stable now. Blisspop 3.5 and the CM 12.1 GAPPs from http://wiki.cyanogenmod.org/w/Google_Apps seem to be the winning combo. The GAPPs that was listed in the Blisspop thread as the "best" seems to be the reason that my previous flash attempts were crashing upon boot. It might be one of the 86 different apps that were included in there rather than the simple 12 of the CM 12.1 GAPPs.
Either way. I've had no issues now except for the previous issue of USB debugging simply refusing to work. I have installed the latest drivers for LG devices and have tried every article's suggestions I could find on how to make my phone be recognized. I've also tried a few different root required apps that are supposed to fix issues of USB connections. None of them seem to do anything. I've also tried different cords, different plugs and different computers. But it seems like the only kind of USB recognition for my phone is when it's off it can charge. It won't charge while it's on unless I've charged it a minimum of 2% while it was off (regardless of the current battery level) and it can't be recognized as a USB device at all.
Any advice for this? Thanks in advance.
xSandmanx59 said:
Good points. From what I can tell I have gotten everything to remain stable now. Blisspop 3.5 and the CM 12.1 GAPPs from http://wiki.cyanogenmod.org/w/Google_Apps seem to be the winning combo. The GAPPs that was listed in the Blisspop thread as the "best" seems to be the reason that my previous flash attempts were crashing upon boot. It might be one of the 86 different apps that were included in there rather than the simple 12 of the CM 12.1 GAPPs.
Click to expand...
Click to collapse
It seems like the trend with ROM publishers is to not update some of those details in the threads; in the VZW variant, I know the BlissPop title still reads 5.0.x when they have been on 5.1 for some time.
I have tried a bunch of packages and have been using the Slim Gapps zero package + the DPI mod for a while now. They work great; there is even a tutrorial on how to roll your own if you like to have somewhere between 12-86.
xSandmanx59 said:
Either way. I've had no issues now except for the previous issue of USB debugging simply refusing to work. I have installed the latest drivers for LG devices and have tried every article's suggestions I could find on how to make my phone be recognized. I've also tried a few different root required apps that are supposed to fix issues of USB connections. None of them seem to do anything. I've also tried different cords, different plugs and different computers. But it seems like the only kind of USB recognition for my phone is when it's off it can charge. It won't charge while it's on unless I've charged it a minimum of 2% while it was off (regardless of the current battery level) and it can't be recognized as a USB device at all.
Any advice for this? Thanks in advance.
Click to expand...
Click to collapse
Some troubleshooting questions:
I think your OS may not supported for Android SDK. Have you ever had it recognized on these machines through ADB before? Windows takes like 5 years to get to the point where most of the drivers work.... I know it's possible in Win7 at this point, but I wouldn't expect it to work in 8.1 or Win10. Someone else who uses it may be able to help with that.
What are the driver's requirements? These are more variables associated with Windows...
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
What version of the Android SDK/Studio are you running?
Have you added the platform-tools to the SDK, as required?
Can you get ADB to recognize the device when you connected and are in TWRP?
epidenimus said:
It seems like the trend with ROM publishers is to not update some of those details in the threads; in the VZW variant, I know the BlissPop title still reads 5.0.x when they have been on 5.1 for some time.
I have tried a bunch of packages and have been using the Slim Gapps zero package + the DPI mod for a while now. They work great; there is even a tutrorial on how to roll your own if you like to have somewhere between 12-86.
Some troubleshooting questions:
I think your OS may not supported for Android SDK. Have you ever had it recognized on these machines through ADB before? Windows takes like 5 years to get to the point where most of the drivers work.... I know it's possible in Win7 at this point, but I wouldn't expect it to work in 8.1 or Win10. Someone else who uses it may be able to help with that.
What are the driver's requirements? These are more variables associated with Windows...
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
What version of the Android SDK/Studio are you running?
Have you added the platform-tools to the SDK, as required?
Can you get ADB to recognize the device when you connected and are in TWRP?
Click to expand...
Click to collapse
Thank you for the response. I have noticed that a few small things are not so frequently updated in the copy/paste updates of the ROM threads. But that's to be expected =P Anyways, to answer your questions:
What are the driver's requirements? These are more variables associated with Windows...
I'm not entirely sure about this one. I know I found the drivers on the LG website for my LS990 model and I also installed a few others including older/latest/various models to test if any of them would work. I'm running windows 8.1 currently and the ls990 seems to have a little less support as the PC suite for LG doesn't include this model in their driver list.
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
Yes, it's been a long running issue on stock, stock rooted, and blisspop all with debugging on. I was able to connect to both of my computers for a long while until one day it just stopped. It was much worse than it is now. For a few days, then it decided to charge up to about 4% when I plugged it in with no battery and then put the battery back and waited for about 3-4 hours. Then I could turn it on long enough to selectively power down and it would then charge while powered off. Over the past couple days I've been able to plug it in and reboot to get it charging again... So bothersome. As for USB debugging, not sure when it stopped exactly but I assume it was around the same time (2 months ago)
What version of the Android SDK/Studio are you running?
I have the latest version of android studio from their website.
Have you added the platform-tools to the SDK, as required?
Yes, I believe so. I'm not 100% on the SDK stuff.
Can you get ADB to recognize the device when you connected and are in TWRP?
No. There is no response from my computer at all during any of the stages of driver and twrp and studio installations. Nothing is listed in my device menu either.
Beyond this, today my phone ran out of battery while I was out and about and then has refused to charge by any method. Then I finally got it to turn on to power down etc so it would charge about 3 hours later. Once I was able to boot back up I went out to smoke and came back to my phone somehow automatically flashing a different version of blisspop that had something about user_modified in the file name which then unloaded all of my saved layouts and whatnot. After about 20 minutes of reorganizing it went black, and has since been locked in a bootloop which has survived full wipes and re-installations of the previous version of blisspop I had been using. I just downloaded the latest version for ls990 once more, and I'll report back with whether or not that fixed the issue at hand.
Related
Hey guys,
I tried getting some help for this over at the Nook Color threads because it all started *after* i rooted my NC, but no one's been able to explain to me what Ive done wrong or whats happened...
So here's the sitch.
o I have ADB installed, but it only activates in device manager when the nook is plugged in, not the G2
o When the NC get usb'd to the PC, it fully registers and gives me access to the SD card on it
o .... where as the G2 just sits there and says "yay im getting power!"
o ,,,, BUT if i plug it into a HUB rather than directly into a usb port on the mobo or front, the PC (win7 x64 ult) seems to see it but doesnt know how to properly assign a driver to it and gives it UNKNOWN
o also i checked the usb-adb ini file, and it lists all my other devices in the hardware cues BUT the G2, which means it hasnt properly registered since then or never had a proper profile to begin with in the PC. It even has my older mt3G listed which I havent plugged in since all this started.
Ive tried multiple driver types, but literately, NOTHING has worked. Its like the G2 isnt even properly registering in the computer when connected. I tried a factory reset, but still no luck. Is there anything beyond a soft fact reset for an unrooted phone? I mean, i need COLD AS STONE back to day 1 reset.
Please help, I really want to root this :'<
and no, the only way now to access my sd card is to turn the thing off and use a reader. Like i said, it literately is NOT seeing it :<
Wrong section. Ask in the Q&A, not the DEV section.
Try installing HTC Sync, even though it doesnt work with the G2 because its sense based, it will install the proper drivers for you. This worked for me.
Heres the link:
http://www.htc.com/www/SupportViewNews.aspx?dl_id=1058&news_id=804
Another method would be install pdanet on you phone fron the Market, then install pdanet for your computer from here and it should install the drivers when you plug your phone in with pdanet app running:
http://www.junefabrics.com/android/
I tried the Sense link, but I couldnt find the download option for it.... anyways, heres a more precise description of the issue
When I go and install PDA Net, it loads up the drivers, but the computer literately is not even registering that a DEVICE has been plugged in via USB. I dont even get the USB connect prompt on the phone!
That's what Im saying, something is up. I need to take the cable with me and try this on another computer now that I think about it to rule out that something isnt damaged on the phone...
What ROM are you using? Gingerbread ROM's act like the (for now), at least from what I understand. I tried CM7 and sure enough - it acted just like what you're describing.
KCRic said:
What ROM are you using? Gingerbread ROM's act like the (for now), at least from what I understand. I tried CM7 and sure enough - it acted just like what you're describing.
Click to expand...
Click to collapse
But thats the whole thing, im not using a ROM, its just the stock OS build. if i was using a ROM, id have tried removing it and reloading it, but this is on a phone that isnt even rooted yet... actually... should I try going temp root again and see if that fixes anything?
Whats the best way to do that now since I keep reading Vision got pulled away because it was damaging phones or something?
Okay, so i tried plugging it into a diff computer.... same result... so whatever it is, its the phone.
Any ideas XDA pplz?
Has it seen the g2 before? if so, get usbdeview, find the drivers in there that would be used for the g2, delete those. Snag PDANet and download that, plug the phone back in and see what ya get. You will get the pop ups again about the new software being loaded since it will have to find and reload drivers for the phone and PDANet will have the drivers you need.
K41N2358 said:
Okay, so i tried plugging it into a diff computer.... same result... so whatever it is, its the phone.
Any ideas XDA pplz?
Click to expand...
Click to collapse
Like the guy above me said, DL or re-DL the drivers (though none should be needed if you're using it as a storage drive, the comp sees it as a usb drive). Is it charging your phone when you plug it in? It's rare, but the USB cable may be bad.
The only other thing I can think of is that something went wrong and the phone isn't releasing the mount to the sdcard, in which case you should try rooting and using a different ROM or a stock rom and it should help.
Well thats the whole thing, the computer doesnt even see the USB part of it. Thats been my whole issue. The computer doesnt see the phone or the usb drive part. It straight does not see the phone at *all*! Doesnt even show up in Dev Manager, but yet it gets power. I even went and got a new micro USB cable, fresh, and still nothing.
im getting to 86 the os and reload Win7, im like super uber pissed over all this because i cant figure it out. I dont even know whats wrong >_<!
Just for kicks (because I had this exact thing happen to another phone of mine - the slide) you're rooted, which means you have clockwork right?
Reboot into recovery and go to the 'mounts' part and select 'mount usb'. Do that with it plugged into your computer and let me know if the phone shows up then. That's the only way I could put it in mass storage mode. I flashed something other than cyanogen's rom and BAM, it worked like it was supposed to (Linux did mount cyanogen though - weird).
If you want to go back to 0 day with your G2, search 'PC10img' and download it. DO NOT FLASH IT YET, you could really screw up your phone since you have s-off. Go to the wiki and scroll to the bottom, it tells you how to get s-on. Once you can verify that you have s-on, proceed to flashing the pc10img.
Wiki
Okay, so, Im way better now. Apparently I managed to get s-off and root ability via
http://forum.xda-developers.com/showthread.php?t=837315
when i reloaded and got rooting ability, somehow, I now have a detectable sd card again.
I dont know how, I dont know why, I just know that Im going to throw CM6.1.1 onto this thing and be rocking it hard
Thanks again for all your help guys, it was awesome to know XDA really helps out its followers
EDIT:
Okay... so now Im mixed. I have a rooted phone, with CM6.1.1, but still doesnt properly recognize when plugged into the PC.
oh well, I already called TMobile and their sending me a new phone under warranty. Its gotta just be a busted port in some way for detection. I dunno. >_<
But still, thanks a lot guys. Means a lot
Alright ... after 2.x years I yet again pickup this beauty.
Unfortunately the one I got is nowhere near the one I had from my old employer, this one was $80 and has seen much better days, but I figured I'd get back into looking what Android had to offer, for me.
So I take a look and I realize I HATE KitKat ... horrible standard OS and if LG keeps doing this to the Android OS it would suck!
Ok ... so I do the following:
Root using SuperSU ... sweet.
I download to the PC FreeGee - realizing no longer needed after 2hrs last night but I'm tired and I say screw it.
So I download FreeGee directly on the LG ... Bootloader unlocked. Sweet.
I copy the zip file for the CM 12.1 for Android 5.1, I think it's for 5.1 but the subsequent events may tell I'm wrong.
(File: cm-12.1-20150521-UNOFFICIAL-geeb)
Now, device installs the OS and reboots successfully. Sweet jesus this looks beautiful! I navigate around the menu and I think all is good and a few icons I have no clue what is going on with the one in the tray on the bottom right.
So I launch it and it goes through first page of info and I realize it's Google's Camera which saves everything in the cloud ... NOT a fan of that, and there is a check box to disable location information I disable it.
I exit the Google Camera app and then the screen goes blank. I see 3 Red LED blinks in the notification light and 6hrs later I STILL cannot power it on!!!
1. Can't power it on!
2. Can't get Bootloader to show up (the one with the Android heart exposed)!!
EEEK.
3. Just the damn LED blinking, consistent blink!!
4. I try Volume UP/DOWN buttons, connect USB to the G, then to Win7 and nothing!
I suspect Google Camera trying to connect to Google's services which may NOT be in CM12.1 for this device. I also suspect since I installed the CM12.1 with the USB connected it tried to connect using ADP, which I feel it KEEPS doing in Win7. I have the factory drivers and the updated drivers NOTHING fully works; just the connect then immediate disconnect chime in Win7.
Files I have: (I'm using Win7 64bit)
These files I've all acquired through various threads there.
LGUnitedMobileDriver_S52MAN314AP22_ML_WHQL_Ver_3.14.1.exe
UPDATE-SuperSU-v1.94.zip (SuperSU to root)
cm-12.1-20150521-UNOFFICIAL-geeb.zip (This was installed before going dead with LED blinking Red.
LGMobileSupportTool.exe (because I do NOT have the S/N, it's in the OS which will NOT boot I cannot download the original OS from LG's servers, arrrgh!)
LG-KK-4.4.2-Intl-Cdn.zip (supposedly the original OS yet HOW the FUNK can I load this onto the LG if I cannot see anything on the screen? Hmmmkay ...
so does this mean I've got a permabrick and i'm fubar'd? IF not would anyone please led an assist, please would you?
Thank you kindly, in advance.
Supa_Fly said:
Alright ... after 2.x years I yet again pickup this beauty.
Unfortunately the one I got is nowhere near the one I had from my old employer, this one was $80 and has seen much better days, but I figured I'd get back into looking what Android had to offer, for me.
So I take a look and I realize I HATE KitKat ... horrible standard OS and if LG keeps doing this to the Android OS it would suck!
Ok ... so I do the following:
Root using SuperSU ... sweet.
I download to the PC FreeGee - realizing no longer needed after 2hrs last night but I'm tired and I say screw it.
So I download FreeGee directly on the LG ... Bootloader unlocked. Sweet.
I copy the zip file for the CM 12.1 for Android 5.1, I think it's for 5.1 but the subsequent events may tell I'm wrong.
(File: cm-12.1-20150521-UNOFFICIAL-geeb)
Now, device installs the OS and reboots successfully. Sweet jesus this looks beautiful! I navigate around the menu and I think all is good and a few icons I have no clue what is going on with the one in the tray on the bottom right.
So I launch it and it goes through first page of info and I realize it's Google's Camera which saves everything in the cloud ... NOT a fan of that, and there is a check box to disable location information I disable it.
I exit the Google Camera app and then the screen goes blank. I see 3 Red LED blinks in the notification light and 6hrs later I STILL cannot power it on!!!
1. Can't power it on!
2. Can't get Bootloader to show up (the one with the Android heart exposed)!!
EEEK.
3. Just the damn LED blinking, consistent blink!!
4. I try Volume UP/DOWN buttons, connect USB to the G, then to Win7 and nothing!
I suspect Google Camera trying to connect to Google's services which may NOT be in CM12.1 for this device. I also suspect since I installed the CM12.1 with the USB connected it tried to connect using ADP, which I feel it KEEPS doing in Win7. I have the factory drivers and the updated drivers NOTHING fully works; just the connect then immediate disconnect chime in Win7.
Files I have: (I'm using Win7 64bit)
These files I've all acquired through various threads there.
LGUnitedMobileDriver_S52MAN314AP22_ML_WHQL_Ver_3.14.1.exe
UPDATE-SuperSU-v1.94.zip (SuperSU to root)
cm-12.1-20150521-UNOFFICIAL-geeb.zip (This was installed before going dead with LED blinking Red.
LGMobileSupportTool.exe (because I do NOT have the S/N, it's in the OS which will NOT boot I cannot download the original OS from LG's servers, arrrgh!)
LG-KK-4.4.2-Intl-Cdn.zip (supposedly the original OS yet HOW the FUNK can I load this onto the LG if I cannot see anything on the screen? Hmmmkay ...
so does this mean I've got a permabrick and i'm fubar'd? IF not would anyone please led an assist, please would you?
Thank you kindly, in advance.
Click to expand...
Click to collapse
Try these threads, it might help you.
http://forum.xda-developers.com/showthread.php?t=2498102
http://forum.xda-developers.com/showthread.php?t=2797190
I bought two brand new Samsung adaptive fast chargers (USB brick & cable) the other day and my phone will not fast charge and my PC will not recognize it. Every time I connect my note 4 to my pc the error message says "USB device not recognized." I've tried everything. I stalled kies, uninstalled then reinstalled my drivers, even took my phone to a repair shop to put in a new charging port.... I have 2 laptops. One is running windows 10 and the other is running windows 7 and they both give me the same error message. I'm pulling my F*****in hair out!!!!!!!!!
Someone please help!!
Akashp2011 said:
Someone please help!!
Click to expand...
Click to collapse
You didn't give much in the way of background but I'll do what I can. I'm on Jasmine ROM, which is pretty much stock Marshmallow.
When I plug in my fast charger, nothing I can see says it's fast charging. There's a box in settings>battery to check for fast charging.
As far as the connection to your computer goes: when I plug in and I pull down on the notification bar, there's a tab that for me says "USB Charging." If I touch on that tab, it'll give a list of options, one of which is "File Transfer." Click on that radio button. If you like, you can go into settings>developer options and touch "USB Configuration." Click on the "MTP" radio button and file transfer will be the default mode when you plug in.
If this seems obvious, I'm sorry. I don't know what level of experience you have with your phone or your phone's configuration. It's not a common problem which is why it took some time to get to answer your question.
douger1957 said:
You didn't give much in the way of background but I'll do what I can. I'm on Jasmine ROM, which is pretty much stock Marshmallow.
When I plug in my fast charger, nothing I can see says it's fast charging. There's a box in settings>battery to check for fast charging.
As far as the connection to your computer goes: when I plug in and I pull down on the notification bar, there's a tab that for me says "USB Charging." If I touch on that tab, it'll give a list of options, one of which is "File Transfer." Click on that radio button. If you like, you can go into settings>developer options and touch "USB Configuration." Click on the "MTP" radio button and file transfer will be the default mode when you plug in.
If this seems obvious, I'm sorry. I don't know what level of experience you have with your phone or your phone's configuration. It's not a common problem which is why it took some time to get to answer your question.
Click to expand...
Click to collapse
I've tried everything I can think of including the tips you provided. I'm on PaulPizz's rom and I didnt have these problems before. Every time I connected my charger, it gave me a notification that it was fast charging, now it doesnt. Now when I connect my device to my pc, my Note 4 doesnt give me any options. Not even MTP or PTP. It's as if i dont even have it connected to my computer.
Akashp2011 said:
I've tried everything I can think of including the tips you provided. I'm on PaulPizz's rom and I didnt have these problems before. Every time I connected my charger, it gave me a notification that it was fast charging, now it doesnt. Now when I connect my device to my pc, my Note 4 doesnt give me any options. Not even MTP or PTP. It's as if i dont even have it connected to my computer.
Click to expand...
Click to collapse
You may have gotten a bad flash. I don't have experience with PaulPizz's ROM but since I believe it's based on the OEM Marshmallow... you are on that version of the ROM, correct?... I'd suggest you try flashing again. And if not PaulPizz, it's all working good for me on Jasmine.
And if you are using the Marshmallow version of PaulPizz, did you unlock the Marshmallow bootloader? You need to be careful. It's quite confusing because Marshmallow ROMs don't necessarily have to use Marshmallow bootloaders. But if the ROM uses a Marshmallow base, your bootloader must be Marshmallow as well.
douger1957 said:
You may have gotten a bad flash. I don't have experience with PaulPizz's ROM but since I believe it's based on the OEM Marshmallow... you are on that version of the ROM, correct?... I'd suggest you try flashing again. And if not PaulPizz, it's all working good for me on Jasmine.
And if you are using the Marshmallow version of PaulPizz, did you unlock the Marshmallow bootloader? You need to be careful. It's quite confusing because Marshmallow ROMs don't necessarily have to use Marshmallow bootloaders. But if the ROM uses a Marshmallow base, your bootloader must be Marshmallow as well.
Click to expand...
Click to collapse
I'm on his latest version of 5.1.1. It did this before I flashed his newest rom. I flashed it thinking it would fix the issue but it didnt. I put his rom on my SD card after i connected it to my computer by itself with an adapter. I did everything right. Wiped data and cache before flashing. The rom works perfectly. I'm really hoping it's not a hardware issue, but unfortunately that's a possibility. I can't upgrade to MM because I have to use Odin and I can't even use it.
Akashp2011 said:
I'm on his latest version of 5.1.1. It did this before I flashed his newest rom. I flashed it thinking it would fix the issue but it didnt. I put his rom on my SD card after i connected it to my computer by itself with an adapter. I did everything right. Wiped data and cache before flashing. The rom works perfectly. I'm really hoping it's not a hardware issue, but unfortunately that's a possibility. I can't upgrade to MM because I have to use Odin and I can't even use it.
Click to expand...
Click to collapse
Give hsbadr's Jasmine ROM a shot. I wouldn't worry about going the 4.3 route. Just flash the 4.0 and see if the problem goes away. If it doesn't, I'll have to agree that it's a hardware issue. If it does go away, then you can install 4.3 and the fixes.
Backup your current ROM first. Check off all of the boxes. Wipe the Dalvik/cache/system/data, (you didn't mention that you wiped the system) then flash the ROM. If you have anything like pictures or music on your internal storage, move them somewhere safe first. Let us know how it works out for you, and good luck.
douger1957 said:
Give hsbadr's Jasmine ROM a shot. I wouldn't worry about going the 4.3 route. Just flash the 4.0 and see if the problem goes away. If it doesn't, I'll have to agree that it's a hardware issue. If it does go away, then you can install 4.3 and the fixes.
Backup your current ROM first. Check off all of the boxes. Wipe the Dalvik/cache/system/data, (you didn't mention that you wiped the system) then flash the ROM. If you have anything like pictures or music on your internal storage, move them somewhere safe first. Let us know how it works out for you, and good luck.
Click to expand...
Click to collapse
Thanks man. I'll give that a shot. And yes I did wipe dalvik, cache, data, and system. Ill flash Jasmine Rom tonight and give you an update.
Akashp2011 said:
Thanks man. I'll give that a shot. And yes I did wipe dalvik, cache, data, and system. Ill flash Jasmine Rom tonight and give you an update.
Click to expand...
Click to collapse
Did you ever have any luck with anything? I have the same issue on my note 4, my usb port is basically useless other than slow charging. I have even replaced the port twice in efforts to fix it, tried different roms, etc. At this point I believe it is hardware, something with the motherboard.
Let me know if you have had any success with anyhting
Fast charge wont work
I too have the same problem. It quit fast charging. I ordered genuine Samsung battery and charge cable. It dont work. Its not the battery or charging device. I finally got it hooked to my pc or recognize it. Fast charge wont work. Its not the batt, charger, or port. Its either VZN software or a hardware issue. I am trying to downgrade it to 6,0 to see if it 6.1 upgrade. Kies wont let me downgrade. I really think it is a bug in Verizon 6.1 upgrade. Any help will be appreciated
My phone will fast charge on my two vehicle chargers (at 1.5 amps and 2.1 amps), but refuses to change any faster than 500 mA on two separate fast charger bricks. The same bricks work fine for fast charging other phones, so it's my phone, not the charging hardware. I'm using the same cable for all instances, which leads me to believe that something is wrong with how the phone interprets the "smart charging" signal on the bricks, or that the phone is sending the wrong charging signal.
Does anyone have the issue with bricks but not with chargers without "smart charging" capabilities?
I've had this problem on stock 5.1.1, Jasmine rom 6.0.1, and now CM13. I full wiped everything when reinstalling, so either it's hardware, or an issue propigated through many roms. I've tried a few different kernels too, just to see if that was the problem.
Akashp2011, did you flash both the rom and the kernel for Paul Pizz? I never tried that combination.
I'm changing the battery tomorrow to check that possibility.
Hey guys,
sorry if my english isn't right but I am so tired so now and so frustrated that I don't know what I could do.
The story is simple: I have a android head unit, running allwinner t3 (aka R40) with stock rom and stock recovery.
So far, there isn't any custom recovery available (I would like to create/compile CWM but CWM-Builder have some 502 Bad Gateways...) and the only way to root on 4.4.2 is with 360Root (On 6.0.1 for the newer Models only with Kingroot).
So far not bad but it takes a lot of patience sometimes and sometimes you can try over 1 week every day many hours and it still don't work!
So where do I need help? I want to add Root/SuperSU/... manually but I have many limitation.
First one is that I can only modify the system.img without any chmod and else (Maybe because I am using windows? Maybe because the Firmware has to be flashed while the Head Unit is powered off aka "Dead flash")
Secondly, ADB is not working, to be honest, the head unit act only as a receiver! It accepts any devices like Keyboard, UMTS/WCDMA Stick, USB Stick, ... but MTP fom HeadUnit or ADB, ... don't work. The only way for ADB is ADB over Wifi but I don't know whether it's good or bad. I saw that the USB is plugged into a slot which seems to be bend out, maybe they plugged it in wrong? I don't know how I can test that but I heard that connecting two devices with wrong polarity will break at least one of them!
Thirdly is, that I can't notice a difference between a rooted stock rom and a unrooted stock rom.
According to WinMerge, the rooted ROM have two new files (/etc/install-recovery.sh and /bin/su) but that's it!
If I transfer those files to my custom ROM with the same rooting app, it wont recognize them! I can try and try until I die.
And last, maybe worst, I can't just update something over. Every change outside the Android OS is mainly done by flashing the whole firmware! They changed that policy a little bit after Android 6.0.1 but this Android have the worst stability, worst GPS Modules and completely bricked Bluetooth! Also the stock recovery on 4.4.2 is useless, touch isn't working and the touch-buttons are also not working. I also tried to use a usb keyboard but also useless. Only the 6.0.1 stock recovery recognizes the touch screen and the touch-buttons but as I said, the Android 6 is terribly made...
I know what it sound like a noob and I didn't provided much information but I want to know whether someone can help me or want to help me... maybe someone say that I have to provide information xyz so yeah, feel free to ask
Best regards
Pascal
At what point did you install the ADB device drivers (kinda important) for your device, so that when you plugged it into anything, the thing could register you were plugging in the HeadUnit......
I started updating the phone to the Jan 2019 update from the Dec 2018 update (I just like having the latest updates) It rebooted into bootloader via ADB just fine. I then ran the flash all.bat without the -w so it wouldnt wipe the phone out completely. It started updating and rebooting just like normal after the bootloader and radio parts. It made it close to the end of the system update and did not reboot the phone. It went back to the bootloader which I thought was odd. Fastboot can no longer see the phone in Fastboot devices. When starting the phone it reboots back into bootloader saying load failed. It also will not boot into recovery (which I expected from the update and not getting to flash twrp back in yet) I have rebooted the phone and my computer as well. I tried my other phone to check the cable and it found it in ADB and Fastboot just fine. I do have the latest SDK installed. Any help would be greatly appreciated.
---Solution---
Chilipepprflea said:
I know this is probably too late for you guys, but maybe it will help someone else. Fastboot commands would result in "waiting on any device" and my Pixel 2 wouldn't boot out of the bootloader. I thought it was done for good based on this thread and others I've read...until I came across this Reddit https://www.reddit.com/r/GooglePixel/comments/b25nso/error_slot_unbootable_load_error/
I did what this guy did and held the power button (ended up being for a couple minutes in my case) and it vibrated and all is good again! adb recognized my phone and I was able to flash again.
Click to expand...
Click to collapse
You'll have to go back into bootloader and do a stock flash follow the steps on googles site. go back to 8.0 or whatever you were on before, make sure that boots up fine. You must not have had updated your sdk before trying to update to 9.0
I was going to just reflash everything but when I do fastboot devices its just blank as if the phone does not exist. Also the computer doesnt do its chime when I plug the USB in while its in bootloader. When the phone is off and I plug it in it shows the charging icon for a split second then boots into bootloader saying ERROR: Slot Unbootable: Load Error. If I try to do any commands in fastboot it just says "waiting for any device"
I was already on 9.0 and was just pushing the January security patch when it stopped near the end of the update. Now I can not get fastboot to even see the device.
Try removing all drivers and fastboot files on your pc. Sounds like you just flashed the wrong file. Were you rooted with magisk? or just on a stock rom. re download the full image and try and re flash. https://developers.google.com/android/images
Because of the slots (a and b) alot of people seem to have trouble flashing things. I have even messed things up as well. On the Pixel devices I havent been able to not go back into stock setups. Even if it took removing all files and starting over.
---------- Post added at 04:19 AM ---------- Previous post was at 04:18 AM ----------
I will keep checking back over here to see if you have any issues.
So I just tried what you had said. Deleted all the SDK files and uninstalled the drivers, rebooted computer and phone redownloaded everything and still can not find the phone via fastboot... magisk was installed but I was doing the full image install without the -w so it would not wipe. it was almost done with it and never actually booted into android it just stayed on the bootloader which I found strange. That is when I noticed that the phone could no longer be found via fastboot devices. I have tried different cords different ports and even a different computer and still have the same result. It did update the bootloader and radio portions of the update. I feel like if I can get fastboot to start working I can save this thing.
I got caught up with friends that came over. You have tried everything I would have tried. Which is good cause you seem to know what you are doing, but not good that it hasnt been resolved. Have you looked at this guide? https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Coolpente said:
I started updating the phone to the Jan 2019 update from the Dec 2018 update (I just like having the latest updates) It rebooted into bootloader via ADB just fine. I then ran the flash all.bat without the -w so it wouldnt wipe the phone out completely. It started updating and rebooting just like normal after the bootloader and radio parts. It made it close to the end of the system update and did not reboot the phone. It went back to the bootloader which I thought was odd. Fastboot can no longer see the phone in Fastboot devices. When starting the phone it reboots back into bootloader saying load failed. It also will not boot into recovery (which I expected from the update and not getting to flash twrp back in yet) I have rebooted the phone and my computer as well. I tried my other phone to check the cable and it found it in ADB and Fastboot just fine. I do have the latest SDK installed. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Are you *sure* it will not boot to recovery? If you're not used to the stock recovery it can fool you. Many ppl see the dead android and stop there. If you can get into the stock recovery you can try sideloading an OTA via adb (which only works in recovery). I would also be trying different computers and cables. If you cannot use fastboot -and- you have no working recovery you might be dead in the water.
OMG @Coolpente!!!! THIS....HAPPENED...TO....ME!!!!
Holy crap! I can't believe this happened to someone else! I thought it was just me and my bad luck!
I literally was doing the same thing (only difference was on my gf's pixel 2 [walleye])! And those who have seen me around this forum the last year know that I am very knowledgeable and don't make the simple and "noob" mistakes! I've literally have helped and recovered people in this/our position -- so it is doubtful there was a amateur or novice mistake made in the updating process or "stone un-turned" in the recovery process!
So here is what happened to me, particularly, and my observations on it...
- When "crap hit the fan", it was very peculiar that fastboot would identify the phone's serial number as "??????????" (when running the command "fastboot devices"). Only after rebooting and disconnecting/reconnecting the usb cable did it (fastboot) simply just stop detecting. To make sure that my computer, usb port, cable, and fastboot is working correctly and able to process properly, I would make sure the fastboot process/server was not running, then I would actually run the command "fastboot getvar all", and as it would "would for device", I would plug in the phone, nothing would happen, then plug in my phone [taimen] (not my gf's walleye), and it would detect it and display all the pertinent information and device details, I would then unplug it from my phone, run the same getvar command, and lastly replug it into the phone (broken gf's walleye) with no detection or success.
- What's also interesting and of note is that when loading straight into the bootloader (via button combination), it displays no error in the list of device details. But when booting into the recovery (note: I, like the OP, had the TWRP custom recovery already flashed and installed) and also the system and/or from a power-off state, it states in red colored font and yellow background, "ERROR: Slot Unbootable: Load Error". Even more than that is when attempting to boot into Download mode, it states a different error (but in the same font style), "ERROR: Operation Denied"!
- I also attempted to manually change the slot in attempts to address the "slot unbootable..." "...load[ing] error", but -- due to either fastboot not detecting or the device not connecting properly I imagine -- without fastboot properly detecting, the commands wouldn't work and execute properly anyway. I've even taken steps further and attempted to format and custom "re-size" partitions. But, for the aforementioned reasons (presumably), it and attempts at commands like it wouldn't likely work and execute, again as previously reasoned. Also, in attempt to tackle the "slot" aspect of the issue, I tried Deuce's script; but as Deuce's script is, simply put, based off of the flash-all.bat that ends up being an advanced batch (pun intended) of commands that manually and individually flashes the stock images/partitions to the partitions of the device -- so, in essence, uses fastboot and since fastboot can't work.... I even found and attempted to use the (hardly heard of; at least to me) tool Skipsoft Android Toolkit (which looks genuinely super dooper awesome btw...)... all for naught :crying: ...
You know, after a year with the Pixel 2 (XL), and after coming back from messing my phone up (15+ times), and actually purely bricking it once (had to get it replaced), I always thought that, as long as one could access the device via the bootloader, one would always have hope (at least in the Pixel's case). So, it's curious but agonizingly ironic being able to access the bootloader (which was not the case in my one and only instance of bricking my device and having a completely "lost cause") just for me not to be able to do anything about it and/or fastboot to not be able to properly connect and send commands to it...
But to me and Coolpente (and anyone else who this may have happened to) I ultimately can't think of anything else that can be done at this point. To re-iterate, I/we had the most up-to-date platform-tools (r28.0.1), it has been proven that the usb cord, port, computer, and drivers are all working as I was able to get the "getvar all" command to work on another pixel mere seconds before attempting the same on this (broken) device, and even attempted all tools available...
Unfortunately, @Coolpente, it does look as if our phones are irrevocably "bricked" and it's all rather doomed and attempting to get it repaired/replaced by the manufacturer ("The Big G") is the only recourse we may have :crying::crying::crying:
I wrote this (very long) post in hopes of giving as much information and details as possible in the desperate hopes that any other solutions might be brought up...
simplepinoi177 said:
OMG @Coolpente!!!! THIS....HAPPENED...TO....ME!!!!
Holy crap! I can't believe this happened to someone else! I thought it was just me and my bad luck!
-- SNIP---
I wrote this (very long) post in hopes of giving as much information and details as possible in the desperate hopes that any other solutions might be brought up...
Click to expand...
Click to collapse
I am so glad I am not the only one that his has happened to! I have rooted several phones as well as almost bricking the one that ultimately bricked... (not up to date sdk tools) You have word for word the exact same thing that is happening to me. no recovery no booting and no download mode just the bootloader which is not found by fastboot. I thought at first it may have been the usb port in the phone disconnecting somehow but when plugging it in from a completely off state it does show the charging battery screen for a split second then boots into bootloader saying it can not load that slot. I am not very fluent in the disassembly of phones like this or I would check to see if the data parts of the USB port are not connected to the board.. It kills me that the phone is not even a year old and something like this would happen.. I have since gotten a replacement phone but I am very interested in seeing if there is a way to fix it in the near future outside of sending it in.
Coolpente said:
I am so glad I am not the only one that his has happened to! I have rooted several phones as well as almost bricking the one that ultimately bricked... (not up to date sdk tools) You have word for word the exact same thing that is happening to me. no recovery no booting and no download mode just the bootloader which is not found by fastboot. I thought at first it may have been the usb port in the phone disconnecting somehow but when plugging it in from a completely off state it does show the charging battery screen for a split second then boots into bootloader saying it can not load that slot. I am not very fluent in the disassembly of phones like this or I would check to see if the data parts of the USB port are not connected to the board.. It kills me that the phone is not even a year old and something like this would happen.. I have since gotten a replacement phone but I am very interested in seeing if there is a way to fix it in the near future outside of sending it in.
Click to expand...
Click to collapse
I know it is highly unlikely, but I'm hanging in there hoping for the same thing as well...
Yeah, it's troubling that this is can be happening coming from very "seasoned" users!
I was considering the same that it feels more like a hardware issue since everything seems to work on the computer end as well as everything working on another pixel device, BUT I can't see how a failed "fastboot" command and process can effect any kind of hardware or physical connections ("data parts")?!
If anything, I believe it has to do with the sequence of events of how things crapped out... I believe that, in some random manner, the bootloader -- which gets flashed and updated first; referencing the script in the flash-all.bat -- gets replaced, but isn't installed/initialized/"placed" properly -- but curiously enough, is installed "properly" enough that it can be re-entered after turning the device off -- that most everything works BUT the all important fastboot connection/interface/detection! That's why I attempted to manually flash the bootloader image ("fastboot flash bootloader bootloader.img"), but, "head-bangingly" poetic in its irony of course, fastboot is required to accomplish this ("this" being fixing freaking "fastboot"! :crying: )
I'm terrified to update my own Pixel at this point.
Unfortunately, this seems to have only been documented in our two cases (so far)...I wonder if it's even worth creating a Google support ticket in attempts to bring it up to them in hopes that they fix whatever might be causing this -- hopefully assisting and saving others from this disaster -- and/or even pull the update until it is stable (although, like I stated, it seems not a prevalent enough issue that many either have successfully updated via this image and process or most haven't brought it up anywhere) and/or keep it from happening in the next update.
In any case, here's hoping ("pray for the best, expect the worst" kind of scenario is most likely appropriate) any kind of solution materializes, or, at the very least, can be shown as a "word of warning" and caution about the (this, specifically) update....
simplepinoi177 said:
OMG @Coolpente!!!! THIS....HAPPENED...TO....ME!!!!
Holy crap! I can't believe this happened to someone else! I thought it was just me and my bad luck!
I literally was doing the same thing (only difference was on my gf's pixel 2 [walleye])!
Click to expand...
Click to collapse
Find a new girlfriend, your problem will be easily solved.
simplepinoi177 said:
I know it is highly unlikely, but I'm hanging in there hoping for the same thing as well...
Yeah, it's troubling that this is can be happening coming from very "seasoned" users!
I was considering the same that it feels more like a hardware issue since everything seems to work on the computer end as well as everything working on another pixel device, BUT I can't see how a failed "fastboot" command and process can effect any kind of hardware or physical connections ("data parts")?!
If anything, I believe it has to do with the sequence of events of how things crapped out... I believe that, in some random manner, the bootloader -- which gets flashed and updated first; referencing the script in the flash-all.bat -- gets replaced, but isn't installed/initialized/"placed" properly -- but curiously enough, is installed "properly" enough that it can be re-entered after turning the device off -- that most everything works BUT the all important fastboot connection/interface/detection! That's why I attempted to manually flash the bootloader image ("fastboot flash bootloader bootloader.img"), but, "head-bangingly" poetic in its irony of course, fastboot is required to accomplish this ("this" being fixing freaking "fastboot"! :crying: )
I'm terrified to update my own Pixel at this point.
Unfortunately, this seems to have only been documented in our two cases (so far)...I wonder if it's even worth creating a Google support ticket in attempts to bring it up to them in hopes that they fix whatever might be causing this -- hopefully assisting and saving others from this disaster -- and/or even pull the update until it is stable (although, like I stated, it seems not a prevalent enough issue that many either have successfully updated via this image and process or most haven't brought it up anywhere) and/or keep it from happening in the next update.
In any case, here's hoping ("pray for the best, expect the worst" kind of scenario is most likely appropriate) any kind of solution materializes, or, at the very least, can be shown as a "word of warning" and caution about the (this, specifically) update....
Click to expand...
Click to collapse
I have considered going to a custom rom and avoiding the stock rom completely... Which would avoid ever needing to use fastboot to update in the future.. but its to late for one phone but not to late for the other. I havent even looked into roms since CM broke down...
Coolpente said:
I have considered going to a custom rom and avoiding the stock rom completely... Which would avoid ever needing to use fastboot to update in the future.. but its to late for one phone but not to late for the other. I havent even looked into roms since CM broke down...
Click to expand...
Click to collapse
Yeah....but, if you think of it, I've been updating by way of Full Factory images via fastboot for over a year (14 months to be exact), so the last 13 times and 13 out of 14 times it worked perfectly....so, pure statistics, I wonder if swearing off fastboot forever is truly pertinent just yet...
Well, at least the pixel 2's been out for....14 months, apparently...so there seems to be a lot of good, stable custom ROMs that have been long in development to choose from, if anything... **~shrugs~**
simplepinoi177 said:
Yeah....but, if you think of it, I've been updating by way of Full Factory images via fastboot for over a year (14 months to be exact), so the last 13 times and 13 out of 14 times it worked perfectly....so, pure statistics, I wonder if swearing off fastboot forever is truly pertinent just yet...
Well, at least the pixel 2's been out for....14 months, apparently...so there seems to be a lot of good, stable custom ROMs that have been long in development to choose from, if anything... **~shrugs~**
Click to expand...
Click to collapse
As far as statistics are concerned yea I have been updating 2 pixels by full factory images for the last year and one has survived all 12 months while the other made it through 11 of 12. but in fear of bricking another pixel device knowing this could potentially happen again... it feels as if going to custom roms would for sure be the safest method and still keep root. Of course losing root and going pure stock would be 100% the best... I love having root and dont want to lose it.
Coolpente said:
As far as statistics are concerned yea I have been updating 2 pixels by full factory images for the last year and one has survived all 12 months while the other made it through 11 of 12. but in fear of bricking another pixel device knowing this could potentially happen again... it feels as if going to custom roms would for sure be the safest method and still keep root. Of course losing root and going pure stock would be 100% the best... I love having root and dont want to lose it.
Click to expand...
Click to collapse
Yeah, I see what you're saying and in the exact same boat (2 pixels, gf's is a walleye, mine's a taimen, both have been updated monthly with no issues or def bricking issues, so 14 of 14 and 13 of 14...)...
But I guess that's definitely one of the "safest" methods, just that support for ROMs come and go (hell, even one of the original custom kernels [Flash] is EOL)...but Pixel 2 is only a year "in" and Google will continue to support it for the foreseeable future so it may look like regular support for walleye/taimen-related mods will continue to get regular updates and support as well...
But still, as I enjoy our conversations, it also serves to "bump" this thread as well...
Anyone have any idea on how to reinstall bootloaders, switch slots, enter custom recovery, flash anything all without -- and this is key -- fastboot (because fastboot will not detect and connect with the device)?!?!
I just tried to update to Feb from Jan and this happened to me....
Anything I can do about it?
James1258 said:
I just tried to update to Feb from Jan and this happened to me....
Anything I can do about it?
Click to expand...
Click to collapse
Awww crap! Super sorry to hear that! As you can see, not a lot of ideas or thoughts were submitted, and haven't been in a long while, so there doesn't seem to be much/anything that can be done it seems...
If you truly have the exact same thing, then that means that the USB connection is not working, so, you're not able to get into the recovery nor able to run any commands, so the only recourse it seems me and @Coolpente is to contact Google and attempt at a RMA...
But, as this is a third instance -- there may be more; I'm convinced there are, they just have not spoken up here specifically -- I wonder if this is something to be brought up to Google Support (https://productforums.google.com/forum/#!forum/phone-by-google) and their support forums? I mean, although this might not be a widespread widely known issue, this issue does make the device completely unusable and able to be rescued! For me, that's a serious matter -- as most other issues you can learn to live with it (while still being able to use the device for the most part) and/or it's something that can be worked on, repaired, debugged, etc. -- that needs to be attended to, dealt with, or at the very least brought to their attention.
simplepinoi177 said:
Awww crap! Super sorry to hear that! As you can see, not a lot of ideas or thoughts were submitted, and haven't been in a long while, so there doesn't seem to be much/anything that can be done it seems...
If you truly have the exact same thing, then that means that the USB connection is not working, so, you're not able to get into the recovery nor able to run any commands, so the only recourse it seems me and @Coolpente is to contact Google and attempt at a RMA...
But, as this is a third instance -- there may be more; I'm convinced there are, they just have not spoken up here specifically -- I wonder if this is something to be brought up to Google Support (https://productforums.google.com/forum/#!forum/phone-by-google) and their support forums? I mean, although this might not be a widespread widely known issue, this issue does make the device completely unusable and able to be rescued! For me, that's a serious matter -- as most other issues you can learn to live with it (while still being able to use the device for the most part) and/or it's something that can be worked on, repaired, debugged, etc. -- that needs to be attended to, dealt with, or at the very least brought to their attention.
Click to expand...
Click to collapse
I just contacted Google for an RMA. Hope it doesn't occur on the phone that will be shipped to me. Now I am without a phone for a couple weeks...
James1258 said:
I just tried to update to Feb from Jan and this happened to me....
Anything I can do about it?
Click to expand...
Click to collapse
Did you also ran the flash all without - w?
Sent from my Pixel 2 XL using Tapatalk