Develop Bugs

[Q] Unlocked bootloader wanting to root

Hi guys!
Well, I'm new in what concerns to root, unlock, ROM's, kernels (no idea of what it is still), etc. I have a Xperia Arc, GB 2.3.4, branded for T-Mobile.
As I'm fed up with the bunch of bloatware, I wanted to root/debrand it, in order to get rid of it.
First I tried with this thread: http://forum.xda-developers.com/showthread.php?t=1035276 Post #2
Links for the ROM were dead, so I searched for some other thread. After a lot, I found this one: http://forum.xda-developers.com/showthread.php?t=1042978
I found it easy to lead, so i tried. I got so far, to even unlock my bootloader, but then, trying to root, I found the images link for the Global firmware was dead.
Then I realized, I wanted to change to the global versión for the mere reason of having ICS sooner (branded phones take longer to receive it, as far as I know). Then I saw, that actually I went in the full wrong direction when unlocking the bootloader.
I tried to relock thebootloader, by following the steps in this thread: http://forum.xda-developers.com/showthread.php?t=1324703
It appears to have worked well, but I'm not sure.
My questions are:
1) I want the SE ICS update, that is due to be available this month anytime. Since unlocking the bootloader might have turned my phone to brick (or not?) when upgrading, how can I be sure I did actually re-lock my bootloader? The guys from Android Soul Comnunity used a "Test" on their videos, which was running a program in fastboot mode, which apparently does something if the phone is unlocked, although it said "it needs to be rooted". Is there a way to know if I did it correctly relock whitout damaging my phone or flashing it by mistake in the process.
2) I really want to flash it to a global version and get rid of the bloatware (maybe rooted if posible), but also getting the official upgrade. Is there a way? I have the latest flashtool version and I downloaded the ftf file for the global version, but whenever I press flash in flashtool, it doesn't show anything (nor sin files or anything else). Maybe I will give it another try if someone else provides me with a functional link to the functional ROM (I really don't remember where I got the one I have).
I hope you guys can help me. I'm not a native english speaker, so forgive me for any mistake. Thanks in Advance
HerrJuancho

seems like you are new to this....so was I about 4 months ago.
if your bootloader is unlocked, good - keep it that way.
the best way to learn how to mess around is follow this thread step-by-step:
http://forum.xda-developers.com/showthread.php?t=1299729
I know that this thread is instructing you to flash cm7 - but dont worry, once you have done that, you will understand the basics and the processes involved.
if you really want ICS - then you can just us Arconium 2.2 as it is the closed custom rom to a stock ICS - it is tweaked and customized, so it will be better than any global rom you try to flash.
http://forum.xda-developers.com/showthread.php?t=1515148

kaatisu84 said:
seems like you are new to this....so was I about 4 months ago.
if your bootloader is unlocked, good - keep it that way.
the best way to learn how to mess around is follow this thread step-by-step:
http://forum.xda-developers.com/showthread.php?t=1299729
I know that this thread is instructing you to flash cm7 - but dont worry, once you have done that, you will understand the basics and the processes involved.
if you really want ICS - then you can just us Arconium 2.2 as it is the closed custom rom to a stock ICS - it is tweaked and customized, so it will be better than any global rom you try to flash.
http://forum.xda-developers.com/showthread.php?t=1515148
Click to expand...
Click to collapse
Thanks, I thought no one would answer.
I don't know if I actually still have a unlocked bootloader. How can I tell the difference? By doing what?
If it is really that good, the I would prefer it over the official. Thanks

HerrJuancho said:
Thanks, I thought no one would answer.
I don't know if I actually still have a unlocked bootloader. How can I tell the difference? By doing what?
If it is really that good, the I would prefer it over the official. Thanks
Click to expand...
Click to collapse
Do this
1)Connect your phone on fastboot mode.
2) open cmd prompt in the fastboot folder
3) type this in the command window
fastboot.exe -i 0x0fce get var version
4) if you get a value like 0.3 or something its unlocked
Sent from my LT26i using xda premium

king-iyokan said:
Do this
1)Connect your phone on fastboot mode.
2) open cmd prompt in the fastboot folder
3) type this in the command window
fastboot.exe -i 0x0fce get var version
4) if you get a value like 0.3 or something its unlocked
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
Well, that's actually one of the steps before unlocking, I thought it was just a sign that the device was well connected and that the drivers were up to date. My phone wasn't unlocked, and it did show 0.3 right before trying to unlock it.

HerrJuancho said:
Well, that's actually one of the steps before unlocking, I thought it was just a sign that the device was well connected and that the drivers were up to date. My phone wasn't unlocked, and it did show 0.3 right before trying to unlock it.
Click to expand...
Click to collapse
Ohh sorry. My bad. Try to boot a custom kernel via fastboot.
Fastboot.exe boot boot.IMG
If you get a notice "device not rooted" or similar the bootloader is loced.
If you are able to boot the kernel the bootloader is unlockd
Sent from my LT26i using xda premium

[Q] [P/Q] Waiting for device in fastboot Xperia Play

Hey guys!, I need some help over here, i have read many post like mine, but i cant find a solution, i have rooted my phone succesfuly now i want to update the kernel and install a custom rom, but im stuck in the fastboot command window it says "waiting for device", here are some pics, to explain it better, drivers seems to be fine, i tryed diferent usb port, im runinig W7... please help.

PsychopathMx said:
Hey guys!, I need some help over here, i have read many post like mine, but i cant find a solution, i have rooted my phone succesfuly now i want to update the kernel and install a custom rom, but im stuck in the fastboot command window it says "waiting for device", here are some pics, to explain it better, drivers seems to be fine, i tryed diferent usb port, im runinig W7... please help.
Click to expand...
Click to collapse
Do you have R800a model? Did you unlocked your bootloader with testpoint?
Also, try back usb port on your motherboard, not front ones

Thanks for your reply, Yes it is a R800a, i used DooMLoRD_v4_ROOT-zergRush-busybox-su, to unlock the phone,
i have tried back usb ports too, and well my pc does detect the device even if it is in recovery, but fastboot doesnt.
Bakisha said:
Do you have R800a model? Did you unlocked your bootloader with testpoint?
Also, try back usb port on your motherboard, not front ones
Click to expand...
Click to collapse

PsychopathMx said:
Thanks for your reply, Yes it is a R800a, i used DooMLoRD_v4_ROOT-zergRush-busybox-su, to unlock the phone,
i have tried back usb ports too, and well my pc does detect the device even if it is in recovery, but fastboot doesnt.
Click to expand...
Click to collapse
ZergRush method is just for rooting, not for "unlocking phone". Rooting is just a way to grant you root user right on your phone (and you can do it on locked bootloader, wich you obviously did). To be able to install custom kernel, you must first unlock bootloader
I don't have R800a model, so i can't help you much, but you can help yourself by reading sticky threads in "general" and "Q&A" sections to inform yourself about your phone, because R800a model is little specific (it doesn't have fastboot access, kernels can be flashed only in flash mode, and only when bootloader is unlocked via testpoint method)

Hey thanks, i didnt knew that, and well it seems that my phone is now unlocked i used wotanserver (pics below 7.99 UE not bad), i still dont have access to fastboot as you mention, now i download flashtool, and well, i am stuck what i have to do now? i have the kernel, the room, i dont know if im missing something.
Bakisha said:
ZergRush method is just for rooting, not for "unlocking phone". Rooting is just a way to grant you root user right on your phone (and you can do it on locked bootloader, wich you obviously did). To be able to install custom kernel, you must first unlock bootloader
I don't have R800a model, so i can't help you much, but you can help yourself by reading sticky threads in "general" and "Q&A" sections to inform yourself about your phone, because R800a model is little specific (it doesn't have fastboot access, kernels can be flashed only in flash mode, and only when bootloader is unlocked via testpoint method)
Click to expand...
Click to collapse

PsychopathMx said:
Hey thanks, i didnt knew that, and well it seems that my phone is now unlocked i used wotanserver (pics below 7.99 UE not bad), i still dont have access to fastboot as you mention, now i download flashtool, and well, i am stuck what i have to do now? i have the kernel, the room, i dont know if im missing something.
Click to expand...
Click to collapse
You don't have fastboot, but you can stll flash kernel with flashtool in flasmode connected (back button pressed while plugging i phone)
There is thread for kernels in ftf format at http://forum.xda-developers.com/showthread.php?t=2350707 that korrectmethod made for guys like you.

Thank you so much Bakisha, i finally install both kernel and rom (Doomlord V14 and AtoMic GB 7.0), it is working like a charm! my only issue is that now, when i pull the game pad, it doenst display the games to select the one i want to play, i mean the dashboard, do i need an app? anyways it looks and feel great, i was about to giving up but it worked at the end, overclock works great at 1.2 Ghz.
and well thx again!.
Bakisha said:
You don't have fastboot, but you can stll flash kernel with flashtool in flasmode connected (back button pressed while plugging i phone)
There is thread for kernels in ftf format at http://forum.xda-developers.com/showthread.php?t=2350707 that korrectmethod made for guys like you.
Click to expand...
Click to collapse

PsychopathMx said:
Thank you so much Bakisha, i finally install both kernel and rom (Doomlord V14 and AtoMic GB 7.0), it is working like a charm! my only issue is that now, when i pull the game pad, it doenst display the games to select the one i want to play, i mean the dashboard, do i need an app? anyways it looks and feel great, i was about to giving up but it worked at the end, overclock works great at 1.2 Ghz.
and well thx again!.
Click to expand...
Click to collapse
just download xperia play launcher from market
YW

[Q] Installing ROM's [Xperia S]

So after a year and half with this phone, I thought about installing a better ROM.
I experience with these kind of things from the time I had the galaxy 1 and I changed tons of ROMs on that.
But the xperia seems a bit different with ROM changing.
What are some basic things I need to know, and where can I find the stock ROM (just in case)?
If this isn't the correct to forum for this post, please notify me.

ROM changing ist not very different from Samsung...
If your bootloader is unlocked and your CWM is working, then you can install all Roms as ZIP like on the Galaxy
Always make an Backup with CWM to be save and get back in case of errors, thereforce i didn't need a the stock ROM
Just have a look here on the last pages
http://forum.xda-developers.com/showthread.php?t=1876890&page=324

Targunitoth said:
ROM changing ist not very different from Samsung...
If your bootloader is unlocked and your CWM is working, then you can install all Roms as ZIP like on the Galaxy
Always make an Backup with CWM to be save and get back in case of errors, thereforce i didn't need a the stock ROM
Just have a look here on the last pages
http://forum.xda-developers.com/showthread.php?t=1876890&page=324
Click to expand...
Click to collapse
thanks! But what I meant is that with my sgs I didn't need to open the bootloader and install CWM since it was already there.
How do I unlock the bootloader and install CWM, should I root it first?

Just have a closer look to the link mentioned above.
I postet there a link to a Guide, how to flash a custom rom (including unlocking Bootloader)
and Mirhawk gave aditional tipps
Have you bought your sgs secondhand?
Because you have to install CWM one time on your sgs, too.
And it is a similar effort to flash sgs with odin then unlocking your bootloader on the xperia S

Targunitoth said:
Just have a closer look to the link mentioned above.
I postet there a link to a Guide, how to flash a custom rom (including unlocking Bootloader)
and Mirhawk gave aditional tipps
Have you bought your sgs secondhand?
Because you have to install CWM one time on your sgs, too.
And it is a similar effort to flash sgs with odin then unlocking your bootloader on the xperia S
Click to expand...
Click to collapse
I always get stuck at rooting. the software runs, and after I do everything it gives me "Error 3" and runs forerver. Any idea?
Error type 3
Error: Activity class {com.sonyericsson.vendor.backuprestore/com.sonyericsson.ve
ndor.backuprestore.ui.BackupActivity} does not exist.
Click to expand...
Click to collapse

Not really
But i can google it for you:
http://forum.xda-developers.com/showpost.php?p=34035358&postcount=88
Edit:
which leads you here: http://forum.xda-developers.com/showthread.php?t=1898240

Targunitoth said:
Not really
But i can google it for you:
http://forum.xda-developers.com/showpost.php?p=34035358&postcount=88
Click to expand...
Click to collapse
I already have that Backup and restore app.
Anyone else?

You also have this one?
http://forum.xda-developers.com/showthread.php?t=1898240
Edit: There is another version in this thread, maybe test this...
Else I can't help you

Targunitoth said:
Not really
But i can google it for you:
http://forum.xda-developers.com/showpost.php?p=34035358&postcount=88
Edit:
which leads you here: http://forum.xda-developers.com/showthread.php?t=1898240
Click to expand...
Click to collapse
Targunitoth said:
You also have this one?
http://forum.xda-developers.com/showthread.php?t=1898240
Edit: There is another version in this thread, maybe test this...
Else I can't help you
Click to expand...
Click to collapse
Nothing works I'll wait for someone else. Thanks for the effort!

Install ROM's in Xperia S is not difficult.​
You must have Rooted your phone and Install CWM (like the comment above)
I was like you when I decided flash ROMs.
I recommend you see if your bootloader is open or not (when you verificate it, you will see in the screen of your phone BOOTLOADER UNLOCK, and then YES or NO. bootloader is easy to open when you have YES, but when it's in not is a bit complicated)
To put the BOOTLOADER UNLOCK in YES, first: you have to have your phone free (your phone have to be available to use with others companies) in my case, for example, i dont have my phone free, but to liberate it with my company, give mea code and after that I introduce it and set free the phone. (after that you will allow to open BOOTLOADER)
Here in XDA have 2 types of ROMS, to LOCK and UNLOCK bootloader, I am using TrinityVengance RaptorXL by f(x)THaxxorX, before that I used, LeopardX 5.0 by savergigio
To flash ROMs you use ClockWorldMOd, its very easy, if you need more help tell me

Milton_Mitnick said:
Install ROM's in Xperia S is not difficult.​
You must have Rooted your phone and Install CWM (like the comment above)
I was like you when I decided flash ROMs.
I recommend you see if your bootloader is open or not (when you verificate it, you will see in the screen of your phone BOOTLOADER UNLOCK, and then YES or NO. bootloader is easy to open when you have YES, but when it's in not is a bit complicated)
To put the BOOTLOADER UNLOCK in YES, first: you have to have your phone free (your phone have to be available to use with others companies) in my case, for example, i dont have my phone free, but to liberate it with my company, give mea code and after that I introduce it and set free the phone. (after that you will allow to open BOOTLOADER)
Here in XDA have 2 types of ROMS, to LOCK and UNLOCK bootloader, I am using TrinityVengance RaptorXL by f(x)THaxxorX, before that I used, LeopardX 5.0 by savergigio
To flash ROMs you use ClockWorldMOd, its very easy, if you need more help tell me
Click to expand...
Click to collapse
Thanks, but I know all that, problem is- it doesn't work. Please look above.

how to
check if my bootloader unlock?

[INFO] Xperia ACRO S Re-listed for Unlocking Bootloader

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.

From Samsung to Sony and confused about Bootloader unlocking.

Im thinking of buying a Z5P and while i have searched a lot, i just cant seem to find the answer to a question i have maybe someone here can help. On Sonys developer website there is instructions on how to unlock the bootloader and the last line of the instructions are as follows, note the part in blue text.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.[/B]
My question is how/where do i buy a Z5P that will definitely be Bootloader unlock allowed yes, surely its not just a case of random devices are unlockable is it? I was going to buy this from carphone its sim free so im expecting to be allowed to unlock the bootloader but dont want to buy it only to find i cant.
http://www.carphonewarehouse.com/phones/sony-xperia-z5-premium/handset?colourCode=BLACK

If the phone has no SIM lock, it's bootloader should be unlockable. I say "should" since I am not aware of other factors that keep the bootloader locked, but there might as well be.
On another note, unless you are a fairly advanced user and are set on flashing your device with a custom kernel, I would not recommend a bootloader unlock before root or an option to back up of TA becomes available.
It contains your device's DRM which gets irreversibly lost which makes your camera perform worse(BIONZ stops working), among other things.

CPW is the place to go for unlockable fones. I got my Z5P from there.
Sent from my SGP311 using XDA Free mobile app

As mentioned elsewhere, IN GENERAL (rare exceptions) - if it's SIM-unlocked it'll be bootloader-unlockable. If it's SIM-locked, the bootloader is almost guaranteed to be perma-locked.
While SIM locks and bootloader locks are technolgically independent, in the case of Sony devices (This rule of thumb can NOT be applied to any other manufacturer), SIMlocked devices have a permanent bootloader lock, devices sold without a SIM lock can have bootloader unlocked. Note that in the case of phones sold with a SIM lock that are later unlocked with a PIN - the bootloader lock is still disallowed.

Cheese for the replys everyone I got the phone from the carphone and its boot loader unlock allowed yes
I got the regular z5 instead though.

Hey, Dunno if I have an option or not, but my phone says Bootloader Unlock Allowed: No.
I imagine that it's a no, but is there any way to unlock the BL? If not I may consider swapping the Z5P out for something else, dunno if I can live without root

NJ72 said:
Hey, Dunno if I have an option or not, but my phone says Bootloader Unlock Allowed: No.
I imagine that it's a no, but is there any way to unlock the BL? If not I may consider swapping the Z5P out for something else, dunno if I can live without root
Click to expand...
Click to collapse
Try flashing another firmware through flashtool that is allowed.

KbaB.BroS said:
Try flashing another firmware through flashtool that is allowed.
Click to expand...
Click to collapse
Worth a punt, didn't think about that. The only concern is that Flashtool isn't supported for the Z5p according to Sony's site.

NJ72 said:
Worth a punt, didn't think about that. The only concern is that Flashtool isn't supported for the Z5p according to Sony's site.
Click to expand...
Click to collapse
As long as you use flashmode there is no need to be supported, because the program doesn't know which phone it is in that state. I flashed my Z5P once using flashtool about a week ago.

KbaB.BroS said:
As long as you use flashmode there is no need to be supported, because the program doesn't know which phone it is in that state. I flashed my Z5P once using flashtool about a week ago.
Click to expand...
Click to collapse
OK, cool, thanks.
Where do I get the firmware from for Flashtool? Can I flash something like AurRom using Flashtool?
Sorry for the idiot questions, but I haven't used Flashtool very much at all. Much more familiar with ODIN, ADB and flashing through recovery...

NJ72 said:
OK, cool, thanks.
Where do I get the firmware from for Flashtool? Can I flash something like AurRom using Flashtool?
Sorry for the idiot questions, but I haven't used Flashtool very much at all. Much more familiar with ODIN, ADB and flashing through recovery...
Click to expand...
Click to collapse
Install flashtool from "flashtool.net"
It comes bundled with Xperifirm where you can download ftf files for every Xperia device. You access Xperifirm through the Flashtool program.
You cannot flash AurROM through flashtool because it's not a ftf file. Flash a stock rom and try unlocking the Bootloader afterwards.
And don't worry about asking "stupid questions". This thread is made for every kind of questions, as long as it's about the device.

KbaB.BroS said:
Install flashtool from "flashtool.net"
It comes bundled with Xperifirm where you can download ftf files for every Xperia device. You access Xperifirm through the Flashtool program.
You cannot flash AurROM through flashtool because it's not a ftf file. Flash a stock rom and try unlocking the Bootloader afterwards.
And don't worry about asking "stupid questions". This thread is made for every kind of questions, as long as it's about the device.
Click to expand...
Click to collapse
Thanks very much.
One final question, in the UK I have EE WiFi calling currently - if I install non-carrier specific firmware I will most likely lose this. Is there any way I can backup the existing software so I can revert whether the flashtool flash works or not?

NJ72 said:
Thanks very much.
One final question, in the UK I have EE WiFi calling currently - if I install non-carrier specific firmware I will most likely lose this. Is there any way I can backup the existing software so I can revert whether the flashtool flash works or not?
Click to expand...
Click to collapse
You can try this guide:
http://m.youtube.com/watch?v=F0bSsGxFdks

NJ72 said:
Thanks very much.
One final question, in the UK I have EE WiFi calling currently - if I install non-carrier specific firmware I will most likely lose this. Is there any way I can backup the existing software so I can revert whether the flashtool flash works or not?
Click to expand...
Click to collapse
What you want to do is follow sonys instructions on how to check if your phone is able to unlock bootloader here: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
If you can unlock your bootloader, which you will know after performing the simple steps provided by sony, then you need to install android studio along with required drivers etc, before you can actually unlock the bootloader.
Android studio can be found here: http://developer.android.com/sdk/installing/index.html?pkg=studio
Read everything throughly, it is important to get all the details regarding usage and installation.
After installing Android studio, you should download all the required SDK's found inside android studio->Configure->SDK Manager.
On the left side you will see several options in the navigation menu.
First go to Appearance & Behavior->System settings->Android SDK. Then in the "window" you have, make sure the first tab is selected (SDK Platforms).
Here you need to check all the android versions your phone(s) run.
Then go to the second tab (SDK Tools) and download:
Android SDK Build Tools
Android SDK Tools 24.4.1
Android SDK Platform-Tools 23.1
Google USB Driver
Android NDK
I am not sure if you really need the NDK one, but the rest I think is required. You can do as I did and choose all if you want.
On the last tab (SDK Update Sites) I have checked everything.
When you have done all of this, you should install Flashtool and go to the install directory and open the Driver folder, where you will find a .exe file. Run this and click next untill you can choose a few items from a list, in this list you should check Fastboot drivers, and USB drivers, and any other options that are relevant to your use, then finish the installation. (The entire installation of Flashtool should be done with 100% admin rights on the user).
After this is done, connect your phone to your pc and go to device management on your pc and you will likely find something similar to this:
If you have this yellow exclamation mark triangle thingy, then you will need to manually install your USB drivers.
Download your driver here: http://developer.sonymobile.com/downloads/drivers/
Then right click the yellow exclamation mark triangle thingy device in device management, and select update driver, then select "Browse my computer for driver software".
On the next window, select "Let me pick from a list of device drivers on my computer".
In the list that appears, select "Show All Devices" and click next.
Click the "Have Disk" button, then navigate to the driver you downloaded, and you will get 3 options in the window on you screen, select "Android ADB Interface" and click next.
Confirm by pressing "Yes" Then press "Install".
If completed without problems you should see "Windows has successfully updated your driver software".
*NOTE* On the above steps, you can also navigate to the folder where you installed android studio, which should be something similar to this: C:\Program Files(x86)\Android\android-sdk\extras\google\usb_driver OR it can be found your USER folder.
and here you can install the usb_driver aswell, which should make most phones support USB debugging and ADB on via your pc.*NOTE*
now reconnect your phone and the exclamation mark triangle thingy should be gone, good!
Next thing you can do is navigate to the installation folder of Android studio, and go to the Platform-Tools folder.
Inside the folder, hold down shift, while right clicking any white empty space inside the folder, and click open terminal here.
In the terminal, type: "adb devices" /Without the " marks. then it should say something about daemon not running etc, when its done, do the same command again, and you should se you device listed. Good, at this point you are ready to unlock bootloader!
If you have succeeded in every step so far, then go ahead and unlock bootloader following sonys instructions!
When you are done, you can simply follow the guides provided in the custom Rom thread itself most of the time.
If not, then a simple way to do it is:
Get all the files you need for the rom flash. That means Kernel, rom img, and a custom recovery like TWRP and SuperSU.
It is REALLY important that all files are for your device specifically!
Put the SuperSU.zip and the custom Rom.zip on your sd card and put it in the phone.
To avoid any trouble, do as I did and save all those files in the Platform-Tools folder, because you need to open the terminal as shown earlier in the post, by holding shift and right clicking in the same folder as the files, this is a must.
Open the terminal from the same folder as the rom, kernel and recovery.
type:
Code:
fastboot flash boot NAMEOFYOUR_KERNEL.img (This is usually boot.img)
fastboot flash recovery NAMEOFYOUR_RECOVERY.img (Usually contains TWRP in name)
fastboot reboot
You should now press volume up key when a led lights up while you see the sony logo, a orange light, not the red one, this will bring you into recovery, from here choose install, then navigate to your SuperSU.zip and install it.
Reboot your phone and you are now rooted, if you also have a custom rom, then place it on your sd card like the SuperSU.zip, but make sure the custom rom is a ZIP file!
Boot into recovery and install the custom rom, wipe cache and dalvick cache.
Congratulations on your custom rom!
Hope this helps a bit, sorry for any errors, but this is exactly how I did it, as far as I can remember!
Btw, this can seem like alot of work, especially when and if you encounter any problems while installing. I know I did encounter ALOT of them, but hopefully with my simple guide you can avoid them!
Luckily, this is just something you have to do once if you do it 100% right!

xirt0n said:
What you want to do is follow sonys instructions on how to check if your phone is able to unlock bootloader here: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
If you can unlock your bootloader, which you will know after performing the simple steps provided by sony, then you need to install android studio along with required drivers etc, before you can actually unlock the bootloader.
Click to expand...
Click to collapse
The problem he has is that his stock ROM (or the phone itself) doesn't allow bootloader unlocking, probably because of SIM and carrier lock. Therefore he first needs to find a way to make the phone unlockable.

KbaB.BroS said:
The problem he has is that his stock ROM (or the phone itself) doesn't allow bootloader unlocking, probably because of SIM and carrier lock. Therefore he first needs to find a way to make the phone unlockable.
Click to expand...
Click to collapse
I am no expert on this, but doesnt the carrier decide if its locked or not?
I've seen people solve it by flashing different and unbranded firmware, but not for this particular phone tho, but I dont think it's officially possible.

xirt0n said:
I am no expert on this, but doesnt the carrier decide if its locked or not?
I've seen people solve it by flashing different and unbranded firmware, but not for this particular phone tho, but I dont think it's officially possible.
Click to expand...
Click to collapse
At this point he could at least try, he's got nothing to lose. I have never had this problem, because I buy my phones unlocked no carrier involved, so these are only suggestions.

KbaB.BroS said:
At this point he could at least try, he's got nothing to lose. I have never had this problem, because I buy my phones unlocked no carrier involved, so these are only suggestions.
Click to expand...
Click to collapse
Yeah, what I would try is first just try to do a full restore of your phone via PC Companion, and if that doesnt work then id try downloading an unbranded firmware from XperiFirm (If I am not mistaken, those named CUSTOM or something are unbranded) and then flash that via flashtool and see if that works, if not then your last hope is to get it replaced by warranty, which I'd say is fraud if the device isnt actually malfunctioning.

xirt0n said:
Yeah, what I would try is first just try to do a full restore of your phone via PC Companion, and if that doesnt work then id try downloading an unbranded firmware from XperiFirm (If I am not mistaken, those named CUSTOM or something are unbranded) and then flash that via flashtool and see if that works, if not then your last hope is to get it replaced by warranty, which I'd say is fraud if the device isnt actually malfunctioning.
Click to expand...
Click to collapse
I don't think PC Companion works at all, because the only thing it does is downloading identical firmware like the one on the phone. So Flashtool only choice.
I replaced mine with one from flashtool that has a lot less bloatware it originally came with.

KbaB.BroS said:
I don't think PC Companion works at all, because the only thing it does is downloading identical firmware like the one on the phone. So Flashtool only choice.
I replaced mine with one from flashtool that has a lot less bloatware it originally came with.
Click to expand...
Click to collapse
Ok, I never personally used PC companion so I didnt know what it does, I just saw people suggest it around