I just rooted my droid to froyo (sapphire) and everything seemed to be going smooth until i rebooted the phone from recovery. The motorola M screen came up and then the sapphire came up. After about ten seconds it goes away and reappears and has been doing this for the past 35 minutes. Is this normal? Any clue on what i need to do to fix this?
alright well i was running flyx and decided i wanted to restore to a backup i made on 2.1 pre installing a rom. after the backup began it ran through and ended up at the motorola boot screen. stuck! this is the only recovery i have. now when i boot into recovery i get this message: e:can't open /cache/recovery/command
So I'm relatively new to rooting. I'm running BB .4, and that went okay. I'm trying to install a theme using ROM Manager. I backup and wipe and it loads into recovery and all that. That runs okay. Then, when it's rebooting, it gets stuck on the DROID screen. Well,actually, it does it once, goes to the Droid eye, and then just repeats the DROID screen over and over. A battery pull allows me to get back into recovery, which lets me restore my back up and then it boots just fine, but I'd really like to make my phone purple. Any ideas?
I rooted my phone and have been using the 3G hotspot and some overclocking apps. Today I decided to load a custom rom. I did some research and bought Rom Manager and Bootstrap. I did the bootstrap and than rebooted to recovery. Than I installed rubix from the sd Card. I found someone else with the problem here and people told them to pull the battery and get into recovery. When I do that I get a droid with an exclamation mark screen. I cant seem to get into recovery or do anything and I am stuck at the rubix boot screen. It seems my problem is because I did not wipe my date or clear cache when installing... but I can't get into recovery to re-do it!
For the past 2 hours I have been searching this site and reading about Rooting and Flashing new ROM's etc. and I'm still having trouble. I downloaded Cyanogen 6.0.0 and when the phone re booted it got stuck at the Cyanogen boot animation screen, and when I pulled the Battery and rebooted in to recovery I was able to restore everything and now the phone works again.
So first off, how long should it take after downloading a new ROM to boot back up with the new ROM installed? And how can I save the ROM in to the SD card? And when I go to DL Cyanogen it asks which home application I should use and gives me ADWlauncher and Launcher 2 as options.
I'm kind of new to Rooting and Roms but I keep getting the same problem while installing Roms using Rom Manager. I flash and then I install the ROM and everything goes well until the boot up screen. It gets stuck in a loop of the Droid and Droid Eye animation and I have to restore it. Can anyone help me figure out what's wrong? I am using the Droid with Froyo, rooted using Easy Root.
Both of the stickers - the one on my phone, and the one on the battery still have red X's. I have read that this is good. I dropped my phone in a toilet (recently flushed thank god) in the Staten Island Ferry Terminal (see, nothing good comes of traveling to SI!) and grabbed it out as soon as I saw it. I had a plastic case on the back of it. Took it apart as soon as I got my wits about me. And no, I wasn't using it - It flew out of my backpack when I turned around.
It will turn on but has this odd boot up screen. I don't believe rice will get the water out of the inside, and I don't have a screw driver tiny enough. If I bring it to the Verizon store will they know it had water damage from the screen alone? It looks normal almost like the DOS blue screen of death sort. Also, the little tiny green sticker in the lower right hand corner that says VOID - is that a water damage indicator too? I don't recall ever caring what it was.
I have a customer with a Droid Eris stuck at the boot screen (3 dancing green droid guys) and it wont go past that. I can boot it into Hboot, I've done a factory reset, didn't work. The customer said they deleted all their contacts from the phone, charged it then the next day it was stuck like this.
feel stupid asking easy questions, but here i go.... tried installing a new kernel and tried one im guessing not compatiable. well, now it won't boot it stops at the motorola symbol and im wondering how i could either install a new kernel or recover a past saved rom.
trying a new Chevy kernel I went into boot loop. No biggie, I just booted into recovery and went back to my goto kernel. BUT, now that causes boot loops and in fact, any kernel I load - I have tried 4 - causes a boot loop. even my stable goto.
My Droid keeps rebooting on it's own. It stuck in a boot loop. I have tried to do a wipe and restore a android backup that I made last week but it is still rebooting. As soon as the phone tries to mount the SD card reboots. I have also tried to restore it to a plain vanilla backup that I made right after I rooted my phone.
Clockwork see the SD card with no problems and can read and write to it. Also Win 7 can see the card when I put it in my laptop. This seems to have started after I used MotoTorch Flashlight and had to do a battery pull on it because the phone locked up.
Just like I did to root, I followed this forum and DroidReview YouTube videos to install ROMs. I installed ROM Manager and downloaded a few (free) ROMs. I made a back up of the stock ROM or whatever you want to call it. For both ROMs, after it downloads, installs, and boots, it gets stuck at the Droid and Droid Eye phases. It goes from saying 'Droid', to the eye, to a black screen, and then starts it over and over again. Thankfully, I was able to figure out how to restore the previous backup I made using the recovery/nandroid menus. what's going on with my Droid (or me)? After two tries, I'm guessing it's not the specific ROMs and something else is going on. All help is appreciated! I really want to get this sorted out! Thank you!!!!!
I've been running Kangerade since shortly after it came out... And loving it.. Yet today I saw my phone was rebooting - and waited (figured it over heated or some such..) and waited... And waited... That android boot image does stop being cute after a while... Crap.. Just cycling... Go into recovery... Umm.. No seriously.. Go into recovery.... Go on.... Nope. (apparently latest ROM MAnager screwed up CWmod..) So... Can't load my phone... Can't restore backup..
, i followed the directions for updating the droid to 2.1. Now stuck in a boot loop. The firmware updated fine and didn't indicate a failure, after i updated i did the reboot from the menu. I've reflashed 2-3 times now and it does not come back, and i've pulled the battery more than a few times.
I was attempting to flash a ROM for the first time. my droid is rooted, I thought I was doing everything right, obviously not. I was using clockwork to flash it. I have titanium backup, and I had it clockwork backed up. It said the flash worked, I tried booting, and got stuck on the "droid" animation, it loops over and over. I booted into recovery mode, cleared data and cache. Now I can occasionally get it through the normal boot animation, all the way past the droid eye, but then it goes back to the "droid animation", only its very glitch, and loops erratically. What should I attempt to do?
I was playing with the new version of Sapphire (0.6.2) and with the themes available now...I thought I'd share some of the wallpapers I created to go with the ROM.This theming also helps me identify what ROM I'm running cause I flash so many.I just noticed a lack of themes and options for the Sapphire ROM so trying to spread some love their way.
So as the title states my Droid has some major water damage, but after about 30 min of low heat in my oven and a few more hours of drying it now powers on. Problem it is stuck on the bootloader. So my question is do you guys think I screwed up whatever part of the phone that stores the ROM, does it need more dry time (this only happened about 4 hours ago), or should I just try reinstalling my ROMS off my SD card without waiting any longer? I'm planning on giving it another cycle of heat/dry time then reflashing everything but don't really want to go through all the hassle.
I went to reboot my Droid because it was lagging a little and when it came back on it go stuck at the Cyanogen boot screen. I pulled the battery, put it back in and held the X to boot in recovery and my recovery won't come up either. It just skips right to the Motorola M and if it doesn't get stuck there it goes back to the Cyanogen screen.
I haven't made any changes to the phone at all so I am completely puzzled on why this is happening. I obviously can't take it back to Verizon since its rooted so if there is a way to fix this I really want to because I love my phone and my wife will kill me if it is screwed up.
I just flashed Myns Two point Two. I used to Amon RA to wipe the things I needed to wipe and then installed the rom. Little to say that when I booted, it got stuck on the boot screen.I've done a hard reset, booted to the loader, and wipe the data but to no avail.
I was on 2.2 rooted on my droid x. Attempted to install a replacement for the taskbar. The phone is stuck in a boot loop now. I've read about 5,000 different pages saying just use RSD. It all starts by saying; plug the phone in, let the computer detect it, install the drivers.. This is where I'm stuck. The only thing I have access to is the recovery console and the big endless loop. So at no point the phone turns on to the point where the PC will detect it as a device.
Been creating a theme last few days. I installed it on my phone, but before doing so i was a good boy and did a nandroid backup. Then i didnt like osme of the things i changed so i restored my backup i just did now its stuck after restoring on the white htc evo screen. NOT GOOD!! I even pulled the battery and SD Card...twice.
I'm running Sapphire 1.1.1 and like it so far. Coming from Cyanogen, I'm mostly interested in the music volume rocker controls for skipping through songs when the screen is off. I know the problem with Sapphire has typically been that the volume rocker controls sometimes continually skip through songs when the button is pressed, but mine seems to only start the current song over. Anyone else have this problem? The lock screen controls work fine, but I'd like to get the volume rocker working correctly so I can keep my eyes on the road when driving.
so I've been into rooting for a few months now. I started on the Droid and moved onto the Droid X. I got my X to 2.1 rooted, then 2.2 rooted, then the 2.2 rooted deodexed post on the forums here. I wanted to move onto FlyX, but wanted to run it clean and not over the deodexed version I had installed. Unfortunately I hadn't made a nandroid backup of the base 2.2 version. So I decided to start COMPLETELY over by flashing the SBF like I did orginally to upgrade to 2.2 (because I had a theme). Now, everytime I flash, it just stays in a bootloop that starts after the moto logo. It will show Droid, explode to the eye, and start over.I've reflashed about 3 times, and taken out the battery several times for each flash. So...any ideas or am I pretty much boned?
First time post here, hoping for some advice. This is the situation: as of late, my Droid would occasionally reboot itself. Didn't think much of it (new phone, new system. Wasn't expecting perfection). However, tonight (while updating an app from the market) the phone froze, rebooted and got stuck in 'The Red Eye of Death' loop. I tried pulling out the battery and sd card several times. No luck. After googling and reading various postings (this forum and others), I started to notice that a lot of the issues revolved around 'rooting'. I have a sense of what rooting is however I have no real interest in it (warranty, wait for update, etc.). But apparently, I have a rooting problem. I'm able to get to the recovery mode (power up while pressing 'X', etc.). The choices I get are: 1.reboot system now 2.apply sdcard:update.zip 3. wipe data/factory reset 4. wipe cache partition. But under all that is 'E:cant open /cache/recovery/command droid'. When I run 'sdcard update' option, I get 'No such file or directory. Verification failed. Installation aborted.' My first question is: what is it trying to update to? I was already at 2.0.1. Has the phone somehow reverted back to 2.0 and is trying to get back to 2.0.1? And if so, why is the update file missing? I think I have four options. The first is to return the phone and wrestle for a new one (and not a refurbished one). Although, this may be the easiest route, there's a lot of work I've put into my phone already; files, settings and apps that I don't want to lose. Plus I just don't want to deal with a Verizon rep if I don't have to.
Second option is to try 'wipe data/factory reset'. Again, don't want to start from scratch. However, I find this option more desirable than the first because I get to keep my 'new' phone, which I've already grown attached to. My only concern with this though, is that I read a post where someone tried this option but his phone then became deactivated and he couldn't re-activate using his original numbers. So that's a potential risk. Third choice putting the sd card into my laptop, download and install the 10mb 'update.zip' file, and recover from there Four: the Droid 2.0.1 sbf file / RSDLite solution posted elsewhere on this forum. So my ending questions are: In regards to options 3, if I took this route would I be in essence rooting the phone, or is rooting more than just manually updating your phone? And did the 'Droid sbf file' come about because the 'update.zip' file doesn't always work? Just need some advice to help me make my decision. Just want my good ole Droid back.