My Arc just stopped working without a reason - one moment it just didn't boot up.
I had unlocked bootloader, phone was rooted and had stock firmware LT15i 4.0.2.A.0.42 Generic Global.
Battery was apparently dead, after replacing it i could connect to the phone with flashtool and fastboot. Still i couldn't boot up the system.
So - as i had no better idea, i flashed phone with Xperia 2011 Range_FreeXperia_ALL.ftf and LT15i_3.0.1.A.0.145_Global.ftf - in case radio was damaged or sth.
After that phone manages to boot up from time to time, but in less than minute dies off and reboots. Mostly it reboots before reaching to homescreen.
So i kept trying with flashing with newer firmware, but no success. its even gets worse - with every other firmware it even doesn't try to boot up.
Flashed firmwares:
LT15i_4.0.A.2.368_Generic Global.ftf
LT15i_4.0.1.A.0.283_Generic Global.ftf
LT15i_4.0.2.A.0.42_Generic Global.ftf
LT15i_4.0.2.A.0.62_Generic Global World.ftf
There were no errors during flashing - with any of firmwares.
Any thoughts what i should try to fix my phone? I have ran out of ideas
Try a different kernel and enter cwm. If you can do that then use flashtool, flash .62 firmware, put a custom rom on the sd card like arconium or se tweaked, fastboot dooms kernel v19 and attempt to flash the rom.
What kernel would you recommend?
For 2.3.4(.62) then doomlords kernel.
sinkster©
So i did flash my phone with .62 using Flashtool. Tried both Doomlord kernels -
ARC-DooMKernel-v19-BM-v2-lower_boot.img
ARC-DooMKernel-v19-BM-v2-high_boot.img
In both cases after turning the phone on i can feel a slight vibration like usual, but that's it. Nth shows up on the screen - so i couldn't enter recovery.
I even tried relocking bootloader and "repairing" the phone using PC Companion. Still nth happens during booting.
Would it help to erase boot, recovery, system and try again with newest firmware and DooMKernel? Or might erasing harm sth?
Flashtool shows me that loader version is: R4A066. Maybe i should update that somehow?
Try flashing .62 with flashtool then boot the phone, before using fastboot.
sinkster©
That's how i usually do it. Tried again, didn't solve the problem - won't boot up.
Assuming it's nothing obvious(user data not wiped, etc)as you've done it before. You originally flashed 2.3.3? And if you run that it boots, so could it be the 0% battery issue? I haven't had issues as I've never flashed a previous gb version, but the 0% issue was pretty common but now resolved(somewhere in here)
Yes, always have wiped userdata and it's probably not 0% issue - if i try boot up LT15i_3.0.1.A.0.145_Global Customized.ftf then i sometimes can glimpse homescreen for couple of seconds and it doesn't show battery as empty.
I understand that flashing Xperia 2011 Range_FreeXperia_ALL.ftf and LT15i_3.0.1.A.0.145_Global Customized.ftf won't update everything possible? Maybe i need to extract and flash some components from some newer ftf's or sth?
All I can think of is maybe the boot file is damaged, or corrupted, it seems to be happening to a few posters. Try connecting in fastboot, use 'erase boot', and maybe system too, and start again.
sinkster©
I have tried 'erase boot' too, doesn't help. What puzzles me, is why my phone chooses to boot up (although continiously rebooting) in 2.3.3? I would have given up hope a long time time ago, if it wouldn't boot up at all
Thanks anyway for trying to help, if any new idea pops into your head (others are also welcome to help me), please let me know
Maybe i do sth wrong what is very obvious, although in June '11 i already unbricked once that phone using the same method and it worked:
1) flashing Xperia 2011 Range_FreeXperia_ALL.ftf
2) flashing LT15i_3.0.1.A.0.145_Global Customized.ftf
3) flashing newest firmware..
Related
OK i've been trawling the forums but so far i've not found an answer.
i've got a T-mobile branded arc and its bootloader is unlocked. it is running .62 firmware.
i'm trying to flash the generic uk .42 firmware but i keep getting the following error:
ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_STATIC="SIN_HEAD_VER";ERR_DYNAMIC="Failed to verify sin header";
i've tried a couple of different firmwares, and i've definitely got my phone in the right mode with usb debugging enabled.
can anyone help?
Thanks
Me again... I remembered a similar thing with someone's x10 a while ago, it was caused by low battery while flashing. The resolution was to repair the boot, which for the x10 meant a service centre. But you can use fastboot to do it, just connect in fastboot and use the erase command, erase boot, erase userdata, erase system. I'd give that a try.
sinkster©
Thanks for the response. Following something I'd read on the X10 forums I did consider doing a repair via pc companion but I wasn't sure what implications it might have following having my boot loader unlocked.
I'll give this a go and let u know if it works.
Thanks again!
ok could really do with some help now. still has the same problem with the added fact that my phone is now bricked.
Please help!!!!!!
after 'erase boot' have you tried booting a new .img?
D/L a rom that's cwm flashable to your sd card, boot into doomkernel and try flashing the rom(if you haven't already)
thanks for the quick response.
i've tried flashing the cyanogen boot image but sadly that fails. sorry to sound like a noob but i went to the github site to download doomkernel but for the life of me i couldnt find the boot image.
in the latest flashtool need to install the drivers or not? inside drives folder one..
I'm really sorry but i don't understand. I don't have any driver issues if thats what your getting at.
Are you able to boot kernels with fastboot?
hey sinkster.
ok managed to install different boot images (tried a few just to check) and all that happens is that i get the splash screen and it stays there.
still can't install any roms using flashtool. and to be honest i'm not sure how to do it using fastboot
any ideas?
thanks
Once you have installed the kernel, disconnect the phone from the pc and turn it on. When you see the kernel image, press the back button. This should send you into CWM and from there you can install a rom like "update.zip". On my girlfriend's x8 after flashing nAa kernel I was also surprised that it did not boot again to stock rom, but afterwards I pressed the back button which led to CWM and flashed a rom. Try to wipe data, cache, dalvik and battery stats also. The rom should work. If you notice any problems, just reinstall the rom again wiping data, cache, dalvik and battery stats (first time I got wifi issue and battery drain issue - android was taking 46% ) ). All the best. I hope I helped.
For flashtool just d/l a rom file(ftf), put it in the firmware folder, power down phone, run flashtool, click flash, select firmware. When it says connect then connect usb while pressing back(led is green) and rom should flash with a log on screen. this will flash an entire rom and kernel, or a baseband. For fastboot, open fastboot folder, move kernel(s) to folder, shift&right-click and select 'open command window here', power down phone and connect usb while pressing menu(blue led). In cmd window you can type 'fastboot devices'to check the phone is connected, to boot a kernel then type 'fastboot flash boot boot.img', or whatever the kernel file is called(I have 4or5 so name them individually)
so first use flashtool and flash the file here http://forum.xda-developers.com/showthread.php?t=1359303
that gives you stock rom/kernel; if you want a custom rom put it on your sd card to flash with cwm. if you want or need a custom kernel the fastboot doomlords kernel
These are the basics, you probably know all the above but just in case.
Gents thank you for your help. got somewhere finally. managed to flash BLENDMIUI onto phone andd got it working. for some reason SE Tweek does not want to work.
sinkster thank you for the summary.i originally mis-typed. when i said i didnt know how to flash a rom with flashtool i actually meant fastboot. but i'm now fully up to speed using cwm.
and thank you valy_cta, that got it working in the end.
its strange that i still get the same error when flashing any roms with flashtool though. tried about 6 or 7 different ones and i still get the initial error.
if i repair the phone with pc companion, would it lock the bootloader again?
other way round, you need to lock the bootloader before you update. Just unlock again, it'll be the same code.
sinkster©
ah the problem with that was that i had to get jinx13 to unlock it.
really what i want to do if flash a stock rom, which i still can't seem to do.
EDIT: since flashtool doesn't seem to work for me I found out from one of DooMLords threads that you can extract the ftf files and flash with fastboot. job sorted.
(Just expaining how i got to the screen...in a lot of detail) Okay so yesterday i unlocked my bootloader through sonys website and everything was fine. Then i decided to try to put CM9 on it from a tutorial i found, didnt work. I then flashed back to verizons 2.3.3 through flashtool and everything was fine...but then i decided i wanted to go back to ZeuscNXTLite rom, i was lazy and used the recoveryPLAY.img to go to CWM. I forgot to clear the cache, data, etc. and i thought it was in a hard-brick because i could hold the power button all it would do is vibrate and i could still put it into flash boot(or whatever the green light means) but the screen always stayed black. I left it on my charger all night hoping it would magically come back i guess...today i got home to find the green light on it flashing faintly and quickly. I decided maybe its working now if i flash the .ftf so i did. Nothing happened so i thought maybe it was the bootloader so i tried using a bootloader relocker .ftf file but that just made my computer inable to recognize my phone. It would flash red a few times now when i plugged it into flashboot then go to flash mode and i could use flashtool. I tried adding the 2.3.3 .ftf back to my phone but it failed halfway through. So about 4 mins after doing this i look at my phone and see the Sony Ericsson screen but after that screen i see a triangle with an exclamation point inside of it and a phone under it. It keeps booting to this screen then shutting off over and over again. Now my question...does anyone know how to fix this? I dont really think its still in a brick since it goes to this weird screen.
Sorry for the extensive explanation. Also sorry if this was a repeat i tried searching but honestly have no clue what to search or even call this.
If you can still use flashtool follow this great guide http://forum.xda-developers.com/showthread.php?t=2054512 so you can fastboot a kernal and get into cwm then you can flash a new rom after wiping everything. :fingers-crossed:
The yellow triangle means you're in download mode, but I don't know what to do since I never had it on the Play.
Flashing the ftf will fail sometimes, you can keep re trying, its finicky so you have to make sure to use a good cable, preferably on a USB port that is not 3.0, and have few other USB devices connected at the sametime as possible.
The reason why CM9 didn't work because sometimes the kernel included does not boot. The boot.img from the FXP152's CM9 rom is one of the working one, you can separately flash it using fastboot.
I flashed a bootloader lock ftf file so wouldnt installing a kernel brick my phone again? Also could flashing the stock ftf file again while my phone is in download mode brick my phone? I'm just being extra careful now...dont want a hard bricked phone.
bandoncontortion said:
I flashed a bootloader lock ftf file so wouldnt installing a kernel brick my phone again? Also could flashing the stock ftf file again while my phone is in download mode brick my phone? I'm just being extra careful now...dont want a hard bricked phone.
Click to expand...
Click to collapse
Did flashing the bootloader lock ftf file work? you need to find out if your bootloader is locked or unlocked.If you have phone off, and hold on to search and you plug in USB to computer and get blue light your bootloader is unlocked (flashboot mode)If its unlocked just flash a kernel wipe and install a custom rom
If it is locked and you can use flashtool you can flash a stock ftf. Kernal is included in stock rom which you can find on forum
Ok i just put the stock ftf on it through flashtool. I tried to turn it on and it shows the Sony Ericsson screen and then the Android screen the turns off. Any help? It's at least showing the charging screen right now...
Also bootloader is locked. Just checked with the fastboot.exe
bandoncontortion said:
Ok i just put the stock ftf on it through flashtool. I tried to turn it on and it shows the Sony Ericsson screen and then the Android screen the turns off. Any help? It's at least showing the charging screen right now...
Also bootloader is locked. Just checked with the fastboot.exe
Click to expand...
Click to collapse
That good :good: Not bricked did you wipe data & cache in flashtool when you flashed ftf?
Yes i wiped cache, app log, and data. Im also using an older version of flashtool...maybe upgrading will help? Gonna check
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.
Hi Friends . Recently I Decided To Tinker With My Xperia Play Phone And Now I Can Put It In To flash and fast boot once to try something but then all I get is blinking red light and to be able to do it again I have to pull battery. Ok so here is the dumb thing I did I unlocked bootloader though sony which by the way I can relock if I need to . then I got excited about all the things I could do so I was bouncing between this site , free xperia , and some junk site with bad guides . So Im Reading and jumping around getting a custom rom and reading how to to use flash tools and im reading this vague guide on flashing a custom rom . I flash it and then in the guide it says to boot in recovery but I didn't now it at the time that you need to install a recovery I thought sony had a stock recovery like the boot and flash mode.. so now im stuck in a bootloop. So I got on this website and started digging . most of what I read is that I can save it by flashing stock firm ware with flash tools . everytime I try to flash it when it gets to system.sin I get a blocked verifaction error. Ive tried it with and without final verifaction checked. also ive tried different stock firmwares and on some of the firmwares they are compressed in a .rar file and when extracted it says file corrupt or broken. ive tried all the sony services PC Companion with bootloader locked again and it says no software available if bootloader is unlocked it says my phone has been modified . ive tried there update engine no software available And there flash tool EMMA no services available . Tried wotan I think but the client just keeps closing. So after all the flashing and stuff im where I mentioned in the beginning one flash attempt then red lights pull battery and try again.
I really think if some one knows why im getting the verification block error in flash tools and could give me the stock firmware I need id be set but im at an end and this is my cry for help . please ill try anything if it might work
phone breakdown -Sony Xperia Play R800x The Verizon one It was running GB 2.3.4 bootloader unlocked and not rooted
Thanks in Advance
All roms/kernels/firmwares are at
http://forum.xda-developers.com/showthread.php?t=2184897
Please note that kernel and recovery is in same file (you can't flash them separately). All custom kernels have recovery build in, but not stock kernel. And, important when choosing wich kernel to flash, flash kernel that match rom you are about to install (example, lupus ics/gb is for ics and gb roms, but not for jb roms).
To flash firmware, use flashboot mode in flashtool. Select firmware, and when asked, (phone turned off) hold back button and insert usb cable to xPlay.
To flash kernel, power off, hold search button and insert usb port to xPlay. Choose kernel from flashtool and wait few seconds. Power on and keep pressing back/volume down (depends on kernel), it will enter recovery. Choose "flash zip" in recovery and wait few minutes (again, kernel must match rom you are installing or you'll get "kernel bootloop" (kernel logo shown, then it restart).
Edit: what is your model? R800 x,i,a?
Sent from my R800i using xda app-developers app
solved
Easy Fix Changed usb Cable Flashed no problem
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.