I bought my Atrix not too long ago and it came with android 2.2.2 and fully upgraded. Anyways I searched all over the forums and google and found nothing.
I followed these steps shown in a guide at briefmobile but the flash always fails because mine shows up as "SE Flash Olympus" and not "NS Flash Olympus". Does this mean I cant unlock the bootloader to instal 2.3.4? or is there something I'm doing wrong?
In the early atrix days it was rumored that NS meant non-secured and SE meant secured. Sadly, all our devices were indeed running a locked bootloader. Perhaps try flashing pudding , the preinstall sbf or the hktw leak? Maybe in your case you have an unlocked device already (not really i guess but your phone is different)
It looks like you're right. My phone has already been unlocked. Thanks for the reply!
Sorry To Resurrect
I am in USA with ATT
I bought my Atrix 2 weeks ago
I downloaded the OTA upgrade so I was running 2.3.4 from ATT
I downloaded the FULL 2.3.4 SBF and RSD Lite from the development thread
http://forum.xda-developers.com/showthread.php?t=1136261
When flashing the SBF my process FAILED to flash and I now have the following message locked on my phone's screen (See abbreviated screen below):
SVF 105:1:2
Failed to boot 0x1000
No OS detected, going to RSD Mode
.
.
.
Starting Fastboot Protocol support
What happened and can i save my phone?
FIXED
zetaex said:
I am in USA with ATT
I bought my Atrix 2 weeks ago
I downloaded the OTA upgrade so I was running 2.3.4 from ATT
I downloaded the FULL 2.3.4 SBF and RSD Lite from the development thread
http://forum.xda-developers.com/showthread.php?t=1136261
When flashing the SBF my process FAILED to flash and I now have the following message locked on my phone's screen (See abbreviated screen below):
SVF 105:1:2
Failed to boot 0x1000
No OS detected, going to RSD Mode
.
.
.
Starting Fastboot Protocol support
What happened and can i save my phone?
Click to expand...
Click to collapse
I was able to fix this issue.
I chose FASTBOOT during the the first 5 seconds of the boot up.
I pressed UP on the rocker switch to activate FASTBOOT mode
I UNLOCKED the bootloader
I loaded the recovery image
I loaded AURA custom ROM...
phew... hardbrick avoided...
zetaex said:
I was able to fix this issue.
I chose FASTBOOT during the the first 5 seconds of the boot up.
I pressed UP on the rocker switch to activate FASTBOOT mode
I UNLOCKED the bootloader
I loaded the recovery image
I loaded AURA custom ROM...
phew... hardbrick avoided...
Click to expand...
Click to collapse
Did you have the usb debugging on and what usb mode were you own?
Sent from my MB860 using XDA App
supermerkin said:
Did you have the usb debugging on and what usb mode were you own?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Debugging was enabled and I was set to "None" for the USB mode.
THANK YOU!!!
zetaex said:
I was able to fix this issue.
I chose FASTBOOT during the the first 5 seconds of the boot up.
I pressed UP on the rocker switch to activate FASTBOOT mode
I UNLOCKED the bootloader
I loaded the recovery image
I loaded AURA custom ROM...
phew... hardbrick avoided...
Click to expand...
Click to collapse
Your notes on how you fixed this saved my phone (and my sanity!) Thanks for taking time to post it.
Note, what I used to unlock and load the recovery image is on atrix4ghacks (it won't let me post the link) but it is labeled How to Unlock Bootloader and Install Permanent Recovery!
Looks like it lost everything and reverted to 2.2.2 but that's much better than a brick any day
kiri_9 said:
Your notes on how you fixed this saved my phone (and my sanity!) Thanks for taking time to post it.
Note, what I used to unlock and load the recovery image is on atrix4ghacks (it won't let me post the link) but it is labeled How to Unlock Bootloader and Install Permanent Recovery!
Looks like it lost everything and reverted to 2.2.2 but that's much better than a brick any day
Click to expand...
Click to collapse
Why did we have to ressurect a dead thread? And this method has been covered extensively in the official how to thread many times.
Sent from my MB886 using xda app-developers app
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
Hi All,
I have an ATT Atrix and I flashed the 2.3.4 beta from http://forum.xda-developers.com/showthread.php?t=1159385 and forgot to unlock the bootloader. I already have the 1.8.3 radio. Right now the phone froze on Dual Core Screen. I guess this has something to do with not unlocking the bootloader. The phone can still boot to fastboot, the original Android recovery and RSD. But, It won't flash all roms I downloaded saying the signature validation is incorrect. And I tried to flashed the unlock sbf and try to unlock the bootloader. And the RSD lite kept saying unable to retrieve interface and thereby failed.
What do I need to do on this case?
Thanks for you help!!! Sincerely!!!!!!
taoistman said:
Hi All,
I have an ATT Atrix and I flashed the 2.3.4 beta from http://forum.xda-developers.com/showthread.php?t=1159385 and forgot to unlock the bootloader. I already have the 1.8.3 radio. Right now the phone froze on Dual Core Screen. I guess this has something to do with not unlocking the bootloader. The phone can still boot to fastboot, the original Android recovery and RSD. But, It won't flash all roms I downloaded saying the signature validation is incorrect. And I tried to flashed the unlock sbf and try to unlock the bootloader. And the RSD lite kept saying unable to retrieve interface and thereby failed.
What do I need to do on this case?
Thanks for you help!!! Sincerely!!!!!!
Click to expand...
Click to collapse
Please post in question and answer section.
Sent from my MB860 using XDA Premium App
taoistman said:
Hi All,
I have an ATT Atrix and I flashed the 2.3.4 beta from http://forum.xda-developers.com/showthread.php?t=1159385 and forgot to unlock the bootloader. I already have the 1.8.3 radio. Right now the phone froze on Dual Core Screen. I guess this has something to do with not unlocking the bootloader. The phone can still boot to fastboot, the original Android recovery and RSD. But, It won't flash all roms I downloaded saying the signature validation is incorrect. And I tried to flashed the unlock sbf and try to unlock the bootloader. And the RSD lite kept saying unable to retrieve interface and thereby failed.
What do I need to do on this case?
Thanks for you help!!! Sincerely!!!!!!
Click to expand...
Click to collapse
I would get it into RSD mode (Press and hold power button and volume UP key at the same time, hook it up to your computer, run RSDlite and flash the stock 1.2.6 located HERE!
since you have not unlocked your bootloader AND you used keneths ROM I do not think you can HardBrick your device flashing backwards considering you weren't successful in flashing forwards.
But just in case.... You are responsible for using any dumb ideas I might have!
Next time, please post in the Q&A section as no one likes to see this stuff in the Developers section
Thanks for replying so quick, I will try it out!!! Thanks very much!!!!!!
The flash to 2.3.4 would not work without unlocking the bootloader. Try a factory reset/wipe then RSD as stated above if the wipe doesn't work.
ClearFire said:
I would get it into RSD mode (Press and hold power button and volume UP key at the same time, hook it up to your computer, run RSDlite and flash the stock 1.2.6 located HERE!
since you have not unlocked your bootloader AND you used keneths ROM I do not think you can HardBrick your device flashing backwards considering you weren't successful in flashing forwards.
But just in case.... You are responsible for using any dumb ideas I might have!
Click to expand...
Click to collapse
Hard brick if he didn't use the cwm method.
Sent from my MB860 using XDA App
Ok would say wrong section but I got time to maybe help.
Just boot into CWM and flash fruitcake 1.8.3 zip. Wipe before flash, this should boot.
I cannot boot to CWM somehow...
nexxusty said:
Hard brick if he didn't use the cwm method.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
OK, I think you guys "Failed" to read is whole post.... Please read before you comment.
He said he has "the original Android recovery"
did booting to RSDLite work?
The flash back did worked. Now phone boot up and live again!!! Thanks very much guys!!!!!
taoistman said:
The flash back did worked. Now phone boot up and live again!!! Thanks very much guys!!!!!
Click to expand...
Click to collapse
I'm glad!!
Note: Once you unlock your bootloader you can never use the method that I outlined for you when flashing back or forward. Just uninstall RSDLite and forget all about it or you will HardBrick your device leaving you with a very expensive paper weight
So Guess who got an Atrix today? me! Guess who also probably bricked their atrix today? me!
So here is what happened:
1: I have an unlocked, rooted Atrix 4G from AT&T running 2.2 1.5.7 I believe.
2: I wanted to flash some roms, so I so I attempted to flash tenfar's CWM, but that didn't work, it said install succeeded but I could not get into CWM ( I tried everything, believe me, I'm no noob)
3: I then attempted to flash CWM from Rom Manager and so I did and I flashed the Atrix version, I then hit boot into recovery from within Rom Manager.
4: What I got next is a screen that says "failed to boot 2, starting RSD mode", now I cannot get passed that screen when it powers up.
5: Worst of all, using MSU (moto sw update), it says device is connected but not what kind, meaning I can't restore it, probably because I had adb mode turned on previosly.
update: after attempting to flash a new SBF, the phone told me it failed because the phone did not re-enumerate. Now I have the same problem, but with a new error message on the boot screen: Battery to low to flash!
I have searched everywhere, now I need to resort to you, xda community, Thanks So Much!!!
If you can get into RSD , check to see if fastboot is an option. If you can get into that I would advise to start over by erasing recovery. Command is fastboot erase recovery, then flash romracers recovery thru fastboot. Once you have recovery reboot into it and flash any ROM like Alien, Aura whatever you like.
Alien Atrix
See the thing is, fastboot is not an option , it immediately goes to RSD mode. I may have found a fix, and I am now flashing a new SFB with rsdlite
That's another option, noticed you were on 1.5.7 so I would advise 1.8.3 fruitcake sbf. Make sure you battery is fully charged, if your battery gives out during sbf flash you will hard brick your phone.
Alien Atrix
while I was flashing the sfb, the device failed to reenumerate and now it gives me a low battery warning, with no way to charge it, regardless, I have a friend who will let me borrow his battery tommorrow then Ill try to flash again, really I should use the 1.8.3? I just tried to flash the 1.2.6, so Your saying its ok to go forward with a SFB flash? I come from a world of Samsung's so these are all new to me besides the time I had a backflip for a week (ugh).
Are you sure your unlocked the bootloader? If you successfully unlocked you would have unlocked on top right corner of boot screen and have fastboot also.
Alien Atrix
I'm not sure if I have there is nothing that says "unlocked" at the top of the screen, and I could previously access the recovery and fastboot before this. I did not get this phone new, it came from the AT&T dev center or something like that. My dad works there.
You need to charge the battery. I stripped an old USB cable down and used the red with the positive side of the battery and black with the negative using tape to hold them in place then inserted the battery in the phone and plugged the USB in the computer. This allowed me to flash a ROM and unlock bootloader. Etc.
Warning this could harm you're phone. If you cross the wrong wires or touch more then just negative or positive areas of the phone and or battery. Although I didn't have any trouble with it you might.
If in doubt do it the right way buy a battery charger for your battery, use someone's battery or phone to charge yours.
Sent from my MB860 using Tapatalk
Ok Im at my computer, If you are unsure of unlocked bootloader I now recommend you RSD either 1.8.3 with unlocker & preinstall or the newest is 2.3.4 with unlocker & preinstall read this thread about 3 times first http://forum.xda-developers.com/showthread.php?t=1136261
Unlock using fastboot, after you get phone to boot for first time, ADB commands for preinstall root, after root use Root Explorer app then delete "install-recovery.sh" @ /system/etc.
Now you are ready to install the newest recovery by Romracer 3.2, Tenfars is outdated and no support from the developer. Read this thread 2 times http://forum.xda-developers.com/showthread.php?t=1204500 I recomend flashing this recovery thru fastboot per Romracer.
Now you are ready to flash your choice of ROM, follow proper procedure to flash new ROMs thru Recovery.
Also check out the unlocked sim codes thread in general, unlock sim.
If I helped click the thanks button
what Im confused on is what exactly i should flash if I am stuck in a kind of RSD mode bootloop/soft brick?
On your first post you said you were on 1.5.7 correct?
Atrix first released with 1.2.6 then updated to 1.5.7 then updated again to 1.8.3
Bootloader was unlocked with the 1.8.3 update
I updated to 1.2.6>1.5.7>1.8.3 then followed this tutorial http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader[/UR
ok thanks very much! Ill get back to you later once I get a fresh battery.
Ok so I'm about to flash the Pudding .sbf, am I doing this right?
iCracked said:
Ok so I'm about to flash the Pudding .sbf, am I doing this right?
Click to expand...
Click to collapse
yes, that's what you should have done in the first place. you can't do anything with "ROM" in its name without unlocking your bootloader which is why you're in this predicament. unlocked phone (maybe you mean SIM unlocked, free to use on any carrier) is not the same as an unlocked bootloader.
The title of this thread is epic. I lol'd.
Sent from my MB860 using XDA App
defnow said:
The title of this thread is epic. I lol'd.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Definitely laughed myself. I knew it was a 'i bricked my pants'.
I voided my warranty.
pukemon said:
Definitely laughed myself. I knew it was a 'i bricked my pants'.
I voided my warranty.
Click to expand...
Click to collapse
haha thanks guys, yes I am SIM unlocked and everything just said unlocked so maybe I thought the reason they where specific to carrier locking was the radios? haha but I was wrong
It's looking like, at least for some users, unlocking the bootloader on OTA 4.5.141 is causing more issues than the expected soft brick that happens with 4.5.91. When new users are asking about unlocking the latest version, I see the standard advice offered:
- flash pudding sbf (just the unlocker)
- probably get soft-bricked
- issue "fastboot oem unlock" command anyway, reboot & life is great
OR use the one-click BL unlock script.
-----------------
But Nottach said he nearly hard-bricked after flashing pudding while unlocking a stock phone on 4.5.141. He had to do a vol up + power combo WHILE inserting the battery in order to bring it back...
and this user apparently had to do at least a battery pull to complete the process (not sure since posts were edited)...
and still other users are reporting success with the one-click tool.
-----------------
So: is it a fair statement that BL unlocking on the latest version runs an increased risk of bricking the phone, compared with 4.5.91? Is there something else I'm missing here? If I had a stock phone on the latest update I'd be thinking twice about unlocking it.
sheeparecurious said:
It's looking like, at least for some users, unlocking the bootloader on OTA 4.5.141 is causing more issues than the expected soft brick that happens with 4.5.91. When new users are asking about unlocking the latest version, I see the standard advice offered:
- flash pudding sbf (just the unlocker)
- probably get soft-bricked
- issue "fastboot oem unlock" command anyway, reboot & life is great
OR use the one-click BL unlock script.
-----------------
But Nottach said he nearly hard-bricked after flashing pudding while unlocking a stock phone on 4.5.141. He had to do a vol up + power combo WHILE inserting the battery in order to bring it back...
and this user apparently had to do at least a battery pull to complete the process (not sure since posts were edited)...
and still other users are reporting success with the one-click tool.
-----------------
So: is it a fair statement that BL unlocking on the latest version runs an increased risk of bricking the phone, compared with 4.5.91? Is there something else I'm missing here? If I had a stock phone on the latest update I'd be thinking twice about unlocking it.
Click to expand...
Click to collapse
Anybody?
Had to replace my Atrix today, new one already has 4.5.141 on it. Is it safe to unlock the BL using pudding? Or should I wait till the Dev's get it fully worked out?
I'll post my experience/method that I did several times over on my 2 Atrix phones (Both AT&T)
Both phones had unlocked bootloader
I upgraded both phones via the Automatic Update (Motorola Website tool...it downloads the SBF and flashes it to your phone)
At that point you're at 141, stock, unrooted (I did this over unlocked bootloader)
Then I used the Automatic Bootloader Unlock 4.2 to do fastboot oem unlock
I root using preinstall method and restore from Titanium Backup
I have not run into any problems going to and from 141 with unlocked bootloader (I did not try going to FroYo but GB works fine)
I release two ATRIX with GB 2.3.6 Version 4.5.141 very easy
Use RSD Lite 5.7
but the pudding in this link:
http://forum.xda-developers.com/showthread.php?t=1136261
First go to applications and places the phone in debug mode, then turn it off, and plug it in RSD mode and flash with RSD Lite SBF
If for some reason fails you failed to boot OS 0x1000 not detected, goin to RSD mode in 5 seconds
Then use this software
http://forum.xda-developers.com/showthread.php?t=1182871
And utliza the Options for Failed To Apply FIX 0x1000 Boot ", the cel should be in fastboot mode
Write down the key will throw you via commands and then put it again when prompted, after this and you will the unlocked bootloader.
regards
psychephylax said:
I'll post my experience/method that I did several times over on my 2 Atrix phones (Both AT&T)
Both phones had unlocked bootloader
I upgraded both phones via the Automatic Update (Motorola Website tool...it downloads the SBF and flashes it to your phone)
At that point you're at 141, stock, unrooted (I did this over unlocked bootloader)
Click to expand...
Click to collapse
When you did this, did you not get soft-bricked? I know I did.
psychephylax said:
Then I used the Automatic Bootloader Unlock 4.2 to do fastboot oem unlock
I root using preinstall method and restore from Titanium Backup
Click to expand...
Click to collapse
I've done the preinstall, but I can't get CWM to flash the recovery partition.
Can anybody help with reinstalling CWM? Should I flash a pudding / SBF again though I know (based on the contents of ReservedOdm that my BL is still unlocked)?
just wanted to post my experience as i did this a couple of days ago...
i flashed the pudding file (not the one that the automatic unlocker script uses when choosing the 2.3.4/4.5.91 option), got the failed to boot error, put the phone into fastboot mode and did the oem unlock commands (on a PC running winXP), and my bootloader was successfully unlocked. at this point i was able to boot into the stock ROM, with the data partition freshly wiped. i then flashed romracer's cwm using fastboot mode, and then installed the nottachtrix rom. btw i noticed that on the stock rom, cwm would not stay loaded. seems like it gets wiped out after reboot? not sure.
i had previously created a tarball of my data partition and restored it after installing the new rom, but this was a bad idea. better to just use the batch functions of TiBu for the apps, and some sort of sms backup app (from the play store) for keeping your messages.
Just the topic I was looking for. I was trying to unlock my bootloader for this version, but haven't been able to find a guide showing me how and this is my first time.
Has anyone ever seen this before? I have reflashed stock recovery to the phone and before i could switch options in the boot menu i was stuck to only rsd or fastboot. I am on 2.3.5 I sent rdl3 to the phone it restarted in bootloader or fastboot just a moto logo i sent the fastboot oem unlock command, peices of derpunlock and also a system.img. now i can choose android recovery in my boot menu but system still wont load.
Did u try doing factory reset from boot menu
Sent from my MB855 using xda app-developers app
Yes i did try that along with every other option given system still not booting up... but another strange thing ive noticed is that the android recovery is now letting me choose what zip i want to install from my sd card although i cannot because everything keeps failing the signature check. Has anyone been in this same situation?
I think i flashed the ap20bl.img with sv1 but i havnt flashed the microboot because i didnt know what command to issue in fastboot mode. for the bootloader i typed something along the lines of "fastboot flash rdl3.bin rdl3_unlocked.smg" then i think it restarted to only the moto logo was there and i typed fastboot devices it showed my phone so i took the cg file from derpunlock and typed a command like fastboot flash boot cg42_000somthing.smg it said ok finished... ???
sunny530 said:
Has anyone ever seen this before? I have reflashed stock recovery to the phone and before i could switch options in the boot menu i was stuck to only rsd or fastboot. I am on 2.3.5 I sent rdl3 to the phone it restarted in bootloader or fastboot just a moto logo i sent the fastboot oem unlock command, peices of derpunlock and also a system.img. now i can choose android recovery in my boot menu but system still wont load.
Click to expand...
Click to collapse
are you saying you're on 2.3.5? if you are, your bootloader is permanently locked. it won't do any good to try and unlock it, unless you don't mind bricking. otherwise i have never seen this error before.
if you are on 2.3.5 i'd recommend flashing the electrify 2.3.5 sbf method to hopefully unbrick and return to stock.
Thanx for the reply na7q but I am pretty sure when software says unrecoverable error you have just killed it. When you torpedo root doesnt that kill the xorg server? as soon as its dead BAM!!! your rooted lol i would really like it if some very knowledgeable people on this subject would take a look at this and if they all tell me to do the same thing then 2.3.5 electrify here i come, However, i am not concerned of getting my phone in working order if my phone remains dead for the next few days i dont mind as long is it contributes to this bootloader being unlocked.
sunny530 said:
Thanx for the reply na7q but I am pretty sure when software says unrecoverable error you have just killed it. When you torpedo root doesnt that kill the xorg server? as soon as its dead BAM!!! your rooted lol i would really like it if some very knowledgeable people on this subject would take a look at this and if they all tell me to do the same thing then 2.3.5 electrify here i come, However, i am not concerned of getting my phone in working order if my phone remains dead for the next few days i dont mind as long is it contributes to this bootloader being unlocked.
Click to expand...
Click to collapse
with 2.3.5 you aren't unlocking anything. can almost guarantee it! it's going to take a miracle! i'd say just restore it with the SBF if possible and continue on with life haha. i rooted like a year ago so i don't remember anything about it at this point haha. the only thing that was important was unlocking the bootloader! we need a breakthrough on that for these locked users. that miracle hasn't happened yet. or even gotten close.
Try flashing signed boot.img. This seems to me like failed to boot 2 in other words.
You can flash almost anything into the phone, the signature is checked after reboot, so "flashing ok" in fastboot is normal feedback, sometimes even if it's not ok (radio).
Also with recovery, you can choose whatever zip you want, but when you hit install, signature is checked.
Well you see i receive no failure to boot 1-4 i just get stuck at the moto dual core screen with nothing written at the top. Is it possible that i flashed the bootloader sucsessfully and did not flash the microboot? i didnt know the command to issue to flash microboot. The unrecoverable bootloader error seems interesting to me how would i find out what kernal i should/can flash and what would be the command would it be in fastboot? can i install a system.img via recovery or install bootstrap through fastboot or stock recovery?