Develop Bugs

problems and questions with unlocking bootloader

Will this void my warranty even if the HTC developer site supports it and if it does is there a way to lock it? I also have problems while getting the codes I must send to HTC it just gets stuck on Waiting for device... Can anyone help me
Sent from my Galaxy Nexus

Hi
This may help you answer your first question
http://forum.xda-developers.com/showthread.php?t=1709782
To your second question:
No. If you unlock the bootloader you can never go back to
the same "Locked" state as before. So looking at the bootloader
it is always visible that the bootloader has been unlocked once.
And the third one:
Is your device listed when youn run
fastboot devices
If not - recheck your USB connection (e.g. Drivers)
More tips are found here
http://forum.xda-developers.com/showthread.php?t=1598964
My first try also failed on Win7 so I went back to my old PC with Vista where it worked
regards
max

That was great thanks a lot very informative. I followed the unlock bootloader tutorial but i don't remember any drivers.. can you link the drivers to me please ?
EDIT: Yes i have windows 7 but no older pc.. Ideas?
Also is there a way to remove sense and have stock ICS can't find any ROM that does that
Sent from my Galaxy Nexus

JamesInsights said:
That was great thanks a lot very informative. I followed the unlock bootloader tutorial but i don't remember any drivers.. can you link the drivers to me please ?
EDIT: Yes i have windows 7 but no older pc.. Ideas?
Also is there a way to remove sense and have stock ICS can't find any ROM that does that
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
http://www.htc.com/www/help/
"HTC Sync for all HTC Android phones", driver comes with Sync. Just make sure to disable the actual software after your install, it's kinda annoying and largely useless.

clxcoltz said:
http://www.htc.com/www/help/
"HTC Sync for all HTC Android phones", driver comes with Sync. Just make sure to disable the actual software after your install, it's kinda annoying and largely useless.
Click to expand...
Click to collapse
Great, Thanks!

Removing preinstalled apps on Xperia play

Hi,
I am been researching for few weeks now. Being just an android user and a beginner level android developer, I am kind of lost in trying to solve my issue. I bought a Xperia Play. It is carrier unlocked. The main issue is the internal memory which keeps getting filled up from time to time, that makes me sacrifice some less used but important apps. I would like to make use of my phone more efficiently and utilise it to its maximum potential. Request someone to help me achieve this by helping me remove these apps.
Thanks

you have to root your phone first and u will find a tutorial im the development section... And after that you can use titanium backup to remove those apps

Hi,
Thanks for the info. But I am kind of lost when I went through the forum. Can you please guide me a specific one? Thanks.
Sent from my R800i using xda app-developers app

You could unlock your bootloader. You can do this here: http://unlockbootloader.sonymobile.com/
This enables you to flash custom Kernels and Roms. Although you don't need this if you only want to root your phone, but in my experience custom roms and kernels are a great advantage if you want to get more out of your phone
The rooting thread would be this one: http://forum.xda-developers.com/showthread.php?t=1325334

Bombasti said:
You could unlock your bootloader. You can do this here: http://unlockbootloader.sonymobile.com/
This enables you to flash custom Kernels and Roms. Although you don't need this if you only want to root your phone, but in my experience custom roms and kernels are a great advantage if you want to get more out of your phone
The rooting thread would be this one: http://forum.xda-developers.com/showthread.php?t=1325334
Click to expand...
Click to collapse
Thanks Bombasti, but the unlock boot loader from sony mobile does not work for phones with IMEI numbers greater than 14 digits. Further, I also tried SuperOneClick but I keep getting the errors in Step 1 stating that the "rm failed for /data/local/tmp/boomsh. No such file directory", Step 2 also returns similar result. Can you help. Thanks.

xdadevprince said:
Hi,
Thanks for the info. But I am kind of lost when I went through the forum. Can you please guide me a specific one? Thanks.
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
Go to the general section then look for my "Mega thread all my tutorials in one thread"
Sent from my R800i using Tapatalk 2
---------- Post added at 12:25 AM ---------- Previous post was at 12:24 AM ----------
xdadevprince said:
Thanks Bombasti, but the unlock boot loader from sony mobile does not work for phones with IMEI numbers greater than 14 digits. Further, I also tried SuperOneClick but I keep getting the errors in Step 1 stating that the "rm failed for /data/local/tmp/boomsh. No such file directory", Step 2 also returns similar result. Can you help. Thanks.
Click to expand...
Click to collapse
Enter the first 14digits
Sent from my R800i using Tapatalk 2

xdadevprince said:
Thanks Bombasti, but the unlock boot loader from sony mobile does not work for phones with IMEI numbers greater than 14 digits. Further, I also tried SuperOneClick but I keep getting the errors in Step 1 stating that the "rm failed for /data/local/tmp/boomsh. No such file directory", Step 2 also returns similar result. Can you help. Thanks.
Click to expand...
Click to collapse
This is not correct. You just have to enter the 14 first digits. So it should work for your phone unless there are other restrictions (e.g. from your phone provider).
Did you try it with the first 14 digits?
Also did you run SuperOneClick as administrator? I have no idea how SupoerOneClick works, but the error says that it can't remove a directory that doesn't exist. Maybe you can create the dir on your phone to fool the program?
Greetings,
Bombasti
-----------------------EDIT:---------------------
I checked the SuperOneClick thread here: http://forum.xda-developers.com/showthread.php?t=803682/
The R800i isn't listed as compatible device, what doesn't mean it's not compatible since the list is incomplete. But I remember that it didn't work for my phone either ( I tried it some time ago). I solved the problem through flashing an already rooted rom. Later i user Cyanogenmod which rooted from the beginning. But this needs an unlocked bootloader first...

Bombasti said:
This is not correct. You just have to enter the 14 first digits. So it should work for your phone unless there are other restrictions (e.g. from your phone provider).
Did you try it with the first 14 digits?
Also did you run SuperOneClick as administrator? I have no idea how SupoerOneClick works, but the error says that it can't remove a directory that doesn't exist. Maybe you can create the dir on your phone to fool the program?
Greetings,
Bombasti
-----------------------EDIT:---------------------
I checked the SuperOneClick thread here: http://forum.xda-developers.com/showthread.php?t=803682/
The R800i isn't listed as compatible device, what doesn't mean it's not compatible since the list is incomplete. But I remember that it didn't work for my phone either ( I tried it some time ago). I solved the problem through flashing an already rooted rom. Later i user Cyanogenmod which rooted from the beginning. But this needs an unlocked bootloader first...
Click to expand...
Click to collapse
superoneclick works fine just make sure you have all the drivers installed

fma965 said:
superoneclick works fine just make sure you have all the drivers installed
Click to expand...
Click to collapse
Ah that might have been my problem then.

Bombasti said:
Ah that might have been my problem then.
Click to expand...
Click to collapse
by all I meant the adb,fastboot and flashmode
Sent from my R800i using Tapatalk 2

[Noob-friendly] Poor man's FlashTool

Version 3 released! Check for even more simplicity and a new UI! NO more copying!
Click to expand...
Click to collapse
If you're experiencing errors, please report them either in the thread or PM me.
Please report ANY errors or typos you come across, I made this in 4 hours without a single break, so there's bound to be an error somewhere
What's new:
-Completely rewritten (ACTUALLY written, not VB)
-Even simpler! NO MORE COPYING!
-Even smaller in disk size!
-No tutorial needed! Yes, it's that easy -- just read carefully and don't panic
There's still no way to:
-relock the bootloader
-flash FTF files
_____________________________________________________________________________________________
Note: Inside the Fastboot.rar, there are fastboot drivers for 2012 Xperias. Install them if you dont have them yet. Those are the only useful files you need from that folder, everything else (both adb and fastboot) are already contained in the new BU.zip!
TESTING:
Reported working Windows versions:
Windows 7 x86
Windows 7 x64
Windows Vista x86
WANT TO HELP?
Then test it and report your phone model and windows version (x64/x86, service pack etc.) -- send me a PM
Please do... You can always flash a kernel or recovery.
Thanks for helping me and all those noobs out
About the attachments:
-Fastboot; contains adb and fastboot, plus Xperia 2012 Windows drivers
-BootloaderUnlock; contains the old PMFT - version 2 (kind of useless unless you understand everything it says in there)
-nexus; the NEW PMFT - version 3 -- if you already have the drivers, this is all you need

someone755 said:
I've been getting some questions on PM lately, about 'how to unlock my bootloader'...
So, fed up with those infinite PMs, I quickly put this together (30 minutes, not much).
It's not much, and I've only tested it for one minute, but it should help the average noob user get their bootloader unlocked.
(I've only tested this on a x86 Win7 PC, so please help me find out where this works on.)
So, the basic idea is, that the noob user extracts the attached adb and fastboot .zip file and extracts it to disk C: (I'll make options for other drives later on, I just need to know whether or not this works). The user then opens up the program inside BootloaderUnlock (and installs it), and, after many warnings, gets to a screen where he is told to input his Bootloader unlock code (obtained from Sony's website).
The program then warns the user a little more, just to make sure he understands, and then, two lines of text show up.
The user enters those lines of text into the console window (the fastboot.exe he extracted at the beginning) and Viola!
If all steps have been done correctly, he now has an unlocked bootloader
It's a simple, yet fool-proof concept, tested on a complete phone moron (after reading some instructions on Sony's unlock site).
Please help me test this, as this may be really helpful to those that don't understand FlashTool and don't have an idea how to do it via the official method.
Also, if you don't understand, there are some instructions within the program (written in VB, so you may need NET framework... MAY need it...)
Thanks for helping me and all those noobs out
Note: extract the fastboot.rar to C:, so you will have the fastboot.exe in C:\Fastboot\fastboot.exe
Note: Inside the Fastboot.rar, there are fastboot drivers for Xperias. Install then if you dont have them yet.
Note: The BootloaderUnlock.rar is a visual basic program. Please help me test it on different Windows systems (XP, Vista, 7, 8, 2000; all both x86 and x64)
Click to expand...
Click to collapse
A way to get a noobs phone bricked?!
Sent from my LT28at using xda app-developers app

derrickdroid said:
A way to get a noobs phone bricked?!
Sent from my LT28at using xda app-developers app
Click to expand...
Click to collapse
No it wouldn't. It'll either work or not
Sent from my Jellybean Xperia S

Yeah, it's actually the same as Sony's way, this program just tells the user what to write into the CMD window.
You can't brick your phone with this, because it either suceeds or fails. Either gain or no gain (and no loss) for the user...

someone755 said:
Yeah, it's actually the same as Sony's way, this program just tells the user what to write into the CMD window.
You can't brick your phone with this, because it either suceeds or fails. Either gain or no gain (and no loss) for the user...
Click to expand...
Click to collapse
i think he was referring to:
IF you are so beginner that you aren't able to even unlock your bootloader
THEN you could be so newbie to brick it

That's possible, if you're pointing to the fact they could brick their phone after unlocking the bootloader.
But before the unlock, no, it wouldn't be possible...
But hey, some people might have trouble with windows and are new to it. (I know many linux users that are forced to use windows for their phones that could use tools like this for their phones (not Sony, but others...)...)

So can this way unlock any bootloader even if it says bootloader locked? Thanks
Sent from my LT28i using xda app-developers app

Nope.
Did you not read the first post?
It's the same as the official method, but simplified...
Nothing's changed, basically, so it can't do more and it can't do less!

Ok thanks just dont understand why they sell ones that can and others you cant unlock oh well
Sent from my LT28i using xda app-developers app

Its not the phone, it's the carrier...

mcmanone said:
Ok thanks just dont understand why they sell ones that can and others you cant unlock oh well
Sent from my LT28i using xda app-developers app
Click to expand...
Click to collapse
It's because companies like AT&T give locked down phones away for free with a service contract. That way they can lock some services to make you pay more. For example AT&T makes you pay an additional monthly fee for the use of tethering (only when you use the att stock Rom, it's free on generic version )
From Jaramie's LT28at
2012Xperia SOFT-BRICK Recovery Thread

So I guess it's great in my country;
you don't get a 'free' phone, you pay at least 1€ (depending on the plan you chose; I chose the one where I get to pay 370€ for a nozomi)
You can always trade your phone on Swappa (you have loads of ads on CM's sites and forums) and get an unlockable one...

what is the difference between this tool and this one?
http://forum.xda-developers.com/showthread.php?t=1794800

This one, you can't flash things with, and you don't need a ton of downloads...
Yours is actually a program that uses FlashTool... It has flashtool included in the libs, which means:
1. You download the program AND the giant FlashTool
2. It can flash FTF, IMG and SIN files (because this is flashtool after all...)
I came up with my method for people with bad internet and limited storage...
It actually is the official method, but with a "paste-press-copy-paste" procedure, although the main idea is about the same as all the others...
Basically, every method is based on the official way, but there's a bit of variation here and there...

someone755 said:
This one, you can't flash things with, and you don't need a ton of downloads...
Yours is actually a program that uses FlashTool... It has flashtool included in the libs, which means:
1. You download the program AND the giant FlashTool
2. It can flash FTF, IMG and SIN files (because this is flashtool after all...)
I came up with my method for people with bad internet and limited storage...
It actually is the official method, but with a "paste-press-copy-paste" procedure, although the main idea is about the same as all the others...
Basically, every method is based on the official way, but there's a bit of variation here and there...
Click to expand...
Click to collapse
okay thanks....
DOWNLOADING

Let the Noob try it !!
Hey Guys,
I am a Noob and have been trying to unlock my bootloader for about a week now, I have tried a few methods without any joy.
I will give this a go and will report back if it works or not. :laugh:

Your problem might be one of these, if it doesn't work:
1. Your phone is not in fastboot mode -- did you check that?
2. You don't have the right drivers installed on your PC -- or do you?
3. Your phone's bootloader may not be unlockable -- now, if you didn't check that, you really are a noob.
4. Your unlock code is incorrect -- that was the case with me, but in the end that was the only problem...

someone755 said:
Your problem might be one of these, if it doesn't work:
1. Your phone is not in fastboot mode -- did you check that?
2. You don't have the right drivers installed on your PC -- or do you?
3. Your phone's bootloader may not be unlockable -- now, if you didn't check that, you really are a noob.
4. Your unlock code is incorrect -- that was the case with me, but in the end that was the only problem...
Click to expand...
Click to collapse
Hi,
Thanks for the reply, the problem i have is with the drivers. I have tried different solutions as posted here and on the web.
But still could not get the drivers to work??
I will try this method as it states the drivers are included. If it all works awesome, if not then I fail and will forever be stuck with stock rom's.

Which windows are you running (vista, 7, 8, is it 32 or 64 bit?)?
Also, did you try with FlashTool's drivers?

someone755 said:
Which windows are you running (vista, 7, 8, is it 32 or 64 bit?)?
Also, did you try with FlashTool's drivers?
Click to expand...
Click to collapse
I'm running windows 7 on a 64 bit laptop.
Tried the flashtool drivers also but still no joy, I check in device management for S1 and each time there is a problem installing the drivers.
I still have a PC running vista so might give that a try if all else fails.
Thanks for your help so far, will keep you updated with how I get on

[Q] Trouble Unlocking Bootloader

Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. I have been trying to unlock this phone for 2 days now!
Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well my code is 16 numbers long. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same.
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.

Tread3r said:
Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. For purposes of convenience and time (I have been trying to unlock this phone for 2 days now!) I will post my IMEI code here ( 3529000059203526 ) and the unlock code given to me by sony through email (61CAA387DC11C4CF).
I hope this doesnt break any rules or anything.
I am doing this to see if anyone here can help me. Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well as you can see my code is 16 numbers long, so in effect I only entered up to number "5". I would like to know if anyone is willing to test my IMEI and see if they get the same code. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key, this is why I am posting. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same (as above).
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.
Click to expand...
Click to collapse
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.

abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Thanks for the advice, I will edit it ASAP.

abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Hey he removed the imei number from his original message but that's pointless unless u remove it from your quote
Sent from my Xperia S using xda app-developers app

I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967

Chriszo said:
I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967
Click to expand...
Click to collapse
Glad to hear im not alone . No I still haven't found a way to unlock it. Sorry for asking but what does "PN" mean? Just so we are clear.

Ok thanks for your answer. No problem, but its just a mistake. Correctly it should be "PM" for personal message. I thought you would write on this way so I cant read any reasults

UPDATE:
I have tried other processes that all have the same steps, be it they were simplified programs with GUI's. I have come to the conclusion that my fastboot driver was installed incorrectly, because the first time I installed it on my phone I was able to see the S1 bootloader icon on device manager and I was able to click on it fast enough to enable it to install the driver. And correct me if im wrong but when we press UP on the volume rocker on our XS's and connect it to the USB we should see a blue right light? Well that is what happens when I do it so I assume I installed it correctly then.
Now after these first few failed attempts at unlocking I got frustrated and just factory reset my phone, completely ( I made back ups of course). This time however I used a program which is suppose to install all the drivers and simplify the whole unlocking process, I dont remember what program exactly, i'll check my files and get back to you guys on that.
Again it failed, showing the FAILED ("oem" error message) so I checked the steps from Doomlords guide and re checked my device manager. This time when I connect my phone it doesnt show the S1 bootloader icon on Dev manager, instead it shows "android phone ADB Interface". BUT I still get the blue LED when I connect my phone via USB, so does that mean I have fastboot on my phone again? ( I assume I do because the program I used says it did install it correctly and it even showed the "install anyway" window)
I am almost loosing all hope to unlock my XS , maybe I got a lemon phone or did something wrong again. I am willing to do another factory reset and restart the whole process again. This time I will follow every single step on the official website and see what happens.
But before I do that I want to ask, does anyone know of any news or whereabouts for an unofficial unlock bootloader process? I know its a long shot because we already have an official way but as from recent experience it doesnt work 100% of the time.

Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/

Chriszo said:
Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/
Click to expand...
Click to collapse
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.

Tread3r said:
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.
Click to expand...
Click to collapse
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).

It was AOKP, the advanced project for this device.
I think your right, but in how far is the bootloader linked to the needed kernel? And why cant the bootloader be unlocked several times...?
Of course the kernel is a main part of the rom, but without an unlocked bootloader even the kernel would not be accepted by the bootloader. Thats the problem with other firmwares/ roms why you have to unlock it

I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?

razormc said:
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).
Click to expand...
Click to collapse
I am using Windows 7 and I have used flashtool. I believe the drivers are correct because,as you said, the blue LED does show and stay while I fastboot my phone. Same goes for the green LED when I go to flashboot.

Chriszo said:
I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?
Click to expand...
Click to collapse
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve

Tread3r said:
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve
Click to expand...
Click to collapse
First, unlock your bl. Then root. I done that on my old Arc S and it works great.
Sent from my LT26i using xda developers-app

@ Tread3r:
Yes the drivers are installed correctly, because the phone starts into fastboot and flashboot with each the right light.
Thats the great problem with our devices. I did it nearly the same way and Ive got a similar problem, as the first answers describe in this post. Actual the original stock rom is installed on my Sony and all works correctly, but its just a short-term workaround
The bootloader unlockind process still end in an error message and that is my problem.
@ Vatih:
Nice try, but this is our problem... :/
---------- Post added at 11:41 AM ---------- Previous post was at 10:57 AM ----------
I cant believe it myself, but the alternative way works, althought I cant read anythink in the tool because of the language...
I've got the superuser app and root permissions and all works.
This link helped me: http://forum.xda-developers.com/showthread.php?p=39498268
It's the tool for the "new" firmware, .55, the latest from sony.
Hope, its also succesfully with your devices

I solved our problem. My bootloader is now open
I did it with the unlock, flashtool tool of this forum that helps you to open the bootloader and flash kernels and roms.
http://forum.xda-developers.com/showthread.php?t=2087337
Seems like just the code was wrong.
It worked with the first try
But be careful, although its just the bootloader, all data will be deleted. My phone is empty again :/ Of course I've got some backups...

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