Related
Hey Guys,
I hope this is in the right section. I'm having some issues with my rooted G1.
I couldn't get it to update to DRC92 (http://db.androidspin.com/android_developer_display.asp?developerid=21) so i tried following these instructions (http://forum.xda-developers.com/showthread.php?t=553416) in the hope starting from scratch would solve the issues. I couldn't even get passed the step 7 in the guide as telnet gave a connection refused error.
I'm now stuck on RC7 and every time i try to add a rom i get
Code:
E:No singnature (454 files)
E:Verification failed
I also tried to change the recovery image to cm-recovery-1.4.img to try and install Cyanogen and i got the error "flash_image: not found".
I would prefer to have the official DRC92 rom installed though.
Does anyone have and ideas as to what the problem is and how i can get around it?
Thanks a lot for your help.
Best Regards, George
Im confused wether you have root...If you are on XDA your arse better have that HTC device or your looking around the wrong ******* forum.Im guessing your phone is fully stock fresh from th bakery i presume? If you have 1.5 now you better get to finding the one click root or find your way over to cyan wiki for the root guide.I be your arse to clicks and dog that you would be better off having root than stock.Oh yeah i forgot but welcome to xda and you better be gettin that root instead of reading this.Are yo usure you have root? WHat recovery are you changing from? You said you wanted to change it to cyan 1.4 when there are only 2 recovery avail..
Thanks for your reply. Yes i have root, i rooted it using an older guide that i can't find now. The recovery image was recover_testkeys.img.
The recovery image i tried to install is at te bottom of this page http://db.androidspin.com/android_developer_display.asp?developerid=3.
Any ideas?
GOPalmer said:
Thanks for your reply. Yes i have root, i rooted it using an older guide that i can't find now. The recovery image was recover_testkeys.img.
The recovery image i tried to install is at te bottom of this page http://db.androidspin.com/android_developer_display.asp?developerid=3.
Any ideas?
Click to expand...
Click to collapse
That is older than the milk used to make yogurt =/
Follow this right air
http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
I bought my phone used and I used the universal androot app to root it without locking the bootloader. I want to take it back to just the way it was when it came out of the box. Are there easy to follow step by step directions anywhere? I've searched but everything says it assumes you know how to use adb and fastboot. I don't. Do directions exist for dummies? It sure was a piece of cake to restore my old iPhone.
Yeah, I had the same problem a few weeks ago. My suggestion is look at some tutorials for installing custom ROMs and then reverse engineer those once you've learned how to use adb and fastboot.
You mean something like this -->
http://androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
cymru said:
You mean something like this -->
http://androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
Click to expand...
Click to collapse
Kind of like that, but this part confused me.
"Once you have this installed, add a folder path for the ADB utility to your System Environment Variables “path” variable."
Ok, when I get to step 7, the command prompt says "FAILED (remote: not allowed)"
What's up with that? HELLLLLLP!
I did a manual erase user data, but now when I go to Type 'fastboot flash userdata userdata.img'
the command prompt tells me FAILED (remote: signature verify fail)
Help?
Okay, sounds like you're panicking.
There's kinda like a fix everything button, and that's a passimg.
Grab it here: (remove the spaces, I'm not allowed to post links)
w w w . megaupload . com/?d=7JQU3MV0
All you gotta do is put that on the root of your SD card. Boot into bootloader mode (hold down trackball when powering) and select recovery. That's all. It'll detect passimg, and fix everything.
The caveat here, is that you'll be on EPE76 - which was super duper annoying to actually upgrade from (but I eventually found a FRF91 rom that worked - I'll see if I can find it and post it for you).
But yeah. Download that. Fix everything. Enjoy
From EPE76 can't you just do an OTA update to upgrade to Froyo? And what exactly does this passimg do and how does it work? I got adb and fastboot working and everything, I just get errors when I try to flash. Do you have to have an unlocked bootloader to do this stuff? I just used the universal androot app to gain root, so the bootloader wasn't actually unlocked.
No. the passimg will just automatically flash radio, recovery, etc. so you don't have to. If you've got it working manually now, no need to use it.
The passimg does pretty much what you were asking about. The Nexus One has the code name "Passion", so "pass/img" is the original factory shipping image for the Nexus One. The OTA should then** come to your phone, maybe in a few hours, but maybe not for a while.
And if I do the passimg it shouldn't screw up the phone since I'm already running froyo and this will kick me back to 2.1?
Read - Nexus One Wiki, "Unroot / Restore your Nexus", PASSIMG.ZIP method.
Written especially to avoid threads like this one.
Well it worked perfectly and now I'm running 2.1 EPE76. Is there a way to force it to update to Froyo?
you should be able to open up your dialer and type
*#*#CHECKIN#*#*
or
*#*#2432546#*#*
scgolfer7 said:
you should be able to open up your dialer and type
*#*#CHECKIN#*#*
or
*#*#2432546#*#*
Click to expand...
Click to collapse
That's a negative. It just says checkin result success, but doesn't download any update. When I go to about phone and system updae it says my system is up to date.
If I was reading correctly I should upgrade from EPE76 to FRF85B and then I should get the FRF91 OTA? Can anyone confirm this?
I got everything working and I'm back to completely stock Froyo FRF91 and I just wanted to thank everyone who contributed to this thread for guiding my annoying newbie ass through the process and teaching me a wealth of knowledge about the Android OS along the way. Thanks again!
For future reference, if you want to restore your phone while having no issues accessing it, just get Rom Manager. Use it to download and install a stock unrooted Froyo rom (just make sure to select wipe data and do not select the rooting options).
Very easy to restore. The passimg method comes in very handy if you cannot even boot into the OS.
I bought a Nexus One second hand. It was rooted and the RA-nexus-v1.9.0-alpha recovery installed.
The ROM was: Android 2.2 (stock)
Build number: FRF91
So, to update to 2.2.1 I downloaded signed-passion-FRG83-from-FRF91.c8847c98.zip and renamed it to update.zip and put it on the SD card. Booted into the recovery, selected flash from SD card and update.zip. I got the following error:
Code:
Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprintE:unknown command [")]
file_getprop("/system/build.prop", "ro.build.fingerprint") == "gE:unknown command
[oogle/passion/passion/mahimahi:2.2.1/FRG83/60505:user/release-keys"]
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted
How do I solve this? I have googled and looked in these forums but I don't have any idea. I wish this phone wasn't rooted so I could just get OTA update, I am very new to android and I really have no idea whats going on and I am afraid to break the phone.
Follow the Unroot/Restore guide here. I recommend FRG33, because 83 can be tricky to flash:
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Sent from my Nexus One using XDA App
Should I use the fastboot method or the PASSIMG.ZIP method? Do I actually need to install the whole ROM again even if it is stock 2.2? I think mine is one of the newer nexus ones (SLCD screen) that came with 2.2 from factory. Also, the PASSIMG method does not seem to explain how to flash original recovery image back.
Sorry for the stupid questions =/
All good questions, if they help you understand...
Fastboot method requires an unlocked bootloader.
I'm guessing your stock ROM will be a rooted stock ROM. This will make sure you're 100% stock, so you can get updates, etc...
This should update recovery, also (can't confirm, because I have never tried it). If not, we can fix that later...
Sent from my Nexus One using XDA App
Yea but I think mine has an unlocked bootloader also, I see that unlock sign when my phone starts up.
I didn't really understand your last response, did you imply I should go with the Fastboot method?
If you have unlocked bootloader, download FRG83 stock ROM, extract the ZIP, and flash images one by one using fastboot. AKA - the fastboot method.
the fastboot method seems a bit complicated, i don't really feel confident with adb and fastboot tools as i have never used them. Would the PASSIMG method also work? It seems that with that all you have to do is copy a ROM to the sd card and flash it? Does it also take care of installing default recovery?
PASSIMG will work with FRG33. Then you'll have to update to FRG83, either by waiting for OTA or by flashing the update manually.
Hm, looks like my ROM isn't rooted. I installed titanium backup and it said no root access. So do i need to go through this whole process at all? If my phone isn't rooted, why am I not seeing 2.2.1 or is that cause i have custom recovery?
Can i just flash 2.2.1 manually using RA recovery? or should i flash stock recovery? if so, how?
Ah edit: the passimg will work you say - will that also go to stock recovery?
Ok. i bit the bullet and did this update using the PASSIMG method and flashed FRG33. It seems to have worked, now if I go into recovery i see a little android with a ! mark in a triangle. Thats stock right?
Thanks for all your help, now how do i force check for updates?
! = stock, yes.
*#*#CHECKIN#*#* (from phone dialer) for updates...
Sent from my Nexus One using XDA App
Ok, i typed that in my dialer and in notification it said "checkin succeed". But when I go to check for updates, i still get nothing.
About phone shows this:
Android Version
2.2
Baseband version
32.41.00.32U_5.08.00.04
Kernel version
2.6.32.9-27237-gbe746fb
[email protected] #1
Build number
FRG33
I'll see if I can find the update. Might take a while...
Sent from my Nexus One using XDA App
any idea why I am not getting it OTA? is it not released in all regions still?
Sorry I took so long (family comes first).
Here ya go (stolen from Rusty - all props to him)
Download:
http://shipped-roms.com/shipped/Pas...RG83 OTA update, possibly from FRF91 too).zip
Rename it to update.zip and copy it to the root of yout SD card.
Power off the phone, hold Vol- and power on. It will boot to the bootloader, detect the passimg file and ask if you wish to install.
After it's done (I think it'll reboot itself, if not, select recovery), power off and power on with Vol- held again. This time dont install the passimg.zip, and choose recovery.
At the Android & warning triangle, hold the power button and press Vol+
Choose install update.
Voilà, a completely up to date, stock phone.
syl0n said:
any idea why I am not getting it OTA? is it not released in all regions still?
Click to expand...
Click to collapse
Could be any number of reasons.
Worry about it if you don't get the next update...
Don't stress, we'll make sure you get Gingerbread... XD
Sent from my Nexus One using XDA App
Will doing update like this, wipe all data on my phone? Or will it be like OTA?
Not sure why you are talking about a passimg.zip, in the previous email. Don't I only have a update.zip?
Sorry dude, I did a cut and paste from one of Rusty's posts, while playing with my son...
This is just like an OTA, and won't wipe anything...
Sent from my Nexus One using XDA App
Just add update.zip to the root of your SD, and flash via recovery...
Sent from my Nexus One using XDA App
thanks ive finally got FRG83 Android 2.2.1 installed on my N1.
Help! I need to unlock my phone and I don't know how!!
The wiki is helpful: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I897
What
Sent from my PC36100 using XDA App
Think you can just use superoneclick root app for computer with phone connected. Can search boards for soc.
Sent from my Samsung Vibrant using XDA App
Thats to root the phone not unlock it, there is an app in the Captivate Developers forum just search and you will find it.
To unlock the samsung SGH I897 CAPTIVATE,You can use the unlock code.You can buy the unlock code from Online site and unlock it...I suggest the site
Wickedunlock.com there you can buy the code for samsung SGH I879 Captivate.,unlock it.
unlocking captivate
there is two ways to unlock the cappy. The most successful one that i have used multiple times is sgs unlock pro I am not sure if the app is still on the market but you should be able to find it on the web or on the app 4shared
Use Galaxy_s Unlock from the market. Its free and worked for me.
Use this. Remember to back up thaat EFS folder on more than JUST your phone. If by any chance it messes up or something else happends that EFS back up will save you a IMEI rebuild....
Can you ask AT&T?
Sent from my SAMSUNG-SGH-I897 using XDA App
Unable to Unlock, Unable to root
Hi Guys,
I am trying to unlock my captivate SGH-I897 by myself (not buying a code) and I am having some trouble in doing it. I have done several steps, each time going backwards to a preview requisite but now I am stucked.
First, I downloaded from the market the app Galaxy S Unlock and when I try to see the SIM Unlock code I get error "You have a busybox problem, fix it."
From this app I cant also save the actual efs folder.
Since I saw that error, I download from the market "Busy Box Free" and when I try to install it, I get the error "The su binary was not found on your phone. This application will not work without root", so I said, let's try to root my cell, this is how I got here and found the topic http://forum.xda-developers.com/showthread.php?t=739304.
I downloaded that app to my PC, followed the step but when my captivate restarts and enters into Android Sys Recovery and I try to reinstall the packages I get the following:
"--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted"
And from this point on I dont know what to do.
Basically what I have done is:
Galaxy S Unlock > Busy Box > Root > Stucked....
I try to post in the One Click root/unroot post bu since I am noob, I couldnt.... Hope you can help guys
t_aaron_h2 said:
Hi Guys,
I am trying to unlock my captivate SGH-I897 by myself (not buying a code) and I am having some trouble in doing it. I have done several steps, each time going backwards to a preview requisite but now I am stucked.
First, I downloaded from the market the app Galaxy S Unlock and when I try to see the SIM Unlock code I get error "You have a busybox problem, fix it."
From this app I cant also save the actual efs folder.
Since I saw that error, I download from the market "Busy Box Free" and when I try to install it, I get the error "The su binary was not found on your phone. This application will not work without root", so I said, let's try to root my cell, this is how I got here and found the topic http://forum.xda-developers.com/showthread.php?t=739304.
I downloaded that app to my PC, followed the step but when my captivate restarts and enters into Android Sys Recovery and I try to reinstall the packages I get the following:
"--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted"
And from this point on I dont know what to do.
Basically what I have done is:
Galaxy S Unlock > Busy Box > Root > Stucked....
I try to post in the One Click root/unroot post bu since I am noob, I couldnt.... Hope you can help guys
Click to expand...
Click to collapse
Look for another 1 click su. The other one has 2 method. Use the none default (I forget the name). Can't help don't have links on phone and no net on computer. Best of luck.
Sent from my ICS powered Captivate using Tapatalk
thanks for the recommendation...
Now I tried to download the update file from here 3w.box.com/shared/jrlqei92q6 and I saved it into my captivate.
Once I had the file in the phone, with Lidia File Manager I moved it from downloads to SD card root. Turned off the phone, entered to recovery and tried to reinstall the packeges and still get the same error
"--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted"
Any other clue????
t_aaron_h2 said:
thanks for the recommendation...
Now I tried to download the update file from here 3w.box.com/shared/jrlqei92q6 and I saved it into my captivate.
Once I had the file in the phone, with Lidia File Manager I moved it from downloads to SD card root. Turned off the phone, entered to recovery and tried to reinstall the packeges and still get the same error
"--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted"
Any other clue????
Click to expand...
Click to collapse
You are on something that isn't 2.1 so you have 3e recovery. The other method I mentioned works on GB so it should work with 3e.
Sent from my ICS powered Captivate using Tapatalk
It looks like you have Froyo on your phone, and will need to flash a kernel with CWM/root already baked into it. You'll need Odin or Heimdall (look in the stock rom master collection sticky in the Development section - it's at the end of the first post in that thread), and the Speedmod Kernel. Flash the k13e.tar file, and you should be good to go with no 3e issues.
jmtheiss said:
It looks like you have Froyo on your phone, and will need to flash a kernel with CWM/root already baked into it. You'll need Odin or Heimdall (look in the stock rom master collection sticky in the Development section - it's at the end of the first post in that thread), and the Speedmod Kernel. Flash the k13e.tar file, and you should be good to go with no 3e issues.
Click to expand...
Click to collapse
^ In fact, after checking "about" on settings I realized froyo was the issue.
I thought a was not gonna be able to do what you said, but after looking up and reading the guides and downloading the right kernel I was able to root my cell!!!
Once it got root, I was also able to install busy box free and use Galaxy S Unlock... So I finally got it done!
Thanks bassplayer and jmtheiss!!!
Hi there,
Before anyone gets angry: I don't want to start a 1000st repetition of questions asked right 2 posts before, nor am I too lazy to use google or read the articles themself.
I just want to know, if there's somebody out there, who succeeded with exactly the same circumstances I failed.
I own a German Motorola Milestone . It is a Milestone, not a Droid! I guess, this is important, since I've read tons of these threads, which all ended in that way, that one tells that the Milestone is a lot stronger protected than the Droid from Verizon is, because it uses Signatures and stuff, to prevent anwanted development for the device.
I always was too shy to apply something like cyanogen to my phone or even root it, because I spend some hope to the (at last) shipped Froyo Update for the device, to make things better. But since Motorola not even raised the CPU clock (which runs only at 550, but 1200 MHz are reported to work without negative issues) to even 800 MHz and I can feel this with Froyos animations and Flash, I decided to give cyanogen a try. I tried to root the device (which succeeded) and tried also all overclocker apps on the market which made the device reboot instantly when applying (but did not raise the speed).
Now I'm trying to install cyanogen since several days, but all guides fail for me.
It all fails when it comes to applying the update.zip: Clockworks's rom Manager, which tells me that the recovery Programm couldn't be found at the boot prompt, opening the update.zip directly gives a message about something's failing with the certificates, ... an endless story
I come more and more to the guess, that all success messages for applying cyanogen to a milestone are only hoaxes, because someone couldn't tell the difference between a milestone and a droid on ebay and such.
I would be very thankfull for any answers, may they tell me that this is true, or that they have succeeded (and how!) Or even hand me the right guide. I have the feeling that I've allready read all the false ones
Sent from my Milestone using XDA App
Richter_Marc said:
Hi there,
Before anyone gets angry: I don't want to start a 1000st repetition of questions asked right 2 posts before, nor am I too lazy to use google or read the articles themself.
I just want to know, if there's somebody out there, who succeeded with exactly the same circumstances I failed.
I own a German Motorola Milestone . It is a Milestone, not a Droid! I guess, this is important, since I've read tons of these threads, which all ended in that way, that one tells that the Milestone is a lot stronger protected than the Droid from Verizon is, because it uses Signatures and stuff, to prevent anwanted development for the device.
I always was too shy to apply something like cyanogen to my phone or even root it, because I spend some hope to the (at last) shipped Froyo Update for the device, to make things better. But since Motorola not even raised the CPU clock (which runs only at 550, but 1200 MHz are reported to work without negative issues) to even 800 MHz and I can feel this with Froyos animations and Flash, I decided to give cyanogen a try. I tried to root the device (which succeeded) and tried also all overclocker apps on the market which made the device reboot instantly when applying (but did not raise the speed).
Now I'm trying to install cyanogen since several days, but all guides fail for me.
It all fails when it comes to applying the update.zip: Clockworks's rom Manager, which tells me that the recovery Programm couldn't be found at the boot prompt, opening the update.zip directly gives a message about something's failing with the certificates, ... an endless story
I come more and more to the guess, that all success messages for applying cyanogen to a milestone are only hoaxes, because someone couldn't tell the difference between a milestone and a droid on ebay and such.
I would be very thankfull for any answers, may they tell me that this is true, or that they have succeeded (and how!) Or even hand me the right guide. I have the feeling that I've allready read all the false ones
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
OK, lets start over with your phone using some different method using my own guide. Do these steps to install CM 7 on your phone
1. Revert your phone back to stock
2. Install Androidiani OpenRecovery
3. Install Custom ROM
All from my guide: http://forum.xda-developers.com/showthread.php?t=983516
If you got any question ask them in the thread or PM me
1. Clockworks's rom Manager doesn't work on Milestone. I screwed that up too so don't feel too bad about that lol.
2. Start here http://forum.xda-developers.com/showthread.php?t=784750
You want CM so start with the CM for milestone thread that explains it directly.
From that page, get Androidian Open Recovery and prepare you SD Card.
3. Now follow instructions on this page: http://android.doshaska.net/rootable.
a. Install RSD Lite 4.6
b. Get the vulnerable recovery sbf and apply it with RSD Lite. (It's tiny... about 5mb)
c. Grab the "Disable_recovery_check_by_OTA" script and put it in sdcard/openrecovery/scripts folder.
4. Put CM6 or CM7 update.zip in the sdcard/openrecovery/updates folder.
5. Boot into Open Recovery. Apply the script from step 3
6. Install CM from the Apply Update menu.
edit: I didn't see post#2 when I hit send lol. I had started, went to do something and finished when I got back.
First of all: Thank both of you for your very nice (and unbelievable quick) replies!
Since you two suggest quite equal ways, and report that even this stupid EU-Brick is capable of running cyanogen, I'm quite enthusiastic, that I will succeed in the next days
I'll update the status here as soon as I git a new one.
eXtink said:
OK, lets start over with your phone using some different method using my own guide. Do these steps to install CM 7 on your phone
1. Revert your phone back to stock
2. Install Androidiani OpenRecovery
3. Install Custom ROM
All from my guide: http://forum.xda-developers.com/showthread.php?t=983516
If you got any question ask them in the thread or PM me
Click to expand...
Click to collapse
Hi eXtink,
I followed your guide and succeeded for an impressive long time. All went well:
I ...
applyed the german .sbf succeffully
booted / set up successfully Androidiani OpenRecovery 3.3
gained root
Installed Cyanogen 7 (0.08-11.03.16 RC3)
All these steps ran without displaying any error. But now, when I reboot the device, I only see the blue Cyanogen - Droid, skating within a blue circle. This hasn't changed several times for more than 10 Minutes now.
Can you tell what's wrong here?
do you see the first bounce again and again?
If it does, it's boot looping which isn't good.
But it usually takes a long time to load the first time...
So if it's not bootlooping, and it's going on for like 15 minutes, you can press shift alt delete to reboot and then try again and it should load quicker
No, it's not resetting or such, it just displays a smooth circle , but this rotates for over 10 Minutes (I rebooted it after that and re-issued a standard Froyo image onto the device after that.).
But you think I should wait for it to boot for ~15 minutes and then, while it still displays the loadspinner, reboot it? Did I understand you correct?
yeah, if it's not bootlooping and you're tired of waiting... just reboot it again.
Sometimes it just gags...
Say, did you feel the phone vibrate at all?
If you did, the lock screen was already up but hidden behind the animation
It godamn works !!! O.O Dunno what I've changed to make this habben, but when I try the exact eaqual steps again, it just works. Everything!
You two are my heroes!!! Thank you very much!
Cyanogenmod 7 on EU - Milestone - Working !!!
Cool Beans!
I'm glad that it worked for ya!
Bonus: this thread is a pretty good "how to"!
i must give it a try for my self. i need to install Cyanogenmod too cuz i had enough with the official one
guys i am not able to perform root, im stuch at the Open Recovery stage and it is unable to locate the Update.zip in the SD Card though it is on the root. there is a problem with the Cashe file :s. any help??
and the message is:
E: can't open cache/recovery/command
--install from sdcard..
finding update package..
openinng update package..
verifying update package..
E:EOCD marker occurs after Start of EOCD
E:signature verification failed
Installation aborted
Any Ideas??
3mar84 said:
guys i am not able to perform root, im stuch at the Open Recovery stage and it is unable to locate the Update.zip in the SD Card though it is on the root. there is a problem with the Cashe file :s. any help??
and the message is:
E: can't open cache/recovery/command
--install from sdcard..
finding update package..
openinng update package..
verifying update package..
E:EOCD marker occurs after Start of EOCD
E:signature verification failed
Installation aborted
Any Ideas??
Click to expand...
Click to collapse
Did you flash the vulnerable recovery?
If so, did you copy the openrecovery folder to the root of your sdcard?
Sent from my Milstone running CM7
Just put update.zip and OR on u SD card (directly). Tur off phone launch bootloader by RSD instal vulnarable recovery. Then turn off and then power+X update.zip and u are at home
thanks guys for your posts...
I already have placed the file on the root of the SD. but seems i had a problem with the ROM, when i tried using another ROM it worked. the problem is that when i was about to continuie Rooting the machine the Touch Screen is not working any more!!! seems i lost my piece!!
zeppelinrox said:
1. Clockworks's rom Manager doesn't work on Milestone. I screwed that up too so don't feel too bad about that lol.
2. Start here http://forum.xda-developers.com/showthread.php?t=784750
You want CM so start with the CM for milestone thread that explains it directly.
From that page, get Androidian Open Recovery and prepare you SD Card.
3. Now follow instructions on this page: http://android.doshaska.net/rootable.
a. Install RSD Lite 4.6
b. Get the vulnerable recovery sbf and apply it with RSD Lite. (It's tiny... about 5mb)
c. Grab the "Disable_recovery_check_by_OTA" script and put it in sdcard/openrecovery/scripts folder.
4. Put CM6 or CM7 update.zip in the sdcard/openrecovery/updates folder.
5. Boot into Open Recovery. Apply the script from step 3
6. Install CM from the Apply Update menu.
edit: I didn't see post#2 when I hit send lol. I had started, went to do something and finished when I got back.
Click to expand...
Click to collapse
Hey I'm new here and really want to be able to get Cyanogen 7 on my Milestone (Canadian version) My only question with your how to guide here is how to install open recovery on my phone. sorry I'm very new to this stuff and dont know a whole lot.
Led Head said:
Hey I'm new here and really want to be able to get Cyanogen 7 on my Milestone (Canadian version) My only question with your how to guide here is how to install open recovery on my phone. sorry I'm very new to this stuff and dont know a whole lot.
Click to expand...
Click to collapse
Once you flash the Vulnerable Recovery via RSD Lite, you want to place the AOR files that you can get from the sticky in Milestone development section onto the root of your SD card.
skadude66 said:
Once you flash the Vulnerable Recovery via RSD Lite, you want to place the AOR files that you can get from the sticky in Milestone development section onto the root of your SD card.
Click to expand...
Click to collapse
OK thanks! One more question though. is there a specific sbf I need? I have a vulnerable recovery sbf called "vulnerable_recovery_only_RAMDLD90_78.sbf" would this be the right sbf for a canadian Milestone on telus? if not I found a thread on this forum that has a link to a vulnerable recovery sbf for telus milestones (found here http://forum.xda-developers.com/showthread.php?t=983516 )
also my device wont show up in RSD, why would this be? I've tried hitting the show device button numerous times but nothing happens
Led Head said:
OK thanks! One more question though. is there a specific sbf I need? I have a vulnerable recovery sbf called "vulnerable_recovery_only_RAMDLD90_78.sbf" would this be the right sbf for a canadian Milestone on telus? if not I found a thread on this forum that has a link to a vulnerable recovery sbf for telus milestones (found here http://forum.xda-developers.com/showthread.php?t=983516 )
also my device wont show up in RSD, why would this be? I've tried hitting the show device button numerous times but nothing happens
Click to expand...
Click to collapse
Yes, the SBF that you have (vulnerable_recovery_only_RAMDLD90_78.sbf) is the one that you can use. I used it for rooting my Telus Milestone as well. When you want to revert back to stock, that's when you'll need a Telus-specific SBF.
skadude66 said:
Yes, the SBF that you have (vulnerable_recovery_only_RAMDLD90_78.sbf) is the one that you can use. I used it for rooting my Telus Milestone as well. When you want to revert back to stock, that's when you'll need a Telus-specific SBF.
Click to expand...
Click to collapse
k great thanks! so I got CM7 for milestone installed on my phone, and it loads up and everything but every few seconds i keep getting a message android.phone stopped responding. So I essentially cant do anything cause this message keeps coming up, also I'm getting a no service signal too, its not registering with Telus. Please help