Edit: problem solved someone remove this thread.. I dont know where the delete button is D
I'm pretty sure there is not much I can do anymore... I don't have an os installed because I couldn't restore it (I coulnd't restore the data..). I'm stuck in twrp and it doesn't recognize sd card. The files in my internal storage are all corrupted. Is my phone now fully bricked? Is there a way to make the phone recognize the sd card? Also I cannot move files from my pc to phone..
Fisuxcel said:
I'm pretty sure there is not much I can do anymore... I don't have an os installed because I couldn't restore it (I coulnd't restore the data..). I'm stuck in twrp and it doesn't recognize sd card. The files in my internal storage are all corrupted. Is my phone now fully bricked? Is there a way to make the phone recognize the sd card?
Click to expand...
Click to collapse
Use the flashtool to restore the system.
umm I don't think I can..
SXUsr said:
Use the flashtool to restore the system.
Click to expand...
Click to collapse
because of this...
No usb device with vid:0x0fce pid:0xb00b !
Press any key to continue . . .
Fisuxcel said:
because of this...
No usb device with vid:0x0fce pid:0xb00b !
Press any key to continue . . .
Click to expand...
Click to collapse
Try Sony EMMA.
nope, doesnt work
asks to connect a phone when I connect it. My pc recognizes the phone but as I said the files are corrupted.
Fisuxcel said:
asks to connect a phone when I connect it. My pc recognizes the phone but as I said the files are corrupted.
Click to expand...
Click to collapse
https://postimg.cc/G45ssGzW
Fisuxcel said:
https://postimg.cc/G45ssGzW
Click to expand...
Click to collapse
Can I boot to bootloader if I don't have an os?
Fisuxcel said:
asks to connect a phone when I connect it. My pc recognizes the phone but as I said the files are corrupted.
Click to expand...
Click to collapse
You've connected it in flash mode?
SXUsr said:
You've connected it in flash mode?
Click to expand...
Click to collapse
doesnt work, I cant let the pc access my phone if I dont have an os. And yes its in flash mode now. You know its supposed to ask for the fingeprint but I cant accept it as long as I cant access the os.
Fisuxcel said:
doesnt work, I cant let the pc access my phone if I dont have an os. And yes its in flash mode now.
Click to expand...
Click to collapse
Your problem now is getting an OS back on the phone. The screenshot you've posted shows it's not in flash mode whilst EMMA is running, so what does EMMA do when you connect it in flash mode when prompted? Restoring the phone with the Flashtool, Newflasher or EMMA shouldn't be this difficult.
SXUsr said:
Your problem now is getting an OS back on the phone. The screenshot you've posted shows it's not in flash mode whilst EMMA is running, so what does EMMA do when you connect it in flash mode when prompted? Restoring the phone with the Flashtool, Newflasher or EMMA shouldn't be this difficult.
Click to expand...
Click to collapse
Umm.. I think I'm in the starting point again..
your device software can't be checked for corruption please lock the bootloader. Stuck in bootloop. I tried to install firmware through EMMA (didnt get any errors so I thought it had installed the firmware). Tried newflasher
got this error:
ERROR: Error CreateFile! failed with error code 5 as follows:
Access is denied.
I when I broke my phone I accidentally flashed wrong firmware, this. Thanks for helping me!
Fisuxcel said:
I when I broke my phone I accidentally flashed wrong firmware, this. Thanks for helping me!
Click to expand...
Click to collapse
Try flashing a XZ1C boot.img with fastboot and try EMMA again.
still not working...
SXUsr said:
Try flashing a XZ1C boot.img with fastboot and try EMMA again.
Click to expand...
Click to collapse
I dunno maybe I just can't use EMMA but it doesnt seem to flash anything.. (phone in flash mode, EMMA doesnt report any problems but when I boot up it bootloops probably because there is no os installed) I was able to flash lineage os (that I had previously installed) but when I tried to set up it all apps crashed and it rebooted.. also I have one back up of the stock rom but twrp would give me some error 255...
Fisuxcel said:
I dunno maybe I just can't use EMMA but it doesnt seem to flash anything.. (phone in flash mode, EMMA doesnt report any problems.
Click to expand...
Click to collapse
What does it do??? Again, it shouldn't be this hard. The phone clearly isn't bricked so user error is at play here.
Fisuxcel said:
I dunno maybe I just can't use EMMA but it doesnt seem to flash anything.. (phone in flash mode, EMMA doesnt report any problems but when I boot up it bootloops probably because there is no os installed) I was able to flash lineage os (that I had previously installed) but when I tried to set up it all apps crashed and it rebooted.. also I have one back up of the stock rom but twrp would give me some error 255...
Click to expand...
Click to collapse
If you're able to flash Lineage why can't you use Flash Tool to wipe the device, flash stock firmware and start over? The device is not bricked.
How to update
betacrypt said:
If you're able to flash Lineage why can't you use Flash Tool to wipe the device, flash stock firmware and start over? The device is not bricked.
Click to expand...
Click to collapse
Now that I have stock rom how do I update it to pie? Last time I flashed lineage os the camera broke.. I would like to run lineage os with working camera...
Fisuxcel said:
Now that I have stock rom how do I update it to pie? Last time I flashed lineage os the camera broke.. I would like to run lineage os with working camera...
Click to expand...
Click to collapse
If you're on the latest stock rom, you're already running Pie. Make sure you're on the latest.
The camera works well on Lineage 16 so you shouldn't be having issues. I would flash the latest stock firmware in Flash Tool. Then flash TWRP , and in TWRP flash the latest version of LOS 16. I'm running it currently and don't have any issues.
lol where is the delete button DD
nevermind
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.
Hi
Yesterday my phone dead? Reloop after sony logo, i cant go to recovery. (before i had Ressurection 5.0.2 rom)
Later i flashed boot.img for lollipop and phone booted with charger, but mt wifi don't worked and i tired to install another rom with cwm.
Later idk how my recovery changed to Cyanogenmod Recovery and i cant do anything
Now i flashed unrooted stock .tft and i still have loops.
When i try to flash boot.img i have problem with writing :
sending 'boot' (10182 KB)...
OKAY [ 0.337s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.339s
Click to expand...
Click to collapse
I have warranty but idk do I have to give my phone to service.
What i have to do?
m1ko8 said:
Hi
Yesterday my phone dead? Reloop after sony logo, i cant go to recovery. (before i had Ressurection 5.0.2 rom)
Later i flashed boot.img for lollipop and phone booted with charger, but mt wifi don't worked and i tired to install another rom with cwm.
Later idk how my recovery changed to Cyanogenmod Recovery and i cant do anything
Now i flashed unrooted stock .tft and i still have loops.
When i try to flash boot.img i have problem with writing :
I have warranty but idk do I have to give my phone to service.
What i have to do?
Click to expand...
Click to collapse
Well, sad to say, but you don't have the warranty anymore, as you have unlocked your bootloader, within erasing all your DRM keys (ironic, I know).
But if you have a TA-Partition backup, then you could just push in, (just be sure before pushing TA to flash stock .ftf with its kernel) and your DRM keys are back. Then you could proceed futher for warranty service.
Firstly, if you don't want go to warranty, try to flash Pabx Lollipo (it's stock lollipop). After that you could check if it has been fixed and flashing commands are properly working
LaurynasVP said:
Well, sad to say, but you don't have the warranty anymore, as you have unlocked your bootloader, within erasing all your DRM keys (ironic, I know).
But if you have a TA-Partition backup, then you could just push in, (just be sure before pushing TA to flash stock .ftf with its kernel) and your DRM keys are back. Then you could proceed futher for warranty service.
Firstly, if you don't want go to warranty, try to flash Pabx Lollipo (it's stock lollipop). After that you could check if it has been fixed and flashing commands are properly working
Click to expand...
Click to collapse
DRM keys ? What is that?
I locked bootloader before and deleted all files accidentally
How to flash this file?<--- nvm
Can i flash userdata.img in flashtool? Idk why fastboot dont work in cmd .-.
Edit2: After flash Unrooted ftf PC Companion accepted my phone and now my phone is repairing, i will write later does it works.
Edit3: PC companion repair dont work too.
m1ko8 said:
DRM keys ? What is that?
I locked bootloader before and deleted all files accidentally
How to flash this file?<--- nvm
Can i flash userdata.img in flashtool? Idk why fastboot dont work in cmd .-.
Edit2: After flash Unrooted ftf PC Companion accepted my phone and now my phone is repairing, i will write later does it works.
Edit3: PC companion repair dont work too.
Click to expand...
Click to collapse
DRM keys are stored in your TA-Partition, they're required for many functions to work: Clear audio, Camera functions, Official ROM and it's updates (If i'm right with this one) and other.
I recommend you to download android SDK, then go to it --> Platform tools --> SHIFT + RMB (right mouse button) --> Open Command Prompt Here.
After that, shut down your phone. Wait atleast 30 seconds. then by holding Vol +, plug it into PC. Blue LED should show up.
Then in CMD type this:
fastboot devices
Click to expand...
Click to collapse
It should be returned some numbers and letters. If it doesn't show anything, then your windows maybe doesn't support fastboot or you don't have drivers to that (fastboot + adb drivers).
Make sure in this folders are fastboot.exe and adb.exe (the most importantly to us is fastboot.exe) and some other files as well.
If ir returns information correctly, then you can download any rom and extract it (I sugges you to use Pabx).
Extract everything from .ZIP/.RAR, you should see system.img, boot.img, userdata.img. Place them into platform-tools directory (where fastboot.exe and other files are).
Then simply write these commands in CMD:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
Click to expand...
Click to collapse
If everything will go OK, then you can reboot your device:
fastboot reboot
Click to expand...
Click to collapse
Then your phone should start normally, after that you can manually install CWM and other things either.
If it didn't work, just quote me regarding the problem, I'll try to help you
LaurynasVP said:
DRM keys are stored in your TA-Partition, they're required for many functions to work: Clear audio, Camera functions, Official ROM and it's updates (If i'm right with this one) and other.
I recommend you to download android SDK, then go to it --> Platform tools --> SHIFT + RMB (right mouse button) --> Open Command Prompt Here.
After that, shut down your phone. Wait atleast 30 seconds. then by holding Vol +, plug it into PC. Blue LED should show up.
Then in CMD type this:
It should be returned some numbers and letters. If it doesn't show anything, then your windows maybe doesn't support fastboot or you don't have drivers to that (fastboot + adb drivers).
Make sure in this folders are fastboot.exe and adb.exe (the most importantly to us is fastboot.exe) and some other files as well.
If ir returns information correctly, then you can download any rom and extract it (I sugges you to use Pabx).
Extract everything from .ZIP/.RAR, you should see system.img, boot.img, userdata.img. Place them into platform-tools directory (where fastboot.exe and other files are).
Then simply write these commands in CMD:
If everything will go OK, then you can reboot your device:
Then your phone should start normally, after that you can manually install CWM and other things either.
If it didn't work, just quote me regarding the problem, I'll try to help you
Click to expand...
Click to collapse
Thanks, i know how to use fastboot but xperia dont charge. I will do everything what u said for a while and i leave edit.
btw. Thanks
Edit: Idk it's important but before it in android 5.0.2 Ressurection ROM sometimes it turn off without charger plugged , i think it was ROM fail
Edit1: Do you think it's better solution than SUS repair?
Edit2:After flash tired to turn on phone but red led blinked 3 times , then i connect phone to charger and red led blinks every 1-2 second. What i have to do?
@m1ko8
Don't be panic
download latest z fw .292 ftf then download flashtool and install it and goto C>flashtool>drivers install that file,then put downloaded ftf to firmware folder ,after run flastool and click thunder icon select flashmode select fw and wait prepairing then connect device when notify popup massage.then progress bar fill when it end disconnect cable and power on ur device
Isuru cs said:
@m1ko8
Don't be panic
download latest z fw .292 ftf then download flashtool and install it and goto C>flashtool>drivers install that file,then put downloaded ftf to firmware folder ,after run flastool and click thunder icon select flashmode select fw and wait prepairing then connect device when notify popup massage.then progress bar fill when it end disconnect cable and power on ur device
Click to expand...
Click to collapse
When I try to install this drivers with checked fastboot and flashtool drivers "Installation failed" for both drivers.
After install FTF my phone still stuck on sony logo and restart , its important what firmware i install? (region?) I have from Play in Poland then i must install Firmware Play PL ? I installed Firmware UK and RU and EU . still i have bootloop.
I tired too repair with pc companion. hmm.. bad luck, today probably i will give my phone to service
m1ko8 said:
When I try to install this drivers with checked fastboot and flashtool drivers "Installation failed" for both drivers.
After install FTF my phone still stuck on sony logo and restart , its important what firmware i install? (region?) I have from Play in Poland then i must install Firmware Play PL ? I installed Firmware UK and RU and EU . still i have bootloop.
I tired too repair with pc companion. hmm.. bad luck, today probably i will give my phone to service
Click to expand...
Click to collapse
I'm sorry to tell you, but you phone doesn't have warranty anymore and specilized Sony staff won't take it for fixing, as you have unlocked your bootloader, so you need take it to local repair service (Sony might fix it, but with some price of course).
Either way, you can try install drivers on other computer, if you have one, then try on it.
LaurynasVP said:
I'm sorry to tell you, but you phone doesn't have warranty anymore and specilized Sony staff won't take it for fixing, as you have unlocked your bootloader, so you need take it to local repair service (Sony might fix it, but with some price of course).
Either way, you can try install drivers on other computer, if you have one, then try on it.
Click to expand...
Click to collapse
I locked bootloader before. Repair with PC companion. Bootloader is locked and when i unlocked it (have unlock code) after reconnect fastboot it was locked again. idk how I think they can't see it cause its power and software problem and service give me new phone . They can see i had unlocked bootloader ?
I think something inside phone overheated and i dont thinnk so does Polish service see it
m1ko8 said:
I locked bootloader before. They can see it?
I think something inside phone overheated and i dont thinnk so does Polish service see it
Click to expand...
Click to collapse
Yeah, if your phone is psychical damage (overheated) and doesn't turn on, then they may change it for you to another one, but If they will bring the life back to it, they would be able to see if DRM keys are in their place, and even if you've re-locked your BL, it doesn't change the situation at all, because in the service menu they could check if DRM keys are not erased, if so - they will not fix it under the warranty
LaurynasVP said:
Yeah, if your phone is psychical damage (overheated) and doesn't turn on, then they may change it for you to another one, but If they will bring the life back to it, they would be able to see if DRM keys are in their place, and even if you've re-locked your BL, it doesn't change the situation at all, because in the service menu they could check if DRM keys are not erased, if so - they will not fix it under the warranty
Click to expand...
Click to collapse
2 days ago my phone stay in my bed at night witch charger and he was very hot. Later i dont turn it on again.
Yesterday i connected my phone to charger and he dont charging. I can go to flashmode and fastboot .Installing system throught fastboot , pc companion repair dont worked. I think they are too lazy to check it.
I have no choice , money is no problem anyway i must repair it
Edit: Now wait ~2 weeks >.<
LaurynasVP said:
Yeah, if your phone is psychical damage (overheated) and doesn't turn on, then they may change it for you to another one, but If they will bring the life back to it, they would be able to see if DRM keys are in their place, and even if you've re-locked your BL, it doesn't change the situation at all, because in the service menu they could check if DRM keys are not erased, if so - they will not fix it under the warranty
Click to expand...
Click to collapse
Some news
Service gave me new Xperia Z (under warranty ofc)
m1ko8 said:
Some news
Service gave me new Xperia Z (under warranty ofc)
Click to expand...
Click to collapse
Cool! I'm happy for you!
And try to not harm your phone anymore, make care of it
LaurynasVP said:
Cool! I'm happy for you!
And try to not harm your phone anymore, make care of it
Click to expand...
Click to collapse
They informed me about motherboard repair. But they gave me new phone
Now i have Android 5.1 and unlocked bootloader But i will take care of my phone .
But.. what ROM You recommend for nice look and smooth work ( You like lollipop? )
They gave you a new z with lollipop preinstalled? Or did you flash a custom rom?
shoey63 said:
They gave you a new z with lollipop preinstalled? Or did you flash a custom rom?
Click to expand...
Click to collapse
Dont be funny OFC I flashed .
m1ko8 said:
They informed me about motherboard repair. But they gave me new phone
Now i have Android 5.1 and unlocked bootloader But i will take care of my phone .
But.. what ROM You recommend for nice look and smooth work ( You like lollipop? )
Click to expand...
Click to collapse
@m1k8 I suggest you to use Validus ROM. Just now I'm waiting for 5.1 update @shoey63 - of course he has phone with an unlocked bootloader, even he said so, that means he just pre-installed it by himself
LaurynasVP said:
@m1k8 I suggest you to use Validus ROM. Just now I'm waiting for 5.1 update @shoey63 - of course he has phone with an unlocked bootloader, even he said so, that means he just pre-installed it by himself
Click to expand...
Click to collapse
What version ? Validus-LP-v7.0-2015-03-09 or Validus-LP-v7.0-2015-03-11? ( New version not always is better)
m1ko8 said:
What version ? Validus-LP-v7.0-2015-03-09 or Validus-LP-v7.0-2015-03-11? ( New version not always is better)
Click to expand...
Click to collapse
09-03 for now. I'm not sure which version was perfect working, as the newest 03-11 isn't working properly as it should to.
Now I'm waiting for the update to 5.1.. I do know that from 03-08 there will be lots of bugs : screen always on, even if you turn of it just will turn to grey color, that's all, ambient auto display doesn't work either and some other problems.
So, I suggest you to try only from 03-03 to 03-08
LaurynasVP said:
09-03 for now. I'm not sure which version was perfect working, as the newest 03-11 isn't working properly as it should to.
Now I'm waiting for the update to 5.1.. I do know that from 03-08 there will be lots of bugs : screen always on, even if you turn of it just will turn to grey color, that's all, ambient auto display doesn't work either and some other problems.
So, I suggest you to try only from 03-03 to 03-08
Click to expand...
Click to collapse
Understand
So , I decided to install ressurection ROM , and work perfect ( Validus rom is dark , i dont like dark themes and have some bugs , Ressurection is for me much better. )
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
hi i'm having problems, for some reason my phone isn't recognised in cmd. it shows up normally under my computer and can transfer files but i can't flash twrp to it (yes the bootloader is unlocked). when i type ''adb devices'' it never shows. not sure what to do here i'm stuck.
Usb debugging enabled?
billybrownbear said:
hi i'm having problems, for some reason my phone isn't recognised in cmd. it shows up normally under my computer and can transfer files but i can't flash twrp to it (yes the bootloader is unlocked). when i type ''adb devices'' it never shows. not sure what to do here i'm stuck.
Click to expand...
Click to collapse
You must have missed to install required drivers for adb and fastboot..
yes usb debugging is enabled
i don't think i have
melmarPH said:
You must have missed to install required drivers for adb and fastboot..
Click to expand...
Click to collapse
i'll put a screenshot up of all the files i got for this (using imgur cause don't know how to upload photo)
https://imgur.com/a/waNSRoy
https://imgur.com/a/6jpyOpj
i'm lost for ideas here, if anyone has more ideas it'd be greatly appreciated
billybrownbear said:
i'll put a screenshot up of all the files i got for this (using imgur cause don't know how to upload photo)
https://imgur.com/a/waNSRoy
https://imgur.com/a/6jpyOpj
Click to expand...
Click to collapse
Looks like ADB doesn't recognize your device. Meaning there is no driver as to where the computer can communicate with your phone. You first have to install adb drivers to get it to work the way it should.
Try this: https://forum.xda-developers.com/showthread.php?t=2588979
melmarPH said:
Looks like ADB doesn't recognize your device. Meaning there is no driver as to where the computer can communicate with your phone. You first have to install adb drivers to get it to work the way it should.
Try this: https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
okay mad, you're my man <3
you sent me on the right path, if you or anyone want to know what was wrong i'll explain it here
adb driver wasn't properly installed i had to manually install it on the device manager. the second issue i had was misc.bin didn't come with any of the downloads so i had to download that from somewhere else then flash it. after that twrp installed successfully. when i flashed the custom rom i wasn't able to reboot the system it would just go back to twrp. after removing the sim it worked then i just put the sim back in, and now everything is working well. thanks for your help
billybrownbear said:
okay mad, you're my man <3
you sent me on the right path, if you or anyone want to know what was wrong i'll explain it here
adb driver wasn't properly installed i had to manually install it on the device manager. the second issue i had was misc.bin didn't come with any of the downloads so i had to download that from somewhere else then flash it. after that twrp installed successfully. when i flashed the custom rom i wasn't able to reboot the system it would just go back to twrp. after removing the sim it worked then i just put the sim back in, and now everything is working well. thanks for your help
Click to expand...
Click to collapse
Sounds good! May I know exactly which rom did you flash? Was it the LOS GSI?
melmarPH said:
Sounds good! May I know exactly which rom did you flash? Was it the LOS GSI?
Click to expand...
Click to collapse
no i might wait until LOS gets a stable rom before i go for that. right now i've flashed the global MIUI 10.3.12.0 rom and it's working well
So using a root app disabler I disabled "telephony service" and when I restarted it shutdown immediately, on the newest WW rom it doesnt have a recovery so I cant go in there and wipe to factory reset. Right now I'm getting slot_b is unbootable. My computer recognizes the phone as "Android Bootloader Interface" but when I run "adb devices" it doesnt show up and I cant run fastboot commands even though I'm plugged into the side usb port. Please help me.
trustedenemy said:
So using a root app disabler I disabled "telephony service" and when I restarted it shutdown immediately, on the newest WW rom it doesnt have a recovery so I cant go in there and wipe to factory reset. Right now I'm getting slot_b is unbootable. My computer recognizes the phone as "Android Bootloader Interface" but when I run "adb devices" it doesnt show up and I cant run fastboot commands even though I'm plugged into the side usb port. Please help me.
Click to expand...
Click to collapse
Was the boot img rooted, is that why you have no recovery? If so, just boot to fastboot mode and flash stock boot instead of root, that should have recovery
trustedenemy said:
So using a root app disabler I disabled "telephony service" and when I restarted it shutdown immediately, on the newest WW rom it doesnt have a recovery so I cant go in there and wipe to factory reset. Right now I'm getting slot_b is unbootable. My computer recognizes the phone as "Android Bootloader Interface" but when I run "adb devices" it doesnt show up and I cant run fastboot commands even though I'm plugged into the side usb port. Please help me.
Click to expand...
Click to collapse
Can you go to bootloader screen ?
If you can
Just use the full stock Rom
Flash it
---------- Post added at 04:45 PM ---------- Previous post was at 04:42 PM ----------
https://drive.google.com/file/d/1M2V1Jh2CS5vt1xbQYlDvhxfu0yB6hmZi/view
Download the Full Rom
Extract it
Use the exe file to install with bootloader screen
Ok that was able to get me back to recovery, I tried to wipe and then boot into android, didn't work got the "your device is corrupt and cannot be trusted and will not boot". Still isn't recognized in adb devices so I don't know how I would proceed from here. My device is the Tencent Edition if that helps with raw firmware/rom.
P.S Thank you guys so much for your help I really appreciate it.
trustedenemy said:
Ok that was able to get me back to recovery, I tried to wipe and then boot into android, didn't work got the "your device is corrupt and cannot be trusted and will not boot". Still isn't recognized in adb devices so I don't know how I would proceed from here. My device is the Tencent Edition if that helps with raw firmware/rom.
P.S Thank you guys so much for your help I really appreciate it.
Click to expand...
Click to collapse
Did you fix it ?
rowihel2012 said:
Did you fix it ?
Click to expand...
Click to collapse
No, I still cannot boot into android and it still isnt recognized in adb devices, but I can get into recovery now.
trustedenemy said:
No, I still cannot boot into android and it still isnt recognized in adb devices, but I can get into recovery now.
Click to expand...
Click to collapse
But you get fastboot mode, just plug the USB in side port and flash latest raw WW Rom.
Here's the link to 1908.21
https://drive.google.com/file/d/13Mgz9GhopE-DUsGT3N_5qC283cKkUxYb/view?usp=drivesdk
Once in fastboot mode (the first menu you see, before selecting recovery, start, power off etc is fastboot mode) check your device is recognised with fastboot devices cmd and then run flashall_AFT.cmd that'll get back your working rom . But also, delete or move the original zip from that same extracted folder, the raw rom with the same name confuses the flashall_AFT.cmd
So I flash the most recent firmware you linked and double checked in recovery that it was pushed to the device and it was, but when I try to boot into android I get the asus logo for a second and then it restarts and it will give me a screen that says "Your device is corrupt. It cant be trusted and will not boot" and then has a link to google support .
trustedenemy said:
So I flash the most recent firmware you linked and double checked in recovery that it was pushed to the device and it was, but when I try to boot into android I get the asus logo for a second and then it restarts and it will give me a screen that says "Your device is corrupt. It cant be trusted and will not boot" and then has a link to google support .
Click to expand...
Click to collapse
Did you let the raw rom flash entirely? It should take a minimum of 10 minutes... The phone should reboot twice (I think) as it completes... Maybe try again, but I'm not familiar with that message...
If the phone doesn't reboot, I would let it run for a half hour or so before rebooting...
There we go, I got it to work man, I was just being impatient with the firmware flash but now I got it to work I appreciate your help and patience so much let me got through and thank your comments and then you can flag a mod to take down this thread. Thank you
trustedenemy said:
There we go, I got it to work man, I was just being impatient with the firmware flash but now I got it to work I appreciate your help and patience so much let me got through and thank your comments and then you can flag a mod to take down this thread. Thank you
Click to expand...
Click to collapse
Excellent, glad you got it working again
trustedenemy said:
There we go, I got it to work man, I was just being impatient with the firmware flash but now I got it to work I appreciate your help and patience so much let me got through and thank your comments and then you can flag a mod to take down this thread. Thank you
Click to expand...
Click to collapse
Yes this way always fix bootloap problem
Thanks asus for this easy flashing