Develop Bugs

[Q] [HELP!] Won't boot after flashing with Flashtool

When I want to turn on my phone, it just won't boot? When I try it, it vibrates and the led flashes ones. Anyone who can help me?
Here's what I did:
I wanted to try out this [THEME] X-Themes [4.0.A.2.368] , I've installed other mod to, so I figured it wouldnt be that hard.
After the last step, Overwriting the original SemcGenericUxpRes.apk and framework-res.apk, I got a bootloop.
So I took my phone and flashed my firmware LT15i_4.0.1.A.0283_(1247-1061), with no user wipe. (Flashtool).
Yey! it worked..
Then I got a mention from SE that there was a new version etc. So I agreed and had to reboot to get 4.0.2.A.0.42 again..
There's where it happenned, It won't boot..
I tried several things;
- Flashing again with Flashtool 4.0.1.A.0283 no wipe
- Flashing again with Flashtool 4.0.1.A.0283 with wipe
- Flashing again with Flashtool 4.0.2.A.0.42 no wipe
- Flashing again with Flashtool 4.0.2.A.0.42 with wipe
But unfortunately, none of these worked..

is you phone unlocked bootloader before 4.0.2.A.0.42?

Looks like your bootloader is unlocked and your phone got bricked after OTA update. Am I right? Take a look and see if it helps:
http://forum.xda-developers.com/showthread.php?t=1126358

Still thanks!
LivingPerson said:
Looks like your bootloader is unlocked and your phone got bricked after OTA update. Am I right? Take a look and see if it helps:
http://forum.xda-developers.com/showthread.php?t=1126358
Click to expand...
Click to collapse
Yep that's true, I also found that post indeed, but I forgot to post it here..
Still thanks!

Arc bricked

I executed the command 'fastboot erase boot' in fastboot when I was not supposed to, while trying to flash .62 FW. After that the phone is unable to startup, at some point the lockscreen would appear for a split second and the phone shuts down. I tried flash mode to the old FW .181 and 184. I also flashed DoomKernel though fastboot and flashed back to kernel from .181. Does someone know what I did wrong and how to fix the phone? Im all hopeless here
I can still go to CWM recovery after flashing doomkernel. I can also flash stock(?) kernel. I have tried back and forth what I mentioned.
I didnt mean to post this on development section, sorry o.o I had too many Xda tabs open from researching.

I've found that. Hopes it will helps
"Developers who are creating new images to try out very often can remove their boot and recovery images which will force the phone to enter bootloader mode every time you boot. To fix this, you would reflash the boot and recovery images back allowing the phone to boot normally."
http://android-dls.com/wiki/index.php?title=Fastboot

this is no brick, i've experienced this before, for easiest way use your ftf files using flashtool to recover it.

Dev thread
Sent from my MT15i using xda premium

Why don't you fastboot a kernel? Then see if it boots
Sent from my MT15i using xda premium

I have tried flashing .ftf (.181/.184) file with flashtool and tried fastboot (doomkernel and kernel from .181).
Right now I have it flashed to .181 with Flashtool and the phone turns on and turns off right when it gets to lockscreen.

Have you tried wotan?
Install the windows software and follow the guidance on your screen.

Does it show 0% battery?
You were on 2.3.4 and flashed 2.3.2 which will cause the 0% battery issue and then the phone turn off by itself.
Sent from my iPad 2 using Tapatalk

Yes the battery shows 0% Ill look into the 0% workaround.

Now Im not sure what Im supposed to do... Phone stays on when charging (not through the pc). How am I supposed to fix 0% battery when Im on .181 or .184? Old FWs.

The only way to get the phone going is to flash back to .184 and apply [ARC/ARC S]DooMKernel for STOCK ROM patched to fix 0% battery. After that when I try to flash prerooted .img 4.0.2.A.0.62 Generic Global (MAA World) it gets stuck on SE logo.
Also the Doomkernel logo only shows up on first reboot right after fastbooting it and next time I turn it on it shows Sony Ericsson.

ST4YSTR0NG said:
I have tried flashing .ftf (.181/.184) file with flashtool and tried fastboot (doomkernel and kernel from .181).
Right now I have it flashed to .181 with Flashtool and the phone turns on and turns off right when it gets to lockscreen.
Click to expand...
Click to collapse
Downgrading your firmware to .181 corrupted the fuel gauge. Now you have the 0% battery issue.

Here's all you need:
http://forum.xda-developers.com/showthread.php?t=1312398
Sent from my iPad 2 using Tapatalk

Thanks guys, Ill try Bazoocaze's guide thoroughly. And Im gonna try it staying on .181 or get the .283.
And then what should I do after the battery indicator has fixed? Will it be ok to flash .62 directly from .181 or .283?
Edit: Forget what I said above, Im gonna try .62 first with Bazoocaze's .62 boot.img but Im wondering if that will work with prerooted .img 4.0.2.A.0.62 Generic Global (MAA World).

Ok thank you so much guys and sorry for my chaotic posts lol. I am now on .42 and recharging battery with FuelGaugeFix.
Is it now safe to follow the instructions from Arconium and boot Doomkernel?
Edit: The phone was running fine and I rebooted it and a big surprise it shows 0% battery and shuts down.
Edit: Oh my... I have such a never ending stupidity. All this time I have been using the command 'fastboot boot boot.img' for kernel. I just realized that its 'fastboot flash boot boot.img'
I apologize for bugging who I may have bugged.

Any ideas about beeing possible to have 0% battery problem if bootloader unlocked?? Cause I downgraded once and my arc didn't notice, it's alright. But I would be more careful in future regarding this.
@ST4YSTRONG do you have unlocked bootloader?

Locked Arcs ran into this problem, too.
Sent from my iPad 2 using Tapatalk

Flo95 said:
Locked Arcs ran into this problem, too.
Sent from my iPad 2 using Tapatalk
Click to expand...
Click to collapse
I suppose you wanted to say UNlocked? Cause that locked has this problem is what I've read somewhere...damn, then I dunno why it happened to me last week that I downgraded from .62 to .58 Lucky of me!!
Thanks!

Very Arc ran into this problem from what I've read.
Looked or unlocked bootloader.
Glad I unlocked my bl before and could easily root 2.3.4 with DooMKernel instead of messing around with downgrading and Gingerbreak etc.
Sent from my iPad 2 using Tapatalk

xexijreil said:
Any ideas about beeing possible to have 0% battery problem if bootloader unlocked?? Cause I downgraded once and my arc didn't notice, it's alright. But I would be more careful in future regarding this.
@ST4YSTRONG do you have unlocked bootloader?
Click to expand...
Click to collapse
Yes I unlocked my bootloader recently when I was downgrading from 2.3.4 to 2.3.2 (I know thats stupid and gives u 0% battery problem) and that was necessary since here the more we download the more we pay. I had bootloop issue while trying to change framework.res.
I did get 0% battery problem before unlocking bl as well, unless Im mistaken and that didnt leave my Arc impaired.
Its when u downgrade to 2.3.2 or more, u get 0% battery problem.

[Q] Another bricked play

i have been trying to fix my play for two days now and have tried everything i can think of
i have a R800i, on 62. firmware, i have tried flashing the stock FTF firmware, tried flashing the "TA brick fix uppdate" tried using wotan client too but no joy
i can still use flashtool and can still enter fastboot but when i turn on my play it just vibrates for a second and then nothing

Get Sony Ericsson Update Service and use that to repair the software; it always works for me no matter what - it can take around 20 retries though -_-... Try removing the battery for 30 seconds after around 10 retries - I have no idea why this helps but it has in the past...

im getting "phone contains modified software that cannot be updated"
is this normal or am i still fuked?

any other suggestions would be greatly appreciated, as it is right now i cant even return it to sony because they will no straight away that i modified the firmware

silvacrest said:
any other suggestions would be greatly appreciated, as it is right now i cant even return it to sony because they will no straight away that i modified the firmware
Click to expand...
Click to collapse
Flash it back to stock using Wotanserver then try SEUS.
Sent from my R800x using Tapatalk

paxChristos said:
Flash it back to stock using Wotanserver then try SEUS.
Sent from my R800x using Tapatalk
Click to expand...
Click to collapse
something is not right, i installed stock using wotanclient, then i tried using SEUS but i still get "the phone contains modified firmware"
im getting no errors using flashtool or wotanclient but apparently the firmware is not being flashed

i had the same problem when i bricked my play all i did was flash generic stock rom on it and took out the sd card and have no problemhttp://www.xperiagamer.com/Stock-Roms/233-se-stock-firmware-for-root.html

sportstj11 said:
i had the same problem when i bricked my play all i did was flash generic stock rom on it and took out the sd card and have no problemhttp://www.xperiagamer.com/Stock-Roms/233-se-stock-firmware-for-root.html
Click to expand...
Click to collapse
tried it, still didnt work, is there a recovery method using fastboot that i could try? im unsure whether flashtool is actually working....

i managed to relock the bootloader which meant SEUS finally allowed me to install the firmware which was successful but the screen is still completely black, tried flashtool and wotanclient afterwards, both installed successfully but the screen is still black, i think the phone is working but the screen it self has died somehow
i was wondering, since the bootloader is relocked and the official stock firmware has been installed, should sony accept the faulty play without issue?

its possible if u run the update service and if it says phone is up to date one would think so ... i would ask a question and see what others say im still new to this site but yet i have learned alot make sure u update ur flashing tool too and make sure its properly flashed and when flashing is completed it should say flash complete.

[Q] R800x won't boot or show splash screen after unlocking

So maybe I'm not as good at this as I thought, but I unlocked my bootloader through the sony website a few days ago. The phone was working fine with 2.3.4 (from verizon). I tried to revert back to 2.3.3 with the (verizon) .ftf file. After flashing it with flashtool, my phone won't boot at all. There is no splash screen and holding down the power button makes it vibrate every 2 seconds. I am still able to reflash the 2.3.3 ftf, but after it completes its the same story. And of course using seus or PC companion says I have modified software and tells me to kick rocks. Perhaps someone smarter than me can help?

Well I'm confused already. The R800x bootloader cannot be unlocked via Sony's method.

Correct. And my play only has done the vibrete every two seconds because it over heated....so I doubt you have unlocked your bootloader and so after flashing 2.3.3 you bricked probably cuz the file you have is mislabled
Sent from my GBTweaked V7.1 R800x using Tapatalk 2

I should have been more specific. I unlocked the bootloader with flashtool's plugin. I acquired the unlock code from the sony website.
I still have the ability to connect in flash mode, but I guess an overheat is possible...
Again, my knowledge is probably more limited than it should be, but is there a way for me to re-flash the coding the bootloader contained?

drdarkwing said:
I should have been more specific. I unlocked the bootloader with flashtool's plugin. I acquired the unlock code from the sony website.
I still have the ability to connect in flash mode, but I guess an overheat is possible...
Again, my knowledge is probably more limited than it should be, but is there a way for me to re-flash the coding the bootloader contained?
Click to expand...
Click to collapse
You damaged its trim area repair that using a patch.....
Sent from my R800i using xda premium
---------- Post added at 04:46 PM ---------- Previous post was at 04:43 PM ----------
http://forum.xda-developers.com/showthread.php?t=1126354 if it doesn't help relock ita bl then flash ftf it'll work
Sent from my R800i using xda premium

Thanks all around! the download link was broken for the first option, so I ended up relocking it and flashing the firmware again. unbricked and back to 2.3.3!
Thanks again guys!
Onward and Upward

Same Issue. Please help.
I now seem to be in the same situation. I unlocked my R800x via the official Sony method about two weeks ago and all was well. I've flashed custom kernels and ROMs and flashed the 2.3.3 ftf countless times. Today I decided to flash the ftf and run stock for a while as my battery life has become crap. It flashed no problem just as it always does, I activated the phone then stuck it in my pocket and went on with life. An hour or so later I take it out and push Home to wake it, but nothing happens. My first reaction is to pull the battery then turn it back on since that usually does the trick, but it vibrates as it normally does but nothing happens. So I flash the ftf again and still the same, I press Power and it vibrates but nothing, the screen just remains black. Since then I've trolled the forums and tried everything I could think of and everything that anyone suggested, but nothing has worked. I haven't tried relocking the bootloader, then flashing the ftf again because I can't seem to find any instructions on how to do it. If anyone can point me in the right direction, I would be more than willing to try it. Any help at all would be greatly appreciated as I am totally lost at this point.I never imagined there would be a day that one of my precious androids wouldn't emerge from a stock firmware flash good as new.
EDIT: I flashed the Xperia BL Relock ftf in this tread then flashed the Verizon 2.3.3 ftf again and it worked! My PLAY has risen from the ashes once again.

Morbyd.X said:
I now seem to be in the same situation. I unlocked my R800x via the official Sony method about two weeks ago and all was well. I've flashed custom kernels and ROMs and flashed the 2.3.3 ftf countless times. Today I decided to flash the ftf and run stock for a while as my battery life has become crap. It flashed no problem just as it always does, I activated the phone then stuck it in my pocket and went on with life. An hour or so later I take it out and push Home to wake it, but nothing happens. My first reaction is to pull the battery then turn it back on since that usually does the trick, but it vibrates as it normally does but nothing happens. So I flash the ftf again and still the same, I press Power and it vibrates but nothing, the screen just remains black. Since then I've trolled the forums and tried everything I could think of and everything that anyone suggested, but nothing has worked. I haven't tried relocking the bootloader, then flashing the ftf again because I can't seem to find any instructions on how to do it. If anyone can point me in the right direction, I would be more than willing to try it. Any help at all would be greatly appreciated as I am totally lost at this point.I never imagined there would be a day that one of my precious androids wouldn't emerge from a stock firmware flash good as new.
EDIT: I flashed the Xperia BL Relock ftf in this tread then flashed the Verizon 2.3.3 ftf again and it worked! My PLAY has risen from the ashes once again.
Click to expand...
Click to collapse
Buddy all that could've been fixed with a battery recalibration app. :silly:

Probably so, but wasn't that soo much more interesting? Lol.

I broke it

Update: The guys at Razer are just about as clueless as a retail phone carrier. They told me to do the exact same thing, the factory reset and all that, but they don't know what they're doing.
So FYI: IF YOU'RE BOOTLOADER IS LOCKED AND YOUR OS WON'T START, YOU'RE SCREWED.
Okay so I rooted the phone on Oreo, the second to last update, and tried to update it to the May update, and the update kept failing inside the system update app. So, I tried installing it by flashing it from a computer. Unsuccessfully. So, I booted into TWRP and installed every image manually through TWRP. Bootlooped it. Soooooo I tried to flash the latest stock image from the computer, and it goes through, but the phone refuses to turn on. And I can't even unlock the bootloader because in the command prompt it says it's not allowed. So I'm stuck with a paperweight that won't unlock any bootloaders and won't even boot into the OS. I think I royally screwed it up and I desperately just wanna use the phone again.
I've tried everything. My drivers are correct, and It just won't cooperate with me no matter what I do to it. It'll either keep booting into download mode or get stuck on the splash screen forever.
I'm literally desperate at this point. I can't do anything with this thing!!! I can't flash anything because it's locked and the phone won't boot into the OS for me to even unlock it.

How did you get twrp with a locked bootloader? :S is that a thing now?
You cant flash the factory images without an unlocked bootloader. So if you didn't check the OEM unlock allowed setting you won't be able to unlock it so won't be able to flash the firmware.
Honestly i think you're out of luck if you can't unlock your bootloader.

Wait how did your bootloader relock itaelf? Because that can happen only with the lock/lock_critical command.
---------- Post added at 02:07 PM ---------- Previous post was at 02:03 PM ----------
Dashaquavius said:
Okay so I rooted the phone on Oreo, the second to last update, sand tried to update it to the May update, and the update kept failing inside the system update app. So, I tried installing it by flashing it from a computer. Unsuccessfully. So, I booted into TWRP and installed every image manually through TWRP. Bootlooped it. Soooooo I tried to flash the latest stock image from the computer, and it goes through, but the phone refuses to turn on. And I can't even unlock the the bootloader because in the command prompt it says it's not allowed. So I'm stuck with a paperweight that won't unlock any bootloaders and won't even boot into the OS. I think I royally screwed it up and I desperately just wanna use the phone again..
I've tried everything. My drivers are correct, and It just won't cooperate with me no matter what I do to it. It'll either keep booting into download mode or get stuck on the splash screen forever.
I'm literally desperate at this point. I can't do anything with this thing!!! I can't flash anything because it's locked and the phone won't boot into the OS for me to even unlock it..
Click to expand...
Click to collapse
Did you say the factory images fully flash with no errors? Both "fastboot flashing unlock/unlock_critical" don't work?

You should try the flash_all.bat or flash_all.sh script from the latest images. If you want to keep your data just comment or erase the line with the "fastboot erase userdata" in the flash_all.
Be sure to have fastboot in your path

Roxas598 said:
How did you get twrp with a locked bootloader? :S is that a thing now?
You cant flash the factory images without an unlocked bootloader. So if you didn't check the OEM unlock allowed setting you won't be able to unlock it so won't be able to flash the firmware.
Honestly i think you're out of luck if you can't unlock your bootloader
Click to expand...
Click to collapse
iliais347 said:
Wait how did your bootloader relock itaelf? Because that can happen only with the lock/lock_critical command.
Did you say the factory images fully flash with no errors? Both "fastboot flashing unlock/unlock_critical" don't work?
Click to expand...
Click to collapse
waiflih said:
You should try the flash_all.bat or flash_all.sh script from the latest images. If you want to keep your data just comment or erase the line with the "fastboot erase userdata" in the flash_all.
Be sure to have fastboot in your path
Click to expand...
Click to collapse
1. I didn't flash TWRP with the bootloader in the locked state, it was while it was unlocked.
2. Out of desperation, after flashing the stock images multiple times (while it says errors and maximum download reached and stuff) I re-locked the bootloader with the command thinking it would finally at least boot into the OS, to no avail.
3. Factory images didn't flash without some kind of error.
4. I'm unable to run any kind of commands, it says it's not allowed.
5. I've flashed multiple times, flashed the previous updates and the latest updates, and there's always some kind of error or it's not allowed.
I'm just gonna contact Razer. Apparently, I can't flash anything if the bootloader is locked? And the phone won't even boot into the OS to let me tick the option? I think I'm screwed.

For what you are telling you may have an outdated fastboot version. Can you try flash_all and post the error messages? kinda difficult to help without that

waiflih said:
For what you are telling you may have an outdated fastboot version. Can you try flash_all and post the error messages? kinda difficult to help without that
Click to expand...
Click to collapse
It says flashing is not allowed for everything.

Ok that is indeed strange. Take a look at this https://insider.razer.com/index.php...afe-method-warning-rebuilds-partitions.23532/
its for the robin but since you already tried everything else you can give it a shot

waiflih said:
Ok that is indeed strange. Take a look at this https://insider.razer.com/index.php...afe-method-warning-rebuilds-partitions.23532/
its for the robin but since you already tried everything else you can give it a shot
Click to expand...
Click to collapse
I just got off with Razer support, they're just gonna send me a new one.
And apparently, absolutely NO OTG support!
Let this thread serve as a warning..

how did you manage to get razer to agree a replacement??.i had a speaker issue and had to send a video of my problem then a week later they finally agreed to replace it.you have done really well for them to accept phone back for replacemnet..as for relocking bootloader as far as i read the other day once you do this phone is bricked

parky169 said:
how did you manage to get razer to agree a replacement??.i had a speaker issue and had to send a video of my problem then a week later they finally agreed to replace it.you have done really well for them to accept phone back for replacemnet..as for relocking bootloader as far as i read the other day once you do this phone is bricked
Click to expand...
Click to collapse
Interesting. I sent 2 phones with speaker issues and they offered a replacement for both and gave me shipping labela.