Related
When ever I try either the Fast boot android recovery, or Factory Reset from the Atrix [rooted W locked boot loader, stock gingerbread] it will reboot only to stop at Failed to Boot 2.
Removing the battery usually recovers the phone.
How to I get around th is problem, or do I have to take it back to AT&T for a swap out? [Or is that possible on a rooted phone?
Going in circles here other wise.
Thanks in advance.
I have a botched CWM install attempt and i am at the same screen whenever i turn on the phone. I am going to flash using RSD and see if that recovers it. Ill post once i find out.
Got tired of going in circles, found the OEM ATT stuff, used RSD lite, and installed the SBF
Now I'm back to normal, bloat and all.
jesgrew said:
Got tired of going in circles, found the OEM ATT stuff, used RSD lite, and installed the SBF
Now I'm back to normal, bloat and all.
Click to expand...
Click to collapse
bro, i oso facing same problem w u. the screen only shows "failed to boot 2. starting rsd mode"
would u like plz to give me step by step to recover it? thx so much, i really appreciate it
c1asis said:
bro, i oso facing same problem w u. the screen only shows "failed to boot 2. starting rsd mode"
would u like plz to give me step by step to recover it? thx so much, i really appreciate it
Click to expand...
Click to collapse
I read the NooB guide here on XDA and there are links to get the needed files: RSD Lite, and the AT&T OEM Gingerbread & current firmware SBF file.
I pulled the battery to recover my phone, then fully charged it up.
Made sure it was in USB debug mode.
Then did the Hardware Reset again.
When it stopped at "failed to boot 2. starting rsd mode" I started RSD lite on my PC, Pointed it at the SBF file, and installed.
It took some time, maybe 5~12 minutes?
But it rebooted a few times and I was good to go.
To test it I did several hardware resets, All A Ok.
Peace here till they get Cyanogen stable
jesgrew said:
I read the NooB guide here on XDA and there are links to get the needed files: RSD Lite, and the AT&T OEM Gingerbread & current firmware SBF file.
I pulled the battery to recover my phone, then fully charged it up.
Made sure it was in USB debug mode.
Then did the Hardware Reset again.
When it stopped at "failed to boot 2. starting rsd mode" I started RSD lite on my PC, Pointed it at the SBF file, and installed.
It took some time, maybe 5~12 minutes?
But it rebooted a few times and I was good to go.
To test it I did several hardware resets, All A Ok.
Peace here till they get Cyanogen stable
Click to expand...
Click to collapse
whats ur version before ur device got bricked? i dont know my version.
and if i used atnt unlocked phone, but i used it in singapore. can i use the atnt US version or OEM South East Asia? thx. realy confusing phone.
also when i connect my phone and i open RSD. it won't detect the phone. the device list in the RSD is empty.
c1asis said:
also when i connect my phone and i open RSD. it won't detect the phone. the device list in the RSD is empty.
Click to expand...
Click to collapse
Here is what little I know:
Put the Atrix in USB debugging mode.
Connect the phone to the USB cable, and the PC.
Change the USB mode to none.
Click OK
Start RSDlite, then it should see your phone.
And if you have a None US AT&T phone you will need that providers OEM SBF file.
Next move for me is unlocking the boot loader.
I used Pete's Motorola Tools for rooting.
So, I followed everything the briefmobile guide that was linked to from the greyblur xda page.
It said it installed, so I rebooted my Atrix and never made it past the "Dual Core Technology" boot screen.
I went into fastboot, then recovery mode (android guy by the triangle with the "!" in it). I reset the phone. Didn't work.
It was running 2.3.4.
I've read something about romracer, but I don't know what that is, where to download it, or how to use it. Please explain in depth if it is relevant.
Please help me. I just got this phone (my first smartphone) today and was really excited to start messing around with Android. I'm probably going to be too nervous to do anything for a while after this. I just want the stock os back. Anything that could get my phone back to where it was is GREATLY appreciated.
There is a one click batch script created by Alaq to revert phones back to stock 2.3.4. Here is the link:
http://forum.xda-developers.com/showthread.php?t=1421522
If you are not sure how to get into fastboot here is how:
1. Turn off your device.
2. Hold down the power button and downward volume button until you see “Fastboot” on your screen.
3. Push the upward volume button.
Greyblur is only for froyo ROMS. That's why you have a nonbooting phone.
Sent from my MB860 using xda premium
Dark9781 said:
There is a one click batch script created by Alaq to revert phones back to stock 2.3.4. Here is the link:
http://forum.xda-developers.com/showthread.php?t=1421522
If you are not sure how to get into fastboot here is how:
1. Turn off your device.
2. Hold down the power button and downward volume button until you see “Fastboot” on your screen.
3. Push the upward volume button.
Click to expand...
Click to collapse
Thank you! So do I just drop this onto my SD card then?
Njl6705 said:
Thank you! So do I just drop this onto my SD card then?
Click to expand...
Click to collapse
No. Put the phone into fastboot, hook it up to your computer, and run the script from your computer.
Dark9781 said:
No. Put the phone into fastboot, hook it up to your computer, and run the script from your computer.
Click to expand...
Click to collapse
Ok. I ran it, it said it was successful, I restarted it, and now I have:
Failed to boot 4
Starting RSD Mode
That only happens when your phones bootloader isn't unlocked. I assumed it was since you tried flashing a custom rom. You are going to have to flash a sbf file. Here is the link to the instructions.
http://forum.xda-developers.com/showthread.php?t=991072
You can find the 2.3.4 sbf file here:
http://www.fileserve.com/file/6TxJg...OLE-26-release-keys-signed-MERetail-06.sbf.gz
Or you can try the 2.3.6 update found here:
http://atrix.tk/4.5.141/
You are going to need to extract the file from the archive so you will need a zip program. I would go with winrar or 7-zip.
Also there is a newer version of rsd lite out than the one posted on the how to. Here is the link
http://mophoforum.com/the2dcour/RSDLite5.5.rar
This should get you running again. Good luck.
Sent from my ATRIX 4G
...first day of owning this phone... I think I'm done with this stuff after this. >.<
If you are trying to install ROMS you need to unlock the bootloader first... Check out the Noobs Guide in the general section.
Dark9781 said:
That only happens when your phones bootloader isn't unlocked. I assumed it was since you tried flashing a custom rom. You are going to have to flash a sbf file. Here is the link to the instructions.
http://forum.xda-developers.com/showthread.php?t=991072
You can find the 2.3.4 sbf file here:
http://www.fileserve.com/file/6TxJg...OLE-26-release-keys-signed-MERetail-06.sbf.gz
Or you can try the 2.3.6 update found here:
http://atrix.tk/4.5.141/
You are going to need to extract the file from the archive so you will need a zip program. I would go with winrar or 7-zip.
Also there is a newer version of rsd lite out than the one posted on the how to. Here is the link
http://mophoforum.com/the2dcour/RSDLite5.5.rar
This should get you running again. Good luck.
Sent from my ATRIX 4G
Click to expand...
Click to collapse
You're sure that if I flash this it won't get bricked further? SBF is firmware, right? I meant my phone was running OS 2.3.4.
I can't get get into rsd or fastboot now. All it says is
Failed to boot 4
Starting RSD mode.
I plugged that into my computer, it recognized my Atrix as SE Flash Olympus, instead of NS flash olympus, so I tried to flash it anyways and it failed.
Please guys. I'm getting desperate here. Please tell me I don't have a $250 paper weight.
If it says "Starting RSD mode," then you're in RSD mode -- that's okay.
RSD Lite also recognized my phone as "SE" instead of "NS." Not sure why, but it didn't harm anything.
Sometimes the flashing process fails with RSD Lite. (Do NOT EVER unplug your phone in the middle of a flash, by the way.) Which SBF did you try to flash?
sheeparecurious said:
If it says "Starting RSD mode," then you're in RSD mode -- that's okay.
RSD Lite also recognized my phone as "SE" instead of "NS." Not sure why, but it didn't harm anything.
Sometimes the flashing process fails with RSD Lite. (Do NOT EVER unplug your phone in the middle of a flash, by the way.) Which SBF did you try to flash?
Click to expand...
Click to collapse
2.3.4, what my phone was originally running.
Okay, good. Don't try any earlier SBF versions; that's the guaranteed way to brick your phone. (You're not hard bricked until it says "Failed to boot, entering NVFlash" -- if you have any other options, it's possible to pull it back.)
Try to flash the 2.3.4 SBF again. I've heard of some people having to try a couple of times before it takes; RSD Lite can be finicky.
I think the most immediately pressing issue would be your battery's charge, because it can't charge if it can't boot. If the program errors out with "Battery too low to flash", you may need to pick up an external charger and/or ask someone nicely at an at&t store to charge your battery in one of theirs.
sheeparecurious said:
Okay, good. Don't try any earlier SBF versions; that's the guaranteed way to brick your phone. (You're not hard bricked until it says "Failed to boot, entering NVFlash" -- if you have any other options, it's possible to pull it back.)
Try to flash the 2.3.4 SBF again. I've heard of some people having to try a couple of times before it takes; RSD Lite can be finicky.
I think the most immediately pressing issue would be your battery's charge, because it can't charge if it can't boot. If the program errors out with "Battery too low to flash", you may need to pick up an external charger and/or ask someone nicely at an at&t store to charge your battery in one of theirs.
Click to expand...
Click to collapse
Ok. So I'll try flashing it a couple more times. My battery should have a decent charge still, so that shouldn't be a problem.
Thanks.
I really need to just calm down and stop loosing my head over this.
UPDATE: When the flash fails, the phone's screen reads:
Failed to Boot 4
Starting RSD Mode
sec_exception: febe, 35, 35
RSD Lite also says
Flashing failed process. Phone did not re-ennumerate after RAM downloader was sent (0x703e).
What does this mean?
Hmm. I'll admit I don't know what that means, so all I can do is help you troubleshoot.
I did some searching, and another user hit this problem when using a USB port on the front of his PC (which is not powered as strongly as one on the back). Did I mention RSD Lite is a finicky beast?
If you're on a desktop machine, try switching to a USB port at the back. If you're on a laptop, try a different port. I'll keep looking for anyone with a similar problem.
EDIT: One last question. You extracted the file before flashing, right? The extension is .sbf, not sbf.gz?
Hmmm... Yeah, I guess all I can do is keep looking.
My battery is now too low to flash, and I don't have a friend who has an Atrix.
I might just sent this into mobiletechvideo's debricking service. This is my first android phone and I'd rather not mess it up anymore.
Yes, it's an SBF file.
Fair enough. Sorry this wound up being a pain. I know full well that sick feeling when you think something's messed up, but your phone is still only in a "soft brick" at this stage and can be recovered.
Keep in mind these things really can be modded safely, but you have to do a LOT of reading at the outset, and stick with roms made very recently. (Last August? ancient history.) It's an interesting technology intersection; these things are proper computers which should be readily customizable, but they're also phones which tend to be locked down by the manufacturer/carrier. By analogy, I can wipe my computer's hard drive and install XP if I want, even though I'm currently on W7. But if I try to install an earlier Android version on my phone, it bricks.
anyway, good luck with getting your phone up and running again.
Thanks. I actually did a decent amount of reading before I got this phone, but it seems I'm more of a kinesthetic kind of learner. I probably should have gotten an older, cheaper phone to play around with before I went all out and got an Atrix.
It really is an interesting intersection. It's too bad the manufactures feel the need to put any restrictions on.
I guess I'll just read some more n00b guides and try again when I have a little more confidence. $50 doesn't seem so bad to get the phone debricked compared to the $250 I payed for it. I don't really have a choice either, since the only means of charging it is thirty miles away at the nearest AT&T store.
Anyways, thanks for helping me troubleshoot. Hit me up if you have any problems. I'd be happy to dig around in the forums and see if I can find anything.
You could have avoided all these problems if you had read the entire thread about greyblur, because it specifically states that it is only for froyo phones. But, as many say, you live and you learn, then you aren't a noob anymore.
Also, if you have warranty on your phone, you can send it in and Motorola should fix it for you from what I've heard.
Sent from my Xoom using XDA Premium HD app
Before some of you gets upset with me posting the same kind of question, please know that I looked at the forum everywhere plus some other forums and tried almost everything. Here's the summary.
I recently got Droid Razr Asia version and I upgraded to EU Retail rom n rooted it.
There was one problem that I noticed that only bluetooth was not working.
Checked online, and found out that it's the radio mismatch b/w EU and Asia version.
So I downloaded RAZRX rom and was trying to flash it again with bootstrap.
So the process started and in 10 seconds it failed.
So I tried to search other forums ...
at some place i found that ... after Hard Resetting, clearing catche; I am also supposed to format the system.
So I followed the whole procedure, and turns out that again it does not get FLASHED. So I downloaded the ASIA version again and tried to format. It did not work. I tried with EU version, it did not work.
So after getting tired, I tried with RSDLite to flash through PC.
That's when I found out that ...
It detects the phone ... but the phone has no EMEI, software version or any other details. Everything is n/a.
Still I tried, and it said "fastboot installation failed" or somethin like that.
And now my phone is stuck on red motorola logo.
I tried to power off and go to bootloader fastboot ...
and it says "Fastboot Locked ... Press power button to power down."
I tried with the DroidRazrUtility1.4 also ...
But it does not detect the phone.
I tried other few things I found online. But nothing worked.
I also drained the battery by keeping it aside to see if the fastboot gets unlocked, but it didn't work.
However, I haven't removed the battery yet. Cause I do not have the tools.
Please can somebody tell me step by step approach how to do this?
Because I haven't found out where I am going wrong in the given methods. and btw, I have followed everything exactly step by step.
Really appreciate any kind of help.
Thank you very much.
Try to flash with RSD Alternative
http://forum.xda-developers.com/showthread.php?t=1453660
Thanks a ton.
But will it still work if my AP FATBOOT mode says that "Device is Locked"
And the battery is on low?
samthehell said:
Thanks a ton.
But will it still work if my AP FATBOOT mode says that "Device is Locked"
And the battery is on low?
Click to expand...
Click to collapse
Probably not. I read on one of the forums there might be a way around the battery being low. I think it was here in xda. Do a search for fast boot install or battery, something like that. If you find that doesn't work you would have to make the tbh cable which allows power to the phone without a battery, or in your case a near dead battery.
Sent from my Droid Razr using Tapatalk
"Device is locked" is natural, (almost) all of our bootloaders are locked. Nothing to do with flashing official ROMs.
You'll need to make a factory cable if the battery is low, search the development forum for a guide.
Sent from my XT910 using xda premium
Thank you all ... Just ordered the cable. Hope it works.
Appreciate all the help.
samthehell said:
Thank you all ... Just ordered the cable. Hope it works.
Appreciate all the help.
Click to expand...
Click to collapse
Here is where u can find full 2.3.6 Asian fastboot file, so you can use rsd for flashing 2.3.6 but for flashing 2.3.5 you have to use Alternative rsd because of bl version
http://forum.xda-developers.com/showthread.php?p=22821170
Sliced by my Razr on Tapatalk
so, i tried to unlock my bootloader following qbking's video and hard bricked my 1st photon. I bricked when i tried to flash derpunlock using rsdlite 5.5
In the compendium thread, it looks like the steps were slightly different and i was wondering if i just screwed up qbking's instructions, or should i follow the compendium instead?
sorry if this is a stupid question. any help would be much appreciated.
You cant get into rsd protocal?
Sent from my MB855 using xda premium
If you followed all the steps you should have been fine, are you sure you didn't forget anything? Maybe download RSS lite 5.6, that's the latest and it worked for my photon
Sent from my MB855 using xda premium
i got to where it said "Starting RSD protocol support" like in the video by holding Power + Vol. up. http://www.youtube.com/watch?v=BwRjFrzClBs
then i hit Start in RSD lite. It froze at "Executing 99%" like the video said it would, but my phone went black and never turned on again.
looking closer, i see that im flashing derpunlock and he's flashing pudding_stock_unlock. could that have done it?
derpunlock is what i used if i remember correctly
does anyone has a link to the driver flash MDM6600
Well yeah its supposed to do that. Did you wait for it to say flashing failed before you unplugged the phone? Cause once it does, that part of the unlocking process is done, and if you turned on your phone manually, it'd still start up like it used to. It might take a while to say flashing failed on rsd lite, but you cant unplug it until you do
yeah, i waited til it said flashing failed. my phone was off when it was done though, couldnt ever get it back on after that.
should i run RSDlite when my phone says "RSD" or "starting rsd protocal"?
also, thanks for the replies everyone.
Rsd
Sent from my Motorola Electrify using XDA
absolutely same problem
My droid x2 freezes on the dual core start up screen every time i try to turn it on, i pulled the battery out the first time this happened, and I've already went into recovery mode and did the (wipe data/factory reset) option, and i also wiped my cache partition, but still my phone freezes on boot. my phone started doing this when i was using "mcTweaker" and a notification popped up and it said i need to reboot, but as the same time i hit reboot system in the options menu. when i did this the phone cut off and since then it always freezes on the dual core screen when i start it up. i am also still on the stock rom and am rooted. any help or tips on how to fix this is highly appreciated.
if you can still can get to recovery, and have a backup, restore it
as you have wiped data, that is unlikely, unless you flashed re-recovery
sbf is your last option
:/
sd_shadow said:
if you can still can get to recovery, and have a backup, restore it
as you have wiped data, that is unlikely, unless you flashed re-recovery
sbf is your last option
Click to expand...
Click to collapse
im not quite sure how to sbf this phone, once again your help is appreciated... do you know how to? ill check around the forums and see if i can find anything too
Oops
sneaker14 said:
im not quite sure how to sbf this phone, once again your help is appreciated... do you know how to? ill check around the forums and see if i can find anything too
Click to expand...
Click to collapse
Ok my bad, i feel lyk such a noob... i just wasnt waiting long enough for the starting RSD protocol support thing. Problem solved
great, just don't flash wrong sbf
Droid x2 and Milestone x2 have different sbfs, because they are different devices, different radios
ok for some reason it stays on the (Starting RSD Protocol Support) screen and never advances onto anything else D: is there a fix for this or is my completely screwed. i thought since the thread i read said it takes 3-5 minutes to start it up thats what my problem was, but i was wrong, the thing just simply wont start up... sorry for false assumption
yes that's it "Starting RSD Protocol Support"
is all is does, till you start rsd lite, doesn't change till half way through sbf or more
Ok thank you sooo much, this was frustrating me since last friday and i think the rsd lite i had was the problem, i went and downloaded a different one and now its working ... once again thanks for your help, ill get back to ya if i mess anything else up haha
sd_shadow said:
yes that's it "Starting RSD Protocol Support"
is all is does, till you start rsd lite, doesn't change till half way through sbf or more
Click to expand...
Click to collapse
now when i try to do it it says (error switching phone to BP Pass through mode) idk what to do or why its doing this
its a driver issue
a couple of options
use the moto drivers program
or ezSBF for x2, no drivers needed
both in my list of stuff
sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
also the fix for the d2 was
" Note: Under certain circumstances (especially when using Windows Vista and Windows 7) there might be a problem with not all device drivers being installed correctly. In such case, the flashing process will abort, and your phone won't be able to boot normally. RSDLite shows the following error message:
Error switching phone to BP Pass through mode
To get around this issue, once you get a Device driver could not be installed message from Windows, don't close RSDLite nor power off the phone. Start Motorola Driver Installer once again, and let it finish. Then if RSDLite didn't timeout yet, head to Device Manager, find the Unknown device, and in its properties' Driver tab click Update driver…. It should now install normally. If RSDLite timed out and you got an error from it, just repeat the SBF process. The driver should now be present, and the flashing process will finish normally.
Once the flashing process is complete, RSDLite will tell you to “power the phone up manually”. In most cases you won't be able to do this straight as instructed: the phone will be bootlooping. Take the battery out, and then place it back in. Press the lock/power button: the phone should boot normally. Close RSDLite. Disregard the warning about flashing not being completed since your phone has already booted into Android.
In case you still get bootloops after pulling the battery, wipe data in Android Recovery. "
Sent from my DROID X2 using xda premium
sd_shadow said:
its a driver issue
a couple of options
use the moto drivers program
or ezSBF for x2, no drivers needed
both in my list of stuff
sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
also the fix for the d2 was
" Note: Under certain circumstances (especially when using Windows Vista and Windows 7) there might be a problem with not all device drivers being installed correctly. In such case, the flashing process will abort, and your phone won't be able to boot normally. RSDLite shows the following error message:
Error switching phone to BP Pass through mode
To get around this issue, once you get a Device driver could not be installed message from Windows, don't close RSDLite nor power off the phone. Start Motorola Driver Installer once again, and let it finish. Then if RSDLite didn't timeout yet, head to Device Manager, find the Unknown device, and in its properties' Driver tab click Update driver…. It should now install normally. If RSDLite timed out and you got an error from it, just repeat the SBF process. The driver should now be present, and the flashing process will finish normally.
Once the flashing process is complete, RSDLite will tell you to “power the phone up manually”. In most cases you won't be able to do this straight as instructed: the phone will be bootlooping. Take the battery out, and then place it back in. Press the lock/power button: the phone should boot normally. Close RSDLite. Disregard the warning about flashing not being completed since your phone has already booted into Android.
In case you still get bootloops after pulling the battery, wipe data in Android Recovery. "
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
so i installed the device manager 2.2.28 and installed the drivers, and im using rsd lite 5.7 and im still getting the error D: so do u know why its still doing this?
sd_shadow said:
its a driver issue
a couple of options
use the moto drivers program
or ezSBF for x2, no drivers needed
both in my list of stuff
sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
also the fix for the d2 was
" Note: Under certain circumstances (especially when using Windows Vista and Windows 7) there might be a problem with not all device drivers being installed correctly. In such case, the flashing process will abort, and your phone won't be able to boot normally. RSDLite shows the following error message:
Error switching phone to BP Pass through mode
To get around this issue, once you get a Device driver could not be installed message from Windows, don't close RSDLite nor power off the phone. Start Motorola Driver Installer once again, and let it finish. Then if RSDLite didn't timeout yet, head to Device Manager, find the Unknown device, and in its properties' Driver tab click Update driver…. It should now install normally. If RSDLite timed out and you got an error from it, just repeat the SBF process. The driver should now be present, and the flashing process will finish normally.
Once the flashing process is complete, RSDLite will tell you to “power the phone up manually”. In most cases you won't be able to do this straight as instructed: the phone will be bootlooping. Take the battery out, and then place it back in. Press the lock/power button: the phone should boot normally. Close RSDLite. Disregard the warning about flashing not being completed since your phone has already booted into Android.
In case you still get bootloops after pulling the battery, wipe data in Android Recovery. "
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
I installed the drivers and im still getting the error for some reason D: i used motorola device manager 2.2.28 to install the drivers. and am using rsd lite 5.7
use ezSBF for x2, no drivers needed
sd_shadow said:
use ezSBF for x2, no drivers needed
Click to expand...
Click to collapse
alrighty im bout to try that, but if that doesnt work is it the last option for me... and if i brought it back to the store would they fix it?
unlikely that verizon would fix, rooting voids warranty
they may replace, if you tell them you don't know what happened
if you bought insurance, that will cover it
Sent from my DROID X2 using xda premium
sd_shadow said:
unlikely that verizon would fix, rooting voids warranty
they may replace, if you tell them you don't know what happened
if you bought insurance, that will cover it
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
all right, if this dont work ill take it back and tell em i dont know what happened. but a problem is it says "failed to boot 1" as soon as you tun the phone on so hopefully they wont know
Whoa are you telling us ezsbf didn't work?? Is this the first "actual" bricking of a x2?
Sent from my MB870 using xda app-developers app
sneaker14 said:
all right, if this dont work ill take it back and tell em i dont know what happened. but a problem is it says "failed to boot 1" as soon as you tun the phone on so hopefully they wont know
Click to expand...
Click to collapse
your holding volume up, when powering on, to boot to 'starting rsd support'?