I'm getting the "Failed to boot 2, then RSD Starting." I've read that I may not have the correct files, or possibly I'm doing something wrong. Can someone dumb down the correction to my issue? I want to get into recovery, so that I can back up and then install CM7. I think I have the latest versions of everything.
Any help is appreciated. Sorry if this is a repost
Have you unlocked your bootloader ?
I had this *exact* same problem. It occurred as I tried to flash ROM Manager's recovery (from ROM Manager) *before* I unlocked the bootloader. IE, I tried to flash the recovery partition before I was unlocked. I could never recover. I tried the AUTOMATIC... unlock batch program - many options, just about everything.
I ended up using Motorola's official MSU to recover to stock. Then I ran the AUTOMATIC... unlock batch program first. Once unlocked, it was pretty simple after that.
Problems with CWM recovery
jmaddr said:
I had this *exact* same problem. It occurred as I tried to flash ROM Manager's recovery (from ROM Manager) *before* I unlocked the bootloader. IE, I tried to flash the recovery partition before I was unlocked. I could never recover. I tried the AUTOMATIC... unlock batch program - many options, just about everything.
I ended up using Motorola's official MSU to recover to stock. Then I ran the AUTOMATIC... unlock batch program first. Once unlocked, it was pretty simple after that.
Click to expand...
Click to collapse
Hello, i've the same problem. I need to ask before do what you do because i'm a noob. i'm rooted and i flashed CWR
1-Doing the MSU stock recover will hard brick my phone?
2-i've been reading the "What's in this Software Update?" and is says it's for 2.3 GB. It will works for me? i'm 2.2.2 froyo.
I was searching but can't find answers.
Sorry about my english
Thanks
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
Alright, I unlocked my ATT Atrix while it was on the stock 1.8.3 sbf. I installed tenfars CWM next. Then I installed kenns Ginger Blur ROM. After that I flashed back to stock 1.8.3 with the SBF file located here http://forum.xda-developers.com/showthread.php?t=1125944
I used this one:
Branding: AT&T US
Version: 1.8.3 Full
Android Version: 2.2.2
Bootloader Version: N/A
Webtop version: 4.257.30
Requires RSD Lite 5.0.0
Requires Moto Android (De)packer 1.3 to edit.
My phone no longer said unlocked at boot. I then went on to do the OTA update to 4.5.91 so that I would have gingerbread.
My question is, am I still unlocked? When I try to boot into android recovery, I get a caution symbol with an android standing next to it. I am no longer rooted either. I have read that you need to use CWM in order to root the Atrix on Gingerbread, but I can't use CWM. So will I have to wait?
I managed to get it rooted via the preinstall.img trick. When I installed ROM manager and flashed CWM it said it flashed successfully. Upon trying to boot into recovery I now get the message "Failed to boot 2." Do I have to unlock it again? I didn't try that first out of fear for bricking. Any help is appreciated
jadwv2210 said:
I managed to get it rooted via the preinstall.img trick. When I installed ROM manager and flashed CWM it said it flashed successfully. Upon trying to boot into recovery I now get the message "Failed to boot 2." Do I have to unlock it again? I didn't try that first out of fear for bricking. Any help is appreciated
Click to expand...
Click to collapse
You're semi unlocked. Usually you just have to reflash pudding again (but don't need to do the oem unlock). So that would be the first thing I would do.
Next, flash tenfars unlocked CWM (make sure to delete the file that it tells you... installrecovery.sh or something). I would use that rather than the rom manager cwm at this time.
mysticdrew said:
You're semi unlocked. Usually you just have to reflash pudding again (but don't need to do the oem unlock). So that would be the first thing I would do.
Next, flash tenfars unlocked CWM (make sure to delete the file that it tells you... installrecovery.sh or something). I would use that rather than the rom manager cwm at this time.
Click to expand...
Click to collapse
Alright so I just need to flash the same unlocked sbf file that I flashed when I unlocked on 1.8.3? The one called zomgunlock-lite.sbf?
jadwv2210 said:
Alright so I just need to flash the same unlocked sbf file that I flashed when I unlocked on 1.8.3? The one called zomgunlock-lite.sbf?
Click to expand...
Click to collapse
Yea, although (i haven't kept up), but the original pudding thread has updated the "pudding" file to resolve some memory timing issues so might want to download that.
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.
Need some help please.
I have Telstra Atrix with ota gingerbread, unlocked BL, rooted.
I can't get it to boot into cwm recovery.
I installed ROM Manager from market, flashed CWM 2.0.2.0 , selected Reboot into Recovery but it only gets to the triangle. From there I can hold down Vol Up+VolDown and get to Basic Android recovery.
I have deleted the racing car app as suggested in one thread to make room, but no help.
If I power off and boot it from Power+Vol Down it comes up "Failed to boot 2"
Can't find a solution in XDA or Google. Any help appreciated.
See if you can fastboot flash a recovery image
sent from my Atrix via XDA premium
Most likely need to delete "install-recovery.sh" @ /system/etc, if it's there, then try re-installing CWM Recovery, and see if that works.
Thanks fellas.
Turns out I had lost my unlock BL by flashing the Telstra Froyo sbf from the xda Atrix Firmwares Superthread.
Reflashed the pudding and it's unlocked again. Actually romracer explained it better in his thread. I thought you couldn't relock bootloader. CWM recovery works now.
Thanks fellas.
Turns out I had lost my unlock BL by flashing the Telstra Froyo sbf from the xda Atrix Firmwares Superthread.
Reflashed the pudding and it's unlocked again. Actually romracer explained it better in his thread. I thought you couldn't relock bootloader. CWM recovery works now.
U can't actually relock the boot loader, it "Burns a fuse" inside the unit when u unlock. But flashing an .sbf makes it appear as if it's locked again.
Sent from my MB860 using Tapatalk
Phalanx7621 said:
U can't actually relock the boot loader, it "Burns a fuse" inside the unit when u unlock. But flashing an .sbf makes it appear as if it's locked again.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Yeah thanks. Romracer explained it to me. It doesn't seem to be common knowledge at all. So people flashing sbf's of stock roms are effectively losing root. I spent hours trying to figure it out and get info searching and asking questions. Anyway, all good now and I appreciate the assistance.
On another point do you know how I can get the Telstra radio so I can use it with custom roms? My phone use is way better since installing Telstra stock Gingerbread ota. If I flash another rom I'll lose it won't I? It is N_01.100.00R
Edit: thanks to @Msd24200 and @marko! for pointing out that Radio remains unchanged when flashing cm7. Also discovered where to get the zip of this radio if I lose it http://forum.xda-developers.com/showpost.php?p=15787709&postcount=1
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.