Related
I was running rooted 2.3.3 on my r800x. I had a problem and re-unlocked my bootloader and flashed stock. The OTA began and I forgot to relock the bootloader. I flashed the fix and it started back up, but I can no longer boot fastboot. I hold down the search key and plug in the usb. Blue light doesn't light and phone boots normally. Any advice
try SEUS?PC Companion? atleast the good thing is it boots normally. my r800i won't boot. I have fastboot and download mode. I get exclamation mark after flashing the latest build or get so many FC when it boots. weird
goodluck matey!
Yeah, I tried SEUS and I've flashed just about every ftf I can think of. All of them will flash but none will fix fastboot. It just sucks because I lost root and can't get it back.
paulbearry said:
Yeah, I tried SEUS and I've flashed just about every ftf I can think of. All of them will flash but none will fix fastboot. It just sucks because I lost root and can't get it back.
Click to expand...
Click to collapse
You could try to root with zergRush. Look for a thread in the dev section that goes something like this:
how to root R800x with zergRush
Regards Dousan...
alright, I'm going to try this now
Your bootloader probably got locked when restoring from a brick or all the flashing ftf files with flashtool. Think i read somewhere that the bootloader get's locked on your model when flashing with flashtool (might be mistaken). Even seems like you've been locked out of fastboot all together?
Anyway sounds like it needs to be unlocked and done with the method @Alejandrissimo uses.
Regards Dousan...
Thanks man! zergRush totally worked. I'm back to root! You're awesome.
and yes, I'm completely locked out of fastboot. Can't figure out why, but for now I'm satisfied with just having root back. Although I would love to know why I can't boot into fastboot.
Hi all.
On Saturday night my Arc (debranded Rogers, locked BL, rooted with zergrush, running 2.3.4 on firmware .42) was running just fine. We were out at a friend's place and I was calling up photos, doing Web searches, no problem. Then yesterday when I turned the beast on it went into in a bootloop - SE logo, blank screen, SE logo, blank screen ...
I managed to boot into CWM to be able to turn it off, but that was as far as I got (and after a wasted afternoon trying to reflash I can't even get to CWM now).
PCC/SEUS are no help at all - after going through the 'Repair phone' process PCC says there's 'no software available for your phone yet'. I've tried reflashing generic f/ware with both Wotanserver and Flashtool 0.6.8.0; with Flashtool I get the same "Final data verification failed" error as reported recently here with an X10 after 99% complete. And this message from the bottom of the log makes me suspicious Flashtool wants me to change mode, which is just a little tricky when I can't start the phone:
INFO - For 2011 devices line, be sure you are not in MTP mode
Current status is the phone boots to the SE logo, then displays an image of an exclamation mark over a phone - one of the least informative images I've seen, unless it represents a tombstone, which seems very possible! - then dies again.
I've looked at a couple of other XDA threads about bricks; the most promising-sounding one was talking about unlocked bootloaders, though, so I didn't try to flash the file they were talking about.
I might feel slightly better if I'd done something - anything! - like an OTA update or whatever to cause this, but all I did was turn the thing off for the night, as I always do.
Please, somebody: help!!
Thanks, in great anticipation.
Didcha tr y reflashing rom or kernel? Also factory reset might help.
Sent from LT18i @ Xda Premium
Thanks, ArmorD.
Just ROM - I can't do anything with the kernel with a locked bootloader, can I?
I'd try a factory reset if I could get into CWM, but I can't. I tried the reset method from here, but the phone still just goes to the SE logo, then the 'tombstone'.
Open to pretty much anything at this stage!
Well, what you can do is i think re-flash it with Update service, it might work than.
Here is the link to update service since you wont find it in SE website.
http://www.mediafire.com/?mkk2w0os8ak1dzf
:S Nvm. You already have tried update service. didn't saw it when i read it first..
Bro, just reflash the system
I have just ended up with a boot loop on my arc.. I reflashed and it worked well!
-cheers
untouchable123 said:
... I reflashed and it worked well! ...
Click to expand...
Click to collapse
So did I, and it didn't! But thanks anyway.
Further news: trying to eliminate possible causes, I've had the SD card checked (by inserting it in another device). It's quite readable. I didn't really think this problem would have anything to do with the card, but it seemed worth trying.
Well, idk. Sorry bro! Try to flash stock firmware with flashtool! And it might work! Also bricked=phone is not turning on at all! Like u press the power button and nothing is happening. Cheer up man u finally gonna fix it. ;-)
Sent from my LT18i using XDA
i have encounter tha triangle with ! inside and a phone beside it, it happens when i tried flashing my phone using wotanserver,i want to root my phone and tried to downgrade to .42 taiwan ftf,but the file in wotanserver is maybe damage and did not finish flashing,then i got that "tombstone" icon.
what i did was flash it with uk tft .42,and it restored my arc s,after that i flash it again with .62 taiwan ftf since i live in taiwan, i dont know if this will work on your phone. or maybe you already tried doing it. i just want to share what i happen to encounter. hope you fix your phone.
Untouchable: thanks - I wish I shared your faith!
asderth8000: thanks also. I tried a different firmware version tonight (US generic; previously World; also tried Australian) but same result - Wotan dies with 'ERROR: File write failed' while writing userdata.s08. It feels like that's close to the end of the process, which suggests Wotan and Flashtool are both getting hung up at the same place. Screenshot of Wotan error atatched - hope it gives somebody some ideas.
I appreciate your help, people. Keep them thoughts coming!
lol bro stop using Wotan use Flashtool!!!!!!! lol my faith is beyond the limit. I have bricked & ubricked my cell a couple of times;-)
Sent from my LT18i using XDA
I got that same error using .42 Taiwan ftf, maybe try UK, it works fine with me although I don't live in UK.
I remember mine was on userdata.07 when an error occured,I thought at first that it was my connection then I tried doing it again and it failed, then I tried the UK version and it goes well. Save your apn settings too.
Anicane said:
Well, what you can do is i think re-flash it with Update service, it might work than.
Here is the link to update service since you wont find it in SE website.
http://www.mediafire.com/?mkk2w0os8ak1dzf
:S Nvm. You already have tried update service. didn't saw it when i read it first..
Click to expand...
Click to collapse
Update service is available again for some time!
http://www.sonymobile.com/gb/tools/update-service/
---------- Post added at 05:15 PM ---------- Previous post was at 05:13 PM ----------
This package has saved me before, even for things it isn't meant for. Worth trying, won't do any more damage I think.
http://forum.xda-developers.com/showpost.php?p=14774499&postcount=1
It's BAAAACK!
First, and most importantly: I have a phone again.
The eventual answer was this thread, suggested by sdk16420. I hadn't tried it before because it was talking about unlocked bootloaders, but I fired it up this morning and ... guess what? I've spent most of the day restoring things, but I'm pretty much there - even rooted again (lost that along the way). The phone says there's an OTA update for .62 ready, but that failed and PCC doesn't believe it exists. Ah well, there's always something ...
Secondly: huge thanks to the XDA community for your support and suggestions. You guys are OK!
Loosely said:
First, and most importantly: I have a phone again.
The eventual answer was this thread, suggested by sdk16420. I hadn't tried it before because it was talking about unlocked bootloaders, but I fired it up this morning and ... guess what? I've spent most of the day restoring things, but I'm pretty much there - even rooted again (lost that along the way). The phone says there's an OTA update for .62 ready, but that failed and PCC doesn't believe it exists. Ah well, there's always something ...
Secondly: huge thanks to the XDA community for your support and suggestions. You guys are OK!
Click to expand...
Click to collapse
No prob bro;-) ask anything u want and we will try to help;-)
Sent from my LT18i using XDA
PLEASE HELP - Potentially bricked LT18i
slightly different similar problem:
LT18i, 2.3.4 build .62.. or it was!
Wares used: SE Bootloader Lock/Unlocker, Flashtool
Flashtool really should come with a lot more documentation and user guide: I'm a software person, but C++ is my confortable realm!
Managed to flash CWM on there and got it stuck in a bootloop of CWM (trying to install RootXperia.zip): tried many other images, the best I can get is a Sony Ericsson Logo looping.. I guess my SD card is okay.
Can't find an up to date, stock, 2.3.4 build .62 to repair my phone..
Help! A Walkthrough of my problem helps me rinse my degree and this equates to thanks and donations, I am a desperate man right now!
Please hassle me for info, help me help you help me!!
My Arc is Crying too!
PS that r800i ROM didn't work for me!
WHAT I NEED FROM YOU LOVELY PEOPLES:
-A link to the stock ROM or LT18i .62
-noobproof couple of steps to explain flashtool 0.6.8.0
-noobproof steps of how to flash the stock ROM/Kernel back in place
Hope you can help me.. my first flash went entirely squiffy!
Thanks in advance!
Omg plz ignore my noob self, except massive props to doomlord.
Sent from my LT18i using XDA
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.
Recently, Xperia Acro S was been removed from the Unlocking Bootloader list on the Official Sony site.
As maintaining a thread on Acro S section, some of my friends were unable to unlock their bootloader due to missing device in the list.
So, I Emailed Sony few weeks ago requesting them to re-list Acro S, and they said, they'll look at this. Now its been Re-listed.
I have even attached three screenshots for your conformation. So see it, Just check out below three links,
SS-01 || SS-02 || SS-03
For those who were waiting to unlock their phone, here's a good news for you all. Go ahead and get the unlock code from official Sony site providing them your IMEI.
1. To Get Unlock Code just click HERE!
2. Unlocking Bootloader step-by-step Guide, just click HERE!
Regards,
hitman-xda
As I said, I'll notify you after Acro S is re-listed, I'll mention you here; @bluvn || @sky202_how89 || @els_sand
Wow, Thanks for the surprise! U make my days!
sky202_how89 said:
Wow, Thanks for the surprise! U make my days!
Click to expand...
Click to collapse
That sounds good
Hey but too bad is I totally brick my phone. Almost all of the solution found by google seems no used.
Out of surprise, it happened for most of the Xperia Phones who are heavy flashing with custom ROM.
Check out the thread here: http://forum.xda-developers.com/xperia-s/help/xperia-acro-s-sim-card-service-detect-t3200650
Now my XAS is becoming a powerful MP4 Player. What a desperate. ;( ;(
sky202_how89 said:
Hey but too bad is I totally brick my phone. Almost all of the solution found by google seems no used.
Out of surprise, it happened for most of the Xperia Phones who are heavy flashing with custom ROM.
Check out the thread here: http://forum.xda-developers.com/xperia-s/help/xperia-acro-s-sim-card-service-detect-t3200650
Now my XAS is becoming a powerful MP4 Player. What a desperate. ;( ;(
Click to expand...
Click to collapse
Did you checked weather your Bootloader is unlocked? If not then check it.
Also try to repair your phone through PC companion.
Its a strange problem. Hearing it first time.
Did you followed exact procedure of the Guide that I linked?
I don't think it occurs due to heavy flashing of ROMs, because I have used every ROM available for the phone for almost 100 times. I usually change my ROM after a month.
hitman-xda said:
Did you checked weather your Bootloader is unlocked? If not then check it.
Also try to repair your phone through PC companion.
Its a strange problem. Hearing it first time.
Did you followed exact procedure of the Guide that I linked?
I don't think it occurs due to heavy flashing of ROMs, because I have used every ROM available for the phone for almost 100 times. I usually change my ROM after a month.
Click to expand...
Click to collapse
The problem occurred when the user try to flash back to stock ROM from Custom ROM.
The Bootloader is unlocked.
Now the BL appear to be like this: Bootloader Unlock Allowed = No (*#*#7378423#*#*)
Enter fastboot fail (No fastboot detected), Only Flash is allowed.
To install CWM or TWRP required fastboot, so I can't do anything besides keep trying to flash wiith different version of stock FTF.
Solution I tried but failed:
- Fix using Sony PC Companion (PCC)
- Flash any version of stock ROM, inclusive of just flashed the "Baseband" only.
- Flash Acro-HD S0-03D ROM then flash back to stock ROM.
- *#*#4636#*#* -> Phone information -> Set preferred network type (any of the option & reboot)
- Settings -> More -> Mobile Networks -> Network Mode(any option & reboot)
- Settings -> More -> Mobile Networks -> Select providers (automatic or manual), it manage to detects the service providers but registered on the network failed.
- Insert other active SIM Card
I try to locate the Antenna Board but it seems like it was attached with the mainboard. Unlike Xperia Z, the Antenna Board is seperated.
I assume this problem occurred when the partition accidentally bricked by Flashtool? I did try to flash different version of Baseband, nothing seems work.
I need someone favors. Create a Pre-rooted Stock ROM(.ftf) with Recovery Accessed (CWM or TWRP).
I found somewhere from this forum stated that tried to install back any of the Custom ROM to fix the No Signal Issue which it appeared to be my last hope. Without Recovery(Required Fastboot to install), I couldn't install any custom ROM.
sky202_how89 said:
The problem occurred when the user try to flash back to stock ROM from Custom ROM.
The Bootloader is unlocked.
Now the BL appear to be like this: Bootloader Unlock Allowed = No (*#*#7378423#*#*)
Enter fastboot fail (No fastboot detected), Only Flash is allowed.
To install CWM or TWRP required fastboot, so I can't do anything besides keep trying to flash wiith different version of stock FTF.
Solution I tried but failed:
- Fix using Sony PC Companion (PCC)
- Flash any version of stock ROM, inclusive of just flashed the "Baseband" only.
- Flash Acro-HD S0-03D ROM then flash back to stock ROM.
- *#*#4636#*#* -> Phone information -> Set preferred network type (any of the option & reboot)
- Settings -> More -> Mobile Networks -> Network Mode(any option & reboot)
- Settings -> More -> Mobile Networks -> Select providers (automatic or manual), it manage to detects the service providers but registered on the network failed.
- Insert other active SIM Card
I try to locate the Antenna Board but it seems like it was attached with the mainboard. Unlike Xperia Z, the Antenna Board is seperated.
I assume this problem occurred when the partition accidentally bricked by Flashtool? I did try to flash different version of Baseband, nothing seems work.
I need someone favors. Create a Pre-rooted Stock ROM(.ftf) with Recovery Accessed (CWM or TWRP).
I found somewhere from this forum stated that tried to install back any of the Custom ROM to fix the No Signal Issue which it appeared to be my last hope. Without Recovery(Required Fastboot to install), I couldn't install any custom ROM.
Click to expand...
Click to collapse
First of all let me clear that 'Unlocking Bootloader Allowed = No'
That means you cannot unlock it unless your coming to stock from other ROM.
Also Bootloader can be unlocked only once. So if your coming back to stock from custom, why did you tried to unlock your BL again?
Even if you flash stock ftf, you no need to unlock your BL again.
Secondly, don't try to flash other ROMs into your phone, you could mess up everything, even hard brick.
Your Fastboot mode isn't working, right? If so, then try to install fastboot drivers from flashtool driver pack. Maybe it could work.
hitman-xda said:
First of all let me clear that 'Unlocking Bootloader Allowed = No'
That means you cannot unlock it unless your coming to stock from other ROM.
Also Bootloader can be unlocked only once. So if your coming back to stock from custom, why did you tried to unlock your BL again?
Even if you flash stock ftf, you no need to unlock your BL again.
Click to expand...
Click to collapse
I did not lock my BL, it just lock back by themselves. I still remember I unlock my BL with Sony Official way in 2013. After that, I did not touch that BL again. It's just after the recent flash which I did the same way like before(Custom to stock ROM), everything mess up.
Secondly, don't try to flash other ROMs into your phone, you could mess up everything, even hard brick.
Your Fastboot mode isn't working, right? If so, then try to install fastboot drivers from flashtool driver pack. Maybe it could work.
Click to expand...
Click to collapse
I even format my pc which I thought it was my pc issue earlier. But ends up I realize it was something regarding to my BL. With BL Unlock Allowed: No, you cannot enter to your bootloader or fastboot.
This video is showing exactly my problem now:
Other thread that I discovered with same issue as I am:
http://forum.xda-developers.com/showthread.php?t=2432566
http://forum.xda-developers.com/xperia-z/help/xperia-z-signal-drops-unable-to-connect-t2183045
My very last but not recommended solution is to change the motherboard. However, looking at the posting not only me having the issue and it mostly happened when users are flashing back from Custom ROMS to Stock ROMS.
Changing motherboard is like changing another phone, your feeling towards the phone changed.
sky202_how89 said:
I did not lock my BL, it just lock back by themselves. I still remember I unlock my BL with Sony Official way in 2013. After that, I did not touch that BL again. It's just after the recent flash which I did the same way like before(Custom to stock ROM), everything mess up.
I even format my pc which I thought it was my pc issue earlier. But ends up I realize it was something regarding to my BL. With BL Unlock Allowed: No, you cannot enter to your bootloader or fastboot.
This video is showing exactly my problem now:
Other thread that I discovered with same issue as I am:
http://forum.xda-developers.com/showthread.php?t=2432566
http://forum.xda-developers.com/xperia-z/help/xperia-z-signal-drops-unable-to-connect-t2183045
My very last but not recommended solution is to change the motherboard. However, looking at the posting not only me having the issue and it mostly happened when users are flashing back from Custom ROMS to Stock ROMS.
Changing motherboard is like changing another phone, your feeling towards the phone changed.
Click to expand...
Click to collapse
After flashing stock ftf, the BL status always shows 'Bootloader Unlock Allowed = No' but it is actually unlocked. So it does not get relock after flashing stock ftf.
It seems like a serious problem.
Maybe, flashing other ROM will help you a bit. For that Obviously your phone must enter into fastboot mode (which is not happening). In this case did you use 'dd' command for installing recovery? If not then you could try it. And I think you'll be succeeded to install recovery and further you can flash ROM.zip through recovery.
You just need to copy recovery.img into your internal memory and enter some command's using adb shell.
sky202_how89 said:
I did not lock my BL, it just lock back by themselves. I still remember I unlock my BL with Sony Official way in 2013. After that, I did not touch that BL again. It's just after the recent flash which I did the same way like before(Custom to stock ROM), everything mess up.
I even format my pc which I thought it was my pc issue earlier. But ends up I realize it was something regarding to my BL. With BL Unlock Allowed: No, you cannot enter to your bootloader or fastboot.
This video is showing exactly my problem now:
Other thread that I discovered with same issue as I am:
http://forum.xda-developers.com/showthread.php?t=2432566
http://forum.xda-developers.com/xperia-z/help/xperia-z-signal-drops-unable-to-connect-t2183045
My very last but not recommended solution is to change the motherboard. However, looking at the posting not only me having the issue and it mostly happened when users are flashing back from Custom ROMS to Stock ROMS.
Changing motherboard is like changing another phone, your feeling towards the phone changed.
Click to expand...
Click to collapse
You must have used a newer version of flashtool. This is causing similar issues for many people. The only solution for now seems going to Sony service center. There is another method too, flashing the TA backup, but I don''t know if it works or not.
hitman-xda said:
After flashing stock ftf, the BL status always shows 'Bootloader Unlock Allowed = No' but it is actually unlocked. So it does not get relock after flashing stock ftf.
It seems like a serious problem.
Maybe, flashing other ROM will help you a bit. For that Obviously your phone must enter into fastboot mode (which is not happening). In this case did you use 'dd' command for installing recovery? If not then you could try it. And I think you'll be succeeded to install recovery and further you can flash ROM.zip through recovery.
You just need to copy recovery.img into your internal memory and enter some command's using adb shell.
Click to expand...
Click to collapse
I will try & let you know soonest. Kinda busy this few days.
---------- Post added at 05:35 PM ---------- Previous post was at 05:32 PM ----------
Mirhawk said:
You must have used a newer version of flashtool. This is causing similar issues for many people. The only solution for now seems going to Sony service center. There is another method too, flashing the TA backup, but I don''t know if it works or not.
Click to expand...
Click to collapse
YES, I am flashing with NEWEST VERSION of Flashtool. After that, the result turned nagative.
Do you mean TA Partition? Do you have a backup copy of it?
---------- Post added at 05:41 PM ---------- Previous post was at 05:35 PM ----------
Latest UPDATE about the issue, PLEASE TAKE NOTE BECAUSE YOU'RE ABOUT TO BRICK YOUR PHONE JUST LIKE ME. THIS IS IMPORTANT!
@hitman-xda , Please pass this message around. Btw, How to quote the name?
If everyone here in this post flashed their phones with Flashtool 0.9.19.x version, then congrats my friends, we're all become owners of bricked phones with no network signal. Flashtool 0.9.19.x versions have sript error which replaces original Ta partition leading to unlocked bootloader to become locked and loss of network signal. If you're guys haven't backuped your Ta partition prior to bootloader unlocking then that's all.
Check here http://forum.xda-developers.com/show...68&postcount=4 and here http://forum.xda-developers.com/show...postcount=2758
Click to expand...
Click to collapse
http://forum.xda-developers.com/xpe...ice-detect-t3200650/post62904161#post62904161
sky202_how89 said:
YES, I am flashing with NEWEST VERSION of Flashtool. After that, the result turned nagative.
Do you mean TA Partition? Do you have a backup copy of it?
Click to expand...
Click to collapse
Flashing with latest flashtool flashes a partition which renders modem of the phone useless. Yes, I mean the TA partition. Each phone's TA partition is unique, so if You flash mine or other person's TA partition, Your phone would not even boot.
This is toooooooooooooooooooooooooooo OVER! It means my phone is bricked forever.
It's their mistake but we have to bear it on our owns.
sky202_how89 said:
This is toooooooooooooooooooooooooooo OVER! It means my phone is bricked forever.
It's their mistake but we have to bear it on our owns.
Click to expand...
Click to collapse
Did nothing worked?
hitman-xda said:
Did nothing worked?
Click to expand...
Click to collapse
Yes, nothing worked because Flashtool just accidentally bricked our Sony in the whole world. A careless mistake destroy the phone.
In 0.9.18.X, simlock.ta is always excluded by default but a careless mistake on the version 0.9.19.(1234) (at that time), The Simlock.ta is included while flashing. Each phone TA has their own unique number. Besides changing the mianboard (the only solution right now), no ones manage to solve this issue.
I wonder how many Sony phone in the world has already been bricked by this Flashtool update.
Androxyde said:
On 0.9.18.X, even if simlock is included, it is excluded from flashing
On 0.9.19.5 I did this way :
- simlock is excluded by default with a warning when including it (unticking button)
- When simlock is included, when flashing, a YES/NO box appears asking if you are absolutely sure you want to flash this unit.
- When creating bundles, simlock can be included (no risk with 0.9.18 as it is always ignored)
So if you have a TA backup, with 0.9.19.5 you can restore the 07DA unit (then reactivating the phone). Thing you cannot do with any previous release as 07DA unit is hardcoded_excluded.
I will publish another patch that will backup any TA unit that is about to be flashed. That way there will always be a solution to come back to the previous state.
simlock, if present, is always ignored in 0.9.18 release
simlock, if present is excluded by default with the ability to include it with a warning and a user query before flashing the unit
people who had issues are ones using ftf bundles created prior to 0.9.18 with simlock included. Never had issues on 0.9.18 as it is excluded by default, I forget to keep this exclusion on 0.9.19.[1234] and added a defautl exclusion on .5 with the ability to include it anyway.
But maybe it is not the right way ... I was asking myself when I did it. I want to give the ability to restore 07DA unit if ever a backup exists
The only way to recover from locked phones is to reactivate them in a service center or to restore the 07DA unit.
Click to expand...
Click to collapse
sky202_how89 said:
Yes, nothing worked because Flashtool just accidentally bricked our Sony in the whole world. A careless mistake destroy the phone.
In 0.9.18.X, simlock.ta is always excluded by default but a careless mistake on the version 0.9.19.(1234) (at that time), The Simlock.ta is included while flashing. Each phone TA has their own unique number. Besides changing the mianboard (the only solution right now), no ones manage to solve this issue.
I wonder how many Sony phone in the world has already been bricked by this Flashtool update.
Click to expand...
Click to collapse
Well, that is disappointing
Hard to believe, that Sony really did that serious change in its software.
hitman-xda said:
Well, that is disappointing
Hard to believe, that Sony really did that serious change in its software.
Click to expand...
Click to collapse
At least you're out of trouble. I suggest you need to backup your TA Partition just in case.
Each TA is unique and cannot be transferred.
If your TA is used by 3rd party, they may face a Hard Brick & cannot be recovered anymore.
Well, this is an added Security by Sony. They are not stupid to "share" openly for free.
Now I'm realize.
sky202_how89 said:
At least you're out of trouble. I suggest you need to backup your TA Partition just in case.
Each TA is unique and cannot be transferred.
If your TA is used by 3rd party, they may face a Hard Brick & cannot be recovered anymore.
Well, this is an added Security by Sony. They are not stupid to "share" openly for free.
Now I'm realize.
Click to expand...
Click to collapse
I can't do that. Coz I have already unlocked my bootloader months ago
hitman-xda said:
I can't do that. Coz I have already unlocked my bootloader months ago
Click to expand...
Click to collapse
That's bad but still not too late. Your next Sony in future will be secured
I'm already ordered the replacement mainboard.
What kind of mainboard-Lock BL or Unlock BL, I do not know because it's not a new one.
Waiting for shipment.
Hey guys,
I can't start up my Sony Xperia S. It just stucks at the SONY logo screen.
I've downloaded Xperia Companion and tried Software Repair, but it says cannot be repaired as the Bootloader is unlocked. Now I'm trying to lock the bootloader but I don't know how.
I'd like to reset my phone to its original form, i.e. bootloader locked and unrooted. Any ideas?
Btw, I'm using a Mac.
Any help/advice is much appreciated. Thanks!
eros101 said:
Hey guys,
I can't start up my Sony Xperia S. It just stucks at the SONY logo screen.
I've downloaded Xperia Companion and tried Software Repair, but it says cannot be repaired as the Bootloader is unlocked. Now I'm trying to lock the bootloader but I don't know how.
I'd like to reset my phone to its original form, i.e. bootloader locked and unrooted. Any ideas?
Btw, I'm using a Mac.
Any help/advice is much appreciated. Thanks!
Click to expand...
Click to collapse
What you did the last thing?
nageswarswain said:
What you did the last thing?
Click to expand...
Click to collapse
I think I was trying to flash custom ROM.
But it didn't work and my phone just wouldn't start up, so I bought a new phone 6 months ago and put this aside.
Now I'd like to start up this phone and try to access my pictures etc.
eros101 said:
I think I was trying to flash custom ROM.
But it didn't work and my phone just wouldn't start up, so I bought a new phone 6 months ago and put this aside.
Now I'd like to start up this phone and try to access my pictures etc.
Click to expand...
Click to collapse
OK download stock ftf (search Google for stock jelly bean for Xperia s). Then flash it by flashtool software. There is plenty of guide for how to flash official jellybean on Xperia s by flash tool.
nageswarswain said:
OK download stock ftf (search Google for stock jelly bean for Xperia s). Then flash it by flashtool software. There is plenty of guide for how to flash official jellybean on Xperia s by flash tool.
Click to expand...
Click to collapse
Thanks for the advice!
I followed the instructions here: https://forum.xda-developers.com/showthread.php?t=2422053
Flash the official jellybean.
It has some progress but I still cannot start up my phone.
When I start it up, the Sony logo appears, followed by the Xperia logo and the colourful light stream. Then it repeats itself, SONY, Xperia, light stream........ etc.
It's better than just the SONY logo I had before.
What should I do next?
Give it some more time on that state.. It should boot OK.. If not then flash again.
nageswarswain said:
Give it some more time on that state.. It should boot OK.. If not then flash again.
Click to expand...
Click to collapse
I flash it again, and still it can't start up.
I gave it 30 minutes, and it's still in the loop, Sony - Xperia - lights.
what should I do?
I've also tried to repair using the Xperia Companion but it says, bootloader is unlocked, so NO.
how to relock the bootloader then?
It's really strange why this happend to you... Are you flashing the correct ftf?try a custom rom ad see what's happening
i believe that the latest flash tool doesnt work with xperia s anymore so look for an older version
Use emma..