Hello I have a big problem. My Sony Xperia Pro-i is stuck in bootloop (soft bricked). USB debugging is not turned on and obviously I can not turn it on. The problem occurred due to a software update that failed due to low battery. I have already tried Xperia Companion and the software repair succeeded (at least that's what the software says). Unfortunately, after flashing with Xperia Companion, you only see the logo again instead of "your device is corrupted and cannot be trusted". The warning comes after about 5 times restart. I have also looked around with "Sony Mobile Flasher by Androxyde" to do the whole thing. I noticed that my device do not exist under devices in the programm. Now I am running out of ideas. I also don't understand why it still doesn't work after a successful reflash. Would be very grateful for suggestions!
xCyberbrain said:
Hello I have a big problem. My Sony Xperia Pro-i is stuck in bootloop (soft bricked). USB debugging is not turned on and obviously I can not turn it on. The problem occurred due to a software update that failed due to low battery. I have already tried Xperia Companion and the software repair succeeded (at least that's what the software says). Unfortunately, after flashing with Xperia Companion, you only see the logo again instead of "your device is corrupted and cannot be trusted". The warning comes after about 5 times restart. I have also looked around with "Sony Mobile Flasher by Androxyde" to do the whole thing. I noticed that my device do not exist under devices in the programm. Now I am running out of ideas. I also don't understand why it still doesn't work after a successful reflash. Would be very grateful for suggestions!
Click to expand...
Click to collapse
Did you try flashing using EMMA instead of that? Is the bootloader unlocked??
Get the it here...
https://developer.sony.com/develop/open-devices/get-started/flash-tool/download-flash-tool/
And here's the official guide to use it...
https://developer.sony.com/develop/open-devices/get-started/flash-tool/how-to-flash/
They are official resources so it's basically doing the Xperia Companion repair, but in full manual (hopefully to correct this)
ragu24 said:
Did you try flashing using EMMA instead of that? Is the bootloader unlocked??
Get the it here...
https://developer.sony.com/develop/open-devices/get-started/flash-tool/download-flash-tool/
And here's the official guide to use it...
https://developer.sony.com/develop/open-devices/get-started/flash-tool/how-to-flash/
They are official resources so it's basically doing the Xperia Companion repair, but in full manual (hopefully to correct this)
Click to expand...
Click to collapse
Hi!
Thanks for the response. EMMA didnt worked i get the error "Device is locked...". I Tryed flashing with "newflasher" what did work (But still in bootloop again with "your device is corrupted and cannot be trusted"). I heard that this can caused by the bootloader if its activated. Unfortunately im not very skilled at Software repairing. So im not sure how to check if the bootloader is activated and how i can enter it.
xCyberbrain said:
Hi!
Thanks for the response. EMMA didnt worked i get the error "Device is locked...". I Tryed flashing with "newflasher" what did work (But still in bootloop again with "your device is corrupted and cannot be trusted"). I heard that this can caused by the bootloader if its activated. Unfortunately im not very skilled at Software repairing. So im not sure how to check if the bootloader is activated and how i can enter it.
Click to expand...
Click to collapse
Sweet hell...
If the bootloader is unlocked, it won't generally relock unless prompted to - that's the good news
Bad news is that if it is in fact locked, it only reacts to officially signed firmware, and you should never never lock it while running anything modified (ROM) or rooted, since when it self contains, it will detect it's not 'officially signed' and **** the bed - AKA hard bricks itself
The boot message not showing the unlocked bootloader warning (The device cannot be checked for corruption blah blah blah) is rather concerning.
I'm curious if what caused this is running the Xperia companion app since that's the one that's generally used as the final step after you relock the bootloader - not sure if it reattempts locking it down once more before completing. This would be bad..
At the expense of losing all your data, have you tried a fastboot wipe? Maybe corrupted files could be causing this as well
I would nuke it then try reflashing again
Careful with those .ta files as well - they can ruin your day
ragu24 said:
Sweet hell...
If the bootloader is unlocked, it won't generally relock unless prompted to - that's the good news
Bad news is that if it is in fact locked, it only reacts to officially signed firmware, and you should never never lock it while running anything modified (ROM) or rooted, since when it self contains, it will detect it's not 'officially signed' and **** the bed - AKA hard bricks itself
The boot message not showing the unlocked bootloader warning (The device cannot be checked for corruption blah blah blah) is rather concerning.
I'm curious if what caused this is running the Xperia companion app since that's the one that's generally used as the final step after you relock the bootloader - not sure if it reattempts locking it down once more before completing. This would be bad..
At the expense of losing all your data, have you tried a fastboot wipe? Maybe corrupted files could be causing this as well
I would nuke it then try reflashing again
Careful with those .ta files as well - they can ruin your day
Click to expand...
Click to collapse
Well it's complicated....
So i cant do a fastboot wipe because "FAILED (remote: 'Erase is not allowed in Lock State')" im not sure about this error but i thought it means that the bootloader ist not unlocked and that is the case. But even if sony companion should still play a verified software on it or not? Or is it already a problem if unverified software has only been installed once on the device? Xperia companion app caused the error ("The device cannot be checked ...") before there was just the logo without warning.
xCyberbrain said:
Well it's complicated....
So i cant do a fastboot wipe because "FAILED (remote: 'Erase is not allowed in Lock State')" im not sure about this error but i thought it means that the bootloader ist not unlocked and that is the case. But even if sony companion should still play a verified software on it or not? Or is it already a problem if unverified software has only been installed once on the device? Xperia companion app caused the error ("The device cannot be checked ...") before there was just the logo without warning.
Click to expand...
Click to collapse
The fact you've flashed non standard/pure OEM software means nothing really - the issue comes upon relocking bootloader. When it relocks, it checks for integrity of the files, and it's got anything BUT the pure non modified as is software as per Sony's official releases, when it self checks for the signatures it won't succeed and will declare it as nom trustworthy/corrupted, and stop the boot. Basically what you've got. But again, unless the Xperia Companion app locked it, this should not be the case unless you manually did it
If the bootloader is locked tho, you cant reflash anything to address it, so it becomes a catch 22. Locking your door with the keys inside the house if you may.
Did you tried newflasher? And flash your firmware and erase data?
raven213 said:
Did you tried newflasher? And flash your firmware and erase data?
Click to expand...
Click to collapse
Yes I did unfortunately didn't helped either. Well maybe sony support helps.
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.
Murphy's law is with me tonight. Tomorrow, I'm meeting someone who wants to buy my xperia P so tonight I plugged out my sim-card, deleted my stuff on the sd-card and did a factory reset. When I rebooted the device to check if indeed everything was deleted, my pc didn't recognise the device. I tried on an other pc but no reaction. I hear the connecting sound and get a notification on the pc that says "usb device not recognised". I tried installing the drivers via SUS but that didn't change anything. I then tried if my sim-card worked but the device gives a notification: the simcard could not be recognised. My simcard is working correctly as it works in an other cellphone. I then thought I could install titanium backup to search for an old backup but I can't even get the wifi going. I also installed other roms but I can't mount /system. The device I have is rooted and unlocked.
Could you help me solve this issue?
Can't understand the problem exactly, is the device booting? If it is what does it mean you cannot mount system?
You also say you have installed other roms, that require mounting of system.
What FW is installed?
ChikeD said:
Can't understand the problem exactly, is the device booting? If it is what does it mean you cannot mount system?
You also say you have installed other roms, that require mounting of system.
What FW is installed?
Click to expand...
Click to collapse
The device was booting but now it's stuck on the Sony image (before the loading image)
The problem is: the device doesn't recognise any simcard. I can't turn on wifi nor does the pc recognise my phone.
When in CWM (when I try installing a new rom that was already on the phone's sd-card beforehand) I can't mount /system.
I can pick a ftf from my sd-card to install a rom but afterwards the problems stay the same: no sim, no wifi, no usb connection possible.
r3inhout said:
The device was booting but now it's stuck on the Sony image (before the loading image)
The problem is: the device doesn't recognise any simcard. I can't turn on wifi nor does the pc recognise my phone.
When in CWM (when I try installing a new rom that was already on the phone's sd-card beforehand) I can't mount /system.
I can pick a ftf from my sd-card to install a rom but afterwards the problems stay the same: no sim, no wifi, no usb connection possible.
Click to expand...
Click to collapse
Can you enter fastboot or flash mode, and do you have flashtool and firmware to flash?
ChikeD said:
Can you enter fastboot or flash mode, and do you have flashtool and firmware to flash?
Click to expand...
Click to collapse
After a lot of cursing and sweating I managed to get it in fastboot, install an ics ftf and now it's updating via pc companion (wifi and pc connection work as before). The only problem that still exists now is the fact that the device doesn't recognise my sim-card. I checked if I didn't put it in the other way around but it's in the right position. I'm sure the sim works because I tested it in another cellphone.
Thanks a lot for helping me
I have never flashed FW with fastboot only kernels.
Maybe it have flashed, TA partition which is normaly not flashed?
Lets see after the update.
ChikeD said:
I have never flashed FW with fastboot only kernels.
Maybe it have flashed, TA partition which is normaly not flashed?
Lets see after the update.
Click to expand...
Click to collapse
I'm sorry it was in FlashMode The update gives me an error but somehow after I rebooted, the sim is now recognised :s
The only problem now is that I'm stuck in JB but I'm doubting to try anything else.
This cellphone has been nothing but random misery to me for the past 6 months The problem with the randomness is that I can't show it to the service centers (they keep on telling me they can't reproduce the problem).
r3inhout said:
I'm sorry it was in FlashMode The update gives me an error but somehow after I rebooted, the sim is now recognised :s
The only problem now is that I'm stuck in JB but I'm doubting to try anything else.
This cellphone has been nothing but random misery to me for the past 6 months The problem with the randomness is that I can't show it to the service centers (they keep on telling me they can't reproduce the problem).
Click to expand...
Click to collapse
Stuck with JB? You rather ICS?
I have recently uploaded Stock ICS 6.1.1.b.1.75 that I have.
ChikeD said:
Stuck with JB? You rather ICS?
I have recently uploaded Stock ICS 6.1.1.b.1.75 that I have.
Click to expand...
Click to collapse
Yea sorry I meant stuck on ICS. It's 2AM now over here so I'm getting a little bit tired I think I'll be able to find an ftf for JB with the search button tomorrow. Anyway, I thank you for your help I'm glad I found Flash tool to fix my problem.
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!
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.
Hi guys
I followed this guide for unlock bootloader and install magisk: https://forum.xda-developers.com/t/...re-and-gsi-rom-flashing-without-twrp.4344371/
I don't blame the author of the guide, it is my device, my responsibility, my decision to attempt this. My fault.
Everything was going great, I unlocked the bootloader successfully and my device wiped and rebooted. It boot back into android, I turn off, go to fastboot mode, and try to flash magisk img file I made earlier in the guide. It says success, then last step of the guide is to wipe with fastboot -w. This fails, says cannot wipe metadata. Reboot, now my phone says "your device is corrupted and cannot be trusted and will not boot"
No idea what to do here, so i try to use Xperia Companion to restore. But it refuses because it detect bootloader is unlocked. Now I try to use NewFlasher to flash firmware from XperiFirm, this starts off fine but then NewFlasher reaches this point
"Extracting sparse chunk super.040"
"Uploading sparse chunk C:\temp\xperiafirmware\flash_sesson_super.0.40"
"download:03b4c9c"
"ERROR: TIMEOUT: failed with error code 997 as follows:
Overlapped I/O operation is in progress
I have tried to do this with another computer, I have tried 2 other USB cables, I have tried another firmware (originally tried the latest version with open carrier but also tried with carrier specific one) I am now running out of ideas to try.
I can get to fastboot mode or flash mode, but if I try to boot OS it says "your device is corrupted and cannot be trusted and will not boot"
Any help or a point in the right direction would be much appreciated
Thank you so much in advance
Last week that happened to me. As long as you can go to fastboot you're good. First is relock the bootlaloader via fastboot then repair it using xperia companion. Or if you can download the firmware via xperifirm then flash it via flasher.
Also make sure that the PC your using has both an Intel CPU or AMD CPU and a full windows install not that cheap windows store only crap..but one you can actually install windows .exe files and make sure you have installed the Xperia drivers by turning off driver verification...o tried without and my 2 in 1 couldn't find my phone for Xperia companion nor the other flashing tool...
Thank you @Mangtas_666 @Ainz_Ooal_Gown I have no idea why but I just couldn't flash the UK firmware, tried 2 versions but neither would flash with NewFlasher. kept getting these timeout errors. But then i randomly decide to try the US firmware (XQ-BC62 instead of XQ-BC52) and it worked 1st try. My phone is up and running again!
The strangest part, when it connect to the internet and I apply all my UK settings, it somehow change back to XQ-BC52 on its own. It is detected as such in "about phone" now even though I didn't re-install firmware since fixing it with the US one. Oh well, i'm not going to complain, I'm just happy it's fixed. Thanks for replying
marshedpotato said:
Thank you @Mangtas_666 @Ainz_Ooal_Gown I have no idea why but I just couldn't flash the UK firmware, tried 2 versions but neither would flash with NewFlasher. kept getting these timeout errors. But then i randomly decide to try the US firmware (XQ-BC62 instead of XQ-BC52) and it worked 1st try. My phone is up and running again!
The strangest part, when it connect to the internet and I apply all my UK settings, it somehow change back to XQ-BC52 on its own. It is detected as such in "about phone" now even though I didn't re-install firmware since fixing it with the US one. Oh well, i'm not going to complain, I'm just happy it's fixed. Thanks for replying
Click to expand...
Click to collapse
No problem fam, glad it got sorted out