Related
Hi all,
Trying to unlock the bootloader. I'm a bit of a noob regarding bootloader. I got it as far as rebooting into bootloader using command prompt. But as soon as the phone gets there it seems to hang. I will no longer get a response via command prompt (just telling me its waiting for device) and the device itself gets unresponsive. The hold 10 seconds to power down thing doesn't work either. I have to physically remove the battery for it to turn off.
Can anyone help me along? Cause I'd really like to root my phone.
Thank you
Roflmao. Guessing you haven't read any threads regarding root
WeeDoggy said:
Hi all,
Trying to unlock the bootloader. I'm a bit of a noob regarding bootloader. I got it as far as rebooting into bootloader using command prompt. But as soon as the phone gets there it seems to hang. I will no longer get a response via command prompt (just telling me its waiting for device) and the device itself gets unresponsive. The hold 10 seconds to power down thing doesn't work either. I have to physically remove the battery for it to turn off.
Can anyone help me along? Cause I'd really like to root my phone.
Thank you
Click to expand...
Click to collapse
Sadly unless you have the h815 version you are NOT going to get any further than what you are getting (at least at this point in time). The ONLY version of the G4 that has root right now is the h815 and that is simply because LG released the bootloader unlock via their page.
It is being worked on but you have to remember that this is a very new device and this is going to take some time, so just relax and play the waiting game with the rest of us in the mean time.
Yeah I have read the thread about rooting and I in fact do have the h815. That's why I am trying to root it and that's why I am busy trying to unlock the bootloader with the LG unlock tool. I said I'm a noob, not a dumbass regarding unlocking a bootloader cause before I had a samsung and I never needed to unlock that.
So once again my question stands why is my device getting unresponsive once it is succesfully been rebooted into bootloader via command prompt?
Thank you
WeeDoggy said:
Hi all,
Trying to unlock the bootloader. I'm a bit of a noob regarding bootloader. I got it as far as rebooting into bootloader using command prompt. But as soon as the phone gets there it seems to hang. I will no longer get a response via command prompt (just telling me its waiting for device) and the device itself gets unresponsive. The hold 10 seconds to power down thing doesn't work either. I have to physically remove the battery for it to turn off.
Can anyone help me along? Cause I'd really like to root my phone.
Thank you
Click to expand...
Click to collapse
Have you enabled the OEM Bootloader In Dev Options? Who is your provider as some of them will force lock the bootloader and not allow it to be unlocked unless you take it to a phone shop but you will void both LG's and Their Warranty and any support from them
Also when you are on bootloader screen with few lines with very litle fonts, try to make sure that in your Windows devices manager, your phone is corectly listed.
For some reason it did happend to me that drivers for the phone in bootloader mode wasn't properly installed.
bleuxeon said:
Also when you are on bootloader screen with few lines with very litle fonts, try to make sure that in your Windows devices manager, your phone is corectly listed.
For some reason it did happend to me that drivers for the phone in bootloader mode wasn't properly installed.
Click to expand...
Click to collapse
When I go into bootloader my PC does make that sound where it's like I disconnected a USB device. But as far as I can tell there's nothing unusual going in Windows device manager. Which drivers have you installed? I installed the pc drivers via my phone. And I saw adb drivers in there when it got installed. I thought that would suffice.
But it also freezes up. I can't close the phone anymore even with the 10-second power hold. It just locks up
Im having the exact same problem did everything right but as soon as i enter bootloading mode my pc just doesnt reconize it anymore or something
WeeDoggy said:
Hi all,
Trying to unlock the bootloader. I'm a bit of a noob regarding bootloader. I got it as far as rebooting into bootloader using command prompt. But as soon as the phone gets there it seems to hang. I will no longer get a response via command prompt (just telling me its waiting for device) and the device itself gets unresponsive. The hold 10 seconds to power down thing doesn't work either. I have to physically remove the battery for it to turn off.
Can anyone help me along? Cause I'd really like to root my phone.
Thank you
Click to expand...
Click to collapse
I had exactly the same problem with the same model. When the device is in fastboot mode and not responding open up devices and printers. For me it was now showing as android instead of G4 and the USB disconnect sound means you dont have to correct drivers even if you installed the LG drivers.
For me the fix was going to windows updater and allow it to update drivers. Now right click the android device and trouble run it. It updated the drivers for me
and I was able to run the command to get the device-id.
Hope it helps
Legion377 said:
I had exactly the same problem with the same model. When the device is in fastboot mode and not responding open up devices and printers. For me it was now showing as android instead of G4 and the USB disconnect sound means you dont have to correct drivers even if you installed the LG drivers.
For me the fix was going to windows updater and allow it to update drivers. Now right click the android device and trouble run it. It updated the drivers for me
and I was able to run the command to get the device-id.
Hope it helps
Click to expand...
Click to collapse
I have the same problem, what do you mean by "windows updater"? do you mean "windows update"?
And what is "trouble run it"?
Thanks in advance.
Without checking the forums I went ahead and clicked on the Wireless Update on the P8000 and now it just hangs on the Elephone logo and is not recognized when I try to connect to the PC. Has anyone else done this and has the same problem, any way of fixing?
UPDATE: Decided to mess around with the phone to try and get back to life, found an old laptop, loaded the Drivers (without any security warnings), loaded the SP Flash Tool. Connnected the phone to the laptop, did not register, downloaded the ROM 150907, went to Flash Tool clicked on scatter.txt file, pressed the power button on the phone and somehow connection was made to the phone. Bottom line is that it kicked into life with the new 150907 software, from a non techie, I am well chuffed, certainly will not be doing a Wireless update anytime soon. The new ROM is a lot more stable and even allows me to use my Works email on the Exchange services account where I had previous issues.
I have the same problem. The OTA update got my phone stuck in the Elephone boot animation. I am using Windows 10 currently and I can't install the drivers. What OS did the computer you used run?
UPDATE: I did it!! I used this guide ( http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/ ) to allow me to install the drivers in Windows 10, and then used the flashtool. It took me some tries to get the flashtool to recognized the device but it did it.
Unfortunately all data was wiped
emkwrx said:
UPDATE: Decided to mess around with the phone to try and get back to life, found an old laptop, loaded the Drivers (without any security warnings), loaded the SP Flash Tool. Connnected the phone to the laptop, did not register, downloaded the ROM 150907, went to Flash Tool clicked on scatter.txt file, pressed the power button on the phone and somehow connection was made to the phone. Bottom line is that it kicked into life with the new 150907 software, from a non techie, I am well chuffed, certainly will not be doing a Wireless update anytime soon. The new ROM is a lot more stable and even allows me to use my Works email on the Exchange services account where I had previous issues.
Click to expand...
Click to collapse
GroupStudyRoomF said:
I have the same problem. The OTA update got my phone stuck in the Elephone boot animation. I am using Windows 10 currently and I can't install the drivers. What OS did the computer you used run?
UPDATE: I did it!! I used this guide ( http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/ ) to allow me to install the drivers in Windows 10, and then used the flashtool. It took me some tries to get the flashtool to recognized the device but it did it.
Unfortunately all data was wiped
Click to expand...
Click to collapse
Which sp flash tool version are you folks running?
For me, with version .520 and .532, the flashtool stops responding as soon as the phone is connected.
Also, does the phone need to be switched off for it to be recognised? Or does it need to start booting after a shutdown?
One more, initiate "download to phone" from flashtool and then connect phone or vice versa?
Sent from my A0001 using Tapatalk
a.cid said:
Which sp flash tool version are you folks running?
For me, with version .520 and .532, the flashtool stops responding as soon as the phone is connected.
Also, does the phone need to be switched off for it to be recognised? Or does it need to start booting after a shutdown?
One more, initiate "download to phone" from flashtool and then connect phone or vice versa?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
The zip I downloaded is this: "SP_Flash_Tool_exe_Windows_v5.1520.00.000"
Yes it has to be switched off first and then to be connected. As for the last question I don't remember exactly because I tried many times in different ways and I don't remember which worked in the end.
a.cid said:
Which sp flash tool version are you folks running?
For me, with version .520 and .532, the flashtool stops responding as soon as the phone is connected.
Also, does the phone need to be switched off for it to be recognised? Or does it need to start booting after a shutdown?
One more, initiate "download to phone" from flashtool and then connect phone or vice versa?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
i use the 532 sp tool and its fine for me. maybe redownload it again.
the phone has to be turned off . then press on download in the sp flashtool and connect the phone..
skeleton1911 said:
i use the 532 sp tool and its fine for me. maybe redownload it again.
the phone has to be turned off . then press on download in the sp flashtool and connect the phone..
Click to expand...
Click to collapse
The problem with this one was phone never stayed off. It would just keep switching on and getting stuck at boot screen.
I managed to fix it. Used 532 SP tool. Used an XP computer with anti virus turned off. To keep the phone shut down, I let it run out of juice (took a loooooooong time, not looking forward to doing this again), and then used an older usb cable to just get the phone to stay alive on usb current. Once you get the vcom loader message for mt65xx for usb recognition, that's when you're good to go.
a.cid said:
The problem with this one was phone never stayed off. It would just keep switching on and getting stuck at boot screen.
I managed to fix it. Used 532 SP tool. Used an XP computer with anti virus turned off. To keep the phone shut down, I let it run out of juice (took a loooooooong time, not looking forward to doing this again), and then used an older usb cable to just get the phone to stay alive on usb current. Once you get the vcom loader message for mt65xx for usb recognition, that's when you're good to go.
Click to expand...
Click to collapse
There is an easy trick to turn phone off. Reboot to recovery . (in stock there is the red android then press and hold power , press vol up and it will Boot into stock recovery)
Browse to "turn phone off."
Then its off and dont reboot, you can use the flashtool....etc
Gesendet von meinem Elephone P8000 mit Tapatalk
sooo, I gues something went wrong... since the new marshmallow images was posted today, there was a thread on reddit on how I can just download the image and rename it and flash it as OTA. The phone reconginzed the image and went half way through the install and then went black. now it wont even buzz or register the charger. Does nothing when connected to the computer either so I assume there is nothing that could be done. Quite a shame, the phone worked quite nicely until is killed it . Anything I can do?
Did you install it thru TWRP?
thekingestkong said:
sooo, I gues something went wrong... since the new marshmallow images was posted today, there was a thread on reddit on how I can just download the image and rename it and flash it as OTA. The phone reconginzed the image and went half way through the install and then went black. now it wont even buzz or register the charger. Does nothing when connected to the computer either so I assume there is nothing that could be done. Quite a shame, the phone worked quite nicely until is killed it . Anything I can do?
Click to expand...
Click to collapse
There is one thing I recommend trying as there is a bug in official firmware where the phone when connected to a computer can turn off randomly and not charge or boot. What you need to do is disassemble the phone and unplug the connector at the top of the phone to disconnect the battery and then plug it in.
krazy23 said:
Did you install it thru TWRP?
Click to expand...
Click to collapse
no, the phone picked up the update from the internal storage
dc959 said:
There is one thing I recommend trying as there is a bug in official firmware where the phone when connected to a computer can turn off randomly and not charge or boot. What you need to do is disassemble the phone and unplug the connector at the top of the phone to disconnect the battery and then plug it in.
Click to expand...
Click to collapse
thanks, I'm aware of that. Some folks experiencing the same issue tried that with no success. My phone is still under warranty and the screw securing the backplate has a seal on it that I dont want to tamper with.
I guess I'll be sending the phone for to Asus for repair...
Don't lose hope.
My phone was in a similar predicament.
No response to any buttons, nothing on screen, no buzzing or LED's at all.
I was able to get it recognized in the xFSTK Downloader and showing up in windows device manager as a Moorefield device.
I tried many times to get it to put the images on the phone through the xFSTK tool and it failed many times.
I was about to give up and tried again this morning and miraculously the writing succeeded and now my phone is in a bootloop (I think the battery may have been completely drained with my attempts to save it's life.)
I have it on charge currently so hopefully when there is enough juice I should be able to flash the raw file and be back up and running.
I see, you can follow the unbricking tutorial in the general section. Works fine for me and saved me from sending it to the service center.
krazy23 said:
Did you install it thru TWRP?
Click to expand...
Click to collapse
I did! And now my phone is dead! But it buzzes when I press the power button for some seconds.. But it's always black
galagala2 said:
I did! And now my phone is dead! But it buzzes when I press the power button for some seconds.. But it's always black
Click to expand...
Click to collapse
That's what happened to my phone, you can follow this thread this worked for me. Unbricking Method
krazy23 said:
That's what happened to my phone, you can follow this thread this worked for me. Unbricking Method
Click to expand...
Click to collapse
do you lose the data this way?
thekingestkong said:
do you lose the data this way?
Click to expand...
Click to collapse
Unfortunately, yes. Because I ticked the "wipe data" checkbox in the ASUS Flash Tool. Not sure what will happen if I don't. :fingers-crossed:
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfon
I also bricked my phone and used the method to fix my phone. Make sure you have all the required drivers installed in your pc/laptop before doing this. I took help of DriverMax to solve the drivers related issues. Make sure before installing and running the XFTSK tool all the drivers and everything is installed otherwise you will see blank forms in the Tool.
My latest configuration was:
Bullhead 32 GB board,
PureNexus (6.0.1): July build
PureNexus Gapps
Stock kernel
TWRP
SuperSU
Situation/problem: One day, the phone went off in my pocket, and I thought it accidentally got powered off or something. When I tried to boot it, it would load the Google screen, but not the boot process (this is not a bootloop as it won't even start the boot process). So I went to the BL, tried to boot from there, no luck.
Then I tried to get into recovery from BL, still it would freeze for a few seconds, load the google screen, and back to BL.
So I realized it was time to clean flash, I connected in fastboot mode, but my computer (Linux, Ubunutu 16.04) won't detect the device fastboot mode (I have done everything before on the same computer). Just to be sure, I tried connecting in 3 different computers so that it wasn't a driver problem, but to no avail.
I am now stuck with a device that won't go past the bootloader and won't even let me flash a new system.
Possible problems I think this may be a problem with the USB port and I had just not realized it, because I had dropped the phone from 1m high just a week ago.
When I called the LG service, they said they'd have to replace motherboard and that it can't have been the USB port.
I am perplexed now, as to what to do. I had saved up loads to buy the latest flagship Nexus just this January, and now it's going away...
Another observation: I was having problems with the phone as it was randomly rebooting every once in a while for a month, but I ignored flashing a new build because I was busy with studies. I don't know if this is related but just putting it out there.
Possible things that I could do? Appreciate your help in advance.
zakoda said:
My latest configuration was:
Bullhead 32 GB board,
PureNexus (6.0.1): July build
PureNexus Gapps
Stock kernel
TWRP
SuperSU
Situation/problem: One day, the phone went off in my pocket, and I thought it accidentally got powered off or something. When I tried to boot it, it would load the Google screen, but not the boot process (this is not a bootloop as it won't even start the boot process). So I went to the BL, tried to boot from there, no luck.
Then I tried to get into recovery from BL, still it would freeze for a few seconds, load the google screen, and back to BL.
So I realized it was time to clean flash, I connected in fastboot mode, but my computer (Linux, Ubunutu 16.04) won't detect the device fastboot mode (I have done everything before on the same computer). Just to be sure, I tried connecting in 3 different computers so that it wasn't a driver problem, but to no avail.
I am now stuck with a device that won't go past the bootloader and won't even let me flash a new system.
Possible problems I think this may be a problem with the USB port and I had just not realized it, because I had dropped the phone from 1m high just a week ago.
When I called the LG service, they said they'd have to replace motherboard and that it can't have been the USB port.
I am perplexed now, as to what to do. I had saved up loads to buy the latest flagship Nexus just this January, and now it's going away...
Another observation: I was having problems with the phone as it was randomly rebooting every once in a while for a month, but I ignored flashing a new build because I was busy with studies. I don't know if this is related but just putting it out there.
Possible things that I could do? Appreciate your help in advance.
Click to expand...
Click to collapse
Here's your solution for it not being detected in fastboot mode.......in fastboot mode, connect your phone to your computer. go to your device manager and find your device. double click on your device, right click on the second option and select update driver. than select browse my computer and than select pick from a list of drivers and manually install the driver for fastboot mode.....hope this helps :good:
dominoeflux said:
Here's your solution for it not being detected in fastboot mode.......in fastboot mode, connect your phone to your computer. go to your device manager and find your device. double click on your device, right click on the second option and select update driver. than select browse my computer and than select pick from a list of drivers and manually install the driver for fastboot mode.....hope this helps :good:
Click to expand...
Click to collapse
I have mentioned in my post: It is not a driver problem
zakoda said:
I have mentioned in my post: It is not a driver problem
Click to expand...
Click to collapse
if its not being detected in fastboot mode, than that means it's a driver problem since the same thing happened to me. you have to manually install the fastboot driver for fastboot mode. I've read your post and I understood exactly what you were talking about. have you even tried to check the driver? have you tried flashing back stock? if you've checked other computers that you have mentioned and it's still not detecting it in fastboot mode with the other computers, than the driver for fastboot mode needs to be updated manually, seeing that if it was detected by the other computers that you have, you wouldn't be asking for help right now because your device would already be up and running. hey i'm just trying to help u here. it doesn't hurt to double check your driver. I may be a junior member, but I know plenty seeing that I've been through the same situation myself. if it's not the driver as you say it's not, what version TWRP were you running and did you restore a backup with the EFS checked?
Hey, I can confirm it's not a driver problem.
I got the phone to boot up yesterday, flashed the latest PureNexus (7.x) and after a short while it again went into reboot cycles.
I tried TWRP, there also mid-flashing it randomly rebooted. I think it is rebooting after even small amount of activity. Maybe the thermal sensors are damaged causing it to flag warning with slightest heating. Or maybe some other circuitry is damaged, causing the temperature to actually rise in short while, and it is not being felt due to the plastic body. In any case I think this is a hardware damage, though I have no clue why. I will try contacting Google to see if they can replace it.
By the way, how long is the warranty valid? I had bought the device in Dec 2015.
zakoda said:
Hey, I can confirm it's not a driver problem.
I got the phone to boot up yesterday, flashed the latest PureNexus (7.x) and after a short while it again went into reboot cycles.
I tried TWRP, there also mid-flashing it randomly rebooted. I think it is rebooting after even small amount of activity. Maybe the thermal sensors are damaged causing it to flag warning with slightest heating. Or maybe some other circuitry is damaged, causing the temperature to actually rise in short while, and it is not being felt due to the plastic body. In any case I think this is a hardware damage, though I have no clue why. I will try contacting Google to see if they can replace it.
By the way, how long is the warranty valid? I had bought the device in Dec 2015.
Click to expand...
Click to collapse
In the most country, the warranty is 12month so maybe gone because now it's 21th of december
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
I would try the android flash tool and flash the whole full ROM onto the phone. Expect to lose your data though.
mkhcb said:
I would try the android flash tool and flash the whole full ROM onto the phone. Expect to lose your data though.
Click to expand...
Click to collapse
Doesn't your phone have to be unlocked to use the flash tool?
The data is all backed up so it's not a problem to lose it. The problem is actually making the phone to boot past the logo... I will try that Android Flash Tool but I fear that the phone should be unlocked first
Try this tool: https://pixelrepair.withgoogle.com/carrier_selection
Not sure if its any different to the android flash tool.
As expected, Android Flash Tool requires you to to have the device unlocked. At this point I am out of ideas and is truly disappointed. The tool mentioned above probably works the same way.
Maybe try sideloading OTA again. Are you able to do that?
mclarence said:
Try this tool: https://pixelrepair.withgoogle.com/carrier_selection
Not sure if its any different to the android flash tool.
Click to expand...
Click to collapse
McNaccken said:
As expected, Android Flash Tool requires you to to have the device unlocked. At this point I am out of ideas and is truly disappointed. The tool mentioned above probably works the same way.
Click to expand...
Click to collapse
Unfortunately, someone else in another thread reported that the Pixel Repair site (not the Android Flash Tool) hasn't been updated for the P6P.
McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
If you can still get into recovery mode, maybe try sideloading the OTA again?
EDIT: Ninja'd by @znel52
Lughnasadh said:
If you can still get into recovery mode, maybe try sideloading the OTA again?
EDIT: Ninja'd by @znel52
Click to expand...
Click to collapse
Yeah I'm afraid since he did a factory reset debugging got disabled. Worth a shot though.
znel52 said:
Yeah I'm afraid since he did a factory reset debugging got disabled. Worth a shot though.
Click to expand...
Click to collapse
Oh crap, didn't think about that.
I know not everyone has access to a laptop but if you do always use that over a desktop. In the event of something like this you will have the battery power to carry you through.
I'm sorry this happened to you. The only option may be to send it to Google for repairs.
Sorry for your phone. I experienced this on a nexus 6 that didn't have USB debugging or OEM unlock enabled. I tried sideload, put the update package on the phone storage, try to update with Android recovery. Nothing worked. Stuff happens with phones. I hope you can get a new phone.
God bless.
Sorry to hear this. It seems that I need to open USB debugging option just in case for my Pixel 6, which finally arrived across the ocean after a month.
McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
Since the Repairtool has not been updated for your needs and considering that your device is not unlocked, your only option is to contact Google (/your seller). Maybe they can offer you an updated version of the tool (unlikely) or replace your device.
You just described, btw, my horror scenario when updating the BIOS of my PC. The lights going out, when doing a firmware update o.o
Oh my. I'm so sorry for you to have experienced that.
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
McNaccken said:
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
Click to expand...
Click to collapse
My apologies for asking the obvious - did you select "adb sideload" in the recovery menu ? At least I was blind enough to oversee that I need to select this option first
Can you boot into fastboot from the recovery ? If yes you could also try installing a factory image instead of the update package.... I read you cannot because your device is locked, but you can unlock in fastboot (you can always relock later).... only downside is that this will clear all data on the phone for sure....
McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
I had a similar issue with applying ota updates and have seen quite a few reports of users having trouble. Not sure what the deal is, but for some reason this phone seems super finicky with updates. Are you still in the return window? You may want to reach out to Google support or one of their "authorized repair shops".
For me, I ran the flash all bat, rebooted, got a message saying my device can't be trusted. So I rebooted, wiped data, rebooted again and got the same thing. So I rebooted, ran the flash all bat file again, rebooted phone, and screen went black and it never powered on again. Suspect circuit board may have fried some how. Anyways, long story short, contacted Google and had a replacement sent out with minimal hassle.
McNaccken said:
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
Click to expand...
Click to collapse
so you can get through this... you'll be fine. pick adb sideload and it will say waiting, then run the command.
you can also change slots at the bootloader menu or try running the unlock oem command to see if it will allow you to unlock..... not sure if you can change slots without unlocking bootloader. try different USB ports on your computer (and restart your computer just in case) along with using the latest platform tools (adb/fastboot) and USB driver directly from Google (not third party apps or websites.
download the OTA zip again (and just open and close it quickly to verify it isn't corrupt).. and also make sure you have 5-10GB of space free on your computer.
usually the boot slot is changed whenever an OTA is flashed. it will tell you what slot you're in at the bootloader menu (where it says fastboot and device state locked).
can you try holding power button (when it's not plugged in) and as soon as you see then Google logo, hold volume down. that will get you to safe mode. and as quickly as you can, enable "OEM Unlocking" - which will allow you to flash a full factory image.
sorry for this comment being all over the place. if you need help, just reply, and I'll be more methodical next time
s3axel said:
I read you cannot because your device is locked, but you can unlock in fastboot (you can always relock later).... only downside is that this will clear all data on the phone for sure....
Click to expand...
Click to collapse
I don't think the problem is that his bootloader is locked - it's unlocked, however, they factory reset the device which likely caused USB Debugging to be turned off, as it defaults to after a factory reset.
I'm so glad years ago I swore to use Uninterruptible Power Supplies (UPS) for all the PCs I build for myself or my wife.