Have been trying to unlock bootloader on my xperia SP and having a lot of trouble with it. I can put it into fastboot mode, but only for about 10 seconds before it starts charging off my laptop and stops fastboot. I've tried searching the forums and elsewhere, but can't see anything about what might be going wrong for it to keep exiting fastboot. Is there any setting or step that isnt mentioned here:
http://forum.xda-developers.com/showthread.php?t=2354721
For reference, my laptop is running windows 8.1, im using usb 2.0, and my xperia is currently on 4.1.2 and I want to upgrade to 4.3. If there's anything else I forgot to mention, just say.
this work for me
scarletsmoke said:
Have been trying to unlock bootloader on my xperia SP and having a lot of trouble with it. I can put it into fastboot mode, but only for about 10 seconds before it starts charging off my laptop and stops fastboot. I've tried searching the forums and elsewhere, but can't see anything about what might be going wrong for it to keep exiting fastboot. Is there any setting or step that isnt mentioned here:
http://forum.xda-developers.com/showthread.php?t=2354721
For reference, my laptop is running windows 8.1, im using usb 2.0, and my xperia is currently on 4.1.2 and I want to upgrade to 4.3. If there's anything else I forgot to mention, just say.
Click to expand...
Click to collapse
hi, i had the same problem a while ago, you have to disable signature driver enforcement on windows 8.1 before you install the fastboot drivers
how to do this? i've found here: http://revryl.com/2013/08/06/install-unsigned-drivers/ (credits to: Denver Dias)
Related
Hello,
Ive Google play edition installed and TWRP recovery, S-off - I bought the phone on ebay and was going to sell it again but the guy wanted stock rom. So I checked this guide htc1guru.com/guides/return-stock-guide/] and started following it, it worked till flash RUU.exe and after that I received waiting for device. Now when I try fastboot command I always get waiting for device. I tried everything from reinstalling drivers, another ports, another cable but without luck. Any advice how to proceed and get the stock ROM ?
Thank you
tslid said:
Hello,
Ive Google play edition installed and TWRP recovery, S-off - I bought the phone on ebay and was going to sell it again but the guy wanted stock rom. So I checked this guide htc1guru.com/guides/return-stock-guide/] and started following it, it worked till flash RUU.exe and after that I received waiting for device. Now when I try fastboot command I always get waiting for device. I tried everything from reinstalling drivers, another ports, another cable but without luck. Any advice how to proceed and get the stock ROM ?
Thank you
Click to expand...
Click to collapse
my first guess is that you are using windows 8.1 with hboot 1.44? If yes then find a windows 7 computer.
alray said:
my first guess is that you are using windows 8.1 with hboot 1.44? If yes then find a windows 7 computer.
Click to expand...
Click to collapse
Yes, Windows 8.1 and I searched whole day for possible solutions however Im still nowhere.
When I enter in fastboot mode I get Unknown USB device - device failed enumeration and so on.
Is there any fix to this or just to get rid of damn Windows 8.1 ?
Regards and thank you for answer
tslid said:
Yes, Windows 8.1 and I searched whole day for possible solutions however Im still nowhere.
When I enter in fastboot mode I get Unknown USB device - device failed enumeration and so on.
Is there any fix to this or just to get rid of damn Windows 8.1 ?
Regards and thank you for answer
Click to expand...
Click to collapse
Simplest solution is to use windows 7, linux or macOS. Windows 8.1 will not work with hboot 1.44. There is a fix somewhere but I dont know, never tried myself.
Ok I need some help. As of right now my tab is dead, the only thing it does when powered on is loads to the Asus splash screen and that's all. I can not get it into Fastboot mode at all and Adb cant find it either. I have already tried Sp Flashtools to no avail. I have all the Vcom drivers installed, every where I searched the one driver that people talked about was the mtk6585 driver ( I think that's what it is ) , the one for me that popped up and went away really fast was a driver called CLOVERVIEW. So needless to say I cant get SP Flash tools to work, and without fastboot mode im really stuck. Ever since I first came across this site a few years back I have rooted, and put custom roms on countless devices, I would call myself an experienced flasher. Well this tab has me feeling like a real noob, I can not figure it out. So if someone can help me it would be greatly appreciated. Thank you XDA world.
Try this: http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466
It worked for me.
silviu74 said:
Try this: http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466
It worked for me.
Click to expand...
Click to collapse
Wont work for me. Like I said, I cant get into droidboot.
Downloading android studio and all sdk tools, hopefully something in this will help. I will post updates on any progress.
zMILWAUKEE said:
Downloading android studio and all sdk tools, hopefully something in this will help. I will post updates on any progress.
Click to expand...
Click to collapse
I just got myself into the same situation. If you can get to a point where CLOVERVIEW comes up, that can be fixed (I actually just added a howto to the general section). However, I don't know how to get out of the stuck splash screen, since it's an awkward medium between download and fastboot. I'm not even sure what I did to cause this; I had just flashed boot.img and splashscreen.img and issued a fastboot reboot-bootloader.
The device does indeed pop up in download mode for about a second while booting; doesn't seem long enough for a flash. I would really like to find out if there is any way to force this device to boot into download mode.
Hello guys,
Even though I am a member of this site for a few years, this is my second post.
Recently, I decided to root my HTC Desire 500. I am a newbie in this topic, ( even though I rooted 2-3 devices, but they were old, so I just used SuperOneClick or Z4Root) so I tried to google it, and found some pretty good guides, but I always faced problems. One guide what I was following is this one: http://forum.xda-developers.com/desire-500/general/how-to-root-install-cwm-twrp-install-t2804938
So first, I tried to unlock the bootloader. I headed to this site: http://www.htcdev.com/devcenter and followed the instructions. I installed the HTC sync as well. I turned off my phone, and launched the bootloader mode. The HTC sync popped up, and scanned my music, but in the left corner I saw a sign: No phone connected...
That was prety worrying for me, but after that, the Windows told me that it can't recognise the connected device. I continued anyway, downloaded the fastboot binary,but I got another error when I tried to run the "fastboot oem get_identifier_token" command, something like: the program can't launch because the AdbWinApi.dll is missing, then it just stopped working. I quickly grabbed the dll from the internet, and ran the command again, but I got another error message: <waiting for device>, and now I don't know how to continue. I tried plugging my phone in when it was turned on, and now everything recognised it, so somehow when it's turned off, the Windows can't identify it. USB debugging is turned on, and fastboot is turned off in the phone's settings. Some more info, that can be helpful: this is what I see in bootloader mode:
Code:
****LOCKED****
Z4U PVT SHIP S-ON RL
HBOOT-1.01.001
RADIO-14.08.36Q4.26
OS-1.10.401.3
eMMC-boot
Aug 1 2013,15:50:50.0
It's a single SIM version.
Maybe the android SDK is missing, as I later noticed, so I headed to this site: http://developer.android.com/sdk/index.html , and clicked on "Installing the SDK", but now I don't know which one should I install: http://i.gyazo.com/5aaf558bfceea91b15963ebaa2351368.png or maybe I have to download something from here? http://i.gyazo.com/221bab07354c3f60675cd3e492d15e65.png I have no idea...
As I told before, I am a beginner, so please be detailed when replying, and I am sorry for wasting your time guys if it's that easy, but I was unable to find the solution... I also have several other questions in this topic after solving the problem, so please stay in touch with me. Any help would be really appreciated.
even i faced the same prob...waiting to see if someone replies..
update: Hey bro, are you trying in windows 8 or 8.1? I was trying on the same. But now I tried with Windows 7 and it is successful. The issue here is when the phone is in fastboot mode windows 8 is unable to recognise the device. In windows 7 it does. try this,
Akhyll said:
even i faced the same prob...waiting to see if someone replies..
update: Hey bro, are you trying in windows 8 or 8.1? I was trying on the same. But now I tried with Windows 7 and it is successful. The issue here is when the phone is in fastboot mode windows 8 is unable to recognise the device. In windows 7 it does. try this,
Click to expand...
Click to collapse
I realised this as I tried to find a fix myself. Thanks for the update tho
Hello everybody
I'm having a problem. After ditching the first custom ROM (Pure Nexus) because Sygic App kept crashing, I wanted to go back to stock but noticed that I couldn't connect to my windows box via USB anymore. It would display the Nexus 6 device with an warning sign in device Manager. Since it had worked on stock it can't be a hardware issue.
So going stock through fastboot was out because no device was found. ADB also didn't find anything. So after going to LightROM, Sygic worked but I still can't connect via USB. The Nexus 6 is displayed in Windows Explorer but no storage underneath it. ADB still doesn't work and Wug's toolkit, as a consequence, can't work with the device either. I can't fiddle with USB options either, since LightROM doesn't pop up a USB notification and I just can't find the options in system settings.
So I'd like to flash via TWRP, which is installed, but for the life of me I can't find any of the TWRP flashable stock ROMs I see mentioned on the net. Also, there ought to be ZIP update packages since OTA doesn't work on rooted devices. Where can I find those?
Thank you
Marco2G said:
Hello everybody
I'm having a problem. After ditching the first custom ROM (Pure Nexus) because Sygic App kept crashing, I wanted to go back to stock but noticed that I couldn't connect to my windows box via USB anymore. It would display the Nexus 6 device with an warning sign in device Manager. Since it had worked on stock it can't be a hardware issue.
So going stock through fastboot was out because no device was found. ADB also didn't find anything. So after going to LightROM, Sygic worked but I still can't connect via USB. The Nexus 6 is displayed in Windows Explorer but no storage underneath it. ADB still doesn't work and Wug's toolkit, as a consequence, can't work with the device either. I can't fiddle with USB options either, since LightROM doesn't pop up a USB notification and I just can't find the options in system settings.
So I'd like to flash via TWRP, which is installed, but for the life of me I can't find any of the TWRP flashable stock ROMs I see mentioned on the net. Also, there ought to be ZIP update packages since OTA doesn't work on rooted devices. Where can I find those?
Thank you
Click to expand...
Click to collapse
If Fastboot cannot connect in the bootloader, it is nothing to do with the ROM. The ROM and bootloader are completely separate, so it is likely a USB hardware issue, or driver issue. Hardware could be PC Port, Nexus port or cable.
I recommend addressing your fastboot issue first rather than trying to work around it.
danarama said:
If Fastboot cannot connect in the bootloader, it is nothing to do with the ROM. The ROM and bootloader are completely separate, so it is likely a USB hardware issue, or driver issue. Hardware could be PC Port, Nexus port or cable.
I recommend addressing your fastboot issue first rather than trying to work around it.
Click to expand...
Click to collapse
I'm almost tempted to walk away from this whistling like I was never even here...
Even though I unlocked the device in fastboot, I completely forgot you'd have to boot into fastboot in order for that to work. As such I should have put this in the noob question thread. I do appologize for wasting your time so spectacularly.
Obviously, as soon as I did boot into fastboot, flashing stock worked like a charm.
Sorry 'bout that.
Marco2G said:
I'm almost tempted to walk away from this whistling like I was never even here...
Even though I unlocked the device in fastboot, I completely forgot you'd have to boot into fastboot in order for that to work. As such I should have put this in the noob question thread. I do appologize for wasting your time so spectacularly.
Obviously, as soon as I did boot into fastboot, flashing stock worked like a charm.
Sorry 'bout that.
Click to expand...
Click to collapse
Haha, no worries. Sometimes it is hard to see the wood for the trees.
hi there, i have a Sony xperia sp, I'm wanting to install a new ROM, as the 4.3 is hideous, i have rooted, added a recovery mode onto the phone to flash/install the new ROM, but when i try install, it will tell me that it's completed and i restart the phone with the Gapps and ROM installed and the phone won't turn on, so i have to repair it through Sony PC Companion 2.1 to get 4.3 back onto the phone, can someone help me as I'm loosing it with ROM installations, I am aware the phone is capable of running higher versions of android but I don't know why the phone won't install properly.
XDA Visitor said:
hi there, i have a Sony xperia sp, I'm wanting to install a new ROM, as the 4.3 is hideous, i have rooted, added a recovery mode onto the phone to flash/install the new ROM, but when i try install, it will tell me that it's completed and i restart the phone with the Gapps and ROM installed and the phone won't turn on, so i have to repair it through Sony PC Companion 2.1 to get 4.3 back onto the phone, can someone help me as I'm loosing it with ROM installations, I am aware the phone is capable of running higher versions of android but I don't know why the phone won't install properly.
Click to expand...
Click to collapse
Hi
You can ask here but you have to create an account first before you can post
Xperia SP Q&A, Help & Troubleshooting
Thank you.
Did you unlock bootloader?
Bigrrd225 said:
Did you unlock bootloader?
Click to expand...
Click to collapse
HI, I'm trying to unlock the bootloader on my xperia but i can't, the phone is able to be unlocked but the fast boot lasts for 5 seconds before going into charging mode, im have tried using a 2.0 and 3.0 usb but still having issues and i am using windows 10
its_connorshaw said:
HI, I'm trying to unlock the bootloader on my xperia but i can't, the phone is able to be unlocked but the fast boot lasts for 5 seconds before going into charging mode, im have tried using a 2.0 and 3.0 usb but still having issues and i am using windows 10
Click to expand...
Click to collapse
Okay
its_connorshaw said:
HI, I'm trying to unlock the bootloader on my xperia but i can't, the phone is able to be unlocked but the fast boot lasts for 5 seconds before going into charging mode, im have tried using a 2.0 and 3.0 usb but still having issues and i am using windows 10
Click to expand...
Click to collapse
Hi, are you the original poster of this thread?
If this is so, you will really need to unlock your bootloader first, that is the rule of thumb if you want to use custom ROMs that require an unlocked bootloader. If you flash a ROM that requires an unlocked bootloader on a locked bootloader, the phone won't boot at all. You will need to check if your device eligible for bootloader unlock first!
To remedy your problem of fastboot lasting for 5 seconds, you might want to make sure you installed the correct Xperia drivers. You can install the drivers by navigating through the FlashTool install directory (C:\Flashtool\drivers) and install the drivers from within. Or, if you do not have flashtool, you may download the drivers pack here: http://forum.xda-developers.com/showthread.php?t=2635830 NOTE! Since you are using windows 10, it also uses the same driver verification thingy that was introduced in windows 8+, therefore you will need to follow the link provided under [Troubleshooting] part of the linked thread.
All you need to do is select fastboot drivers, flashmode drivers, and adb drivers for Viskan board.
if you have succeeded on installing proper drivers, you will now have to try again unlocking the bootloader. I highly recommend using FlashTool for unlocking purposes (if youre coming from another device, you might be familiar with the fastboot unlock command).
If fail, one common issue with fastboot lasting for a few seconds is a bad USB cable. Try to find another genuine cable and use it. If you dont have any options, try to position the USB cable in a correct position, so that the connection between your XSP and the PC is solid.
If else fails, i would lastly suggest for you to try on another PC.
TechnoSparks said:
Hi, are you the original poster of this thread?
If this is so, you will really need to unlock your bootloader first, that is the rule of thumb if you want to use custom ROMs that require an unlocked bootloader. If you flash a ROM that requires an unlocked bootloader on a locked bootloader, the phone won't boot at all. You will need to check if your device eligible for bootloader unlock first!
To remedy your problem of fastboot lasting for 5 seconds, you might want to make sure you installed the correct Xperia drivers. You can install the drivers by navigating through the FlashTool install directory (C:\Flashtool\drivers) and install the drivers from within. Or, if you do not have flashtool, you may download the drivers pack here: http://forum.xda-developers.com/showthread.php?t=2635830 NOTE! Since you are using windows 10, it also uses the same driver verification thingy that was introduced in windows 8+, therefore you will need to follow the link provided under [Troubleshooting] part of the linked thread.
All you need to do is select fastboot drivers, flashmode drivers, and adb drivers for Viskan board.
if you have succeeded on installing proper drivers, you will now have to try again unlocking the bootloader. I highly recommend using FlashTool for unlocking purposes (if youre coming from another device, you might be familiar with the fastboot unlock command).
If fail, one common issue with fastboot lasting for a few seconds is a bad USB cable. Try to find another genuine cable and use it. If you dont have any options, try to position the USB cable in a correct position, so that the connection between your XSP and the PC is solid.
If else fails, i would lastly suggest for you to try on another PC.
Click to expand...
Click to collapse
Thank you so much! i have managed to unlock my bootloader, but i have one more question, when i unlocked my bootloader, it wiped my whole phone, is this normal?
its_connorshaw said:
Thank you so much! i have managed to unlock my bootloader, but i have one more question, when i unlocked my bootloader, it wiped my whole phone, is this normal?
Click to expand...
Click to collapse
No problem, friend! Yes, unlocking the bootloader will wipe the phone's data. This is warned multiple times on the unlock bootloader page of SONY.
TechnoSparks said:
No problem, friend! Yes, unlocking the bootloader will wipe the phone's data. This is warned multiple times on the unlock bootloader page of SONY. [/QQUOTE]
I have managed to install the custom ROM, thank you again
I'm running on 5.1.1 but the sp runs very slowly on occasions, would upgrading to v6.0 work fine or even better than 5.1.1? I have noticed its a lot better than 4.3.
Click to expand...
Click to collapse
its_connorshaw said:
TechnoSparks said:
No problem, friend! Yes, unlocking the bootloader will wipe the phone's data. This is warned multiple times on the unlock bootloader page of SONY. [/QQUOTE]
I have managed to install the custom ROM, thank you again
I'm running on 5.1.1 but the sp runs very slowly on occasions, would upgrading to v6.0 work fine or even better than 5.1.1? I have noticed its a lot better than 4.3.
Click to expand...
Click to collapse
Sorry, but I can't answer to that
Click to expand...
Click to collapse