Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
unlock it using flash tool, just press unlock wait and enter the code.. done
KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
try using different usb cable/ different port.
Had same problem....some driver was missing
Sent from my C5503 using xda app-developers app
I've finally gotten flash tool to work, however now it gives me an error saying that my device cannot be officially unlocked,
EDIT: i'm pretty sure i've unlocked the bootloader now, as flashtool had me enter an unlock code and my device has had all of its data reset.
however my issues continue as now flashtool utterly refuses to pick up my device. I have re-installed all drivers, flashtool, etc but still nothing.
sometimes it may have conflicts when flashtool and other tools use their own instance of adb or fastboot. I think the best thing to do now is reinstalling regular drivers normally. don't forget to enable usb debugging...
this may be useful :
Code:
[I]ADB_PATH[/I]\adb kill-server
exit
create a text file, paste this code then save it as ADB - Kill.cmd
Related
I am trying to unlock my device and keep having the problem of it not being recognized in fastboot.
I have the latest drivers from the android SDK (4.0), and have trying reinstalling them. It appears to mount fine, and all of the adb commands work. However, when I try fastboot devices, it returns nothing. fastboot oem unlock only gives a "waiting for device".
Any ideas?
Thanks
Device needs to be in the fastboot screen of the bootloader...
Sent from my Nexus One using XDA App
While I feel really stupid for somehow missing that fact in dozens of threads, it doesn't seem to fix the problem. I now have it in fastboot and at the top is says "FASTBOOT USB". Windows recognizes the device when its plugged in, but still no luck with devices.
Nevermind, I figured it out. It downloaded fastboot from another source. I am guessing that I was somehow missing a file. Thanks though.
Last night I was on my nexus before I would go to bed. I opened the franco kernel app and then noticed that r6 was available for download. I downloaded and flashed it and was about to go to sleep when I noticed the notification light that my phone was charging. I thought it was neat then tried to get some sleep, but my promised sleep did not come quick. After a good chunk of time had passed, I thought that my lack of sleep was caused by the green light that was barely noticable. I searched and searched in the app to try and find an option to disable the LED, but could not. I then decided that the best way to get rid of the light, would be to flash the older r5 kernel so I wouldn't have to see the light anymore. I hit flash and my phone rebooted and then brought me to the bootloader. I attempted to reboot but I could not. I've tried using adb and nexus root toolkit to get my device to work again, but they can't seem to find it without the correct drivers. I installed Motorola device manager, nothing. I tried to follow the instructions in the toolkit to get the correct drivers installed but I can't continue with the need to enable debugging, which I cannot do from being stuck at the bootloader.
Under bootloader logs, I have the following messages:
Invalid boot image size!
failed to validate boot image
Fastboot Reason: Fall-through from normal boot mode
Any help would be greatly appreciated.
USB debugging is an android setting. It can only be used when android is running. If you had USB debugging on, it would make absolutely no difference in recovery or bootloader so don't let that step stop you.
From the logs, it sounds like your kernel download is corrupt or didn't flash properly. I had a similar message when I flashed a partially downloaded recovery image today.
Just fastboot flash a complete boot image
I tried that last night by launching adb and doing 'adb devices' but my device is unrecognized and I am unsure of how to go about fixing that.
thecupman said:
I tried that last night by launching adb and doing 'adb devices' but my device is unrecognized and I am unsure of how to go about fixing that.
Click to expand...
Click to collapse
Tried what exactly? Adb and fastboot are two different things. Adb works in android or recovery only. Fastboot works in boot loader only. Boot to boot loader and do "fastboot devices"
Ah that was my mistake. But the fastboot devices command just returns a new line for a new command to be entered in
thecupman said:
Ah that was my mistake. But the fastboot devices command just returns a new line for a new command to be entered in
Click to expand...
Click to collapse
That probably means there is a blank line between them - showing that no device is found. Unlike Adb it just gives a blank line instead of "no devices".
Probably means a driver issue or cable issue. Try different USB ports / cables if you can. Check to see if there are any yellow triangles in device manager too.
I'm new to this phone so I don't know where the drivers are if you need them. If I ever find them, I'll port my nexus 5 Adb and fastboot thread over here. Unfortunately i use Linux at home so I don't really have a driver issue.
Oh, so if I were to use Linux I wouldn't have to deal with missing drivers? I'm assuming that's the issue since no matter which port I use, 'Connect USB Data Cable' doesn't change
thecupman said:
Oh, so if I were to use Linux I wouldn't have to deal with missing drivers? I'm assuming that's the issue since no matter which port I use, 'Connect USB Data Cable' doesn't change
Click to expand...
Click to collapse
I can't say for sure. In Linux you may need to add UDEV rules. I didn't though. My bootloader is just recognised.
Please do check your device manager though.
I'm sorry i can't help more right now. I'm going to bed.
Okay, thank you! I'll reply if I encounter any other errors!
The Google driver works for all Nexus devices (except the GNex): http://developer.android.com/sdk/win-usb.html
Hi,
I looked all over the place but could not find a way to unlock the bootloader of the latest version of my device. Currently running Android 6.0 H81120p and rooting this version as well!
hammy88 said:
Hi,
I looked all over the place but could not find a way to unlock the bootloader of the latest version of my device. Currently running Android 6.0 H81120p and rooting this version as well!
Click to expand...
Click to collapse
i recommend for you to KDZ 20p refurbished..
and heres the instruccions same as 20i
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
i tried but its not working as i get stuck on waiting for device after i type the command to reboot to bootloader, installed google usb drivers , lg drivers and all but nothing seemed to be fixing the issue
hammy88 said:
i tried but its not working as i get stuck on waiting for device after i type the command to reboot to bootloader, installed google usb drivers , lg drivers and all but nothing seemed to be fixing the issue
Click to expand...
Click to collapse
did you click on screen when you gave the command to go into fastboot it shows some sort of numbers and leters and asks you if you want to allow phone .??/ did you
Yes I did allow the computer to have access to the phone, when i typed the command to reboot to bootloader it did, but then when i type the command to fastboot oem unlock it gets stuck on waiting for any device. I tried doing it again just to check, after i get to bootloader, i typed adb devices it doesn't show any device thats connected
hammy88 said:
Yes I did allow the computer to have access to the phone, when i typed the command to reboot to bootloader it did, but then when i type the command to fastboot oem unlock it gets stuck on waiting for any device. I tried doing it again just to check, after i get to bootloader, i typed adb devices it doesn't show any device thats connected
Click to expand...
Click to collapse
adb reboot bootloader (phone reboots to bootloader)
fastboot oem unlock (this wipes ALL data!!)
debugging tick and unlock oen in dev options.?
raptorddd said:
adb reboot bootloader (phone reboots to bootloader)
fastboot oem unlock (this wipes ALL data!!)
debugging tick and unlock oen in dev options.?
Click to expand...
Click to collapse
I checked the oem unlock, and the USB debugging thing is checked as well. Developers Options is on but same issue. I installed the latest USB drivers, installed Google USB drivers. I went to device Manger and I can't see that my device is even connected!
hammy88 said:
I checked the oem unlock, and the USB debugging thing is checked as well. Developers Options is on but same issue. I installed the latest USB drivers, installed Google USB drivers. I went to device Manger and I can't see that my device is even connected!
Click to expand...
Click to collapse
can try another computer maybe. i use the drivers from LGUP..
am afraid i do not know how to proceed from here. am pretty sure you are not alonei gave read someting similar but.. i didnt pay attention
I tried 3 other computers , did not help resolve the issue
hammy88 said:
I tried 3 other computers , did not help resolve the issue
Click to expand...
Click to collapse
i came across this try it.
http://forum.xda-developers.com/showpost.php?p=69339003&postcount=2
Use Linux dude, also try different cables. My stock g4 came with a bad cable that only charged.
I've had exactly the same problem as hammy88. Is what is referred to as "fastboot mode" the same as download mode? I know it's relatively easy to get into download mode. But "adb reboot bootloader" doesn't work for me.
Fastboot mode ≠ Download mode
If you did tick "Enable OEM unlock" , and adb reboot bootloader doesn't work, then I guess is BL is locked now.
I tried the method , i found that Android Bootloader does not have a green light, so i went to device manager to try to update the driver but it wasn't even there, clicked on view to show the hidden items or whatever then found android device, when i clicked update the driver i could not find the Google fastboot thing to update it with, all i got was either LG usb or ADB interface even thoough i downloader google fastboot usb drivers few days ago
hammy88 said:
I tried the method , i found that Android Bootloader does not have a green light, so i went to device manager to try to update the driver but it wasn't even there, clicked on view to show the hidden items or whatever then found android device, when i clicked update the driver i could not find the Google fastboot thing to update it with, all i got was either LG usb or ADB interface even thoough i downloader google fastboot usb drivers few days ago
Click to expand...
Click to collapse
Brother, be calm. Find the fastboot drivers. And update.
You will figure it out. Just do it.
hi fellows im fascing a problem,
Im unable to get my phone in adb or fastboot mode
when i plug my phone in and hit ADB Devices after allowing "Using USB to transfer files" it shows no device,
but if i dont allow it shows my devices.
again if i hit "Adb reboot-bootloader"
i restarts in bootloader but again here fastboot shows nothing.
any knid guy also let me know how to unlock bootloader on august patch after resolving this issue.
reinstalling windows solved my problem
Ibtisaam said:
hi fellows im fascing a problem,
Im unable to get my phone in adb or fastboot mode
when i plug my phone in and hit ADB Devices after allowing "Using USB to transfer files" it shows no device,
but if i dont allow it shows my devices.
again if i hit "Adb reboot-bootloader"
i restarts in bootloader but again here fastboot shows nothing.
any knid guy also let me know how to unlock bootloader on august patch after resolving this issue.
Click to expand...
Click to collapse
reinstalling windows solved my problem
Hi I've a pixel5, it was reset to V11 software for compatibility with my son's medical device. Now with added security the app wont work because the bootlaoder is open. When I boot it say sits unlocked and to visit g.co/ABH
I've tried but cannot get it closed
When I go to fastboot I get the 'no command'.. on tring to flash it allows me to see the device and reboot the bootloader BUT then it will not respond to the cmd fastboot devices. when I try fastboot flashing lock it just says <waiting for device>
Any help? !
Billy
Try installing the usb driver https://developer.android.com/studio/run/win-usb
billyedit said:
Hi I've a pixel5, it was reset to V11 software for compatibility with my son's medical device. Now with added security the app wont work because the bootlaoder is open. When I boot it say sits unlocked and to visit g.co/ABH
I've tried but cannot get it closed
When I go to fastboot I get the 'no command'.. on tring to flash it allows me to see the device and reboot the bootloader BUT then it will not respond to the cmd fastboot devices. when I try fastboot flashing lock it just says <waiting for device>
Any help? !
Billy
Click to expand...
Click to collapse
I'm confused about "sits unlocked" and if this means you're stuck on the unlocked bootloader warning screen. If the phone hangs you're better off keeping the bootloader unlocked until that problem is sorted out. If it's starting, on the other hand...
Waiting for device means fastboot isn't communicating with the phone. Could be USB drivers. But if you flashed Android 11 from the same computer, drivers were working then, right?
In Developer options make sure USB debugging is enabled. While there, and while the bootloader is still unlocked, make sure OEM unlock is in the On position; it will flip back to Off when the bootloader is locked again.
Use Platform Tools 33.0.3 when trouble shooting USB to avoid trouble shooting Platform Tools 34.x.x.
As long as you get serial number output from commands adb devices and fastboot devices, fastboot flashing lock should work to re-lock the bootloader. Remember to finalize locking with the phone buttons.
Thank you both is was indeed the USB driver that needed the google update... All is well! thanks