Database Develop

Got a Droid with software issues for $50, Now need Help!

SEE MY NEXT POST! I Got it, but it boot-loops.
My Friend said his Droid forgets contacts, is loosing texts & was acting up after the 2.2 software update so Verizon replaced it. But only took the battery so he still has it. I could wipe, root, n install CM6 and most likely get it running good right. I'm thinking after a radio and OS reinstall it might be ok.
Is $50 worth it. Where can I get an originally battery? And will the phone still work if I call and register it on another Verizon account?
Thanks for any help.

So worth it....ebay

OK, so I got the Droid and I have it home. I got a battery cover and battery from my friend at verizon.
So, what Recovery options are there for the Droid. I don't know anything about the droid. I've always done things on my Nexus One only. I tried holding X while booting and this is the screen I get
http://twitpic.com/2lpio0
and this Droid has an endless boot-loop. I'm not sure whats wrong atm. or what verizon may have tried to do to fix it for the customer. What should be my first move. How can I boot into the stock recovery and do a factory wipe?

Update. I've loaded SPRecovery ESE81 while following the Cyan Wiki for the Droid. I've tried a Full Wipe, and Cache wipe. It still does an endless boot-loop.. I'm not sure what my next move is from here.
I was going to keep following the Cyan Wiki for the Droid and install the rooted ESE81.update file from the Wiki. But that is 2.1 and I'm pretty sure the phone has 2.2 So the radio's wouldn't match. Or would flashing the ESE81 file from the wiki also do the radio? (if so from there I'd be rooted and can flash some CM6 like I have on my Nexus One). I'm not sure what to do next. I don't know how messed up it is, or what all Verizon did. but for now it boot-loops, and it has SPRecovery ESE81 on it.. What should I do next. What steps should I take?
Thanks for any help!
*Update - I've learned Droid doesn't have Radio mis-match problems. thats only GSM phones, so from here I should just flash the rooted ESE81 and from there flash CM6 right?

double post
Well, something messed up here. I was able to load 2.1 on the phone it booted once, seemed fine and on reboot I'm back to boot loops all over again, tried wipe and reflash. Same thing. I then flashed CM6.0-Droid and now I get the CM boot animation, but it still is having a boot loop. I'm not able to get it to boot into the system other than that one time. WTH.
idea's? oh and how do I charge the Droid without it turning on, when I plug it in, it boots. (N1 doesn't do this)

Try using RSDlite to flash ese81 while in the bootloader screen. (Bootloader - power and up on d-pad)
Sent from my Droid using XDA App

xguntherc said:
idea's? oh and how do I charge the Droid without it turning on, when I plug it in, it boots. (N1 doesn't do this)
Click to expand...
Click to collapse
that is a crazy issue with Motorola. I don't know why they do like that.
my solution is ... charge the battery using external charger

Bootloop after trying to restore w/ Bootstrap

So I was trying to restore back to my stock ROM backup using the boot strap recovery. There weren't any errors during the process of restoring the image but when it was time to boot the phone up it would stay in a bootloop.
I have tried factory reset with the power button and volume buttons but it'd go straight back to the loop.
I am trying really hard to understand this whole adb thing with the sdk program but I have no idea how to use it.
Can anyone please help this noob?

Return to stock - Windows.
FAQ sticky in the Bionic Development forum.

Thanks for the reply. I'll try this out when I come home from work.
Also, I reactivated my droid x until then. Will I need to go to Verizon for a new sim card for my bionic once I can start it up again?

I don't think so, but I am not sure. Have not bootlooped yet myself or had to FXZ.

I believe you may have to go for a new SIM card. The way the Verizon explained it to me when I returned my Charge was when you deactivate from a 4G to 3G only phone, that SIM is lost. However, 4G to 4G is fine.
Wouldn't hurt to try, but a good possibility you will have to.
Sent from my DROID BIONIC using xda premium

idefiler6 said:
I don't think so, but I am not sure. Have not bootlooped yet myself or had to FXZ.
Click to expand...
Click to collapse
About 2 hours after I said this, I bootlooped. Good thing this FXZ method works!!

haha yeah with all the new roms u cant help but to explore.
btw after 5 FAILED flashes I tried one more time with rsdlite and it finally worked!
It took about 20-25 minutes for the whole process to fully boot up my phone but I am very happy and thankful for the people on this forum.
The weird thing is that when it booted up... it booted up to an old restore of UNL3ASH3D. confused but im happy its fully functioning.

You won't need a new SIM card. I did an FXZ restore after I rooted my phone, unrooted it (didn't need to have it rooted because there were no ROMs and no CWM yet) and it wouldn't let me root again so I flashed to stock and it rooted just fine. You will need to flash the radio again though (or at least I did after installing DroidTh3ory's ROM because it kept showing 3G in spots I know i had 4G, worked fine after I flashed).

Broken out of the box?

Hey guys, I do no not own this phone (just picked up a Nexus 5) but, my dad does. He has been waiting for MONTHS to get his hands on this. It is his first Android device and he was able to ditch his work iPhone for it. However, he has been having an absolutely horrible experience:
I was remotely walking him through setup (moto transfer with iCloud to gmail account, etc etc).
- He turned on his phone, set up wifi, entered account credentials, played around for a minute or two.
- After this, he was prompted for an update, I told him to accept it
- After he accepted it, the phone WILL NOT TURN on. It boots to the homescreen, says it is "activating" the device, then it needs to restart.
- When it restarts, he sees the following attached screenshot.
I am assuming this was the Kit Kat update. I know tons of people have had problems with this (yes, I read the forums before posting, even though it is not my device). However, everyone with problems seemed to be rooted/not on stock. He is COMPLETELY stock.
If he chooses to reboot normally, he gets the homescreen, activation, then, it turns off and goes back to the attached screen.
If he chooses recovery, it goes back to this screen.
I'm not sure how an OTA could jack a phone up that was completely stock.. But it has happened.
Is there anything I can do remotely to help him start using his new phone? As I said, he has been excited for months for this phone and now just wants to throw it against the wall.
Is this screenshot the fastboot screen? If so, can I use the "fastboot erase cache" command?
Any *detailed* answers would be greatly appreciated... I'd love to get this working for him ASAP.
Thanks everyone!
View attachment 2415287

This is a pretty horrible out of box experience for something he was so excited about. I'm hoping this is something I can just do while remotely controlling his PC... I feel bad for the guy

fastboot erase cache
and then flash a stock recovery
Enviado desde mi XT1052 usando Tapatalk

waiflih said:
fastboot erase cache
and then flash a stock recovery
Enviado desde mi XT1052 usando Tapatalk
Click to expand...
Click to collapse
Not having this phone myself, how do I flash a recovery if I can't access current recovery or boot? Can I flash with a locked bootloader? Is the screen my dad is seeing the fastboot screen?
Any ideas how a stock out of the box phone would encounter this?
Thanks!
Sorry it's just hard to not have a device and jump into this when there are a million threads and it is completely different than any device I've owned (also I have no hands on time with it).
Thanks again. The more details the better so that I can do this remotely.
Sent from my Nexus 5 using XDA Premium 4 mobile app

yes that screen is fastboot mode, so u can download the files for ur rom here
http://sbf.droid-developers.org/ghost/list.php
and use fastboot to flash only recovery
Enviado desde mi XT1052 usando Tapatalk

Ok. I will have to figure out how to flash sbfs via fastboot then. I'm assuming it is a simple set of commands. I will try and find a tutorial when I am not driving. Thanks
Sent from my Nexus 5 using XDA Premium 4 mobile app

EmperorX said:
Ok. I will have to figure out how to flash sbfs via fastboot then. I'm assuming it is a simple set of commands. I will try and find a tutorial when I am not driving. Thanks
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which model/carrier of phone does your dad have?

Xatt said:
Which model/carrier of phone does your dad have?
Click to expand...
Click to collapse
He's on Verizon, 16gb.
So confused as to how this happens fresh out of the box. Don't know how it's possible. I'm determined to fix it for him today though so he doesn't have to wait even longer
Sent from my Nexus 5 using XDA Premium 4 mobile app

If he just bought it, why are you messing around with this? Take it back to the retailer you bought it from and tell then what happened... Get a new phone...
AT&T Moto X rocking rooted 4.4

theraffman said:
If he just bought it, why are you messing around with this? Take it back to the retailer you bought it from and tell then what happened... Get a new phone...
AT&T Moto X rocking rooted 4.4
Click to expand...
Click to collapse
He got it customized from MotoMaker... If it's a relatively simple fix (and it's not a hardware issue) I'd rather do it myself so he doesn't have to wait yet again for who knows how long.
Sent from my Nexus 5 using XDA Premium 4 mobile app

waiflih said:
yes that screen is fastboot mode, so u can download the files for ur rom here
http://sbf.droid-developers.org/ghost/list.php
and use fastboot to flash only recovery
Enviado desde mi XT1052 usando Tapatalk
Click to expand...
Click to collapse
I'm assuming I can use any of the builds from verizon there? I'd like to get him to update OTA and see if it works this time or not... Was thinking about flashing one of the three 4.2.2 ones

EmperorX said:
He got it customized from MotoMaker... If it's a relatively simple fix (and it's not a hardware issue) I'd rather do it myself so he doesn't have to wait yet again for who knows how long.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
EmperorX I work for Moto. If you wouldn't mind providing the IMEI I'll get our engineers to take a look. You can PM me. Thanks!

I found this toolkit:
However, i'm assuming the fastboot menu will not work to just flash stock as you need to be in "Android or hboot"
The fastboot screen I took the picture of is not the same thing as hboot correct?

They are interchangeable terms. Hboot refers typically to an HTC bootloader

gunnyman said:
They are interchangeable terms. Hboot refers typically to an HTC bootloader
Click to expand...
Click to collapse
Awesome, looks like I may be able to fix this for him after all. Just need to remotely get androidsdk and adb setup on his computer with RSDlite as backup if this toolkit doesn't work and I *should* be able to make this happen. I think i've got enough info to do this now. Thanks guys!

EmperorX said:
He got it customized from MotoMaker... If it's a relatively simple fix (and it's not a hardware issue) I'd rather do it myself so he doesn't have to wait yet again for who knows how long.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Gotcha, makes sense not to want to go through all that. Sorry this happened to your dad. First I've heard of an issue this big on the moto x.
AT&T Moto X rocking rooted 4.4

theraffman said:
Gotcha, makes sense not to want to go through all that. Sorry this happened to your dad. First I've heard of an issue this big on the moto x.
AT&T Moto X rocking rooted 4.4
Click to expand...
Click to collapse
He was on the phone with Motorola "tier 2" support this morning for 3 hours. Their solution was to order a new phone and expedite shipping and return the old one when it gets here. I'm going to try this way first. They said this happens to "1 in 10,000" people. Lol, he's a lucky guy!

Well, now it's stuck on the fastboot screen with the following error:
No valid PIV block in SP for system
piv validation failed (system)
boot up failed
-__-

EmperorX said:
Well, now it's stuck on the fastboot screen with the following error:
No valid PIV block in SP for system
piv validation failed (system)
boot up failed
-__-
Click to expand...
Click to collapse
Sounds like the phone's partitions are all jacked up. Get a new phone is the solution.

EmperorX said:
Well, now it's stuck on the fastboot screen with the following error:
No valid PIV block in SP for system
piv validation failed (system)
boot up failed
-__-
Click to expand...
Click to collapse
what probably happened was your dad never activated the phone then tried to take an ota or something like that and it got all jacked up. Alternatively, he could have (for some reason) gotten the 4.4 OTA even though the phone was on original stock FW. This could have f'd the phone up if it skipped the 4.2.2 OTA. If you need to help you dad out, download teamviewer or logmein (remote computer access programs) and just guide him through when to plug the phone in etc.
Not sure about the error you are getting but it could be because you are flashing the wrong FW for the phone, possibly an older FW or an updated FW and the order you are flashing it could be causing the error. You can fix this relatively easily if you were more familiar with fastboot. I can try and walk you through some stuff as well on gchat if you need some help. I could also remote into your dads computer and do everything that needs to be done (he could then remove my ability to remote in clearly). All that being said Im fairly busy so just answering some questions for you would be easier but more time consuming for your dad. For starters, you probably should be flashing the 4.2.2 FW found on sbf. it is the middle fw for verizon on the list. You also can probably just use rsdlite since he hasn't set the phone up. It is super easy. Just go to the thread for rsd lite back to 100% stock and you will be good to go. Then make sure he activates and sets the phone up and everything before he takes the OTA this time.

[Q] VZN Moto X DE TWRP Bootloop

i looked. i swear. however, can't find anything that addresses my issue or at least i don't recognize it at my issue.
I have a DE Moto X on VZN.
unlocked bootloader
reverted from 4.4 to 4.2.2
flashed TWRP-2.6.3.1-ghost-4.4
Everything was working just fine and i couldn't leave well enough alone. I was screwing around and tried to flash/install/whatever an apk that would invert gmail colors....basically white to black. i'm not sure if it was before or after i did that but i created a backup in case it screwed something up and i wanted to revert. well, i loaded it and nothing happened so i went to restore my device from the backup i had just created and TWRP told me it was complete/successful or something and gave me the option to reboot. i did and now my phone is stuck in a boot loop. i've tried to restore several times to no avail.
i can get into bootloader menu but normal start up starts the boot loop process again. TWRP loads if i go into recovery. phone isn't recognized by RSD Lite. not sure what to do.
Can anyone help or tell me what additional info you need to be able to help?

texaslegend said:
i looked. i swear. however, can't find anything that addresses my issue or at least i don't recognize it at my issue.
I have a DE Moto X on VZN.
unlocked bootloader
reverted from 4.4 to 4.2.2
flashed TWRP-2.6.3.1-ghost-4.4
Everything was working just fine and i couldn't leave well enough alone. I was screwing around and tried to flash/install/whatever an apk that would invert gmail colors....basically white to black. i'm not sure if it was before or after i did that but i created a backup in case it screwed something up and i wanted to revert. well, i loaded it and nothing happened so i went to restore my device from the backup i had just created and TWRP told me it was complete/successful or something and gave me the option to reboot. i did and now my phone is stuck in a boot loop. i've tried to restore several times to no avail.
i can get into bootloader menu but normal start up starts the boot loop process again. TWRP loads if i go into recovery. phone isn't recognized by RSD Lite. not sure what to do.
Can anyone help or tell me what additional info you need to be able to help?
Click to expand...
Click to collapse
So you've tried restoring your nandroid prior to the flash, and still get bootloops, right? Have you tried wiping the caches? You can also try a full wipe and see if that gets you out of the boot loop, and then you can go back and try to restore your nandroid.
If all else fails and you can get into fastboot, there are instructions here on getting back to stock: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images. I would pull my backup from the device first from within TWRP (although if you don't erase userdata it should still be on the phone). You'll have to re-flash TWRP, but that process should get you back to having a working phone.

there might also be a problem with the fact that oyu were running 4.2.2 and using twrp that was built for 4.4. there is a twrp that was built for 4.2.2 so i don't know why you used the one built for 4.4. don't know what the differences are if any that would affect running twrp 4.4 on a 4.2.2 firmware but there may be some major issues.

You could try manually deleting everything with fastboot, then boot into recovery to restore your backup before flashing the 4.2.2 TWRP.

Thanks for the help. I thought I edited my post to say I fixed the problem. Did that with a wipe from the twrp bootloader our whatever that screen is called when you not into recovery.
Thanks
Sent from my XT1060 using xda app-developers app

I am curious as to why you downgraded back to 4.2.2?

Mainly for FoxFi WiFi. I use it on road trips for my kid's iPad and Nabi.
Sent from my XT1060 using xda app-developers app

If you have an unlocked bootloader, why not use one of the available mods with 4.4?

First I guess would be because I didn't know about it. I wasn't really planning on unlocking and rooting to begin with.
I got the DE because at the time I needed a phone it was the only x I could get with 32GB.
Which mood are you talking about I might have to check it out
Sent from my XT1060 using xda app-developers app

texaslegend said:
First I guess would be because I didn't know about it. I wasn't really planning on unlocking and rooting to begin with.
I got the DE because at the time I needed a phone it was the only x I could get with 32GB.
Which mood are you talking about I might have to check it out
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
There's a flashable zip in this thread.
http://forum.xda-developers.com/showthread.php?t=2561560
It's for 4.4 not 4.2 though, don't flash it unless you update.

Make it easy on yourself and use the Xposed module http://forum.xda-developers.com/showthread.php?t=2601859

HELP: Phone rebooting, VZW Developer Edition

Kind of stuck here.
I have VZW developer edition. Rooted, 4.4 with TWRP
Foolishly I accepted the OTA update to 4.4.2, this failed of course but now my phone is constantly rebooting. It stays up for a few minutes then powers back to recovery.
Help !!!
Thanks.

Its a Dev phone just fxz and re-root
Sent from my XT1080 using xda app-developers app

bigv5150 said:
Its a Dev phone just fxz and re-root
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
If only I had a clue what that meant

homemadehitshow said:
Kind of stuck here.
I have VZW developer edition. Rooted, 4.4 with TWRP
Foolishly I accepted the OTA update to 4.4.2, this failed of course but now my phone is constantly rebooting. It stays up for a few minutes then powers back to recovery.
Help !!!
Thanks.
Click to expand...
Click to collapse
Can you get into the bootloader (hold power + volume down)? If so, you'll probably need to reflash the stock recovery before the update will install.

Thanks, after I stopped panicking and calmed down I was able to flash Stock Recovery and then the next reboot caused the standard update to work. Kind of surprised really, still rooted etc.
Right now phone is working but Wi-Fi indicator is not lit, even though it is using the wi-fi.

Clear cache and dalvik cache?
Sent from my XT1060 using Tapatalk

homemadehitshow said:
Thanks, after I stopped panicking and calmed down I was able to flash Stock Recovery and then the next reboot caused the standard update to work. Kind of surprised really, still rooted etc.
Right now phone is working but Wi-Fi indicator is not lit, even though it is using the wi-fi.
Click to expand...
Click to collapse
Well you have the dev edition, they aren't going to take root from you. Don't know what's up with your wifi, though. When I updated I ended up having to restore a backup and updating again because of several extremely strange problems.

homemadehitshow said:
Thanks, after I stopped panicking and calmed down I was able to flash Stock Recovery and then the next reboot caused the standard update to work. Kind of surprised really, still rooted etc.
Right now phone is working but Wi-Fi indicator is not lit, even though it is using the wi-fi.
Click to expand...
Click to collapse
Disable WiFi and turn it back on right after.
Sent from my Moto X DE

Yep, everything seems to be working again now.
I have blindly followed instructions for flashing etc. using Fasboot but I think I'm finally getting a better feel for what is going on with it.

homemadehitshow said:
Yep, everything seems to be working again now.
I have blindly followed instructions for flashing etc. using Fasboot but I think I'm finally getting a better feel for what is going on with it.
Click to expand...
Click to collapse
Good job taking some initiative. Not as difficult as you thought it'd be right?

the verizon 4.4.2 SBF file is out so any issues anyone is having they can just flash the whole SBF file and be complety stock 4.4.2
enjoy
http://sbf.droid-developers.org/download.php?device=0&file=841