Re-Unlock Bootloader - Atrix 4G Q&A, Help & Troubleshooting

I recently unlocked my phone and rooted, I tried to flash CM7 Beta everything went well except when i rebooted it got stuck at the dual core screen. After trying everything, I decided to flash back to stock since cm7 wouldn't boot. My question is now that I flashed back to stock do I need to re-unlock my device? Does it stay unlocked? Can I just root it and retry CM7 again?

it happens to me too im reading on the forum but i dont think the bootloaders remain unlock cuz when u do the process it say that in the warnings

No one knows?
I read that once you unlocked you are unlocked forever because when you unlock it kills a fuse but you can cover up the 'unlocked' message so the average joe (such as ATT or Best Buy employee) wouldn't know you unlocked for insurance purposes.
I've also read posts though, like you, that state that it does re-lock the bootloader, so I am confused! I dont want to try flashing again though and end up with a hard-brick!

only installing official roms after unlocking will re-lock your phone or brick it. so if you can no longer see 'unlocked' when you turn your phone on then you will need to re-unlock the bootloader.
before installing any custom roms you need to do a backup. after that, do a full wipe/factory reset, wipe cache & wipe dalvik cache. then install your custom rom, reboot, wait anything up to 10 minutes, and voila!
theres no 'fuse' that needs blowing to unlock the phone, by the way. its all software based, and it can be re-locked providing that there is freely available software that allows you to do so!
Sent from my MB860 using XDA App

konna280 said:
only installing official roms after unlocking will re-lock your phone or brick it. so if you can no longer see 'unlocked' when you turn your phone on then you will need to re-unlock the bootloader.
theres no 'fuse' that needs blowing to unlock the phone, by the way. its all software based, and it can be re-locked providing that there is freely available software that allows you to do so!
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Might want to do some reading and research. This has all been discussed previously in a couple of threads with links supporting a hardware unlock. Nobody has provided any proof of a software only unlock as of yet. Would appreciate if you posted where you got your information.
Cheers!

konna280 said:
only installing official roms after unlocking will re-lock your phone or brick it. so if you can no longer see 'unlocked' when you turn your phone on then you will need to re-unlock the bootloader.
before installing any custom roms you need to do a backup. after that, do a full wipe/factory reset, wipe cache & wipe dalvik cache. then install your custom rom, reboot, wait anything up to 10 minutes, and voila!
theres no 'fuse' that needs blowing to unlock the phone, by the way. its all software based, and it can be re-locked providing that there is freely available software that allows you to do so!
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
+1
Can you provide a link that this is indeed a software lock?...
Sent from my GT-I9000 using xda premium

CaelanT said:
Might want to do some reading and research. This has all been discussed previously in a couple of threads with links supporting a hardware unlock. Nobody has provided any proof of a software only unlock as of yet. Would appreciate if you posted where you got your information.
Cheers!
Click to expand...
Click to collapse
Sorry, when i say software based i mean the use of software (using programs to flash files) to modify hardware. hardware based unlocking would mean having to modify hardware, such as soldering or other means of modifying/replacing components.

konna280 said:
Sorry, when i say software based i mean the use of software (using programs to flash files) to modify hardware. hardware based unlocking would mean having to modify hardware, such as soldering or other means of modifying/replacing components.
Click to expand...
Click to collapse
Soo..
You start a new thread about a topic that already has 17 threads dedicated to it.
You clearly dont understand how the current unlocking process works.
You claim to know of a new sw unlock, but even after being asked a few times will not elaborate or give a link or other info about it.
And your making up your own terms depending on what makes sence to you.
That settles it. You win the lolthread of the day, and were not laughing with you.

let's simplify:
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
This unlocks the bootloader through the use of software, does it not?
http://tinyurl.com/6gwycaq (explains what a bootloader is)
Plus... I didn't start the thread. You might need to do a little reading on that.
I've clearly unlocked, rooted, and installed a new ROM on my atrix (i initially used the gingerbreak app to root it, but decided to change the ROM at a later date, so unlocked it fully)
I don't claim to know of a sw unlock. I merely stated that software is used (RSD lite, drivers etc) to carry out the unlocking procedure.
Oh, by the way, it's "WE'RE not laughing with you" (not very nice ) and "YOU'RE making up your own terms". Little bit of research for you, if you want

konna280 said:
...
theres no 'fuse' that needs blowing to unlock the phone, by the way. its all software based, and it can be re-locked providing that there is freely available software that allows you to do so!
...
Click to expand...
Click to collapse
I think you're mistaken, it's a hardware lock. There has not been a software only solution shown. Since I have gone through the steps you described, and then re-unlocked my bootloader, the two processes were different (unlocking vs. re-unlocking), meaning that something changed when I unlocked the bootloader.
http://en.wikipedia.org/wiki/Antifuse#Antifuses_in_integrated_circuits
Trust me, this stuff is in all the ICs that you use.

Ok then, i apologize for not doing my research
I just ASS-U-MEd that if it can be re-locked then there is no modification taking place to the hardware itself (such as blown fuses - I'll admit though I only recently heard about eFuse's/Antifuse's as I've never dealt with them before, and therefore didn't know that the Atrix had them)
Thanks for the info.

lockety lock lock lock Lmfao

Im still laughing. No apostraphes needed.

WiredPirate said:
Im still laughing. No apostraphes needed.
Click to expand...
Click to collapse
nvm lol
10char

reunlocking is the same presedure which you did before. just you dont need to do the fastboot unlock oem.i did it and reunlock 2.3.4 telstra

Related

Im scared to unlock bootloader again. Second attempt?

So guys I really wanna unlock the bootloader and flash some roms but this is my third atrix. Im using the 14 day grace period very very graciously. Anyways first atrix kept locking up- exchanged. Second one I tried to unlock it with pudding. Did the rsd thing with the. Sbf file and I was doing it. Then toward the end it failed. Complete brick- exchanged.
Anyways is there something else I should do, possibly a different route? Im using an AT&T atrix. Thanks.
Wait for official release and get it officially unlocked?
Sent from my MB860 using XDA Premium App
tsouza said:
Wait for official release and get it officially unlocked?
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
I can wait for the release, but are they unlocking it with it. For sure?
Well, IMO better hope for it than risk another brick...
Sent from my MB860 using XDA Premium App
tsouza said:
Well, IMO better hope for it than risk another brick...
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
True. Very true.
magicriggs said:
So guys I really wanna unlock the bootloader and flash some roms but this is my third atrix. Im using the 14 day grace period very very graciously. Anyways first atrix kept locking up- exchanged. Second one I tried to unlock it with pudding. Did the rsd thing with the. Sbf file and I was doing it. Then toward the end it failed. Complete brick- exchanged.
Anyways is there something else I should do, possibly a different route? Im using an AT&T atrix. Thanks.
Click to expand...
Click to collapse
I think you might have returned the first 2 prematurely.
1st one probably could have factory reset or flashed a new sbf
2nd one was probably a fixable soft brick.
So I'd say you're safe, but up to you as there's always a risk.
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
2. Flash pudding only SBF so you can unlock the bootloader. http://diamantephoto.com/fastboot.rar direct link. Flash this one.
http://forum.xda-developers.com/showthread.php?t=1136261 Original Post about pudding.
It will go to a text only 14 option screen and say something like boot failed 0x1000. Don't freak out and tell me you bricked you phone blah blah blah. You still have to unlock the bootloader by choosing fastboot from your phone and connecting it to the computer via usb. Make sure you have ADB with fastboot tools installed on you computer.
Open command prompt from you computer and type fastboot oem unlock. It'll display warning about voiding warranty and a unique device id. Type again fastboot oem unlock ############. The # are the unique device numbers. Don't type # it wont work. The instructions are posted on the pudding thread if you would like to read more about it.
Then type fastboot reboot to reboot. Unlock should be displayed on top left of screen and it'll take 5 long mins to boot up.
3.Then you need to install CWM and root.
You'll find instructions in the developers form. But if your lazy here is the CWM link. http://forum.xda-developers.com/showthread.php?t=1138541 follow the instructions or every time you reboot you will loose CWM. For root there are two available for gingerbread. http://forum.xda-developers.com/show....php?t=1140110 I used this one and got root.
http://forum.xda-developers.com/show....php?t=1138204 I hear this works too.. Haven't tested read the post if you want to use this method.
As always don't blame me for bricking if you happen to do so. DO IT AT YOUR OWN RISK. these are the steps I took to unlock and everything works great. Absolutely no problems with my phone after wards.
One thing unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything with titanium or you favorite app. I would not restore system apps as i've had a few problems with email and motoblur force closes.
Sent from my MB860 using Tapatalk
magicriggs said:
I can wait for the release, but are they unlocking it with it. For sure?
Click to expand...
Click to collapse
not sure. i got a leaked 4.5.91 build, it's not unlocked (although early beta does). you still have to flash the pudding img yourself.
delect this post
The returns were genuine. I did a factory reset on the first one and it still kept locking up, on the wake up. Had to pull battery out to turn back on. Multiple times. Second one was a complete brick. I couldn't get into rsd, wouldn't turn on and computer didn't recognize it in any mode. Im pretty familiar with rsd, used it with OG and X but this one got me walking om egg shells.
magicriggs said:
The returns were genuine. I did a factory reset on the first one and it still kept locking up, on the wake up. Had to pull battery out to turn back on. Multiple times. Second one was a complete brick. I couldn't get into rsd, wouldn't turn on and computer didn't recognize it in any mode. Im pretty familiar with rsd, used it with OG and X but this one got me walking om egg shells.
Click to expand...
Click to collapse
hmm you are very unlucky then. You're the only one to hard brick from pudding. Probably advise you not to do anything with your phone.
Jnewell05 said:
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
Click to expand...
Click to collapse
im on build number 4_1.8.3 and i check for updates and it says my device is up to date. any
ideas?
magicriggs said:
im on build number 4_1.8.3 and i check for updates and it says my device is up to date. any
ideas?
Click to expand...
Click to collapse
4.1.83 is a great point to unlock the bootloader. DO NOT install the 4.5.91 OTA udpate, too risky to hard brick if you flashed an sbf. Of course, you don't have to sbf back anymore, but I would steer way clear of that when there are perfectly good options available. Only use customized ones like Kenneth's or the CherryBlur ROM. More will start flowing soon.
So what your advising is not to even unlock it. All I really want is volume wake.
magicriggs said:
So what your advising is not to even unlock it. All I really want is volume wake.
Click to expand...
Click to collapse
That's the exact opposite of what I'm advising. I knew I was taking some level of risk when I unlocked, but it's a risk well worth taking. Very, very low failure rate. Recoverable. But I can't accept the risk for your phone.
OSNPA said:
That's the exact opposite of what I'm advising. I knew I was taking some level of risk when I unlocked, but it's a risk well worth taking. Very, very low failure rate. Recoverable. But I can't accept the risk for your phone.
Click to expand...
Click to collapse
Oh gotcha. Thanks for the info.
Jnewell05 said:
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
2. Flash pudding only SBF so you can unlock the bootloader. http://diamantephoto.com/fastboot.rar direct link. Flash this one.
http://forum.xda-developers.com/showthread.php?t=1136261 Original Post about pudding.
It will go to a text only 14 option screen and say something like boot failed 0x1000. Don't freak out and tell me you bricked you phone blah blah blah. You still have to unlock the bootloader by choosing fastboot from your phone and connecting it to the computer via usb. Make sure you have ADB with fastboot tools installed on you computer.
Open command prompt from you computer and type fastboot oem unlock. It'll display warning about voiding warranty and a unique device id. Type again fastboot oem unlock ############. The # are the unique device numbers. Don't type # it wont work. The instructions are posted on the pudding thread if you would like to read more about it.
Then type fastboot reboot to reboot. Unlock should be displayed on top left of screen and it'll take 5 long mins to boot up.
3.Then you need to install CWM and root.
You'll find instructions in the developers form. But if your lazy here is the CWM link. http://forum.xda-developers.com/showthread.php?t=1138541 follow the instructions or every time you reboot you will loose CWM. For root there are two available for gingerbread. http://forum.xda-developers.com/show....php?t=1140110 I used this one and got root.
http://forum.xda-developers.com/show....php?t=1138204 I hear this works too.. Haven't tested read the post if you want to use this method.
As always don't blame me for bricking if you happen to do so. DO IT AT YOUR OWN RISK. these are the steps I took to unlock and everything works great. Absolutely no problems with my phone after wards.
One thing unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything with titanium or you favorite app. I would not restore system apps as i've had a few problems with email and motoblur force closes.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
i used update.zip ..did not flash back to 1.83...update.zip (blur 1.83 etc etc) was from leaked moto servers...i have new bootloader cause my andriod recovery is different...of course BL is locked....can i still unlock??

HTCdev.com **Evo3D Rooting Info** "Live"

Well at last, HTC has brought us their method to root HTC Evo 3D & Sensation.. Just register to become a member (dev) and begin rooting your Evo3D. I wanted to show you all what to expect.. and of course there are disclaimers so view screen shots for full details. I have not tried this setup so please give feedback, I do have the phone but it's been rooted by other methods.. just giving fellowship & sharing information. Enjoy!
Go to HTCDev.com to get started.. (This will VOID your warranty, root your phone & give you super human strenghts)
Previous rooting gave phone's the same voided warranty especially servicing in carriers service center, same deal. Revolutionary method also voids warranty so now people have choices.. (Former Sprint Service Mgr)
As informed please give useful feedback if you have used this method so we know where we stand with this and in fact "IF" HTC is helping us out.
Thx to Doomstang for input-
Doomstang said:
Well I think I've finally gotten somewhere...Wireless Tether was just successfully granted Superuser permissions.
This was all done without ever having rooted this phone in the past...so I accepted the OTA update, unlocked with HTC Dev's process, got a working recovery going, and then got Superuser installed.
graffixnyc posted the link to the working recovery so I used that: http://www.multiupload.com/AQ9KV7IME9
Click to expand...
Click to collapse
And Graffixnyc-
graffixnyc said:
This was the version of CWM that booted for me. I flashed through fastboot and also did a nandroid restore just fine. This was the version IEF(from alpharev) gave me on irc
http://www.multiupload.com/AQ9KV7IME9
I was able to get into recovery from selecting recovery from the fastboot method and from doing adb reboot recovery. Sorry for not posting earlier I had finals yesterday and went out after to celebrate
http://www.multiupload.com/AQ9KV7IME9
Click to expand...
Click to collapse
Please make sure all items are installed and up to date.
Google Android SDK zip:
http://developer.android.com/sdk/index.html
Java Runtime Environment:
http://java.com
HTC Sync (Windows Only):
http://www.htc.com/www/help/
Continued "disclosure"
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty. Please note that unlocking your bootloader does not mean that you will be able to unlock the SIM lock. Unlocking your SIM lock is at the discretion of your operator/carrier and is not part of the bootloader unlocking scope.
Our devices have been designed with our hardware and software specifications in mind and unlocking the bootloader will change the software and may cause unexpected side effects. It is impossible for HTC to ensure the proper functioning of your device after this. In the worst case scenario, it is possible that your device may be physically damaged due to overheating or the behavior of your device might be altered including, but not limited to, hearing aid compatibility (HAC) and specific absorption rate (SAR) values.
Some content on your device may also be invalidated and cannot be accessed any more because of invalid DRM security keys. This includes content that you may have purchased through a 3rd party vendor and through HTC. Furthermore, although you will still be able to receive updates to your device via FOTA (“firmware over the air”), we do not guarantee that updating your device via FOTA will not render your device unusable. Please understand that you will not be able to return your device to the original state and going forward your device may not be held covered under the warranty for all claims resulting from the unlocking of the bootloader. HTC bears no responsibility if your device is no longer usable afterwards.
HTC is committed to assisting customers in unlocking bootloaders for HTC devices. However, due to some of our carrier customers concerns, certain models with specific restrictions may not be able to be unlocked. Please refer to our list of supported devices to see if your device is eligible for unlocking the bootloader.
We strongly suggest that you do not unlock the bootloader unless you are confident that you understand the risks involved. This is a technical procedure and the side effects could possibly necessitate repairs to your device not covered under warranty. If you are still interested in unlocking the bootloader, and you understand the consequences both to your device and to your warranty, then you may refer to the following pages where we have provided the unlocking instructions.
If there's an error you will see screen shot below.. with details on what happened.
So maybe I'm confused about what this does ... I went through the process and everything seems to have worked. Bootloader now shows unlocked. I tried to flash a recovery (both clockworkmod and TWRP) and it seems to flash successfully but when I try to run recovery it just reboots the phone after showing the HTC logo for a minute. I was hoping to install the rooted OTA but not sure what to try next...
nabbed said:
No. I'm not confused about the unlock.
I'm worried about a man who makes a guide about unlocking the device he does not have...
Am I wrong to be worried, about a man, who makes a post, about unlocking a device, he does not have?
Has has tested the method?
Click to expand...
Click to collapse
Yooooo. Godzson is a trusted guy and helps many devs in the community. No sense in flamming him when you'll just start pissing off devs here.
Sent from my PG86100 using Tapatalk
Godzson is a trusted member on here. Don't think you have to worry about him. Why would someone take all this time to write up a post with pics and the info just to mess with people? Smh....... Alot of the devs in the 3d community who do roms and themes don't even have the damn 3d. Don't start turning this community into **** by questioning people trying to help.
gthing said:
So maybe I'm confused about what this does ... I went through the process and everything seems to have worked. Bootloader now shows unlocked. I tried to flash a recovery (both clockworkmod and TWRP) and it seems to flash successfully but when I try to run recovery it just reboots the phone after showing the HTC logo for a minute. I was hoping to install the rooted OTA but not sure what to try next...
Click to expand...
Click to collapse
TWRP doesn't work and CWM Is a hit or miss. You should of tried the stock recovery, I think it had one. Wait till a root for the new boot loader I say.
I think the unlocked just gives partial access to the bootloader if I am correct. Your security flag(s-off) is still on.
Sent from my EVO3D(overclocked) via XDA App
Godzson is only posting to what HTC promised, here a unlocker. He is also a trusted member, who provides a substantial amount of information for the community. Please they are also right to say some dev, and do not have this device and do an amazing job developing for it. let's please keep peaceand move forward..
Why waste your time reposting instructions found on htcdev.com? People want to know what happens after you do the method and how it helps put custom software on your phone.
mwalt2 said:
Why waste your time reposting instructions found on htcdev.com? People want to know what happens after you do the method and how it helps put custom software on your phone.
Click to expand...
Click to collapse
Because sometimes people want to see the process without having to DO the process....
Why question it? Just don't read through 2 pages or more of posts if it's offensive to you.
Yo GODZSON, you do know that the little green android guy isn't the only one that's green around here, don't you? LMFAO. Just look at the noobs trying to flame you, and don't even know anything about you, LOL. Yeah, LOL. Like they got room to talk. Keep up the great work buddy.
On a more serious note, does this method actually allow you to root? Cuz I didn't really see anything on HTC's site, or in your post about rooting. Yet the title states rooting with HTC's unlock method. Just a fyi.
Sent from my PG86100 using XDA Premium App
Well sir maybe doing a lil research would benefit the questions. I did assist with 2 threads in Evo3D (screen pics and 3D converting). I placed this for information to the community and for knowledge to those that may want to see what it looks like and have other options of rooting their phone. I do have the device but's its been rooted therefore I havent tried this "Official" method. Would be nice to ask with some manners in XDA you can get suspended, banned, etc for your actions, this is a community to help each other out.
Thanks to all the fellow dev's for the kind words.. to all the noobs with lack of knowledge no worries we're here for you to help out, much love for you.. hey we all started there at one time
Well I think I've finally gotten somewhere...Wireless Tether was just successfully granted Superuser permissions.
This was all done without ever having rooted this phone in the past...so I accepted the OTA update, unlocked with HTC Dev's process, got a working recovery going, and then got Superuser installed.
graffixnyc posted the link to the working recovery so I used that: http://www.multiupload.com/AQ9KV7IME9
this is a joke!
HTC's unlocked bootloader is a joke, it just says "unlocked" but you cannot flash any new recoveries and you get S-ON. Don't try this folks, stay rooted! My 3D is now officially bricked with HTC method, it's not unlocked at all as you can't do anything with it.
zedomax said:
HTC's unlocked bootloader is a joke, it just says "unlocked" but you cannot flash any new recoveries and you get S-ON. Don't try this folks, stay rooted! My 3D is now officially bricked with HTC method, it's not unlocked at all as you can't do anything with it.
Click to expand...
Click to collapse
I'm very sorry to hear yours was bricked but I was able to flash a working recovery (although the first 2 I tried did fail) and gain SU permissions even with S-ON still showing.
thnx
Doomstang said:
I'm very sorry to hear yours was bricked but I was able to flash a working recovery (although the first 2 I tried did fail) and gain SU permissions.
Click to expand...
Click to collapse
Thanks I actually saw your post and trying that now! We will have ROOT!
It does look like things are working for some starting here in one of the other threads.
Great write up
Lol, sorry HTC. We beat you to it.
Sent from my EVO 3D using XDA Premium App
The unlock is terrible, I got it to work on my Dad's phone, but I could only get into clockwork once, TWRP doesn't work, and only a manual flash of clockwork seemed to work, I tried to get in with Rom Manager for him so he could do a backup, and it wouldn't go either, and it didn't want to go back in for me manually either, just boots up.
Oh well, I managed to root it and get a rom installed. So we shall see how everything goes.
It's S-ON still, which is complete crap.
nfollin said:
The unlock is terrible, I got it to work on my Dad's phone, but I could only get into clockwork once, TWRP doesn't work, and only a manual flash of clockwork seemed to work, I tried to get in with Rom Manager for him so he could do a backup, and it wouldn't go either, and it didn't want to go back in for me manually either, just boots up.
Oh well, I managed to root it and get a rom installed. So we shall see how everything goes.
It's S-ON still, which is complete crap.
Click to expand...
Click to collapse
4.0.1.5 failed for me too.
I started with CWM 4.0.1.4.
I clicked update recovery in ROM Manager and it said 4.0.1.5 successfully installed after I granted it SU permissions. Had it reboot into recovery from ROM manager and the phone just restarted...so I manually went to recovery via HBoot and it fails to load and restarts the phone. I guess I'll push that 4.0.1.4 back to it now.
so the bootloader gets unlocked but yet it stays S-on? wtf lol ?

Does Unlock after Relock Still Wipe?

I have not yet taken the plunge to unlock my runs-hot Rezound, but I had a question brought on by seeing how prolific Nils is with his releases.
I know the initial unlock wipes the phone. I also know that you cannot run a RUU to save your butt in an emergency if your phone is unlocked. From this, it makes sense to unlock, flash your rom, relock. If you have an emergency, you can RUU, and that is probably a real good way to be.
But this leaves me wondering ... anyone know if a subsequent unlock from a re-lock wipes the phone as well (because THAT would be a pain if you wanted to update a ROM).
Thanks!
jdmba said:
I have not yet taken the plunge to unlock my runs-hot Rezound, but I had a question brought on by seeing how prolific Nils is with his releases.
I know the initial unlock wipes the phone. I also know that you cannot run a RUU to save your butt in an emergency if your phone is unlocked. From this, it makes sense to unlock, flash your rom, relock. If you have an emergency, you can RUU, and that is probably a real good way to be.
But this leaves me wondering ... anyone know if a subsequent unlock from a re-lock wipes the phone as well (because THAT would be a pain if you wanted to update a ROM).
Thanks!
Click to expand...
Click to collapse
1. I think you can RUU with unlock.
2. Yes. You would have to wipe.
Thanks!
dmeadows013 said:
1. I think you can RUU with unlock.
Click to expand...
Click to collapse
Thanks for the answer! I guess its a tough decision to have to make because I am 99.9999999999999999999999999999% sure (from reading XDA very carefully and constantly) that you CANNOT run a RUU (from a PC) if your phone is in the unlocked state; meaning if you really bork it, you are stuck if you left it unlocked.
jdmba said:
Thanks for the answer! I guess its a tough decision to have to make because I am 99.9999999999999999999999999999% sure (from reading XDA very carefully and constantly) that you CANNOT run a RUU (from a PC) if your phone is in the unlocked state; meaning if you really bork it, you are stuck if you left it unlocked.
Click to expand...
Click to collapse
Ah. You should be able to flash the HBOOT RUU with unlock. They are posted in my Root Thread in Development

[Q] SK17a - SIM unlock, ICS, Bootloader Unlock

Hi all,
I've read a couple of stickies, and been through quite a bit of threads here at XDA, and I still can't find my answer. I hope that this is the right place for questions, if not, please excuse my ignorance and move it to the correct forum.
Here's my problem:
I have an Xperia Mini Pro (SK17a), locked to Rogers. It's one of the phone models that don't have the ICS upgrade. Perhaps I can blame that on Rogers, but then again, I can blame a lot of things on Rogers. I've been waiting for the ICS upgrade for quite a while, and now I'm just going to take this into my own hands and install a custom rom.
My understanding of this is that unlocking the bootloader will make my life much easier, and it's what I intend to do. The thing is, I'm SIM-locked to that god-awful company Rogers. From my 'research', I've read a bunch of stories and stuff, but nothing that gives me a definite answer. Do I have to have my phone SIM-unlocked to unlock my bootloader? (For either the official SE unlocking service and Test Point method). Will SIM-Unlocking also sever any bonds that connect my phone to Rogers? If that's the case, then I might just be able to update via PC Companion, which I can settle for if it takes less work than unlocking the bootloader.
My efforts in trying to update via FlashTool (and the official ICS .ftf) were futile, resulting in Flashtool giving me an unsatisfactory "ERROR- Error flashing. Aborted", which I think may be because my bootloader is locked, or I'm SIM-locked to Rogers.
(Using the latest version of flashtool)
Currently, my phone is running the latest stock Gingerbread, with root and CWM.
This ties in nicely to my next question, regarding Recoverys.
When I read the thread pertaining to CWM on the Mini Pro, it said that it should only be installed on a stock rom. Would this mean that CWM isn't used with custom roms? I find this to be stupid, as then you wouldn't be able to access the Recovery menu when **** actually turns bad, and you've got to flash a stable rom in a pinch.
That's all for now, thanks in advance.
-Dillon
P.S.
I'm not too much of a noob, so I can understand all of this crazy Android lingo; I've rooted/installed custom roms on my fair share of devices. On the other hand, I'm no pro either.
I know that bumping is generally frowned upon, but I'm doing it in hopes that perhaps somebody that could answer my questions just missed my thread.
Again, my apologies.
Sent from my Kindle Fire using xda app-developers app
Same problem
Man I have the exacttt same problem and doubt as you do, specially about the SIM LOCK, I want ICS on my phone too, I have the same model. Have you gotten any answers?
well you can unlock your boot loader and install custom rom and after unlock you will unable to update through seus or pc companion until you relock the bl. i suggest u to use test point in this way you will not lose drm keys. and if there is a problem in network try different baseband.
Before unlocking bootloader you must remove sim-lock. Basically it comes down on buying sim unlock code.
DillonBladez said:
I know that bumping is generally frowned upon, but I'm doing it in hopes that perhaps somebody that could answer my questions just missed my thread.
Again, my apologies.
Sent from my Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
I had no problems flashing ICS via flash tool on my then locked bootloader, sim locked device, so I'm thinking that's not the problem here.
Make sure you have installed the right drivers for your device, that it has usb debugging activated and that it is configured to msc (usb storage) when flashing.
Also, when I unlocked my bootloader via paid method (alejandrissimo) it also eliminated the sim lock :beer: I think it's part of the process. Anyway, maybe you could explain a little further about the error log you get on flash tool.
Don't forget to click thanks if I helped.
Edit: about cwm, of course you can use it on custom roms, some kernel even have that included. . First you install it on your stock ics and then you get to flash other roms.
Sent from my SK17i using xda app-developers app
unforgiven1311 said:
I had no problems flashing ICS via flash tool on my then locked bootloader, sim locked device, so I'm thinking that's not the problem here.
Make sure you have installed the right drivers for your device, that it has usb debugging activated and that it is configured to msc (usb storage) when flashing.
Also, when I unlocked my bootloader via paid method (alejandrissimo) it also eliminated the sim lock :beer: I think it's part of the process. Anyway, maybe you could explain a little further about the error log you get on flash tool.
Don't forget to click thanks if I helped.
Edit: about cwm, of course you can use it on custom roms, some kernel even have that included. . First you install it on your stock ics and then you get to flash other roms.
Sent from my SK17i using xda app-developers app
Click to expand...
Click to collapse
I have a sim locked phone and the bootloader can't be unlocked because my phone was made in 12w22. No test point and no sony options because the status of the bootloader says Bootloader status: no.
The question is: if i by a sim-unlock code the bootloader status turns to yes?
i really need to unlock bootloader because my battery is causing me nightmares!! thanks for the help. sorry for the bad english(or not) .I'm portuguese

[Q] Xperia X10a, confusion about the bootloader, and its ability to be unlocked

I have an x10a, and I have for a while. But, its getting old, and boring. I wanted to spice it up with a custom ROM, namely Cyanogenmod. But going through the steps, xflashtool doesn't seem to want to play ball, informing me that "Your phone bootloader cannot be officially unlocked".
I've flashed it before, but only back to stock. This time I want something new.
Now, I've googled around and I've found a few pieces of information about this, but nothing concrete, and certainly nothing very in-depth.
I need to know;
- Does this mean that my attempts at a custom ROM are just at a halt completely? Too bad for me, try a different phone?
- If not, can I force the bootloader to be unlocked, and will it remove my ability to use the radio capability in the phone? (as I have read in a few places now), because my phone isn't a lot of good without the ability to do phone things.
- If I can force it, how, and are there any downsides?
and bonus round;
- Why are there certain phones that just can't have the bootloader unlocked.
Cheers in advance guys, I'd really like to hear some good news about this, but anything is better than what I have at this point.
AzzaMan said:
I have an x10a, and I have for a while. But, its getting old, and boring. I wanted to spice it up with a custom ROM, namely Cyanogenmod. But going through the steps, xflashtool doesn't seem to want to play ball, informing me that "Your phone bootloader cannot be officially unlocked".
I've flashed it before, but only back to stock. This time I want something new.
Now, I've googled around and I've found a few pieces of information about this, but nothing concrete, and certainly nothing very in-depth.
I need to know;
- Does this mean that my attempts at a custom ROM are just at a halt completely? Too bad for me, try a different phone?
- If not, can I force the bootloader to be unlocked, and will it remove my ability to use the radio capability in the phone? (as I have read in a few places now), because my phone isn't a lot of good without the ability to do phone things.
- If I can force it, how, and are there any downsides?
and bonus round;
- Why are there certain phones that just can't have the bootloader unlocked.
Cheers in advance guys, I'd really like to hear some good news about this, but anything is better than what I have at this point.
Click to expand...
Click to collapse
1st: you still can flash custom rom, look for the one that have stated (for locked bootloader)
2nd: yes you can, there is testpoint method (correct me If I'm wrong)
3rd: no afaik
Bonus: because there are carrier locked, or just plain damn unlucky
Sent from my GT-P3110 using xda app-developers app
TakuyaZ said:
1st: you still can flash custom rom, look for the one that have stated (for locked bootloader)
2nd: yes you can, there is testpoint method (correct me If I'm wrong)
3rd: no afaik
Bonus: because there are carrier locked, or just plain damn unlucky
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Champion. Cheers for the lightning fast reply, didn't expect to hear back for a day or two. I'm gonna begin my search for a copy of cyanogenmod for x10's that are for locked bootloaders. This should be fun
AzzaMan said:
Champion. Cheers for the lightning fast reply, didn't expect to hear back for a day or two. I'm gonna begin my search for a copy of cyanogenmod for x10's that are for locked bootloaders. This should be fun
Click to expand...
Click to collapse
Cyanogen mod cant be installed in locked bootloader, due to cm require an custom kernel
Sent from my GT-P3110 using xda app-developers app
TakuyaZ said:
Cyanogen mod cant be installed in locked bootloader, due to cm require an custom kernel
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Damn it... Any suggestions for a good alternative? I'd like something either really fancy, or really low RAM and Battery usage.
TakuyaZ said:
...
Bonus: because there are carrier locked, or just plain damn unlucky
Click to expand...
Click to collapse
My X10i is carrirer locked, and I could unlock the boot loader without any problems.
The problem with those who lose their radio capability, is, as I suspect it to be, because they tried SIM-unlock their devices with third party methods in a way that are not supposed to be done. (A "bad" hack method of some kind). Once they unlock the boot loader, they lose that poor third party hack, and the device reverts back to a SIM-locked state. Since most of the people who do SIM-unlock their devices, uses a different carrier, will also lose the radio because of the carrier/SIM lock.
One can safely unlock the boot loader if:
* The device remains SIM-locked and haven't been touched by poor, unknown SIM-lock hacks.
* The device isn't SIM-locked in the first place. (Device was delivered in an unlocked state)
* The device is SIM-unlocked with the proper method, where one get proper unlock codes from their original carrier matched with the IMEI code.
SysGhost said:
One can safely unlock the boot loader if:
* The device remains SIM-locked and haven't been touched by poor, unknown SIM-lock hacks.
* The device isn't SIM-locked in the first place. (Device was delivered in an unlocked state)
* The device is SIM-unlocked with the proper method, where one get proper unlock codes from their original carrier matched with the IMEI code.
Click to expand...
Click to collapse
My phone was delivered locked to... Vodaphone? I think. I unlocked it a long time ago. But, I unlocked it by given them my IMEI, and getting the unlock code from them. So, as legit as it gets really. I am still not allowed to just unlock my bootloader. Based on what I've seen in this thread, and a couple of other places, if I force the bootloader to unlock by "less sturdy" means, I should be fine with my sim-unlock, or be able to just contact them again and get a new unlock code.
So, this Testpoint method that TakuyaZ mentioned, anyone able to point me in the right direction for that or an alternative? I can't seem to find a decent tutorial anywhere.
AzzaMan said:
My phone was delivered locked to... Vodaphone? I think. I unlocked it a long time ago. But, I unlocked it by given them my IMEI, and getting the unlock code from them. So, as legit as it gets really. I am still not allowed to just unlock my bootloader. Based on what I've seen in this thread, and a couple of other places, if I force the bootloader to unlock by "less sturdy" means, I should be fine with my sim-unlock, or be able to just contact them again and get a new unlock code.
So, this Testpoint method that TakuyaZ mentioned, anyone able to point me in the right direction for that or an alternative? I can't seem to find a decent tutorial anywhere.
Click to expand...
Click to collapse
What method did you try to unlock the bootloader with? As far as I know your SIM-unlocked status shouldn't be affected at all, as it is properly unlocked, with the radio accepting all carriers. (Radio part of the device is semi-isolated from the rest of the system)
Try this method, and you should be fine: (But I cannot promise anything. If you do try it, you're on your own.)
http://forum.xda-developers.com/showthread.php?t=1253277
It's the method I used on a few X10i devices. Works on SIM-locked devices (They'll remain SIM-locked after, as it should be), as well as unlocked devices that previosly has been SIM-locked, but unlocked with the proper codes from the carrier. They remained SIM-unlocked after unlocking the boot loader. Good news that is.
So if you really know that your device has been properly SIM-unlocked with codes delivered from the carrier that locked the device in the first place, you should be fine. A.f.a.i.k, the only ones that lost their radio on their devices, are the ones who used improper third party hacking methods to SIM-unlock their devices.
Warning: If you are not 100% sure about what method that has been used to SIM-unlock your device. Stop. And turn back.
Alright, attempting the method posted above, I have hit a snag. I then proceeded to hit the same snag over and over again, trying minutely different methods.
My problem is with the qsd8250_semc tool.
The most I can get out of it is;
"
Process requires standard 2.x android firmware.
Press any key to continue...
Getting ROOT rights.
error: protocol fault (no status)
error: device not found
error: device not found.
Waiting...
"
Any suggestions? At this point I've tried the methods listed on the sites below, but nothing is working.
http://forum.xda-developers.com/showthread.php?t=1253277
http://www.modaco.com/topic/346145-how-toguideunlock-x10-bootloader-permanently/
AzzaMan said:
Alright, attempting the method posted above, I have hit a snag. I then proceeded to hit the same snag over and over again, trying minutely different methods.
My problem is with the qsd8250_semc tool.
The most I can get out of it is;
"
Process requires standard 2.x android firmware.
Press any key to continue...
Getting ROOT rights.
error: protocol fault (no status)
error: device not found
error: device not found.
Waiting...
"
Any suggestions? At this point I've tried the methods listed on the sites below, but nothing is working.
http://forum.xda-developers.com/showthread.php?t=1253277
http://www.modaco.com/topic/346145-how-toguideunlock-x10-bootloader-permanently/
Click to expand...
Click to collapse
Did you try with Flashtool? Don't use the newest version, you need 0.9.10 release. From http://androxyde.github.io/ There is a thread on here some where ill inbox you the link if I find it.
But it is easy as to do. By memory I think you click the padlock in flashtool to root phone then click on the plugins and you have the option to unlock boot loader with a click. Not sure if you have to add recovery first? Get the older version of flashtool though.
I'm sure someone will remember and help :good:
Found this http://forum.xda-developers.com/showthread.php?t=1254087
Hey mate this is the thread I used http://forum.xda-developers.com/showthread.php?t=1821750
doodownunda said:
Did you try with Flashtool? Don't use the newest version, you need 0.9.10 release. From http://androxyde.github.io/ There is a thread on here some where ill inbox you the link if I find it.
But it is easy as to do. By memory I think you click the padlock in flashtool to root phone then click on the plugins and you have the option to unlock boot loader with a click. Not sure if you have to add recovery first? Get the older version of flashtool though.
I'm sure someone will remember and help :good:
Found this http://forum.xda-developers.com/showthread.php?t=1254087
Hey mate this is the thread I used http://forum.xda-developers.com/showthread.php?t=1821750
Click to expand...
Click to collapse
The only things needed on the X10 part is it to have original (Stock) firmware with Android 2.1 or 2.2, with the original 2.6.29 kernel.
Also one need to enable debugging over USB (Debug Bridge) in the developer settings. And lastly need the drivers installed if using Windows. (Which I assume is the case here)
Once that's done, it should all work.
I've written a Linux script if anyone needs it. Still need the other files from the original qsd8250.7z toolset from the_laser's thread. See attached files.
Place qsd8250_semc.bash in the same director as qsd8250_semc.cmd, then execute it.
One also need Linux-version of the adb command, and in the system PATH variable.

Categories

Resources