We can no longer unlock your bootloader with codes. Please do not ask me or ash for bootloader unlock codes. We can not help you.
This thread is now here for historical purposes representing times when people were free to do what they wanted with their devices. Fsck yourself with a rake, Verizon.
The bootloader has been unlocked. Let's get our freaking root on.
Disclaimer: Read through these instructions in their entirety. If these don't make sense to you, you do not need to be rooting your phone. Nobody here has the time required to teach you how to use cmd in Windows. We will not baby step you through how to use ClockworkMod Recovery. Root is not a mythical land with fairies and unicorns where nothing ever goes bad. If you don't know how to properly install a driver in Windows, you probably don't need an Android device to begin with, let alone a rooted one.
These instructions are intentionally left vague. Do your research on these terms. Understand what you are doing before you do it.
tldr: if you fsck your phone up, it's on you and only you.
Easy Way (YRMV!)
This is by far the easiest method. You will have to read between the lines here. I will not detail all the steps. Please record your experiences in this thread and let me know how it all goes! We're all still learning. This is basically copied from Bin4ry's CWMR Thread so thanks go to him! The easy steps below assume a lot of basic knowledge steps. Like unlocking the bootloader. If you're unsure of what to do, you probably shouldn't be doing it.
Download the CWM recovery from multiupload
Boot off of that file (DO NOT FLASH): fastboot boot recoveryPLAY.img
Copy this to your memory card and flash it with the booted recovery
Reboot and test root
Second Method: Advanced User Instructions
Unlock your bootloader. Check out Ash's thread: thread
Download Doom's all in one kernel from here
Use fastboot to "hot boot" the kernel: fastboot boot boot.img
Your phone may or may not boot. It doesn't matter. Let it be for a while, then power it off.
Doom's kernel will have rooted your stock system.
If You're On A Mac...
Or maybe just need some general help with some more detailed insturctions than are labeled here, check out the awesome post that Cubsfan3493 made for everyone. He's even got a downloadable PDF with pictures. Go give him some thanks at his post!
Is the R800x running 2.3.2 or 2.3.3. There's reports that Gingerbreak and alternatives are no longer working in 2.3.3.
It's running 2.3.2 right now. OTA updates say its up to date. I'm trying to figure out if I'm just having a generic issue with the breaks (like memory cards for example) or if Verizon maybe patched the exploit in their 2.3.2 build.
I have tried pretty much everything as well, I really hope some dev's start to pop their noises in here as I am a bit sad about the activity so far
I've been trying to root mine as well. The discussion I've been having is in this thread
http://forum.xda-developers.com/showthread.php?t=1097856
I'll keep an eye on both threads, but I have had no luck so far.
I'm guessing it's something they fixed in the final Verizon build before release. Curious... What's your build #? Mine is 3.0.A.2.184.
Sent from my R800a using XDA App
axiomjunglist said:
I'm guessing it's something they fixed in the final Verizon build before release. Curious... What's your build #? Mine is 3.0.A.2.184.
Click to expand...
Click to collapse
Yes i think verizon fixed the exploit gingerbreak uses before releasing the handset in the usa. When i was on build number 3.0.A.2.184 (uk xplay R800i) it rooted in like 30 seconds.
But in the new update 3.0.1.A.0.145 the exploit has been fixed. So all devices around the world have been left unrootable (for now ) the devs will figure away out.
I think the uk version 2.3.3 build 3.0.1.A.0.145 has been rooted (for unlocked bootladers) http://forum.xda-developers.com/showthread.php?t=1098736 So if your bootloader is unlocked soon it maybe possible. If its locked your stuck waiting with the rest of us for a rooting method on locked devices.
I saw you updated from another post, did you lose root access after the update?
Sent from my R800a using XDA App
axiomjunglist said:
I'm guessing it's something they fixed in the final Verizon build before release. Curious... What's your build #? Mine is 3.0.A.2.184.
Click to expand...
Click to collapse
build number - 3.0.E.2.89
A shame they didn't let us all have unlocked bootloaders.
axiomjunglist said:
I saw you updated from another post, did you lose root access after the update?
Click to expand...
Click to collapse
Yes i did. But the fixes added in the update are worth loosing root, for the time being . Being unable to root only applies to people with a locked bootloader. But im guessing devs from the arc and play forum are possibly looking for ways to root with a locked bootloader
Yeah I have the option to unlock my bootloader but don't want to just yet. I'll hold off on the update until a new version of gingerbreak arrives
Sent from my R800a using XDA App
For the record, it seems like the bootloader is unlockable on the R800x. Fastboot is totally accessible by the same means and the oem unlock command is recognized, the phone is responsive, it's just looking for a key, the same as the GSM counterpart. The only difference is that the Verizon version doesn't have an IMEI (or does it.... since it does have a sim card slot....), just an ESN. So obviously you can't obtain an unlock key from this number.
Mills00013 said:
For the record, it seems like the bootloader is unlockable on the R800x. Fastboot is totally accessible by the same means and the oem unlock command is recognized, the phone is responsive, it's just looking for a key, the same as the GSM counterpart. The only difference is that the Verizon version doesn't have an IMEI (or does it.... since it does have a sim card slot....), just an ESN. So obviously you can't obtain an unlock key from this number.
Click to expand...
Click to collapse
Wonder if you pop a pre-paid SIM in the slot (or try a friend's AT&T/T-Mobile SIM) and disabled the CDMA radio if you could get an IMEI to pop up on the keypad using *#06#. Might work? I have no clue... and you'd still have to send it to SE and hope they clear it.
I have a few SIMs here that I could try. Ill see what I come up with in a little bit. My gut is telling me that Verizon probably has the SIM slot firmware disabled. Thats only because they havn't officially mentioned it anywhere. In fact, the slot itself is actually hidden by a piece of plastic that you have to remove. One wouldnt have any idea it was there unless you were looking for it and even then you feel like you're breaking your phone to access it.
I also considered hooking it up to QPST to see if it would grab some serial numbers out of the device. Can anyone confirm if this is a qualcomm chip inside the phone?
I just tried a T-mo and an AT&T SIM, neither give me any sort of insertion notification or acknowledgement that they are present. So I'd say the slot is firmware disabled. But it should still have an IMEI, right? That would be programmed by Qualcomm out of the factory before Ericsson would have even installed it. Or am I taking crazy pills?
do a ADB devices on your phone it gives what I think is a IMEI number and if you put the first 14 in on sony's site it gives you a unlock code, i am to much of a wussy to try it tho lol.
b00sted said:
do a ADB devices on your phone it gives what I think is a IMEI number and if you put the first 14 in on sony's site it gives you a unlock code, i am to much of a wussy to try it tho lol.
Click to expand...
Click to collapse
more than willing to be take a chance on mine. i ran adb devices. got code. first 14 digits (minus the b) sent to sony and got an unlock code.
next steps i'm confused on. how do i boot to fastboot mode? i tried holding menu key and inserting usb... didnt' seem to do anything...
ran
9. In the cmd windows type in fastboot.exe -i 0x0fce getvar version
and it did nothing just sat there (waiting for device).
Is there an indication you are in fastboot mode? should 0fce be different on our phones? any ideas?
EDIT: its hold search, not menu, got it to fastboot mode and got response.. trying now. will post results
EDIT 2 : and fail.
ace518 said:
more than willing to be take a chance on mine. i ran adb devices. got code. first 14 digits (minus the b) sent to sony and got an unlock code.
next steps i'm confused on. how do i boot to fastboot mode? i tried holding menu key and inserting usb... didnt' seem to do anything...
ran
9. In the cmd windows type in fastboot.exe -i 0x0fce getvar version
and it did nothing just sat there (waiting for device).
Is there an indication you are in fastboot mode? should 0fce be different on our phones? any ideas?
EDIT: its hold search, not menu, got it to fastboot mode and got response.. trying now. will post results
EDIT 2 : and fail.
Click to expand...
Click to collapse
ya I just tried too and fail :/ #sadpanda
Neither the adb devices nor the fastboot devices codes have anything to do with the IMEI number.
Enviado desde mi R800i usando Tapatalk
I am willing to donate towards the first person that can get root and CWM on this!
Related
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??
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 ?
I'm in over my head. Very much so. I've been flashing for years and a friend of mine has handed off his ATT atrix after making some big mistakes. He was rooted and somehow/for some reason deleted CWM and the new OTA ended up getting his device to this point (photo in attachment). I'm not very familiar with RSD, as luckily I've never found myself in a predicament like this. I've been all over this forum, the pudding/fruitcake/fastboot threads, and although I've seen the 'Don't SBF' warnings everywhere, I don't know what else to do, and I don't want to take any more action without knowing the consequences. I think this is a pretty unique situation. I'm asking for a detailed instruction on getting this phone restored (I've seen some say it's not possible, but other places saying a guy figured out a way). I need the specific links, and specific steps (as I've had much issue with broken links). I have access to ubuntu and windows so whichever is more simple is fine. I could try my luck but I'd rather reach out to someone who knows before hand.
*As far as I know the battery is high enough to flash (it's sitting with the battery pulled for now)
I don't care about retaining root, having a custom recovery or anything of that nature. I just need this phone to be in working condition again. Upon that happening we'd be happy to throw 20$ (via paypal) to whoever can get us there. Thanks in advance.
maybe this will help
I was rescued previously by the nice folks on atrixforums. you can reference this link http://www.atrixforums.com/forum/rescue-squad/6164-se-flash-olympus-help.html
Should be able to flash Romracers CWM via fastboot > http://forum.xda-developers.com/showthread.php?t=1204500 then get back into recovery. You can also flash a Fruitcake in fastboot mode > http://forum.xda-developers.com/showthread.php?t=1163009.
From your picture it looks like the bootloader was unlocked before, and maybe need to issue the unlock command again. This thread may help you > http://forum.xda-developers.com/showthread.php?t=1182871
Looks like ya just need to do the fastboot oem unlock commands to unlock the BL and finish the process....
thanks
Thanks for the quick responses guys, I'm off to work now but I'll try this tonight. Once again thank you.
I had the exact same problem, same thing happened with my phone, don't worry, you're okay!
First, are you sure that's the right SBF? I would confirm whether it is because that's the easiest way. Next, do what others have said and try to flash a recovery on it, from there on you can just unlock the phone and flash any rom.
Hope you get it sorted out.
G-Man. said:
Looks like ya just need to do the fastboot oem unlock commands to unlock the BL and finish the process....
Click to expand...
Click to collapse
brandonmangan - based on your screenshot you posted, you need to do the fastboot oem unlock commands, you flashed the pudding sbf with the unlockable bootloader. Get the fastboot drivers installed and then run the commands as they are listed in the pudding thread. Thats ALL you need to do.
Good ghod what a state I've managed to get myself into: I've been unlocking/re-locking my phone (ROM: OTA ICS, S-On, Unlocked, Rooted) for right at a year now, but, during the recent OTA update push, I managed to get it into a state where it will no longer unlock. My (long, sorry) story follows...
I started receiving the recent OTA push two or three weeks ago. The problem is that I'd renamed the HTClinkifydispacher apk and odex files, and added a couple of things to /system/app/build.prop so the update would fail. Why was this such an immediate problem? Because I use my phone for an alarm clock and would wake up on random days to see it booted to recovery---after having overslept. Grrr.
Being the impulsive guy that I am, rather than just ask here how to stop the f$*kin' update, I found and saved the OTA.zip file to my sdcard, fixed the two problems I was having, re-locked the bootloader, and booted to recovery. Next, I *thought* I picked the OTA zip file to install... but I was wrong.
For at least one reason (I wanted to install a kernel with tun.ko installed so I could use a VPN network connection), I had a copy of SebastianFM's 1.4 overclocked kernel zip on my sdcard and mistakenly picked *it* instead of the OTA zip (hey, the fonts are small in Amon Ra). Well, that install failed, and, when I saw what I'd done, I thought "uh oh," so I rebooted the phone fully to see if I'd done any damage. None was apparent. So I moved on, once again re-booting into recovery and (this time successfully) installing the OTA zip.
Woo-hoo!
I thought I was golden, but I was wrong: Using my original unlock code and an up-to-date copy of the Android SDK on my linux box, I tried to reflash the unlocktoken partition using the fastboot command. My cursor froze/still freezes at something like "[0kb downloaded]..." It's almost like I've lost permission to write to that partition in the bootloader.
After the first sixteen times of trying various re-flashes of the August OTA, I thought "Gee, maybe it's something to do with the firmware," and since doing something is almost always worse than doing nothing (yes, that's what I meant to say), I did the only thing I could do: I flashed the Global Update RUU zip from October that I got off of Android Police's site. It's a great ROM; unfortunately, I still cannot unlock my bootloader.
In anticipation of some possible questions, let me add that
(1) I've factory reset any number of times;
(2) When I did the flashes, I immediately re-flashed a second time to ensure that the flashes took;
(3) When I connect my USB cable, I see "Fastboot USB" light up in the fastboot section of HBOOT.
(4) When I issue any other fastboot command, such as "fastboot devices" or "fastboot get_identifier_token", I get responses from the phone.
(5) Even though I have my original Unlock_code.bin file from HTCdev, I went through the whole unlock process from that site (sent a new identifier token; got the Unlock_code.bin back; tried "fastboot flash unlocktoken Unlock_code.bin") on two other occasions. Interestingly, the identifier_tokens would vary, but any new Unlock_code.bin files have all been identical---if the md5sum hash can be trusted to distinguish them.
Can anyone out there in expert-land help me figure out how to re-unlock my bootloader?! !? Beer can be involved.
Many thanks for your patience and kind consideration...
cheers,
john
Hey All,
So, I'd like to first say thanks to all of you who read and considered throwing in an opinion on how I might move forward with my little problem.
Secondly, I have some followup from HTC, which spawns a followup question. Please read on...
Since my OP, I have been in a back and forth with HTC about what I did to my phone that has left me unable to re-unlock it. Their answer, in a nutshell, was that I'd accepted the update while my phone had a 3rd-party recovery on it. Guilty as charged, I did; Amon Ra 3.15.
More specifically, they wrote: "If any portion of this check fails due to the stock recovery not being present, the update may load but the security sector will not authenticate. This may be blocking the re-unlock."
If you're like me, you'll note that there are a couple of "may"s in those two sentences that have left me wondering if they're just giving me a stock "I really don't know what the hell happened to your phone" answer.
So just to satisfy my curiosity, has anyone else out there ever had a problem flashing OTAs while having a 3rd-party recovery on their phones?
thanks again,
john
There's a couple threads about the recent OTA, one in General and one in this section. People posted about their various experiences, you might find some useful info in those.
I wonder if you can s-off at this point and fix your issue? I don't know if you need to be unlocked to s-off, I know you end up locked, but if not, that would give you the freedom to flash what you want without needing to be "unlocked".
feralicious said:
There's a couple threads about the recent OTA, one in General and one in this section. People posted about their various experiences, you might find some useful info in those.
Click to expand...
Click to collapse
Yes, I've looked through them and had no luck finding anything relevant to my case.
feralicious said:
I wonder if you can s-off at this point and fix your issue? I don't know if you need to be unlocked to s-off, I know you end up locked, but if not, that would give you the freedom to flash what you want without needing to be "unlocked".
Click to expand...
Click to collapse
The phone has to be unlocked to do the s-off thing.
thanks,
john
Update: Problem Solved!
Hey All,
As the post title states, I finally did get this sorted out.
The solution? Borrowing a windows 7 computer, downloading the HTC device drivers, fastboot and adb, and then merely running the 'fastboot flash' thing. Like I'd done a thousand times already on my linux system. Sheesh.
Thanks to all who read or contributed to this thread...
cheers,
john
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.