Hello, this is my first post with XDA, please forgive any poor grammar, spelling ect. Please assume I do have the proper drivers installed and downloaded the rom md5 check ect.
Like the title says my Xperia Play r800at is stuck in a boot loop. Trying to give you a picture of where I am right now ill put the list of events in order:
1 - Had an xperia play on stock for about a year. One day I get bored and successfully flashed XPLAY with flashtool, using the proper rom found on XDA.
2 - Subsequently, rooted Xplay using zerg rush (I believe it was) thing is, I'm pretty sure I left the boot loader untouched. Xplay continues to work fine for several weeks until.
*Here's where things start to fall apart!*
3 - Xplay begins to experience "snowy" screen, indicative of bad flex cable, had to replace that leaving the device was out of commission for a couple weeks.
4 - Flex cable arrives, I replace it . Upon first startup snowy screen problem is gone, however Xplay refuses to boot past the first "Sony Ericsson" startup (screen goes black and repeats - hence boot loop).
5 - I read on other forums that re-flashing the rom has worked for other people experiencing this issue. I tried installing the same firware rom that last worked - still bootloop. I tired the default firmware rom from SE - still bootloop.
6 - Tried using the Sony Companion Repair tool. At first it wouldn't do work coming back with "cannnot find software for this device error". Assuming that its because I'm rooted and possibly unlocked the bootloader somehow, making the sony repair tool not play nice.
7 - I ran the "Xperia_Relock_bootloader.ftf Application (found on xda) which seemed to relock the bootloader (or something). Then after that I tried to re-flashed a rom - still boot loop.
8 - But after doing that Sony Companion finally does recognize my phone and allows me to repair the device. Which is supposed to fix boot loop error... but not for me
At this point I'm all out of ideas and direction. Anyone help please??
zimension said:
Hello, this is my first post with XDA, please forgive any poor grammar, spelling ect. Please assume I do have the proper drivers installed and downloaded the rom md5 check ect.
Like the title says my Xperia Play r800at is stuck in a boot loop. Trying to give you a picture of where I am right now ill put the list of events in order:
1 - Had an xperia play on stock for about a year. One day I get bored and successfully flashed XPLAY with flashtool, using the proper rom found on XDA.
2 - Subsequently, rooted Xplay using zerg rush (I believe it was) thing is, I'm pretty sure I left the boot loader untouched. Xplay continues to work fine for several weeks until.
*Here's where things start to fall apart!*
3 - Xplay begins to experience "snowy" screen, indicative of bad flex cable, had to replace that leaving the device was out of commission for a couple weeks.
4 - Flex cable arrives, I replace it . Upon first startup snowy screen problem is gone, however Xplay refuses to boot past the first "Sony Ericsson" startup (screen goes black and repeats - hence boot loop).
5 - I read on other forums that re-flashing the rom has worked for other people experiencing this issue. I tried installing the same firware rom that last worked - still bootloop. I tired the default firmware rom from SE - still bootloop.
6 - Tried using the Sony Companion Repair tool. At first it wouldn't do work coming back with "cannnot find software for this device error". Assuming that its because I'm rooted and possibly unlocked the bootloader somehow, making the sony repair tool not play nice.
7 - I ran the "Xperia_Relock_bootloader.ftf Application (found on xda) which seemed to relock the bootloader (or something). Then after that I tried to re-flashed a rom - still boot loop.
8 - But after doing that Sony Companion finally does recognize my phone and allows me to repair the device. Which is supposed to fix boot loop error... but not for me
At this point I'm all out of ideas and direction. Anyone help please??
Click to expand...
Click to collapse
I also have a R800at, when you unlock the bootloader it pretty much becomes at R800i. There is only one thing I can think of is "R800i_4.0.1.A.0.283_ReFlash" which is apparently supposed to unbrick your device you can download it here http://forum.xda-developers.com/showthread.php?p=42229855#post42229855 I've never used it but I always keep it saved just in case.
You should definitely unlock your bootloader again before trying this. Then you should flash an unlocked vendor frimware, either R800i_4.0.2.A.0.62_phoenixvendor or R800_4.0.2.A.0.79 after you flash the "reflash" frimware.
Related
Trying to fix an Xperia Play R800at. It was running the R800a 2.3.4 North American Generic ftf, and my son had rooted it using gingerbreak (he thinks) on flashtool. Also at one point he attempted to unlock the bootloader but doesn't think that worked
Anyway, the phone was running fine for a long while, and then we switched from a 16gb sd to a 32gb sd. During the switch my son moved some games from the phone memory to the sd. Other than the loss of game progress, everything seemed to be working fine. About a week later the screen started going black during games or when he closed the phone. Because of the feedback he could tell the phone was still operating, just no lit screen. The problem would clear on reboot.
So we researched the problem on Sony and XDA, and it appears the best solution was to reload the software. However since the phone was rooted we had to reload using flashtool first, and then force a recovery reload via PCC. Meanwhile the phone display stopped working altogether and the phone would vibrate but seemingly not boot up.
Steps we have taken so far:
- flashed back to AT&T 3.0.1.8.0.285 using flashtool Result: flashtool said successful but phone would vibrate but not boot
- used PCC to load the Xperia R800 Play software Result: software for phone not found
- used X10_V1_BLRelock.ftf just in case my son was able to unlock the bootloader
- flashed back to AT&T 3.0.1.8.0.285 using flashtool Result: flashtool said successful but phone would vibrate but not boot
- used PCC and the Sony Recovery to load the Xperia R800 Play software onto the phone Result: successful load but goes into bootloop (SE logo comes up bright, fades, blacks out, and does it again and again
- tried various other play ftfs in flashtool - flashtool now telling me USB Debugging is off, and WARN - This file is ignored : simlock.ta - ftf loads otherwise, but Sony's Recovery tool does not recognize anything but the AT&T software
- went back to AT&T 3.0.1.8.0.285 and then re-updated on Sony - same bootloop
- tried to boot the phone in fastboot mode by holding the search button and plugging the usb in - appears to connect in flash mode
So - I believe it is now un-rooted, and relocked, USB Debugging is off, the standard AT&T 3.0.1.8.0.285 software is on there, it goes into bootloop
Any ideas how to fix from here?
I got a soft bick recently in my Xperia Play r800a, but the screen always worked. What I did was flash an r800i ftf and it worked. The simlock.ta omission is maybe an effect of flashing the x10 BL unlock bundle, but it doesnt work to unlock the xplay, and maybe thats why the phone is like that (who knows..... just never flash something made for other model until it is confirmed to work on yours, like some arc and neo v basebands and scripts)
The debugging off state is caused by the stock ftf flashed. When you flash it you get a complete new system with stock configs, so the debuggin is set off by default and thats what you got. Its also unrooted, just if you were wondering
Maybe you should try flashing an r800i ftf (all r800a,at,i work on your device, cause they are all GSM. But NEVER flash an r800x Rom cause it works on CDMA, and it will surely brick your phone.
You could also try to flash a custom stock-based Rom. They can work on stock kernel and will give you a clean sytem as well, but since your screen is not working, it has to be in .ftf format. Just check 'skip kernel' and 'skip confirmation' when doing so.
The only method for a branded phone for unlocking bootloader is to use testpont method (paid) by alejandrissimo (look unlock-bootloader.com). He maybe repair your phone btw
Sent from my SK17a using xda app-developers app
rlpip said:
Trying to fix an Xperia Play R800at. It was running the R800a 2.3.4 North American Generic ftf, and my son had rooted it using gingerbreak (he thinks) on flashtool. Also at one point he attempted to unlock the bootloader but doesn't think that worked
Anyway, the phone was running fine for a long while, and then we switched from a 16gb sd to a 32gb sd. During the switch my son moved some games from the phone memory to the sd. Other than the loss of game progress, everything seemed to be working fine. About a week later the screen started going black during games or when he closed the phone. Because of the feedback he could tell the phone was still operating, just no lit screen. The problem would clear on reboot.
So we researched the problem on Sony and XDA, and it appears the best solution was to reload the software. However since the phone was rooted we had to reload using flashtool first, and then force a recovery reload via PCC. Meanwhile the phone display stopped working altogether and the phone would vibrate but seemingly not boot up.
Steps we have taken so far:
- flashed back to AT&T 3.0.1.8.0.285 using flashtool Result: flashtool said successful but phone would vibrate but not boot
- used PCC to load the Xperia R800 Play software Result: software for phone not found
- used X10_V1_BLRelock.ftf just in case my son was able to unlock the bootloader
- flashed back to AT&T 3.0.1.8.0.285 using flashtool Result: flashtool said successful but phone would vibrate but not boot
- used PCC and the Sony Recovery to load the Xperia R800 Play software onto the phone Result: successful load but goes into bootloop (SE logo comes up bright, fades, blacks out, and does it again and again
- tried various other play ftfs in flashtool - flashtool now telling me USB Debugging is off, and WARN - This file is ignored : simlock.ta - ftf loads otherwise, but Sony's Recovery tool does not recognize anything but the AT&T software
- went back to AT&T 3.0.1.8.0.285 and then re-updated on Sony - same bootloop
- tried to boot the phone in fastboot mode by holding the search button and plugging the usb in - appears to connect in flash mode
So - I believe it is now un-rooted, and relocked, USB Debugging is off, the standard AT&T 3.0.1.8.0.285 software is on there, it goes into bootloop
Any ideas how to fix from here?
Click to expand...
Click to collapse
when you did this were you using the latest version of flashtool? installed all adb drivers? is the AT&T 3.0.1.8.0.285 the original back up image of the phone it was rooted? or did you download this from any other source?
Update
fritzbored said:
when you did this were you using the latest version of flashtool? installed all adb drivers? is the AT&T 3.0.1.8.0.285 the original back up image of the phone it was rooted? or did you download this from any other source?
Click to expand...
Click to collapse
Yes - latest version of flashtool. AT&T ftf came from the one listed here http://forum.xda-developers.com/showthread.php?t=1603737
julian280 said:
... The simlock.ta omission is maybe an effect of flashing the x10 BL unlock bundle, but it doesnt work to unlock the xplay, and maybe thats why the phone is like that (who knows..... just never flash something made for other model until it is confirmed to work on yours, like some arc and neo v basebands and scripts)
When you flash it you get a complete new system with stock configs, so the debuggin is set off by default and thats what you got. Its also unrooted, just if you were wondering
Maybe you should try flashing an r800i ftf (all r800a,at,i work on your device, cause they are all GSM.
You could also try to flash a custom stock-based Rom. They can work on stock kernel and will give you a clean sytem as well, but since your screen is not working, it has to be in .ftf format. Just check 'skip kernel' and 'skip confirmation' when doing so.
The only method for a branded phone for unlocking bootloader is to use testpont method (paid) by alejandrissimo (look unlock-bootloader.com). He maybe repair your phone btw
Click to expand...
Click to collapse
I actually did the Blagus relocking ftf which says it is for the Play too here: http://forum.xda-developers.com/showthread.php?t=1134334 After I did this Sony Mobile Update Service started recognizing the phone and 285 sw version and allowed software download and repair.
I figured the Debugging setting and the rooting reset when I flashed it. I tried r800i ftf - same problem. Was thinking about a custom ROM but first things first. I am going to replace the ribbon cable and try again. I suspect the original problem was possibly ribbon cable related. (I shot alejandrissimo a note and he suggested I try this first as well.)
Thanks both for your reponses.
Ok, first of all, I have been searching these forums and google all day, so please at least consider reading my question.
So today I decided to finally update my Xperia Arc S to Jelly Bean with CyanogenMod. I own this device for 2 years and all I have done hack-wise was rooting it.
And what the problem is? The update failed, and according to what I have read, this may have been caused due to insufficient internal memory. After that, my phone rebooted and it just can't boot now, it gets stuck with the Sony Ericsson logo.
I also have read that possible solutions were: Update with PCC, SEUS, Flash it with a Stock ROM, flash a stock kernel... And I CAN'T do any of these. PCC and SEUS just don't recognize my phone, SEUS doesn't even have Arc S on the list! The closest i have got to solving the problem was with flashtool, in which I got this happy message "15/044/2013 20:44:42 - ERROR - Error flashing. Aborted" over and over. Having read that this could be caused by the kernel, I tried flashing it instead. But after installing DroidSDK, I can't detect any devices using the "adb devices" command.
Any ideas? If I am just being stupid, I'm sorry, but I swear I searched a hell lot before posting this >_>
Even the repair option in PC Companion?
First - sorry for my english.
Second - try this:
Deattach battery from phone and connect the charge. LED must be green. Wait for ~10 min & then try to flash via Flashtool again and again. Please be patient. In some situations successful flashing might be on 5-6 flashing.
KamenPurin said:
Ok, first of all, I have been searching these forums and google all day, so please at least consider reading my question.
So today I decided to finally update my Xperia Arc S to Jelly Bean with CyanogenMod. I own this device for 2 years and all I have done hack-wise was rooting it.
And what the problem is? The update failed, and according to what I have read, this may have been caused due to insufficient internal memory. After that, my phone rebooted and it just can't boot now, it gets stuck with the Sony Ericsson logo.
I also have read that possible solutions were: Update with PCC, SEUS, Flash it with a Stock ROM, flash a stock kernel... And I CAN'T do any of these. PCC and SEUS just don't recognize my phone, SEUS doesn't even have Arc S on the list! The closest i have got to solving the problem was with flashtool, in which I got this happy message "15/044/2013 20:44:42 - ERROR - Error flashing. Aborted" over and over. Having read that this could be caused by the kernel, I tried flashing it instead. But after installing DroidSDK, I can't detect any devices using the "adb devices" command.
Any ideas? If I am just being stupid, I'm sorry, but I swear I searched a hell lot before posting this >_>
Click to expand...
Click to collapse
You have installed PcC,SEUS,good.Install gordon flash just in case(look for it on google)!Install flashtool on your pc,turn your Arc on(i know it's bootlooping,but try it can't hurt),run flashtool(just run it),connect your phone(it must be ON),and leave it for a while and see if flashtooo is recognizing your phone(if it does there will be some lines)!.-If this works continue!Download stock .ftf file for lt18i!
I suppose you know how to use flashtool?!.
Try that if that doesn't work SEUS will work and it has Arc and Arc S just look a bit,i know 'cause i have it.PcC won't work 'cause your phone isn't booting up,Well at least it never worked for me when i bricked my arc like this,but did work flashtool,always.I couldn't use SEUS 'cause of a bootloader unlocked.
Good luck,hope you'll fix it and next time,before flashing read the thread twice and follow the exacted steps,no jumping...
P.S for flashing JB you need to have ICS inatalled and i'think bootloader unlocked(not sure)...Cheers
Sent from my Xperia Arc LT15i using XDA
stuck on logo
I am having the same problem, my arc s is stuck on the sony logo, i tried using flashtool but it is always giving me this error :"12/000/2014 02:00:22 - ERROR - 12/000/2014 02:00:22 - ERROR - Error flashing. Aborted".
i tried using SEUS but it doesn't recognize the phone
I don't know what else to do , need help
Hi there!
I don't know if anyone will read these lines, since it's already quite an old phone, but I'll give it a try anyway.
Short story: my wife dropped her phone and the digitizer got smashed. I removed it and before I got the new digitizer on, our kid had had the time to break the LCD. So I bought a new LCD + digitizer module and installed it. Then I started the phone and got stuck at the Sony boot logo.
I've tried the repair function of the Xperia companion. It apparently detects the phone and goes throught the whole procedure, then tell me the phone's software's been repaired, but when I start it, I'm stuck at the logo again.
Just in case you wonder:
- bootloader is locked
- USB debugging was not enabled
So is there anything I can try, or should I just head to the phone store and buy her a new one? She was happy with it and sees no reason to change it, so if there's a chance we might save it...
EDIT: I have also tried this now:
- download a stock ROM in ftf format
- installed flashtool
- flashed the ROM (no USB debugging or unlocked bootloader required)
- flash successful
But I'm still stuck at the Sony logo, only that now, instead of having "Sony" in the center of the screen and "Xperia" on the bottom, I only have "Sony" in the center. I was hoping for more change than that
Thanks!
Fa
Alright, I haven't received a lot of answers, so I'm just going to post as I go. Maybe I'll get the damn thing boot again and this will help someone in the future.
Now I have downloaded a custom ROM, a recovery (actually I have dld both CWM and TWRP) and I'd like to flash it BUT: in order to do that, the bootloader must be unlocked.
I used flashtool (the "blu" button), and it worked. So that's out of the way. Now it seems I should have USB debugging on, but surely there is a way to flash a ROM without it? Or am I screwed?
How do I flash a recovery for the first time? The files I downloaded are img.
Thanks!
And here we go again
So I found from the list of Nougat ROMs that a very good one is LOS by Munjeni, so I decided to go with it (if I get the phone to work, I might as well go with a good ROM .
The instructions were clear, so first, what I did was:
- flash the openbootloader file to enable permanent recovery (flashed with Flashtool)
- flash recovery, I first went with TWRP provided on Munjeni's own page, but I could not use the touch interface, so I switched to CWM, since it offers physical button support (flashed with Flashtool)
- Then I copied the ROM (zip file) I downloaded from the same place to my microSD and inserted it into the phone.
- I wiped everything as required in the instructions
- I flashed the ROM from CWM
And voilà! I can now boot into the ROM!
The only problem is that my touch screen is unresponsive, although the whole LCD/digitizer assembly is brand new
It seems the touch interface just does not work, since it is unavailable in both recoveries and in the ROM.
Anyway, this is probably it for this thread, since the issue being stuck on Sony logo and not booting is solved (well, it boots into a ROM, not stock, but that's beside the point). Hope this will help someone else in the future!
Cheers!
Hi Everyone,
I have a 5T running android 9 - completely stock. The device is SIM free, I have never customised it at all - if anything it's never been connected to a PC even.
A few days ago I was using my phone as normal (on whatsapp) but it completely froze. It now boots up to the "Your device is corrupt and cannot be trusted and may not work properly" - it freezes on start up and won't work at all.
- I can get to the fastboot screen
- I can get to the recovery screen to install from ADB
The fastboot screen says in red - device state - locked.
The device is a clean, un-customised phone. Only a few days prior I checked for any OTA updates but I haven't received android 10 yet.
I haven't flashed phone firmware or anything for years now. (By years, I literally mean years - back in the Nokia 8210 days). My only other experience of flashing firmware was with Samsung phones and 'debranding' them.
As I was not trying to root the device or anything - how do I fix this issue? I've searched the forums but I cannot fine a scenario similar to mine therefore I'm a bit confused as to what to do to resolve it.
I've tried to sideload this - oneplus.com/uk/support/softwareupgrade/details?code=PM1574156155944 via recovery but it says installation failed.
Any help appreciated thanks!
Sounds like you're straight out of luck to recover any data if your device is completely stock, as to unlock your bootloader to access encrypted data would mean a factory reset. You could try try one of the unbrick tools using the guide here. You will lose your data.
I tried the unbrick tool here - forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
... and it doesn't work. The phone now boots to a blank screen with a constant white LED.
Could this be a hardware issue?
I'm not too concerned about losing my data - already gave up on trying to keep my data when the problem first occurred!
After the 4th use of the unbrick tool (each time it completes successfully) I was finally able to boot into the phone.
I got as far as setting the region but then it wouldn't find any wifi networks. It then completely froze on this screen and is now back to "your device is corrupt and cannot be trusted" and will continually try to boot and freeze on the oneplus logo. Sometimes it will boot to a blank screen with a white LED.
Has anyone else had this issue? I'm definitely suspecting a hardware issue now...
oneplus5t_ said:
After the 4th use of the unbrick tool (each time it completes successfully) I was finally able to boot into the phone.
I got as far as setting the region but then it wouldn't find any wifi networks. It then completely froze on this screen and is now back to "your device is corrupt and cannot be trusted" and will continually try to boot and freeze on the oneplus logo. Sometimes it will boot to a blank screen with a white LED.
Has anyone else had this issue? I'm definitely suspecting a hardware issue now...
Click to expand...
Click to collapse
Problem fixed?
unfortunately not. Any ideas on next steps?
That's an odd issue for sure. My only idea would be installing TWRP and maybe formatting from there and using fix permissions etc. to see if it has any effect.
I've done some googling to try and understand "TWRP" but I'm not sure I fully understand. Are there any forum posts I can refer to?
- phone has been flashed several times
- before this whole saga dev mode was enabled, but only to reduce animation scale - USB debugging was never enabled
- the phone has always been stock / sim free - never rooted
Thanks
Can you get into recovery? If yes then try connecting to a pc whilst in recovery as it should let you open your phones internal storage on PC but im not too sure if stock recovery allows it, (TWRP) does. Then copy whatever files you need. Let us know if you can get into fastboot mode aswell
It sounds similar to an issue I have just experienced with a friends 5T. In my case it's a hardware issue (seems like Wi-Fi has died). Just for kicks try to flash the Android 7 firmware. For some reason it allowed me to boot the phone fine and use it, albeit without any Wi-Fi. I sideloaded OOS 4.7.6 and that seems to be the last version 7. You could also use the older unbrick software. Academic I fear as I think you have a hardware issue.
Hey all,
Haven't touched this phone in years, but was inspired to pick it up again yesterday. I can't for the life of me remember all the crap I did to it back in the day, but there was some "minimal" thing installed to it that made it play PS games better or something, and there was some LuPuS wolf thingy that came up when it booted.
Half the stuff I tried to do within the phone was crashing, so in my infinite wisdom I decided, "Hey! Why not just flash back to stock firmware!?"
And so the genius that I am, attempted to do just that.
So I found Flashtool and a nice stock rom and pretty much it did something, but then eventually fails every time as "Failed to verify sin header" and aborts the flash.
Now the phone is stuck in a loop, either the Sony Ericsson logo comes up, then a exclamation point in a triangle, or it goes into Flash mode.
I've tried several different stock roms:
R800i_4.0.2.A.0.58_Enhanced
R800i_4.0.2.A.0.62
And I've tried several versions of Flashtool:
flashtool_0.9.24.4
flashtool-0.6.8.0-windows
flashtool-0.9.11.0-windows
But no combination of any of those gets me past the error during flash.
I also tried the Xperia Companion, but it only complains my phone is locked and won't let me do anything. Of course it's not locked, and I can't even unlock it because it doesn't boot into anything.
I also tried the SEUS but it crashes upon launch (Windows 10).
Anything else I can do? Or is this phone toast?
Thank you in advance!
EDIT:
Alright, time for some extra silliness... and maybe I just don't understand what I'm reading here. So the sticker on the phone under the battery reports R800x, indicating the Verizon version.
The old Flashtool actually let me flash a stock Verizon ftf on there, but then it returns to the looping between Sony Ericsson/Exclamation point and Flash mode.
I ran the 9.24.4 version of Flashtool and attempted the same Verizon stock ftf. And here's what it said....
Current device : R800i
Also, the newer versions of Flashtool report this:
Bootloader status : UNROOTABLE
But the older copy of Flashtool reports I'm rooted.
I did try to get SUS working on another PC, but has same issues, seems to crash/die reaching out to a server that no longer exists.
EDIT 2:
Woohoo! Fixed! Continued to research all the info out there, and seems I just had to relock bootloader.