Related
I read through many threads and have followed the official Sony bootloader unlocking instructions. I have requested and received the unlock code from Sony via email. I have downloaded the inf file and placed it in the correct folder in Android SDK (which I also updated). But I am cannot access fastboot mode, I hold down Vol + and plug in the USB cable but the device shows a red led and goes into charging mode. Also the PC never prompts me to install fastboot driver it simply loads the SP as Sony mass storage device (in device manager).
I have read that some people seem to think that the SIM lock affects the ability to access fastboot but this SP is SIM unlocked. Sony's official guide to unlocking the bootloader says I need to access fastboot mode to enter the unlock code but how can I unlock the bootloader if I can't get into fastboot mode?
hmmm... don't know really... i once entered fastboot mode by mistake, while trying to root stock rom. wasn't reading instructions and put device in a fsatboot mode instead of debugging... was on stock rom so don't know if custom rom would let me do that. should check myself... if anything i know it is possible to get me that blue light shining.
To enter fastboot mode in Xperia SP just power down the phone and hold down the volume up key while pluging your phone into your pc
If you need flashmode do the same thing but with the volume DOWN button held down.
I´ve got the same problem. I can´t enter in flashmode neither in fastboot mode. I´m on windows 8 32bits and I installed the .245 Deodexed ROM with a problem on root and without CWM. I don´t know what to do now, please help me.
As I explained in the first post, I understand how to access fastboot mode (and flash mode). I got root and backed up the TA partition, the stock apps (from 1.257) and backed up the stock ROM. Then, after I wasn't able to get into fastboot, I have installed CWM for LB and flashed a custom ROM based on 2.245. I am able to enter flash mode but not fastboot. As I said before, the phone is SIM unlocked but is acting like it came from a carrier, with locked bootloader and fastboot disabled. How can Sony disable fastboot? I don't get it. Any one want to take a guess how long I will have to wait until some clever dev finds an exploit?
gandalf_grey91 said:
As I explained in the first post, I understand how to access fastboot mode (and flash mode). I got root and backed up the TA partition, the stock apps (from 1.257) and backed up the stock ROM. Then, after I wasn't able to get into fastboot, I have installed CWM for LB and flashed a custom ROM based on 2.245. I am able to enter flash mode but not fastboot. As I said before, the phone is SIM unlocked but is acting like it came from a carrier, with locked bootloader and fastboot disabled. How can Sony disable fastboot? I don't get it. Any one want to take a guess how long I will have to wait until some clever dev finds an exploit?
Click to expand...
Click to collapse
Sorry for that i dont think that it is your computers fault because you enter fastboot (and flashmode) using your mobile phone NOT your PC
So i would roughly assume that this is a Rom bug or something in the flashing proccess went wrong.
jackaros said:
Sorry for that i dont think that it is your computers fault because you enter fastboot (and flashmode) using your mobile phone NOT your PC
So i would roughly assume that this is a Rom bug or something in the flashing proccess went wrong.
Click to expand...
Click to collapse
Thanks for trying to help, but I understand that flashmode and fastboot are accessed using the phone. Actually the phone needs a piece of software like flashtool to keep it in flashmode otherwise it drops into charging mode. I didn't mention my computer so I don't know where you got that from.
As I explained, I am unable to access fastboot with stock ROM (1.257) and a custom ROM (based on 2.245) so it can't be a ROM bug or the flashing process having gone wrong.
if it's not too much of a trouble for you, go and flash .245 stock, than .257 stock kernel only. like you are trying to root it for the first time, complete rooting procedure, and than proceed on to installing CWM, but instead of connecting device in debugging mode to install CWM, try and see if you can put it in a fastboot. this was exactly the moment when i accidentally put mine SP in fastboot. of course, i'm not saying to go ahead and install anything if you score, but only to confirm if you can put your device into a fastboot mode since installing anything without CWM will likely soft brick your device.
Same problem here, i can't do anything using flashtool after flashed 2.245. I did with SUS, maybe is some flashtool issue.
Ze Tolas said:
Same problem here, i can't do anything using flashtool after flashed 2.245. I did with SUS, maybe is some flashtool issue.
Click to expand...
Click to collapse
It may be a flashtool problem you are right because 2 incidents with different Roms that both use flashtool to flash those roms.....
its pretty much self explenatory.
skojevac said:
if it's not too much of a trouble for you, go and flash .245 stock, than .257 stock kernel only. like you are trying to root it for the first time, complete rooting procedure, and than proceed on to installing CWM, but instead of connecting device in debugging mode to install CWM, try and see if you can put it in a fastboot. this was exactly the moment when i accidentally put mine SP in fastboot. of course, i'm not saying to go ahead and install anything if you score, but only to confirm if you can put your device into a fastboot mode since installing anything without CWM will likely soft brick your device.
Click to expand...
Click to collapse
Interesting. Ok, I've read up on the process. So I use the various stock .ftf files and flashtool with the phone in flash mode? Bear in mind that kernel didn't allow fastboot when I used it with the stock .257 ROM the device came with. If I do it, I will nandroid backup first, of course, but I think I remember reading in one thread that someone managed to soft brick their XSP doing this very thing.
Bear in mind that kernel didn't allow fastboot when I used it with the stock .257 ROM the device came with. [/QUOTE said:
that's why you need to complete rooting procedure. root stock 1.257 kernel, than back to stock 2.245 with root preserved, and before you would install CWM try to put device in a fastboot mode, this assuming you still have a UB.
Click to expand...
Click to collapse
have you tried to boot into android, open a root terminal and type
exec reboot bootloader
that should bring you straight into fastboot
SuicideFlasher said:
have you tried to boot into android, open a root terminal and type
exec reboot bootloader
that should bring you straight into fastboot
Click to expand...
Click to collapse
All that happens is that the terminal session ends and closes (not FC) the terminal app. Using the same command via adb just does a standard reboot.
i just placed my in a fastboot mode, no problems whatsoever. do you have drivers for the device installed? you will find these in flashtool installation folder.
skojevac said:
i just placed my in a fastboot mode, no problems whatsoever. do you have drivers for the device installed? you will find these in flashtool installation folder.
Click to expand...
Click to collapse
Yes. The fastboot_with_android_usb_file.rar package specified on DooMLoRD's bootloader unlocking/relocking appears to have been removed and there are no new links in that thread. So, I found and installed the drivers included with the flashtool. But it seems to be the device that is the problem. It is acting like a carrier locked model. I am rapidly starting to believe that this one has a locked bootloader.
gandalf_grey91 said:
Yes. The fastboot_with_android_usb_file.rar package specified on DooMLoRD's bootloader unlocking/relocking appears to have been removed and there are no new links in that thread. So, I found and installed the drivers included with the flashtool. But it seems to be the device that is the problem. It is acting like a carrier locked model. I am rapidly starting to believe that this one has a locked bootloader.
Click to expand...
Click to collapse
I said before, it's new firmware (maybe RU) with a Windows Flashtool issue. Today i did flash kernel to my SP using Linux client.
Same issues
gandalf_grey91 said:
All that happens is that the terminal session ends and closes (not FC) the terminal app. Using the same command via adb just does a standard reboot.
Click to expand...
Click to collapse
Hi, I have some similar issues. I've also been flashing some stuff and whenever I try to go to fastboot it just boots into CWM. Very annoying to say the least. The dark blue light goes on when i hold down volume up and for a short moment I see the fastboot driver installing on my computer. But before it completes it's already in CWM.
Not sure what to do from here on wards, maybe some advice on which kernel to flash? I am pretty sure the latest kernel I flashed is the .254 root kernel from doomlord.
Ps. I really would like to flash CM when it becomes available as nightly :angel:
Thanks in advance!
Fast boot mode for xperia ion hspa???
gandalf_grey91 said:
As I explained in the first post, I understand how to access fastboot mode (and flash mode). I got root and backed up the TA partition, the stock apps (from 1.257) and backed up the stock ROM. Then, after I wasn't able to get into fastboot, I have installed CWM for LB and flashed a custom ROM based on 2.245. I am able to enter flash mode but not fastboot. As I said before, the phone is SIM unlocked but is acting like it came from a carrier, with locked bootloader and fastboot disabled. How can Sony disable fastboot? I don't get it. Any one want to take a guess how long I will have to wait until some clever dev finds an exploit?
Click to expand...
Click to collapse
I had already installed cm10.1 jb for my xperia ion.
Now i tried to install cm11 kitkat for my xperia ion.
Every thing is gone good.
But now got stuck up with a problem.
fast boot mode is active only for 5 seconds while connecting my xperia ion to System with flash tool.
help me to do the need ful.
Guide me to download compatible drivers and flash tool for fast booting process.
If you have UNLOCKABLE bootloader, then you dont have a FASTBOOT mode on your phone. Its just pure luck. some phones dont have it... kind of a sony crap... I also happen to be one of those LUCKY ppl. no unlock, so stuck with Stock kernel forever.
When you connect your phone to Flashtools in FLASHMODE...
See for a string BOOTLOADER: NOT_ROOTABLE.... it means you belong in the lucky group...
If it says rootable, then you're doing something wrong.
Pardon me if i read something incorrect. i skimmed through all the posts before posting.
I'm on CM11 which has been working for weeks, last night my phone died completely and when I put it in the charger it wouldn’t light up no matter which outlet/cord I used. It reboots itself after a few seconds of being on, and so soon that I cant enter into recovery or select factory reset under recovery from bootloader because it selects recovery for me and then turns off. My Hboot is 1.44, S-on, its rooted as well. I have reached the edge of my competence, I'd really appreciate any and all help.
nicksperception said:
I'm on CM11 which has been working for weeks, last night my phone died completely and when I put it in the charger it wouldn’t light up no matter which outlet/cord I used. It reboots itself after a few seconds of being on, and so soon that I cant enter into recovery or select factory reset under recovery from bootloader because it selects recovery for me and then turns off. My Hboot is 1.44, S-on, its rooted as well. I have reached the edge of my competence, I'd really appreciate any and all help.
Click to expand...
Click to collapse
first try to re-flash your recovery to resolve
if not, you must flash stock ROM :
turn your phone on in bootloader mode or RUU mode (fastboot oem rebootRUU)
find your right RUU.exe from here > flash it
Note : you must flash the correct RUU that meet your CID & MID
if you can't know/find the correct RUU?, post your CID & MID
moha_moha20106 said:
first try to re-flash your recovery to resolve
if not, you must flash stock ROM :
turn your phone on in bootloader mode or RUU mode (fastboot oem rebootRUU)
find your right RUU.exe from> flash it
Note : you must flash the correct RUU that meet your CID & MID
if you can't know/find the correct RUU?, post your CID & MID
Click to expand...
Click to collapse
i dont know how to run adb commands when my phone wont turn on long enough to get registered by adb or the computer its on. it cant stay in bootloader for more than a few seconds, cant go into fastboot nor recovery. my radio is 4A 14.3250.13 and my phone is for AT&T, is that helpful?
it seems that there is nothing left to do with the phone. no fastboot, no recovery, no factory reset, no computer recognition. no adb/fastboot command gets the phone to be recognized. i have the latest htc drivers installed manually but when the computer recognizes there is a usb anything it tries to install the drivers but the phone quickly turns off and the driver installation fails. adb devices comes up empty, getvar cid keeps waiting for device forever, and trying to push files doesn’t work because it cant recognize it's there in the first place. is there anything I can do?
Here is the bootloader page I see if it helps.
nicksperception said:
Here is the bootloader page I see if it helps.
Click to expand...
Click to collapse
first, you must hit THANKS if anyone try to help you, or reply to help you
read this post if you need to learn more about ADB / Fastboot commands
Maybe my topic will help you (it's just one page back) http:// http://forum.xda-developers.com/showthread.php?t=2707187
detovenaar said:
Maybe my topic will help you (it's just one page back) http://forum.xda-developers.com/showthread.php?t=2707187
Click to expand...
Click to collapse
you link was broken
@nicksperception
try the link in my Quote above
detovenaar said:
Maybe my topic will help you (it's just one page back) http:// http://forum.xda-developers.com/showthread.php?t=2707187
Click to expand...
Click to collapse
I appreciate the help but I cant even get my phone to be recognized in fastboot or adb. It said "waiting for device" when i tried to get my cid for hours. It turns off too quickly for the computer to recognize it. Did you have this problem? If so how did you fix it?
I'm stuck in the boot loader and adb devices says *daemon not running. starting it now.... *damon started successfully* List of devices attached ... BLANK...
I need to go back to stock since ALL RUU's cannot flash says wrong version
Image version 1.31.651.2 when installing 1.29.651.10 .... Error will not work..
I'm stuck in the bootloader without TWRP or recovery or anything other than Fastboot USB and Bootloader reboot power down basically...
THANKS
[Q] Carrier Unlock to AT&T Anyone?!?
Can someone help me get my phone completely wiped back to 110% stock everything so I can attempt to carrier unlock it to AT&T?
I paid for my Carrier unlock codes and want to use the phone on AT&T but nothing pops up to enter codes or anything like that at all...
My phone apparently has no recovery and no rom but hangs booting the rom....
Can someone who already carrier unlocked to AT&T in the USA tell me about the speeds and thoughts on how you did it?
I paid for my IEMI unlock pin and codes... now i just need to enter them and i had tried on ViperOne ... not stock
THANKS
1chris89 said:
I'm stuck in the boot loader and adb devices says *daemon not running. starting it now.... *damon started successfully* List of devices attached ... BLANK...
I need to go back to stock since ALL RUU's cannot flash says wrong version
Image version 1.31.651.2 when installing 1.29.651.10 .... Error will not work..
I'm stuck in the bootloader without TWRP or recovery or anything other than Fastboot USB and Bootloader reboot power down basically...
THANKS
Click to expand...
Click to collapse
Try this RUU.
Threads merged. @1chris89 please do not post like questions in different sections.
TonyStark said:
Threads merged. @1chris89 please do not post like questions in different sections.
Click to expand...
Click to collapse
Loading latest RUU ... has been about 10 minutes and its stuck at 4%... I just killed the process on windows 7 x64 and with it still on the HTC logo held power and volume down. Which booted back to bootloader... Gonna try it again...................................................
1chris89 said:
I'm stuck in the boot loader and adb devices says *daemon not running. starting it now.... *damon started successfully* List of devices attached ... BLANK...
I need to go back to stock since ALL RUU's cannot flash says wrong version
Image version 1.31.651.2 when installing 1.29.651.10 .... Error will not work..
I'm stuck in the bootloader without TWRP or recovery or anything other than Fastboot USB and Bootloader reboot power down basically...
THANKS
Click to expand...
Click to collapse
well first youre not supposed to use adb in the bootloader thats what fastboot is for. ensure that youre in fastboot and not hboot mode and if your drivers are installec properly you will see fastboot usb and is you run fastboot devices your device will appear when plugged into the computer. also you dont have to be on a stock rom to sim unlock just have to be on a sense rom.
Thanks I have gone through the tutorials and sim unlocking doesn't work. Its not the same as when unlocking an AT&T or T-Mobile phone when you put in the new sim and it asks for a code to unlock, enter code ----- Done.
So right now my TWRP is frozen basically can't use my touch to use it it's frozen.
Should I just RUU back to 5.0.3.6 stock....?
I just want to enter my unlock code HTC sent me.... Otherwise this phone is literally a Paper Weight.
Thanks
Are you soff?
Hi I installed GSM TWRP on my SPRINT and I can't get TWRP to work anymore it's like frozen to touch input...
I just wanna get SPRINT TWRP so I can disable SIMLOCK in the BOOTLOADER so I can use my AT&T sim with it.
I tried all the RUU's and they sit at "1/5 CHECKING HEADER..."
THANKS
That's the step it kept stopping at for me. Try the guide I wrote here: http://forum.xda-developers.com/spr...de-reset-phone-using-ruu-htcfastboot-t2876110
Hello people.
So i got a custom recovery (TeamWin project). I disabled OEM Unlock on purpose, because i thought it wouldn't show the red line up in the bootscreen.
After trying to reboot, it wouldn't reboot, and i can't go into Recovery mode. I can't install any custom firmware too, because i've got the OEM Unlock set to "off"
Can someone please help, i can't find a topic similiar to my case, where i've bricked my phone and have no idea what to do.
Thanks to all those who are tying me to help <3.
Viesuliss said:
Hello people.
So i got a custom recovery (TeamWin project). I disabled OEM Unlock on purpose, because i thought it wouldn't show the red line up in the bootscreen.
After trying to reboot, it wouldn't reboot, and i can't go into Recovery mode. I can't install any custom firmware too, because i've got the OEM Unlock set to "off"
Can someone please help, i can't find a topic similiar to my case, where i've bricked my phone and have no idea what to do.
Thanks to all those who are tying me to help <3.
Click to expand...
Click to collapse
As long as you can get it in the download mode you can use fastboot with a PC.
mr.natural said:
As long as you can get it in the download mode you can use fastboot with a PC.
Click to expand...
Click to collapse
It doesn't recognize my device. I have tried every single tutorial found on google and still can't seem to unlock my bootloader.
Can't flash recovery nor the official stock firmware.
Viesuliss said:
It doesn't recognize my device. I have tried every single tutorial found on google and still can't seem to unlock my bootloader.
Can't flash recovery nor the official stock firmware.
Click to expand...
Click to collapse
If you are on Windows you have to install the right (usb)driver.
mr.natural said:
If you are on Windows you have to install the right (usb)driver.
Click to expand...
Click to collapse
No luck with that. I installed. Restarted my computer and device.
Went in to download mode and nothing shows up.
Viesuliss said:
No luck with that. I installed. Restarted my computer and device.
Went in to download mode and nothing shows up.
Click to expand...
Click to collapse
Look and ask on the forum/thread of your device
Hello, I rooted, and installed custom recovery on my 1+3t. And the new update came out. I decided to give it a shot. Long story short. I locked my bootloader. And when I try to boot it up. It shows logo for one second, vibrates, and is stuck in that bootloop. I can get into recovery, and fastboot, but bootloader is locked. Any ideas?
Use recovery unbrick tool.
And don't lock your bootloader when you're going to flash any kind of mod, like Magisk.
You can unlock bootloader if you have activated oem unlock and usb debugging in the developer option. Then you are good to go for custom recovery..
You should never re-lock your bootloader after you flash anything not signed by OnePlus. Your device can never be booted up and only can be fixed if you use the unbrick tool by Qualcomm.
thes3usa said:
You should never re-lock your bootloader after you flash anything not signed by OnePlus.
Click to expand...
Click to collapse
My thoughts exactly.
To the OP, you don't need to lock the bootloader to update this device. And you should never lock the bootloader with mods on the phone (TWRP, root, etc.).
Good rule of thumb, is to read up before doing an update like this. Would have saved you a lot of hardship, as all the info is here on XDA for those that care to search and read.