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.
X1053, rooted and unlocked bootloader on T Mob US
Tried to install a new kernel but it failed. Wiped cached (factory reset in twrp) and now it won't boot past the animation logo.
As its not booted into the OS, windows won't recognize it as a device so i can't install a new rom to try again. Windows 8 'bings' when I connect it but it won't load as a drive.
I CAN get into AP Fashboot Flash Mode If I then go to Recovery, it still takes me to twrp. But there are not zip files to install that work and I can't work out how to copy them over without windows recognizing the device?
Thanks in advance
You'll maybe need to flash the same stock firmware version you're on now...4.4 or 4.4.2 or whatever version you were on. Then root again.
This will help you...
http://forum.xda-developers.com/showthread.php?t=2603358
Good luck!
kj2112 said:
You'll maybe need to flash the same stock firmware version you're on now...4.4 or 4.4.2 or whatever version you were on. Then root again.
This will help you...
http://forum.xda-developers.com/showthread.php?t=2603358
Good luck!
Click to expand...
Click to collapse
Thanks for the reply. the problem is I can't connect to the phone to transfer a new firmware on. It 'bings' on USB plug but won't open as a USB drive. I can't get the phone to boot, can only get it to recovery. i tried reinstalling the motorola drivers again but still no luck.
When it was running Ok, I could plug it in (when it used to load into the android OS OK) and it would appear as a USB drive in Windows 8. I also tried on a different laptop.
emailrob said:
Thanks for the reply. the problem is I can't connect to the phone to transfer a new firmware on. It 'bings' on USB plug but won't open as a USB drive. I can't get the phone to boot, can only get it to recovery. i tried reinstalling the motorola drivers again but still no luck.
When it was running Ok, I could plug it in (when it used to load into the android OS OK) and it would appear as a USB drive in Windows 8. I also tried on a different laptop.
Click to expand...
Click to collapse
When you boot into bootloader, does the phone itself recognize that it is connected via USB? If so, you have to obtain the current SBF of your phone and flash over the files via fastboot.exe and mfastboot.exe.
There are plenty of guides throughout this site. Take your time and read everything before you make your first move.
Cyphir said:
When you boot into bootloader, does the phone itself recognize that it is connected via USB? If so, you have to obtain the current SBF of your phone and flash over the files via fastboot.exe and mfastboot.exe.
There are plenty of guides throughout this site. Take your time and read everything before you make your first move.
Click to expand...
Click to collapse
OK panic nearly over! I managed to get it flashed using RDS lite. 4.4 is back on now, although I lost my root Not sure I want to go down the whole downgrade to 4.2.2 etc but I'll see. Thanks again
Just adding a reply in case anyone has a similar issue.
RSDLite managed to get the firmware back on. It lost root, but what actually happened is the recovery got deleted / corrupted.
So i went back through the rooting guide which started by adding twrp and then flashing. Rebooted, and SuperSU tells me all is OK and root is there.
:laugh:
Is your phone recognized by fastboot or adb?
Since your bootloader is unlocked, manually flash the 4.4.2 firmware files, then TWRP, then boot into recovery, use adb to push SuperSU or whichever root program you prefer to /sdcard, then use TWRP to flash it.
nhizzat said:
Is your phone recognized by fastboot or adb?
Since your bootloader is unlocked, manually flash the 4.4.2 firmware files, then TWRP, then boot into recovery, use adb to push SuperSU or whichever root program you prefer to /sdcard, then use TWRP to flash it.
Click to expand...
Click to collapse
Its all working OK now thanks. I just flashed 4.4 again and re-installed TWRP.
I need some help...I updated my firmware and I must of updated with the wrong firmware...did they one with stock recovery or something. Now my phone doesn't have a custom recovery and I do not have root. I tried to download the trwp tool and flash but it says I do not have root. Also when I try to adb connect to my phone it doesn't recognise that the device is there. I am running Insert Coin 4.4.4 version 5.03. Any help is much appreciated! Also I should mention the firmware was from Captain Throwbacks thread with the latest. I am also Soff.
Very strange @Captain_Throwback's firmware should not have stock recovery included.
You can fastboot flash twrp.
ADB = OS/Recovery
Fastboot = Bootloader
My computer won't even recognize my phone now so I can't flash anything through fastboot. The command prompt says waiting for device
kpahl1973 said:
My computer won't even recognize my phone now so I can't flash anything through fastboot. The command prompt says waiting for device
Click to expand...
Click to collapse
Are you in fastbootusb ?
Yes fastbootUSB and its in red letters
kpahl1973 said:
Yes fastbootUSB and its in red letters
Click to expand...
Click to collapse
Unplug phone
Uninstall everything HTC and reboot PC
Install these drivers
Plug phone in (drivers should install)
If not try this:
On your PC go to device manager and find your phone, right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Thanks that worked...flashed the recovery successful but wont let me go into it. I think its because I am not rooted. Do I just use the all in one tool to get root back?
kpahl1973 said:
Thanks that worked...flashed the recovery successful but wont let me go into it. I think its because I am not rooted. Do I just use the all in one tool to get root back?
Click to expand...
Click to collapse
If it flashed successfully you should be able to get into recovery.
Are you sure you flashed the correct version? There are several for the M8.
I ended up flashing another version and I got into recovery. Root Checker still says I dont have root so I am going to wipe and reflash my rom. Hopefully that will do it. Not sure what happened but I really appreciate the help with getting the drivers corrected so I could communicate with my device again. With out adb I didnt know what I was going to do.
Guys, if anyone could help me out it would be greatly appreciated. Ok, here's my situation I tried to root my phone using kingroot but it keeps randomly rebooting. So, I've read somewhere that you can change kinguser to supersu by using supersu me. That's what I did now what happened is after installing and rebooting my phone is now in bootloop. So tried reflashing using flashtool but everytime it says that usb debugging must be on and there's no way for me to do that. Is there anyway for me to recover my phone and fix it? Hope you guys can help me.
P.S. Sorry if this is not the right place to post this. Thanks.
huantong said:
Guys, if anyone could help me out it would be greatly appreciated. Ok, here's my situation I tried to root my phone using kingroot but it keeps randomly rebooting. So, I've read somewhere that you can change kinguser to supersu by using supersu me. That's what I did now what happened is after installing and rebooting my phone is now in bootloop. So tried reflashing using flashtool but everytime it says that usb debugging must be on and there's no way for me to do that. Is there anyway for me to recover my phone and fix it? Hope you guys can help me.
P.S. Sorry if this is not the right place to post this. Thanks.
Click to expand...
Click to collapse
Have you installed Sony drivers before using FlashTool?
Only flashtool can recover you from this situation and remember to press up or down button and then connect the USB cable. Then only it will boot into flashmode
Sent from my Xperia ZR using XDA Free mobile app
I've just had a similar experience using kingroot on stock lollipop.. It's a horrible app and of no use really.. This is how i got out of it and rooted my phone properly: download a .ftf stock rom for your region, search in the cross device section for perfcreator, fastboot tool and look in xenius9's thread for a boot.img (recovery, doesn't matter if it's a CM12 img or not for now) and finally a flashable zip supersu and NUT's dual recovery INSTALLER (important this) for ZR..
Place the boot.img in the folder you extracted the fastboot tool to, open perfcreator and point it to your stock ftf firmware and to your supersu zip.. press create and this will make a proper rooted flashable zip firmware, which you place in your SD-card on your phone.. (I used my friends phone to place the firmware onto the SD card and put it back on my hone)
Open the folder with fastboot tool and also include the boot.img.. Power off your phone and press vol-up while you connect your usb cable.. The led will turn blue showing your in fastboot mode, and put the cursor on your pc on a empty space in the fastboot folder, hold shift and right-click... This will open a pop-up and select "open command window here"..
A black screen will appear and type the following: fastboot flash boot boot.img.. press enter
this will take 3 seconds and you will have a working recovery on your phone for now..
Now type in the same black screen: fastboot reboot..
Your phone will boot and you press vol-up or down to get to recovery.. the led will show pink or green ..
wipe your cache/data/system and once done, install the rooted firmware you placed on your sd card.. This will remove the recovery you have installed once you reboot but once you have set your phone up, go to settings/about/build number and press several times until you have unlocked developer options.. go to developer options and check debugging..
connect your phone to the pc, open the dual recovery installer and follow the instructions
You now have a fully rooted phone with recovery installed... Sounds complicated maybe but just take your time and you'll be fine..
Hello,
So I have a P7 at B126. I tried rooting it with kingroot and tried to install TWRP. I got to the part where you have to use fastboot to flash the img and it fails so I gave up. Now I am trying to get into recovery and I can't. It just either goes to a black screen or a Boot failed screen.
Thanks in advance
Hi, I'm a little confused right now. Explain what you did so far a bit more detailed, so we could help you.. Which instruction were you are following? What was the exact error? Is your bootloader unlocked? Can you boot normally?
l3Nni said:
Hi, I'm a little confused right now. Explain what you did so far a bit more detailed, so we could help you.. Which instruction were you are following? What was the exact error? Is your bootloader unlocked? Can you boot normally?
Click to expand...
Click to collapse
I can boot normally.
What I did was this.
I followed the guide to root my phone. Rooted it and then tried to install the TWRP custom recovery. It failed at the installing the recovery for some permission error. So I stopped trying to install it. Now I apparently don't have a recovery at all.
I also installed some root apps like SetCPU, Xposed(Which didn't work), SuperSU(Which didn't Work)
If I try to adb reboot recovery it just takes me to the boot failed screen with the android logo on it. If I try using the Power + Down button it just shows me the huawei ascent P7 screen and just go black.
Also when I go to the fastboot/rescure mode it says my bootloader is unlocked.
Thanks for the reply.
Ah okay. So, boot into the fastboot mode, put the recovery.img in the adb folder on your pc, run cmd and type 'cd c://..' (location of adb folder), then 'fastboot flash recovery [name of recovery.img]' (for example 'fastboot flash recovery recovery_twrp.img'). Now you should get a working recovery.
Are you sure you really got root access? Eventually due to this you got the permission error..
l3Nni said:
Ah okay. So, boot into the fastboot mode, put the recovery.img in the adb folder on your pc, run cmd and type 'cd c://..' (location of adb folder), then 'fastboot flash recovery [name of recovery.img]' (for example 'fastboot flash recovery recovery_twrp.img'). Now you should get a working recovery.
Are you sure you really got root access? Eventually due to this you got the permission error..
Click to expand...
Click to collapse
I do because adb has admin permissions but fastboot doesn't. I tried that with trying to flash twrp on my p7 but i get a failed error after like a second I the command. So I tried flashing a stock recovery and it throws the same error in fastboot.
When I type fastboot devices I get this
? fastboot
No id for my phone but adb sees it.
Ok, your pc does obviously not recognize the p7 in fastboot mode. Did you install the Hi Suite? Through this way you should get the correct drivers (maybe even update/reinstall). If this does not help, I think I can't help you, sorry. You may wait for more help or google what do when the device isn't recognized in fastboot.
Just flash the newest SuperSU.zip when you got a recovery.. That should fix problems with root apps/ the su binary.
Offtopic: I'm not sure if you noticed, but, you're running a pretty old firmware.. You may think about updating
l3Nni said:
Ok, your pc does obviously not recognize the p7 in fastboot mode. Did you install the Hi Suite? Through this way you should get the correct drivers (maybe even update/reinstall). If this does not help, I think I can't help you, sorry. You may wait for more help or google what do when the device isn't recognized in fastboot.
Just flash the newest SuperSU.zip when you got a recovery.. That should fix problems with root apps/ the su binary.
Offtopic: I'm not sure if you noticed, but, you're running a pretty old firmware.. You may think about updating
Click to expand...
Click to collapse
Hi Suite installed and correct drivers are loaded(I hope) and yes thats why Im trying to get this fixed because it wont even let me update firmwares
Try on another pc.. You could also try flashify (look in Google play), but in case of a softbrick you have real problem. Do this on your own risk, most times nothing bad will happen, but it could!
I would recommend to flash the stock recovery, update up to B621 and then installing a custom recovery.
can't boot into recovery
stoutrouge said:
Hello
So I have a P7 at B126. I tried rooting it with kingroot and tried to install TWRP. I got to the part where you have to use fastboot to flash the img and it fails so I gave up. Now I am trying to get into recovery and I can't. It just either goes to a black screen or a Boot failed screen.
Thanks in advance
Click to expand...
Click to collapse
Hi mate.
1. Use your pc, Go shuame.com and download "rom flash program".
2. Enter fastboot&rescue mode and connect your phone and PC
3. The program will recognize your phone.
4. Download anyrom and flash by the program.
The process will not complete but you will have Shuame recovery.
But my case it didn't work properly
5. I downloaded CWM from here "pan.baidu.com/s/1dDq0qcT" password :bttc
Start this program with connect your phone and press nomber 1 and ENTER.
I don't exactly remember my phone was on fastboot & rescue mode or recovery mode.
But I could get recovery and did rom flash so it was fixed.
*****from: Godfrey Peligrino ---sorry i dont know how to post BUT, this guide helped me with my p7 L10 B619..just connect it to pc and let it boot over and over and when pc acknowledge you phone..click rom and just wait if not do it again..hope this will help you too..the writings is on chinese so just copy the english thumbnails before you proceed to download...(QUOTE) THANKS TO THE GUY WHO POST THIS....HE IS TOMODACHI5..