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.
Hi All,
Request all to provide any suggestions related to the below issue:
I rolled back from android n preview 2 to android m after which my display is scrambled.I am not able to view any thing on it.
But I am getting calls and able to pick them when I roughly expect the place where I can swipe the dialer right to pick the call.
Few things that I want to highlight is :
1)I had unstable wifi connection while downloading the android m OTA.
2)I removed the unlock bootloader check before rolling back in the developer options.
3)I can also sense that i am able to take screen shots when I am holding the power button and the volume down button based on the sound it normally makes (while capturing screenshots)
I am not able to come to conclusion whether this a hardware issue?(may be i need the replacement of the screen) or can it be due to corrupt ota file update?
Any suggestions would be much appreciated.
thanks
I would first see if flashing the m factory image solves the issue. Then look at hardware.
k.s.deviate said:
I would first see if flashing the m factory image solves the issue. Then look at hardware.
Click to expand...
Click to collapse
thank you but the problem is I am not able to see the screen at all and hence I am not able to go to the fastboot mode or recovery mode.
NeverBackDown said:
thank you but the problem is I am not able to see the screen at all and hence I am not able to go to the fastboot mode or recovery mode.
Click to expand...
Click to collapse
use "adb reboot bootloader" from command prompt to enter bootloader or if you know the device is off, press power + vol up + vol down for roughly 5sec, thatll get into bootloader. than flash factory image.
or last case scenario use wug fresh toolkit to force flash the image, make sure you select the device fails to boot box (I think that's what its called, the only other one states "device on/normal" <-- so NOT that one)
k.s.deviate said:
use "adb reboot bootloader" from command prompt to enter bootloader or if you know the device is off, press power + vol up + vol down for roughly 5sec, thatll get into bootloader. than flash factory image.
or last case scenario use wug fresh toolkit to force flash the image, make sure you select the device fails to boot box (I think that's what its called, the only other one states "device on/normal" <-- so NOT that one)
Click to expand...
Click to collapse
Thanks I am first looking for type c to usb to connect it to my computer,I will try for it tomorrow and also the first option you provided will work only if usb debugging is already enabled on my phone ,right?
NeverBackDown said:
Thanks I am first looking for type c to usb to connect it to my computer,I will try for it tomorrow and also the first option you provided will work only if usb debugging is already enabled on my phone ,right?
Click to expand...
Click to collapse
yes, the adb command will only work if debugging is on. Once in bootlader, use fastboot commands, debugging doesn't matter at that point.
k.s.deviate said:
yes, the adb command will only work if debugging is on. Once in bootlader, use fastboot commands, debugging doesn't matter at that point.
Click to expand...
Click to collapse
Hi All,
I got the cable ,I had everything to flash the official factory images.But the problem is as mentioned earlier I haven't checked the oem unlock in the developer option and this is not allowing to flash the factory images and fastboot flashing unlock is failing.
Is there any work around for this please?
NeverBackDown said:
Hi All,
I got the cable ,I had everything to flash the official factory images.But the problem is as mentioned earlier I haven't checked the oem unlock in the developer option and this is not allowing to flash the factory images and fastboot flashing unlock is failing.
Is there any work around for this please?
Click to expand...
Click to collapse
Not that I'm aware of. Sorry, there is a thread on here that may prove useful that deals with bricked phones with OEM unlocked off. The info there might help you at least get back to stock.
k.s.deviate said:
Not that I'm aware of. Sorry, there is a thread on here that may prove useful that deals with bricked phones with OEM unlocked off. The info there might help you at least get back to stock.
Click to expand...
Click to collapse
In that case ,do you think the service center guys have some other means to deal with if it is a software issue?
NeverBackDown said:
In that case ,do you think the service center guys have some other means to deal with if it is a software issue?
Click to expand...
Click to collapse
Possibly, I have no experience dealing with a service center unfortunately.
NeverBackDown said:
In that case ,do you think the service center guys have some other means to deal with if it is a software issue?
Click to expand...
Click to collapse
I also want to highlight that,I am getting a black screen on the fastboot mode too,i cant see nothing there..Only way i am able to identify that my device is in fastboot mode is by giving fastboot devices command.
So can this be a software issue?
NeverBackDown said:
Hi All,
I got the cable ,I had everything to flash the official factory images.But the problem is as mentioned earlier I haven't checked the oem unlock in the developer option and this is not allowing to flash the factory images and fastboot flashing unlock is failing.
Is there any work around for this please?
Click to expand...
Click to collapse
You might want to look into android screencast.
I don't know if it still works with the latest android releases, but back in kitkat days if I had a screen that wouldn't display I could use screencast and I'd get the framebuffer displaying on the PC. While viewing on PC I could then do touchscreen "guesses" more accurately and presumably you'd be able to enable OEM unlocked bootloader so you can flash factory images.
I have this device and i m loving it but after miui update, it does not connect to computer..no matter whatever i have done including usb debugging,power cycles,reinstalling drivers,mtp,ptp mode. However, when connected to pc, i can hear the connection sound..moreover, softwares like mobogenie,moborobo does recognize the device and connects..even miui suite does not connect..it says enable usb debugging whereas it already has been..plz extend your expertise and help
imurreflection said:
I have this device and i m loving it but after miui update, it does not connect to computer..no matter whatever i have done including usb debugging,power cycles,reinstalling drivers,mtp,ptp mode. However, when connected to pc, i can hear the connection sound..moreover, softwares like mobogenie,moborobo does recognize the device and connects..even miui suite does not connect..it says enable usb debugging whereas it already has been..plz extend your expertise and help
Click to expand...
Click to collapse
Have you tried EDL mode and reflashing Stable MIUI 8 there? Whole different driver, whole different mode.
Crossvxm said:
Have you tried EDL mode and reflashing Stable MIUI 8 there? Whole different driver, whole different mode.
Click to expand...
Click to collapse
Can you please explain what EDL mode is
.i m from India so not sure if reflashing the device will avoid warranty and OTA updates
imurreflection said:
I have this device and i m loving it but after miui update, it does not connect to computer..no matter whatever i have done including usb debugging,power cycles,reinstalling drivers,mtp,ptp mode. However, when connected to pc, i can hear the connection sound..moreover, softwares like mobogenie,moborobo does recognize the device and connects..even miui suite does not connect..it says enable usb debugging whereas it already has been..plz extend your expertise and help
Click to expand...
Click to collapse
imurreflection said:
Can you please explain what EDL mode is
.i m from India so not sure if reflashing the device will avoid warranty and OTA updates
Click to expand...
Click to collapse
EDL mode is Xiaomi's official way to flash on our locked bootloader. It is the only way we can go from Stable to Developer, or recover our device without unlocking the bootloader. It doesn't void the warranty since it is not a modification, nor root, nor a custom rom.
In short, EDL mode for us locked bootloader users (Redmi Note 3, Mi Max, etx) is fastboot mode. If you have owned an older Xiaomi device before the locked bootloader, you probably remember how we can get into Fastboot mode or Recovery mode via the Power + Volume Down or Volume up button combination while powered off. Locked bootloader doesn give us access to those, and instead, we must use Volume Up + Volume Down + Power button combination at the same time while our device is off in order to get into EDL mode (the phone will vibrate, but the screen will stay black and will be detected differently on Windows).
Crossvxm said:
EDL mode is Xiaomi's official way to flash on our locked bootloader. It is the only way we can go from Stable to Developer, or recover our device without unlocking the bootloader. It doesn't void the warranty since it is not a modification, nor root, nor a custom rom.
In short, EDL mode for us locked bootloader users (Redmi Note 3, Mi Max, etx) is fastboot mode. If you have owned an older Xiaomi device before the locked bootloader, you probably remember how we can get into Fastboot mode or Recovery mode via the Power + Volume Down or Volume up button combination while powered off. Locked bootloader doesn give us access to those, and instead, we must use Volume Up +at Volume Down + Power button combination at the same time while our device is off in order to get into EDL mode (the phone will vibrate, but the screen will stay black and will be detected differently on Windows).
Click to expand...
Click to collapse
Hey, thats great info.. Thanks a lot.. I was able to get the issue resolved. I found that thete was an issue with MTP driver.. I reinstalled it and PC immediately recognized it.. Thanks again for your help
Hi Guys,
Yesterday during an official update of my oneplus 5t (using the update manager from the phone itself), the phone got bricked and i dont know why....
So after some research i found it is hard bricked ( basically i cant do nothing, power on i cant, power +volume UP/DOWN too, and even when i plug the charge cable i have neither vibrations nor LED on)
So i follow this tutorial to unbrick the phone:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
I could get the phone recognize by the PC by pressing UP to see the phone as QUSB-BULK and then QUALCOMM QD LOADER after driver's update.
But when i run MSMDownloadTool ( V4.0.27 dumpling 43_0.36_180613) as administrator and click on start, the process get stuck in "waiting for device"
the status of connection before click on start was "connected" and after click and some process it turn to N/A
the status of communication is "memory size....."
status of last communication is "waiting for device"
I have tried several time and always the same result..... stuck in the waiting device
does someone have an idea on how to solve this? because i really need to unbrick the phone....
thank you in advance
EDIT:
I tried another version of MsmDownloadTool (dumpling_43_O.06_171206) and this time, the downloading of cache image failed....
I dont know what to do
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
DaRk-L0rD said:
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
Click to expand...
Click to collapse
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
rokusho32 said:
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
Click to expand...
Click to collapse
Thing are much easier with the unlocked bootloaders!
Charge your phone all night long even if you don't see any sign of life (green or red led light).
Then hold together the Volume UP button and the power button for few seconds into the fastboot mode (hold both buttons for at least 10 seconds) and let me know.
DaRk-L0rD said:
Thing are much easier with the unlocked bootloaders!
Charge your phone all night long even if you don't see any sign of life (green or red led light).
Then hold together the Volume UP button and the power button for few seconds into the fastboot mode (hold both buttons for at least 10 seconds) and let me know.
Click to expand...
Click to collapse
I tried this before and nothing happened....
then when i connect to the pc by pressing UP+ power button, the pc detected it as QUSB_BULK then i install the qualcomm driver and finally i could see the phone in the usb device.
But after MSMDownloadTool step, the process got stuck and display "memory size" as explained in the thread.
rokusho32 said:
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
Click to expand...
Click to collapse
rokusho32 said:
I tried this before and nothing happened....
then when i connect to the pc by pressing UP+ power button, the pc detected it as QUSB_BULK then i install the qualcomm driver and finally i could see the phone in the usb device.
But after MSMDownloadTool step, the process got stuck and display "memory size" as explained in the thread.
Click to expand...
Click to collapse
Go here:
https://forum.xda-developers.com/showpost.php?p=74504343&postcount=3
Follow the instructions for the adb drivers installation.
Once done that, let me know
DaRk-L0rD said:
Go here:
https://forum.xda-developers.com/showpost.php?p=74504343&postcount=3
Follow the instructions for the adb drivers installation.
Once done that, let me know
Click to expand...
Click to collapse
I have installed the ADB drivers
which version of MSMDownloadTool should i use?
DaRk-L0rD said:
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
Click to expand...
Click to collapse
I know this is an old thread, but I'm hoping you have an idea. I have bricked my rooted OnePlus6. I did have Magisk installed. Bootloader was unlocked. I was able to factory reset the phone, but the bootloader was still locked (I had TWRP installed and factory reset using it). I then used Fastboot to relock the bootloader, and that's when my troubles started. I could only get into Fastboot. I found a solution on the web, installed the Qualcomm drivers (and they recognize my device, which I connected by holding down the volume up button before connecting to the USB cable), and started the OnePlus 6 (MSM) unbrick tool. However, it just sits there saying "waiting for device". I actually seem to have two entries for the device, one saying Index and one saying "1" (although I think the device is on COM3). Should it take forever? How can I get it past "Waiting for device". Thanks.
rcbjr2 said:
I know this is an old thread, but I'm hoping you have an idea. I have bricked my rooted OnePlus6. I did have Magisk installed. Bootloader was unlocked. I was able to factory reset the phone, but the bootloader was still locked (I had TWRP installed and factory reset using it). I then used Fastboot to relock the bootloader, and that's when my troubles started. I could only get into Fastboot. I found a solution on the web, installed the Qualcomm drivers (and they recognize my device, which I connected by holding down the volume up button before connecting to the USB cable), and started the OnePlus 6 (MSM) unbrick tool. However, it just sits there saying "waiting for device". I actually seem to have two entries for the device, one saying Index and one saying "1" (although I think the device is on COM3). Should it take forever? How can I get it past "Waiting for device". Thanks.
Click to expand...
Click to collapse
I have same situation.. did you resolve this problem?
piechu11 said:
I have same situation.. did you resolve this problem?
Click to expand...
Click to collapse
I contacted OnePlus and I sent them the phone and they reinstalled the operating system. I was never able to fix it myself. I even had an online session with OnePlus and they couldn't get the MSM software to recognize the phone (even though it was truly connected to my laptop). I also had an issue with my OnePlus 8T that got messed up doing something with Magisk, and OnePlus reinstalled the operating system as well. I still can't boot from the A partition though; just the B partition.
piechu11 said:
I have same situation.. did you resolve this problem?
Click to expand...
Click to collapse
Okay, for anyone facing same problem as me, i found solution (working for me). Before using MSM Tool, you need to install Qualcomm USB Drivers.
During instalation you need to choose second option "ETHERNET-DHCP"!
At first, I chose WWAN-DHCP - which caused problem with connection
piechu11 said:
Okay, for anyone facing same problem as me, i found solution (working for me). Before using MSM Tool, you need to install Qualcomm USB Drivers.
During instalation you need to choose second option "ETHERNET-DHCP"!
View attachment 5511425
At first, I chose WWAN-DHCP - which caused problem with connection
Click to expand...
Click to collapse
Thank you this solved my problem exactly.
i was restoring my metro by tmobile oneplus nord n10 BE2025 model with build tag BE88CF
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.