My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
I suspect that it is a USB problem at one end or another.
If I connect up the phone to the PC using the original lead I can find it using adb devices and the device is showing up as error free "Sony sa0113 ADB Interface Driver" in Windows 10 device manager.
However the phone isn't charging and I can't get it into Fastboot by holding the up vol key and plugging in the USB lead.
I can get a black screen with the blue led by running adb reboot bootloader and the phone is recognised from fastboot devices but when I try to unlock the bootloader I get an error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0fce oem unlock 0xB4D9AxxxxC359F2C
...
FAILED (remote: Command did not succeed)
finished. total time: 0.042s
Any help appreciated.
PhilG57 said:
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
I suspect that it is a USB problem at one end or another.
If I connect up the phone to the PC using the original lead I can find it using adb devices and the device is showing up as error free "Sony sa0113 ADB Interface Driver" in Windows 10 device manager.
However the phone isn't charging and I can't get it into Fastboot by holding the up vol key and plugging in the USB lead or by running adb reboot fastboot
If feels like I haven't go the fastboot USB drivers but I can't see how or where I can add them.
Any help appreciated.
Click to expand...
Click to collapse
Disable driver signature enforcement then reinstall sony drivers
tapiwasam said:
Disable driver signature enforcement then reinstall sony drivers
Click to expand...
Click to collapse
Thanks. I think I am OK there because I accepted the drivers from an unverified source during installation.
Also I can see the phone with both adb devices and fastboot devices
However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led.
adb reboot bootloader just goes into bootloader mode and not fastboot mode which is needed to unlock it. Go directly into fastboot by typing adb reboot fastboot
Then when your phone led is flashing blue, run your fastboot "oem unlock" command.
Saw now that you already tried that sorry about that.
Tried running cmd with admin privileges to see if that shows any difference?
Also from sony:
Please note! It will only be possible to unlock the boot loader for certain releases. You can check if it is possible to unlock the boot loader of your device in the service menu by following the steps below:
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
Click to expand...
Click to collapse
PhilG57 said:
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
.... snip....
Click to expand...
Click to collapse
You don't need to unlock your bootloader to simply downgrade to official MM! Just use flashtool to flash the appropriate MM ftf. There are plenty guides available on XDA and elsewhere.
I'm lost in your explanation.
You wanted to unlock your bootloader to be able to downgrade your phone? That's right? And it's fine to me, but you don't need to do that if you don't feel like. Unlocking your bootloader is nog necessary to downgrade to MM via flashtool.
So you tried to unlock your bootloader. But what you write what happened afterwards is completely unclear to me, because it contradicts itself.
-->> "Also I can see the phone with both adb devices and fastboot devices"
Fine. This means your connected with your phone and fastbook recognizes your phone. So bootloader is unlocked and software to control that works fine.
-->> "However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led."
Fine, so you unlocked your bootloader, and rebooted in fastboot.
-->> Obviously. It's an unlocked bootloader, you can double unlock it or something like that. You can relock it if you want (which doesn't make any difference for what you want to do) but that's a different method.
Is there any reason that you absolutely need to a second method to enter fastboot mode? Or any fastboot mode? It could be possible with another kernel, but I don't see the point to flash another kernel. I would just leave it like it is.
PhilG57 said:
Thanks. I think I am OK there because I accepted the drivers from an unverified source during installation.
Also I can see the phone with both adb devices and fastboot devices
However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led.
Click to expand...
Click to collapse
that is notmal behaviour, that is fastboot mode, indicated by that blue LED
Thanks for the clarification that I don't need to unlock the bootloader to downgrade using flashtool. What I didn't say was that I couldn't reinstall Nougat using the Sony tool software restore option or get anywhere with flashtool because the phone won't go into the blue led mode by inserting the USB and holding the up vol button. I did try running flashtool in one window and the command line tools in another with the idea of running flashtool first and then unplugging the phone and replugging it to use command line to get the blue LED state, but that doesn't work because the command line tools can't see the phone once flashtool is running and has addressed the phone.
From what i read, i assume you are on nougat and want to go back to MM, right?
So you would need flashmode instead of fastboot mode.
You get there with holding Vol down button and plugging in USB cable on turned off phone.
Flashmode also shows a green notification light instead of the blue one.
If you having Problems to get there, please check following:
make sure to have latest version of flashtool installed http://www.flashtool.net/downloads.php
install drivers from your flashtool\drivers folder
don't use an USB 3.0 port or cable(have heard of some people having trouble with)
PhilG57 said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0fce oem unlock 0xB4D9AxxxxC359F2C
...
FAILED (remote: Command did not succeed) <- this
finished. total time: 0.042s
Any help appreciated.
Click to expand...
Click to collapse
OP, I had the exact same problem as you. At the time I tried absolutely everything but never found the culprit. So after several months I actually succeeded today
This is the guide I followed - https://forum.xda-developers.com/z5-compact/general/guide-how-to-root-z5c-painful-using-t3549388 and it worked perfectly.
A few pointers:
- Go to the service menu (*#*#SERVICE#*#*) before you begin, before you turn OEM Unlocking ON from Dev Options .
- Take note of what it says in Configuration and Firmware.
- Now enable OEM Unlocking and take note again, it should say stuff like Model Number: Unknown and other unknown stuff.
- Reboot - IMPORTANT.
- Use the guide I gave you and you will be fine, it took me ages to find a solution but now I'm on MM and rooted
Hope I helped :fingers-crossed::fingers-crossed::fingers-crossed:
Related
Hi there,
I have a problem that i suspect others may have, i did my searching on google and on xda but found nothing so i have no other choice but to post. I am trying to fastboot flash a prerooted .67 firmware, i put my phone into fastboot and connected the usb cable, the led STAYS blue that seems to be fine(i have installed fastboot drivers using flashtool /drivers directory), i type in the fastboot command to flash it and it just sticks at "waiting for device".
Any ideas?
Thanks
What happens when you type:
fastboot.exe -i 0x0fce getvar version
Also:
1. Disable any antivirus
2. reboot your PC
3. Change to another USB port
4. Make sure the .img is in the same folder as the fastboot.exe
Try fastbooting an official firmware instead if that works then I believe you have encountered the 'bug' in the bootloader that is currently stopping any custom roms
unrealboot1 said:
Hi there,
I have a problem that i suspect others may have, i did my searching on google and on xda but found nothing so i have no other choice but to post. I am trying to fastboot flash a prerooted .67 firmware, i put my phone into fastboot and connected the usb cable, the led STAYS blue that seems to be fine(i have installed fastboot drivers using flashtool /drivers directory), i type in the fastboot command to flash it and it just sticks at "waiting for device".
Any ideas?
Thanks
Click to expand...
Click to collapse
Hi,
you know that every smartphone has a flash and a fast boot Feature ?
Some Smartphone, look´s like Sony, use:
Speaker UP Button and USB Connect for Fastboot
(by Sony the Home Button lights blue)
and
Speaker Down Button and USB Connect for Flash
(by Sony the Home Button lights green)
For Fastboot.exe ........ xy.img must be use the Fastboot
Feature.
In first using Fastboot.exe, after Phone Connect you must
wait that the PC find all Drivers.
If Fastboot doesn´t work again, maybe you need "SDK Android"
and "Google SDK Driver"... will find over Net.
Doesn´t work again, the use "Flashtool.exe" Methode and
convert the xy.xy Firmware to xy.ftf for Flashtool use.
Onex1
my version is 0.5
i tried all of this except the last point of Onex1. Nothing works still sticks at waiting for device. Also havent restarted my pc i will try that soon but i think that might be a long shot.
Also my device is recognised as an adb device if that helps.
Any ideas guys? I have been trying but now im all spent. My xperia s is unlocked and factory bootloader unlocked if that helps
I know this thread is really old, but I was having this same issue and it was fixed by using a newer version of the Android SDK. So if you're having problems, try updating!
U must enable USB debugging mode
Send from Xperia U
i have the same issue
power on off button is broke
i can boot to recovery but i cant select to flash anything because of the button its not working
adb works for me too because its recognized when i write adb devices but when i write fastboot devices nothing happens and everything i do it says waiting for device
anyway PrakashGD, he said adb is working, that means USB Debugging is ON, if it was off adb would've not worked duh
Ensure fastboot driver is installed
Sent from my ST25i using xda premium
Hey,
I'm currently trying to root my Sony Xperia Z2 but I can't get past the unlockbootloader stage.
I use the instructions given at Sony Developer World after entering my IMEI and all that, but one step don't work for me:
"3. On your Xperia™ Z2, press the Volume up button at the same time as you connect the other end of the USB-cable. For Windows users, when asked for a driver, point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file."
I connect the phone and it lights up blue as it should but computer is not asking me for any drivers. And seem I have to do this step as the next step is:
"4. When your device is connected, open a command window on your computer and go to the platform-tools folder within the Android SDK folder and type in ">fastboot devices" "
And if I type "fastboot devices" after the ">" nothing happens. If I try it with ">fastboot devices" the cmd.exe goes "The system cannot find message text for message number in the message file for Application."
Thanks for any help!
Andreas
I recomend using flashtool instead, also backup your TA partition because your warrent is voided by your bootloader being unlocked
Flashtool.net < it has a drivers.exe run in the drivers folder, run that first
I was never able to unlock my bootloader via sonys instructions across few devices, flashtool alwaus has worked for me
Thanks!
Gonna try it out but wondering if I should backup the TA Partition before or after the fastboot?
For example at this thread it states first step as "root" which feels more like the last step.
http://forum.xda-developers.com/xpe.../tutorial-backup-ta-partition-to-drm-t2234627
AndreasWY said:
Thanks!
Gonna try it out but wondering if I should backup the TA Partition before or after the fastboot?
For example at this thread it states first step as "root" which feels more like the last step.
http://forum.xda-developers.com/xpe.../tutorial-backup-ta-partition-to-drm-t2234627
Click to expand...
Click to collapse
Before!
Unlocking the bootloader deletes your DRM keys so backing up your TA after you have unlocked the bootloader would be pointless.
The order you need to do things is...
Root (this allows you to backup your TA)
Backup your TA
Unlock your bootloader
Flash a flash a custom recovery
Flash ROMs to your heart's content
If you want to go back to stock (including restoring your DRM keys)...
Flash a stock FTF using flashtool
Lock the bootloader
Root
Restore your backed up TA
Flash the same FTF using flashtool (to remove root)
Hey!
I have the same problem here, nothing happens when i write fastboot devices while trying to unlock my device (but adb is working, in fact, i got into bootloader mode using adb).
I tried also using flashtool, but it says my device isn't able to be unlocked (but checking it in my z2 following Sony 's website steps it says: UNLOCK BOOTLOADER:YES).
Thanks!
Daniel30 said:
Hey!
I have the same problem here, nothing happens when i write fastboot devices while trying to unlock my device (but adb is working, in fact, i got into bootloader mode using adb).
I tried also using flashtool, but it says my device isn't able to be unlocked (but checking it in my z2 following Sony 's website steps it says: UNLOCK BOOTLOADER:YES).
Thanks!
Click to expand...
Click to collapse
If you aren't getting device ID on fastboot devices then either your device isn't in fastboot mode or your pc isn't detecting it, check that you have the correct drivers installed, flashtool can do it for you, and try again.
ghostofcain said:
If you aren't getting device ID on fastboot devices then either your device isn't in fastboot mode or your pc isn't detecting it, check that you have the correct drivers installed, flashtool can do it for you, and try again.
Click to expand...
Click to collapse
Thanks for helping!
That was the first i though, but if i can use adb, drivers should be okay, or at least that's what it should be.
And about not being in fastboot mode, i got into it through adb, and my notification led was blue, as it should be when the device is in fastboot mode.
Thanks again!
If I'm not mistaken fastboot and adb drivers are different, at least they are on htc devices. If fastboot devices returns no results it's because the pc can't communicate with any fastboot devices connected to it, end of.
I have the Huawei Ascend Y300-0151 and am trying to unlock the bootloader, in which I cannot get through their website because it's really buggy and won't accept my information.
So these are the steps I've taken:
- Download SDK Manager and install platform-tools and Google USB Driver
- Boot my phone up and connect to the PC
- I can run the command 'adb devices' and my device shows with a unique ID.
- Boot my phone into recovery/download mode (purple screen).
- Connect my phone, the PC detects it.
- However, when I run the command 'fastboot devices', nothing shows up.
Yes, I have installed a driver for my device and it's now showing as Android Bootloader Interface.
I've run out of ideas and have been googling for answers for a very long time, but to no avail.
Any help would be greatly appreciated, thanks!
illquo said:
I have the Huawei Ascend Y300-0151 and am trying to unlock the bootloader, in which I cannot get through their website because it's really buggy and won't accept my information.
So these are the steps I've taken:
- Download SDK Manager and install platform-tools and Google USB Driver
- Boot my phone up and connect to the PC
- I can run the command 'adb devices' and my device shows with a unique ID.
- Boot my phone into recovery/download mode (purple screen).
- Connect my phone, the PC detects it.
- However, when I run the command 'fastboot devices', nothing shows up.
Yes, I have installed a driver for my device and it's now showing as Android Bootloader Interface.
I've run out of ideas and have been googling for answers for a very long time, but to no avail.
Any help would be greatly appreciated, thanks!
Click to expand...
Click to collapse
Given that your attempting to unlock the bootloader of your Huawei device, you should probably send an email to Huawei support requesting for your bootloader unlock code (thats what I did and they replied asking for my device information, and I gave it to them to which I then got my unlock code). For ADB to work you need to boot into fastboot mode, not recovery, then simply use the bootloader unlock code with the following command in cmd: fastboot oem unlock <insert your code here>
And then your done. Be cautious when unlocking your bootloader as you should make sure you have your developer options enabled and the "allow bootloader to be unlocked" option enabled as well.
LaserOP said:
Given that your attempting to unlock the bootloader of your Huawei device, you should probably send an email to Huawei support requesting for your bootloader unlock code (thats what I did and they replied asking for my device information, and I gave it to them to which I then got my unlock code). For ADB to work you need to boot into fastboot mode, not recovery, then simply use the bootloader unlock code with the following command in cmd: fastboot oem unlock <insert your code here>
And then your done. Be cautious when unlocking your bootloader as you should make sure you have your developer options enabled and the "allow bootloader to be unlocked" option enabled as well.
Click to expand...
Click to collapse
I have e-mailed them 2 weeks ago and they are not replying. You're meant to do it through their website, but as I've said, I supply the correct information and it either re-directs to a page that is not there or says I am not entering my information correctly when I've done it over and over again.
The purple screen is fastboot mode isn't it? Because that's the screen I'm entering the commands in, but it's not showing up. I cannot enter in a code for fastboot oem unlock because my device will not be recognized by fastboot in the first place.
So before I am to unlock my bootloader, I'm trying to get my device recognized by fastboot.
illquo said:
I have e-mailed them 2 weeks ago and they are not replying. You're meant to do it through their website, but as I've said, I supply the correct information and it either re-directs to a page that is not there or says I am not entering my information correctly when I've done it over and over again.
The purple screen is fastboot mode isn't it? Because that's the screen I'm entering the commands in, but it's not showing up. I cannot enter in a code for fastboot oem unlock because my device will not be recognized by fastboot in the first place.
So before I am to unlock my bootloader, I'm trying to get my device recognized by fastboot.
Click to expand...
Click to collapse
You can send them an email to get the unlock code, trust me, thats what I did. Maybe try contacting them via their support section of their site if you didn't do so last time.
By the "purple screen" do you mean the screen with options such as "HBOOT", "Fastboot", "Reboot" etc.? The "fastboot devices" command should work if it is recognised by the command "adb devices"
LaserOP said:
You can send them an email to get the unlock code, trust me, thats what I did. Maybe try contacting them via their support section of their site if you didn't do so last time.
By the "purple screen" do you mean the screen with options such as "HBOOT", "Fastboot", "Reboot" etc.? The "fastboot devices" command should work if it is recognised by the command "adb devices"
Click to expand...
Click to collapse
I'll give it a go again, thanks.
By purple screen, I mean holding down the power button and both volume control buttons and the screen boots into a purple screen. Just a purple screen, that's it. I can boot into two other modes by holding down the power button and the volume up button and another by holding the power button and volume down button. I don't have a boot mode that displays any options as you've listed above.
EDIT: I'm in fastboot mode now! It was the mode where you hold down the power button and volume down button. Hahaha. I'll let you know how I get on with unlocking the bootloader. Thanks for your help
No problem, if you found my replies helpful please press the thanks button! It is much appreciated!
So I just purchased this phone and am trying to follow the instructions on the Sony site. The rooting status in my service menu says my devices should be able to be unlocked.
Device is on android 13 on latest update, OEM unlock and USB debugging are both enabled.
I downloaded the usb drivers and the platform tools from the Sony site.
I opened a command prompt in the platform tools folder and when I run fastboot devices I get a response
When I run the command with my unlock code, I get the error
FAILED (remote: Command not supported in default implementation)
I tried to go to device manager to update the drivers, however when I do that it says the best driver is already installed.
I read in another thread to try to boot into the bootloader rather than fastboot. When I select reboot to bootloader the device seemingly shuts off.
EDIT: OK, I'm dumb and was in fastbootd mode rather than fastboot. I've now entered fastboot correctly (holding volume up while I plug it in, getting a black screen and a blue LED), updated the drivers correctly, and am now getting the error that the device is already unlocked. Now I guess I just need to verify that it is indeed unlocked, anyone have some advice on that?
EDIT 2: OK it seems to be going through the unlock process despite that error rather than the expected confirmation. After a few reboots it is now giving me the setup process again so I hope it worked. Leaving thread up for others who have the same issue to stumble accross.
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.