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.
Related
picked up a Z1 and went straight to rooting it.
rooted succesfully, installed the dualrecovery, and then attempted ot install VANIR only to realize that i did not unlock the bootloader.
so it will not turn on. holding power it vibrates every 2 seconds. plugged in it does teh same, but also blinks red.
i can get the computer to recognize it several different ways.
blue led- fastboot interface in device manager - not detected in adb devices
red/green/blank led - SOMC flash - no adb
PC companion is no go.
I have no idea where to go from here. I am currently downloading flashtool to see where that gets me, but I was hoping someone might have some direct and well known solution that i did not uncover in my searching..
Thanks
jewnersey said:
picked up a Z1 and went straight to rooting it.
rooted succesfully, installed the dualrecovery, and then attempted ot install VANIR only to realize that i did not unlock the bootloader.
so it will not turn on. holding power it vibrates every 2 seconds. plugged in it does teh same, but also blinks red.
i can get the computer to recognize it several different ways.
blue led- fastboot interface in device manager - not detected in adb devices
red/green/blank led - SOMC flash - no adb
PC companion is no go.
I have no idea where to go from here. I am currently downloading flashtool to see where that gets me, but I was hoping someone might have some direct and well known solution that i did not uncover in my searching..
Thanks
Click to expand...
Click to collapse
you have to flash a new firmware from flashtool.this will solve your problem.you cant enter to recovery?
Sent from my C6903 using XDA Premium 4 mobile app
Anonymuszymus said:
you have to flash a new firmware from flashtool.this will solve your problem.you cant enter to recovery?
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
He will not be able to enter recovery because dual recovery is system based which he cannot get to as its now trying to boot a custom kernel with a locked bootloader.
Also the recovery on a custom kernel is in the kernel, which also cannot boot. Hence a bootloop with no chance of recovery mode
The solution should be easy enough
Flash a stock FTF for your device using flashtool
gregbradley said:
He will not be able to enter recovery because dual recovery is system based which he cannot get to as its now trying to boot a custom kernel with a locked bootloader.
Also the recovery on a custom kernel is in the kernel, which also cannot boot. Hence a bootloop with no chance of recovery mode
The solution should be easy enough
Flash a stock FTF for your device using flashtool
Click to expand...
Click to collapse
downloading flashtool now.
Will flashtool recognize the phone even though adb does not?
this for ftf?
http://xperiafirmware.com/8-firmware/42-sony-xperia-z1-c6903
this for bootloader?
http://forum.xda-developers.com/showthread.php?t=2440597
jewnersey said:
downloading flashtool now.
Will flashtool recognize the phone even though adb does not?
this for ftf?
http://xperiafirmware.com/8-firmware/42-sony-xperia-z1-c6903
this for bootloader?
http://forum.xda-developers.com/showthread.php?t=2440597
Click to expand...
Click to collapse
Look in the general section for a sticky thread called FTF mega collection for the best FTF file for you.
Once you have flashed that then you should* root, then unlock the boot following the official sony instructions (http://bit.ly/1cebNlh).
once you have done that flash the boot.img of the rom you want to flash using fastboot them flash the update.zip in recovery
*The reason to root before unlocking the boot is to backup the DRM keys in your TA partition. If you do not do that you lose them forever.
Hi,
I just installed this rom:
http://forum.xda-developers.com/xperia-sp/development/final-solution-rom-lbl-t3073678
Everything went fine. I did all the steps. After installing the ROM and the fixes I chose system reboot from CWM Recovery. Since then I can't turn my phone on. If I press the power button there is a short vibration, but nothing happens.
1. Tried to reset with the button on the back of the phone. No go.
2. Tried all the button combination but can't even get back to recovery.
3. If I connect it to my computer then the led goes green and windows gives me that sound when you connect something new, but after 10 seconds the led turns off and I get the other sound for dismounting device. No diver can see it, neither flashtool does.
4. It doesn't charge. Well, at least the led does not turn on so I guess it's not charging.
Any idea?
You have a kernel problem, Flash with Flashtool the kernel of your rom in fastboot mode (Volume +, and connect your usb cable) with flashtool or if that don't available, flash a stock kernel in fastboot mode (Volume + and connect your usb cable at your phone), when it's flashed, restart your phone
Vic19911992 said:
You have a kernel problem, Flash with Flashtool the kernel of your rom in fastboot mode (Volume +, and connect your usb cable) with flashtool or if that don't available, flash a stock kernel in fastboot mode (Volume + and connect your usb cable at your phone), when it's flashed, restart your phone
Click to expand...
Click to collapse
From where can I get a proper kernel? Does it matter that it has locked bootloader?
Also which flashtool should work?
fishmong3r said:
From where can I get a proper kernel? Does it matter that it has locked bootloader?
Also which flashtool should work?
Click to expand...
Click to collapse
Normally, you can flash the kernel included in your rom, it's a file name boot.img, flashtool is good i think, can you send error messages with flashtool if you have any messages
fishmong3r said:
Hi,
I just installed this rom:
http://forum.xda-developers.com/xperia-sp/development/final-solution-rom-lbl-t3073678
Everything went fine. I did all the steps. After installing the ROM and the fixes I chose system reboot from CWM Recovery. Since then I can't turn my phone on. If I press the power button there is a short vibration, but nothing happens.
1. Tried to reset with the button on the back of the phone. No go.
2. Tried all the button combination but can't even get back to recovery.
3. If I connect it to my computer then the led goes green and windows gives me that sound when you connect something new, but after 10 seconds the led turns off and I get the other sound for dismounting device. No diver can see it, neither flashtool does.
4. It doesn't charge. Well, at least the led does not turn on so I guess it's not charging.
Any idea?
Click to expand...
Click to collapse
If you have locked bootloader you must flash the stock kernel trough the flashmode, williams kernel is custom it will brick your device
Spasik said:
If you have locked bootloader you must flash the stock kernel trough the flashmode, williams kernel is custom it will brick your device
Click to expand...
Click to collapse
I double checked that it works for locked bootloaded. It's even the name of the thread: [Final Solution ROM][UBL/LBL][V2][ODEXED for extreme smoothness][William's Kernel]
So the issue now is that I can't even install the driver (windows 10) as the device is being disconnected after 10 seconds of plugging in. I got the tft file now for the stock kernel and installed flashtool but it can't detect the phone (in that 10 secs), it says that driver is missing. Tried the C:\Flashtool\drivers\Flashtool-drivers.exe and selected the necessary drivers but it never succeeds. Attached the screenshot of the failure of installing the drivers.
fishmong3r said:
I double checked that it works for locked bootloaded. It's even the name of the thread: [Final Solution ROM][UBL/LBL][V2][ODEXED for extreme smoothness][William's Kernel]
So the issue now is that I can't even install the driver (windows 10) as the device is being disconnected after 10 seconds of plugging in. I got the tft file now for the stock kernel and installed flashtool but it can't detect the phone (in that 10 secs), it says that driver is missing. Tried the C:\Flashtool\drivers\Flashtool-drivers.exe and selected the necessary drivers but it never succeeds. Attached the screenshot of the failure of installing the drivers.
Click to expand...
Click to collapse
You must turn off driver verification, g00gle it
Spasik said:
You must turn off driver verification, g00gle it
Click to expand...
Click to collapse
OK, I'm getting closer. Thank you so far.
So drivers are installed. Computer can detect phone. All I can't do is to boot my phone to fast boot. It's always in flash mode not fast boot. I'm trying to power on and pushing the volume down, but no go.
Code:
26/049/2015 21:49:27 - INFO - Device connected in flash mode
26/049/2015 21:49:32 - INFO - Now plug your device in Fastboot Mode
fishmong3r said:
OK, I'm getting closer. Thank you so far.
So drivers are installed. Computer can detect phone. All I can't do is to boot my phone to fast boot. It's always in flash mode not fast boot. I'm trying to power on and pushing the volume down, but no go.
Code:
26/049/2015 21:49:27 - INFO - Device connected in flash mode
26/049/2015 21:49:32 - INFO - Now plug your device in Fastboot Mode
Click to expand...
Click to collapse
you must start with phone turned off, fastboot doesnt work because you have hardlocked bootloader
pick stock ftf of your choice let it load and when it prompts you connect turned off phone with volume- pressed
then root it with towelroot and install super su, open it and update su binary
when you will be done with that contact me or respond to this post i will help you with next steps
Spasik said:
you must start with phone turned off, fastboot doesnt work because you have hardlocked bootloader
pick stock ftf of your choice let it load and when it prompts you connect turned off phone with volume- pressed
then root it with towelroot and install super su, open it and update su binary
when you will be done with that contact me or respond to this post i will help you with next steps
Click to expand...
Click to collapse
OK, to be honest I don't get any of that. What is towelroot, how to install super su and how to update its binary? Also what do you mean "let it load" (ftf)?
I have to mention that the bootloader is locked because it can't be unlocked.
fishmong3r said:
OK, to be honest I don't get any of that. What is towelroot, how to install super su and how to update its binary? Also what do you mean "let it load" (ftf)?
I have to mention that the bootloader is locked because it can't be unlocked.
Click to expand...
Click to collapse
Yeah i know that your bootloader is not unlockable, by ftf loading i mean that select .ftf you want to flash first and wait until it prepares and prompts you to connect the phone, btw last flashtool that works with sp is flashtool-0.9.18.6 , if you will have problem with understanding that try to search how to flash ftf on xperia sp on youtube i hope you will get it eventually
towelroot is an app from geohot you can get it here https://towelroot.com/ it can root your device
super su is an app on google play it is free and it controls root apps, in other words it grants or denies root access, once you will gain root with towelroot, open super su and it will prompt you to update binary just select normal and it will work
Spasik said:
Yeah i know that your bootloader is not unlockable, by ftf loading i mean that select .ftf you want to flash first and wait until it prepares and prompts you to connect the phone, btw last flashtool that works with sp is flashtool-0.9.18.6 , if you will have problem with understanding that try to search how to flash ftf on xperia sp on youtube i hope you will get it eventually
towelroot is an app from geohot you can get it here https://towelroot.com/ it can root your device
super su is an app on google play it is free and it controls root apps, in other words it grants or denies root access, once you will gain root with towelroot, open super su and it will prompt you to update binary just select normal and it will work
Click to expand...
Click to collapse
I have version 0.9.19.10. And I can't select the file before I connect the phone with fastboot. The file has to be selected after. This is the tutorial I try to follow:
https://www.youtube.com/watch?v=IXTzA7Qrrv4
So my problem is still that I can't get into fastboot to flash the kernel. So towelroot and super su are not my options until I can't get into the system.
Any other clue on how to get it flashed?
fishmong3r said:
I have version 0.9.19.10. And I can't select the file before I connect the phone with fastboot. The file has to be selected after. This is the tutorial I try to follow:
https://www.youtube.com/watch?v=IXTzA7Qrrv4
So my problem is still that I can't get into fastboot to flash the kernel. So towelroot and super su are not my options until I can't get into the system.
Any other clue on how to get it flashed?
Click to expand...
Click to collapse
you cant use fastboot with your bootloader locked that is the point there is NO WAY of flashing custom kernel with bootloader locked or you will brick your device, only way to flash kernel on lbl is to flash stock kernel in your case WITH FLASHTOOL TROUGH FLASHMODE
https://www.youtube.com/watch?v=Sz3LVw_MfzQ this may help you understand what i am trying to tell you
Spasik said:
you cant use fastboot with your bootloader locked that is the point there is NO WAY of flashing custom kernel with bootloader locked or you will brick your device, only way to flash kernel on lbl is to flash stock kernel in your case WITH FLASHTOOL TROUGH FLASHMODE
https://www.youtube.com/watch?v=Sz3LVw_MfzQ this may help you understand what i am trying to tell you
Click to expand...
Click to collapse
I understand what you are saying. But flashtool doesn't let me flash kernel in flash mode.
So it's a catch 22? After all this means that it's already bricked, isn't it?
fishmong3r said:
I understand what you are saying. But flashtool doesn't let me flash kernel in flash mode.
So it's a catch 22? After all this means that it's already bricked, isn't it?
Click to expand...
Click to collapse
You are not trying to flash kernel only, but that is possible too, you are trying to flash whole stock firmware.
Yes your phone is bricked because you flashed custom kernel on LBL.
Download some .205 or .207 firmware from android development section of xperia sp xda forum and flash it with flashtool.
There are plenty of tutorials online, i dont mean to be rude but you just must try and understand it yourself.
Here you have link for firmwares http://forum.xda-developers.com/showthread.php?t=2311964
just flash the ftf and phone should be ok, if you will be succesfull i can help you with rooting and flashing something suitable for locked bootloader xperia sp
Good luck
Spasik said:
You are not trying to flash kernel only, but that is possible too, you are trying to flash whole stock firmware.
Yes your phone is bricked because you flashed custom kernel on LBL.
Download some .205 or .207 firmware from android development section of xperia sp xda forum and flash it with flashtool.
There are plenty of tutorials online, i dont mean to be rude but you just must try and understand it yourself.
Here you have link for firmwares http://forum.xda-developers.com/showthread.php?t=2311964
just flash the ftf and phone should be ok, if you will be succesfull i can help you with rooting and flashing something suitable for locked bootloader xperia sp
Good luck
Click to expand...
Click to collapse
Wait a sec. It seems I could flash the kernel in flash mode.
It was keep disconnecting but finally the sony logo appeared and it booted to the system. It doesn't work properly, and it's very slow, but now I can get into CWM. Do you have any suggestion which ROM should I install on it?
fishmong3r said:
Wait a sec. It seems I could flash the kernel in flash mode.
It was keep disconnecting but finally the sony logo appeared and it booted to the system. It doesn't work properly, and it's very slow, but now I can get into CWM. Do you have any suggestion which ROM should I install on it?
Click to expand...
Click to collapse
yes
this is debloated stock http://forum.xda-developers.com/xperia-sp/development/rom-binomical-v1-1-final-t3111555
works great
and this is lbl cm11 http://forum.xda-developers.com/xperia-sp/development/rom-cyanogenomod-11-xperia-sp-t3041391
great aosp rom for lbl device
Spasik said:
yes
this is debloated stock http://forum.xda-developers.com/xperia-sp/development/rom-binomical-v1-1-final-t3111555
works great
and this is lbl cm11 http://forum.xda-developers.com/xperia-sp/development/rom-cyanogenomod-11-xperia-sp-t3041391
great aosp rom for lbl device
Click to expand...
Click to collapse
OK, I will do that part tomorrow. I'm a bit tired of all this sh*t.
Thank you for all your help, I do really appreciate it.
fishmong3r said:
OK, I will do that part tomorrow. I'm a bit tired of all this sh*t.
Thank you for all your help, I do really appreciate it.
Click to expand...
Click to collapse
No problem, no need to thank me just hit thanks button, I'm glad I helped you
Cannot get into recovery. Device seems to be bricked.
After Sony logo there is nothing else other than black screen. Please help me recover my device.
Don't Panic, this can easily be recovered. However the data that was inside I'm afraid is gone forever. Maybe it can be recovered maybe not, anyway I'm giving you some easy steps you can follow to recover your device.
1. Download Flashtool
2. Download the Firmware you want to load into the phone. (Search in the forum for .ftf ---make sure it is for Xperia Z --- files or you can download Xperifirm and make them on your own)
3. Once you have the .ftf file ready click on the Flash (Lightning) icon and select the firmware (.ftf) [Mode to flash is FLASHMODE]
4. When the phone is just one second from booting up (I know you are now in a cycle - loop but try as many times until you get it right), with the VOLUME DOWN button pressed connect it into the PC.
5. Wait for flash - About 10-15 min and you are done.
For any questions ask here. Good luck
I recovered my phone via Sony PC companion. Succesfuly managed to flash dual recovery again. Flashed ROM and Gappps.
This time Phone didnt start after reboot. There is not even a sony logo. No reboots at all and now it seems bricked ?
If anyone is reading please help me out.
I tried using Flashtools getting into Fastboot mode (Blue light flashing), but Flashtoool responded saying needs to installl drivers. I did that as well, but now the flashtools wont start at all.
I am trying via pc companion, Its stuck on a step where its asking me to remove my battery.. How do I recover ? Please help. Thanks in advance.
ProudRed said:
I recovered my phone via Sony PC companion. Succesfuly managed to flash dual recovery again. Flashed ROM and Gappps.
This time Phone didnt start after reboot. There is not even a sony logo. No reboots at all and now it seems bricked ?
If anyone is reading please help me out.
I tried using Flashtools getting into Fastboot mode (Blue light flashing), but Flashtoool responded saying needs to installl drivers. I did that as well, but now the flashtools wont start at all.
I am trying via pc companion, Its stuck on a step where its asking me to remove my battery.. How do I recover ? Please help. Thanks in advance.
Click to expand...
Click to collapse
Can you get to the point where the phone lights up the GREEN LED (flash mode) ?
Also what version of windows are you using?
aaronkatrini said:
Can you get to the point where the phone lights up the GREEN LED (flash mode) ?
Also what version of windows are you using?
Click to expand...
Click to collapse
Hi, Flash mode is working for me. I have recovered couple of times using flashtools in flash mode. But fastboot mode is not working for me. It says drivers are missing though I have installed drivers..
I went through tthe threads and could find a workking method to unlock the bootloader. Sony has too many appps which I do not need, I want to get rid of them as it consumes a lot of batttery. Hence a custom Rom with basic stuffs arre the soolution.
If you can help me unlock my BL I'd be thankful
And one more question, does TWRP's Latest version only works for Unlocked BL ?
ProudRed said:
Hi, Flash mode is working for me. I have recovered couple of times using flashtools in flash mode. But fastboot mode is not working for me. It says drivers are missing though I have installed drivers..
I went through tthe threads and could find a workking method to unlock the bootloader. Sony has too many appps which I do not need, I want to get rid of them as it consumes a lot of batttery. Hence a custom Rom with basic stuffs arre the soolution.
If you can help me unlock my BL I'd be thankful
And one more question, does TWRP's Latest version only works for Unlocked BL ?
Click to expand...
Click to collapse
First, Try to do things in order!!!
You are very messy, first you needed to unbrick the device, now you want to unlock its BL and want to know if you can install TWRP!
Install a stock firmware, make sure you can unlock the phone (by checking in the settings menu)...
And post some info...
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
aaronkatrini said:
First, Try to do things in order!!!
You are very messy, first you needed to unbrick the device, now you want to unlock its BL and want to know if you can install TWRP!
Install a stock firmware, make sure you can unlock the phone (by checking in the settings menu)...
And post some info...
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
Click to expand...
Click to collapse
Device unbricked, stock rom running with Root access and dual recovery installed. Fastboot drivers cant be installed, what to do ? And how to do ? OS Windows 10
All issues solved. On custom ROM now. Thank You to those who tried to help.
ProudRed said:
All issues solved. On custom ROM now. Thank You to those who tried to help.
Click to expand...
Click to collapse
Good for you, for anyone who needs to install fastboot driver on windows 10, when they cannot install they need to disable windows driver signature:
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Also for some who is in the same situation please post your solution, it helps the community.
P.S.: you can always hit that thanks button instead of thanking
I would like to know if there are custom kernels available for battery saving ? I flashed Zomie kernel and it was repeatedly booting my device into multirom recovery.
Right now I am on mokee, can I use any custom kernel with it ? If yes what ? I couldnt find many custom kernels for the device and what about Roms ? Not many custom Roms as well, only found RR and Mokee. Slim LP does not have a working link and couldnt find other popular roms too for this device.
I never tried new kernels, only thing install Kernel Adiutor and underclock, also change the governor mode.
As for the rom I use the modified stock rom by @androidexpert35, it provides good balance between performance and battery life. For any Rom you should write in their dedicated post. Keep experimenting but do it in a reasonable way and don't try to ask for everything, search and read others. Good luck
My C6903 in LP 5.1.1 doesn't take photos (or videos) when the app tries to focus. Without focus enabled (using other app) it goes perfectly. I've tried with 14.6.A.1.236 Customized BAL, 15.5.A.0.242 Movistar AR and a few more, all obtained from XperiFirm.
I tried pushing that "4k and timeshift" .zip which I read could fix the camera but no luck.
Curious thing is that Rooting Status shows "Unknown", I don't know if this could be related or not. I bought the phone on eBay (used) and I couldn't tell you if it's been unlocked or not.
But I know that everything can't be messed up because in JB 4.3 (14.2.A.1.136 Generic BAL from XperiFirm) camera works well, and Rooting Status shows "Bootloader Unlock Allowed: Yes"; And in KK 4.4 (updated via OTA from mentioned JB firmware) camera stops working in the same way but Rooting Status keeps on "Bootloader Unlock Allowed: Yes".
What could I try? I think I've already read everything related to the Rooting Status Unknown and Camera freeze problems in this forum and still have no clue (even in other Xperias forums too).
Thanks by the way
PS: Yet I didn't tried unlocking bootloader just because it may bring more problems, but if needed I would do it in a blink
matidx said:
PS: Yes I didn't tried unlocking bootloader just because it may bring more problems, but if needed I would do it in a blink
Click to expand...
Click to collapse
This is definitely a bad way to troubleshoot your problem, but go ahead and make yourself a backup of your phone's TA partition and unlock the bootloader of your phone. As long as you made a backup of the partition, the DRM keys will stay intact when you re-lock the bootloader; thus, you won't lose any exclusive Sony features upon restore. Make sure you have the proper adb and fastboot drivers before you begin.
Backup TA partition: http://forum.xda-developers.com/showthread.php?t=2292598
Unlock bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Flash any custom ROM (don't flash the Marshmallow ROMs) found in either the Android Development or Original Development page for Z1. You can also flash a modified Sony ROM in the Android Development section that has mostly all of the features in Sony's stock ROM plus some additional ones picked from CM/AOSP ROMs. Either way, if your problem is fixed, then it's a problem with the FTFs you flashed. If not, restore your TA/DRM keys (it'll re-lock your phone's bootloader) and report back.
Good luck fixing your problem!
kentexcitebot said:
This is definitely a bad way to troubleshoot your problem, but go ahead and make yourself a backup of your phone's TA partition and unlock the bootloader of your phone. As long as you made a backup of the partition, the DRM keys will stay intact when you re-lock the bootloader; thus, you won't lose any exclusive Sony features upon restore. Make sure you have the proper adb and fastboot drivers before you begin.
Backup TA partition: http://forum.xda-developers.com/showthread.php?t=2292598
Unlock bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Flash any custom ROM (don't flash the Marshmallow ROMs) found in either the Android Development or Original Development page for Z1. You can also flash a modified Sony ROM in the Android Development section that has mostly all of the features in Sony's stock ROM plus some additional ones picked from CM/AOSP ROMs. Either way, if your problem is fixed, then it's a problem with the FTFs you flashed. If not, restore your TA/DRM keys (it'll re-lock your phone's bootloader) and report back.
Good luck fixing your problem!
Click to expand...
Click to collapse
Tried that but it looks like the volume up button isn't recognized when booting or something like that. What really matters is I can't enter to fastboot mode, tried everything. Any ideas?
matidx said:
Tried that but it looks like the volume up button isn't recognized when booting or something like that. What really matters is I can't enter to fastboot mode, tried everything. Any ideas?
Click to expand...
Click to collapse
Install proper drivers for fastboot. Power the phone off completely, then while plugging your phone into the computer, hold the top volume button. You should be able to enter fastboot if fastboot drivers are properly set up.
kentexcitebot said:
Install proper drivers for fastboot. Power the phone off completely, then while plugging your phone into the computer, hold the top volume button. You should be able to enter fastboot if fastboot drivers are properly set up.
Click to expand...
Click to collapse
Is there a way to know if fastboot drivers are properly installed? I've checked and reinstalled them about 5 times, but I'll try again tomorrow just to be sure I'm not missing anything.
I don't know if there are different drivers but always installed the flashtool ones. By the way I'm running Win10 but also tried in Win7 and no luck.
matidx said:
Is there a way to know if fastboot drivers are properly installed? I've checked and reinstalled them about 5 times, but I'll try again tomorrow just to be sure I'm not missing anything.
Click to expand...
Click to collapse
If your computer can successfully detect the device and output it's serial number when you input through command prompt:
Code:
fastboot.exe devices
you'll know that fastboot is working and drivers are set up correctly. If you look at your device LED, the LED will be lit blue. Remember: you need to already have downloaded and installed the applications through the executabe in the adt folder to get the fastboot and adb applications.
matidx said:
I don't know if there are different drivers but always installed the flashtool ones. By the way I'm running Win10 but also tried in Win7 and no luck.
Click to expand...
Click to collapse
Go here to download the correct fastboot driver files: http://doomlord.xperia-files.com/download.php?dlid=Rmxhc2h0b29sLWRyaXZlcnMtMS4zLTIwMTQwMjA5
If your computer can successfully detect the device and output it's serial number when you input through command prompt:
Click to expand...
Click to collapse
Right, I know what that command line does, but that will work only when drivers are properly installed AND phone is detected. What I believe is that there are some kind of problems with the phone to not go into fastboot mode, so it wont be detected at fastboot, always in flashmode.
Is there a way to know if drivers are properly installed even if the phone isn't recognized?
Remember: you need to already have downloaded and installed the applications through the executabe in the adt folder to get the fastboot and adb applications.
Click to expand...
Click to collapse
What is the adt folder? You mean adb or the obsolete Android Development Tools (now Android Studio)?
By the way, I'm also having this issue... http://forum.xda-developers.com/xperia-z1/help/baseband-lost-reboot-t3352858
Maybe it could be related someway (like motherboard going bad or something else).
matidx said:
What is the adt folder? You mean adb or the obsolete Android Development Tools (now Android Studio)?
Click to expand...
Click to collapse
My apologies, I should've been more clear and double-checked the information!
They apparently renamed the file. I was referring "adt" to my folder that's dated all the way back to 2013, so....whoops!
You can grab the download from here: http://developer.android.com/sdk/index.html. If you don't want the entire bundle, search for "Get just the command line tools" and click on the links for your platform.
matidx said:
Right, I know what that command line does, but that will work only when drivers are properly installed AND phone is detected. What I believe is that there are some kind of problems with the phone to not go into fastboot mode, so it wont be detected at fastboot, always in flashmode.
Is there a way to know if drivers are properly installed even if the phone isn't recognized?
Click to expand...
Click to collapse
Just download the S1 driver file through the link I provided earlier, install, reboot computer, then run the same command as I told you from my previous post: if it outputs the serial number of your phone, then you're fine; but if it doesn't, post back. As long as your computer can establish a basic connection to your Z1 (PC can see it in flash mode, could access it somehow), your phone is capable of fastboot.
kentexcitebot said:
My apologies, I should've been more clear and double-checked the information!
They apparently renamed the file. I was referring "adt" to my folder that's dated all the way back to 2013, so....whoops!
You can grab the download from here: http://developer.android.com/sdk/index.html. If you don't want the entire bundle, search for "Get just the command line tools" and click on the links for your platform.
Just download the S1 driver file through the link I provided earlier, install, reboot computer, then run the same command as I told you from my previous post: if it outputs the serial number of your phone, then you're fine; but if it doesn't, post back. As long as your computer can establish a basic connection to your Z1 (PC can see it in flash mode, could access it somehow), your phone is capable of fastboot.
Click to expand...
Click to collapse
I think I've followed everything right but to be clear I'm gonna explain what I've done so far:
- Installed Android Studio (I believe it comes with those "just the command line tools").
- Installed Flashtool's driver (same as the DoomLord link you provided, even a later update than that link), also did that thing about "Disable Driver Signature Enforcement" because I'm on Win10 64bit.
- Always checked by cmd command line "fastboot.exe devices", I've never get any error (so cmd always detected it as a valid command line) or any other cmd print.
- I have a TA backup but after I made it tried to unlock bootloader but no luck. Anyway, just restored the backup and only sign I got is "Upgrading NFC firmware" or something like that after booting, the "NFC upgrade" went well but still no fastboot access.
---
- When I plug the usb + press volume up button to try get fastboot mode, phone's led goes red then green then it goes off and in flashtool I get flashmode with no led on.
---
By the way, I have an Xperia SP and already unlocked bootloader so I pretty know how it should go. Having no problem with it accessing fastboot or even locking or unlocking on the XSP.
Because of this and baseband problem, I can't stop thinking motherboard is messed up.. But anyway, whatever you think I could try just let me know.
I need to lock my bootloader to do an exchange at T-Mobile. I have 20R stock flashed, but it still says custom bootloader upon boot, how do I relock it safely?
I read that "fastboot oem lock" will work, but will brick it if I don't do it perfectly. Any advice on what to do?
TechGuruGJ said:
I need to lock my bootloader to do an exchange at T-Mobile. I have 20R stock flashed, but it still says custom bootloader upon boot, how do I relock it safely?
I read that "fastboot oem lock" will work, but will brick it if I don't do it perfectly. Any advice on what to do?
Click to expand...
Click to collapse
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
I'm terribly sorry if bumping is not ok.
Thought it wasn't worth making a new thread, since my post is about the one above.
Has anybody actually tried these steps above? (Since every other thread mentioning this says it's a one-way only thing..)
Does locking the bootloader means also loosing the custom recovery? (I'd expect that, but asking to be sure)
Does it return the phone to it's original state? (ie. before one unlocked the bootloader, or there are some differences?)
Does it also means I would be able to get official OTA updates and so on? (since with a custom recovery, that's not possible)
Thanks in advance.
Yes, it does work. I did it, worked perfectly. Yes it does return your device to it's original state. Just make sure the stock ROM is flashed and all should be well. I didn't try, but I see no reason why it wouldn't let you get OTA updates from T-Mobile. Let me know if you need help.
Nadeox1 said:
I'm terribly sorry if bumping is not ok.
Thought it wasn't worth making a new thread, since my post is about the one above.
Has anybody actually tried these steps above? (Since every other thread mentioning this says it's a one-way only thing..)
Does locking the bootloader means also loosing the custom recovery? (I'd expect that, but asking to be sure)
Does it return the phone to it's original state? (ie. before one unlocked the bootloader, or there are some differences?)
Does it also means I would be able to get official OTA updates and so on? (since with a custom recovery, that's not possible)
Thanks in advance.
Click to expand...
Click to collapse
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
raptorddd said:
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
Click to expand...
Click to collapse
Thanks both for replying.
And no @raptorddd , I did not mean that.
Your post is the only mentioning that locking the bootloader is possible, while all the other similar threads have ony people saying otherwise / it's not possible. I guess a slightly doubt is legit to have, don't take it wrongly
raptorddd said:
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
I have follow this instructions and now it giving me and error. Any fix??
WARMANH811 said:
I have follow this instructions and now it giving me and error. Any fix??
Click to expand...
Click to collapse
What error?
TechGuruGJ said:
What error?
Click to expand...
Click to collapse
Secure booting Error!
Error code: 1003
MODIFIED ! !
WARMANH811 said:
Secure booting Error!
Error code: 1003
MODIFIED ! !
Click to expand...
Click to collapse
are you sure you have h811.? i did not get that error ive tried this twice..
i remeber getting an security boot error on LG G2 i fix by flashing firmware .. so maybe KDZ could help..
if not am not sure then search for that error and find out how to fix.
raptorddd said:
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
My H811 T-mobile phone needs service. It has original 20v software version. It is unlocked with TWRP and rooted. Can I use this method? Do I first have to downgrade software to some other version? Will this method also take out TWRP and root or do I still have to take them out before doing this? How? Please help.
joecandle said:
My H811 T-mobile phone needs service. It has original 20v software version. It is unlocked with TWRP and rooted. Can I use this method? Do I first have to downgrade software to some other version? Will this method also take out TWRP and root or do I still have to take them out before doing this? How? Please help.
Click to expand...
Click to collapse
no need to downgrade. to remove root and any trace if phone works. is to use KDZ then once it boots into system do the lock procedure. so it locks and the small white letter are removed. this way its like stock rom and recovery and the above commmands will make bootloader locked. and sent to repair. if bootloops try the freezing method.
Used on an LG Aristo that has Cyanogen and it worked
raptorddd said:
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
Click to expand...
Click to collapse
This was the only one i found that didnt brick my phone and trust me ive bricked and unbricked this phone many times
When you use the fastboot command to lock back your bootloader, the phone doesn't revert automatically to the stock recovery and actually that is partly the reason why it bricks and other main reason is that changes made to bootloader to obtain root brick the phone. before you relock bootloader, if you have SuperSU (in-app menu option) or Magisk (uninstall zip file), use their respective methods to unroot the phone, then use twrp to flash .image file of stock recovery to recovery partition then use the fastboot command to lock the bootloader. Even then it may or may not work because if whatever method the phone uses to check the integrity of bootloader and/or recovery, such as md5, if it doesn't match, the phone will still brick. Since all your data on phone will be erased regardless as soon as you lock the bootloader, i personally just fastboot lock the bootloader, remove battery to power down, use the volume up and plug usb cable in from pc to put phone in download mode and just use LGUP (uppercut) if have kdz file already, which i do, i just let LG Bridge download the file, find it in programs folder and copy it to another location before LG Bridge deletes it --OR-- just use error recovery option in Software Update tab in LG Bridge as both LGUP and LG Bridge will detect the phone in download mode even if it is bricked.
By the way, I have used both methods above dozens of times without any issues, someone above who mentioned phone boot-looping because of locking the bootloader, it is boot-looping not because of hardware flaw which was widespread in LG G3 but a software issue (phone boots up, doesn't find the software configuration it is looking for and just restarts) and they are not the same issues, no need to freeze the phone, won't help.
the method works, but no OTA from T-Mobile. "verification problem".
When I try to "adb reboot bootloader" I get "security error".
If I try reboot recovery, TWRP is definitely not there.
Just want to update from20Q to 20X.
Any help would be appreciated.
metropical said:
the method works, but no OTA from T-Mobile. "verification problem".
When I try to "adb reboot bootloader" I get "security error".
If I try reboot recovery, TWRP is definitely not there.
Just want to update from20Q to 20X.
Any help would be appreciated.
Click to expand...
Click to collapse
The above points to you not giving permission possibly because either you missed the permission pop-up or selected option that didn't allow permission.
Can anyone help me?
When i unlock bootloader on my lg velvet 4g the fingerprint stop working so i want to relock. But when i put this on cmd "adb reboot bootloader" it only restarts my phone. Doesnt shows me the bootloader menu it only restarts normaly
Lukasz23 said:
Can anyone help me?
When i unlock bootloader on my lg velvet 4g the fingerprint stop working so i want to relock. But when i put this on cmd "adb reboot bootloader" it only restarts my phone. Doesnt shows me the bootloader menu it only restarts normaly
Click to expand...
Click to collapse
managed to solve?