Related
Hi,
On My atrix I download latest update sent by ATT for Gingerbread, Atrix was rebooted after that and Now I am stuck at error message "Failed To Boot 2" and "Startup RSD Mode". I cannot do anything at this screen. I took out the battery and phone was started but after starting up, immediately will show message "Power off, shutting down" and it will shut down and start in boot mode with the same error messaage "Failed to boot 2". Please help what should I do to come out.
I beleive I can use Motorola PC method to update my phone but since I cannot come out from boot mode, I am not able to even us PC mode.
I had GingerBlur installed, rooted phone before updating the latest ATT update.
I had the same problem. I used rsd to flash froyo with pudding and the problem was solved. I too had tried to unlock the bootloader while on gingerblur. Hope this helps.
Sent from my MB860 using XDA App
lordofthering said:
Hi,
On My atrix I download latest update sent by ATT for Gingerbread, Atrix was rebooted after that and Now I am stuck at error message "Failed To Boot 2" and "Startup RSD Mode". I cannot do anything at this screen. I took out the battery and phone was started but after starting up, immediately will show message "Power off, shutting down" and it will shut down and start in boot mode with the same error messaage "Failed to boot 2". Please help what should I do to come out.
I beleive I can use Motorola PC method to update my phone but since I cannot come out from boot mode, I am not able to even us PC mode.
I had GingerBlur installed, rooted phone before updating the latest ATT update.
Click to expand...
Click to collapse
I used RSD to load the factory SBF ("beta" 5.9.1") and it got me working again. I was running on a stock ROM, though, only rooted.
I have the same problem as the op but wanted to ask a real quick question in regards to this topic. How did you manage to flash back to the orginal sbf? When the phone is plugged in and powered up at this screen, RSD (5.3.1) is unable to detect the phone making it impossible to flash it.
I'm not trying to hijack this post but looking to shed a little insight in case the op is having the same issue.
Thanks!
mikedaman34 said:
I have the same problem as the op but wanted to ask a real quick question in regards to this topic. How did you manage to flash back to the orginal sbf? When the phone is plugged in and powered up at this screen, RSD (5.3.1) is unable to detect the phone making it impossible to flash it.
I'm not trying to hijack this post but looking to shed a little insight in case the op is having the same issue.
Thanks!
Click to expand...
Click to collapse
I thought it wasnt connected either when looking in the upper left pane of RDS. However, the status section under the 2 upper windows showed connected, so I went forward from that. Progress was indicated in the same lower section entry.
Sent from my android!
psyop1 said:
I thought it wasnt connected either when looking in the upper left pane of RDS. However, the status section under the 2 upper windows showed connected, so I went forward from that. Progress was indicated in the same lower section entry.
Sent from my android!
Click to expand...
Click to collapse
Thanks for the follow-up. I will give it a shot tonight and let you know how it goes. I think it was Rom Manager that screwed it up. When it forced the recovery software install, i'm pretty sure that is what caused it. I did have gingerblur installed so might not have been compatible. Just an FYI.
mikedaman34 said:
Thanks for the follow-up. I will give it a shot tonight and let you know how it goes. I think it was Rom Manager that screwed it up. When it forced the recovery software install, i'm pretty sure that is what caused it. I did have gingerblur installed so might not have been compatible. Just an FYI.
Click to expand...
Click to collapse
I had overwritten my stock recovery image as well, which is what caused me to do it this way. Should work for you.
Sent from my android!
psyop1 said:
I had overwritten my stock recovery image as well, which is what caused me to do it this way. Should work for you.
Sent from my android!
Click to expand...
Click to collapse
So I came home tonight and tried it once more on my PC and nothing showed connected. I figured I would give it one more try by installing a fresh copy of RSD Lite and the Moto drivers on my laptop. I plugged in the phone with the error on the screen and it did detect it!
It's currently installing the image (1.8.3 SBF) and at about 6% the error is now gone. Going to cross my fingers and hope for the best. Thanks for all the info and Ill make one final post with the results.
interesting im in the same boat lol
so how does one find a sbf file for the atrix i have the same issue
There are links in the forum to the "prerelease" version which turned out to be the same as the released version.
Sent from my Transformer TF101 using Tapatalk
I had the same problem using 01.97.00R SBF and installing the AT(HoneyComb)RIX with ClockWorkMod.
I solved with the file "ATT 2.3.4 pudding+root" and RSD 5.3.1, it installed Gingerbread plus 01.77.30P SBF
very good
FENZ-IT said:
I had the same problem using 01.97.00R SBF and installing the AT(HoneyComb)RIX with ClockWorkMod.
I solved with the file "ATT 2.3.4 pudding+root" and RSD 5.3.1, it installed Gingerbread plus 01.77.30P SBF
very good
Click to expand...
Click to collapse
Could you explain how to do that?
I run Install update and then it's show "Failed to boot 2.. " everytime
I'm Android newbie and have no experience to fix this.
nuboat said:
Could you explain how to do that?
I run Install update and then it's show "Failed to boot 2.. " everytime
I'm Android newbie and have no experience to fix this.
Click to expand...
Click to collapse
Is your phone unlocked?
Do you have a recovery (CWM) installed?
Edit: I see it has to be...Please give more information about what you´re doing.
If so, just download another rom and follow the flash-instructions using CWM.
As long as you can access the Recovery/Fastboot etc., you can fix things.
DO NOT BLINDLY USE RSDlite and SBF!!! It can turn your phone into a very expensive letter-weight.
I do not know what to do anymore ...
My phone is Hard Brick, AT & T, have no guarantee of any account, and live in the EU.
Jel is worth it in the United States sent in for repair and how much will we charge??
Atrix, or to throw against the wall and forget it ....
Well last night I tried to unlock my brothers Atrix 4G on 2.3.4 using zomgunlock-lite.sbf using RDS Lite.
It failed and the phone was unable to boot with the error code 0x1000.
So basically I thought it was for sure bricked, but I kept looking around. I found nothing.
However I did find this file:
filesonic.com/file/1507329091/1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
Which is apparently like a restored bootloader(or something, i'm new to android), so i plugged the phone into the computer, arrowed down to RSD support or whatever on the phone, and using RSD lite 5.3.1 I managed to flash that file onto the device and get it working again.
Maybe I was never hard bricked in the first place but everyone I found on the internet thought so.
Hope this helped some people, it was a great relief when it worked for me.
After flashing the "zomgunlock-lite.sbf" you could have pulled the battery (then put it back in) and without turning it on just plug back into the computer and it would have turned on by itself and given you a menu in which you would have selected fastboot and then entered the commands for unlocking the bootloader.
I'm glad you got yours working and appreciate the info but there is a way out of it. Actually, someone has created an automatic script for just that occasion here:
http://forum.xda-developers.com/showthread.php?t=1182871
Just follow the directions for the error.
ravicus said:
Well last night I tried to unlock my brothers Atrix 4G on 2.3.4 using zomgunlock-lite.sbf using RDS Lite.
It failed and the phone was unable to boot with the error code 0x1000.
So basically I thought it was for sure bricked, but I kept looking around. I found nothing.
However I did find this file:
filesonic.com/file/1507329091/1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
Which is apparently like a restored bootloader(or something, i'm new to android), so i plugged the phone into the computer, arrowed down to RSD support or whatever on the phone, and using RSD lite 5.3.1 I managed to flash that file onto the device and get it working again.
Maybe I was never hard bricked in the first place but everyone I found on the internet thought so.
Hope this helped some people, it was a great relief when it worked for me.
Click to expand...
Click to collapse
glad you're phone is ok, but yea you were not hard bricked. You just had to redo the OEM unlock command in fastboot one more time. The hard brick is when trying to downgrade, not from flashing pudding and it takes away the ability to RSD or fastboot. If those options are there then there's a way out.
I think a mod should change title so people aren't getting false hope.
You were soft bricked. Unlocking a stock 2.3.4 phone always results in a 0x1000 No OS error, at which point you are supposed to choose fastboot before the 5 seconds are up (or reboot into fastboot mode if you miss the 5 second window) and run fastboot oem unlock once to get the unique key and then again with the key followed by a fastboot reboot.
I repeat, all unlock attempts on stock 2.3.4 OTA Atrices will result in this temporary soft brick.
This thread really did me a massive favor in telling me exactly what I was searching for when google was being useless. Thank you guys. Particularly the post above mine about soft bricks.
ravicus said:
Well last night I tried to unlock my brothers Atrix 4G on 2.3.4 using zomgunlock-lite.sbf using RDS Lite.
It failed and the phone was unable to boot with the error code 0x1000.
So basically I thought it was for sure bricked, but I kept looking around. I found nothing.
However I did find this file:
filesonic.com/file/1507329091/1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
Which is apparently like a restored bootloader(or something, i'm new to android), so i plugged the phone into the computer, arrowed down to RSD support or whatever on the phone, and using RSD lite 5.3.1 I managed to flash that file onto the device and get it working again.
Maybe I was never hard bricked in the first place but everyone I found on the internet thought so.
Hope this helped some people, it was a great relief when it worked for me.
Click to expand...
Click to collapse
Massive n00b post, nothing but misinformation.
Sweet.....
soft brick could be fixed.. my phone is hard one, can not be read by PC.. it is always booting loop.
and blemeIf
I have also hard bricked my Atrix. I have read many post on this forum and on google that phone can not be recovered after hard brick. Is it confirmed that there is no way to recover after a hard bricked? Please help.
mysticdrew said:
glad you're phone is ok, but yea you were not hard bricked. You just had to redo the OEM unlock command in fastboot one more time. The hard brick is when trying to downgrade, not from flashing pudding and it takes away the ability to RSD or fastboot. If those options are there then there's a way out.
I think a mod should change title so people aren't getting false hope.
Click to expand...
Click to collapse
So, i did try to downgrade using RSD lite since nothing seemed to work when i was stuck at the unlocked M screen despite flashing 3 different roms via CWM. Now i get the error message failed to boot 0x1000, but there are no options at all and my phone just goes to black after 1sec. this is considered hard bricked correct? and there is nothing i can do other than send it into motorola
patsprobst said:
So, i did try to downgrade using RSD lite since nothing seemed to work when i was stuck at the unlocked M screen despite flashing 3 different roms via CWM. Now i get the error message failed to boot 0x1000, but there are no options at all and my phone just goes to black after 1sec. this is considered hard bricked correct? and there is nothing i can do other than send it into motorola
Click to expand...
Click to collapse
Try http://forum.xda-developers.com/showthread.php?t=1648947
dcarpenter85 said:
You were soft bricked. Unlocking a stock 2.3.4 phone always results in a 0x1000 No OS error, at which point you are supposed to choose fastboot before the 5 seconds are up (or reboot into fastboot mode if you miss the 5 second window) and run fastboot oem unlock once to get the unique key and then again with the key followed by a fastboot reboot.
I repeat, all unlock attempts on stock 2.3.4 OTA Atrices will result in this temporary soft brick.
Click to expand...
Click to collapse
I can't believe it was so hard to find these particular instructions and that it is not listed anywhere on the sbf file. Thank you so much for your answer and the last sentence should be added to the sbf file. Actually your whole statement should be there. Thanks a lot. Saved me a lot of anguish.
Alright here goes
So my question is, what options do i have? I can't access any recovery options (Fastboot, android recovery, etc) and my RSD lite wont connect.
Short Story
Every time i try to boot my Atrix (after trying to update CherryPi), I get the Failed to boot 2, Starting RSD mode. Unfortunately, when I plug my phone into a computer RSD doesn't see it. It's like its not even phased.
Long Story
Okay, so I got my atrix not too long ago. Got my phone rooted at proceeded to use gingerblur. Then shortly there after, I attempted to upgrade to the Gingerbread OTA update, which got me stuck in a boot loop. (Now I'm a little confused, I don't think that I have unlocked my phone at all. I don't ever recall "unlocked" being on the boot screen at all). From this point I don't think RSD was working. I spent about a week trying to get it to work. Then I was able to fastboot flash the stock img files for gingerbread to my phone. So now I had a working gingerbread atrix. I sat stock for a little while, figgured out how to root via fastboot (again, no rsd support at this point). After I was rooted I installed CherryPi 0.3 via CWM. It worked great, a couple of days later I went to do the CherryPi 0.X > 0.5 and it flashed with CWM "successfully" got to the AT&T logo on bootup and then crashed and has been giving me the failed to boot 2.
I hope i've given you guys enough info. If any of you super hackers live in San Diego, I'd be more then willing to bring my phone over for you to figure out. So I just really need to know what my options are. If I take it back to AT&T will they likely give me a new one? (I'm good at playing dumb). I traded my phone originally so I don't know what kind of warranty is in place. Can I contact Motorola and get a new handset? Just looking for suggestions.
Thanks guys
Have you tried to reinstall the motorola driver?
Yes, when I first "lost" RSD support and since the current "Failed to boot 2" message.
It has the flash interface when I plug it in, but the motorola software dosent see it, same with RSD. just like nothing is plugged in.
Why not put it into fastboot mode when it reboots and then flash a different file?
phobos512 said:
Why not put it into fastboot mode when it reboots and then flash a different file?
Click to expand...
Click to collapse
It won't boot into any other mode, upon putting the battery in, it shows the dual core logo for about 1.5-2 seconds that pops up the "Failed to boot 2" message and starting RSD mode.
Judging by your first post u mentioned that u never unlocked your boot loader, unless I'm reading this wrong. These ROMS weren't meant to be flashed with the Bootstrapped version of CWM (The one that requires u to be plugged in to AC power) so not sure if that sheds any light on the subject or not. Again, if I read your post wrong, I apologize.
Sent from my MB860 using XDA Premium App
Phalanx7621 said:
Judging by your first post u mentioned that u never unlocked your boot loader, unless I'm reading this wrong. These ROMS weren't meant to be flashed with the Bootstrapped version of CWM (The one that requires u to be plugged in to AC power) so not sure if that sheds any light on the subject or not. Again, if I read your post wrong, I apologize.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Ya, from what I can tell its Motorola locking me out for using an modified rom. But I think that I should be able to return to a stock firmware using RSD lite or the Motorola software restore from thier site, but neither see my phone connected. This leads me to belive that somewhere in the process the RSD protocol got messed up. Now I really don't know much, just enough to be dangerous. So if theres anyone that can tell me if I'm even looking the right direction.
And if I am right is there anything I could possibly do?
gjRabbit said:
Alright here goes
So my question is, what options do i have? I can't access any recovery options (Fastboot, android recovery, etc) and my RSD lite wont connect.
Short Story
Every time i try to boot my Atrix (after trying to update CherryPi), I get the Failed to boot 2, Starting RSD mode. Unfortunately, when I plug my phone into a computer RSD doesn't see it. It's like its not even phased.
Long Story
Okay, so I got my atrix not too long ago. Got my phone rooted at proceeded to use gingerblur. Then shortly there after, I attempted to upgrade to the Gingerbread OTA update, which got me stuck in a boot loop. (Now I'm a little confused, I don't think that I have unlocked my phone at all. I don't ever recall "unlocked" being on the boot screen at all). From this point I don't think RSD was working. I spent about a week trying to get it to work. Then I was able to fastboot flash the stock img files for gingerbread to my phone. So now I had a working gingerbread atrix. I sat stock for a little while, figgured out how to root via fastboot (again, no rsd support at this point). After I was rooted I installed CherryPi 0.3 via CWM. It worked great, a couple of days later I went to do the CherryPi 0.X > 0.5 and it flashed with CWM "successfully" got to the AT&T logo on bootup and then crashed and has been giving me the failed to boot 2.
I hope i've given you guys enough info. If any of you super hackers live in San Diego, I'd be more then willing to bring my phone over for you to figure out. So I just really need to know what my options are. If I take it back to AT&T will they likely give me a new one? (I'm good at playing dumb). I traded my phone originally so I don't know what kind of warranty is in place. Can I contact Motorola and get a new handset? Just looking for suggestions.
Thanks guys
Click to expand...
Click to collapse
Hey man, I have the same problem with you.. have you some progress for that..
I find some infor from forum that this kind of hard brick can be solved by using the developping cable to reflash the sbk file, this method is pending at the SBK file is unavailable which is not released out by MOtorola.. I find a one of my friend who is working in MOTO (Tianjing, CHINA) to see my device, I hope he can help me to unbrick my phone.. when i have good news, I'll update it.
Hi all,
first up, after having spent three days going through the forums I've come up empty on a problem I'm currently experiencing. I'm not a complete n00b on this stuff but currently I'm stuck so hopefully someone can help me.
Backstory:
Bell Atrix, with root but a locked bootloader received and successfully installed the OTA 2.3.4 update last week.
I'm in Australia so am running on the Telstra Network. (not in Canada on the Bell).
After the upgrade, I had the problem with 3G+ Data, so started to investigate.
Tried to follow the instructions given here:
(fastboot) 2.3.4 OrangeFR (Jul5: 4.5.2A-11) w/ RAM fix for Intl. unlocked
So, I tried unlocking the bootloader to flash the files mentioned (system.img). Ultimately I've now concluded that I mustn't have unlocked the bootloader successfully.
After system.img had moto-fastbooted across, when booting I currently get the 'famous':
Failed to boot 4
Starting RSD
So, off I went to RSDLite, with the latest install, the latest moto drivers, and armed with the IHOP_Bell.sbf, I thought I'd try RSD'ing that to my phone.
It gave me SUCCESS, but still no fastboot access.
So I tried intl-fix-try1.sbf [inside the IHOP_Bell.rar] with the same results.
Still Failed to Boot 4.
Now, from all the reading it sounds like I need to flash an entire sbf to my phone.
That's OK, but I can't find one that I feel safe dropping on there.
All of the talk is that flashing a Froyo SBF to a phone that has been OTA updated to 2.3.4 is Baaaaaaad (ie hard brick), and the only 2.3.4 available appears to be the ATT one.
Am I missing something incredibly obvious here?
I've been through the pudding thread, and the SBF thread at length but remain none the wiser. Until I can either unlock my bootloader, and have fastboot access, there's not much I can do.
Seems the way to do this is with a full ROM.
Any of you good people out there able to help a fella?
cheers
Sorry, I should also add that I can't seem to get to fastboot either.
When I plug in the phone to USB, green light comes on.
Then, I press power button again, green light is brighhter and it starts the moto screen.
After about 8 sec the Failed to boot 4 message comes up.
So I tried fastboot, power on with vol down button held.
Exactly the same outcome, no fastboot access it seems.
can you get into RSD lite mode by starting up the phone with the volume UP button and power held?
Phalanx7621 said:
can you get into RSD lite mode by starting up the phone with the volume UP button and power held?
Click to expand...
Click to collapse
Thanks for the reply mate.
Whether I hold vol-up during the boot doesn't seem to make a difference - it still boots to:
Failed to Boot 4
Starting RSD Mode
From there though RSDLite (windows 7/latest version/latest moto drivers) does recognise the phone via USB.
I am able to flash that pudding IHOP sbf to the phone (but after doing so it seems to have no effect. I can't get to the next step due to a lack of fastboot access).
So I'm comfortable that I can make an RSD connection from PC to phone, but from there can't seem to make much progress.
Thanks
Just wondering if anyone's got any clues on how to fix this one? I've been quoted $180 to fix but if anyone's happy to do it for less I'll pay... I'm in Australia...
Hi XDA, been lurking for a while and today decided to start posting, beginning with a relatively urgent question.
My brother's been marveling at the ability to flash custom ROMs onto my Galaxy S2, and decided he wanted to root his Atrix today. Rooting process went well (he used Pete's Motorola Root Tools) and then flashed CWM through ROM Manager, but did NOT unlock his bootloader. After CWM was purportedly done, he put a ROM onto his HDD, turned the phone off, and attempted to boot into CWM. He was greeted with an error message, "Failure to Boot 2, Starting RSD Mode", which pops up whether he tries to turn on the phone normally or by holding the volume button down. Taking out the battery doesn't help.
Now, my assumption is that because he didn't unlock his bootloader, he's getting this error, but my experience with Android dev is limited. So, how would I go about fixing this? My only concern is getting the phone back to a working state, we don't care about the data on it.
Thank you for the time taken to read and answer this question, any and all help is appreciated.
Warm Regards,
Leo
EDIT: Just want to make sure, I did a fair amount of searching before I made this thread and found a bunch of answers, just not sure which one I should do. One thread champions just unlocking the bootloader, others suggest flashing an OEM ROM, which I'm not sure how to do without CWM. Essentially I'm just looking for some guidance and would deeply appreciate any help I can get.
EDIT 2: Forgot to add - he was running 2.2.1 stock. Root was successful. Feel free to ask any questions if necessary.
UPDATE: I've been trying to use these instructions to unlock the bootloader, but I'm stuck on the step that asks you to reboot your phone into RSD mode. The phone doesn't boot without being plugged in, and gives me the following error when I do:
Failed to Boot 2, Starting RSD Mode
"Battery is too low to Flash". Right now the phone's plugged into the wall with this message displaying,
It also goes without saying that RSD Mode, in fact, is never started .
Added some more information (apparently new members aren't allowed to post links, so added the information as UPDATE in the original post).
Again, thanks for your help and suggestions.
Bump, somebody please weigh in.
- Leo
Sent from my i777 using Tapatalk, on ICScrweD 2.1
FatalFlaw said:
Hi XDA, been lurking for a while and today decided to start posting, beginning with a relatively urgent question.
My brother's been marveling at the ability to flash custom ROMs onto my Galaxy S2, and decided he wanted to root his Atrix today. Rooting process went well (he used Pete's Motorola Root Tools) and then flashed CWM through ROM Manager, but did NOT unlock his bootloader. After CWM was purportedly done, he put a ROM onto his HDD, turned the phone off, and attempted to boot into CWM. He was greeted with an error message, "Failure to Boot 2, Starting RSD Mode", which pops up whether he tries to turn on the phone normally or by holding the volume button down. Taking out the battery doesn't help.
Now, my assumption is that because he didn't unlock his bootloader, he's getting this error, but my experience with Android dev is limited. So, how would I go about fixing this? My only concern is getting the phone back to a working state, we don't care about the data on it.
Thank you for the time taken to read and answer this question, any and all help is appreciated.
Warm Regards,
Leo
EDIT: Just want to make sure, I did a fair amount of searching before I made this thread and found a bunch of answers, just not sure which one I should do. One thread champions just unlocking the bootloader, others suggest flashing an OEM ROM, which I'm not sure how to do without CWM. Essentially I'm just looking for some guidance and would deeply appreciate any help I can get.
EDIT 2: Forgot to add - he was running 2.2.1 stock. Root was successful. Feel free to ask any questions if necessary.
UPDATE: I've been trying to use these instructions to unlock the bootloader, but I'm stuck on the step that asks you to reboot your phone into RSD mode. The phone doesn't boot without being plugged in, and gives me the following error when I do:
Failed to Boot 2, Starting RSD Mode
"Battery is too low to Flash". Right now the phone's plugged into the wall with this message displaying,
It also goes without saying that RSD Mode, in fact, is never started .
Click to expand...
Click to collapse
You are correct in just trying to unlock the BL. Unfortunately, you will need a charged battery to do so. If you don't have access to a different battery, you can go to an AT&T store and they should charge it for you.
The OEM you're referring to is a full .sbf, instead of just the smaller "unlock" .sbf. That is an option, but in all honesty, unlocking the BL should be the quickest way to fix your situation.
If you run into any problems, let us know.
Thanks for the advice, it's immensely reassuring. He went to an AT&T store and they were unhelpful, refused to charge it for him I'm going to order a battery charger off Amazon and charge it that way, and will post here when I have results.
In the meantime if anyone else has something to add it would be quite appreciated.
Thanks,
Leo
Sent from my i777 using Tapatalk, on ICScrweD 2.1
Alright, we've run into a problem.
The screen never gets past the error message "Failure to Boot 2, Starting RSD Mode". We turn it off, hold power and up at the same time, and it still boots to that message. I press the power button and hold the volume up button, nothing changes.
The battery is charged.
Is there something I'm missing here?
FatalFlaw said:
Alright, we've run into a problem.
The screen never gets past the error message "Failure to Boot 2, Starting RSD Mode". We turn it off, hold power and up at the same time, and it still boots to that message. I press the power button and hold the volume up button, nothing changes.
The battery is charged.
Is there something I'm missing here?
Click to expand...
Click to collapse
The .sbf's are flashed while your phone is in RSD Mode
in order to charge your battery (to fix the "Battery is too low" message) you will need to sacrifice any USB cable, cut it open and tape the red and black wires to the battery. (Red goes on +, Black goes on -)
ghost_og said:
The .sbf's are flashed while your phone is in RSD Mode
Click to expand...
Click to collapse
Yep, I realized that. I thought "Starting RSD Mode" would at some point subside, and it would say something along the lines of "In RSD Mode" or something. But he flashed an unlock SBF and got it unlocked. He now has a beautiful Atrix running ICS MIUI.
Thank you all for the help.
Same problem but the solution does not work for me
I am in the same boat. I downloaded RSD 5.9 and used the file in pudding.rar. After I loaded the file, RSD said it passed with 100% load but the phone is still stuck in the same place. Can anyone help?