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
Related
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).
Being the noob I am, I can't post this question in the dev forum. Does anyone know if Liberty is compatible with safestrap or not? I know the official instructions says CWM only, but I have read that many install using safetstrap without any problems.
That said, I for the life of me can't get it to boot after install. Are there any special tricks to get it to work with safestrap? Being a noob to Android (this D3 is my first foray into Android), I would like to stick with safestrap until I am very comfortable since it is rather idiot-proof. Thanks!
uconnjack said:
Being the noob I am, I can't post this question in the dev forum. Does anyone know if Liberty is compatible with safestrap or not? I know the official instructions says CWM only, but I have read that many install using safetstrap without any problems.
That said, I for the life of me can't get it to boot after install. Are there any special tricks to get it to work with safestrap? Being a noob to Android (this D3 is my first foray into Android), I would like to stick with safestrap until I am very comfortable since it is rather idiot-proof. Thanks!
Click to expand...
Click to collapse
The thread at RootzWiki in the dev section for Droid3 is very helpful.
Some of the things to double check:
- Make sure you're swapping to "safe mode" before flashing the .zip
- Wipe data/cache
It works fine with safestrap
Sent from my DROID3 using xda premium
I have been switching to safe mode, clearing data/cache, rebooting, installing the ROM zip (with no apparent errors), clearing data/cache again, and then trying to boot the ROM, but it just hangs on a blank screen for >20 minutes before I pull the battery. Tried this a few times, even redownloading the zip, but its always the same.
Steel Droid and Maverick have worked fine, but just can't seem to get Liberty to work. I have reviewed and seacrhed the forums, inluding rootwiki, hoping there was some special trick that needed to be done with this specific ROM, but have found nothing.
Maybe I will try installing an older Liberty ROM to see if that works' and also maybe reinstalling safestrap, maybe even rerooting.
Any ideas?
Sent from my DROID3 using Tapatalk
uconnjack said:
I have been switching to safe mode, clearing data/cache, rebooting, installing the ROM zip (with no apparent errors), clearing data/cache again, and then trying to boot the ROM, but it just hangs on a blank screen for >20 minutes before I pull the battery. Tried this a few times, even redownloading the zip, but its always the same.
Steel Droid and Maverick have worked fine, but just can't seem to get Liberty to work. I have reviewed and seacrhed the forums, inluding rootwiki, hoping there was some special trick that needed to be done with this specific ROM, but have found nothing.
Maybe I will try installing an older Liberty ROM to see if that works' and also maybe reinstalling safestrap, maybe even rerooting.
Any ideas?
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
Check the MD5, mine kept doing that until I downloaded over 3g. Downloading over 3g finally gave me an MD5 match
Sent from my DROID3 using xda premium
I flashed Liberty 2.0 with Safestrap, two days ago. First reboot after flashing led to the phone hanging on the spinning eagle boot-up animation. I booted into recovery, wiped data, formatted, and re-flashed, and it worked fine during that boot-up. However, boot-up times are strange, and there's usually a blank black screen when booting up for about 10-15 seconds for me prior to the boot animation showing up.
On a side note, my battery life with Liberty 2.0 is horrendous. Phone Idle = 36%, Cell Standy = 39%, Android OS = 3%, Wifi = 2%. I don't get it. Haven't really downloaded any apps at all yet.
Lyxdeslic said:
I flashed Liberty 2.0 with Safestrap, two days ago. First reboot after flashing led to the phone hanging on the spinning eagle boot-up animation. I booted into recovery, wiped data, formatted, and re-flashed, and it worked fine during that boot-up. However, boot-up times are strange, and there's usually a blank black screen when booting up for about 10-15 seconds for me prior to the boot animation showing up.
On a side note, my battery life with Liberty 2.0 is horrendous. Phone Idle = 36%, Cell Standy = 39%, Android OS = 3%, Wifi = 2%. I don't get it. Haven't really downloaded any apps at all yet.
Click to expand...
Click to collapse
It has a different way of reporting battery usage, it doesn't affect it though (based on 5.6.890) I've had my phone on for 9 hours now, medium usage, and I'm at 86%.
Lyxdeslic said:
I flashed Liberty 2.0 with Safestrap, two days ago. First reboot after flashing led to the phone hanging on the spinning eagle boot-up animation. I booted into recovery, wiped data, formatted, and re-flashed, and it worked fine during that boot-up. However, boot-up times are strange, and there's usually a blank black screen when booting up for about 10-15 seconds for me prior to the boot animation showing up.
On a side note, my battery life with Liberty 2.0 is horrendous. Phone Idle = 36%, Cell Standy = 39%, Android OS = 3%, Wifi = 2%. I don't get it. Haven't really downloaded any apps at all yet.
Click to expand...
Click to collapse
If flashing from the last version of Liberty there shouldn't be a need to wipe, I didn't anyway. It took quite a while, more than 5min, to finally boot just after flashing. As far as the 10-15 second delay, that is how safestrap works. 10 seconds at the safestrap splash screen and about 10 seconds of black before the bootanimation. Though I'm not sure of why the later takes so long. For me the previous version of Liberty took just as long to boot.
Yup, that was it, the MD5s would not match up until I downloaded over 3g. Wireless or PC->phone would always have mismatched numbers. I didn't check the Steel Droid or Maverick ROMS I downloaded wirelessly, but those installed fine regardless. Wonder why the consistent download errors for the Liberty ROM?
Thanks for your help!
uconnjack said:
Yup, that was it, the MD5s would not match up until I downloaded over 3g. Wireless or PC->phone would always have mismatched numbers. I didn't check the Steel Droid or Maverick ROMS I downloaded wirelessly, but those installed fine regardless. Wonder why the consistent download errors for the Liberty ROM?
Thanks for your help!
Click to expand...
Click to collapse
I don't know why either I figured it was my router having a moment, but you're the second other person I've helped with that.
eww245 said:
If flashing from the last version of Liberty there shouldn't be a need to wipe, I didn't anyway. It took quite a while, more than 5min, to finally boot just after flashing. As far as the 10-15 second delay, that is how safestrap works. 10 seconds at the safestrap splash screen and about 10 seconds of black before the bootanimation. Though I'm not sure of why the later takes so long. For me the previous version of Liberty took just as long to boot.
Click to expand...
Click to collapse
If you want to use the new lockscreens or themes you'll need to preform a data wipe, Kejar said so himself.
Androidsims said:
I don't know why either I figured it was my router having a moment, but you're the second other person I've helped with that.
If you want to use the new lockscreens or themes you'll need to preform a data wipe, Kejar said so himself.
Click to expand...
Click to collapse
Using ring lockscreen, haven't tried any of the themes though. I'm suprised it did work actually.
I'm running it with safe strap right now not the best battery life but it'll do til hash gets ics running (which I know he will cm7 is my favorite but need tethering and camera)
Sent from my DROID3 using Tapatalk
My md5 sum is correct and I've cleared the data/cache but I only get a black backlit screen for 20 min + til I remove the battery. Anyone got a tip of what to do?
Sent from my DROID3 using XDA App
kAmaOn said:
My md5 sum is correct and I've cleared the data/cache but I only get a black backlit screen for 20 min + til I remove the battery. Anyone got a tip of what to do?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
SBF back to stock 5.6.890, reroot, reinstall safestrap, re-do EVERYTHING pretty much. Thats my solution to everything.
No matter what I try I cannot get past this screen.
//merickk.smugmug.com/Other/Misc/Miscellaneous-Stuff-1/i-P8ZBVg4/0/L/0626120050-L.jpg
I've even tried to moto-flash the mbm and cdt files from a downloaded leak file and no luck there either.
Formatting the internal memory after FXZing back to 902 and installing the leak on a fresh formatted SD card with only the leak file on it after OTAing to 905 doesn't work either. I've tried 6 or 7 2233 files, and a couple 2231 files as well as a couple different 902 FXZ files.
ICS is there somewhere otherwise I don't think it'd get that far into the boot process and charge the battery.
When I do a battery pull and try to reboot, it just sits at the Droid screen.
Pulling the battery while plugged in takes me to the Dual Core screen where it sits.
When sitting at the starting applications screen I am able to get tactile feedback when pressing and holding the home key but after sitting for an hour or so there is no feedback from the home key. No response from any of the other keys. The keys are also lit up.
This has happened every time with every leak file I've flashed the exact same way.
Does anyone have any suggestions?
Quite a conundrum... Maybe you should wait for the OTA to come out, let it brick your phone, then take it to Verizon and demand to trade it in for a phone with good battery life and no data drops? lol. If I were in your shoes and it looked like the ICS update was gonna make my phone eligible for a warranty replacement, I'd use that as an opportunity to let Verizon spring for a new device. Just sayin'.
My guess is you either currently have or have had CWM recovery installed. If so.... uninstall safestrap/bootstrap, then use root explorer go to/system/bin and delete 2 files... "hijack" and "logwrapper", then change the name of "logwrapper.bin" to just "logwrapper" once you have done that, reboot into stock recovery and try again!
Thats the only thing i can think of, i know the above will solve the problem of getting the error when attempting to flash. Sounds like yours flashed but just wont finish booting.
Sent from my DROID BIONIC using xda app-developers app
XperianceIT said:
My guess is you either currently have or have had CWM recovery installed. If so.... uninstall safestrap/bootstrap, then use root explorer go to/system/bin and delete 2 files... "hijack" and "logwrapper", then change the name of "logwrapper.bin" to just "logwrapper" once you have done that, reboot into stock recovery and try again!
Thats the only thing i can think of, i know the above will solve the problem of getting the error when attempting to flash. Sounds like yours flashed but just wont finish booting.
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
i have the same problem , did this work for the OP?
Hey guy's Im hoping you can help me.
Last night while browsing my phone froze, so i performed a battery pull and on putting it back in the phone refuses to boot.
If i plug thr charger in alone, the LED's blink orange/green
If i place a battery in the charging light turns on. I have two batteries so I tried them both. Still nothing.
I was able to boot into recovery and tried to clear the clash and do a full reset. upon reboot the phone stuck on the boot screen.
I tried a battery pull once again, and since that I have only been able to get the phone to boot once after numerous tries only to get 7 vibrations.
The power button still works, if i try turning it on while on charge the orange light goes out, but nothing.
Ive tried the battery trick while on the charger alone the green light goes on but again nothing, I've tried different chargers, I'm now at a loss.
While typing this IVe been able to get it to boot once again, but again i get 7 vibrations and nothing.
Any help would be appreciated, I have no phone, while my GNEX is being repaired under warranty
A noob question... you said that you do a full reset... Did you flash the rom again? (give more details.. rooted phone...hboot.. rom...)
Obsy said:
A noob question... you said that you do a full reset... Did you flash the rom again? (give more details.. rooted phone...hboot.. rom...)
Click to expand...
Click to collapse
full reset as in going into recovery and wiping everything, unfortunately, I have note been able to get back in since to try and reflash a new rom.
I'm currently running a stock hboot, with the last stable release of MIUI before MIUI4 cant remember the exact version number. The phone is rooted and locked.
Thanks for the swift response
poseoff said:
full reset as in going into recovery and wiping everything, unfortunately, I have note been able to get back in since to try and reflash a new rom.
I'm currently running a stock hboot, with the last stable release of MIUI before MIUI4 cant remember the exact version number. The phone is rooted and locked.
Thanks for the swift response
Click to expand...
Click to collapse
Why don't you copy the miui zip onto your SD card, and flash it back from recovery? If you are running GB MIUI, the last version for that would be 2.3.30.
Sent from my Nexus One using xda app-developers app
sphinxcs898 said:
Why don't you copy the miui zip onto your SD card, and flash it back from recovery? If you are running GB MIUI, the last version for that would be 2.3.30.
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
Agreed, I've preped my SDcard with a Passimg.zip. however I'm at a point where I cant get the phone to turn on constantly. since posting this morning. I've had no success - c'est la vie. I'm reluctantly thinking of moving on, however I really loved my N1 believe it or not it was much more reliable than my GNEX which is in under warranty repair for the 3rd time already!
Running a completely stock VZW Moto X on the latest update (4.4.2). Woke up this morning to a half dozen or so app updates, including Active Display and Moto Help. I updated these two, and then an update for Beautiful Widgets started after. My phone then locked up and restarted. Now, it loads through the boot screen and then loads the Verizon screen, then the device goes black. I've tried wiping cache, to no avail. Any suggestions? I've installed the Moto X drivers via the Moto site, but the device isn't being recognized via ADB. I would really really really like to retrieve my files from the phone before doing a full factory reset...
Haven't seen anyone else report this....
Sent from my XT1060 using Tapatalk
Same symptoms on unlocked dev edition
I can't for sure tie it to an update, but the only thing that I did on my Moto X today was enable Motorola Connect. In the ensuing ~3 hours my phone bit it and would get to the Motorola Unlocked Bootloader screen and stop. Tried to boot to custom recovery, but it wouldn't work. Tried reloading TWRP, but gave access error on write but it seems to have fixed it enough to let TWRP open. TWRP showed list of access errors, like the memory had been corrupted. Need to find 4.4.2 image and load it back on via FB, as recovery has no data now.
stastnysnipes26 said:
Haven't seen anyone else report this....
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
omaharper said:
I can't for sure tie it to an update, but the only thing that I did on my Moto X today was enable Motorola Connect. In the ensuing ~3 hours my phone bit it and would get to the Motorola Unlocked Bootloader screen and stop. Tried to boot to custom recovery, but it wouldn't work. Tried reloading TWRP, but gave access error on write but it seems to have fixed it enough to let TWRP open. TWRP showed list of access errors, like the memory had been corrupted. Need to find 4.4.2 image and load it back on via FB, as recovery has no data now.
Click to expand...
Click to collapse
You have a totally separate problem from the OP. I don't have an unlocked boot loader and haven't done a ton of research on the risks of unlocking the consumer edition. 4.4.2 images are posted all around the forums. I would start there.
Sent from my XT1060 using Tapatalk
Thanks. You are right, not the same problem, when my phone soft bricks when I haven't been doing anything to it I get twitchy. I have the DE and have tried (a bunch of times) using RSD Lite and fastboot to push files back to phone, but after reboot everything looks to be reverted back like if WP was enabled, which it isn't. I will take a cruise thru the forums looking for similar issues, but any suggestions would be appreciated
stastnysnipes26 said:
You have a totally separate problem from the OP. I don't have an unlocked boot loader and haven't done a ton of research on the risks of unlocking the consumer edition. 4.4.2 images are posted all around the forums. I would start there.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
omaharper said:
Thanks. You are right, not the same problem, when my phone soft bricks when I haven't been doing anything to it I get twitchy. I have the DE and have tried (a bunch of times) using RSD Lite and fastboot to push files back to phone, but after reboot everything looks to be reverted back like if WP was enabled, which it isn't. I will take a cruise thru the forums looking for similar issues, but any suggestions would be appreciated
Click to expand...
Click to collapse
If you have a Dev edition fast boot stock vzw files, fast boot OEM unlock and reflash SU. simple as that.
Sent from my XT1060 using Tapatalk
Yup. Have gone thru that procedure several times, but phone won't get past the bootloader unlocked screen, and even after flashing stock (with stock recovery partition) TWRP still shows up, so some write to memory isn't sticking. It's very strange, used same procedure on this phone when upgrading to 4.4.2 from 4.2.2 and on other phones with no problem. Since TWRP can't access the flash, I am wondering if I actually have a corrupted memory module. If I can't get things working, I will start a thread. Don't want to hijack this one. Thanks.
stastnysnipes26 said:
If you have a Dev edition fast boot stock vzw files, fast boot OEM unlock and reflash SU. simple as that.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
As an update to the original post...
My phone "magically" booted at some point while it was sitting on my table. It's been working since then, but I tried to restart today and the thing won't boot up again. No idea what causes this and adb still isn't working with the phone in recovery mode.
Well I'm from the old school of if a car won't start you check 3 things spark fuel air. So in the case of our phones I always say fxz if an fxz fails to fix the problem than I lean towards a hardware failure. I have never had an fxz not fix a software issue. And I have bricked more than my fair share of devices several times.
I just did my custom order of the Moto X today. I hope I won't run into any issues. I'm switching from the iPhone 5S.
Sent from my XT1058 using Tapatalk
..
Y
thesandman00 said:
As an update to the original post...
My phone "magically" booted at some point while it was sitting on my table. It's been working since then, but I tried to restart today and the thing won't boot up again. No idea what causes this and adb still isn't working with the phone in recovery mode.
Click to expand...
Click to collapse
Have you tried fastboot?
Also getting the drivers to work can be tricky. You have to install them and then use device manager while you're phone is plugged in to get it working.
Sent from my XT1060 using Tapatalk