Database Users

giving up

i guess im going to call verizon with a bs reason i need a new phone. I have tried to update off nan from when i first rooted downloads but wont install dont understand sbfing and zip files wont load need serious help

What exactly is your phone doing right now? Is it stuck on the boot logo or what?

Its operational, I just flashed back to first nan and reloaded fission cause nothing I did the 928 back to stock ect worked, even tried updating without signing into google, unrooted and all that just frustrated it won't work
Sent from my DROIDX using XDA App

Ok, so you are up and running then. The only thing i was going to suggest is flashing SBF to get you back to Stock Android 2.2 and starting the process over again. I had a similar problem and wiped everything clean IOT get what i wanted. SBF'ing is simpler then you think, all you need is 2 files (rsdlite_4.8 and VRZ MB810_2.3.15 sbf). There's lots of articles here on it and I used them when I thought I bricked my phone. I started all over and was able to receive my 2.2.1 update.....finally!!

have you done the ota update? if so use 2.3.32.sbf you can get it by google and search droid x 2.3.32 sbf and its the first result. and dl rdlite 4.8. very easy to flash. several guides on here as stated.

I got it my drivers are up to date but won't find my phone.. And I'm leary all I got to do is that file and update?
Sent from my DROIDX using XDA App

Try running rsdlite as the administrator. (Right click rsdlite)

Now won't find it and I got a toshiba, only a little bit over a year old
Sent from my DROIDX using XDA App
EDIT - finally got rsd lite to recognize but first attempt failed trying again... pray
EDIT #2 - YEs, rebooted with 2.3.320 now to find 2.3.340 n flash it

Bricked? SBF from GB .576 to Froyo .340. HELP!!!!

So I tried to SBF back to 2.3.340 like I done before and now I get stocked on the red M logo. When I try to go into recovery I only get to the exclamation point and pressing the search button doesn't do anything!!
What can I do?
Help please. I don't see an answer on the forums
Thanks
UPDATE: I had the system-only SBF. Found the SBF full and it worked.
Now try to figure how to install the zip files because my phone is not letting me

Venc said:
So I tried to SBF back to 2.3.340 like I done before and now I get stocked on the red M logo. When I try to go into recovery I only get to the exclamation point and pressing the search button doesn't do anything!!
What can I do?
Help please. I don't see an answer on the forums
Thanks
Click to expand...
Click to collapse
It sounds like you did the "system only" sbf.. Make sure it's the full sbf
Sent from my DROIDX using XDA App

bigshotrob22 said:
It sounds like you did the "system only" sbf.. Make sure it's the full sbf
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Hey,
Is it even out? I don't see it online
EDIT: I think I found the full SBF. I'll try it. Thanks
UPDATE: bigshotrob22 you are awesome!! Thank you it worked!!! Now I have to cancel my order for the replacement LOL

That happened to me. I SBF'd back to .340 and still had the Red M logo from the Gingerbread .595.
I was unable to get into recovery at all. I eneded up not having the phone for the day and did the SBF again when I got home, you can still access the bootloader, just not recovery (or atleast I was able to) to do the SBF back to .340.
You said you have done the SBF before..my issue with was I did not go into the factory recovery FIRST and wipe all data. I have since done three SBF's and wipe data (in stock recovery, not BOOT STRAP) first. I wiped data, DID NOT REBOOT device. Powered off, and went straight into the bootloader to SBF.
That seems to work for me now.
If it is the samething that happened to me...the wipe did not completely do its job. I make it a habit to wipe 3-4 times before doing anything.

try pushing the volume button up& down at the same time instead of search
Sent from my DROIDX using XDA App

[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

[Q] Bricked phones droidx please help

So i bricked my friends droid x and its currently stuck in bootloader.
Bootloader
30.04
Err: A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
ok to Program
Transfer mode: USB
Ive been googling around and i havent seen anything. I wanted to know if there is anything.

There is a very easy way to fix it, but before I tell you, I need to know how this happened?
(Eg. installing an OTA update)
Sent from my DROIDX using Tapatalk 2

Have u tried to sbf?

This is were I would get my proper sbf and use Linux to reflash the phone as stock. Then data reset it. Reboot and start over. You'll get it. If IT's boot up problem occurs after reboot from flash then try different from that one is not working for you or directions not proper
Sent from my DROIDX using xda premium

Like mike said, sbf time. Its pretty easy, just download the Motorola drivers, SBF file, and RSD Lite. Can be done on windows or linux.
I would recommend using the .605 sbf file rather then .621, as .621 can't be easily rooted or sfb'd.
Link with step-by-step: ugh, im a new user so it wont let me post outside links. Its stickied on Droid X forums>Rescue Squad>Droid X SBF
Sent from my DROIDX using XDA

Just realized its stickied on this forum as well
Sent from my DROIDX using XDA

Trouble with sbf

I tried to install kitkat using the guide i found on here. Something went screwy and i was unable to reboot my phone without pulling the battery and unable to enter cwr. I was running miui.us rom so I figured i had to put the stock rom back on and try again.
I originally tried to flash with VRZ_MB810_2.3.34_1FF_01 and now the phone says service req. Flashing failed in RSD lite 6.1.4. So I tried flashing with VRZ_MB810_2.3.32_1FF_01 from TBH. Failed to flash as well.
Phone now says
Bootloader
30.04
Err:A5,70,70,00,00
MEM_MAP Blank
Service Req'd
Please point me in the right direction.
*Edit I just tried the ezSBF and it failed when it tried to upload to the phone. It rebooted the phone but phone stayed at black screen.

freelancenoob said:
I tried to install kitkat using the guide i found on here. Something went screwy and i was unable to reboot my phone without pulling the battery and unable to enter cwr. I was running miui.us rom so I figured i had to put the stock rom back on and try again.
I originally tried to flash with VRZ_MB810_2.3.34_1FF_01 and now the phone says service req. Flashing failed in RSD lite 6.1.4. So I tried flashing with VRZ_MB810_2.3.32_1FF_01 from TBH. Failed to flash as well.
Phone now says
Bootloader
30.04
Err:A5,70,70,00,00
MEM_MAP Blank
Service Req'd
Please point me in the right direction.
*Edit I just tried the ezSBF and it failed when it tried to upload to the phone. It rebooted the phone but phone stayed at black screen.
Click to expand...
Click to collapse
use 621 SBF or 621 ezSBF
sd_shadow's [Collection] of Links for: Droid X (MB810)
Sent from my XT907 using Tapatalk

Fixed it with 1FF-p3a_shadow_cdma_shadow-user-2.3.4-4.5.1_57_DX8-51-120111-test-keys-signed-Verizon-US. Then had to figure out how to get rid of the boot loop. Wipe data and cache fixed that. After all that I was finally able to install cm-11-20141226-UNOFFICIAL-shadow. Phone seems happy with it so im happy with it. First time in 2 years that i've even powered this phone on. Guess I had to learn how to flash all over again lol.

yes that is the 621 SBF
Sent from my XT907 using Tapatalk