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 ....
Related
Hi all.
I'm in dire need of help...
I was glad to see the gingerbread update popping up on my atrix...so i got home (better internet) and did the update. Everything seemed fine until i tried to put the phone to sleep (pushed the power button). The thing just rebooted. Tried it again and the same thing happened...next time it turned on i just waited for it to go to sleep mode by itself and again it booted.
Searching the forums, the answers pointed me to the direction of a factory reset...and away i went...to no new results. It just kept on booting. So i decided to do a rollback do the previous version and that's when it got ugly. RSD gave me a FAIL in the flashing process and now i cant boot the phone.
Thing is...it gives me the black and white screen saying it couldn't boot, but as soon as the RSD mode msg shows up it just turns of. I can't get it to stay on for the usb to pick the phone up...
how am i supposed to retry to flash it again?!
ANY help would come in handy...i'm about to loose hope.
Thanks in advance!
-claudio
are you getting a screen with just...
(SVF message: 105:1:2 failed to boot 0x1000)
or something like this?
No OS detected, going to rsd mode in 5seconds press a key to stop count down available modes are:
1)rsd
2)fastboot
3)NvFlash
4)Bp HW Bypass rsd
5)BP HW bypass QC Dload
6)BP HW diag & Boot AP
7)BP HW Bypass BP only
8)BP SW Bypass RSD
9)Android recovery
10)boot android (no BP)
11)Device UID
12)console=tty50,115200n8
13 Early USB enumeration
14)BP tools
Did you not read the WARNING thread? It's stickied and is called WARNING for a reason.
[WARNING] Hard Brick with Official 4.5.91 Update
http://forum.xda-developers.com/showthread.php?t=1160408
If the error is indeed (SVF message: 105:1:2 failed to boot 0x1000), you are SoL.
Defnow...i keep getting the first msg. followed by a REALLY quick one about RSD and then the phone shuts off...to the point where i need to take the battery out so i can look at the msg again. Edgeicator was right on target with the link.
Edgeicator, you got it right...unfortunately i didn't read the post...the shock of loosing a phone like this (specially living in Brazil) was enough to have me trying everything i could...i did read a couple of posts where people was being told to try the rollback...i was stupid and unlucky...a dangerous combination.
So i guess there's no solution in sight? should i just prepare myself psychologically to buy ANOTHER phone?
Thanks for the answer guys.
hard brick man. Sorry.
Sent from my MB860 using XDA App
if u can somehow get the phone to stay on and be recognized in RSD u could try to flash the pudding sbf then fast boot and load the system and boot.img files from the fruitcakes thread. Otherwise ull be buyin a new phone if u cant get a warranty replacement.
GeekIndustries said:
Defnow...i keep getting the first msg. followed by a REALLY quick one about RSD and then the phone shuts off...to the point where i need to take the battery out so i can look at the msg again. Edgeicator was right on target with the link.
Edgeicator, you got it right...unfortunately i didn't read the post...the shock of loosing a phone like this (specially living in Brazil) was enough to have me trying everything i could...i did read a couple of posts where people was being told to try the rollback...i was stupid and unlucky...a dangerous combination.
So i guess there's no solution in sight? should i just prepare myself psychologically to buy ANOTHER phone?
Thanks for the answer guys.
Click to expand...
Click to collapse
I believe if its still under warranty you call up the ATT guys which will direct you to the Moto guys and they will ask you to ship your phone to them to fix since its a software related issue.
And how the hell do you manage to HARD BRICK your phone even with all these threads and warnings.
One question though, when you boot up the phone does the computer recognize it? I believe if it does you still can fix it.
Yeah i thought so...it sucks, but its good learning.
As i said before, searched around the web and got a couple posts, all pointing in the direction of a rollback, even if already updated to 2.3.4 ...bad luck for me.
I already sent msgs to those threads so they post a big ass red warning so no one will follow the same path.
...time to ponder my next buy...should i go for a replacement Atrix...should i try the galaxy 2s...should i get a crappy phone and wait for Atrix2?
GeekIndustries said:
Hi all.
I'm in dire need of help...
I was glad to see the gingerbread update popping up on my atrix...so i got home (better internet) and did the update. Everything seemed fine until i tried to put the phone to sleep (pushed the power button). The thing just rebooted. Tried it again and the same thing happened...next time it turned on i just waited for it to go to sleep mode by itself and again it booted.
Searching the forums, the answers pointed me to the direction of a factory reset...and away i went...to no new results. It just kept on booting. So i decided to do a rollback do the previous version and that's when it got ugly. RSD gave me a FAIL in the flashing process and now i cant boot the phone.
Thing is...it gives me the black and white screen saying it couldn't boot, but as soon as the RSD mode msg shows up it just turns of. I can't get it to stay on for the usb to pick the phone up...
how am i supposed to retry to flash it again?!
ANY help would come in handy...i'm about to loose hope.
Thanks in advance!
-claudio
Click to expand...
Click to collapse
Another one bites the dust...Sounds like a HARD Brick. Ginger*ucked!!
GeekIndustries said:
Hi all.
I'm in dire need of help...
I was glad to see the gingerbread update popping up on my atrix...so i got home (better internet) and did the update. Everything seemed fine until i tried to put the phone to sleep (pushed the power button). The thing just rebooted. Tried it again and the same thing happened...next time it turned on i just waited for it to go to sleep mode by itself and again it booted.
Searching the forums, the answers pointed me to the direction of a factory reset...and away i went...to no new results. It just kept on booting. So i decided to do a rollback do the previous version and that's when it got ugly. RSD gave me a FAIL in the flashing process and now i cant boot the phone.
Thing is...it gives me the black and white screen saying it couldn't boot, but as soon as the RSD mode msg shows up it just turns of. I can't get it to stay on for the usb to pick the phone up...
how am i supposed to retry to flash it again?!
ANY help would come in handy...i'm about to loose hope.
Thanks in advance!
-claudio
Click to expand...
Click to collapse
Another one bites the dust...Sounds like a HARD Brick. Ginger*ucked!!
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.
I am a new Android convert and purchased the Photon 4G last week. I successfully rooted, though I have not unlocked the bootloader. I flashed the Photon Laser 1.1 ROM, and then the Alien 1.1 Rom and theme. After noticing that I had no 3G/4G, I decided to revert to stock and avoid the Alien 1.1 for now. I went into Clockworkmod and wiped the dalvik cache, which I think was my major mistake, then in android recovery mode I wiped the cache 3 times, and did a factory restore. From this point forward I can not boot the phone successfully. Once it comes up to the tap the android to begin screen, I receive multiple error messages requesting the calander, phone, and other apps be force closed. I am unable to get into the phone at all. Additionally, if I tap the android icon, I can see the icon flex indicating my tap, but nothing happens. I've spent the last 6 hours attempting to use RSD Lite to reflash the stock image, but I receive an error each time stating "Failed flashing process. Unable to retrieve initialization values from INI file. (0x7029); phone connected." I need some direction from anyone that can help. Thank you in advance.
WEC2011 said:
I am a new Android convert and purchased the Photon 4G last week. I successfully rooted, though I have not unlocked the bootloader. I flashed the Photon Laser 1.1 ROM, and then the Alien 1.1 Rom and theme. After noticing that I had no 3G/4G, I decided to revert to stock and avoid the Alien 1.1 for now. I went into Clockworkmod and wiped the dalvik cache, which I think was my major mistake, then in android recovery mode I wiped the cache 3 times, and did a factory restore. From this point forward I can not boot the phone successfully. Once it comes up to the tap the android to begin screen, I receive multiple error messages requesting the calander, phone, and other apps be force closed. I am unable to get into the phone at all. Additionally, if I tap the android icon, I can see the icon flex indicating my tap, but nothing happens. I've spent the last 6 hours attempting to use RSD Lite to reflash the stock image, but I receive an error each time stating "Failed flashing process. Unable to retrieve initialization values from INI file. (0x7029); phone connected." I need some direction from anyone that can help. Thank you in advance.
Click to expand...
Click to collapse
Hey, I just wanted to confirm that you used RSDlite to flash the Final SBF release...45.2.5? And that didn't work? I've had issues with RSDlite attempting flash and then fail on me too. In that case, my phone would turn on into the Moto-boot logo, and then get stuck. I took the battery out and put it back in and it seemed to get me back into the phone after booting. Maybe you can try to reflash the final 45.2.5 update again?? Try using the cmd terminal to reboot or push files onto the phone? Sorry I don't know too much..I'm still really new to android.
I have followed the exact steps from this page: (http://forum.xda-developers.com/showthread.php?p=16328237), but every time RSD Lite fails with the error message I listed in the original post. I have pulled the battery several times, but am unable to get past the "tap the Android" screen. Tapping it leads to no change at all. I have no access to CWM anymore, and can only access recovery from Android recovery now, which I have used to reboot a few times at this point. When I reboot, I am greeted with errors that include "The process com.android.phone has stopped unexpectedly. Please try again." and "The application Suggestions Poll Scheduler Service (process com.motorola..suggestions.scheduler) has stopped unexpectedly. Please try again." and "The application Calander Storage (process com.android.calendar has stopped unexpectedly. Please try again."
WEC2011 said:
I have followed the exact steps from this page: (http://forum.xda-developers.com/showthread.php?p=16328237), but every time RSD Lite fails with the error message I listed in the original post. I have pulled the battery several times, but am unable to get past the "tap the Android" screen. Tapping it leads to no change at all. I have no access to CWM anymore, and can only access recovery from Android recovery now, which I have used to reboot a few times at this point. When I reboot, I am greeted with errors that include "The process com.android.phone has stopped unexpectedly. Please try again." and "The application Suggestions Poll Scheduler Service (process com.motorola..suggestions.scheduler) has stopped unexpectedly. Please try again." and "The application Calander Storage (process com.android.calendar has stopped unexpectedly. Please try again."
Click to expand...
Click to collapse
I know it's somewhere in this forum, but if you brick your phone and render it useless, you can try and reflash the original SBF...not the update. Give it a shot. Just let the force closes go, but see if you can connect to your computer. Best of luck!
Thanks, but I think that's what I was doing. Maybe it was the update. Can anyone point me to the original sbf? Thanks again for the replies.
http://www.multiupload.com/FNZKNV0T3G
thats the link, u need to unzip and then mount it on RSDlite
Thank you so much. I will download now and run it. Let you know if it finally works. Thank you for the link and help.
So nothing under the sun worked at all. I ended up having to take the phone back to the retailer and received a new one. I am happy now because after two days I have a functioning phone. I still believe that my error was clearing the dalvik cache before the factory reset, but I wouldn't have done that had the Alien ROM, which I mostly liked, hadn't killed my non-wifi data reception, as in I had none. Thank you the those of you who took time out to read and post a reply to help me. I am very grateful.
Help
Hey guys:
Yesterday I made mega mistake, I've flashed CM7 but... I didn't notice that I had to unlock the bootloader, obviously didn't work , but now, the phone is stuck on "unable to boot 2 entering RSD mode" with the Moto logo, so I tough, I will flash it again with the official Sprint update and fix the whole thing, but RSD gets to 100% restarts the phone and then phone shows just garbage! just like a blurry image, can't describe correctly but doesn't go any further. I've removed the battery start the phone again and then I get the same message "unable to boot 2 entering RSD mode". I'm on a loop right now, any advise will very appreciated, thanks'
Try flashing the 154_5 sbf...when in rsd mode...ive always had luck,with it as a starting point.
Sent from my MB855 using xda premium
KTT16 said:
Try flashing the 154_5 sbf...when in rsd mode...ive always had luck,with it as a starting point.
I will certainly give it a shot. I don't remember right now which file is the one that i got, I'm at work, but took me about 2 days in a row to download the file on my 128 kbps connection... third world connection.. I know.
Something that I would like to know is, when I turn the phone on takes directly to the error, if I press power + volume up then takes me to fast boot and stays there and if I do power + volume down gives a messages for about 1 second goes away and the phone goes like dead... I have to remove the battery to get it going again. Is there anything else that I need to know?.
thanks'
Click to expand...
Click to collapse
you need to get into rsd mode by powering up + volume up but use rsd verion 5.5 when connecting to the computer. Then after run the sbf and wait till it asks to manually power up the phone..pull battery and ur golden.
Make sure youre fully charged and have allege drivers installed properly.
Sent from my MB855 using xda premium
KTT16 said:
you need to get into rsd mode by powering up + volume up but use rsd verion 5.5 when connecting to the computer. Then after run the sbf and wait till it asks to manually power up the phone..pull battery and ur golden.
Make sure youre fully charged and have allege drivers installed properly.
You're the man!!!, I've dowloaded the file you told me and RSD 5.5 and I'm back in bussiness. I just unlocked the bootloader... ready to try CM7, yay!.
Thank you for your support, best regards.
Click to expand...
Click to collapse
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?
I recently bought an S4 on eBay, and the phone activated and is working perfectly fine minus one thing: it won't update. The update downloads and starts to install, but about ten seconds into the install the "falling Android" logo appears, indicating that something went wrong. Upon reboot it tells me the software update was unsuccessful.
I don't know if the phone is currently or was previously rooted. Could this have something to do with the failed update? If so, how would I go about getting the phone back to stock? I have previous experience with rooting Android devices, but never anything in the Galaxy family. Also, because this is my girlfriend's phone, it doesn't need to be rooted, only upgraded.
If it has nothing to do with it being rooted, what's the problem here, and how do I fix it?
Sportsmaniac13 said:
I recently bought an S4 on eBay, and the phone activated and is working perfectly fine minus one thing: it won't update. The update downloads and starts to install, but about ten seconds into the install the "falling Android" logo appears, indicating that something went wrong. Upon reboot it tells me the software update was unsuccessful.
I don't know if the phone is currently or was previously rooted. Could this have something to do with the failed update? If so, how would I go about getting the phone back to stock? I have previous experience with rooting Android devices, but never anything in the Galaxy family. Also, because this is my girlfriend's phone, it doesn't need to be rooted, only upgraded.
If it has nothing to do with it being rooted, what's the problem here, and how do I fix it?
Click to expand...
Click to collapse
If you know how to get into download mode, get there and tell me what it says in the upper right hand corner.
If it's been rooted and has a high flash count it might prevent the upgrade.
If there is a custom recovery installed it would prevent it as well. You can check on that by turning the phone off then holding power and volume up until it says REBOOTING RECOVERY in blue letters at the top. Once it boots into recovery see if it's the stock recovery or a custom one.
Skipjacks said:
If you know how to get into download mode, get there and tell me what it says in the upper right hand corner.
If it's been rooted and has a high flash count it might prevent the upgrade.
If there is a custom recovery installed it would prevent it as well. You can check on that by turning the phone off then holding power and volume up until it says REBOOTING RECOVERY in blue letters at the top. Once it boots into recovery see if it's the stock recovery or a custom one.
Click to expand...
Click to collapse
I'm not quite certain what you're referring to when you say "download mode". Do you mean just starting the download of the update?
As for the recovery, it looks stock to me. It's titled "Android system recovery <3e>".
Sportsmaniac13 said:
I'm not quite certain what you're referring to when you say "download mode". Do you mean just starting the download of the update?
As for the recovery, it looks stock to me. It's titled "Android system recovery <3e>".
Click to expand...
Click to collapse
Power off again, hold power and volume DOWN this time until it says ENTERING DOWNLOAD (or something like that).
In the upper left corner there will be a bunch of tiny writing.
Skipjacks said:
Power off again, hold power and volume DOWN this time until it says ENTERING DOWNLOAD (or something like that).
In the upper left corner there will be a bunch of tiny writing.
Click to expand...
Click to collapse
Okay, after doing that the top-left says this:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
Also, I just emailed the guy I bought the phone from, and he informed that that it was indeed rooted, but he flashed it back to stock before selling the phone. He suggested to wipe the cache, but after trying that in recovery the error logo came up again.
Sportsmaniac13 said:
Okay, after doing that the top-left says this:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
Also, I just emailed the guy I bought the phone from, and he informed that that it was indeed rooted, but he flashed it back to stock before selling the phone. He suggested to wipe the cache, but after trying that in recovery the error logo came up again.
Click to expand...
Click to collapse
You have the Verizon version of the S4. This is a forum for the international version.
Version may have tweaked the software update to require you to do something else. I think you are best off asking this question in the Verizon S4 forum.
It's not that I don't want to help you, but without knowledge of what Verizon might have done I'm just shooting in the dark. The users on the Verizon forum might have an immediate answer for you as this might be a common problem with a simple fix for all I know.
Here's the link...
http://forum.xda-developers.com/galaxy-s4-verizon/help
Skipjacks said:
You have the Verizon version of the S4. This is a forum for the international version.
Version may have tweaked the software update to require you to do something else. I think you are best off asking this question in the Verizon S4 forum.
It's not that I don't want to help you, but without knowledge of what Verizon might have done I'm just shooting in the dark. The users on the Verizon forum might have an immediate answer for you as this might be a common problem with a simple fix for all I know.
Here's the link...
http://forum.xda-developers.com/galaxy-s4-verizon/help
Click to expand...
Click to collapse
Okay. Thanks for the help anyways, I appreciate it.
Sportsmaniac13 said:
Okay. Thanks for the help anyways, I appreciate it.
Click to expand...
Click to collapse
OK, you've been moved to the Verizon forum.
The OTA failing quickly as you describe usually means that one of the files that the OTA is trying to update has been modified.
What you should do is figure out what build your phone is running (Settings, More, About phone, then look at "Build number").
That will tell you what you need to flash to restore the phone to stock, hopefully with a no-wipe image.
Thanks for all your help guys. I finally solved the issue, so I figured I'd post how I did it in case anyone else runs into something similar.
I actually updated the phone through Verizon Software Upgrade Assistant. I'm assuming that through doing this I flashed the phone back to stock. Once this was over, the phone notified me of another update, and this time everything went smoothly. The phone is now completely stock and completely up-to-date.
So if anyone has a similar problem, give Verizon Software Upgrade Assistant a shot.