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.
Gentlemen, I couldn't find a section for Xperia Pro, please excuse me if this is misplaced.
I rooted my MK16i from ICS 4.0. according to a guide here on XDA forum, with no problems (from 4.1.a.435 .. i think).*
Then I installed system tuner and backed up the bloatware and what I believed was obviously named as packages that support them. Things were working great and the phone gained some performance improvements.
UNTIL, I installed Viber and Skype, and niether were working. I thought I would fix it by restoring all the backed up services and apps. Once I did that and rebooted the phone, it became useless
THe phone keeps rebooting. I get to the XPERIA loading screen and then it restarts again
I tried to connect it to the PC to flash another ROM with the Flashtool, but it is not recognized. All I get is in the computer screen a removable disk drive, that is not accessible.
Note: I didnt update the firmware after I rooted.
Can anybody help?
have you worked with flashtool before ? because there hardly could be any wrong with flashtool. use the latest version with proper drivers.
and since you have rooted phone, have you unlocked your bootloader ? if yes, then flash any custom kernel, go to CWM, then place rom zip on sdcard and stright flash rom via CWM.
flashtool should work though. you can try on different computer.
If flashing a kernel or installing custom ROM sounds a bit out-of-reach, you can always go for the repair option in PC Companion. It worked for me when I had soft-bricked my Neo V (it wouldn't go past the SONY logo). However, be advised that this repair option will erase your phone's internal memory. Also, your phone will be brought on the latest stock ROM, so you will need to root your phone again.
Good Luck!!! :good:
acemccloud1 said:
If flashing a kernel or installing custom ROM sounds a bit out-of-reach, you can always go for the repair option in PC Companion. It worked for me when I had soft-bricked my Neo V (it wouldn't go past the SONY logo). However, be advised that this repair option will erase your phone's internal memory. Good Luck!!! :good:
Click to expand...
Click to collapse
I tried to do somethingn like this but sony companion itself cannot detect the phone either.
My question is, is there a brick that cannot be fixed? I took it to a shop today and still they cannot fix it.
Have you tried to use sony update service?
How are you connecting your phone to flashtool?
Can you show us log from flashtool?
New development:
Now I tried to flash the phone with flashtool 32bit rather than 64-bit and it detected the phone! I could even flash the only firmware in Aeonworld's post Here.
Now I can see the phone connected in my computer.
However, the phone still won't boot but when I power on it gives black screen and after a short while, the led on the side becomes green.
For some reason though, I cannot continue with the rooting steps in his guide.
So anyways, after the second reboot, not the first for some reason, the phone gets detected in PC Companion, and I installed the update and now it is working again :victory:
Thank you all for your support.
moeness86 said:
New development:
Now I tried to flash the phone with flashtool 32bit rather than 64-bit and it detected the phone! I could even flash the only firmware in Aeonworld's post Here.
Now I can see the phone connected in my computer.
However, the phone still won't boot but when I power on it gives black screen and after a short while, the led on the side becomes green.
For some reason though, I cannot continue with the rooting steps in his guide.
So anyways, after the second reboot, not the first for some reason, the phone gets detected in PC Companion, and I installed the update and now it is working again :victory:
Thank you all for your support.
Click to expand...
Click to collapse
Good to hear that bro!!! R&D always makes a man better
Hey Guys,
Really hoping someone can help me out here. I've been trying to root a friend's Xperia U for the past 3 days now, without much luck!
Its on ICS, Firmware ST25a 6.1.1.B.1.10, unlocked bootloader. The two methods are Bin4ry's script and using FlashTool .For starters, USB debugging is enabled.
In both cases, the phone was undetected, even after installing loads of drivers found all over the web. After extensive reading, I came across a suggestion to enable USB tethering, and lo behold! The phone was detected!
"What's the problem then?", you ask?
Well, after following the careful instructions to restore the 'RootME' backup (on the phone), it phone reboots. When it comes back on, the screen is a mess, very dark (similar to a burnt screen) and extremely slow to respond. I read elsewhere that this is quite normal(!) and will be fixed after subsequent reboots.
The problem lies here, as I believe USB tethering is no longer ticked after the reboot, and it needs to be, doesn't it? Both Flashtool and the script wait for the phone to be detected, with no change at all. I somehow manage to navigate to 'Settings', but on trying to access tethering, it always crashes as below:
"Unfortunately settings has stopped"
Ugh.
How do I see the message when the screen is burnt out, you ask?
Pulling down the notification bar lets me see parts of the screen on its way down, and back up
Soooo...
Without USB tethering enabled, rooting does not complete, and I am left with a nearly un-useable device (until a factory reset). My internet speeds are terrible, and I am now in the process of downloading another firmware (6.1.1.b.1.54) in the hopes that it does not need USB tethering enabled to be detected by Flashtool (or Bin4ry's scripts)!
Thoughts? I want this baby rooted and CWM'ed!
Use xperia u toolkit..search in forums.eats very easy to root and do so many other things.i rooted mine using that only.
Sent from my ST25i using xda app-developers app
sanstorm said:
Hey Guys,
Really hoping someone can help me out here. I've been trying to root a friend's Xperia U for the past 3 days now, without much luck!
Its on ICS, Firmware ST25a 6.1.1.B.1.10, unlocked bootloader. The two methods are Bin4ry's script and using FlashTool .For starters, USB debugging is enabled.
In both cases, the phone was undetected, even after installing loads of drivers found all over the web. After extensive reading, I came across a suggestion to enable USB tethering, and lo behold! The phone was detected!
"What's the problem then?", you ask?
Well, after following the careful instructions to restore the 'RootME' backup (on the phone), it phone reboots. When it comes back on, the screen is a mess, very dark (similar to a burnt screen) and extremely slow to respond. I read elsewhere that this is quite normal(!) and will be fixed after subsequent reboots.
The problem lies here, as I believe USB tethering is no longer ticked after the reboot, and it needs to be, doesn't it? Both Flashtool and the script wait for the phone to be detected, with no change at all. I somehow manage to navigate to 'Settings', but on trying to access tethering, it always crashes as below:
"Unfortunately settings has stopped"
Ugh.
How do I see the message when the screen is burnt out, you ask?
Pulling down the notification bar lets me see parts of the screen on its way down, and back up
Soooo...
Without USB tethering enabled, rooting does not complete, and I am left with a nearly un-useable device (until a factory reset). My internet speeds are terrible, and I am now in the process of downloading another firmware (6.1.1.b.1.54) in the hopes that it does not need USB tethering enabled to be detected by Flashtool (or Bin4ry's scripts)!
Thoughts? I want this baby rooted and CWM'ed!
Click to expand...
Click to collapse
hope u have downloaded the new firmware, flash it by flashtool to help u simple there are custom kernal that are pre-rooted and CWM installed (just 10mb in size) you can find them here
http://forum.xda-developers.com/showthread.php?t=2391151
in the android 4.0 section
if u need more help just send me a private message by just cliking my avatar.
smartananallavan said:
hope u have downloaded the new firmware, flash it by flashtool to help u simple there are custom kernal that are pre-rooted and CWM installed (just 10mb in size) you can find them here
http://forum.xda-developers.com/showthread.php?t=2391151
in the android 4.0 section
if u need more help just send me a private message by just cliking my avatar.
Click to expand...
Click to collapse
Macha, thanks for your reply! :good:
I didn't realize this thread was around. I thought it was moved here.
Its all good
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 everybody,
I have a big problem because my Sony Xperia Z Ultra C6802 doesn't work anymore and doesn't respond to touch anymore since i flashed a certain twrp-recovery to the recovery-partition with fastboot.
So that's why i'm forced to connect my wired mouse to it to be able to control it as far as that's possible. I tried to flash another twrp-recovery to it but fastboot doesn't work anymore and is broken, or so it seems. In any case it's impossible to use fastboot or adb for that matter because the phone wont boot into the bootloader-mode. So could someone please help me with this issue??!! Before i started to hack my phone it worked perfectly and the display responded normally to touch input. The only thing i can do with it at the moment is boot into twrp and the rom which is Lineage-os 18.1. But even when i'm booted into the rom the display still doesn't respond to touch anymore and i still have to use my connected wired mouse to use it.
I hope to hear from you soon about this!
Kind regards,
Laurens
Bump.
[email protected] said:
Hello everybody,
I have a big problem because my Sony Xperia Z Ultra C6802 doesn't work anymore and doesn't respond to touch anymore since i flashed a certain twrp-recovery to the recovery-partition with fastboot.
So that's why i'm forced to connect my wired mouse to it to be able to control it as far as that's possible. I tried to flash another twrp-recovery to it but fastboot doesn't work anymore and is broken, or so it seems. In any case it's impossible to use fastboot or adb for that matter because the phone wont boot into the bootloader-mode. So could someone please help me with this issue??!! Before i started to hack my phone it worked perfectly and the display responded normally to touch input. The only thing i can do with it at the moment is boot into twrp and the rom which is Lineage-os 18.1. But even when i'm booted into the rom the display still doesn't respond to touch anymore and i still have to use my connected wired mouse to use it.
I hope to hear from you soon about this!
Kind regards,
Laurens
Click to expand...
Click to collapse
Bump
It seems your Z ultra is soft bricked. All you have to do is download "Xperia Companion" software
and press "Software Repair", then check the option "My device cannot be detected or started...", then follow the steps provided.
As a result you will have your zultra with a fresh stock rom (Lollipop) from Sony.
Then, you can custom mod your phone again.
EDIT: don't forget to lock your bootloader before running xperia companion!
xda_user749 said:
It seems your Z ultra is soft bricked. All you have to do is download "Xperia Companion" software
and press "Software Repair", then check the option "My device cannot be detected or started...", then follow the steps provided.
As a result you will have your zultra with a fresh stock rom (Lollipop) from Sony.
Then, you can custom mod your phone again.
EDIT: don't forget to lock your bootloader before running xperia companion!
Click to expand...
Click to collapse
Allright!! Thank you so much for responding to my post!! Finally now i can move on and fix my phone again and start all over again!! : D
xda_user749 said:
It seems your Z ultra is soft bricked. All you have to do is download "Xperia Companion" software
and press "Software Repair", then check the option "My device cannot be detected or started...", then follow the steps provided.
As a result you will have your zultra with a fresh stock rom (Lollipop) from Sony.
Then, you can custom mod your phone again.
EDIT: don't forget to lock your bootloader before running xperia companion!
Click to expand...
Click to collapse
I only have one more question: since i can't get access to the bootloader (fastboot), how do i bypass the problem of having to re-lock the bootloader again with (needed) access to the bootloader and fastboot before continuing with Xperia Companion??
Try This:
- Download FlashTool (I'm using version 0.9.30 and it works on my Zultra)
- Extract it to a folder (eg c:\flashtool)
- Go to C:\Flashtool\drivers and install the drivers (FASTBOOT, FLASHMODE and everything with Zultra... )
- Run C:\Flashtool\FlashTool64.exe, and let it update througth github
- Press the BLU botton, follow the instructions on how to connect your phone, then select the model and press Relock
EDIT: The following approach is the flashmode, so you may not have a problem. Please report here if you finally succeed unbricking your phone...
Good luck
xda_user749 said:
Try This:
- Download FlashTool (I'm using version 0.9.30 and it works on my Zultra)
- Extract it to a folder (eg c:\flashtool)
- Go to C:\Flashtool\drivers and install the drivers (FASTBOOT, FLASHMODE and everything with Zultra... )
- Run C:\Flashtool\FlashTool64.exe, and let it update througth github
- Press the BLU botton, follow the instructions on how to connect your phone, then select the model and press Relock
EDIT: The following approach is the flashmode, so you may not have a problem. Please report here if you finally succeed unbricking your phone...
Good luck
Click to expand...
Click to collapse
Could you please upload Flashtool 0.9.30 somewhere and post the downloadlink here in this thread? Because version 0.9.30 is nowhere to be found when i search for it with Google. Only version 0.9.34 is available from the official Flashtool-website, or can i use that one also?
Edit: well first i tried to run Xperia Companion while my phone was unlocked (just to confirm if it works or not) and it didn't gave me any errors, but now it does give me an error saying it can't continu because my phone is locked and i first have to unlock it again before continuing. Do you have any ideas on how to proceed now?
Ps: also my phone is now dead since i locked it again and doesn't respond to anything except it vibrates shortly after pushing the on-button but nothing appears on screen!
Ps1: It appears so that Xperia Companion probably means with "that my phone is locked" that i have a screenlock which i need to unlock first before proceeding.
And yet another thing happened namely: the program complaints about me not having a working internet-connection which doesn't make any sense since every other device in my house has a good working internet connection! I have included a picture of the error below so you can see what i mean.
Eventually it worked!! after successfully relocking the bootloader my phone was completely dead and only vibrated shortly after pressing the power-button and that was it. But since Flashtool reported that the relocking-procedure was successfully fullfilled, i then carried on with Xperia Companion but this time on my Macbook Air (because of the error i got on Windows, see screenshot).
Finally i managed to let it install the original sofware and this time it completely reanimated my phone again, and even my display returned back to normal again!!
So now i can finally begin all over with installing the latest Lineage version onto the phone, thanks to you!!
Ps: before i forget: i found eventually a Flashtool website which has the version you got (0.9.30) so i downloaded that and used it in the process!!
So i can't express enough how much i appreciate your help and can't thank you enough for all of this!!
Glad you could make it!
This is the standard procedure when things go wrong with custom flashing with any xperia device that becomes completely unresponsive.
Two things:
- version 0.9.30 is what I'm currently using. Most likely the newer versions are working as well.
- To unlock your bootloader again, you only have to press the BLU button in Flash Tool and then UNLOCK.