Hello,
I just jumped on a good deal for Xperia Z5 (E5823) with software issue. Device boots up to the Xperia logo screen and hags there. I am preparing myself for flashing but hoping a simple hard reset might solve the problem. What should my steps be? I already downloaded Flashtool and did some reading on the forum to get myself familiar with the process. Looks like I will need to download FTF file (I am in US, prefer to have unbranded with minimal carrier bloat) and can use your advice on which version/file to start with. Ideally I would want to root as well, but for now more concerned about restoring back to stock. I did read that Lollipop has a better performance, but open to suggestions for whatever is easier/stable. Any guidance/advice is appreciated (with links to tools or downloads if avail). Is there a way to tell what version # along with region/customization I have installed now?! Should I try the Sony Companion software?
For the record, I have successfully flashed custom ROMS on various Samsung/LG devices, as well as Nexus 4/5. Therefore, feel pretty confident this should not be impossible or any harder. Thanks A LOT.
An update after spending few hours yesterday. PC Companion doesn't recognize the phone when attempting to repair (Vol down + insert USB). It did install few drivers when connected to PC, and it looks like the phone does go into flashmode (as indicated by LED staying green). Then tried the Flashtool, created FTF file (based on tutorial at XperiaBlog) and again the same thing, can't get the phone to be recognized in flashmode. It does respond in fastboot mode and able to get some identifying information. I couldn't find any information on how to flash system, kernel, etc through fastboot (was hoping to use the Flashtool FastBoot mode option, but picking corresponding SIN files resulted is fail errors). I am afraid that flashmode might not work for me as the phone might not have USB debugging enabled (not sure what was done to it and who had it prior).
Are the other alternatives/methods I should try? I wish there was a way to send flash commands from ADB command prompt (like with Nexus phones) and from fastboot mode. Any ideas? Really love the phone, though and want to get it repaired to replace my huge LG! Thanks everyone.
coolmen777 said:
An update after spending few hours yesterday. PC Companion doesn't recognize the phone when attempting to repair (Vol down + insert USB). It did install few drivers when connected to PC, and it looks like the phone does go into flashmode (as indicated by LED staying green). Then tried the Flashtool, created FTF file (based on tutorial at XperiaBlog) and again the same thing, can't get the phone to be recognized in flashmode. It does respond in fastboot mode and able to get some identifying information. I couldn't find any information on how to flash system, kernel, etc through fastboot (was hoping to use the Flashtool FastBoot mode option, but picking corresponding SIN files resulted is fail errors). I am afraid that flashmode might not work for me as the phone might not have USB debugging enabled (not sure what was done to it and who had it prior).
Are the other alternatives/methods I should try? I wish there was a way to send flash commands from ADB command prompt (like with Nexus phones) and from fastboot mode. Any ideas? Really love the phone, though and want to get it repaired to replace my huge LG! Thanks everyone.
Click to expand...
Click to collapse
Why couldn't you use adb? I use it to flash the recovery every once in a while, I hate flash tool. It took me a good 4 different PCs before I found one it would work on
civicsr2cool said:
Why couldn't you use adb? I use it to flash the recovery every once in a while, I hate flash tool. It took me a good 4 different PCs before I found one it would work on
Click to expand...
Click to collapse
I gladly would, except that I am not very comfortable using it due to lack of experience and available zips for my Z5 compact. Can you point me to that info and how to make zips to flash and what to start with? I am willing to try it.
Also, how can I check if my boot loader is unlocked? Can't seemed to find a command to use. Thanks again.
Any pointers for zips or how to flash a rom through fastboot? Thanks.
coolmen777 said:
Any pointers for zips or how to flash a rom through fastboot? Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2277112
We have a couple aosp Roms available to flash, I'd try cm13. I don't know if you've tried to unlock your bootloader yet or not but you should try that. You could also try flashing zombie kernal and see if that'd boot up.
civicsr2cool said:
Why couldn't you use adb? I use it to flash the recovery every once in a while, I hate flash tool. It took me a good 4 different PCs before I found one it would work on
Click to expand...
Click to collapse
civicsr2cool said:
http://forum.xda-developers.com/showthread.php?t=2277112
We have a couple aosp Roms available to flash, I'd try cm13. I don't know if you've tried to unlock your bootloader yet or not but you should try that. You could also try flashing zombie kernal and see if that'd boot up.
Click to expand...
Click to collapse
Thanks for the reply and guidance. I would prefer to stick with Stock Xperia software and launcher. From my experience, CM tends to be buggy and I need full stable functionality with max battery (hoping to give Stamina a test). I am not sure if the bootloader is unlocked and don't want to mess with it unless I absolutely have to (does unlocking BL still messes with DRM keys for camera processing?) Wish I could see if it is unlocked somehow, maybe someone tried to flash/root it and messed up the bootloader somehow.
I will look at zombie kernel (does it need unlocked bootloader or recovery to flash, will it work with stock ROM?) Thanks again for your help.
coolmen777 said:
Thanks for the reply and guidance. I would prefer to stick with Stock Xperia software and launcher. From my experience, CM tends to be buggy and I need full stable functionality with max battery (hoping to give Stamina a test). I am not sure if the bootloader is unlocked and don't want to mess with it unless I absolutely have to (does unlocking BL still messes with DRM keys for camera processing?) Wish I could see if it is unlocked somehow, maybe someone tried to flash/root it and messed up the bootloader somehow.
I will look at zombie kernel (does it need unlocked bootloader or recovery to flash, will it work with stock ROM?) Thanks again for your help.
Click to expand...
Click to collapse
I'm only trying to suggest things that could get the phone working again not permanent solutions lol I don't run cm13 yet as it's definitely not refined. Flashing a stock ftf should be able to bring you to complete original specs without unlocking bootloader or anything.
civicsr2cool said:
I'm only trying to suggest things that could get the phone working again not permanent solutions lol I don't run cm13 yet as it's definitely not refined. Flashing a stock ftf should be able to bring you to complete original specs without unlocking bootloader or anything.
Click to expand...
Click to collapse
Lol, I understand now. It looks like the bootloader might still be locked as I am unable to flash zombie kernel (command: "fastboot flash boot boot.img" results in sending OK, but Failed: remote command not allowed). Looks like I am stuck to trying to unlock a bootloader to keep trying to revive the phone. Just bothers me that I can't get into Flashmode (even after installing drivers that come with Flashtool). Could this be because the phone might not have USB debugging enabled? Is there a way to try to flash the stock through fastboot (as zip) instead of ftf?
My big concern is loosing TA partition and associated DRM keys (any way to back it up from fastboot or toolkit?). Or is that not a factor with the hack available now? Sorry for all these questions, just getting more and more frustrated with this.
coolmen777 said:
Lol, I understand now. It looks like the bootloader might still be locked as I am unable to flash zombie kernel (command: "fastboot flash boot boot.img" results in sending OK, but Failed: remote command not allowed). Looks like I am stuck to trying to unlock a bootloader to keep trying to revive the phone. Just bothers me that I can't get into Flashmode (even after installing drivers that come with Flashtool). Could this be because the phone might not have USB debugging enabled? Is there a way to try to flash the stock through fastboot (as zip) instead of ftf?
My big concern is loosing TA partition and associated DRM keys (any way to back it up from fastboot or toolkit?). Or is that not a factor with the hack available now? Sorry for all these questions, just getting more and more frustrated with this.
Click to expand...
Click to collapse
Come to think of it without getting into the phone to enable unlocking the bootloader I don't think you would even be able to do that. Even if the drivers weren't installed the phone should go into flash mode. I had a hard time with my first attempt with flash tool at getting into flash mode. If you hold power and volume up you should be able to power down the phone completely then hold volume up while plugging in. The problem I had was my PC has a few different USB ports and I was using one that was meant for charging and it wouldn't go into flash mode, tried a different port and it went well after that.
Failed: remote command not allowed ???
This error is because you have not enabled OEM Unlocking from the Developer Option.
If you have enabled it but still receiving the error then you have not unlocked bootloader properly.
There is no need to unlock bootloader for flashing official sony firmwares. It is pretty simple. If you are facing any problems then please feel free to message me.
my email : [email protected]
#coolmen777
Looks like this phone got the dreaded sleep of death bug (won't turn on at all, no matter which combination of buttons I press). Had it on the charger for last 3 days (no led indicators at all and no vibrations), so I got a brick now. Any ideas? This phone should still be under warranty (manufactored week 9 of 2016), but Sony USA refuses to service International phones in their facility. Learned that based on IMEI, this is a Hong Kong version and they want an invoice from authorized dealer for warranty work. Are there are other countries that honor warranty without checking invoice (go by date of manufactoring?) I had Moto and LG repaired before just based on age of phone, no invoice needed. This is my last resort option (to attempt sending in for service).
coolmen777 said:
Looks like this phone got the dreaded sleep of death bug (won't turn on at all, no matter which combination of buttons I press). Had it on the charger for last 3 days (no led indicators at all and no vibrations), so I got a brick now. Any ideas? This phone should still be under warranty (manufactored week 9 of 2016), but Sony USA refuses to service International phones in their facility. Learned that based on IMEI, this is a Hong Kong version and they want an invoice from authorized dealer for warranty work. Are there are other countries that honor warranty without checking invoice (go by date of manufactoring?) I had Moto and LG repaired before just based on age of phone, no invoice needed. This is my last resort option (to attempt sending in for service).
Click to expand...
Click to collapse
search on here for a thread about flashing the wrong ftf onto the phone, I think op used a tablet ftf and had teh same results and had to send to sony
edit:
http://forum.xda-developers.com/z5-compact/help/flashed-wrong-mm-rom-phone-dead-help-t3330929
civicsr2cool said:
search on here for a thread about flashing the wrong ftf onto the phone, I think op used a tablet ftf and had teh same results and had to send to sony
edit:
http://forum.xda-developers.com/z5-compact/help/flashed-wrong-mm-rom-phone-dead-help-t3330929
Click to expand...
Click to collapse
Thanks, not very encouraging given the fact that Sony USA supposedly doesn't currently have a service center to repair international phones (closed their TX center). Are there other countries (Canada or UK) which have less stringent policies of needing invoice (for proof of purchase) and can simply go off of manufacture date from the IMEI or device info? Thanks again.
Related
Hello all.
My Xperia X10 Mini Pro is stuck on bootloop as you can see on this video
http://youtu.be/EhaBn0uuSvE
It just got like that from one moment to the other..I was using stock ROM
I tried to flash with Flashtool with these ROMs
U20a_2.1udpt1_Generic
ST17i-Active_4.1.B.0.431-1254-6360_SONY
On the first ROM it gets 100% successfull but still cant boot !
This phone was bought on Portugal, so I dont know if the ROM makes any difference..
Need some advice please !
I've read somewhere that Gordon's Gate (part of Flashtool) can still access a phone even when it bootloops.
Could you document what steps you already took? Perhaps link to the article you followed? (Below is a list of certain steps one usually takes when installing custom ROMS, but they are by no means always necessary, could you perhaps indicate what you already did?)
Rooted Yes/No/Not Sure
ClockWorkMod installed Yes/No/Not Sure
Unlocked bootloader Yes/No/Not Sure
Custom kernel Yes/No/Not Sure
The location of where the phone was bought will not make a lot of difference for the ROM. It might affect things like hardware keyboard layouts, but there are fixes available for those. But things like specific baseband and firmware are still important. By carefully reading the description, you can usually check if your phone can be used.
To be honest, I only have used Flashtool to flash new kernels to my X10 Mini Pro, for just installing another ROM I use ClockWorkMod.
What you can try:
Unbrick through SEUS: here (video)
I've read about people unbricking their devices with PC Companion, here.
If you should be able to regain access to the phone and still want to tinker:
This ROM works nice with the stock kernel
Later, you could unlock the bootloader, flash custom kernels (nAa ICS 04) and install ROMS needing such custom kernels (the U20 ICS ROMS, like MiniCM9)
Should you feel the need to ever unlock the bootloader, use this tool
Cheers and thanks for your post !
I used SEUS and updated to latest firmware but still no success on booting. It stills the same...
Rooted No
ClockWorkMod installed No
Unlocked bootloader No
Custom kernel Not Sure
Any chance that you can point me a stock rom and stock kernel to see if it boots that way?
JotaM07 said:
Cheers and thanks for your post !
I used SEUS and updated to latest firmware but still no success on booting. It stills the same...
Rooted No
ClockWorkMod installed No
Unlocked bootloader No
Custom kernel Not Sure
Any chance that you can point me a stock rom and stock kernel to see if it boots that way?
Click to expand...
Click to collapse
Don't update, repair... leave your phone unplugged when SEUS searches for updates, it can't recognise your phone when it's not connected and will give you a repair option. choose that, and make sure you select your phone from the list presented. it will then flash original kernel and firmware to your phone.
Don't know which kernel you flashed before you got this bootloop, but the second rom you mentioned in your opening post isn't even for your phone, so i guess you got confused with what goes for your phone. You don't even get a kernel logo, so i guess you flashed a kernel for a different model altogether, or your stock kernel got corrupted. a repair should fix it.
I'm now updating on PC Companion like belgianguy said
If unsuccessfull I'll follow your instructions, thanks a lot in advance !
Same on PC Companion..no boot !
SmG67, I dont see any repair option on SEUS. It detects the phone and says thar it's updated. If I remove the battery while is searching my phone it keeps saying that it's updated. What am I doing wrong ?
On PC Companion I got the Repair option, it repaired, but...surprise...still can't boot !
JotaM07 said:
Same on PC Companion..no boot !
SmG67, I dont see any repair option on SEUS. It detects the phone and says thar it's updated. If I remove the battery while is searching my phone it keeps saying that it's updated. What am I doing wrong ?
On PC Companion I got the Repair option, it repaired, but...surprise...still can't boot !
Click to expand...
Click to collapse
That's a shame... because you now have all official sony ericsson firmware on your phone, kernel and rom... If it's still not booting the kernel, there's nothing you can do about it, maybe a repair-shop might be able to fix it.
Well, a repair-shop isnt able to fix it because the mini-usb port has bad contact and they consider this phone out of warranty because of that ! It almost never happens that bad contact..
JotaM07 said:
Well, a repair-shop isnt able to fix it because the mini-usb port has bad contact and they consider this phone out of warranty because of that ! It almost never happens that bad contact..
Click to expand...
Click to collapse
Well if it's that far gone it might very well be a hardware issue. But just to be sure, could you start Flashtool and see if it still recognizes the device (see screenshot of what I see).
If it isn't able to, an older version of s1tool had an IDENTIFY option that required you plug the USB cable into the computer (but not in the phone), to shut down the phone, then push the BACK button and then plug the usb cable into the phone.
The bad contact you mentioned might be causing troubke as well, are you sure it isn't the cable that is at fault? Perhaps try to attach the USB cable in such a way that its not stressed and so that the phone cannot move (to prevent it from disconnecting due to a bad contact). Your flashes very well might have gone faulty because of that. But then again, the SEUS/PC Companion flashes seem to have succeeded, so hopefully Flashtool can shed some light here.
I was using XZXperience 2 on my Sony Xperia S, and then sony companion detected that i had firmware 6.1.A.1.45 and 6.1.A.55 was available, so just to give it a try, I installed that update, but that is a failed update, it says unfortunately music player stopped working, or unfortunately xperia keyboard stopped working etc. The main problem is that my system does not recognize my XS anymore, it says USB Device Not Recognized, so I cant connect it to Flashtool or PC Companion for repair. The Sad part is that I cant even connect it in Flash Mode, I tried a hard reset by using power button and volume up buttons, but no use. I should mention that once it recognized my phone when i turned off my laptop and removed its battery too, after restarting both phone and laptop, flashtool detected that phone was connected with USB Debugging OFF, though it was on, but as a try, I unchecked USB Debugging and then checked it again, and it worked. Now my Xperia S was connected in USB debugging mode, I tried to install busybox, rooted it, and tried to install CWM recovery,flashtool said that busy box was installed and phone was rooted, but it could not install recovery and I used another tool to install recovery,which had a bat file and it installs recovery automatically. But it didnt. After restarting my phone, the same issue appeared again, My PC does not recognize my Xperia S, tried previous procedure several times, but no use. Cant even repair it as my set cant go in flash mode. What can I do? have I bricked my Xperia S? I`m in Pakistan and there is no official Sony Mobile franchise as they dont launch their flagships in Pakistan. Please help me, considering I`m used to with rooting,flashing etc. How can I connect my phone in flash mode? Thank you.
Thanx
Sewrizer said:
It looks like another strike from the productors. They usually send you malicious updates which cause your device to stop working. This only happens to rooted phones which run custom roms. And since the rooted users only flash their roms in zip format, sending an OTA update patch(designed for stock rom) to a custom rom can only lead to a malfunction. I am not sure whether or not sony did that on purpose, but the truth is that after installing a custom rom NEVER do OTA updates(unless they are from the rom's developer).
If you want an update check your rom's thread and there may be new flashable versions.
As for making your device work, the only thing you can do is to call technical support or go to a phone service(in my country they are called gsm services, and they fix mostly everything, both hardware and software. Some even claim to be able to fix water damage) but given that your warranty is voided, you will have to pay for the reparations. I guess they will only do a re-soft(delete everything, and install the stock version, you may lose your root, i am not sure here.)
I hope this helps, this is how we fix things like this in our country, so it will work in your case too, hopefully.
Sent from Area 51 using my HTC Sensation XE, hit thanks if I helped
Click to expand...
Click to collapse
Thanx for your advice. I was almost hopeless, but after spending continous 16 hours, I`m now able to get a solution. I got another data cable, removed battery of my laptop, and made a hard reset to my phone, and after 10-15 min I tried again, and Thanx GOD, it detected my phone, so I hurriedly start repair my phone option and connected my phone in flash mode which was successful and that was not less than a miracle, because i`ve been repeating same procedure and it was not working, this time luckily it worked, now i`m using stock rom with firmware 6.1.A.2.55. Now I would either wait for official Sony JB Update or I would flash a custom ROM XZXperience 2, which I found awsome, as it had no bugs, and it improved battery and sound quality was significantly imrpove + Bravia Engine 2 with improved graphics. I would ask users to not to give up hope, there is always a solution to every problem.
device not recognized
jibraiel.hassan said:
Thanx for your advice. I was almost hopeless, but after spending continous 16 hours, I`m now able to get a solution. I got another data cable, removed battery of my laptop, and made a hard reset to my phone, and after 10-15 min I tried again, and Thanx GOD, it detected my phone, so I hurriedly start repair my phone option and connected my phone in flash mode which was successful and that was not less than a miracle, because i`ve been repeating same procedure and it was not working, this time luckily it worked, now i`m using stock rom with firmware 6.1.A.2.55. Now I would either wait for official Sony JB Update or I would flash a custom ROM XZXperience 2, which I found awsome, as it had no bugs, and it improved battery and sound quality was significantly imrpove + Bravia Engine 2 with improved graphics. I would ask users to not to give up hope, there is always a solution to every problem.
Click to expand...
Click to collapse
I have sony xperia s.....before it was working perfectly fine but than suddenly i got message on my laptop usb device not recognized.. i have not rooted my phone than also.. since then m suffering from it and transferring files via wi fi... please help me.. i tried almost every thing.. but i dont know how to perform hard reset.... and what kind of new data cable are u talking about..as i bought this phone from other country so sony service center is not entertaining....
pratik1315 said:
I have sony xperia s.....before it was working perfectly fine but than suddenly i got message on my laptop usb device not recognized.. i have not rooted my phone than also.. since then m suffering from it and transferring files via wi fi... please help me.. i tried almost every thing.. but i dont know how to perform hard reset.... and what kind of new data cable are u talking about..as i bought this phone from other country so sony service center is not entertaining....
Click to expand...
Click to collapse
Get a new data cable, fortunately almost all phone now a days have same data cable, u can try data cable of some HTC, Samsung, Blackberry or even Iphone`s data cable. Secondly, u must turn off your PC, and remove its power source, if it is laptop then also remove its battery. Then after 5-10 minutes, turn on your PC and connect the phone. Also try installing drivers, which u can by using PC Companion. You can also install drivers by using FlashTool. Download it and extract it, then go to the installation folder and look for folder "Drivers" open it and u will see an exe file. Just run it and select Xperia S and follow the instructions.
maybe not new usb cable sometimes usb port is broken
Hey, I had the same problem a few time ago, you can try to restore with flashtool, if you can still get in to flash mode
Sony xperia S not starting
Plzzzz help I m realy worried
few months back i had unlocked the bootloader of my xperia s and flashed CWM 10 on it...Now i Thought of locking the bootloader and to get official updates...i locked the bootloader directly by using flash tool....after i locked it and tried to turn on the phone it is not turning on...a green light just flashes once and the phone vibrates once after that nothing happens...plzzz helppp
elegantuser29 said:
Plzzzz help I m realy worried
few months back i had unlocked the bootloader of my xperia s and flashed CWM 10 on it...Now i Thought of locking the bootloader and to get official updates...i locked the bootloader directly by using flash tool....after i locked it and tried to turn on the phone it is not turning on...a green light just flashes once and the phone vibrates once after that nothing happens...plzzz helppp
Click to expand...
Click to collapse
-.-
There's nothing strange: you are using a custom kernel and you have locked bootloader
It's impossible it could work
You need to flash official stock rom to boot up
Sent from my LT26i using xda app-developers app
Phone responded
mirhl said:
-.-
There's nothing strange: you are using a custom kernel and you have locked bootloader
It's impossible it could work
You need to flash official stock rom to boot up
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
the phone has responded and is working now...i unlocked the boodloader using cmd..and the phone worked...One Thing plzz tell that i want to bring my phone to stock ics from sony..and want to get the OTA update...is it possible??
elegantuser29 said:
the phone has responded and is working now...i unlocked the boodloader using cmd..and the phone worked...One Thing plzz tell that i want to bring my phone to stock ics from sony..and want to get the OTA update...is it possible??
Click to expand...
Click to collapse
Since you CAN'T use custom kernels with locked bootloader (and so, no cm10)
You only need to flash stock rom and then relocking your bootloader
http://forum.xda-developers.com/showthread.php?p=23180725
Sent from my LT26i using xda app-developers app
I am also having the same problem
I have sony Xperia S. I updated to the latest stock firmware version(6.2.B.1.96). after this update I rooted my phone using old kernel .200 and update the firmware's kernel again to stock after that I locked the boot loader again. Now I can't use memory stick that I used to use before with OTG cable. And now, if I am trying to enter flash mode by pressing volume down key, the led turn green for a while only about 10 sec while this was happening, my pc say that USB device not recognized. So, now I can't use flashtool or sony update service tool(SUS) as well.
Now I am using stock .96 rom with no error but I want to install CWM and also want to unlock boot loader again to test some custom roms.
Pls help me what I have to do and what should. I am now in Delhi.
aungthumoe said:
I have sony Xperia S. I updated to the latest stock firmware version(6.2.B.1.96). after this update I rooted my phone using old kernel .200 and update the firmware's kernel again to stock after that I locked the boot loader again. Now I can't use memory stick that I used to use before with OTG cable. And now, if I am trying to enter flash mode by pressing volume down key, the led turn green for a while only about 10 sec while this was happening, my pc say that USB device not recognized. So, now I can't use flashtool or sony update service tool(SUS) as well.
Now I am using stock .96 rom with no error but I want to install CWM and also want to unlock boot loader again to test some custom roms.
Pls help me what I have to do and what should. I am now in Delhi.
Click to expand...
Click to collapse
To unlock the bootloader you need to enter fastboot (blue led) with vol+ during the boot, not vol-
Or you can also reboot the phone from adb with
adb reboot bootloader
If phone still doesn't stick to fastboot, it has to be a driver problem
There are lots of guide on the procedure (which is really hard on windows 8)
Sent from my noobish GT-I9100 using xda app-developers app
Yes i use windows 8.1
mirhl said:
To unlock the bootloader you need to enter fastboot (blue led) with vol+ during the boot, not vol-
Or you can also reboot the phone from adb with
adb reboot bootloader
If phone still doesn't stick to fastboot, it has to be a driver problem
There are lots of guide on the procedure (which is really hard on windows 8)
Sent from my noobish GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yes I use windows 8.1
now. I can't use memory stick with OTG cable but I can only use mouse or keyboard with OTG cable. I don't know why?
I can access fastboot mode but I can't access flash mode. pc said that device not recognized. so, I think it is device error.
aungthumoe said:
Yes I use windows 8.1
now. I can't use memory stick with OTG cable but I can only use mouse or keyboard with OTG cable. I don't know why?
I can access fastboot mode but I can't access flash mode. pc said that device not recognized. so, I think it is device error.
Click to expand...
Click to collapse
I dont really understand what you did
But my advice is: unlock your BL and enjoy the magic of aosp ROMs (magic included inside doomkernel for stock sony is fine too)
Sent from my noobish GT-I9100 using xda app-developers app
Bricked my phone - please help!
Hi,
I think I bricked my Xperia S. I already had cyanogen 10 on my phone, so I thought I could just flash the new Cyanogen 11 4.4.2 ROM and GAPPS over top. I followed the instructions but I skipped the Fastboot step. I cleared the cache and system and then went ahead with the ROM and GAPPS. Once the ROM and GAPPS were installed, I selected "Reboot" and the phone turned off and now it won't boot at all. If I hold the power button, I get a faint vibration and if I hold the up volume and power I get the 3 vibration sequence but no boot. Please help!
This is what I was using:
http://forum.xda-developers.com/showthread.php?t=2555243
Okay, so I waited patiently for Lollipop to drop on the Z Ultra C6833 in Singapore -- but apparently this is almost the only country which will not be getting the OTA (I can't even get them to answer on Twitter or FB whether this is true). So, I finally followed Sony's instructions to unlock the bootloader. That succeeded. But then I was presented with a language-selection screen after the subsequent boot which I wasn't expecting, and since I thought I just wanted to just go down into recovery and not set up a refresh ROM, I powered off the device without proceeding through the language selection screen.
Apparently, that was a bad call because I've been in a bootloop since then which triggers after a freeze in the swishy boot animation. I flashed the TWRP recovery image I found on these forums, but no go. The volume up/down tricks have never put me into a recovery environment, and the only thing I can succeed in doing still is putting it into fastboot. Sony PC Companion's recovery process won't complete because it detects foreign software (probably the TWRP recovery, right? -- but where do I get stock recovery, and would that even work anyway? And Emma let me in once, but subsequently refuses to respond to the supplied configuration INI file (I'll try to fully reinstall this thing later).
I love this phone. Best phone I've ever had. My plan is up and I *could* get a new phone, but I don't want to move on! I want my Z Ultra. So, someone hold my hand, please. I am even willing to pay a bounty (via PayPal) for a live chat if that is what it takes to get someone knowledgeable to help me in a timely fashion. I live in Singapore (UTC+8), and I do biphasic sleeping, so I'll also be awake between 1:30am and 4:00am my time. Thanks in advance for **any kind of help!**
Sincerely,
Hopeful and anxious expat in Singapore
Edit: I will pay $60 USD by PayPal to the individual who can provide a productive resolution (preferably write here and be available over chat so I can learn from you -- PM me for Hangouts, Skype, VSee, or Firefox Hello contact details). A "productive resolution" does not mean necessarily that we will fix my phone. It may mean that we conclude definitively that we can't. I will take this thing into the Sony Service Centre and give them my money if I have to, but I'd rather give it to one of you fine folks. I only want to give a few more hours to this. I've already been phoneless for two days.
New information in the continuing saga
Reinstalling Emma didn't help, nor did putting customization.ini in creative locations or pasting the developer mode line from that INI file into other INI files within the Emma directories. So I gave up on Emma until I can get to another computer.
After a user kindly uploaded this SIN file (http://forum.xda-developers.com/xperia-z-ultra/general/bootloader-devices-real-recovery-t3117566) to a fileshare for me, I figured out (here https://android.stackexchange.com/questions/65058/why-custom-roms-are-zip-filed-than-made-as-ftf) that "FlashTool" is not the same as Sony's "flashtool" Emma, so I installed it. It wanted me to put the phone in flashmode -- so I held volume down while plugging in the cable, which never before displayed anything different on the screen, nor a green LED which I've read elsewhere I should be seeing (e.g. http://www.theandroidsoul.com/sony-xperia-z-ultra-flash-mode-51769/). But despite the lack of visual clues, FlashTool told me it connected to flashmode and the flash succeeded. It didn't seem to help at all, though, as I still get the bootloop just as before and I still can't access a recovery mode.
That means that I can apparently get into both fastboot and flashmode, which I wanted to make special note of. Is it possible to access ADB while the phone is powered off?
just download flashtool, install driver in included in flashtool folder.
download also any FTF, generic zultra, dont care if 3g or lte.
flash it, should resolve the issue.
in flashtool, make sure you dont touch and leave the flash option as default. it will wipe your data, cache and everything.
to be safe, remove sim and sdcard.
More information...
curiouso9 said:
just download flashtool, install driver in included in flashtool folder.
download also any FTF, generic zultra, dont care if 3g or lte.
flash it, should resolve the issue.
in flashtool, make sure you dont touch and leave the flash option as default. it will wipe your data, cache and everything.
to be safe, remove sim and sdcard.
Click to expand...
Click to collapse
None of the supplied drivers match the "S1Boot Fastboot" device which comes up in my Device Manager. Also, none of the updated FlashTool Xperia Driver Pack match (http://forum.xda-developers.com/showthread.php?t=2635830), nor the drivers on SonyMobile.com, nor the drivers which come with Sony PC Companion. I didn't have this problem on my other Windows 10 machine, but just in case that is an issue, I'm downloading the Android SDK 1.2.1.1 Beta to see if I get any mileage out of that.
I attempted to flash the FTF supplied here (http://forum.xda-developers.com/showpost.php?p=60958777&postcount=3) but I got the following messages:
INFO - Opening device for R/W
INFO - Start Flashing
INFO - Checking header
ERROR - Processing of loader.sin finished with errors.
INFO - Ending flash session
ERROR -
ERROR - Error flashing. Aborted
INFO - Device connected in flash mode
Click to expand...
Click to collapse
Then I used XperiFirm to download my original .108 firmware and attempted to flash it but got the same errors as above.
Download flashtool
I assume you're on windows 8.1/8 you have to disable driver signature enforcement. Then install the drivers than flashtool will detect your phone.
Flash ftf
You will need to re-root, and you can unlock the bootloader.. After that flash away. Remember to install recovery and back up ta. I'm a noob at this and did it for the first time a few weeks ago, so I know you can do it.
Rockin' and rollin'
RealityFails said:
I assume you're on windows 8.1/8 you have to disable driver signature enforcement. Then install the drivers than flashtool will detect your phone.
Click to expand...
Click to collapse
I'm on Windows 10 -- I wasn't getting any errors, so DSE didn't even occur to me. I disabled it and was able to re-flash stock. Still, I struggled with getting a recovery installed, but after several attempts, and started from scratch a few times, one of them finally stuck. After that, I installed a custom ROM and things are running perfectly.
Thanks!
David
mypetocean said:
I'm on Windows 10 -- I wasn't getting any errors, so DSE didn't even occur to me. I disabled it and was able to re-flash stock. Still, I struggled with getting a recovery installed, but after several attempts, and started from scratch a few times, one of them finally stuck. After that, I installed a custom ROM and things are running perfectly.
Thanks!
David
Click to expand...
Click to collapse
Download rashr and it will have recoveries for you
Disappointment with the Service Center
By the way, when I decided I had been too long without an operating phone (before I got the DSE tip), I took the phone to a Sony Mobile Service Center and had them diagnose it. They concluded that there was a hardware failure rather than a software failure (which would require some 300 SGD to repair). I declined, returned to the office, saw the message about DSE, and was immediately successful in reflashing stock. I took it back to the Sony Mobile Service Center and had them confirm that there was in fact no hardware issue -- and that their diagnosis was incorrect. Thanks for the help folks!
Could someone give me a super quick guide on how to get this on my phone? I coming from years of Samsung phones and never owned a Sony before or know anything about it. I have CM on all my Samsung devices for years and simply want a CM ROM in the Z and get it done with with. I picked up a 99% like new second-hand Ultra Z LTE C6833 today, has stock 5.02 and I don't have a clue how to get this flashed in the easiest and simplest way possible. As for locked or not bootloader, I also don't have a clue. First step which is to install TWRP I immediately got stuck because the links posted are dead (teamw.in/project/twrp2/219)
Without wanting to waste anyone's time, if someone could give me the simplest and most painless info on how to get the Z flashed, I'd be super appreciative. The threads on this phone are in the hundreds at this point and I read all sorts of very confusing and contradictory info. I worry to kill or brick it immediately before I even get started.
Thanks much in advance
Read. Thats my tip.
Every sony device past 2011 works the same way.
Look at different xperia forums, for example at the Z1 section, Z2, Z3 etc.
Look at the rooting guides. Unlock guides. Ta backup guide. Just read and read.
Dont just look at the first guide and jump right in.. read first.
Explore the Xda forum. You will find the guides im talking about. im on my phone.. a bit difficult to post links atm
Much good information can be found here
http://forum.xda-developers.com/crossdevice-dev/sony
You can check if the bootloader is unlocked or locked by opening the dialer and entering *#*#7378423#*#*. Then tap "Service Info" and then "Configuration". It'll either say "Bootloader unlocked: Yes", or "Bootloader unlock allowed: Yes/No". If it says NO on the latter, then you can't unlock the bootloader and you're pretty much screwed. Bell Canada devices have locked bootloaders, and I believe it's the same with UK O2. Chances are that you can unlock it, but you could of course be really unlucky.
If you can unlock the bootloader, then your Ultra will pretty much behave like a Nexus device when it comes to rooting and stuff like that. Just flash a custom kernel with recovery, like NUT's Dual Recovery (with CWM and TWRP), then flash SuperSU, and you'll have recovery and root. Next step is to flash CM12.1 and you're done. It's very easy once you have recovery.
Klaos3000 said:
You can check if the bootloader is unlocked or locked by opening the dialer and entering *#*#7378423#*#*. Then tap "Service Info" and then "Configuration". It'll either say "Bootloader unlocked: Yes", or "Bootloader unlock allowed: Yes/No". If it says NO on the latter, then you can't unlock the bootloader and you're pretty much screwed. Bell Canada devices have locked bootloaders, and I believe it's the same with UK O2. Chances are that you can unlock it, but you could of course be really unlucky.
If you can unlock the bootloader, then your Ultra will pretty much behave like a Nexus device when it comes to rooting and stuff like that. Just flash a custom kernel with recovery, like NUT's Dual Recovery (with CWM and TWRP), then flash SuperSU, and you'll have recovery and root. Next step is to flash CM12.1 and you're done. It's very easy once you have recovery.
Click to expand...
Click to collapse
Thanks MUCH for the detailed info!
I checked the bootloader info as you said and it's not unlocked, but can be done. It seems a daunting task but let me start by trying to get it done. Hopefully I won't screw-up the phone. I'm searching how to do it as there seem to be several ways.. After I complete the unlocking (let's hope) I'll report back and try jump on the next steps. Probably will have some follow-up doubts or questions.. this is all a very different and more complex process than the Samsung devices I've owned that never required any of this crazy gymnastics..
Anyway, thanks again very much and keep you posted!
VeEuzUKY said:
Thanks MUCH for the detailed info!
I checked the bootloader info as you said and it's not unlocked, but can be done. It seems a daunting task but let me start by trying to get it done. Hopefully I won't screw-up the phone. I'm searching how to do it as there seem to be several ways.. After I complete the unlocking (let's hope) I'll report back and try jump on the next steps. Probably will have some follow-up doubts or questions.. this is all a very different and more complex process than the Samsung devices I've owned that never required any of this crazy gymnastics..
Anyway, thanks again very much and keep you posted!
Click to expand...
Click to collapse
I'll give you the short guide:
- Go to this (offical Sony) site and give them your IMEI and whatnot
- Wait a couple of minutes, and you'll receive a key
- Now, there are two ways to unlock the bootloader - both equally official, but the easiest one is to use Flashtool.
- Hit the "BLU" button and enter the key you got fra Sony. You only have to do this once.
- Once this is done, you can start flashing a kernel with recovery and flash whatever you'd like.
I'll help you along the way if you need to, so don't be afraid to ask any questions. Start by unlocking the bootloader, and I'll be here if you need any help.
Klaos3000 said:
I'll give you the short guide:
- Go to this (offical Sony) site and give them your IMEI and whatnot
- Wait a couple of minutes, and you'll receive a key
- Now, there are two ways to unlock the bootloader - both equally official, but the easiest one is to use Flashtool.
- Hit the "BLU" button and enter the key you got fra Sony. You only have to do this once.
- Once this is done, you can start flashing a kernel with recovery and flash whatever you'd like.
I'll help you along the way if you need to, so don't be afraid to ask any questions. Start by unlocking the bootloader, and I'll be here if you need any help.
Click to expand...
Click to collapse
Hello I am new to Sony too and I have a question. If I unlock the bootloader root flash custom roms and then decide to get back to stock and lock the bootloader will my warranty be voided?
Sent from my C6833 using Tapatalk
mike13ftw said:
Hello I am new to Sony too and I have a question. If I unlock the bootloader root flash custom roms and then decide to get back to stock and lock the bootloader will my warranty be voided?
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
Yes, and that's why it's a good idea to backup your TA folder, which contains the DRM keys. Once you unlock the bootloader, these keys disappears, and that's why it's a good idea to make a backup of them. There are a couple of tools that does this for you, and you can find them in the cross-development section.
Klaos3000 said:
I'll give you the short guide:
- Go to this (offical Sony) site and give them your IMEI and whatnot
- Wait a couple of minutes, and you'll receive a key
- Now, there are two ways to unlock the bootloader - both equally official, but the easiest one is to use Flashtool.
- Hit the "BLU" button and enter the key you got fra Sony. You only have to do this once.
- Once this is done, you can start flashing a kernel with recovery and flash whatever you'd like.
I'll help you along the way if you need to, so don't be afraid to ask any questions. Start by unlocking the bootloader, and I'll be here if you need any help.
Click to expand...
Click to collapse
Thank you very much!
Well so far EVERYTHING HAS BEEN A TOTAL NIGHTMARE! Nothing I try to do works!
First I installed flashtool, latest version. Im running Windows 7 64bit. It was a nightmare to get flashtool downloaded and installed. After I finally got it installed, ot took another hour updating itself and syncing stuff. When it finally finished and while holding down the Volume Down key I connected the phone to the PC via USB cable, Immediately I get an error of device driver errors. flashtool gives me also several errors. Then I tried to install the Flashtool-drivers-1.1-20130911. Then another problem, the drivers dont install at all with a message "DPinst.exe cannot execute on your operating system". That's it, finished! When I go to the Windows Device Manager, all I see is an exclamation mark under S1 Service.
So then I tried the FastBoot method. Also no luck. While holding down the Volume Up key I connected the phone to the PC via USB cable, the phone's blue light turns on, and again I get a DRIVER NOT INSTALLED ERROR. My computer refuses to recognize the phone and the device driver is never installed . The Windows Device Manager shows an exclamation mark under S1Boot FastBoot.
Then I tried the Sony way and installed the Android SDK!!!!! Immediately I find I need to download more crap, thie time the JRE Development Kit! Takes me 3 hours do download this with my useless internet connection. At this point I am already ready to throw my laptop out the window and break the stupid phone in a million pieces!
But then, there is the next problem. After all downloaded and installed, before I can even started I get stuck again, because Im supposed to go to the android SDK folder c:\android-sdk\extras\google\usb_driver and replace/install the fastboot drivers “android_winusb.inf”.. well, I dont have an extras or google or usb_driver folder on my SDK installed folder! NOTHING! THIS IS ALL RIDICULOUS!
Finally I searched everywhere on the internet for other possible Ultra Z drivers. I ft to Sony's own site and found Xperia Z Ultra (C6833, C6806, and C6843) drivers, Xperia Z Ultra (XL39h) drivers, Xperia Z Ultra (SOL24) drivers, Xperia Z Ultra (SGP412) drivers and others.. this is all crazy what a nightmare of mess and miss-information everywhere about this phone! Anyway, I tried all of them. None works.
I am so frustrated and desperate. My God! Cant get anything done. Nothing.................................. I cant believe this..
UPDATE: I give-up. Ive spent the whole day and downloaded and installed GIGS of apps and software and drivers. Nothing communicates with this useless phone. Im done.
Could anyone give me advice if its there is an alternate way to, root install a recover and flash this piece of **** phone without unlocking the bootloader which basically I cant do? If not, it will fly out the window asap, I cant deal with this ridiculous drama. Years of handling and flashing all sorts of hardware COMBINED, never gave me 1/10th of the misery and headaches this hardware has given me in one day. Xperia, never again..
By the way, Sony's "AMAZING" PC Companion app is so great and fantastic that it doesn't even have an uninstaller! No joke! Once in the computer, crawling endless directories with all sorts of files, drivers and registry entries, it will NEVER come out again. All is amazing..
You did the opposite of what I advised you to do. You did not read correct guides.
Q:Ask yourself what do you want to achieve?
You wrote in your first post "if someone could give me the simplest and most painless info on how to get the Z flashed".
Q:My counterquestion is why? Is your phones software unstable? Are you curious to learn to modify the devices software?
A:If your device is unstable. Please do a factory reset.
Q:Are you curious to learn how to modify the software?
A:Then collect information. Read. Set a timer for how long you will spend learning. Let say 45 minutes.
When 45 minutes has passed. STOP.
Take a break. Do something else and continue the next day. Repeat until you are confident to try a simple operation
For example: learn how to use adb and fastboot. Learn the commands. What they do.
I can not stretch enough how important it is to read and learn before you jump into things.
I do not see why I or anyone here should help you to unlock your bootloader. Because you do not have a clear purpose or knowledge how to do this.
VeEuzUKY said:
UPDATE: I give-up. Ive spent the whole day and downloaded and installed GIGS of apps and software and drivers. Nothing communicates with this useless phone. Im done.
Could anyone give me advice if its there is an alternate way to, root install a recover and flash this piece of **** phone without unlocking the bootloader which basically I cant do? If not, it will fly out the window asap, I cant deal with this ridiculous drama. Years of handling and flashing all sorts of hardware COMBINED, never gave me 1/10th of the misery and headaches this hardware has given me in one day. Xperia, never again..
By the way, Sony's "AMAZING" PC Companion app is so great and fantastic that it doesn't even have an uninstaller! No joke! Once in the computer, crawling endless directories with all sorts of files, drivers and registry entries, it will NEVER come out again. All is amazing..
Click to expand...
Click to collapse
That what I did for the drivers and work just fine .Try it
Edit: forgot to post link http://forum.xda-developers.com/showthread.php?t=2095087
Sent from my Xperia Z Ultra using Tapatalk
SÜPERUSER said:
You did the opposite of what I advised you to do. You did not read correct guides.
Q:Ask yourself what do you want to achieve?
You wrote in your first post "if someone could give me the simplest and most painless info on how to get the Z flashed".
Q:My counterquestion is why? Is your phones software unstable? Are you curious to learn to modify the devices software?
A:If your device is unstable. Please do a factory reset.
Q:Are you curious to learn how to modify the software?
A:Then collect information. Read. Set a timer for how long you will spend learning. Let say 45 minutes.
When 45 minutes has passed. STOP.
Take a break. Do something else and continue the next day. Repeat until you are confident to try a simple operation
For example: learn how to use adb and fastboot. Learn the commands. What they do.
I can not stretch enough how important it is to read and learn before you jump into things.
I do not see why I or anyone here should help you to unlock your bootloader. Because you do not have a clear purpose or knowledge how to do this.
Click to expand...
Click to collapse
Just to briefly correct you: I'm the type of guy that has NEVER gotten a virus on a computer. I'm the type of guy that has rooted, flashed and played around with phones for many years with more or less degree of difficulties, but always successful. I'm the type of guy that has helped many many people in this community with their hardware, when I know how. I'm the type of guy that has knows many things about the works of Samsung devices that I have used for many years and have never had an issue learning what's needed. I am the type of guy always ready to offer friendly advice when someone is in need of something I may offer help with. Finally, I am the kind of guy that has a Dell laptop, running Windows 7 64bit, that by whatever reason refuses to install the proper drivers for the Ultra Z, or the kind of guy that maybe has a flawed Ultra Z. After all, it's a second hand unit and about 2 years old, despite that it looks new.
So, the only thing this type of guy can do, is 1) try a different computer to see if the communications with the phone work, and if not, check the phone because obviously that's where the only place the problem can come from. To try different USB cables and do phone resets, that I did today several times. I learned those basics the first day of my flashing life, long long ago.
There is NOTHING to read or learn or do, when there is no communication between the phone and the computer that connects to it. You seem not to understand the very basics of the problem here is not lack of reading, instead is only lack data flow between devices.
Anyway, thanks for the constructive advice!
2 extra things: all the tools, apps and drivers you have suggested, I have them all. All the procedures, steps, folders where stuff is and goes.. I've done all. I learn very quickly. The issue is none of that.. the issue is, no driver for this phone will install on my laptop, for whatever reason. Is that simple.
And then there is another issue.. for you, and most people on XDA, downloading and getting "stuff" is a breeze. But not me. Where I am, XDA is blocked, and even with a VPN, hardly works. To reply to you or just log-in, sometimes is an hour. And most file hosts? Mega? Rapidgator.net? Zippy share?.. a few hundred others? Well.. they doesn't work. Uploaded.net.. Mediafire.. Google Drive.. AndroidFile Host, and just about everything else, all DON'T WORK. All blocked. So are blocked most of the VPNs now. So, while for you, go here, get this, download that, is all a piece of cake, for me, is not. Most things to get download are truly a nightmare. And when it comes to download a ROM or any 2 or 3 hundred Mg files, sometimes takes me days of endless wait and interrupted downloads. I live in a crazy country called China, where all Google stuff, Android included, is forbidden, and all around it.. XDA included.
So, talk is easy. But when access to simple and basic information is so difficult to get and everything comes at a premium, life is really a bit more complicated than maybe you can imagine. So...... yeah, help is very much appreciated indeed, in the same way I am always willing to help others when I can, without calling out their lack or reading or question their abilities to follow my advice
Alright, that was quite painful to read, not because of something wrong you wrote, but because I've been there too. I don't know what device you had prior to the Ultra, but just forget what you learned from that device.
Just sit down, relax and figure out what you're trying to do, and then how to maybe achieve it. Yes, I do understand that your laptop doesn't cooperate at all, but that's just technology. Of course it won't work when it should. We've all been there.
1. Set up your computer to be able to communicate with your Ultra. Installing the SDK is overkill since the only thing from the SDK you need is Fastboot and ADB drivers. You can easily install those two by installing this tiny tool that does it for you.
Fastboot and ADB is now installed.
2. Install Flashtool. You've already done this. Connect your Ultra and open Flashtool. Flashtool should grab and set things up for the Z Ultra automatically. This should only take 5-30 seconds. Not three hours. The device should still be powered on at this stage.
3. Okay, now you have Flashtool installed, and it recognizes your Ultra. Next step is to go to that Sony site I linked to, to get the unlock key. Fill in the required info, and you'll get the key sent on your email. Don't misplace it.
4. Go back to Flashtool, hit the "BLU" button, paste the key in, and that's it. Don't set the device into fastboot or flashmode until Flashmode asks you to do it. Fastboot can be active and connected forever, but Flashmode will disconnect by itself after a minute or so.
5. Your bootloader is now unlocked. This means that you're free to do whatever you'd like to do with it. Xperia devices do not come with a default recovery system, so we'll have to flash a custom kernel that includes a recovery. You can find them in the dev section. Once you've flashed or hotbooted a custom kernel with CWM or TWRP, you're free to root by flashing SuperSU, and flash whatever ROM you'd like to flash.
It's very easy to deal with Xperia devices once you have things set up (mainly Flashtool), and the basic steps are:
- Unlock bootloader (one time thing)
- Flash custom kernel
- Done
It's the same procedure as Nexus devices, only that we have to use special tools to unlock our bootloaders, while Nexus' use one command in a terminal. The issue here though is the tools, and not the process, and I feel your pain. I really do. It would've been so much easier if I could just show up at your door, do it for you, and leave
---------- Post added at 06:46 PM ---------- Previous post was at 06:43 PM ----------
VeEuzUKY said:
And then there is another issue.. for you, and most people on XDA, downloading and getting "stuff" is a breeze. But not me. Where I am, XDA is blocked, and even with a VPN, hardly works.
Click to expand...
Click to collapse
Then let's make it easier? My upload speeds aren't an issue, so please point to a site that I can upload the tools too, which you then can download from at proper speeds
Klaos3000 said:
Alright, that was quite painful to read, not because of something wrong you wrote, but because I've been there too. I don't know what device you had prior to the Ultra, but just forget what you learned from that device.
Just sit down, relax and figure out what you're trying to do, and then how to maybe achieve it. Yes, I do understand that your laptop doesn't cooperate at all, but that's just technology. Of course it won't work when it should. We've all been there.
1. Set up your computer to be able to communicate with your Ultra. Installing the SDK is overkill since the only thing from the SDK you need is Fastboot and ADB drivers. You can easily install those two by installing this tiny tool that does it for you.
Fastboot and ADB is now installed.
2. Install Flashtool. You've already done this. Connect your Ultra and open Flashtool. Flashtool should grab and set things up for the Z Ultra automatically. This should only take 5-30 seconds. Not three hours. The device should still be powered on at this stage.
3. Okay, now you have Flashtool installed, and it recognizes your Ultra. Next step is to go to that Sony site I linked to, to get the unlock key. Fill in the required info, and you'll get the key sent on your email. Don't misplace it.
4. Go back to Flashtool, hit the "BLU" button, paste the key in, and that's it. Don't set the device into fastboot or flashmode until Flashmode asks you to do it. Fastboot can be active and connected forever, but Flashmode will disconnect by itself after a minute or so.
5. Your bootloader is now unlocked. This means that you're free to do whatever you'd like to do with it. Xperia devices do not come with a default recovery system, so we'll have to flash a custom kernel that includes a recovery. You can find them in the dev section. Once you've flashed or hotbooted a custom kernel with CWM or TWRP, you're free to root by flashing SuperSU, and flash whatever ROM you'd like to flash.
It's very easy to deal with Xperia devices once you have things set up (mainly Flashtool), and the basic steps are:
- Unlock bootloader (one time thing)
- Flash custom kernel
- Done
It's the same procedure as Nexus devices, only that we have to use special tools to unlock our bootloaders, while Nexus' use one command in a terminal. The issue here though is the tools, and not the process, and I feel your pain. I really do. It would've been so much easier if I could just show up at your door, do it for you, and leave
Click to expand...
Click to collapse
Klaos3000, you are great. Difficult to find words to thank you the time you take to try help me out. Really much appreciated. It's almost 1AM my local time here and tomorrow I will give a try to all you suggest me step by step. If I run into additional difficulties, I will try use another computer. Maybe is my specific laptop with my windows installation that is being stupid with the Ultra Z hardware. I have installed endless drivers for HTC, LG and mainly Samsung phones and tabs, and have never had any difficulty.. just last week I installed drivers for a friend's new Galaxy Tab S2, got a recovery in, got it rooted and manually cleaned of a lot of useless samsung system bloat stock apps and crap, all about 20 minutes. Hard to understand why with an Xperia phone, things are so complicated. Anyway, tomorrow will follow your advice and report back.
Again, thanks a lot for your help
Klaos3000, despite being so late, I decided to give this another try and follow your steps.
But I Immediately run into similar problems.. I CANNOT get drivers installed.
1. I have downloaded and installed Minimal ADB and Fastboot as you suggested.
2. I have flashtool-0.9.19.7 installed and did the 0.9.19.8 upgrade by updating the x10flasher.jar file.
3. Now you suggest I connect my phone and open Flashtool. But connect my phone how? Boot it up? USB debugging on or off? Or you mean connect the phone turned off and then on press Volume up? Or press Volume down?
I tried all this, and again I get a device driver error. Because there are NO DRIVERS installed for the phone. This is same problem as before. And if I go to the drivers folder inside Flashtool and try install the drives, I immediately get an error that they cant be installed in my operating system.
I am completely stuck as before in this very simple step.
Attached screnshots when I enter Flashmode:
And this is what happens when I try install drivers from C:\Flashtool\drivers:
And if I try go to FastBoot Mode with the phone's blue light on (Volume up + connect USB Cable) this is what I get:
UPDATE:
I have finally unlocked the bootloader, using the Fastboot method! I still could not get the Flashtool drivers to recognize my phone, but the FastBoot ADB drivers installed without a problem. 2 things Ive learned with this experience I want share with anyone in the future that has similar difficulties:
1) I switched to a friend's old laptop with Windows XP. Under XP, FastBoot ADB drivers installed at the first time and absolutely zero problems.
2) I used a USB 2.0 port! If connected to a USB 3.0 port, another cascade of new problems immediately arise.
So that's it. I want thank VERY MUCH everyone in this thread that was so kind to try and help me as much as possible. I would not have gotten this done with it
My next step is to install a recovery from:
http://forum.xda-developers.com/showthread.php?t=2261606
But I only see downloadable versions for looked bootloaders. Also, I want to flash a custom CM based ROM next and see a warning regarding Unlocked Bootloader with CyanogenMod, AOSP and OmniRom that the kernel needs be repack to replace the built in recovery with XZDualRecovery or things will either not work at all or require unexpected operating instructions. So again, I am extremely confused as what files to choose and what to do and worry to look for the wrong thing and worry to make a catastrophic mistake. And also I have no idea what method I should use:
- ZU-lockeddualrecovery2.8.21-RELEASE.flashable
- ZU-lockeddualrecovery2.8.21-RELEASE.installer
Thanks again for the advice and the feedback in all this
So my trusty old E5823 motherboard died due to a power short from a bad charger. I tried everything to bring it back to life but nothing worked, so I found an E5803 board and did a swap. The rest of the components are from the E5823.
It successfully gets into fastboot and flash mode without a problem. I flashed the E5803 32.4.A.1.54 firmware but it is stuck in a bootloop.
I imagine there's an issue with the phone refusing to accept the E5823 components - but in as far as I'm aware there are no hardware differences but the E5803 has the fingerprint sensor disabled.
I think there might be a software fix around this, so this is why I'm asking for help.
I was going to try flashing a custom kernel but I don't know the IMEI of the E5803 board so I can't unlock the bootloader to try.
Any ideas?
Follow-up Q: Is there a way I can log the bootloader actions to the console as I try to boot up the phone so I can find out what exactly is failing?
Quick bump: any ideas?
WizaJ said:
So my trusty old E5823 motherboard died due to a power short from a bad charger. I tried everything to bring it back to life but nothing worked, so I found an E5803 board and did a swap. The rest of the components are from the E5823.
It successfully gets into fastboot and flash mode without a problem. I flashed the E5803 32.4.A.1.54 firmware but it is stuck in a bootloop.
I imagine there's an issue with the phone refusing to accept the E5823 components - but in as far as I'm aware there are no hardware differences but the E5803 has the fingerprint sensor disabled.
I think there might be a software fix around this, so this is why I'm asking for help.
I was going to try flashing a custom kernel but I don't know the IMEI of the E5803 board so I can't unlock the bootloader to try.
Any ideas?
Click to expand...
Click to collapse
The problem is most likely a failure in the bootloader verification chain.
WizaJ said:
Follow-up Q: Is there a way I can log the bootloader actions to the console as I try to boot up the phone so I can find out what exactly is failing?
Click to expand...
Click to collapse
Not that I know of w/out a testpoint and ome of those special boxes they use to have access to UART and low level functions. They cost a pretty penny.
What you can do is find a way to retrieve the logs from the failed boot if the kernel is able to get to the stage where you can adb. Stock recovery mode afaik can get you adb access and you can grab the file from there. (/sys/fs/pstore - that's dmesg).
If that doesn't work you can try flashing E5803 firmware and see if it boots. You might be stuck w/out a fingerprint reader but that's a small price to pay and it's a good starting point.
The IMEI should have been written on the board you bought or an accompanying document/leaflet/sticker.
trax7 said:
The problem is most likely a failure in the bootloader verification chain.
Not that I know of w/out a testpoint and ome of those special boxes they use to have access to UART and low level functions. They cost a pretty penny.
Click to expand...
Click to collapse
Dammit I imagine they really do. Not able to get access to that.
trax7 said:
What you can do is find a way to retrieve the logs from the failed boot if the kernel is able to get to the stage where you can adb. Stock recovery mode afaik can get you adb access and you can grab the file from there. (/sys/fs/pstore - that's dmesg).
If that doesn't work you can try flashing E5803 firmware and see if it boots. You might be stuck w/out a fingerprint reader but that's a small price to pay and it's a good starting point.
The IMEI should have been written on the board you bought or an accompanying document/leaflet/sticker.
Click to expand...
Click to collapse
Unable to adb in either normal startup, fastboot or flash mode so I guess I'm stuck here too. I *did* flash E5803 firmware and same result. Flashtool didn't let me flash the E5823 firmware. Unfortunately the IMEI is also not visible on the board and it didn't come with any documentation, it was a board from a phone whose screen cracked a long time back.
Thanks so much for your response and advice, I had really given up on this thing.
WizaJ said:
Dammit I imagine they really do. Not able to get access to that.
Unable to adb in either normal startup, fastboot or flash mode so I guess I'm stuck here too. I *did* flash E5803 firmware and same result. Flashtool didn't let me flash the E5823 firmware. Unfortunately the IMEI is also not visible on the board and it didn't come with any documentation, it was a board from a phone whose screen cracked a long time back.
Thanks so much for your response and advice, I had really given up on this thing.
Click to expand...
Click to collapse
Ended up buying a new phone - that also solved the problem lol.