Motorola :: Droid 1 No Signal And Will Only Boot To Bootloader
Oct 5, 2010
I have a Moto Droid 1 rooted from spf recovery via .zip. I then used Rom Manager to install Clockworkmod Recovery and flash Cyanogenmod 6.0 (Froyo). It worked absolutely fine for about a month. Then last night, I found my phone upstairs on AC, and it was on the bootloader menu. I restarted it and found it would only boot into the bootloader. I booted into recovery and tried to reboot from there. This worked but when my phone booted into Cyanogenmod, it had no signal at all. After resetting it a few times, I tried doing a factory reset. The problem persisted. I tried wiping the cache partition. Still won't connect. I rerooted. Still won't connect. I did what I thought was flashing my ROM again, but it didn't seem to work (I'm not sure how I could tell). When I try to restore Nanroid, it says "no files found"
My droid x signal pretty much always between -92dBm and -87dBm with 1-3 3g bars. My former droid eris would get -92dBm with 1 bar and also drain incredibly fast.
On the droid x, if I go into google maps, the circle of the cell tower appears and the place I live at is half way within the edge of the circle and the other half is outside of the circle. I always seem to be connected to this tower. Bad luck I guess that I'm on the outskirts of the circle.
Does anyone know how cell towers are distributed? Do they overlap sometimes?
I run pandora with the screen off for a half hour with the screen off and my battery is down to 70%. I have about 15% screen brightness and battery saving mode on.
yesterday, I was on meebo for an hour and 45 minutes and it was down to 60% from a full charge.
I unlocked my bootloader a month before and I didn't know how to relock it back so I searched and found this website >>androidgadgematic I followed everything it mentioned and after finished installation, I hold on the boot button, the green light indicator blinked once and vibrated once but after that gave no respond. I didn't unroot my phone before doing the relock procedure. Now, I really don't know what to do because I searched google but none. I indeed need a step by step procedure to save my phone. How to boot my phone now, or else it is dead. I don't have if any method to reinstall ALL system files, no matter kernel, firmwares via my pc as long as it can helo my phone to boot up.
I tried installing Tranquility and must have screwed something up because now my phone won't boot past the Motorola Logo. It's been sitting here like this for about 15min and I can't even boot into recovery by holding the power and home buttons. I don't know what else to do now. Idk if my phone is bricked but even if it is don't I need the SBF file to unbrick it and I can't find that file any where. I did a nand backup or whatever before doing any of this so hopefully that can help me. What should I do now?
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.
trying to grt my driod into bootloader so i can down grade and root but cant even get phone into bootloader mode tried powering up while holding d-pad up didnt work, tried powering up holding camera and volume down didnt work dont know what else to try..
I am trying to root my Droid but everytime I hold power and up on dpad it just gets stuck on a black screen. I can tell it is trying to go to the bootloader but it just doesn't go. Do I need to hold the power button while holding the dpad up? I need to know because I dropped my phone in some water a few weeks ago and it screwed my power/sleep button up a little bit.Sorry this question may be such a cluster but I'm just trying to get some tips or information on what to do.
Trying to root my moto droid, following all instructions in the "The All-new Guide to All Things Root-related" thread. However it seems I've found myself a problem that isn't described anywhere i can find. Upon opening RSD and rebooting into the bootloader my computer (Windows XP pro 32 bit) says that its found new hardware: "SE Flash OMAP3430 MI". I've already installed the provided 32 bit drivers for my droid, but it seems the bootloader itself requires its own set of drivers. Tried showing the found new hardware wizard where the droid drivers where located, would not accept them. Also tried the search the internet option, again no luck. Something's clearly amiss...
So I hear there is a new SBF that works with the new bootloader?I have 2.3.15, but I never did the OTA update. What is the easiest way for me to get up to date with the new radio? Currently I have 30.01 bootloader.I read that I can use the FULL 2.2 SBF file to update the bootloader and the more importantly, the Radio. I am wondering however if I need to remove remove Bootstrap or Unroot first? I would imagine I do not, but you can never be too careful, there seems to be alot of misinformation, and I'm digging up posts where some people say the Full 2.2 SBF will not update the bootloader.
I have ran into a issue while trying to root my Droid. I was following the sticky and the first time I used RSD and loaded SPRecovery 2.1 SBF it failed. I got a Critical Error DEA1. I then booted the phone and ran the file again and it completed this time.I have powered down and held X each time and never get past this screen. I then went into the section on putting the stock OS back and I get the same issue. Is there anything I can do? I have been searching the forms, but I cannot find anything.
I just recently updated my phone to 2.2 using the new 2.2 SBF. My phone is running great now after fresh install. I thought the SBF would flash a new bootloader version like the OTA. I think the OTA is 30.03 that changed signatures preventing downgrading. Anyway after I flashed the new SBF I looked at the bootloader version and it was still 30.01. Dose anyone have any info on this?
When all of the leaks were kicking around, I installed the leaked 2.2. I used the 2.1 SBF to restore the phone a couple times during my playing around with various ROMs.When the full 2.2 SBF rolled around, I used that to upgrade to 2.2 rather than accepting the OTA, partly because it was easier to do that than it was to roll back the leaked 2.2, then accept the OTA. However, it looks like, during this process, my bootloader never changed. I'm still at 30.01. Intuitively, I guess this makes sense - you can't update the bootloader from within the bootloader. However, there have been a lot of questions surrounding the new 2.2.1, bricked phones, and bootloader versions. I know the theory is that it's just from wiping data but nonetheless, I'm wondering what my options are or if I need to worry about it at all? Can I SBF back to 2.1 and accept the OTA to get a recent bootloader, since I still have the 30.01 bootloader version? I guess there's little harm in trying since I could always SBF back to 2.2, but I'm just wondering if I'm asking for trouble.
with sprecovery on my phone. I'm trying to force 2.2 but cannot do it through sprecovery for some reason. RSDlite instructions say I must get to a bootloader screen. I cannot because when I hold power and x it goes into the sprecovery/nandroid back up with the Android guy with a ! on him.
I was following the instructions on "How to: Return DROID X Back to Android 2.1 to go from 2.2 leak, to stock 2.1 so I can get the OTA 2.2 update. I've never rooted and after RSD did several things, it gave an error something like "Error sending RAM download for bootloader..." (there was more to it than that, but I don't have it on my screen anymore). After trying several things, my phone now comes on to the bootloader, but says "Code Corrupt" then "Battery Low" and "Cannot Program" flash on individual lines below. I plugged it into an outlet for nearly two hours and I'm still getting the same thing.Anyone seen this if so how do I get beyond it? One thing I read said that he just checked "ODM_Serial" under Config>Flash/Flex options and started over and it worked. That would be great, but the computer won't recognize it as connected as long as it's doing what I described above.
Incase anyone wants to know how to get into Bootloader you turn the phone off then hold Power+Volume Down+Camera and it will go into Bootloader 2C.5C. It says Battery OK, OK to Program Connect USB Data Cable. When I plugged it in I got a driver failure instantly (win 7) so maybe someone else will have better luck.
So I have a rooted Droid X running official 2.1. I want 2.2 but I want to keep my original bootloader. Is there an update.zip that can take me to the OTA or the leaked OTA without messing with my booloader or recovery? I would also not like to wipe my data ether.
I was looking at the OTA ZIP file from VZW and noticed some BIN and IMG files. I'm guessing that it bootloader and baseband images. Is there a way that I can swap out those files with a nicer bootloader? Basicly what I want is stock OTA 2.2 with 29.01 or 30.01 bootloader but I want the new baseband with the update. Can I do this or does it just fail because of signatures, checksums, or some other crap I can't think of?
Hopefully just a mini emergency. Last I knew I was still running the original .9 leaked 2.2 froyo update. Tried installing bootstrap to upgrade to TBH's leaked .15 update and now my phone is stuck in the boot cycle the first time I tried booting in bootstrap recovery. I pulled the battery and tried booting into recovery, wiped cache and data, still can't get my phone to boot. Searched to see how to remove the bootstrap through adb to no avail. Figured it would just be easier to sbf, but remembered that was bricking a lot of people. Checked my bootloader and I'm on 30.01, but can't remember which version bootloader works with sbf. I found that 2.2 official OTA upgrades the bootloader to 30.03, but I'm still really afraid to sbf without confirming I'll be ok.
So is anyone still waiting on progress to be made on the bootloader before going OTA? With root of course
I am having rare stability issues with Flyx / Tranquility on 2.3.9. I never went past this update/combination.
Im thinking if going to 2.2 OTA and rooting seeing as though it seems like no work is being done on cracking the stock bootloader. I know it is, but we haven't gotten any info from anyone lately. What are you guys doing?
I just got a CLN warranty replacement with the new bootloader (30.04) and was wondering if I can more or less return the phone to stock after un-rooting since there is no sbf for this bootloader yet or it hasnt been tested with the 2.2 sbf (BL 30.03).
What I was thinking would happen:
1. Root 2. Install Bootstrap 3. Create bare backup 4. Install ROMS, themes, etc. 5. Return to stock: 6. Restore bare backup 7. Unroot 8. Factory wipe
Would this work or would the bootstrap remain dormant cause its still in /system? Meaning the recovery could possibly come up while rebooting or something else?
I have a X that has 2.1 -update 1 on it that I got from a friend. I want to have 2.2 on it but when I try to update the phone OTA, it says that I am up to date. So I am guessing that are some things he played with that is making this not work.What I am hoping I can acomplish is get stock 2.2 on my X even if it involves RSD lite or other methods.RSD was the way I was going to go, untill I ran into the problem that the camera button does not work, so i can not get into the bootloader.Also, adb reboot bootloader isn't working, and rooting and trying to get Clockwork Recovery to work isn't doing what I need.So I am out of ideas on how to get 2.2 or any other ROM for that matter on my X.
I've updated this OP to make it easier for new comers to find some of the most important posts as well as a few important outside links that inform this thread. It is my personal feeling that if you are reading these forums, and considering buying ANY Android phone, this thread is a very important one to read. It is far better to be informed than to realize after you buy a product that it wasn't what you expected (I almost made this mistake). The main purpose of this thread is to discuss what a signed (encrypted) boot loader is, what the implications of having a signed boot loader are, whether or not the Droid X may have one, why you may care, what you may be able to do about it if you do care, etc, etc. This thread is filled with a lot of long posts (including this one), so prepare yourself for that. Not all of them have tons of merit (mine included) so keep that in mind. Below are some of the most informative posts you'll find in this thread. That said, I highly suggest further reading: there are many great ones that I haven't linked to here.