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.
Related
Okay guys, i flashed the 2.3.4 ota as soon as it came out (before all this trouble with it of course) and now i am stuck because i was under the impression that the new bootloader would be unlocked so i had never even though about eating any pudding before the fact. Now i come to my trouble, im running a totally stock 2.3.4 att and i cant seem to find a way out.
Question #1- If i have a locked bootloader can i fruitcake back?
Question #2- Is there a possible way to unlock the new bootloader?
Question #3- How in heck do i get root, im on windows 7 and i recently tried the two bat files that one of the devs released and they were a no go, it didnt seem to flash the preinstall when i tried to look for it, it wasnt there. I have been quietly trying to fix this on my own for days now i am asking for a little help. Im stumped.
I got root using the /preinstall method with those 2 .bat files posted yesterday.
From page 30-35 is the guidance I followed from mramirezusa.
Other than that we are in the same boat.. I read puddings will flash relatively safely.http://forum.xda-developers.com/showthread.php?t=1159950&page=30
cthomas5714 said:
Okay guys, i flashed the 2.3.4 ota as soon as it came out (before all this trouble with it of course) and now i am stuck because i was under the impression that the new bootloader would be unlocked so i had never even though about eating any pudding before the fact. Now i come to my trouble, im running a totally stock 2.3.4 att and i cant seem to find a way out.
Question #1- If i have a locked bootloader can i fruitcake back?
Question #2- Is there a possible way to unlock the new bootloader?
Question #3- How in heck do i get root, im on windows 7 and i recently tried the two bat files that one of the devs released and they were a no go, it didnt seem to flash the preinstall when i tried to look for it, it wasnt there. I have been quietly trying to fix this on my own for days now i am asking for a little help. Im stumped.
Click to expand...
Click to collapse
Question #2- Is there a possible way to unlock the new bootloader? yes use pudding
cthomas5714 said:
Okay guys, i flashed the 2.3.4 ota as soon as it came out (before all this trouble with it of course) and now i am stuck because i was under the impression that the new bootloader would be unlocked so i had never even though about eating any pudding before the fact. Now i come to my trouble, im running a totally stock 2.3.4 att and i cant seem to find a way out.
Question #1- If i have a locked bootloader can i fruitcake back?
Question #2- Is there a possible way to unlock the new bootloader?
Question #3- How in heck do i get root, im on windows 7 and i recently tried the two bat files that one of the devs released and they were a no go, it didnt seem to flash the preinstall when i tried to look for it, it wasnt there. I have been quietly trying to fix this on my own for days now i am asking for a little help. Im stumped.
Click to expand...
Click to collapse
hey man first things first. dont panic, you are not stuck. this is temporary at best, in the mean while theres plenty of stuff you can do, sbf is not safe to begin with. so actually be gladd you only got to use RSD one time
first things first, get yourselfed unlocked, pudding will do the trick. once after pudding, you never have to touch RSD
Once you are done with pudding go ahead and get tenfars unlocked cwm
once you are done with that you are free to flash pretty much all the roms, as usually custom roms, or fruit cakes dont have bl, only the rest
enjoy
Okay guys, thanks for your help. but let me get this clear, i do not have a unlocked bootloader, im a pudding virgin. I can simply rsd the 1.83 with pudding and thats it? No worries no nothing?
cthomas5714 said:
Okay guys, thanks for your help. but let me get this clear, i do not have a unlocked bootloader, im a pudding virgin. I can simply rsd the 1.83 with pudding and thats it? No worries no nothing?
Click to expand...
Click to collapse
Yes but you still can't use any other sbf. I'd use the raw pudding sbf, unlock, then use CWM from here on out. No more rsd
Sorry about that. There is just the unlock and then the unlock packaged with 1.8.3. The one that has has been causing bricks from my understanding is the packaged one. Be sure you flash just the unlock.
Anyone know what exactly will be erased from /data after flashing the unlock? Also I don't want to restore backed up files that will conflict with new ones. Any guidance on this is appreciated.
snudmusk said:
Sorry about that. There is just the unlock and then the unlock packaged with 1.8.3. The one that has has been causing bricks from my understanding is the packaged one. Be sure you flash just the unlock.
Anyone know what exactly will be erased from /data after flashing the unlock? Also I don't want to restore backed up files that will conflict with new ones. Any guidance on this is appreciated.
Click to expand...
Click to collapse
All user data is wiped when unlocking. The 1.8.3 sbf with pudding is safe to flash but i recommend just using pudding and then CWM and ditch rsd.
jruweaver said:
All user data is wiped when unlocking. The 1.8.3 sbf with pudding is safe to flash but i recommend just using pudding and then CWM and ditch rsd.
Click to expand...
Click to collapse
Agree, just use the pudding only sbf. to unlock , then preinstall to get root.
Make sure to have 50 or so battery so you don't run into the trouble I had with battery being to low to fastboot. Also once you flash pudding you wont be able to boot the phone, don't panic just follow steps to fastboot oem unlock and phone will boot fine afterwards.
Sent from my MB860 using Tapatalk
woahh no bad idea, im scared. I did exactly as you all said and it acts like its hard bricked, SVF:105 error but then it says no OS detected and i have 14 options
1RSD
2Fastboot
3Nvflash
4-9BP something
9Android recovery
10Boot android (no bp)
11Device UID
12Console
13early usb enumeration
14BP tools
WHAT DO I DO?
cthomas5714 said:
woahh no bad idea, im scared. I did exactly as you all said and it acts like its hard bricked, SVF:105 error but then it says no OS detected and i have 14 options
1RSD
2Fastboot
3Nvflash
4-9BP something
9Android recovery
10Boot android (no bp)
11Device UID
12Console
13early usb enumeration
14BP tools
WHAT DO I DO?
Click to expand...
Click to collapse
Which did you flash? Pudding or 1.8.3 with pudding?
Try connecting your phone to pc select fastboot and finish the pudding instructions (fastboot oem unlock)
It might boot then.
Sent from my MB860 using XDA Premium App
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/show....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/show....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.
Is there a way to root without unlocking the bootloader?
five3zero said:
Is there a way to root without unlocking the bootloader?
Click to expand...
Click to collapse
Yes.
Follow the instructions listed on here:
http://forum.xda-developers.com/showthread.php?p=15023030
The 3rd post has the instructions I followed.
If you have problems be sure to read through the thread as someone else has most likely already had the same issue.
This worked for me.
cthomas5714 said:
woahh no bad idea, im scared. I did exactly as you all said and it acts like its hard bricked, SVF:105 error but then it says no OS detected and i have 14 options
1RSD
2Fastboot
3Nvflash
4-9BP something
9Android recovery
10Boot android (no bp)
11Device UID
12Console
13early usb enumeration
14BP tools
WHAT DO I DO?
Click to expand...
Click to collapse
Just do: fastboot oem unlock (or whatever tthe code is)
Them: fastboot reboot
Sent from my MB860 using XDA App
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 ?
Hello everyone. I am new to the world of android, but I'm a quick enough learner. Here is my specific problem:
I have an AT&T Atrix 4g. It is currently superuser rooted. It is currently running Android ROM 2.3.4.
Shortly after rooting the device, I downloaded ROM Manager and successfully installed through the application Clockwork Recovery. I tried to select the option to back up the current ROM (the stock android) on my SD card.. however, during the load screen, I got an error message stating
"Failed to boot 2
Starting RSD protocol support"
So doing some research, I came upon the conclusion that the reason I can't backup or really do anything with ROMs is that I needed an unlocked bootloader.
I went to Atrix4ghacks and followed the instructions on how to unlock bootloader and install permanent recovery.
This is the critical part: When I entered into the command prompt "fastboot oem unlock", instead of proceeding normally I got the return message:
"OEM unlock is not implemented"
Again, did a google search and read that Android 2.3.4 on Atrix 4g does NOT allow unlocked bootloaders.
So, the questions that I have that result from this are:
1.) Can someone here confirm that, in fact, I am unable to unlock the bootloader on my phone?
2.) If so, is there a viable workaround that is both reasonably safe and not overly complicated? Please note that I have no backup in case something goes wrong, leading me to
3.) Is there a way to backup my stock 2.3.4 ROM without an unlocked bootloader?
4.) Can I revert safely to an older android version that supports unlocked bootloaders?
5.) Can you actually install new ROMs without an unlocked bootloader?
6.) Am I totally screwed?
HUGE THANKS to anyone who actually bothered reading this, and even more thanks to anyone who can answer/point me in the right direction. Much appreciated!!!
thats becouse u havent flashed yet the bootloader ill give a post related to this and esay way to do it
http://forum.xda-developers.com/showthread.php?t=1182871
and you CANT go back to 2.2 or 2.3 u can hard brick your phone
tufo430 said:
thats becouse u havent flashed yet the bootloader ill give a post related to this and esay way to do it
http://forum.xda-developers.com/showthread.php?t=1182871
and you CANT go back to 2.2 or 2.3 u can hard brick your phone
Click to expand...
Click to collapse
Thanks a ton for that link. I'm sorry to ask once again, but I'm very wary of possibly bricking my phone... so I must ask: Is your solution possible with 2.3.4? Or will the phone softbrick?
If you did the Over The Air (OTA) update to 2.3.4 then yes your phone will softbrick after flashing the bootloader. Re-enter fastboot and issue the unlock commands and everything will be fine when you reboot.
I want to thank everyone who has given great information here as my last two phones this place has been invaluable place of information.
I am now trying to be more "carefull" for a mistake I made. I ended up hard bricking a phone with the dreaded Failed to boot 0X1000. I have rooted phones before and understand the process enough to get by.
However I am back at square one I was months ago when I bricked my phone (since have gotten a new atrix), Im ready to try this again. I have done ALOT of reading but to be honest there seems to be do this and do thats than people in the world. I dont want to make the same mistake again.
Trying to find "the way" seems to be at issue. Ive seen everything from avoid RSD to using it to things not addressing as if the brick issue even happened. I feel like theres no path to follow. Im wondering how many others feel this way too who are at the crossroads of doing it.
My phone is rooted, and has Android 2.3.4 and System 4.5.91.MB860.ATT.en.US if that help to point me in the right direction.
Thank you!
You need to go to the IHOP thread, I believe it is stickied, and download only the unlock sbf. You will flash that with RSD and then follow the unlocking directions.. I.e. boot to fastboot, then issue the command "fastboot oem unlock" and follow the instructions on screen. Once done, you will be unlocked. You can then flash recovery via fastboot. You are then free to flash ROMs.
The only reason to ever have to flash an SBF after this is for warranty reasons. However, DO NOT flash a froyo one. Only flash gingerbread based ones or you will hard brick again.
Any questions?
Sent from my MB860 using xda premium
Yes if you follow the instructions in the IHOP thread you shouldn't have a problem:
http://forum.xda-developers.com/showthread.php?t=1136261&highlight=international+house+of+pudding
Here is a useful step-by-step guide to unlocking bootloader:
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
I personally would use the pudding file over the unlock file linked in the Briefmobile walkthrough, i'm sure they are the same but i know for a fact the pudding file works. This at least gives you the step-by-step procedure you are wanting.
Here's a video as well:http://www.youtube.com/watch?v=K4Bf9QIZsRI
I was pretty new to all this when i unlocked my atrix and didn't have any issues, just make sure you follow the instructions properly. Also as d3athsd00r stated try to avoid flashing SBF files via RSD after your bootloader is unlocked, the safest way to flash stuff is via CWM recovery.
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