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] Possible Brick

Hope you guys can help with this.
I updated to the rooted Gingerbread leak. Didn't really like it so I made the retarded mistake of just flashing Liberty to my phone. Completely forgot that if I wanted to go back I had to SBF.
So I went to SBF back to Froyo. The SBF went through with no issue but now my phone won't boot. When booting normally or going to recovery I get this. I've tried two computers and can't get either to recognize my phone, but my phone does recognize that it's plugged in.
Now I understand that if you have bootloader 30.04 and try to go back to Froyo you'll basically get a brick. Is this true or is there some way to fix this that's been documented that I'm oblivious of? Thanks very much if you guys can help me.

I have bootloader 30.04 and I have SBF'D back to froyo twice with no issues, are you sure you have the complete SBF file and not the system only file?
Sent from my DROIDX using XDA Premium App

[Q] I'm stuck - Bootloader Err after SBF

Background:
I've rooted then unrooted my Droid X in the past. Today I tried to install the OTA Gingerbread update. After the download and the reboot the Droid X booted into Clockwork Recovery (as has been normal recently). After selecting reboot, the phone reboots and tells me the update has failed.
I attempted to SBF using this guide: droidforums dot net/forum/droid-x-hacks/99958-rooolers-guide-root-backup-roms-2-2-ota.html#3.
The file I used was: VRZ_MB810_2.3.15_1FF_01.sbf.
Now:
I have the following on my screen (black).
Bootloader
30.04
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Connect USB
Data Cable
I searched and found that I needed to use a 2.3.34 SBF, so I found this: SHADO_X6_2.3.34_SYSTEM-ONLY.sbf.
After SBFing with the new SBF I have the same result.
I'm stuck, I'm short on time, any help would be appreciated.
Thanks!

pvliii said:
Background:
I've rooted then unrooted my Droid X in the past. Today I tried to install the OTA Gingerbread update. After the download and the reboot the Droid X booted into Clockwork Recovery (as has been normal recently). After selecting reboot, the phone reboots and tells me the update has failed.
I attempted to SBF using this guide: droidforums dot net/forum/droid-x-hacks/99958-rooolers-guide-root-backup-roms-2-2-ota.html#3.
The file I used was: VRZ_MB810_2.3.15_1FF_01.sbf.
Now:
I have the following on my screen (black).
Bootloader
30.04
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Connect USB
Data Cable
I searched and found that I needed to use a 2.3.34 SBF, so I found this: SHADO_X6_2.3.34_SYSTEM-ONLY.sbf.
After SBFing with the new SBF I have the same result.
I'm stuck, I'm short on time, any help would be appreciated.
Thanks!
Click to expand...
Click to collapse
You need the full sbf.
Sent from my DROIDX using XDA App

You needed to use VRZ_MB810_2.3.34_1FF_01.zip. you can try that, if it doesn't work you might have completely bricked it.
Sent from my DROIDX using XDA App

Same thing happened to me this morning, but different ERR numbers. Verizon & Motorola were no help. Took it to the Verizon store, they forced Froyo 2.2 back on the phone. Its working now, but keeps trying to update. I am waiting until I get home to back up everything, then I will wipe the phone and let it update on its own. Seems to be a bootloader issue with either Bootstrap or rooting.
Sent from my DROIDX using XDA App

If I'm on GB my phone ALWAYS gives me a "code corrupt" after running the 2.3.340 full SBF. A system SBF afterwards always fixes the issue. Weirdly, I can't just do the system SBF. Its like I have to brick the phone with the full SBF and then repair it with the system SBF.

ashish8 said:
You needed to use VRZ_MB810_2.3.34_1FF_01.zip. you can try that, if it doesn't work you might have completely bricked it.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I'm running VRZ_MB810_2.3.34_1FF_01.sbf now. I'll post back with my results.
Thanks everyone for the input so far.

After flashing with VRZ_MB810_2.3.34_1FF_01.sbf it looks like we're back in business. Everything looks the way it was before I started all this.
I'll try updating to GB now and report back.

ashish8 said:
If I'm on GB my phone ALWAYS gives me a "code corrupt" after running the 2.3.340 full SBF. A system SBF afterwards always fixes the issue. Weirdly, I can't just do the system SBF. Its like I have to brick the phone with the full SBF and then repair it with the system SBF.
Click to expand...
Click to collapse
You should probably download the file again

[Q] SBF and now stuck SOS

Hey guys so i mistakenly updated to 2.3.3 the other day and really didn't like it so I rooted my phone, and was about to flash Miui when I changed my mind and tried to Deodex my phone, because i had already rooted the phone I tried to do the manual deodex shown in the "noobs guide post" i did everything according the the instructions but it didn't work. So I grabbed the SHADO_X6_2.3.34_SYSTEM-ONLY.SBF file and loaded it in RSD lite to flash back and un-root my phone.. well half way into the process the phone rebooted to the Red M logo.. and everything I've done since has been to no avail.. i tried to download other SBF files that were supposed to be the "full" sbf but for some reason RSD lite wont even let me flash them... If i boot holdig the menu button the phone will bring up the recovery menu and from there i can still select the 4 different options but even after doing the factory data reset and formatting the catch nothing seems to change.. I have been looking for several hours now to get this working and I'm getting really frustrated. So i just want to apologist if this situation has already been dealt with but if you guys could help me out to get my phone working again i would be incredibly great full.

Look into the full sbf using the linux iso 1kds did, wish I would post links
Sent from my DROIDX using XDA App

STAYFROSTY777 said:
Look into the full sbf using the linux iso 1kds did, wish I would post links
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I think I read something about the but havn't been able to find where to get the linux iso, am i correct in saying you can temporarily boot linux from the disk to do this? BTW Thank for the sugestion, my wife was about to make me sleep in the dog house for messing my phone up lol so when i get off work i'll try to find the Linux iso, maybe i can even find a thred that has a walk through to fix it.
In the event that I do get everything working again, is it easier to flash roms from gingerbread or from Froyo? or if you want a gingerbread rom i'm assuming you have to flash it from gingerbread correct?

Yes your correct about the roms from my understanding, and haha I know the feeling, yeah just burn the iso onto a disc (its not very big) on boot from disc on your computer, follow the instructions, and it will sbf you to froyo, probably be doing this for me tomorrow since in have some problems with tethering, good luck man, let me know how it goes
Sent from my DROIDX using XDA App

sweet I'll be happy to have my phone back.. lol i miss it, i feel lost without it to be honest. I never knew how attachedi was to my phone. but anyway I'll forsure let you know how it goes i'm praying that this will fix my phone, I have never really come accross a true definition of how to tell if your phone is "bricked" or not. it seems like everyone says their phone is bricked just because they cant get it to boot up but i always thought that the term "bricked" refered to the phone being so screwed up that you can no longer fix or salvage it.. does anyone know the actual definition?

I was recomended to look at this web page it was incredabley helpfull!! i'm running throught the process right now so i'll report my results when done but i'm pretty optimistic about this.
http://www.droidxforums.com/forum/droid-x-sbf/23638-linux-solution-your-windows-rsd-lite-problems.html

Awesome man, i used that method, might be doing again after work today to change roms
Sent from my DROIDX using XDA App

yeah i was so happy that it worked although i was still worried at first because the phone still boots to the Red M logo but after a sec it goes the the droid eye and then load GB anyway now i just need to really understand how to deodex and flash a rom right way, but at least now i know how to fix the phone if i screw something up. One more question, would you guys say that my phone was considered bricked? if so than is it safe to say that there is nothing you can do to it that you can't fix using the Linux boot SBF method?
btw the actual page i used with all the downloads of Linux is right here in case anyone else needs it.
http://www.droidxforums.com/forum/droid-x-sbf/23638-linux-solution-your-windows-rsd-lite-problems.html

It doesn't sound like it was bricked, and so for I haven't seen anything to bad where you can just use the Linux way, unless you mess up the hardware lol

well thats somewhat good to know lol thanks for all the advice

Anytime buddy, always glad to help
Sent from my DROIDX using XDA App

The reason why the first sbf didn't work is because you used a SYSTEM only Sbf and it was for froyo 2.3.340 instead of the FULL sbf which reverts everything back to froyo instead of just the system.
Sent from my DROIDX using XDA App

hmm so how is the system only sbf any different than doing a factory reset while running 2.3.340? i mean does doing the system only sbf undo rooting your phone?

[Q] 4.5.621 uprgrade failed

I have a droid x that is rooted and has the hack so I can wirelessly tether. I used the voodoo ota root keeper to try and keep my root. When I try to install the update it fails. I also have clockworkmod recovery installed. Any suggestions?
rkshack

Rkshack said:
I have a droid x that is rooted and has the hack so I can wirelessly tether. I used the voodoo ota root keeper to try and keep my root. When I try to install the update it fails. I also have clockworkmod recovery installed. Any suggestions?
rkshack
Click to expand...
Click to collapse
If you do take it there is quite a hassle getting it back to be rootable but if you must? You will need the latest version of rsdlite the desired sbf .602 or .605 which will revert it back to stock then you can take the OTA. My guess is somewhere along the way you froze or uninstalled some of the preinstalled bloatware? Which can cause the update to fail this was my case at least I sbfed to. 602 then took 2 OTA'S to .621 unfortunatley I regreted it you may want to look around at method to freeze updater instead your rooted try a different rom or 2 before making the decision

rom question
Thepooch said:
If you do take it there is quite a hassle getting it back to be rootable but if you must? You will need the latest version of rsdlite the desired sbf .602 or .605 which will revert it back to stock then you can take the OTA. My guess is somewhere along the way you froze or uninstalled some of the preinstalled bloatware? Which can cause the update to fail this was my case at least I sbfed to. 602 then took 2 OTA'S to .621 unfortunatley I regreted it you may want to look around at method to freeze updater instead your rooted try a different rom or 2 before making the decision
Click to expand...
Click to collapse
Where are the best areas to look for info on roms. I have clorkwork rom manager but there are not any roms I recognize.
If I were to back up my rom and then use titatanium back up would I be able to restore to my current state.
rkshack

Rkshack said:
Where are the best areas to look for info on roms. I have clorkwork rom manager but there are not any roms I recognize.
If I were to back up my rom and then use titatanium back up would I be able to restore to my current state.
rkshack
Click to expand...
Click to collapse
RootzWiki is the best place to find roms.
You can make complete backups in ClockworkMod Recovery of your entire rom. I would use MyBackup Root to backup things like individual apps, data, SMS, etc.
Sent from my DROIDX using Tapatalk

update failed
Rkshack said:
I have a droid x that is rooted and has the hack so I can wirelessly tether. I used the voodoo ota root keeper to try and keep my root. When I try to install the update it fails. I also have clockworkmod recovery installed. Any suggestions?
rkshack
Click to expand...
Click to collapse
I also had the same failure, it was due to my having removed some of the bloatware. I loaded the 605 SBF file and rooted this installed al the root programs i would need along with voodoo ota and made a root backup, ran all my programs and did the update, all went ell and I was able to renew root with voodoo ota keeper. so far i have had no problems and am on the 621 update and fully rooted. Titanium backup works fine and I have been able to remove the bloatware.
Hope this helps and i am not too late.

From what every been saying, don't upgrade to 621. Just flash a custom rom right now since you are rooted and you can sbf back to 602 or 605 as needed.
I have 2 Droid X and both running CM7 and its awesome. I tried MIUI and Gummy but couldn't get into it.

4.5.621 install failure
Greetings. This looks like the right thread for this issue, but if not, please redirect me.
Some background:
DroidX
Android version 2.3.3
System version 4.5.605.MB810.en.US
currently rooted
Being a laggard, I did not accept the 621 update when first offered through OTA. My 4.5.605 DroidX was rooted and I'd read that I'd have to either unroot or "hide" root in some manner. It seemed like a bit of trouble and I had other life issues at the time.
After things cleared, I contacted VZ and they pushed the upgrade again. After "unrooting", I accepted the OTA upgrade, but each installation attempt failed after a successful download. No other diagnostics, just "the update failed". I tried this multiple times after reboots, battery removal, cache clearing and such. I then did a factory reset and tried again - still the same sequence, successful download, install now, update failed.
So I called VZ and Moto. They suggested accepting the update while attached to a solid WiFi. All the same tricks were turned as with the OTA (another factory reset, clear cache, remove/replace battery) only these attempts used the WiFi (excellent signal). Same failure.
Moto then suggested I ship in the unit and for $110 they would handle it. Right.
So I found Blur_Version.4.5.621.MB810.Verizon.en.US.zip, downloaded it to the SD card and attempted to install using the recovery mode menu. This also fails but at least offers up the message: assert failed apply_patch ("system/app/AccountAndSyncSettings, apk", "-" then some odd number letter sequences followed by "error in /tmp/sideload/package.zip status 7.
I've since rerooted just out of curiosity to see if that would still work.
All this to fix the irritating bug of the phone powering back on by itself.
Any hints or advice?
Thanks.
-Joe

Sending your device in is not necessary at all.
It seems that you have removed one of the systems stock apps. Replace any apps that you may have removed and attempt to take the update again.
Or, you can SBF back to 602 and take the OTA update to .621. Just be sure to back up everything that you need (not including app data).
Sent from my Galaxy Nexus using Tapatalk 2

missteps
Bloatware was renamed but I've been pretty careful not to delete anything... even kept a list of what was renamed and to what. All that has been rolled back but clearly something was missed. The only thing that threw me a curve was the symlink on the Madden Football app, but even that now looks pre-modified.
I take it that changes to ACLs would also glitch the update, but what about file timestamps? How pristine do these stock apps have to be?
I'll check them again since there's little to lose in doing so. If I can't find a discrepancy, the sbf to 602 will be the next step.
Ironically, the reason for embarking on the bloat removal at the outset was to cure the auto-power on bug, which is now supposedly fixed in 621.
But it's all about the learning.
Thanks again.

Help me please 2.3.3 to 2.3.4
I recently tried updating my phone....When I go to system settings and then go to About phone and then system updates.... I get this update 4.5.621.en.us. Then I click download and then when it finishes...I click install and then it shuts off and then it boots up and says " Failed to update software" Click ok... Then that's it... Someone please help me....
DETAILS of FIRMWARE and ETC..
System Version: 4.5.605.MB810.Verizon.en.us
Model number: DroidX
Android Version: 2.3.3 Gingerbread
Someone please help me with this annoying error

Legit-Reflex said:
I recently tried updating my phone....When I go to system settings and then go to About phone and then system updates.... I get this update 4.5.621.en.us. Then I click download and then when it finishes...I click install and then it shuts off and then it boots up and says " Failed to update software" Click ok... Then that's it... Someone please help me....
DETAILS of FIRMWARE and ETC..
System Version: 4.5.605.MB810.Verizon.en.us
Model number: DroidX
Android Version: 2.3.3 Gingerbread
Someone please help me with this annoying error
Click to expand...
Click to collapse
Have you tried downloading the update via wifi? Is the update appoximately 32MB? Have you tried to flash the 621 sbf?
Sent from my MB860 using xda app-developers app

palmbeach05 said:
Have you tried downloading the update via wifi? Is the update appoximately 32MB? Have you tried to flash the 621 sbf?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
I don't know how to flash, and yes i've tried multiple times downloading the update....help

Legit-Reflex said:
I don't know how to flash, and yes i've tried multiple times downloading the update....help
Click to expand...
Click to collapse
Download RSD Lite, i think the latest revision is 5.7. then download the 621 sbf, any necessary drivers, and it also helps to have the fastboot/adb package as well (even though fastboot is useless for us, still something good to have).
backup anything you need backed up or do a nandroid. reboot to bootloader. connect device to computer. start up RSD Lite. click show device. click the button that lets you browse for files. select 621 sbf. click start. sit back and let it do its thing and you'll be back up and running in no time

Links files and instruction on how to flash a sbf, are in my list
sd_shadow's [Collection] of Links for: Droid X (MB810)
Sent from my XT862 using Tapatalk

deboyz1014 said:
From what every been saying, don't upgrade to 621. Just flash a custom rom right now since you are rooted and you can sbf back to 602 or 605 as needed.
I have 2 Droid X and both running CM7 and its awesome. I tried MIUI and Gummy but couldn't get into it.
Click to expand...
Click to collapse
621 isn't all bad. It's easy enough to root it now with an apk called Framaroot and you will then have all the latest security updates from Motorola. If you do go with 621 you are then"stuck" there as it is not possible to go back to any earlier versions. Most of the most recently updated Roms work fine with it.
Sent from my SCH-I535 using Tapatalk