How do I install a custom rom on my Droid 1? - Motorola Droid and Milestone General

I have a rooted droid 1 and I want to install cyanogenmod 7.0.3. I got rom manager the free edition and I flashed clockworkrecovery. When I tried to install the rom from sd card, it just rebooted and went to a triangle with an ! and that's all. I waited, but nothing happened, so I did a battery pull and rebooted my droid. I flashed clockwork again, because a friend told me it probably didn't flash properly. I got the success notice again. Then I tried again, but this time my phone just rebooted. What am I doing wrong

That's really weird... I just put that ROM on my D1 and it installed perfectly, even though it took 3 tries. I followed a guide on how to install it using ROM Manager (since it was my first time). Since I am a noob here at XDA, it won't let me post a link to the website, but I'll copy and paste the tips for you.
Problem During Flashing?
If after the "Reboot and Install" step, you immediately get a picture of Android with a big exclamation point, most likely it means the ROM image you downloaded was not cryptographically signed by the developer (which happens if they were in a hurry to release or simply don’t use encryption).
That’s OK – you can fix this by:
clicking the exclamation point screen, which goes to the ClockworkMod recovery menu or simply rebooting into recovery manually (that’s one of the options in the ROM Manager). Alternatively, you can boot into recovery by holding Power and Home buttons together while powering up your phone
selecting the option that says "install zip from sdcard"
toggling the "toggle signature verification" option to turn the verification off (it should say "Signature Check: Disabled")
giving flashing another try by selecting "choose zip from sdcard" and selecting the right ROM, just like before.
This is on the Android Police forums posted by Artem Russakovskii. I don't take credit for this.
Goodluck!!!
Adam

Thanks.
Anyways, I had to flash the latest version of clockwork. Then it worked

Sweet! Well I welcome you to the wonderful world of custom ROMs then.
Sent from my Droid using XDA App

Related

[Q] Cyanogen without using SDK?

Is there a way to flash one of the Cynaogen or other mods without installing the android SDK? I am not extremely technically inclined when it comes to this stuff and I am not sure I understand how to do it.
Any help would be greatly appreciated.
Thanks
yes, most people install cyanogen rom on their phone without even touching a computer
So informative ...really
Well I attempted the SDK install and when I run ADB I dont get a list of devices. When I plug in the phone windows automatically installs drivers.
So I downloaded USBDeview uninstalled and plugged the phone back in, same drivers installed.
So where to from here?
Ok so followed all the instructions on Cyanogens page and ADB will not see my device, when I go to Start > Devices the Nexus One shows up and says Driver not installed.
I downloaded the drivers from the SDK and no luck, I added the path to environamental variables, tried again, no luck
Tried to force the driver install and manually install through windows and states the driver I am trying to install doesnt contain info about my device. Check to make sure its an x64 driver.
Running windows 7 ultimate. any ideas what could fix this?
Ok so added and renamed the proper files to recovery.img and added cynaogens mod and renamed to update.zip
Rebooted phone
Recovery Mode
Wiped
Install from SDcard update.zip
Installation failed
Where am I going wrong?
Download ROM Manager from the market and you can do it from there. I think you need the pay version too do nightlies, but the stable CM releases are available in the free version.
Sent from my Nexus One using XDA App
1) Can I assume you are rooted?
2) Can I assume you downloaded the adb drivers from Google?
If so I don't know how to help you without telling you to download clockwork mod sorry.
This is what I did.
Downloaded and installed 1 click root from here http://forum.xda-developers.com/showthread.php?t=747598
Downloaded Cyanogen Rom and gapps from here http://forum.xda-developers.com/showthread.php?t=722798 and saved them to my SD card.
Downloaded Rom Manger from the Market.
Ran 1 click root
Ran Rom manager, installed the clockwork recovery from rom manager.
selected install zip from sd, found zip of cyanogen and selected it.
Pressed perform back and perform wipe then press OK.
Rom Manager did its magic and installed cyanogen for me.
The phone rebooted, I opened up rom manger again and pressed install from sd card again
Found and clicked on gapps zip file. This time I didn't perform a backup or wipe(not sure if I was supposed to or not), Hit ok, then ok to reboot.
Rom Manager worked its magic again and voila I had/have Cyanongen rom with my Google apps.
I did this all last night and from memory, but I'm fairly sure those are steps I took. However if it breaks your phone its your own fault
jcohenlv said:
Ok so added and renamed the proper files to recovery.img and added cynaogens mod and renamed to update.zip
Rebooted phone
Recovery Mode
Wiped
Install from SDcard update.zip
Installation failed
Where am I going wrong?
Click to expand...
Click to collapse
Ur phone is not rooted. Period
jcohenlv said:
So informative ...really
Well I attempted the SDK install and when I run ADB I dont get a list of devices. When I plug in the phone windows automatically installs drivers.
So I downloaded USBDeview uninstalled and plugged the phone back in, same drivers installed.
So where to from here?
Click to expand...
Click to collapse
It will pop up and says that it cant find the driver for ur phone. Go on and manually apply the driver urself then u are set.
Not sure if this will help, but check USB debugging and the one below it in phone settings/applications/development.
Ken
Phone is rooted, used 1 click root.
When I try and manually install the driver Win7 tells me the drivers I try and load do not contain information about my hardware.
Ill try Average Canadians method and see how it goes.
Thanks
Ok so I attempted this as mentioned,
Now my phone is stuck at a looping "Cynaogen Mod" screen after doing the backup from Rom Manager.
Steps Taken to This Point:
D/L One Click Root - Unrooted Phone
Ran One Click Root Again - Rooted Phone
Downloaded Clockwork Rom Manager
Set Permissions For Super User
Downloaded Cyanogen 6 RC3 + GApps
Ran backup - phone rebooted
Phone rebooted and ran a bunch of stuff got to Cyanogen (mod) loading screen (looks like a boot animation) and this is where its stuck looping.
Any Ideas?
The animation is an android on a skateboard with a blue arrow circling it and has what I will call "lightning" circling around the outside. The lightning gets about 3/4 of the way around the circle then the screen goes black and starts over.... just wanted to give a bit more information.
Any help would be appreciated
Thanks
OK booted into recovery, got a green screen instead of the typical blue which I am assuming is a good sign
Ran "install from sd card"
Navigated for a few minutes till i found the Cyanogen zip file (update-cm-6.0.0-N1-RC3-signed.zip)
Installed
Phone rebooted
Got to Cyanogen Mod loading screen phone rebooted again and its stuck in the loop again......
Any ideas?
Ok attempted to flash back to stock FroYo 2.2 and getting:
asster failed: file_getprop("/system/build.prop. "ro.build.fingerprint") == google/passion/passion/mahimahi:2.1-update1/ERE27/24187:user/release-keys" ||
file_getprop("/system/build.prop. "ro.build.fingerprint") == google/passion/passion/mahimahi:2.2-update1/FRF50/38042:user/release-keys" || file
E:error in sdcard/update.zip
(Status 7)
Installation aborted.
I am assuming I am getting this cause the update is for FR50 and not FR91?
Ok so another update
Attempted to flash 2.1.1_Downgrade and still getting same error as above just with a different file name version.
At this point I will just wait for one of you to get back to me hopefully
Ok so .. trial and error is a great way to learn
If I would have opened my eyes the first time I would have seen the "nandroid" option and just restored my backup
So after a minor freak out, and a cigarette I have regained my composure and I am in the process of a restore. Lets see what happens
Ok so phone is back to where it was when I did the backup.....
Going to attempt this again and try it with what I think was the missed step THE WIPE!
Uh oh..... got the blue screen instead of the green screen before phone wiped .... hmm guessing that when i did the restore it re-flashed the original recovery mode. So looks like I am starting over with a fresh phone ....lol
(hope this commentary isnt too annoying, but they way I see it is one day it may help another noob like myself do this on his phone )
WOOT WOOT!
So there it is! CM 6 RC3
I want to thank everyone who offered advice in this thread and to that crazy Canadian who offered a great option to get this done!

[Q] N1 in trouble! Please help

Hi guys...
First off, i'm somewhat of a noob. Got my N1 already rooted a few months back but i've tried many different ROM's since. I'm using Clockworkmod Recovery.
I was running Cyanogen 6.1 yesterday and wanted to create a backup of stock froyo for gingerbread's release.
So, i did a backup of Cyan 6.1 and followed the following steps off Android Central's forum.
Step One
Download this file. It's the flashable, stand alone version of FRG33.
You can't go straight back to FRG83 using this method. Just trust us.
Place the PASSIMG.zip file on the root of your SD card.
Power off your Nexus One, then hold volume down while pressing the power button.
Your phone will spend a minute or so looking for an update file (the PASSIMG.zip file).
When it has the info it needs, it will ask if you would like to install it. Press the volume up key to choose to install the file.
Your Nexus One will take another few minutes installing the update, then it will reboot.
Let it reboot the whole way, then go on to step two.
Step two is for the update to FRG83 which i did.
The phone boots and runs fine...
But ever since I did all that, my N1 looks like its unrooted. I can't use ROM manager, Titanium backup to restore since they all tell me they don't have su rights. I installed Superuser from the market. It opens but does nothing with my app's rights.
adb can't find my device when I try to list it (adb devices). Neither can Fastboot (fastboot devices), in fastboot mode.
I see the padlock at boot
I can't go into recovery. I get the robot with an exclamation mark. If i hit the power and vol-up I get the android system recovery menu (in blue) with only 4 options; reboot, apply sdcard:update.zip, wipe data/factory reset and wipe cache partition.
I've tried rooting it with Universal Androot but it failed.
I've no idea where to go from there...
Please help!
You have to root again. Use the rageagainstthecage exploit.
Sent from my Nexus One using XDA App
Ok... N1 is rooted using VISIONary.
However, I can't boot into recovery mode (clockworkmod). I still get the exclamation mark.
If I try to use adb, i always get an error: device not found.
If I try to unlock with fastboot oem unlock, i get a waiting for device message but it never finds anything....
Almost there... i think!
Ok... using Clockworkmod, flashed recovery and all is good!
Thanks for your help!

[Q] No functional recovery image... now what.

Ok, so after using clockwork rom manager on my nook color and seeing how convenient it was, I thought, "hey maybe this would be good on my milestone." WRONG. I flashed the clockwork recovery (they even had an option for milestone) and when I rebooted into recovery from the software (either in rom manager or the reboot power option) it just rebooted straight into android. When I held the power and camera keys, it just took me to bootloader.
Under rom manager, there was also an option to flash the RA recovery, but that didn't seem to help (exact same behavior as clockwork recovery).
I'm currently running the CM7 mod and prior to this fiasco, I was using RA 1.7 (pretty sure). edit: RA 1.7 was my girlfriend's HTCmagic, I just remembered that I would have had some version of openrecovery on this phone.
So, I guess my question is, what are my next steps here? I'd really like to stop flying without a recovery. My only shred of an idea was to flash a stock image from rsdlite and set my milestone all the way back to stock and then reroot and re everything, but if someone has a better idea, I'd be very open to that as my plan seems like a big hassle.
A) not really the place for this post but anywa
B) you should beable to just flash the Vulnerable recovery http://android.doshaska.net/rootable then you can install a recovery from this forum thats for our phone!
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Tyfighter said:
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Click to expand...
Click to collapse
Quite alright if you have any more problems feel free to just PM me
Check this thread:
http://forum.xda-developers.com/showthread.php?t=1139120
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Tyfighter said:
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Click to expand...
Click to collapse
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
zacthespack said:
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Click to expand...
Click to collapse
what your doing (power + camera) is meant to put you into the bootloader mode... to get into recovery, hold 'x' on the physical keyboard and then hold the power button. This will get you into recovery. Hope this helps.
~D
are you sure that you did in fact flash the vulnerable bootloader, and not a newer, non-vulnerable one? sounds like that.. exploit fails, system reboots. also, if you are running an original rom right now, it does check the bootloader every reboot and flashes the non-vulnerable one!
Tyfighter said:
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
Click to expand...
Click to collapse
I'm a bit confused with how you're getting into Recovery mode, but the way to enter recovery is to hold Power + X, then Camera + Vol Up when you see the Motorola Logo.
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
EDIT: Despite RSD lite saying that the process as a success, the reflash did nothing.
Tyfighter said:
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
Click to expand...
Click to collapse
Where did you get the VR sbf? android.doshaska.net/rootable ?
Yep, that's the one.
EDIT: Finally got up the guts to load the official Telus sbf into RSD lite and pull the trigger. It seems like this is probably beyond salvage now. Once again, many thanks to everyone, and if all goes well, I hope to only be in the ranks of the unrooted/unmodded for a few minutes.
EDIT the second: Okay, so flash to stock went perfectly. Everything works, including recovery, but not openrecovery. I can get to the menu to flash the .zip, but it fails the esignature check. Which I'm assuming points to Vulnerable recovery not flashing correctly or perhaps my file is corrupt, or maybe something more exotic and exciting. I flashed SHOLS_U2_03.11.0 if that's relevant.
For those interested, everything is up and functional again.
I had to first flash back to stock, then flash the vulnerable recovery located at http://modmymobile.com/forums/downloads.php?do=file&id=28089 , then the standard, boot to recovery, blah blah blah, install a new rom.
Let this be a lesson to the rest of you; Clockwork Rom Manager does not, I repeat, does NOT seem to work on our milestones. Which is a real shame...
I realize this is a double post, but I'm just so darned jubilant to be able to update my rom again.

[Q] Screwed Up GingerVolt Install

So, I activated my phone and then rooted the phone fine, using the all-in-one package for root.
After that I flashed GingerVolt + BlitzKrieg . I think it was wrong to install BlitzKrieg Kernel without at least booting once with GingerVolt stock kernel.
So when the thing booted up, it failed to detect the SIM card, and won't activate again. (the SIM was already activated before rooting). But now the activation process said, 'NO SIM found' .
Anyway, after that , I was unable to boot in to recovery, the phone would hang when selecting 'revocery' from the power button option. and Power Button + Vol Down also didn't work.
So with no way to go back in to recovery, I did a 'factory reset' from the settings menu.
After that the phone boots in CWM recovery, but that's all it does. It only boots in recovery. I have tried to reflash GinngerVolt or to restore to the backup (Stock + root) but to no avail.
Now the phone is stuck booting in to recovey. "adb devices" shows
"IMEI-NO recovery". But no matter what, I can't get it to boot normal.
Any clues how I can get out of this mess ?
Replying to self.
Looks like the culprit is using 'factory reset' method. Found another thread, and a solution on another forum (Can't post links yet )
Gonna try the LGNPST method.
For any newbies looking in to this, the lesson is
1) Boot atleast once in GingerVolt before overwriting stock kernel.
2) DON'T USE 'FACTORY RESET' option, you phone will then only boot in CWM.
If that doesn't work, there is another thread somewhere that has an "exit recovery zip" that you can flash. That may work.
From My Bryce Device
Edit: here's the thread
http://forum.xda-developers.com/showthread.php?t=1161537
Thanks KaneOfMars, but I was able to get back to stock, using LGNPST, although I suspect your link would have worked just as well.
In fact using LGNPST was an adventure in it self, every time I clicked the Upgrade button, the LGNPST.exe would crash (Windows 7 64bit). So tried the China Telcom version LGNPST_CT.exe, and that one said 'c:\windows\system32\drivers\wnsdrvr.sys NOT FOUND'.
Then found another LGNPST_CT.exe standalone inside the LGNSTP.zip file which contained the LGNPST installations.
Put this LGNPST_CT.exe inside the C:\LG Electronics\LGNPST folder, and this one had another option beisdes, "Upgrade" called "Binary Download".
And that is a misnomer, coz it is infact "Binary Upload" to the phone, and this option is the one I used to upload the 'V*7.tot' file (the stock 2.3.4 image), back on LG Revo.
Hope someone can benefit from some of this, I spent a good part of yesterday figuring all this out.
gumnaam.sur said:
Thanks KaneOfMars, but I was able to get back to stock, using LGNPST, although I suspect your link would have worked just as well.
In fact using LGNPST was an adventure in it self, every time I clicked the Upgrade button, the LGNPST.exe would crash (Windows 7 64bit). So tried the China Telcom version LGNPST_CT.exe, and that one said 'c:\windows\system32\drivers\wnsdrvr.sys NOT FOUND'.
Then found another LGNPST_CT.exe standalone inside the LGNSTP.zip file which contained the LGNPST installations.
Put this LGNPST_CT.exe inside the C:\LG Electronics\LGNPST folder, and this one had another option beisdes, "Upgrade" called "Binary Download".
And that is a misnomer, coz it is infact "Binary Upload" to the phone, and this option is the one I used to upload the 'V*7.tot' file (the stock 2.3.4 image), back on LG Revo.
Hope someone can benefit from some of this, I spent a good part of yesterday figuring all this out.
Click to expand...
Click to collapse
Just for reference, you can do a factory reset but ONLY through recovery. Doing a factory reset through the phone menu is what will get you stuck in recovery.
Sent from my GingerFusion Revo using Tapatalk.

[Q] Quick Question about MB886

Hello Everyone,
I have a Motorola Atrix HD MB886 and have been successful at unlocking the bootloader. I want to upgrde the rom from 4.1 to 4.4. Every article that I have found says start in restore mode and gives directions on what to do. Well the first 3 steps are there with no problem but when it says to "Wipe Dalvik cache" and to "Install zip from SD card". Those features are not there. I do have a feature that says install from external SD card but it does not see the zip file. So I have taken another approach. I have installed an app called Rom Customizer and it does see the package and again it informs me it need to boot in recovery mode. The phone just sits there and displays the android logo with the red triangle but never does anything then reboots as normal without applying any changes. What am I doing wrong? I will admit I am new to this and this is my other phone. When the logo appears are my supposed to do something? If I do go into the recovery mode I still only have the same options as before so am I leaving something out? Any help will be appreciated and thanks in advance....
texasgoldbuyer said:
Hello Everyone,
I have a Motorola Atrix HD MB886 and have been successful at unlocking the bootloader. I want to upgrde the rom from 4.1 to 4.4. Every article that I have found says start in restore mode and gives directions on what to do. Well the first 3 steps are there with no problem but when it says to "Wipe Dalvik cache" and to "Install zip from SD card". Those features are not there. I do have a feature that says install from external SD card but it does not see the zip file. So I have taken another approach. I have installed an app called Rom Customizer and it does see the package and again it informs me it need to boot in recovery mode. The phone just sits there and displays the android logo with the red triangle but never does anything then reboots as normal without applying any changes. What am I doing wrong? I will admit I am new to this and this is my other phone. When the logo appears are my supposed to do something? If I do go into the recovery mode I still only have the same options as before so am I leaving something out? Any help will be appreciated and thanks in advance....
Click to expand...
Click to collapse
Do you have a custom recovery? philz recovery is the best for me. http://forum.xda-developers.com/showthread.php?t=2686374

Categories

Resources