Database Develop

[Q] Unable to access Fastboot mode

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.

[Q] 4.4 OTA bricked - fastboot inaccessible !

I had android GE 4.3 on it, rooted.
I have the original GE bootloader (that robot) installed.
I downloaded the official 4.4 update through android, rebooted for install.
Now after the install the phone does not boot up anymore, instead it goes into RECOVERY and shows that triangle robot.
I tried wipe of cache and data wipe.
Whatever i try I am not able to get this device into fastboot / bootloader anymore!
It takes longer than usual,, it is stuck in that HTC screen since I have unlocked the bootloader but it does not enter the usual menu.
Instead it just directly goes to the robot.
I tried about everything I could think about,
It seems the OTA really bricked my phone by damaging the bootloader so it does not load at all anymore.?!?!
The only USB accessible feature I see is that in the robot screen it registers a device through USB.
Sadly not ADB or fastboot, it is a volume. It even loads as volume but is inaccessible (like a CD without disk)
Windows recognizes it as WDP FileSystem.
I doubt this will help at all, just wanted to note it.
I am about to throw the phone into trash, if it had not been so expensive.. Anything that can be done to repair this brick ?

Lirezh said:
I had android GE 4.3 on it, rooted.
I have the original GE bootloader (that robot) installed.
I downloaded the official 4.4 update through android, rebooted for install.
Now after the install the phone does not boot up anymore, instead it goes into RECOVERY and shows that triangle robot.
I tried wipe of cache and data wipe.
Whatever i try I am not able to get this device into fastboot / bootloader anymore!
It takes longer than usual,, it is stuck in that HTC screen since I have unlocked the bootloader but it does not enter the usual menu.
Instead it just directly goes to the robot.
I tried about everything I could think about,
It seems the OTA really bricked my phone by damaging the bootloader so it does not load at all anymore.?!?!
The only USB accessible feature I see is that in the robot screen it registers a device through USB.
Sadly not ADB or fastboot, it is a volume. It even loads as volume but is inaccessible (like a CD without disk)
Windows recognizes it as WDP FileSystem.
I doubt this will help at all, just wanted to note it.
I am about to throw the phone into trash, if it had not been so expensive.. Anything that can be done to repair this brick ?
Click to expand...
Click to collapse
Now search for the right adb and fastboot driver. There is a .msi installer (adb + fastboot .msi) something like that. Than push the right recovery via fastboot. Voila

Alfa Kenny One said:
Now search for the right adb and fastboot driver. There is a .msi installer (adb + fastboot .msi) something like that. Than push the right recovery via fastboot. Voila
Click to expand...
Click to collapse
Hi,
I solved it.
It took about 30-50 reboots until the phone entered the fastboot menu.
The problem was that the phone kept skipping the whole fastboot menu and went into recovery instead.
A very strange firmware bug caused by the failed OTA

[Q] Help, unloked bootloader, Unknown Device even at bootloader, no usb.

Hello, thanks for your time, I need Help. I have been reading the whole day with no results.
1. what i have: I have the Atrix hd from AT&T sim unlocked, bootloader unlocked, CWM v6.0.2.8, it charges by using bp tools while connected to usb charger. now it is 100%.
2. the problem. I can´t make it go up, it can get to fastboot and CWM, when I try to make it start normally it goes to the bootloader unlocked screen and stays there then turn off and goes to the same screen again, when I connect it to the pc while it's off it then turn on to the fastboot and the pc recognizes it as unknown device , the fastboot says.
AP Fastboot Flash Mode (S)
10.9B(*) (sha-2e68372, 2012-11-17 23-33-08)
eMMC Info: Size 8GB
Device is UNLOCKED, Status Code: 3
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Flash Failure
else I can go there by using the +, - and Power button, and selecting Fastboot, and it changes the
USB Connected -> Connect USB
Flash Failure -> Menu Selected.
if i connect to the pc it says nothing, I have tried with different PCs and usb cables, also I tried using "Fastboot Reboot"? on my father's Atrix 2 with the same cable and it worked.
I can not mount /data or /sdcard, but i can mount the xternal sdcard.
I have been looking for a Update.zip for the Atrix HD, but nothing found, also the Atrix HD is not supported by the kitchen, it is to flash stock JB with CWM.
how i got there?
first I Rooted, and unloked bootloader with myth tools, i was in Stock JB,
then I instaled CWM and flashed Pacman pac_mb886-nightly-20131222,
then flashed stock ICS 7.7.1Q-115_MB886_FFW-14_SIGNED_CFC.xml.zip with Myth,
then I started geting the Unknown Device and could'nt mount the phone on the pc, even in fastboot,
then flashed back pacman, but the problem kept going,
then tried flashing JB with Myth and manually using the CMD Fastboot and the script of flashing.bat in the myth and the phone died, it went fine until flashing modem from then on it said failed directory doesnt exist, or device not found, or too many links.
again thanks.
EDIT: Thanks for all of those who say my post, editing here to tell you how I managed to fix it.
first I went into CWM, then mount and format -> format data and data media, (Sdcard), something I didn't want, coz I lost all my data and bakups, but anyway i clicked it hopping it wouldnt function, but it did, wen I saw succes.
formated system, data, cache, dalvik, mounted external sd, and instaled pacman, and gaps, that i had there, then reset system now.
it went to fastboot reason flash failed, turned off.. vol + & - , star normally, it went to warning bootloader unlock and finally pacaman bootanimation, I saw glory.
Now I just have to fix the fastboot booting and the warning but reading ill get it.

Glad you got it working. You should also update to the latest cwm or Philz for recovery.

Yes, and you can install Philz Touch recovery zip from within CWM - then you can install the KK ROMs.

[Q] HTC One Fastboot Commands Not Working

Hey! So I rooted and installed cyanogenmod on my HTC One M7, and It was working fine for a while. Then recently it wouldnt turn on. I can access the bootloader, but my recovery - ClockWorkMod - was not working. I cannot enter recovery or factory reset my device. Also when I try to flash a new recovery via fastboot, it says that it failed to write, and my devices freezes on the fastboot screen. In fact any command I try via fastboot fails. I Hope to be able to restore my phone back to stock sense. Any help?

My sdcard is Fragmented
Glognaw said:
Hey! So I rooted and installed cyanogenmod on my HTC One M7, and It was working fine for a while. Then recently it wouldnt turn on. I can access the bootloader, but my recovery - ClockWorkMod - was not working. I cannot enter recovery or factory reset my device. Also when I try to flash a new recovery via fastboot, it says that it failed to write, and my devices freezes on the fastboot screen. In fact any command I try via fastboot fails. I Hope to be able to restore my phone back to stock sense. Any help?
Click to expand...
Click to collapse
My sdcard is fragmented:crying:

Bootloader won't start

After a long search, I couldn't find anything related to this issue, that's why I've posted this here.
So I tried to root an LG 4X HD, I rooted it immediately without unlocking BL, now everytime I boot into bootloader, I get this:
[LGE_SECURITY] ERROR: boot image signature
Critical failure: unable to start kernel
Unrecoverable bootloader error (0x0000002)
Android (ICS) boots just fine, has root access... but can't access recovery
I know I did something wrong here, little help?
Sent from my LG G2 using Tapatalk... Awesome

Unlock the boot loader
don't forget to hit thanks!

abhi08638 said:
Unlock the boot loader
don't forget to hit thanks!
Click to expand...
Click to collapse
Tried that, won't get into OEM BL unlock mode... it's just odd.
Sent from my LG G2 using Tapatalk... Awesome

hanisod said:
Tried that, won't get into OEM BL unlock mode... it's just odd.
Sent from my LG G2 using Tapatalk... Awesome
Click to expand...
Click to collapse
On ICS you can't unlock bootloader, try upgrading to JB.
Press thanks if it helps

hanisod said:
After a long search, I couldn't find anything related to this issue, that's why I've posted this here.
So I tried to root an LG 4X HD, I rooted it immediately without unlocking BL, now everytime I boot into bootloader, I get this:
[LGE_SECURITY] ERROR: boot image signature
Critical failure: unable to start kernel
Unrecoverable bootloader error (0x0000002)
Android (ICS) boots just fine, has root access... but can't access recovery
I know I did something wrong here, little help?
Sent from my LG G2 using Tapatalk... Awesome
Click to expand...
Click to collapse
My problem is same as yours or nearly the same.
I unlocked bootloader on V20a with "adb reboot oem-unlock" and installed CWM + CM11. Everything was working fine, but GPS. From time to time loses signal, takes more minutes to get lock, etc...
I read somewhere on this forum that there is a problem with the V20x basebands and the solution is to roll back to V10x. So I flashed back to V10H with .dz file. When I type "adb reboot bootloader", "adb reboot-bootloader" or "adb reboot oem-unlock" the phone just restarts. (At this point I can boot into LG's recovery.) Rooted the system and flashed CWM recovery from shell. When I want to boot in to new recovery then appears this message. (I can boot into system.)
Again if I flash back the V20a, I can boot into bootloader and can install custom recovery (without re-unlocking).
I would like to know, how could I manage to work V10x+CWM+CM11 together

jeBACH said:
My problem is same as yours or nearly the same.
I unlocked bootloader on V20a with "adb reboot oem-unlock" and installed CWM + CM11. Everything was working fine, but GPS. From time to time loses signal, takes more minutes to get lock, etc...
I read somewhere on this forum that there is a problem with the V20x basebands and the solution is to roll back to V10x. So I flashed back to V10H with .dz file. When I type "adb reboot bootloader", "adb reboot-bootloader" or "adb reboot oem-unlock" the phone just restarts. (At this point I can boot into LG's recovery.) Rooted the system and flashed CWM recovery from shell. When I want to boot in to new recovery then appears this message. (I can boot into system.)
Again if I flash back the V20a, I can boot into bootloader and can install custom recovery (without re-unlocking).
I would like to know, how could I manage to work V10x+CWM+CM11 together
Click to expand...
Click to collapse
you need to mod 20x kdz with 10x baseband, and flash that. there's a tutorial somewhere around the forum, search and you'll find it.

The tutorial that Flying_Bear is talking about is:
[BASEBANDS][TUTORIAL] Freedom! Choose your baseband.