Database Users

[Resolved] dx moto logo boot error

hello all
sorry if this is in the wrong section.
today i decided i didnt like my old rom and tried to install fission using the fission rom manager. in the install screen, i forgot to check the wipe box by mistake.
now my phone WILL NOT go any farther than the white moto logo at the very beginning of the boot animation. Is there anyway I can fix this? i am not that experienced at this stuff, so a good explanation is needed. please help!
i just figured out how to get to (stock) recovery from boot, but even after wiping and retryin a few times, it still wont work....
i have also not upgraded or updated really anything since i got my phone months ago, except root, and deodex, and flyx rom
-matt

You won't lose root, and when you sign back into google all your apps will come back. Did you make a recent backup? If so you can use it from recovery
Sent from my DROIDX using XDA App

You can even wipe and reinstall if you still wanna try fission since you're in recovery.
Sent from my DROIDX using Tapatalk

google has all of my tons of apps? sik. but from recovery there is no option to restore/backup nandroid, like bootstrap
the options are reboot, apply sdcard update.zip, wipe data/factory reset, wipe cache partition

Oh you're in stock recovery... Just wipe and reboot.
Sent from my DROIDX using Tapatalk

well thanks for helping, but even after i wiped 3 or 4 times trying, it still desnt work. any ideas?
idk if fission requires 2.3.32 or somethin, but i dont think i hav updated anything since i got my phone a long time ago, just thought id add that

Try pulling the battery, should reboot to clockwork recovery when you put battery back in, then you can restore a backup or flash a rom from sd card.
Sent from my DROIDX using XDA App

mattmartin77 said:
well thanks for helping, but even after i wiped 3 or 4 times trying, it still desnt work. any ideas?
idk if fission requires 2.3.32 or somethin, but i dont think i hav updated anything since i got my phone a long time ago, just thought id add that
Click to expand...
Click to collapse
Most roms require .320/.340. You definitely wanna upgrade if you plan on flashing in the future.
Sent from my DROIDX using Tapatalk

well neither of those solve my problem, i am debating on whether on not to take it to verizon, but idk if they will even help me.

if you can get to clockwork recovery you can download a rom by computer and transfer to your sd card, or put your card in another phone to download it. Then flash that rom. Be sure to mount the system before flashing
Sent from my DROIDX using XDA App

Hi matt.. soon after getting my X, I got stuck in your situation while flashing a rom. I took it to verizon and after trying to troubleshoot it for a few minutes, they decided to just overnight me another one. I told them that I woke up and the phone was stuck at the M. I didn't mention anything about being rooted or trying to flash a rom.
The phone was also within the one year warranty though. You might want to try this route if all else fails.
Good luck!!
Sent from my DROIDX using XDA App

If everything else fails you can sbf. I'll pm you a link for the 2.2315 full sbf, just download rsd lite 4.8 and google how to do a sbf if your not familiar. Then you can do the official ota and be up to date
Sent from my DROIDX using XDA App

thnx everyone. ive never sbf'ed before, but ill give it a shot. i wish i could get to clockwork, it would make everything so much easier.

i triedflashing a new sbf, but rsdlite gives me the error- could not find initial values in the ini file or somthin... any ideas? its my fisrt time putting on a new sbf.

mattmartin77 said:
i triedflashing a new sbf, but rsdlite gives me the error- could not find initial values in the ini file or somthin... any ideas? its my fisrt time putting on a new sbf.
Click to expand...
Click to collapse
What version of rsd are you using? you can just sbf .320 full then .340 system only and it will be updated no need to sbf an old file.

i am using the newest rsd i could find. 4.9 right? and it seems as if i need pst_flash.ini according to the sbf installation instructions i found here
edit: hey thnx everyone for the help. i took it to verizon and the techs said it was a "complete software crash". yay i bricked my phone:/... the good news is that verizon is overnighting me a new one.
when i get it i am going to root it. i also want it to be the latest sbf or whatever its called so i can get either fission or gummyjar on there. now i need 2 more questions answered.
1. which option in about is the one that tells me what sbf im on?
2. i kinda need a really good tut on how to flash a new sbf and get it to .340 because i clearly failed miserably at it last time, so anyone have a link or willing to write it up?

It should have.340 on it or be ready to update. You can check by going to settings, about phone, build number. It should say 2.2.340
Sent from my DROIDX using XDA App

oh build number. thnx bro, so many confusing numbers, why cant there just be simple names? lol

Full SBF isn't out yet for 2.3.340 you will need the SBF for 2.3.320 and then the patches to get to 2.3.340. Keep it handy just in case!

yah i have the .15 sbf right now for safe keeping but i cant find the .32 or the .34 patch, but it isnt urgent since i heard that the new phone that is coming will be preloaded with the newest everything.
can i just use z4root to root my new phone? or do i have to do the doroot thing in adb like i originally did on my first dx?
I also wanted to know if i could use one of the kernels i saw in the fission rom manager with a rom other than fission, such as gummyjar.

[Q] Recovery options for new user

Hi, just bought myself a new Motorola Atrix phone and i'd like to know what are my backup options?
Tried stock recovery but it shows only wipe+reboot options. There are no backup/restore features i'd expect from recovery system.
If i flash CWM, how can i uninstall it and get back to stock one if i happen to have return it to service shop someday (god forbid)?
Thanks

purpler said:
Hi, just bought myself a new Motorola Atrix phone and i'd like to know what are my backup options?
Tried stock recovery but it shows only wipe+reboot options. There are no backup/restore features i'd expect from recovery system.
If i flash CWM, how can i uninstall it and get back to stock one if i happen to have return it to service shop someday (god forbid)?
Thanks
Click to expand...
Click to collapse
please read the noob thread at the top of the forum, it will explain everything you need to know about unlocking your bootloader, installing a custom recovery, and then flashing new ROMs.

im very familiar with unlocking bootloader, rooting, flashing recovery and such. That topic doesn't say anything about going back to stock recovery if i remember correctly. Correct me if im wrong.

purpler said:
im very familiar with unlocking bootloader, rooting, flashing recovery and such. That topic doesn't say anything about going back to stock recovery if i remember correctly. Correct me if im wrong.
Click to expand...
Click to collapse
if you've already done all your research, then you would know that you can reflash a stock 2.3.4 sbf file with RSDlite to turn your phone back into completely stock.
that is, if you've already done all your research.. i mean, it's not like you can google these questions or anything

heh, so flashing SBF will erase CWM recovery right?

purpler said:
heh, so flashing SBF will erase CWM recovery right?
Click to expand...
Click to collapse
There is no stock recovery.... CWM does not come with your phone, you installed it. And who cares if you have a recovery on the phone and have to take it back?? You think the jack holes at AT&T even know what recovery is, let alone how to enter recovery mode... they all have iPhones.
Just flash a fruitcake if you have to take it back, and be done with it.
OBTW, since you unlocked your bootloader, you're unlocked forever... how you going to hide that?
Sent from my MB860 using xda premium

purpler said:
heh, so flashing SBF will erase CWM recovery right?
Click to expand...
Click to collapse
it will turn your phone completely stock again. it will even 'relock' your bootloader for you. just be careful, and only use it as a last resort since RSDlite always has a chance to brick your device permanently.

Alcapone263 said:
it will turn your phone completely stock again. it will even 'relock' your bootloader for you. just be careful, and only use it as a last resort since RSDlite always has a chance to brick your device permanently.
Click to expand...
Click to collapse
Can not re-lock bootloader... only can make the Unlocked word dissappear from boot screen.
Sent from my MB860 using xda premium

It doesnt show "Unlocked" message at least so im pretty much safe. Where i bought it they barelly knew specs of my phone god forbid to find out if its unlocked.
Lemme rephrase my question: If i flash CWM, can i erase it with flashing stock SBF?

purpler said:
It doesnt show "Unlocked" message at least so im pretty much safe. Where i bought it they barelly knew specs of my phone god forbid to find out if its unlocked.
Lemme rephrase my question: If i flash CWM, can i erase it with flashing stock SBF?
Click to expand...
Click to collapse
Yes... maybe... I don't know...
If they didn't know anything about your phone, why are you even worried.
You're safe??? safe from what? The unlocked bootloader police??
Sent from my MB860 using xda premium

Swiftks said:
Can not re-lock bootloader... only can make the Unlocked word dissappear from boot screen.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
which is why relock was surrounded by apostrophes. although, technically if you reflash the stock .sbf it takes away the pudding files in the bootloader, which is what allows us to flash custom recovery and stuff. have you ever reflashed a stock 2.3.4 sbf and then tried to install CWM through fastboot? it just doesn't work. the fuse in your device may be blown, but without those pudding files injected into the bootloader, you might as well have a locked device.

@Swiftks
you totally trolled my topic dude. and you aren't helping at all :\

purpler said:
you totally trolled my topic dude. and you aren't helping at all :\
Click to expand...
Click to collapse
your questions aren't making any sense. you can't install CWM without unlocking the bootl.oader, so if there's no unlocked text when you start the phone up, you're not gonna be able to do anything with CWM.
and it's already been established that if you flash a .sbf file, it will give you a stock recovery again.

Alcapone263 said:
which is why relock was surrounded by apostrophes. although, technically if you reflash the stock .sbf it takes away the pudding files in the bootloader, which is what allows us to flash custom recovery and stuff. have you ever reflashed a stock 2.3.4 sbf and then tried to install CWM through fastboot? it just doesn't work. the fuse in your device may be blown, but without those pudding files injected into the bootloader, you might as well have a locked device.
Click to expand...
Click to collapse
Ill agree with this.... so we agree, it's netural... an unlocked device that you can't do any of the cool unlocked features with.
Sent from my MB860 using xda premium

purpler said:
@Swiftks
you totally trolled my topic dude. and you aren't helping at all :\
Click to expand...
Click to collapse
Dude... are you done crying. Man up, grab your sack and stop worrying about what may happen if you have to return your phone.
Why do you want to install CWM Recovery... I'm assuming to flash a ROM... well guess what genius, you have to unlock your bootloader first... which means if these super scientists who work only at your local phone store, want to know if you've tampered with your phone, they're gonna know.
Sent from my MB860 using xda premium

i just wanted to know if flashing SBF erases already installed CWM. If i have CWM, its quite obvious bootloader's unlocked, at least to me it would.
My question was inspired by situation where i might need to return phone under warranty to service shop and hide that it has been unlocked and screwed with custom ROM's as much as i can.
There are some strange reboots/shutdowns which wasnt paid so phone is going back with hidden traces of being total geek.
Clearer?

purpler said:
i just wanted to know if flashing SBF erases already installed CWM. If i have CWM, its quite obvious bootloader's unlocked, at least to me it would.
My question was inspired by situation where i might need to return phone under warranty to service shop and hide that it has been unlocked and screwed with custom ROM's as much as i can.
There are some strange reboots/shutdowns which wasnt paid so phone is going back with hidden traces of being total geek.
Clearer?
Click to expand...
Click to collapse
Let me more precise with you.... Since you have unlocked your bootloader, you have burnt a fuse that can not replaced, short of cracking open the phone, finding the fuse, and fixing it (if that's even possible). So, if they are paying that close of antention to notice that you have CWM Recovery installed, they most likely would also notice that the bootloader fuse is gone, therefore who have tampered with your phone.... whether you flash a sbf file it not.
Sent from my MB860 using xda premium

</epic misunderstanding>

Wow. This thread is epic. Btw, chuck Norris can relock his bootloader.
Sent from my MB860 using Tapatalk

Phalanx7621 said:
Wow. This thread is epic. Btw, chuck Norris can relock his bootloader.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Damn right he can!

My method on 2.3.6

I know there have been varying posts on the subject, but I thought I would share my experience with the update. I originally started out on a bootloader unlocked, rooted, At&t branded Atrix. I had installed the 2.3.4/4.5.91 fruitcake previously and had been using it for some time. When the update came down I rolled back to stock recovery using fastboot and after the installation of the update, the phone gave me an failed to boot 4. I used rsd to flash the official 2.3.4/4.5.91. I received a failed to boot 1. (After going to launder my, now soiled, trousers) I noticed that when I plugged the phone in, RSD still recognized the phone, even though it did not show the "entering RSD mode" tag. It occured to me to attempt to flash pudding using the 4.2 auto unlock. Immediately after flashing pudding the phone booted up and everything was working fine.
At this point I rooted and installed clockwork on the phone using the same 4.2 tool. I then used Voodoo OTA Rootkeeper to back up my root. Unfortunately the tool installs clockwork in order to root the phone, so I had to flash back to stock recovery using fastboot. . I then booted, downloaded, and then installed the update.
After the update the phone rebooted, and gave me "failed to boot 2, starting RSD mode". At which point I installed pudding again using the tool. Rebooted after having installed pudding, the phone booted beautifully. I used OTA Rootkeeper to restore my root after the boot. Everything is working fine and it is on current version 4.5.141. I hope this helps someone else, or maybe someone to find a more simple, straight-forward way of doing this.

Doogiedoo said:
I know there have been varying posts on the subject, but I thought I would share my experience with the update. I originally started out on a bootloader unlocked, rooted, At&t branded Atrix. I had installed the 2.3.4/4.5.91 fruitcake previously and had been using it for some time. When the update came down I rolled back to stock recovery using fastboot and after the installation of the update, the phone gave me an failed to boot 4. I used rsd to flash the official 2.3.4/4.5.91. I received a failed to boot 1. (After going to launder my, now soiled, trousers) I noticed that when I plugged the phone in, RSD still recognized the phone, even though it did not show the "entering RSD mode" tag. It occured to me to attempt to flash pudding using the 4.2 auto unlock. Immediately after flashing pudding the phone booted up and everything was working fine.
At this point I rooted and installed clockwork on the phone using the same 4.2 tool. I then used Voodoo OTA Rootkeeper to back up my root. Unfortunately the tool installs clockwork in order to root the phone, so I had to flash back to stock recovery using fastboot. . I then booted, downloaded, and then installed the update.
After the update the phone rebooted, and gave me "failed to boot 2, starting RSD mode". At which point I installed pudding again using the tool. Rebooted after having installed pudding, the phone booted beautifully. I used OTA Rootkeeper to restore my root after the boot. Everything is working fine and it is on current version 4.5.141. I hope this helps someone else, or maybe someone to find a more simple, straight-forward way of doing this.
Click to expand...
Click to collapse
Thanks for the info. Do you mind if I re-post in this thread over in the dev forum? I noticed your post count is too low to post over there.
I just got my phone back from Motorola after they fixed a shattered screen. I had sent it in with an unlocked BL, running a CM7 kang. They sent it back running stock .141.
Since I didn't do the update, I had no idea how to proceed re-unlocking it. But it sounds like between you and Nottach, I should be ok with the pudding unlocker(knock on wood).

how did you get rid of superuser on fruitcake?

ghost_og said:
Thanks for the info. Do you mind if I re-post in this thread over in the dev forum? I noticed your post count is too low to post over there.
I just got my phone back from Motorola after they fixed a shattered screen. I had sent it in with an unlocked BL, running a CM7 kang. They sent it back running stock .141.
Since I didn't do the update, I had no idea how to proceed re-unlocking it. But it sounds like between you and Nottach, I should be ok with the pudding unlocker(knock on wood).
Click to expand...
Click to collapse
Not at all, if it's any use to anyone, feel free to repost it. Also, I had a hardware problem (screen banding) on my atrix and sent it back for repairs. When it was returned, it no longer showed unlocked. The bootloader was still unlocked, but I had to reapply the unlock sbf to get it to show again (before using another rom).
ummkiper said:
how did you get rid of superuser on fruitcake?
Click to expand...
Click to collapse
I still had it installed on fruitcake, but lost it (well, rather lost root access, as the app "superuser" is still there but not functional) when I installed the sbf file initially. I'm not sure if flashing pudding or using the automatic unlock on the fruitcake initially would have worked. I didn't think to try it initially.

Cool,thanks for the info.
Sent from my Nexus One using xda premium

Cwm recovery issues

Hey guys, i have a few weeks experience flashing and all that leet stuff, but it seems i have a problem! I started to modify my ATRIX on 2.3.4, i unlocked sim, rooted, unlocked bootloader, and flashed custom recovery. I played around with a few roms, then i decided to update my fw to 2.3.6, well before i could do that i had to undo all mods so i ended up flashing a stock 2.3.4 fw and upgraded OTA. Im pretty sure that was my mistake... i may have needed an unlocked 2.3.6 sbf.. i re-rooted, and flashed cwm with rom manager, now when i go to boot in recovery mode i get failed to boot 2 starting rsd protocol. Everything is fine i just need to know where i messed up and how to get cwm running again. P.S. ive also been having an issue with my camera! I open the cam app and i get black screen, factory reset does NOT fix! Ive seen post's saying that the module is bad if that does not work BUT, when using flashlight app the flash lights up for a sec and then shuts off. When i switch to front camera it will stop responding, i'll click wait and after a min it will show image and i can take a pic(only with front cam). If i could get both issues solved i would be very grateful! If any other info is needed ill be sure to respond asap! Thank you in advanced for reading and assisting with my issues!
Sent from my MB860 using XDA

Get the cwm recovery img & flash with Fastboot and that should fix your recovery.
Sent from my MB860 using Tapatalk 2

Thanks for a reply but I did that as well and ended up getting an error. "Failed to process command flash:recovery error(0x180002)". I tried this method at first, received that error then tried to flash cwm through rom manager and recieved failed to boot2 starting rsd protocol.
Sent from my MB860 using XDA

Try unlocking bootloader again just to make sure ... Maybe that factory firmware closed hole on you when flashed.. Then flash cwm image ....

xRawwRRRRx said:
Thanks for a reply but I did that as well and ended up getting an error. "Failed to process command flash:recovery error(0x180002)". I tried this method at first, received that error then tried to flash cwm through rom manager and recieved failed to boot2 starting rsd protocol.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
XRange said:
Try unlocking bootloader again just to make sure ... Maybe that factory firmware closed hole on you when flashed.. Then flash cwm image ....
Click to expand...
Click to collapse
+1. You'll always need to re-flash pudding BL after using an .sbf.

ghost_og said:
+1. You'll always need to re-flash pudding BL after using an .sbf.
Click to expand...
Click to collapse
Would you happen to have the file? 2.3.6
Sent from my MB860 using XDA

xRawwRRRRx said:
Would you happen to have the file? 2.3.6
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Think what you seek lies here in Puddling thread..
http://forum.xda-developers.com/showthread.php?t=1136261

XRange said:
Think what you seek lies here in Puddling thread..
http://forum.xda-developers.com/showthread.php?t=1136261
Click to expand...
Click to collapse
adding to this: the automatic unlocker should work for you too. I had to re-unlock my phone after Motorola upgraded it when it was out for repairs. Worked like a charm.
(IF you're on AT&T)

ghost_og said:
adding to this: the automatic unlocker should work for you too. I had to re-unlock my phone after Motorola upgraded it when it was out for repairs. Worked like a charm.
(IF you're on AT&T)
Click to expand...
Click to collapse
Thank you soo much! I had to "re-unlock" bootloader! Now i have my custom recovery! One more thing have you or any other reader out there figured out a solution to my camera problem?
Sent from my MB860 using XDA

Try one custom roms see if that fixes camera, if not you might have carry phone for bad camera...

Simple question about firmware flashing, can't seem to find the answer

So I see plenty of ROMs posted that say you need such and such firmware to run it, but never instructions on flashing firmware. I used Sunshine, so I am s-off/rooted but bootloader is still locked, running stock ROM. My phone tries to do the OTA firmware update from last week, but fails because the system partition has unexpected data. I thought if I flashed stock recovery back that I could get OTA's, I guess not.
My question is, what is the best way to manually flash the 1.82.605.6 firmware? Do I just rename the .zip I have, put it in the root of the sd and boot into download mode? All I'm worried about is not losing s-off and of course not bricking my device. I really don't care if data gets wiped, but I'd like to avoid it if possible. Any help would be greatly appreciated it, I've been looking for a solid answer to this for a couple of days because I didn't want to post this question and get chewed out for not looking first, but I can't seem to find a clear 100% answer to this. Thank you in advance.

jkhtx said:
So I see plenty of ROMs posted that say you need such and such firmware to run it, but never instructions on flashing firmware. I used Sunshine, so I am s-off/rooted but bootloader is still locked, running stock ROM. My phone tries to do the OTA firmware update from last week, but fails because the system partition has unexpected data. I thought if I flashed stock recovery back that I could get OTA's, I guess not.
My question is, what is the best way to manually flash the 1.82.605.6 firmware? Do I just rename the .zip I have, put it in the root of the sd and boot into download mode? All I'm worried about is not losing s-off and of course not bricking my device. I really don't care if data gets wiped, but I'd like to avoid it if possible. Any help would be greatly appreciated it, I've been looking for a solid answer to this for a couple of days because I didn't want to post this question and get chewed out for not looking first, but I can't seem to find a clear 100% answer to this. Thank you in advance.
Click to expand...
Click to collapse
Custom rom or not?
Sent from my HTC6545LVW using Tapatalk

dottat said:
Custom rom or not?
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
No, I'm still on the stock rom. All I've done is s-off and root. I was running twrp but I flashed back to stock.
I have 1.82.605.6_NoBoot_NoRecovery_firmware.zip which I'd like to flash, I'm just unclear on the best method, and I don't want to do anything to my $700 phone unless I'm 100% sure about what I'm doing.

jkhtx said:
No, I'm still on the stock rom. All I've done is s-off and root. I was running twrp but I flashed back to stock.
I have 1.82.605.6_NoBoot_NoRecovery_firmware.zip which I'd like to flash, I'm just unclear on the best method, and I don't want to do anything to my $700 phone unless I'm 100% sure about what I'm doing.
Click to expand...
Click to collapse
Just flash my ruu. Then twrp and your supersu zip. Won't wipe won't change s-off status.
Sent from my HTC6545LVW using Tapatalk

dottat said:
Just flash my ruu. Then twrp and your supersu zip. Won't wipe won't change s-off status.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
See that's what everyone is saying, just flash the ruu, and it's assumed that everyone knows what that means, but I don't. By that do you mean rename my .zip, place in the root of sd and reboot to download mode?

dottat said:
Just flash my ruu. Then twrp and your supersu zip. Won't wipe won't change s-off status.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
I found your thread, thanks for your help. Hope I didn't come off as having attitude, looking back it seems kinda like I was. Thank you for your help.