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...
Related
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
So, after trying for a month to unlock my bootloader with every single method I can find online, I've come to this:
-There are two methods described on XDA, and those are the official Sony way and the FlashTool way
-Both methods give me an error (see attachment)
-I've heard of a 'testpoint' method, but I can only find a tutorial for 2011 phones (also, there are no visible testpoints on the phone without taking it apart)
-Nobody has helped me yet, as every thread I post in dies as soon as I ask my question...
So, if anyone can help me with my bootloader unlocking, that'd be great... (preferrably with FlashTool or the official way)
I have the drivers installed, and I've tried on 3 different PCs, so I know it's not a USB port going bananas...
Thanks
(and sorry if I missed the correct forum)
and you have tried the sony webpage to unlock the bootloader?
If it's unlockable there shouldn't be any problems using that site.. Or do you get a error there too??
Nope, nothing works...
I don't really know what to do now, since I really am used of ROM flashing back from my Desire days...
The last ROM I tried was MIUI for locked bootloaders, but I got a brick out of that... XD
someone755 said:
Nope, nothing works...
I don't really know what to do now, since I really am used of ROM flashing back from my Desire days...
The last ROM I tried was MIUI for locked bootloaders, but I got a brick out of that... XD
Click to expand...
Click to collapse
Go to the sony official bootloader page and ask for a new one. Just do all the steps again and it will work, it's probably because you used the key and it failed the first time. That's how it worked for me
Nope, that ain't the problem... At least probably not, because I got the same key 3 times from Sony...
I'll check again and report back if it succeeds
Thanks for your help
Well I got a new code (entered another email address and another name, though the IMEI is still the same... (wtf's up with that, anyways?))...
I'm as chilled as a kid on a christmas morning DDD
Gonna try it out
EDIT: I THINK it worked... The CMD window says 'okay' but I'm not sure...
EDIT2: Yay! IT worked!! Thanks a million times DD
Hi all!
Okay so I'm ready to bash my face off something till I die... lol I've been up all night screwing with my xperia play from rogers. First I did the touchpoint method to unlock the bootloader and s1tool confirms that it's unlocked. However, no fastboot and when I punch in the code provided by SE to see the value of "bootloader unlock allowed"... it's still "no". From what I understand the touchpoint method shouldn't change this value. However because this value is still set, I have a feeling that this is why I can't enable fastboot.
I'm trying to flash a custom jellybean rom using flashtool and because of the aforementioned situation, I can't. I'm wondering if anyone can point me in the right direction to get fastboot working. I hate that I've paid through the nose for all the android devices I own and I yet I still don't technically own them. Anyway I won't rant....
P.S. Just to be verbose, when I do fastboot.exe devices... just hangs saying waiting for device. Device shows up in Device Manager but is code 31 cannot start. Also if I hold search and plug in USB or any of those combos I absolutely cannot get a blue light. I can also assure anyone that I've spent probably 8 hours straight googling the bleep out of this issue and working on it so I'm not being lazy I've just reached the limits of what I can do on my own and am begging for any help that is available!
Thanks in advance!
Also just more info, I've got the devices rooted if that makes anything simpler or opens up options. I'm also wondering if this might be a driver issue because I was doing this on my windows 8 machine and from 7 up you have to do a bunch of stupid temporary system configurations to allow unsigned drivers plus wondering if it's a driver incompatibility issue. If that's the case can I use flashtool on my linux machine? Something I'll look in to... just wanted to post as much info as I can. Thanks again!
So no one in this forum has any idea?
No one here has absolutely any idea about what I can or can't do with this bootloader situation? Wow....
You dont have fastboot thats why but you can flash. Ftf custom kernels
Sent from my LT28i using xda app-developers app
psxpetey said:
You dont have fastboot thats why but you can flash. Ftf custom kernels
Sent from my LT28i using xda app-developers app
Click to expand...
Click to collapse
Pardon my ignorance.... but you mean I can flash a custom kernel on my rogers r800a that will have fastboot? I'm asking basically because theres a working jellybean rom it but without fastboot I can't use flashtool to flash this custom rom. I'm a bit of a noob sorry and I ought not to be with what I do for a living. lol
Furinax said:
Pardon my ignorance.... but you mean I can flash a custom kernel on my rogers r800a that will have fastboot? I'm asking basically because theres a working jellybean rom it but without fastboot I can't use flashtool to flash this custom rom. I'm a bit of a noob sorry and I ought not to be with what I do for a living. lol
Click to expand...
Click to collapse
When you do test point unlock you don't get fast boot you have to use flash mode and .ft kernel and whatnot go into flash tool and press boot loader unlock it should fail and say its already unlocked
Sent from my R800i using xda app-developers app
Got it!
After much struggle.. I've got it all working and running slimbean. It's quite a huge pain in the rear to get set up so I'll post a complete guide on this thread afterward... especially considering that this thread comes up in top google search results for me when I look up "unlock bootloader R800a" and other such similar phrases.
Furinax said:
After much struggle.. I've got it all working and running slimbean. It's quite a huge pain in the rear to get set up so I'll post a complete guide on this thread afterward... especially considering that this thread comes up in top google search results for me when I look up "unlock bootloader R800a" and other such similar phrases.
Click to expand...
Click to collapse
So uh... what happened to the guide?
someguymartin said:
So uh... what happened to the guide?
Click to expand...
Click to collapse
Honestly this was almost a year ago and I ended up chucking that damn phone out and getting my wife a new one. I barely remember the whole process I just remember it being about 3-4 days of me being intensely angry and frustrated lol. I do recall it involved ripping apart the phone and shorting out certain pins that are covered by the sticker under the battery, but I believe that portion was for unlocking the sim, I really can't remember. I'll see if I can dust off those brain cells and get the whole thing back and post nfo if successful.
someguymartin said:
So uh... what happened to the guide?
Click to expand...
Click to collapse
This I used as for part of the process:
https://www.youtube.com/watch?v=zM8lWE4Layc
However I don't believe this tutorial includes unlocking the bootloader. I believe sony provides a utility or something to unlock the bootloader but you're missing fastboot. I think the process involved flashing a custom kernel, not sure. I'll keep digging into my memory and post more nfo back later. Kernel was Lupus kernel I recall that much.
Edit:
Here is complete guide with bootloader unlock process explained as well.
http://forum.xda-developers.com/showthread.php?t=2187172
More links http://unlockbootloader.sonymobile.com - but as I recall this doesn't work for rogers branded r800a.
Hello,
I have a Sony Xperia Arc S, manufactured on the 12W07, with Bootloader Unlock Allowed: No.
After almost two years with the phone and having jjdoctor's Hybrid Rom installed, phone rooted and CWM via XParts, I decided I wanted to give it a go on Jelly Bean roms.
In order to do this, I knew I had to unlock the bootloader, and after my carrier failed to reply to my e-mails and contacts, I tried to do it via WotanServer. Now, I know XDA isn't WotanServer's support forum (they don't seem to have one), but I'm hoping more of you had the same problem and can assist me in its resolution.
I registered on the site, paid the 7.99€ it's asking right now to SIM/Bootloader unlock and attempted the process on my Windows 8, x64 laptop with PC Companion and flashboot installed (I think this is important for you). I'll try to break down my questions now, so that it's easier for you to answer.
1 - When installing the X Unlock Tool 1.6.0., I noticed that it failed installing two drivers (see attached image). It only installed one of them. Is it normal?
2 - I thought this was ok and continued. I opened the program, selected my phone model, logged in and a youtube video prompted. I performed as asked, used a paper clip to make the test point stuff and my computer installed some QualComm driver (see attached image). The X Unlock Tool just stood there, frozen. What was it supposed to do?
3 - I tried some more times to perform the test point method, with no luck. The program just stucks and doesn't progress from the youtube video.
4 - "I'm going back to Xperia Ultimate HD and leave jjdoctor's rom for a while". Yeah, right. As I tried to "Reboot to Recovery" on XParts (and other SW I've tried now, like ROM Manager and ROM Toolkit), the phone reboots, stays just a tiny fraction of a microsecond on CWM and then reboots normally. I've tried all key combinations, with no luck. Maybe I killed something in my bootloader?
5 - I've already sent 3 e-mails to WotanServer, two asking for support and the last one asking for a refund. Since I can't use the SW, I want my money back. It's only 8€, but it's still my money. It's been a week now, and nobody replied. Is it normal?
If someone can help or just share a similar story for us to find a solution, I'd be happy.
Thanks.
P.S.: I am now stuck on the STOCK ICS ROM I placed on my phone via flashboot I think I'm going to try to go back to stock GB, as this is way too slow...
I don't want to contact you on gtalk, I want a solution to be publicly available here and, if you may, concrete answers to my questions.
If the driver installation failed, you will not be able to do it correctly. Do please ensure that drivers have been installed correctly.
僕のLT18iから送られてきた
You need to enable unsigned driver support in Windows 8 then reinstall the software.
Google Windows 8 driver testsigning
Sent from my LT18i using Tapatalk
Ok, I have now been able to install the drivers correctly thanks to devstaff.
However, the unlocking process keeps stopping on the "youtube video" section. It installs the Qualcomm device and just stays that way for a while (I now hold the world record in staying in the same position holding a paper clip fixed to two points).
devstaff said:
You need to enable unsigned driver support in Windows 8 then reinstall the software.
Google Windows 8 driver testsigning
Sent from my LT18i using Tapatalk
Click to expand...
Click to collapse
You have to remove the paperclip once the device is detected
Sent from my MT11i using xda app-developers app
Just did that, waited for the "Qualcomm" thing to install, removed the paper clip, kept the cable pluged, and nothing happened. I am going to try this on Windows 7.
What puzzles me the most is that the program just doesn't go anywhere. I've youtubed other videos and it's almost instant: you do the test point, it installs the driver and the program goes into the unlocking phase. Mine? It just stays there, staring back at me with the "Next" button disabled.
Try with win7 and post... Wether it worked or not
Windows 7 did the trick. Thanks everyone for your support. It now shows as sim unlocked and bootloader unlock allowed yes. Do I still have to put the codes from Sony or is it all done?
You still need the code from Sony, follow the instructions on the website.
僕のLT18iから送られてきた
rfpsebastiao said:
Windows 7 did the trick. Thanks everyone for your support. It now shows as sim unlocked and bootloader unlock allowed yes. Do I still have to put the codes from Sony or is it all done?
Click to expand...
Click to collapse
No problem, would have worked though if you just enabled test signing on Windows 8.
Sent from my LT15i using Tapatalk
---------- Post added at 06:29 PM ---------- Previous post was at 06:27 PM ----------
rfpsebastiao said:
Windows 7 did the trick. Thanks everyone for your support. It now shows as sim unlocked and bootloader unlock allowed yes. Do I still have to put the codes from Sony or is it all done?
Click to expand...
Click to collapse
No, you don't. Wotanserver removes both simlock and unlocks the bootloader for you also.
Sent from my LT15i using Tapatalk
Hmm I disabled it on Windows 8 and successfully installed the drivers, but I just couldn't get it to work. On Windows 7 I did it on my first try. Oh well, no harm done. I'll report to the people at WotanServer. They never replied, but I'll provide my feedback and link them to this thread (and I'll keep the shocking title :laugh.
Before I saw your reply I tried to perform the steps to unlock the bootloader via fastboot and Sony codes, but at the cmd I got a message stating that the bootloader was already unlocked.
I'm now enjoying Jelly Bean on my Arc S.
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