I'm trying to unlock my bootloader - following the instructions on the Sony website... and a bunch of other websites outlining similar processes.
NOTE: Experienced at flashing ROMs / rooting for other devices...
When I boot into fastboot mode I get nothing displayed on my phone - I'm sure it is in fastboot mode as the notification led turns blue as expected. However any commands I send (fastboot -I 0x0fce getvars version) all end up with <waiting for device>
I've tried putting it into fastboot mode by 2 methods:
1) Phone off, hold down 'Vol Up' and plug in USB cable
2) Running adb and sending the "reboot bootloader" command.
Both these result in the notification led turning blue as expected, but no display on the phone.
I think the drivers are correct as I can connect and see the device from adb - also tried other drivers and 2 separate machines just to be sure... so not sure what's going on.
Questions:
1. Should there be something displayed on the phone when it's in fastboot mode ?
2. Is the driver for fastboot different from the adb driver ?
3. Any pointers as to where I am going wrong, or tips on troubleshooting further ?
Thanks .. Ken
fastboot driver is different than the adb driver. Look in device manager to see if it's being installed properly
shutdown.exe /r /o /f /t 00
enter this command at the command prompt, then enter and confirm the visit unless the Advanced and uncheck the startup method and verify the driver signature then the continuation
Wysłane z mojego D6503 przy użyciu Tapatalka
---------- Post added at 11:32 AM ---------- Previous post was at 11:30 AM ----------
shutdown.exe /r /o /f /t 00*
enter this command at the command prompt, then enter and confirm the visit unless the Advanced and uncheck the startup method and verify the driver signature then the continuation
Wysłane z mojego D6503 przy użyciu Tapatalka
My screen is black in fastboot mode. Had no problem unlocking it.
Have you installed the fastboot drivers?
Sendt fra min D6503
Related
I'm having issues attempting to unlock the bootloader on my g5. I can boot into fastboot mode from the os. Once I'm in fastboot however the driver won't install in windows to allow me access to run the fastboot oem unlock command.
I've installed the correct LG G5 Driver set (LG United Mobile Driver) as far as I can tell. I've tried manually selecting the driver in windows. Everything works perfectly in debug mode in the os but once I've used the adb reboot bootloader command and it reboots, it goes off the radar and I can't do anything else.
I'm using the LG G5 T-Mobile edition H830 v10d.
Try running adb kill-server after doing adb reboot bootloader. Then do you get anything when you run fastboot devices?
Keep in mind, you'll need to have "Enable OEM Unlock" flipped in USB Debugging.
Also, if you're using the h830, you should post this in the tmobile specific forums.
Well got same problem here. Once in bootloader, i have the welcome to Fastboot Mode phone screen but i can't do anything using command prompt. Fastboot devices returns nothing attached.
Even pushing 10s power button does nothing. Have to pull out battery.
Don't understand.
Any help ?
Thanks.
WILMANS2M said:
Well got same problem here. Once in bootloader, i have the welcome to Fastboot Mode phone screen but i can't do anything using command prompt. Fastboot devices returns nothing attached.
Even pushing 10s power button does nothing. Have to pull out battery.
Don't understand.
Any help ?
Thanks.
Click to expand...
Click to collapse
Did you solve this? I have the same problem.
Yep. Had to install google sdk driver.
Envoyé de mon LG-H850 en utilisant Tapatalk
WILMANS2M said:
Yep. Had to install google sdk driver.
Envoyé de mon LG-H850 en utilisant Tapatalk
Click to expand...
Click to collapse
Just the Google USB drivers or the whole SDK? What version of Windows are you on?
Can u post a link to the download?
WILMANS2M said:
Yep. Had to install google sdk driver.
Envoyé de mon LG-H850 en utilisant Tapatalk
Click to expand...
Click to collapse
???
For anyone having the issue, I solved it as follows (on Windows 7):
You've used adb to reboot into fastboot, but fastboot isn't responding. "fastboot devices" in adb shows no devices.
1. Go to device manager
2. Look for a device called Other Device, or something similar. Expand that, you should see a device called Android with yellow exclamation a mark.
3. Right click the device, select Update Driver Software.
4. Select Browse my computer for driver sofware
5. Select Let me pick from a list....
6. In the column on the right, find something a driver that says Fastboot driver or something similar (I can't see it now that I've installed it).
7. Install that, go back to your command line interface, type fastboot devices to confirm you now have access.
I have the same problem with h850
I am trying to unlock the bootloader of my moto z xt1650-03, adb seems to find it, but issuing the" adb reboot bootloader" command simply turns the device off instead of opening the bootloader.
Fastboot does not recognize the device if I manually put it in bootloader by key combination.
USB debugging enabled. Oem unlocking enabled.
My device is devoloper edition which has markings on top right corner of the phone and "Motorola Confidential Property not for sale" also written.
http://cloud.tapatalk.com/s/58d220f1149f5/Screenshot_20170322-115628.png?
http://cloud.tapatalk.com/s/58d220c3b881f/Screenshot_20170322-115638.png?
Sent from my XT1650 using Tapatalk
And do I have the latest software update ?
NPL25.86-17-3
zohaibshafijutt said:
I am trying to unlock the bootloader of my moto z xt1650-03, adb seems to find it, but issuing the" adb reboot bootloader" command simply turns the device off instead of opening the bootloader.
Fastboot does not recognize the device if I manually put it in bootloader by key combination.
USB debugging enabled. Oem unlocking enabled.
My device is devoloper edition which has markings on top right corner of the phone and "Motorola Confidential Property not for sale" also written.
http://cloud.tapatalk.com/s/58d220f1149f5/Screenshot_20170322-115628.png?
http://cloud.tapatalk.com/s/58d220c3b881f/Screenshot_20170322-115638.png?
Click to expand...
Click to collapse
while that command should work, it's not the only way
power off, hold volume down button, power on
Sent from my sailfish using XDA Labs
Are you suggesting that I put it into bootloader through key combination you just told ?
Sent from my XT1650 using Tapatalk
I put my device in bootloader adb devices command does not work but fastboot devices command works. When I execute the command to unlock my bootloader"fastboot oem get_unlock_data, it gives error
* ... INFOunlock data:
INFOcid_get_cid_data: version 0 datablock
INFOfailed
OKAY [ *0.016s]
finished. *total time: 0.016s
Sent from my XT1650 using Tapatalk
And as I said my device is "prototype" so no official support to unlock my bootloader.
Sent from my XT1650 using Tapatalk
So my device is recognized when it's turned on but then I go to command prompt and click ADB reboot bootloader (enter). It just says waiting for device. If it's on and I click ADB devices in the command prompt it tells me the serial number and then says device. On the computer management it is recognized as a device it says the name Xperia XA Ultra. I tried to update the Google driver into ADB but that was a failed attempt. I couldn't quite understand what I was supposed to do there or really even follow the instructions because it kept telling me that I was unable to update drivers after I followed the instructions they gave me. I just kept getting an error message. So I'm wondering how do I solve this problem? I really would like to unlock my bootloader and I'm not even sure if it's going into fastboot. I got the notification after turning off the phone hold Volume Plus and plug it in it said of my computer that it was installing the fastboot drivers. I'm assuming it was in fastboot at that time even though I didn't get a blue light it just turned blue for a minute and then it was Green. It said it was installing fastboot drivers so I'm assuming it was in fastboot mode. This is a really tricky process I guess.
What windows do you have?
Also I would recommend you to Google how install fastboot on your Windows type.
Sent from my F3213 using xda premium
I have windows 10
Windows 10. Why would I need to install fastboot on Windows? Fastboot is on my Android device. I use ADB. Android debugging bridge is the bridge that goes between your operating system and fastboot the bootloader and Android and all of that in order to be able to communicate with the phone. Why would I need to install Fastboot on my windows? You sound like a customer service representative. I can't even talk to them anymore because they tried to get me to act like Chris Farley.
If you don't install fastboot on your computer you can't unlock bootloader you can't install custom recovery or root the phone!
Sent from my F3213 using xda premium
Hello,
Here is the link to the ADB Installer that contains all the files you need (ADB, Fastboot and Drivers). Download and following the screen information to install the program.
https://forum.xda-developers.com/showthread.php?t=2588979/
Thanks,
Danjuma
Hi there
please note that Windows 10 x64 blocks the installation of unsigned drivers. To be able to install them anyway you have to enter the Windows Test Mode. To do this you just have to run "bcdedit /set testsigning on" in an administrative command line and restart your computer afterwards. You'll see "Test Mode" at the bottom right corner of your desktop. To leave the testmode use "bcdedit /set testsigning off" and restart again.
Done all of this and it doesn't work...
You have to use drivers from Sony for Flashmode and use drivers included in Flashtool (C:\flashtool\drivers) for fastboot and ADB. No problem for me with Windows 10 64bits and don't need to use Test mode.
sony m4 aqua cant enter in flash mode solution ????
Plug your switched on phone into computer
Make sure you have usb unbugging selected on in developer's option's
Im on the assumption that you already have adb and fastboot installed
Open a command prompt window and on the command line write -- adb devices --
If all's good you should see your phones serial number.
If not then check your s1 driver's and your cable first.
Once that is all good on the command line write -- adb reboot bootloader ----
You will now notice that phone's Led has turned blue and your phone is now ready for fastboot command's
Remember that the command line is case sensitive.
Good Luck.
I'm at a total loss here...
phone has unlocking and USB debugging toggled on.
phone is not a US phone and unlocking is allowed.
phone goes into fastboot mode (by turning on while holding volume)
"fastboot devices" command returns my phone is in fastboot and connected
"fastboot oem unlock 0xPASSWORD" returns FAILED (remote: 'Command not supported in default implementation')
and fastboot: error: Command failed
I have no idea what to do or try from here.
If I try to flash an image i get:
FAILED (remote: 'Download is not allowed on locked devices')
so, defiantly still locked out of the bootloader
Try below steps
1. Ensure you have platform tools 33.x , 34 has issues.
2. Try to reboot to bootloader from pc.
adb reboot bootloader
3. Try running
fastboot flashing unlock unlockcode
Try it :
fastboot oem unlock
or
fastboot flashing unlock
SOLVED I am so happy. I'm on day 3 of trying to get the phone to bootload.
there is definitely a difference between going into fastboot through the phone itself and through adb commands on PC.
fastboot through the phone shows the drop down menu and no blue light illuminated on phone.
fastboot through adb phone is black screen with a blue light on right corner on the phone.
the windows drivers behave differently between the two. I am running windows 10. phone model XQ-CT72
steps that solved the issue. For anyone in the future.
I downloaded and used platform tools version 33.0.3 NOT version 34.
"adb reboot bootloader" used from windows PC
opened windows device manager found my "discovered device" and forced it to use the SONY driver downloaded from sonys website. It would not detect it on its own, or even use the SONY driver without me telling it to specifically. device manager> "andorid" > properties > update driver > browse computer for driver > installed sony driver
everything worked following these instructions here https://www.droidwin.com/unlock-bootloader-and-root-sony-xperia-1-iv/
alexriethmeier said:
There is definitely a difference between going into ...
Click to expand...
Click to collapse
fastboot, part of the android bootloader, abl
fastbootd, part of recovery
I had same issue and same solution fixed it what you showed and did. I was terrified, after investing so much money on this phone and not getting it unlocked.
You won't need to go through such hassle if you just use Linux VM (a Ubuntu distro will do). The driver works out of the box.