[Q] CM7 on a HBOOT 1.01 Legend - is it possible?? - Legend General

Okay brief background:
Originally stock VFAU supplied Legend, updated to the stock Froyo. Rooted by (roughly) following the steps outlined in the How to root HBoot 1.01 thread and am now happily able to flash roms using ClockworkMod 3.0.0.6 "fake flash" update.zip
Was keen to try out CM7RC2 on this phone so I have downloaded the update and Gapps .zips from the Cyanogenmod wiki page.
Tried multiple times now to flash the CM7 update and the relevent Gapps, always formatting user data / cache / dalvik before hand. After the process, I am always able to boot into CM7 on the device, but it appears the Gapps update hasn't been applied properly / at all. For example - on initial boot, I don't get the google android setup wizard, so no way to link the phone to my gmail account. Gmail app isn't installed, and when I try to launch Market it just goes to a white screen for a second, and then back to the launcher.
I'm wondering if this is related to the fact that the phone is on HBOOT 1.01, and S-ON? or is there another explaination? eg, a specific kernel, or radio that I should be flashing before I try to flash CM7 (nothing is mentioned in the install guide over at CM wiki).
Thanks in advance.

are you shure ou downloaded the right gapps
the one touse is "gapps-mdpi-20101020-signed"

karlanal said:
are you shure ou downloaded the right gapps
the one touse is "gapps-mdpi-20101020-signed"
Click to expand...
Click to collapse
Hey mate, thanks for the quick reply! Just to clarify - are you sure this is the right version of Gapps for CM7 on the Legend?? Looking here under the "Google Apps Version" section it appears that the correct version for all devices running CM7 should be Gapps-gb-20110307-signed.zip and that gapps-mdpi is for CM6??
I tried your suggestion nontheless, and with that version of Gapps flashed - I'm now getting a boot-loop of the cyanogen boot animation

I'm on HBOOT 1.01 (Vodafone Legend) and CM7 was the first I tried, though it was back around the nightly build 31. I didn't have any issues and CM7 started up straight away. I realised I was missing all the Google stuff so did a separate flash, maybe you could try this. I'm yet to try the RC version hopefully no issues here...

EpicSauce said:
I'm on HBOOT 1.01 (Vodafone Legend) and CM7 was the first I tried, though it was back around the nightly build 31. I didn't have any issues and CM7 started up straight away. I realised I was missing all the Google stuff so did a separate flash, maybe you could try this. I'm yet to try the RC version hopefully no issues here...
Click to expand...
Click to collapse
I have tried flashing the gapps package as a separate flash (after the intial flash to CM7, booting into CM7, then reboot into recovery to flash Gapps), and the result has been the same as when I flash them together.
I had wondered about trying a nightly, but being new to CM roms please forgive my next question. To flash a nightly, do I first have to flash CM7 RC2, then flash the nightly, or can you just flash the nightly by itself, then Gapps over the top??
I'm definitely willing to give it a try at this stage.

Flashing the nightly won't need a prior RC2 flash, its a self contained package so you shouldn't have any problems. Hopefully the Gapps flash works this time.

black beard said:
Hey mate, thanks for the quick reply! Just to clarify - are you sure this is the right version of Gapps for CM7 on the Legend?? Looking here under the "Google Apps Version" section it appears that the correct version for all devices running CM7 should be Gapps-gb-20110307-signed.zip and that gapps-mdpi is for CM6??
I tried your suggestion nontheless, and with that version of Gapps flashed - I'm now getting a boot-loop of the cyanogen boot animation
Click to expand...
Click to collapse
yes i was wrong, gave you the wrong gapps suggestion
i was allways using "gapps-gb-20110120-signed" and all was working great

EpicSauce said:
Flashing the nightly won't need a prior RC2 flash, its a self contained package so you shouldn't have any problems. Hopefully the Gapps flash works this time.
Click to expand...
Click to collapse
Well tried flashing the latest nightly last night, full wipe, then flash, then reboot, then reboot into recovery and flash the Gapps and it worked!! Don't really understand why something like that wouldn't work with the RC
karlanal said:
yes i was wrong, gave you the wrong gapps suggestion
i was allways using "gapps-gb-20110120-signed" and all was working great
Click to expand...
Click to collapse
Thats cool mate - made me recheck myself anyway

Related

Moving from Cyanogen to Super D

Hi Peeps,
I have searched in vain for a guide to changing from cm 4.2.15.1 to super d stable, but I cant seem to find one.
can someone advise me what to do so I dont brick my phone, and is it really worth moving to super d I hear its faster.
I am running cyanogen 4.2.15.1 H&E red I have the ra-dream 1.5.2 recovery, I have ext2 partition on sd card and I have a PVT board
Also I am worried about the ext2 partition because I have heard you have to remove it first and there is a certain way to do it??
Thanks in Advance
I was able to flash SuperD over Cyanogen without wiping or repartitioning. This is with an sdcard partitioned the usual way, fat32 and ext2.
The only issue I ran into was the battery meter - had to remove /data/system/batterystats.bin. Not sure of the exact procedure, so I did that from the recovery console and then booted up with a full charge.
Works great and really is a lot faster.
I would always wipe when moving from one rom to another. You never know what's could be hanging around.
I go thru this same process every time and never had problems:
1. Nandroid or Bart backup
2. Copy backup from SDcard to PC just in case SD card gets corrupted somehow
3. Wipe
4. Install new rom
5. Fix apk mismatch
6. Reboot
7. Check to see if Gapps are working, namely market, talk, sync, and of course google voice
nmw407 said:
I would always wipe when moving from one rom to another. You never know what's could be hanging around.
I go thru this same process every time and never had problems:
1. Nandroid or Bart backup
2. Copy backup from SDcard to PC just in case SD card gets corrupted somehow
3. Wipe
4. Install new rom
5. Fix apk mismatch
6. Reboot
7. Check to see if Gapps are working, namely market, talk, sync, and of course google voice
Click to expand...
Click to collapse
5. When you say "fix apk mismatch"....what do you mean?
7. I did the same thing (went from Cyanogen to SuperD) and I can boot into SuperD fine, but it won't connect to T-mobile's network and I am missing the Market. Any help?
shuboy00 said:
5. When you say "fix apk mismatch"....what do you mean?
Click to expand...
Click to collapse
It's an option in Amon_RA's recovery
shuboy00 said:
7. I did the same thing (went from Cyanogen to SuperD) and I can boot into SuperD fine, but it won't connect to T-mobile's network and I am missing the Market. Any help?
Click to expand...
Click to collapse
Wipe, Flash the DRC83_Base_Defrangled, the flash SuperD. Since both are legal, they need to pull the google apps from the base. And you would probably be fine without a wipe from SuperD to CM since they are similar donut builds. Wipes are recommended if you go from eclair to donut (and donut to eclair, elcair to sense, sense to dount.....). Cyanogen fixed it so you don't need to wipe as in the olden days...
mejorguille said:
It's an option in Amon_RA's recovery
Wipe, Flash the DRC83_Base_Defrangled, the flash SuperD. Since both are legal, they need to pull the google apps from the base. And you would probably be fine without a wipe from SuperD to CM since they are similar donut builds. Wipes are recommended if you go from eclair to donut (and donut to eclair, elcair to sense, sense to dount.....). Cyanogen fixed it so you don't need to wipe as in the olden days...
Click to expand...
Click to collapse
I see. So I am already running the DRC83_Base_Defrangled. Here is what I am doing:
I am currently running Cyanogen 4.1.99. My build number is DRC83. But my model number says "Android Dev Phone 1" <-- could that be why I don't have the Market in my roms?
So anyways this is what I do from Cyanogen 4.1.99: I backup, wipe, flash the DRC83, flash SuperD, then flash the 26I radio. Like I mentioned, rom boots up fine, just no market and no network access. Am I doing something wrong?
Absolutely no reason to flash the radio. The only thing that I can think of is that you have a bad download? Download this. Go to recovery, backup, flash the base, flash the rom. That should be all you have to do. Also, try CM 4.2.15.1 if SuperD isn't working for you. You are using a version of cyanogen about 4 months old and there have been 20 something releases since.
mejorguille said:
You are using a version of cyanogen about 4 months old and there have been 20 something releases since.
Click to expand...
Click to collapse
i believe he said that he is running latest cyan rom. try backing up your fat32 partition and reformat, that should do the trick
b0ricuaguerrero said:
i believe he said that he is running latest cyan rom. try backing up your fat32 partition and reformat, that should do the trick
Click to expand...
Click to collapse
I was referring to the poster above my post
mejorguille said:
Absolutely no reason to flash the radio. The only thing that I can think of is that you have a bad download? Download <removed>. Go to recovery, backup, flash the base, flash the rom. That should be all you have to do. Also, try CM 4.2.15.1 if SuperD isn't working for you. You are using a version of cyanogen about 4 months old and there have been 20 something releases since.
Click to expand...
Click to collapse
K. Did what you said. Downloaded the base you provided. Flashed. Then flashed the SuperD rom. Booted up. First I see is "!Sorry - The process com.google.process.gapps has stopped unexpectedly. Please try again." Still no network and still no Market. Urgh. Frustrating!!
Also, I tried CM 4.2.15.1 after the SuperD didn't work and it hung on the G1 screen. IDK why 4.1.99 works but not 4.2.15.1.
i guess it didnt hung, you just have to wait a bit longer.

What the hell...?!?!?

Hey All,
First I want to apologize if this isn't the place for this thread or if this has been brought up before.
Now onto what I came here for. I have a myTouch 3G phone (the one without the jack) and I have rooted my phone a couple of months ago. The rooting process went fine and currently I'm running the CyanongenMod 4.2.15.1 rom on my phone. It's running fine as it should be. Now my dilemma is when I tried to update to CM 5.0.7 or 5.0.8. At first when I flashed the rom, I thought everything was fine during the setup process but then when it came to using any Google apps, none of them seem to work with the exception of GTalk and Google Maps. I've tried the troubleshooting guide where it says to do the fix_permissions but that didn't work at all. After about 3 days of trial and error, I finally admitted defeat and flashed back to CM 4.2.15.1. I also came to the conclusion that my phone will only take 1.5 & 1.6 roms whereas any roms 2.0 and above will not work correctly. I even tried to flash CM 6.0 RC1 and it got stuck at the green boot screen.
My question is there something wrong with my phone or am I doing something wrong? Has anyone else ran into this problem? Please let me know because I would love to have the 2.0 and above roms on my phone.
Thanks in advance
Did you do a full wipe and then upgrade?
Yes I did a complete wipe, even did the command that you do in fastboot
u gotta install the google pack i think....for that u will find it in cyanogen forums
If you mean by installing the gapps after flashing the rom, I've done that already. Also I've even reflashed the gapps again just to make sure and I also tried the fix_permissions and that didn't work either.
I also saw that the browser was acting funny too (not sure if that's part of gapps)
Sent from my T-Mobile myTouch 3G using XDA App
Hello,
In your sign, you're using an old rom with the old method of app2sd (on /system/sdcard/), newer rom uses /sd-ext/ but 1.6.2 recovery is not compatible with the new method.
Not sure but try to update your recovery with 1.7.0.
Good luck, Scargoll.
scargoll, i failed to mention that I'm already using Amon Ra's 1.7G recovery image. I need to update my sig (my bad). also as i stated before, i tried upgrading to CM 5.0.8 and running into issues, that's why i'm still running CM 4.2.15.1
Yup. Wrong section. I'll move to General when I get back home.
Google Addon: FRF91-MDPI-2
Mirror: http://kanged.net/mi...91-3-signed.zip
EBI1 Port:
Download: http://briancrook.ca...ebi1-signed.zip
MD5Sum: 30f00833c6b9e15027603be4cbe415cc
Are those what you tried?
jeff, if i'm correct the FRF91 Google Addon is for the CM 6.0 RC1 rom and i don't have a MyTouch 3G 1.2 32A phone to be using the EBI1 port.
Well, since you say so, your phone is just jacked.
Have you tried reflashing the whole ROM and GAPPS again? See if a different version of cyanogenmod works for you.
jeffakajeff said:
Well, since you say so, your phone is just jacked.
Click to expand...
Click to collapse
LOL...jacked how?
appledroid said:
Have you tried reflashing the whole ROM and GAPPS again? See if a different version of cyanogenmod works for you.
Click to expand...
Click to collapse
appledroid, i've tried relashing both CM 5.0.7 and CM 5.0.8 roms gapps. the roms flashes fine but when it comes to using the gapps (with the exception of GTalk & Maps), they either close without a warning or i get a app loop (GMail does that most before it finally closes without warning)
sounds to like your running out of space on a partition while flashing. try fireat's mtd partition hack and see if it works for u.
flash the 1.1 zip
flash cm6
flash gapps
flash 1.2 zip
and then reboot
chrisgto4 said:
sounds to like your running out of space on a partition while flashing. try fireat's mtd partition hack and see if it works for u.
flash the 1.1 zip
flash cm6
flash gapps
flash 1.2 zip
and then reboot
Click to expand...
Click to collapse
hey chris,
running out of space on a partition - are you talking about the space on the phone or on the SD Card? if it's the SD Card, not sure how that's possible when I have 4GB card (also it's not partitioned as of now but before I did have it partitioned)
if i follow this route, do i need to flash CM 6 or can I flash CM 5.0.8?
also where can i find the 1.1 and 1.2 zip files?
in any case, i'll try both to see what's up
um does anyone know what chris is talking about?
c'mon....anyone?
hey im not to sure why u cant switch to the latest cm roms. cause mine is doing fine on every updates.
i use clockworkmod recovery
try redownloading the rom. while downloading, watch ur downloading progress bar, makesure u have good internet connection. do not let the data connection change speed( switching from 3g to e or g) do not let phone switch from portrait to landscape.
if any of the above does happen you will have to cancel current download then redownload.
try to download cm6 rc3 - its 2.2 and it have lots of goodies. gapps are also preinstall
well i had this problem too... i was stuck on green screen... setup abort... gapps was acting up... so i did the above and everything is fine...
i hope this works for
rooted mt3g 32b cm6-rc3 htcClay 1.3
forgot to mention... since u have this problem, i recommend a full wipe... i dont kno if it is ok to flash without wipe from cm4 to cm5 or 6... flashing rom over another rom is wat i normally do... cause i hate reinstalling apps
rooted mt3g cm6-rc3 htcClay 1.3

Missing Market in Cyanogen 6 w/ Update

I had recently flashed to Cyanogen 6.0.0 after buying my Aria and following the directions to root the device, backing it up, etc. However, upon booting into the new ROM, I was missing the Market icon (nowhere to be found!). I then went over to Liberated and had no issues, but missed some features from 2.2 source that Cyanogen is based off of. Therefore, I again flashed to 6 after a few weeks of using Liberated, and then applied the Cyanogen update, but still I'm missing the Market icon. What should I do??
Thanks in advance!
Did you wipe/factory reset before flashing?
Did you install the GAPPS package?
oahceasgnikgneas said:
Did you wipe/factory reset before flashing?
Did you install the GAPPS package?
Click to expand...
Click to collapse
Nevermind, JUST as I was posting this, I happened to go over the Wiki again and need to just install GAPPS.. sorry! Thanks again for the reply... at least this should pop up if other people happen to search this same issue...

Hey guys, i really need help here

I'm currently using the wildfire. I rooted it and installed rom manager.
I did backup my rom (CWRv3.2.0) and installed the wildpuzzle rom (Newest one).
But i think forgot to wipe off the data. After installing the rom, it booted fine but it says that my phone memory was low.
I waited for a very long time but it does not respond. Hence, i thought something was wrong and tried to go to cwr and did a factory reset.
But now it gives me a black screen after the htc logo.
And after 10 to20 minutes and it still does not respond. I went back and did a restore(before the wildpuzzle rom I've installed)and it came out that my phone cannot boot and stucked in a loop. (after 2 turns it went back to cwr)
I'm scared that i might bricked my phone.
Help please! Much appreciated!
When you do a Factory Reset in Clockworkmod, you need to flash a ROM again. Also, if you read the thread completely, WildPuzzle 2.3.2 does NOT work. It was released untested by danne (as he stated), and, various tests by users show it didnt boot.
EDIT: And if you are talking about Android 2.2 Sense ROM's, you will need to flash it using Clockworkmod 2.x. They are not supported on 3.x
So do i have to flash a new rom like CyanogenMod ? Sorry, I'm a complete noob at these. Edit: Its the Wildpuzzle 2.2 froyo v0.8 rom.
Clubbysupercharged said:
So do i have to flash a new rom like CyanogenMod ? Sorry, I'm a complete noob at these. Edit: Its the Wildpuzzle 2.2 froyo v0.8 rom.
Click to expand...
Click to collapse
Yeah flash the CyanogenMod 7 ROM. But before you install this ROM please make sure to Wipe the data, Clear cache partition and also to clear dalvik cache and then proceed to install the CM7 ROM
Yes! Thanks a lot! Flashed Cm7 Nightly Builds 2.3.4. Running perfectly
EDIT: Wifi does not connect lol, stucked on locating ip address.

[Q] Stuck on Google logo, can't access recovery mode

I've just tried upgrading to ICS and failed. Apparently I flashed the wrong kernel - should have flashed the CM7 one, but flashed the CM9.
Now my Defy is stuck on the Google logo and I don't know how to reach recovery mode. Pressing Power+voldown does nothing. Power+volup gives me the bootloader, which asks me to connect a usb cable, but I have no idea what to do after that.
I have two Nandroid backups: one stock (2.2) and another with CM7 (2.3.7). My Defy has a green lens.
Is there any way to restore my phone to one of those backups?
Thanks in advance
Do you still see the blue led for custom recovery?
Hmetool said:
I've just tried upgrading to ICS and failed. Apparently I flashed the wrong kernel - should have flashed the CM7 one, but flashed the CM9.
Now my Defy is stuck on the Google logo and I don't know how to reach recovery mode. Pressing Power+voldown does nothing. Power+volup gives me the bootloader, which asks me to connect a usb cable, but I have no idea what to do after that.
I have two Nandroid backups: one stock (2.2) and another with CM7 (2.3.7). My Defy has a green lens.
Is there any way to restore my phone to one of those backups?
Thanks in advance
Click to expand...
Click to collapse
You will need to flash a new SBF with RSD lite
follow instructions in this thread
How to flash new SBF
Hmetool said:
I've just tried upgrading to ICS and failed. Apparently I flashed the wrong kernel - should have flashed the CM7 one, but flashed the CM9.
Now my Defy is stuck on the Google logo and I don't know how to reach recovery mode. Pressing Power+voldown does nothing. Power+volup gives me the bootloader, which asks me to connect a usb cable, but I have no idea what to do after that.
I have two Nandroid backups: one stock (2.2) and another with CM7 (2.3.7). My Defy has a green lens.
Is there any way to restore my phone to one of those backups?
Thanks in advance
Click to expand...
Click to collapse
Do not flash any sbf's. Reboot the phone, at the blue led press Vol- and when you get into boot menu, flash the correct kernel. If you flashed Defy build, flash CM7 (Froyo) kernel. If you flashed the Defy+ build, flash CM9 (Bingerbread) kernel.
fiskenigaten said:
Do you still see the blue led for custom recovery?
Click to expand...
Click to collapse
I see the blue led, but it goes on to green regardless of what I do (power+voldown does nothing). I've tried to access recovery mode several times, but the phone doesn't respond. Maybe I'm doing something wrong.
rperdue5 said:
You will need to flash a new SBF with RSD lite
follow instructions in this thread
How to flash new SBF
Click to expand...
Click to collapse
I've read the guide, but my original SBF is missing ever since MegaUpload's demise. Is it possible to use the Nandroid backup instead?
Auris 1.6 vvt-i said:
Do not flash any sbf's. Reboot the phone, at the blue led press Vol- and when you get into boot menu, flash the correct kernel. If you flashed Defy build, flash CM7 (Froyo) kernel. If you flashed the Defy+ build, flash CM9 (Bingerbread) kernel.
Click to expand...
Click to collapse
Ok, apparently I wasn't pressing the button at the right time. Recovery mode is now working. However, I don't have the correct kernel in my SD card - only the wrong one.
My Nandroid backup seems not to be working too, apparently. I went into recovery and restored it, but boot still doesn't work. I wiped data/cache/dalvik cache and tried again, but it still didn't work. I'm at a loss here.
Should I try to flash some other sbf, since I can't find my phone's stock one?
Hmetool said:
Ok, apparently I wasn't pressing the button at the right time. Recovery mode is now working. However, I don't have the correct kernel in my SD card - only the wrong one.
My Nandroid backup seems not to be working too, apparently. I went into recovery and restored it, but boot still doesn't work. I wiped data/cache/dalvik cache and tried again, but it still didn't work. I'm at a loss here.
Should I try to flash some other sbf, since I can't find my phone's stock one?
Click to expand...
Click to collapse
go to ICS thread and on the first post there is a link to signed CM7 kernel zip..copy it to ur sd card and flash it..
arpith.fbi said:
go to ICS thread and on the first post there is a link to signed CM7 kernel zip..copy it to ur sd card and flash it..
Click to expand...
Click to collapse
I just tried installing the zip from the sdcard, but I got an error message: "Can't make /tmp/update_binary. Installation aborted". It seems that I can't install any zip now.
Is there any way out of that? I'd be more than happy if I could just flash my nandroid backup, even if that means being stuck without ICS for a bit more time.
I'm on ClockworkMod Recovery v2.5.1.8, if that helps.
Hmetool said:
I just tried installing the zip from the sdcard, but I got an error message: "Can't make /tmp/update_binary. Installation aborted". It seems that I can't install any zip now.
Is there any way out of that? I'd be more than happy if I could just flash my nandroid backup, even if that means being stuck without ICS for a bit more time.
I'm on ClockworkMod Recovery v2.5.1.8, if that helps.
Click to expand...
Click to collapse
Hi,
I faced a similar issue but it was since I flashed CM9 for Defy in my Defy+ with 2.3.6(stock) ! Nothing was working and I would get some boot errors! I rectified it by flashing full SBF and then rooting. Well if you want I can provide you with the SBF I have but it is for 2.3.6 and so you will loose downgradability. I have 4.5.1-134-DFP-1321 - retail-asia full Blur multilanguage with me. However, you can also give Walter's fixed SBF and Nandroid backup a try
Thanks, it turns out that flashing a sbf was a nice way out of this mess. I flashed a 2.2.2 which is almost identical to my stock rom (couldn't find that one).
If I root my phone now, can I still try to restore my nandroid backup? Or should I just skip that and try flashing ICS again?
My SD card has the 03-19 CM9 Nightly, gapps and both CM9 and CM7 signed kernels. Should that suffice? CM7 kernel is the right one for green lens defy, right?
Hmetool said:
Thanks, it turns out that flashing a sbf was a nice way out of this mess. I flashed a 2.2.2 which is almost identical to my stock rom (couldn't find that one).
If I root my phone now, can I still try to restore my nandroid backup? Or should I just skip that and try flashing ICS again?
My SD card has the 03-19 CM9 Nightly, gapps and both CM9 and CM7 signed kernels. Should that suffice? CM7 kernel is the right one for green lens defy, right?
Click to expand...
Click to collapse
If you are on a green lensed Defy, then yes - flash CM7 signed kernel and one of the Froyo bulds of Quarx or Epsylon3 - try them all if you wish and see which one you like the most.
Procedure is easy:
1. Full wipe
2. Flash CM7 kernel
3. Flash ROM
4. Flash gapps
5. Full Wipe
6. Reboot
When you decide to try a new ROM, there is no need to flash the kernel again, just wipe, flash the new ROM and gapps and then wipe again.
Auris 1.6 vvt-i said:
If you are on a green lensed Defy, then yes - flash CM7 signed kernel and one of the Froyo bulds of Quarx or Epsylon3 - try them all if you wish and see which one you like the most.
Procedure is easy:
1. Full wipe
2. Flash CM7 kernel
3. Flash ROM
4. Flash gapps
5. Full Wipe
6. Reboot
When you decide to try a new ROM, there is no need to flash the kernel again, just wipe, flash the new ROM and gapps and then wipe again.
Click to expand...
Click to collapse
Thanks, that's great. Are all regular Defy roms Froyo builds unless stated otherwise? I couldn't find that info on the files I have.
One question: by full wipe you mean data/cache/dalvik cache or is there anything else that I'm missing?
Hmetool said:
Thanks, that's great. Are all regular Defy roms Froyo builds unless stated otherwise? I couldn't find that info on the files I have.
Click to expand...
Click to collapse
Yes, "Defy build" means Froyo kernel based, "Defy+ build" means GB kernel based.
Hmetool said:
One question: by full wipe you mean data/cache/dalvik cache
Click to expand...
Click to collapse
Exactly.
Auris 1.6 vvt-i said:
Yes, "Defy build" means Froyo kernel based, "Defy+ build" means GB kernel based.
Exactly.
Click to expand...
Click to collapse
Yep, that's exactly what it is..
I've just rooted my phone again, followed the steps and installed CM9. It worked like a charm. I was pleasantly surprised at how smoothly it runs, didn't expect that sort of quality from a Nightly. Awesome.
Thanks a lot for saving my phone, guys.
Hmetool said:
I've just rooted my phone again, followed the steps and installed CM9. It worked like a charm. I was pleasantly surprised at how smoothly it runs, didn't expect that sort of quality from a Nightly. Awesome.
Thanks a lot for saving my phone, guys.
Click to expand...
Click to collapse
Sounds great Well since CM9 nightly is still a long way to go, you may want to dual boot CM7 and CM9. Install CM7 as primary and dual boot to CM9.
Guide: http://forum.xda-developers.com/showthread.php?t=1375156
i did the same thing on my defy im a noob and need alor of help.
Ok so i had a motorola defy and i wanted to update it to cyanogenmod 7 but it must have been the wrong one and now its stuck on google boot i can't get to my custom recovery screen by pressing volume - and power buttons and if i press volume + i get this black screen asking to plug in the usb to the laptop which i did but i don't know what to do now. i need complete instructions! , iv checked ALOT of forums and tried following this ones instructions, but RSD lite wont download and install like it said it would . and i have no idea how to get tmobile android 2.2 OS for motorola defy. if i could just get that back i would be more then forever greatfull . please someone HELP ! please all be forever in debt to whoever can help me.
blackhack516 said:
Ok so i had a motorola defy and i wanted to update it to cyanogenmod 7 but it must have been the wrong one and now its stuck on google boot i can't get to my custom recovery screen by pressing volume - and power buttons and if i press volume + i get this black screen asking to plug in the usb to the laptop which i did but i don't know what to do now. i need complete instructions! , iv checked ALOT of forums and tried following this ones instructions, but RSD lite wont download and install like it said it would . and i have no idea how to get tmobile android 2.2 OS for motorola defy. if i could just get that back i would be more then forever greatfull . please someone HELP ! please all be forever in debt to whoever can help me.
Click to expand...
Click to collapse
Try running three setup as administrator. Read all in defy guide. Check the wiki for more guides.
Sent from my MB525 using XDA
do u have a link?
labsin said:
Try running three setup as administrator. Read all in defy guide. Check the wiki for more guides.
Sent from my MB525 using XDA
Click to expand...
Click to collapse
do u have a link

Categories

Resources