I've been following the official Sony method to unlock the bootloader, you can see that procedure here. I have downloaded and installed the SDK Manager, then replaced the fastboot driver for Sony phones like they say, then I can also successfully put my phone into fastboot and my computer also recognizes it as "S1Boot Fastboot" but when I try to update the driver to point it to use the driver supplied to the SDK, I get this message when trying to install it (in the driver error.png). I'm not sure if it's trying to say that it won't work or something. So I proceeded to the command prompt stage (that's in cmd1.png) and entered fastboot. That worked. Then I entered fastboot devices and get a new empty line, whereas I'm supposed to get some text returned (see cmd2.png). Trying to enter the command to unlock bootloader after that doesn't seem to be doing anything (see cmd3.png).
So, anybody have any suggestions?
Update: It looks like the fault is becuase the Fastboot drivers aren't being accepted by W10... I've put the files on a USB and gonna try on the old ****ty computer... it's a dual boot so if neither W7SP1 nor W10 work I'll just resort to Linux Ubuntu. Why has it got to be so hard?
You need to disable driver signature verification in advanced setting in order to install drivers on Windows 8.1 so maybe it's same in w10.
Good Luck.
Xperia M2 D2303 on K.K. 4.4.4
Related
hello,
I'm hoping someone here can help me sort out my current problem.
I've been trying to root so I can install the latest ICS port, but having problems at the Fastboot screen.
I apologize in advance if some of the references/names I'm using are incorrect.
So, I had originally unlocked my Nexus S sometime early this year. When I restart the phone, the "unlocked" lock picture shows up under the "Google" words, and when I go into fastboot mode, the Lock State is Unlocked.
I'm running 2.3.6 right now on the Tmobile version of the phone.
When the phone is on (not in fastboot mode), I can execute ADB commands and the device is recognized. As soon as I go into fastboot it isn't.
I'm running 64bit Win 7, and I have gone through the various threads that have listed this issue, and installed PDA Net drivers and still there is no solution.
In Fastboot mode, while connected to computer under device manager, it shows up under Universal Serial Bus Controllers as an Unknown Device... I'm unable to update any drivers for it, and even when I try to manually update the drivers by going to the PDANet drivers it does not allow it.
When the phone is on in regular mode in device manager it shows up as Android Phone and within that it has a listing called Android Composite ADB Interface.
As mentioned above, when phone on in regular mode everything is detected.
I installed clockwork app from market, assuming that the phone was "rooted" based on the "unlock state" in fastboot mode, but it immediately says that phone needs to be rooted because it was unable to find SuperUser file etc etc.
I've spent the better part of a few days trying to figure this out by checking all sorts of links, but I haven't found a solution. The main issue is that the phone is not being recognized when in fastboot mode when connected by USB. And I'm unable to install the proper drivers for fastboot mode.
Hopefully this makes sense, and someone can provide some insight.
Thanks in advance!
I'm not positive about this but couldn't you adb push the su binary and apk? I don't own the Nexus but I would think since its unlocked you could just push the files. If this would work I would think it's just a temporary solution to allow superuser permission. As I understand it, fastboot is the preferred method for the Nexus.
Sent from my PG06100 using Tapatalk
Did you try a fastboot command like fastboot devices?
Don't know if this applies to you but I had a similar sounding problem when trying to root my Nexus S where everytime I booted into fastboot mode I had an error message at the bottom of the screen saying something like 'fastboot status-fail Invalid command' and so I couldn't use any fastboot functions.
To get around it I used this one-click root . For some reason I got an error message halfway through for whatever reason and it wouldn't complete the root for me but it booted me into fastboot without receiving the error message and then once I was in I went and rooted manually.
The CWM is out of date on that site though (possibly the super-user zip too) so I replaced them with the latest versions and popped it in my dropbox for you, if you wanna try it out.
http://dl.dropbox.com/u/47770734/One-Click-Nexus-S.zip
Edit: just had a little look through the bat script and the initial commands that got me into fastboot properly is (with your phone in debugging mode):
adb start-server
adb reboot bootloader
Click to expand...
Click to collapse
So you could try that first if you wanna go through manually.
Know that you can't run adb command while in fastboot mode. Boot into your CWM and then you can start an adb shell and you'll be able to push all the files you want and execute all the commands you need.
Fastboot mode is for running fastboot indeed. Try 'fastboot devices' while you're in the bootloader and see if devices pop up. If not, you really have to figure out your drivers issue. Maybe remove the device completely from your PC (including driver files) and reinstall it using the PDAnet drivers.
Greetz
I have a Sony Xperia Z3 model D6653 with Android 4.4.4 build 23.0.1.A.1.49, I tried to unlock the boot loader at the Sony website, It went al right till the part when I need to run cmd at the platform-tools folder (from sdk bundle), when I write "fastboot devices" the cmd don't respond me with anything, it just appears another line to enter a command again
- Installed the Google USB Driver, Android 4.4W.2 and Android 4.4.2 SDKs (don't know why there is not for 4.4.4)
- USB Debugging Mode: ON
- Fastboot mode (blue led at the phone corner) successful
I think that this normally happens when the PC dont detect the device
I'm stuck at this phase, please someone help me, thanks!
docs.google
.com/file/d/0B31eiZiEHpNFMGgwVnBMWXBQVjQ/edit?pli=1
xda didn't allow me for posting a photo url so I put it separated
Use the minimal adb and fastboot set up, that's a lot easier
http://d-h.st/zwu
If nothing here works, get the flashtool drivers for the z3. Works like a charm. Also, you should probably TA backup, if you haven't already.
I think it didn't worked for me,the thing is that I need to unlock bootloader to put root in the device
http://forum.xda-developers.com/z3/development/root-stock-kernel-twrp-v01-test-28-09-t2889794
https://drive.google.com/open?id=0B31eiZiEHpNFSnhzdGs1TU5pc00&authuser=0
dan_729 said:
I think it didn't worked for me,the thing is that I need to unlock bootloader to put root in the device
http://forum.xda-developers.com/z3/development/root-stock-kernel-twrp-v01-test-28-09-t2889794
https://drive.google.com/open?id=0B31eiZiEHpNFSnhzdGs1TU5pc00&authuser=0
Click to expand...
Click to collapse
You can root without unlocking.
Search XDA.
As mentioned, I need to go back to stock in order to unlock my phone but it has been a very long time since I have done anything techy to this phone. I know I needed an RUU file (which one?) and drivers but I also read about it failing in Windows 10. Can anyone advise how I can unlock my Rogers evita device?
I should also note that after a bit of research, I am trying to flash the RUU (using the command 'astboot flash zip PJ83IMG.zip' without quotes) but it just says 'waiting for devices' even though fastboot is red and says fastboot usb... Is this the result of having Windows 10 (drivers do not work)?
I have installed the drivers and HTC sync/adb from, the following:
http://forum.xda-developers.com/showthread.php?t=2588979
It is still not useful. I should also note when trying to sync via fastboot, in device manager I see under USB (device failed enumeration).
I know it's a few months later, but if it can help someone, here is how I got ADB-Fastboot (especially Fastboot) working under Windows 10 64bit.
I'm pretty sure I remember correctly doing just that, after messing for days without success.
If you're not successful, I might be forgetting something.
(of course, I cleaned my PC removing any HTC driver and any ADB-Fastboot solutions I had installed before doing the 3 steps below, also cleaning the Windows Registry)
1. Download and install latest HTC Sync Manager, then uninstall Sync Manager keeping only the drivers installed.
2. Find and Install latest Minimal ADB and Fastboot.
3. Download and install latest Java SE Development Kit 32bit version (even for Windows 10 64bit).
Connecting phone to PC was recognized, started Minimal adb-fastboot and then typed adb devices, worked fine.
Rebooted the phone to Bootloader then put it in fastboot usb mode and typed fastboot devices, worked fine.
So here's the background: I have a OnePlus 6, which I had rooted previously. I accidentally updated it without first patching the boot image, so it's not rooted now.
In an attempt to root it again, I need to use fastboot. However, whenever I use
adb reboot bootloader
it reboots the phone to fastboot mode, as expected, but then
fastboot devices
displays nothing. I find this extremely strange, because I have used fastboot commands before on both my windows machine and on my Linux machine (though I recently switched distros and have a new installation on there, so it may be missing some driver or something).
I have tried looking for any necessary drivers (I saw that sometimes usb drivers are different from fastboot drivers, but I don't know if that's the case regarding OnePlus) but after installing everything I found, it still doesn't work.
I have also tried running adb as root (on Linux) and as administrator (on Windows) but neither worked.
I tried to use Tool All In One to root it for me, but it seemed to run into the same problem. It wouldn't detect the phone in fastboot mode.
I'm absolutely baffled as to why this may be; Anyone know why this happens or what I may do to fix it?
I had the similar issue last week when adb command of fastboot devices would not identify the device. I used the fastboot ROM method to reflash the stock rom and everything worked fine afterwards including fastboot devices command identifying the device correctly. Needless to say, it would delete everything on your phone. Here is the link:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Good luck!!
Fastboot version
Update your fastboot, maybe it's an old version.
Also check your device manager and see if the phone is listed there. Sometimes it's necessary to disable driver signature check in Windows 10. Also install the driver before you use your commands - some users reported that for some reason the driver or connection is lost after windows reboot.
A) Check fastboot drivers/reinstall them (adb and fastboot use different drivers). You might want to check if there are unknown devices in your Windows device manager, or the name of the device once fastboot mode is engaged and you plug the cable
B) Plug it in another USB port (less likely to be the problem, since ADB actually works)
Hi! So I'm new in this forum and I'm trying to flash Xperia xa2 Ultra H3223 but had two problems, first I try flashing with Flashtool but no matter what it said "no partition delivery" or something "yes to continue", found some forum and said something about copying file 50.2.fsc and manually sync but again, clicked and nothing happened. Then I installed Emma but the only firmware was from the US (I'm from Mexico) and was a custom old version 50.1 with no other option. Finally, I just installed Newflasher, follow the instructions and nothing, just this:
"ERROR: TIMEOUT: failed with error code 997 as follows:
Se estß ejecutando la operaci¾n de E/S superpuesta.
- Error write! Need nBytes: 0x18 but done: 0x0
nBytes[0x0]:
- Error writing command getvar:max-download-size!
End. You can disconnect your device when you close newflasher.exe"
I've done everything, followed every tutorial and nothing seems to work.
By the way, I'm trying to flash firmware 50.2A.3.22, last year my phone bricked and the only thing I found was firmware Commercial and Journalists wich worked well but now I want to try other version and then LineageOs but guess I'll have to wait.
Don't know what I'm doing wrong, if I turn on my phone works perfect and nothing been erased.
My device is bootloader unlocked and no root.
Please let me know if you need to know something else, I'm not desperate but was kind of excited to try Lineage
Thanks!
I had the same problem with my H3113.
While I had installed flashtool and the drivers that come with it, it seems like they are too old for the XA2. They are from 2014.
What I had to do was get flashtool from the Sony website and open up the .exe with 7-Zip:
https://developer.sony.com/develop/open-devices/get-started/flash-tool
Inside of that is the file Sony_Mobile_Software_Update_Drivers_x64_Setup.exe - this one installs a driver from 2017.
After a reboot, flashing with Newflasher worked. What a damn pain!
I had the same problem and can confirm it works. I wish I saw this comment earlier.
If you flash with flashtool will it relock bootloader?
I am running Windows 10 Pro v. 21H1 and also have a Sony H3223.
I am trying to install the latest plain LineageOS on the phone for which is still supported. The H3223 is unlocked so there are a variety of guides for different flashing projects.
LineageOS wiki suggests installing a universal ADB driver which sadly does not apply for this phone. So I then took a peek at SailfishOS and their flashing guide... incidentally, they specify the use of Sony's Xperia X driver. This forum has a thread suggesting the use of Sony's Xperia XZ2 driver.
SailfishOS was specifying the XZ2 driver as well until they updated their guide for Windows 21H1.
I have tried to install both drivers in alteration—both times I uninstalled everything Android via safe mode—and both drivers will not properly install. I get the icon with the yellow triangle badge in my Device Manager list for 5 seconds but then it changes immediately to the questions mark badge and is only visible after showing hidden devices. This is true even while the phone is plugged in.
The phone is being connected via the included USB cable and is being plugged into a USB 2.0 port on my PC.
The phone when connected does get picked up by Windows and I get listings in other places under Device Manager. ADB sees my phone when I run any adb commands but booting into fastboot mode makes the above happen every time.
In other words, when I connect the phone to my PC, Windows installs some driver from who knows where. At this point, adb commands work but fastboot commands don't work. After this, I uninstall the stuff Windows sets up and I boot the phone into fastboot mode only. When this happens, Windows only shows an Android listing under Device Manager for hidden devices. This is the same device that is designated for the driver update in any guide I find... so at this point I have tried updating this object with the Xperia X and Xperia XZ2 drivers. The Sony object that's supposed to get added to the device tree is never added an instead it's as if nothing happened.
I have followed both the LineageOS guide and SailfishOS guide and I have no clue why Windows will not update the driver. There is nothing complicated about either guides... as I said, adb commands work but that is without me installing any driver and Windows does stuff. The only time I see what I'm supposed to see is when all drivers are uninstalled and I connect the phone to my PC while it's going into fastboot mode. However, Windows will not properly see the phone in fastboot mode due to the driver not being applied.