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.
Related
Hi!
I've been trying to flash my Xperia Mini with Cyanogenmod 9, but I'm stuck at step 6 under Flashing CyanogenMod in the Xperia Mini full guide. (Would post link, but as I do not have 10 posts, I can't. :crying: )
I've followed through the entire guide, successfully unlocked the bootloader and so on. However, after step 5 (Volume up + connect to computer = blue LED, which should be correct according to the guide), the device will not appear in command prompt after typing "adb devices". However, it appears whenever the phone is on and connected to the PC (with USB debugging enabled).
I have tried everything from reinstalling drivers (from the official Sony website, Google USB drivers, the ones that are mentioned in the guide for use with CM flashing, etc.) to the whole process of reinstalling the Android SDK. I have tried googling around with no luck, despite finding tonnes of threads with people having the same problem. Anyone know what might be the problem?
Download Flashtool and connect the device in Fastboot mode (volume up while connecting usb). What happens? Flashtool reports a device in fastboot mode?
mihahn said:
Download Flashtool and connect the device in Fastboot mode (volume up while connecting usb). What happens? Flashtool reports a device in fastboot mode?
Click to expand...
Click to collapse
It appears in DooMLoRD's "Get Device Info" for some reason. What should I do here? Proceed to flash using Flashtool through "Select kernel to Flash"?
*EDIT*
I got things working! Installed it through recovery and everything is working fine! Thanks!
I bricked my opx I was able to bring it to life but the ****ty recovery doesn't let me flash anything so I am stuck no OS and boot loader locked and my computer isn't recognizing the dam thing I have installed SDK tools and google USB drivers but for some reason I am not able to get the Dan thing to connect right when I try via adb sideload it starts then the phone says fail...... Please help I am love this device and brand but I am getting really mad I am about a week in to trying to fix this but no luck I am using windows 10 also
Sorry to say, but you gotta follow this thread.
[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus X
Since you may ignore the other thread you started or it may get deleted I'll copypasta here:
We can try to unlock the bootloader as it is now, but that doesn't usually work unless you checked "OEM Bootloader Unlock" in the system settings before the device was bricked. Hindsight is 20/20 but as a word of advice for the future, never ever mess with a device unless you know the bootloader is unlocked or have made it possible to unlock it later without the OS. It also doesn't void the warranty on OnePlus devices to do so.
So first things first, the recovery will normally only flash the stock ROM as provided by OnePlus. You can download that file from here: http://downloads.oneplus.net/2016-04...xygenOS_2.2.1/. For future reference, when the bootloader on a device is locked the bootloader will not boot any software that isn't complete stock. If you try and change the OS or Recovery and it's not stock, the bootloader will not load it. This goes for any Android device.
If ADB sideload is working for you but hasn't been installing on the device (as-in, it sends the file but the device fails to install it) then you should be able to just sideload the zip file. It'll be slow though since it's about 780megs. If it doesn't send it then you can try using the ADB "push" command which is like copy and paste. You "push" the file from your computer to a folder on the device (you can see what folders are available using "adb shell" and then navigating with CD "change directory" and LS "list". If you can't find the sdcard you may have to mount it). Once again, it'll push slowly but once it does you should be able to install it from the internal memory.
If that works and it boots, go to Settings -> About Phone and tap the Build Number until it says you've enabled developer settings. Go to Settings -> Development and turn on "OEM Unlocking". Power the phone down. Hold the Power key and Volume Down until it shows the OnePlus logo and "Fastboot". I believe if you have the Android SDK you have the Fastboot program (it's commandline like ADB). Open CMD or Powershell and as long as it's the only device plugged into the computer you should be able to simply type "Fastboot oem unlock" and it will unlock the bootloader. Once again, it doesn't void your warranty.
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:
Hi guys I am having an interested issue,
I want to install custom rom in my phone
I have downloaded in depth test and applied for un depth test
my mobile do connect to computer when it prompt to select mod I do select file transfer and my mobile do connect to laptop
and it shows in "adb devices" but when it goes into bootloader mod my mobile gets disconnected I have done everything I could
I have install every possible driver i got from articles but non worked is it the issue with my windows 10 ? or driver issue I have spent my whole night on this but couldn't find the way
fastboot devices
0purple said:
fastboot devices
Click to expand...
Click to collapse
what does it mean ?
when i connect my phone it prompt me with this and usb debugging is on
i tried adb devices but it didn't showed anything but when i chose transfer file it do connect to the laptop and shows in adb devices
najam489 said:
what does it mean ?
Click to expand...
Click to collapse
Try it once you are in fastboot
wow its showing
najam489 said:
wow its showing
Click to expand...
Click to collapse
0purple said:
Try it once you are in fastboot
Click to expand...
Click to collapse
i have another problem now my device is showing with fastboot devices but my devices status is locked when i tried this command "fastboot flash recovery recovery.img" it didnt work i am follwing this article https://www.guidetoroot.com/root-realme-3-pro/
thank you for your help my bootloader wasn't unlock it is now thanks a lot
It appears your device's bootloader is locked. Try:
fastboot oem unlock
fastboot flashing unlock
If that doesn't help, search for a guide on how to unlock bootloader for your specific brand.
It also looks like don't really know what you are doing. Make sure you are following trusted guide. If no, I'll be happy to help.
0purple said:
It appears your device's bootloader is locked. Try:
fastboot oem unlock
fastboot flashing unlock
If that doesn't help, search for a guide on how to unlock bootloader for your specific brand.
It also looks like don't really know what you are doing. Make sure you are following trusted guide. If no, I'll be happy to help.
Click to expand...
Click to collapse
well i did installed custom roms few time but i dont know much, i did unlock bootloader now the problem is i do install custom recovery twrp and it do installed and rom manager shows that custom recovery is installed but pressing volume down + power button just shows fastboot logo and it restart my phone, and with command "
adb reboot bootloader" i am able to boot into fastboot mood and when i go to recovery from their it open stock recovery instead of twrp
Stolen from my guide:
7. Go into fastboot mode
8. fastboot flash recovery recovery.img
9. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
10. fastboot reboot recovery
12. Sometimes recovery doesn't want to stick as a permanent one. To test it, hold the power button and select "Reboot to recovery". If you reboot to TWRP, you can move on, but if you reboot to stock one, flash recovery using fastboot again and from recovery flash recovery again (sounds crazy, right?). I won't give you instructions on this, research it yourself. Make sure guide you will find is for your device and your recovery.
I just purchased a G8343 on eBay and have attempted to unlock the bootloader, but the OEM unlock command seems to merely hang every time I run it.
By sheer luck, the bootloader ended up unlocked, but when I try to flash recovery, the command also hangs—this time without leaving the recovery actually flashed.
I can't restore with Xperia Companion as the bootloader is unlocked and Flashtool doesn't work to flash the device. Sony's official Emma also appears to not want to work with the device, stating "No available services for this model"—presumably because the G8343 is not listed on the officially supported devices for Sony's "Open Devices". I've even tried newflasher but that times out in fastboot as well.
What do?
To flash the recovery, make sure it is powered off and UNPLUGGED. Then plug in the phone while holding the Volume UP button. You should see a blue LED light.
Then check windows device manager and make sure to install the Android Bootloader drivers are installed. Then you can freely use "fastboot flash recovery twrp-xxxxx.img" easily.
You can not flash recoveries the same way you use Newflasher, since that uses the flashmode and not fastboot.