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.
Hello, I heard that to hard reset the phone, i need a flashtool. And to unlock bootloader i need to enable usb debugging, however i cant access my phone, because for some weird reason the pin code doesnt work. Can you help me reset the phone? its Xperia S
So im currently trying to repair it with pc companion, but when it says to connect the phone holding the down button, and when i do it, nothing happens, the computer doesnt recognise it. The flash mode stays for 5 seconds, the goes into charge mode. Looked in device manager, but theres nothing. Probably enabling usb debugging would work, but how am i supposed to enable it with phone locked. Maybe i need some drivers?
Try with the Sony Flash Tool from their site, u'll have to get the stock 4.1.2, but at least u'll be able to use your phone
dodek0309 said:
Try with the Sony Flash Tool from their site, u'll have to get the stock 4.1.2, but at least u'll be able to use your phone
Click to expand...
Click to collapse
Well i think it needs bootloader unlocked, but i will try pc companion to reset the phone, maybe that will work. But thanks anyway.
Can someone help?
I was unrooting my phone and I must've skipped a few steps but now my phone is bricked I guess. All I can do at the moment is get into the bootloader but whenever I try and flash anything (recovery,roms etc) I don't permission since I locked my bootloader (it said in a tutorial.. whoops). I tried to follow the unbricking guide here on XDA but it tells you to install weird qualcomm drivers and whenever I try and apply it to my device in device manager it just says that it's not compatible with my device.
So yeah, my bootloader is locked but I need to flash a recovery to get me out of this mess, what do I do?
Have you tried fastboot oem unlock?
It "might" work even if the related setting (in Developer Options) is disabled.
After doing that, try to normally restore the stock firmware.
Ps note that you'll definitely lose all data
Simone98RC said:
Have you tried fastboot oem unlock?
It "might" work even if the related setting (in Developer Options) is disabled.
After doing that, try to normally restore the stock firmware.
Ps note that you'll definitely lose all data
Click to expand...
Click to collapse
Yeah but it just fails
edit- i'll retry the unbricking guide tomorrow
The guide still doesn't work for me, I'm just having problem with the drivers you're meant to use.
I posted on there my issue on more detail.
Update- I fixed it.
I wasn't going into proper recovery mode (I had to turn it off completely and hold volume while plugging in). Then, it popped up on device manager under USB and the drivers worked. Afterwards, I just followed the rest of the tutorial haha.
My wife's fingerprint reader stopped working after the phone fell and she doesn't remember what pin she used to set it up. I tried to factory reset the phone but it still asks for a pin after a wipe.
I want to wipe the phone and install a recovery but I never got around to enabling OEM bootloader unlock and USB debugging.
Would I still be able to unlock the bootloader without having those things enabled? Is there any way to enable them via fastboot or ADB?
In short: no
I just had this same problem with my fiancee's phone.. She forgot as well.. I was able to reset it with a wipe in the stock recovery..
Sent from my Nexus 6P using XDA-Developers Legacy app
DonDizzurp said:
My wife's fingerprint reader stopped working after the phone fell and she doesn't remember what pin she used to set it up. I tried to factory reset the phone but it still asks for a pin after a wipe. I want to wipe the phone and install a recovery but I never got around to enabling OEM bootloader unlock and USB debugging. Would I still be able to unlock the bootloader without having those things enabled? Is there any way to enable them via fastboot or ADB?
Click to expand...
Click to collapse
No. There is no way to enable oem unlock without booting into the OS and enabling it through dev options, nor is there any way to use ADB to toggle it. At this stage the only things you can do are FDR or sideload a full OTA from your PC... but if you don't have her Google login and password (not PIN) you will still be locked out. That is the way FRP works.
I know this sounds dumb, but have you tried clearing the fingerprint sensor? These can be finicky.
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.