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
Related
Sorry, I know this is the arc forum, but as there is no mk16 forum, I saw that usually people post pro development's in arc's forums.
I bought an used mk16 with the 4.0.1.a.0.283 firm, and the bootloader unlockable as explained in this link the SE website.
I installed Android SDK, JDK, PC companion, etc. I was unable to install the fastboot drivers until I found someones in SE website and now it seems to be OK (blue light if I connect the phone (turned off) to the computer while holding menu key)
After that, I configured my phone to enable USB debugging. Then I installed flashtool, and I tried to root the phone with it. It worked! (I didn't expect it to work, because I saw a few post with scripts, etc. to root the phone...)
So...
- Now I am with that firmware, rooted. Wich rootable firmware do you recommend me to flash to my phone? I always loved cyanogenmod, but I don't know if there is problems with the freexperia releases (like bad quality in camera picture, low volume, etc.)
- What is the baseband? I have one ending in 49.
- What are the requirements to install clockworkmod recovery? I love this recovery to do my nand backups, etc. Do i need to unlock bootloader to this? Is there any chance to lock again the bootloader? You know, for warranty things.
- Do you have ny list of what apks are secure to erase from /system/app? For example, I don need the moxier pro, let's golf, etc.
I suppose that those questions have been answered before, but without the mk16 forum, searching that info is quite impossible...
Thanks in advance.
Search keywords: mk16 mk16i bootloader flashtool wotan
khodos said:
Sorry, I know this is the arc forum, but as there is no mk16 forum, I saw that usually people post pro development's in arc's forums.
I bought an used mk16 with the 4.0.1.a.0.283 firm, and the bootloader unlockable as explained in this link the SE website.
I installed Android SDK, JDK, PC companion, etc. I was unable to install the fastboot drivers until I found someones in SE website and now it seems to be OK (blue light if I connect the phone (turned off) to the computer while holding menu key)
After that, I configured my phone to enable USB debugging. Then I installed flashtool, and I tried to root the phone with it. It worked! (I didn't expect it to work, because I saw a few post with scripts, etc. to root the phone...)
So...
- Now I am with that firmware, rooted. Wich rootable firmware do you recommend me to flash to my phone? I always loved cyanogenmod, but I don't know if there is problems with the freexperia releases (like bad quality in camera picture, low volume, etc.)
- What is the baseband? I have one ending in 49.
- What are the requirements to install clockworkmod recovery? I love this recovery to do my nand backups, etc. Do i need to unlock bootloader to this? Is there any chance to lock again the bootloader? You know, for warranty things.
- Do you have ny list of what apks are secure to erase from /system/app? For example, I don need the moxier pro, let's golf, etc.
I suppose that those questions have been answered before, but without the mk16 forum, searching that info is quite impossible...
Thanks in advance.
Click to expand...
Click to collapse
Xperia Pro has a very few roms for now.The famous CM7 & CM9 are available for Xperia Pro.I guess,MIUI is also available(not sure).But,You must unlock your bootloader in order to install these roms.Rooted phone is not enough to install these roms.Atleast not yet. And rest assured,there is not drawback regarding camera and volume.Different users have different taste,many like it and many dont.But the fact is they are closely equal.
Basebands are well explained by a XDA member in the following post,please do take a look at it
http://forum.xda-developers.com/showthread.php?t=1462360
For CWM, you only need a rooted phone.And the easiest way to install CWM on locked-bootloader Xperia 2011 device is by using this beautiful app from the following link.Go check it out
http://forum.xda-developers.com/showthread.php?t=1437840
For relocking bootloader,i haven't come across any thread which claims to relock Xperia Pro's bootloader.But yes,relocking Xperia Arc's bootloader is poosible.You can give it a try but I'm not sure if it would work on Xperia Pro or not.Here is the link:
http://forum.xda-developers.com/showthread.php?t=1134335&highlight=relock
Here again,we have a the list of system apks with their descriptions for Xperia Arc's firmware.I assume that the Xperia Pro Has Almost the same System Apks with it so the list for Xperia Arc would also imply for Xperia Pro as well.Here is the link:
http://forum.xda-developers.com/showthread.php?t=1089470
PS: Welcome To XDA
Thank you very much for all that information and the wellcome.
I can execute commands like "fastboot.exe -i 0x0fce getvar version" or "fastboot.exe devices" while in fastboot mode, so I assume that's OK.
But in the SE website they are very insistent about voiding warranty depending of blablabla. My phone is an unlocked (SIM free) from fabric one. I understand it will void the warranty if the phone would be form Vodafone (for example), but not mine... Do you know anything about this?
Do you recommend me any official rom? maybe the .42 one?
Now I have clear everything about the baseband, thanks.
That CWM apps you linked say to me (downloades form market) that MK16i is not supported by the app
I will take a look at that APK list, but first I want to be able do a NAND backup before starting to remove apks
Thanks again.
khodos said:
Thank you very much for all that information and the wellcome.
I can execute commands like "fastboot.exe -i 0x0fce getvar version" or "fastboot.exe devices" while in fastboot mode, so I assume that's OK.
But in the SE website they are very insistent about voiding warranty depending of blablabla. My phone is an unlocked (SIM free) from fabric one. I understand it will void the warranty if the phone would be form Vodafone (for example), but not mine... Do you know anything about this?
Do you recommend me any official rom? maybe the .42 one?
Now I have clear everything about the baseband, thanks.
That CWM apps you linked say to me (downloades form market) that MK16i is not supported by the app
I will take a look at that APK list, but first I want to be able do a NAND backup before starting to remove apks
Thanks again.
Click to expand...
Click to collapse
See, Unlocked phone means the phone is SIM free,i.e you can use any carrier SIM in your phone.But, Unlocked-Bootloader is a different thing.When you unlock bootloader,then you are free to flash any ROM which is compatible with your phone.Unlocking Bootloader voids warranty and that is what the SE website is trying to say.
I would recommend you to update your phone to the official .42 fimware version because it has many new features when compared to .283 ROM.Use SE update service or PC Companion for updating your phone.
And about cwm..try this...
http://forum.xda-developers.com/showthread.php?t=1302037&highlight=cwm
Thx again
I know the diff between sim locked and bootloader looked. It's just that I don't understand why they let you unlock the bootloader, but don't keep the warranty...
I have unlocked the bootloader right now. Didn't know that it wipes all your configuration, apps, etc! At least, it's still rooted.
I have installed that CWM, and booted to it, but now I don't know what combination do I have to press to boot again into CWM XD Maybe is an image to boot just one time?
And about the ROM you recommend, PC Companion offers me the .62, not the .42. SE Update Service tells me that I have modified software (because of the rooting, I suppose) so it can't update my phone. Any idea?
Thanks again
khodos said:
Thx again
I know the diff between sim locked and bootloader looked. It's just that I don't understand why they let you unlock the bootloader, but don't keep the warranty...
I have unlocked the bootloader right now. Didn't know that it wipes all your configuration, apps, etc! At least, it's still rooted.
And about the ROM you recommend, PC Companion offers me the .62, not the .42. SE Update Service tells me that I have modified software (because of the rooting, I suppose) so it can't update my phone. Any idea?
Thanks again
Click to expand...
Click to collapse
Now that you have unlocked-bootloader, then you must not use SE update service,niether PC Companion Update nor SE OTA updates !! If you do,then it will brick your phone.
The other option you have is to flash a firmware.For more details follow this link http://www.wotanserver.com/en/sony-ericsson/se/xperia-pro-mk16/unlock-tool/debranding-flash
Thx!
I edited my previous post with this:
I have installed that CWM, and booted to it, but now I don't know what combination do I have to press to boot again into CWM XD Taking a look at the commands executed in the bat, maybe is an image to boot just one time?
Thanks about the wotan link. Really easy to flash. Now I'm in .42. Do you know where can I find the firmware changelogs?
I'll take a second look to flashtool, because I'm going to need it to flash the CM 7.2 and the baseband...
Thanks again.
khodos said:
Thx!
I edited my previous post with this:
I have installed that CWM, and booted to it, but now I don't know what combination do I have to press to boot again into CWM XD Taking a look at the commands executed in the bat, maybe is an image to boot just one time?
Thanks about the wotan link. Really easy to flash. Now I'm in .42. Do you know where can I find the firmware changelogs?
I'll take a second look to flashtool, because I'm going to need it to flash the CM 7.2 and the baseband...
Thanks again.
Click to expand...
Click to collapse
Search in this forum and you can find the changelog
Have fun.
Sent from my LT18i using XDA
QUESTION
AFTER OPENING THE BOOTLOADER
I CAN FLASH THE ROM AN OFFICIAL FTF?
PANCHOMATASANO said:
AFTER OPENING THE BOOTLOADER
I CAN FLASH THE ROM AN OFFICIAL FTF?
Click to expand...
Click to collapse
Yea sure..
---------- Post added at 01:06 PM ---------- Previous post was at 12:58 PM ----------
khodos said:
Thx!
I edited my previous post with this:
I have installed that CWM, and booted to it, but now I don't know what combination do I have to press to boot again into CWM XD Taking a look at the commands executed in the bat, maybe is an image to boot just one time?
Thanks about the wotan link. Really easy to flash. Now I'm in .42. Do you know where can I find the firmware changelogs?
I'll take a second look to flashtool, because I'm going to need it to flash the CM 7.2 and the baseband...
Thanks again.
Click to expand...
Click to collapse
Well if u wan a permantent CWM based recovery and u r using any stock or stock based ROM use this kernel.. flash it using fastboot..
http://www.mediafire.com/?m4f43973m3vxybs
PANCHOMATASANO said:
AFTER OPENING THE BOOTLOADER
I CAN FLASH THE ROM AN OFFICIAL FTF?
Click to expand...
Click to collapse
If you just need to flash an official firmware, then there is no need to unlock the bootloader. I was advised not to unlock it when not necessary (for example to flash the phone with some custom ROM like CM). Because with locked bootloader you should not be able to brick the phone and you could be always able to save the situation using Sony PC Companion.
So if you need to flash an official firmware, you can do it without any unlocking via Wotanserver. The firmware flashing is free, just register there. The flashing is very easy - there is a graphic wizard which tells you what to do.
EDIT: Ooops, flashing FW using Wotanserver is no longer free - costs 2 EUR now. Few weeks ago I flashed my phone there for free...
OK so we got a SE Experia Arc S LT18i with 1253-8238_4.0.1.A.0.165 ('prototype' model on loan from a friend = prehistoric!) and looking into upgrading the thing if at all possible.
So if I am correct it's a case of: 1st: Root, 2nd: Unlock bootloader, 3rd: Install recovery, 4th: Flash ROM of choice
Bootloader is locked and phone not rooted.
Tried using Flashtool to root phone but it is greyed out so tried Tools > Root > Force zergRush = fail, (not tried Force psneuter/Emulator ?)
Tried unlocking bootloader using Flashtool, but this also failed (SE unlock website wanted IMEI code one digit less than the phone reports?!! got a code by ditching the first 0 of the IMEI, but didn't work anyway - crashed phone)
Attempted to root using command line ADB method to push zergRush and execute the script, but this too doesn't work (phone crashes and reboots).
Fastboot? I have it installed but not yet come across any how-to's that use this (did I say yet? )
The apps available on Play Store seem to be automations of above methods for one-click users.
Further exhaustive reading/searching here and on talk.sonymobile.com leads me to believe that the first step might be to flash a different kernel version before it's possible to root, after which everything else should fall into place...I'm up for trying this but of course don't want to risk bricking the phone, so backing up first would be a good plan, *but* I need root to be able to install recovery! I know enough about booting operating systems to know that changing kernel version with a locked boot loader might just result in bork! This is where the expertise of you guys comes in!! Maybe you know that flashing another (similar?) kernel will be fine with Fashtool even without unlocking bootloader and rooting phone? Perhaps I missed a simple and easy way of rooting? Any suggestions very welcome - thanks in advance!
FYI: *I only run Linux* so pointing me at any of the windows tools on offer is of no help to me
Oh and PS: yes I have searched and found a ton of helpful info, well actually *way too much* info to the point of saturation and confusion!! :laugh:
There can never be too much information, yours and others problem is that you try rushing through it, because if you didn't you'd find the answers you were looking for.
Sent from my CM9'd Arc
XperienceD said:
There can never be too much information, yours and others problem is that you try rushing through it, because if you didn't you'd find the answers you were looking for.
Sent from my CM9'd Arc
Click to expand...
Click to collapse
Well it's not the quantity of info, but the quality of info! Failing that the filtration system used to distill the good stuff out!
Anyroads, I was still hoping for someone to chip in with something like "Yeah go for it, that will work fine"! or "Don't do it, try this instead"!
I'm believing from my readings so far, that short of flashing an incorrect radio, or interrupting a flash process, it isn't easily possible to brick an Arc?
acesabe said:
Anyroads, I was still hoping for someone to chip in with something like "Yeah go for it, that will work fine"!
Click to expand...
Click to collapse
I would have just tried it instead of starting a thread to ask, failing that I would have then read the stickys/guides explaining how to unlock and root.
acesabe said:
it isn't easily possible to brick an Arc?
Click to expand...
Click to collapse
No, you would just use the flashtool to flash a stock ROM.
XperienceD said:
I would have just tried it instead of starting a thread to ask, failing that I would have then read the stickys/guides explaining how to unlock and root.
Click to expand...
Click to collapse
Well, that's because you are XperienceD!
No, you would just use the flashtool to flash a stock ROM.
Click to expand...
Click to collapse
Ok cool, so Flashtool can be used to save an unbootable device too then...
acesabe said:
Well, that's because you are XperienceD!
Click to expand...
Click to collapse
It's how I got to be experienced. :silly:
acesabe said:
Ok cool, so Flashtool can be used to save an unbootable device too then...
Click to expand...
Click to collapse
Yep, you just need to flash a stock ROM.
XperienceD said:
I would have just tried it instead of starting a thread to ask, failing that I would have then read the stickys/guides explaining how to unlock and root.
Click to expand...
Click to collapse
Me too.
Thread closed.
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.
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...
So after a year and half with this phone, I thought about installing a better ROM.
I experience with these kind of things from the time I had the galaxy 1 and I changed tons of ROMs on that.
But the xperia seems a bit different with ROM changing.
What are some basic things I need to know, and where can I find the stock ROM (just in case)?
If this isn't the correct to forum for this post, please notify me.
ROM changing ist not very different from Samsung...
If your bootloader is unlocked and your CWM is working, then you can install all Roms as ZIP like on the Galaxy
Always make an Backup with CWM to be save and get back in case of errors, thereforce i didn't need a the stock ROM
Just have a look here on the last pages
http://forum.xda-developers.com/showthread.php?t=1876890&page=324
Targunitoth said:
ROM changing ist not very different from Samsung...
If your bootloader is unlocked and your CWM is working, then you can install all Roms as ZIP like on the Galaxy
Always make an Backup with CWM to be save and get back in case of errors, thereforce i didn't need a the stock ROM
Just have a look here on the last pages
http://forum.xda-developers.com/showthread.php?t=1876890&page=324
Click to expand...
Click to collapse
thanks! But what I meant is that with my sgs I didn't need to open the bootloader and install CWM since it was already there.
How do I unlock the bootloader and install CWM, should I root it first?
Just have a closer look to the link mentioned above.
I postet there a link to a Guide, how to flash a custom rom (including unlocking Bootloader)
and Mirhawk gave aditional tipps
Have you bought your sgs secondhand?
Because you have to install CWM one time on your sgs, too.
And it is a similar effort to flash sgs with odin then unlocking your bootloader on the xperia S
Targunitoth said:
Just have a closer look to the link mentioned above.
I postet there a link to a Guide, how to flash a custom rom (including unlocking Bootloader)
and Mirhawk gave aditional tipps
Have you bought your sgs secondhand?
Because you have to install CWM one time on your sgs, too.
And it is a similar effort to flash sgs with odin then unlocking your bootloader on the xperia S
Click to expand...
Click to collapse
I always get stuck at rooting. the software runs, and after I do everything it gives me "Error 3" and runs forerver. Any idea?
Error type 3
Error: Activity class {com.sonyericsson.vendor.backuprestore/com.sonyericsson.ve
ndor.backuprestore.ui.BackupActivity} does not exist.
Click to expand...
Click to collapse
Not really
But i can google it for you:
http://forum.xda-developers.com/showpost.php?p=34035358&postcount=88
Edit:
which leads you here: http://forum.xda-developers.com/showthread.php?t=1898240
Targunitoth said:
Not really
But i can google it for you:
http://forum.xda-developers.com/showpost.php?p=34035358&postcount=88
Click to expand...
Click to collapse
I already have that Backup and restore app.
Anyone else?
You also have this one?
http://forum.xda-developers.com/showthread.php?t=1898240
Edit: There is another version in this thread, maybe test this...
Else I can't help you
Targunitoth said:
Not really
But i can google it for you:
http://forum.xda-developers.com/showpost.php?p=34035358&postcount=88
Edit:
which leads you here: http://forum.xda-developers.com/showthread.php?t=1898240
Click to expand...
Click to collapse
Targunitoth said:
You also have this one?
http://forum.xda-developers.com/showthread.php?t=1898240
Edit: There is another version in this thread, maybe test this...
Else I can't help you
Click to expand...
Click to collapse
Nothing works I'll wait for someone else. Thanks for the effort!
Install ROM's in Xperia S is not difficult.
You must have Rooted your phone and Install CWM (like the comment above)
I was like you when I decided flash ROMs.
I recommend you see if your bootloader is open or not (when you verificate it, you will see in the screen of your phone BOOTLOADER UNLOCK, and then YES or NO. bootloader is easy to open when you have YES, but when it's in not is a bit complicated)
To put the BOOTLOADER UNLOCK in YES, first: you have to have your phone free (your phone have to be available to use with others companies) in my case, for example, i dont have my phone free, but to liberate it with my company, give mea code and after that I introduce it and set free the phone. (after that you will allow to open BOOTLOADER)
Here in XDA have 2 types of ROMS, to LOCK and UNLOCK bootloader, I am using TrinityVengance RaptorXL by f(x)THaxxorX, before that I used, LeopardX 5.0 by savergigio
To flash ROMs you use ClockWorldMOd, its very easy, if you need more help tell me
Milton_Mitnick said:
Install ROM's in Xperia S is not difficult.
You must have Rooted your phone and Install CWM (like the comment above)
I was like you when I decided flash ROMs.
I recommend you see if your bootloader is open or not (when you verificate it, you will see in the screen of your phone BOOTLOADER UNLOCK, and then YES or NO. bootloader is easy to open when you have YES, but when it's in not is a bit complicated)
To put the BOOTLOADER UNLOCK in YES, first: you have to have your phone free (your phone have to be available to use with others companies) in my case, for example, i dont have my phone free, but to liberate it with my company, give mea code and after that I introduce it and set free the phone. (after that you will allow to open BOOTLOADER)
Here in XDA have 2 types of ROMS, to LOCK and UNLOCK bootloader, I am using TrinityVengance RaptorXL by f(x)THaxxorX, before that I used, LeopardX 5.0 by savergigio
To flash ROMs you use ClockWorldMOd, its very easy, if you need more help tell me
Click to expand...
Click to collapse
Thanks, but I know all that, problem is- it doesn't work. Please look above.
how to
check if my bootloader unlock?