Database Users

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.

**Rooted Phones*** Reset back to First Time Root

Ok apparently in my futile attempts to OC the Pure Hero 1.0 Rom I've totaly got something hosed up. The phone works but features that others have working flake out on me. Is there a way to wipe fully the whole thing and reset back to the rooted 2.1 Rom as we did before the Recovery image.
If it is as simple as just flashing the original developers Rom please don't flame me..I did search.
I do a factory wipe then Dalvik Wipe then Ext Partition wipe before flashing an image.
I currently can't get Wifi to work on Punk.Kaos Rom nor on the Pure Hero (I think that was an issues though)..
Thanks for all the hard work you guys do....

copy a rom you want to use to your sdcard. then go into recovery, wipe the phone, then flash zip from sdcard. done!

That is what I have been doing and some of the settings are still flaking out and the Kaos rom is V15 he fixed wifi in v2. I can't even get Jamezelle's sensable rom to even flash with out a boot loop at animation.
Thanks for the help.

No nandroid backup?? I know before flashing the first Rom on the phone I made a nandroid back up on my wifes and pretty much do everytime before flashing a new rom. These things are priceless

Follow the the original root procedure.

*Suggestion*, when phone boots.... open setcpu and adjust the CPU OC setting.... maybe...

id say go to the downgrade to 1.5 from 2.1 root thread and do that and then re upgrade and reinstall the recovery image.

I agree with doing a full downgrade to 1.5 and rooting again. I had problems similar to yours and this solved the problem. Good luck.
-------------------------------------
Sent via the XDA Tapatalk App

Thanks I just wanted to confirm that should be the process of going to 1.5 thne to 2.1 and restoring the Recovery. One last question and then a Mod can close this thread. The Rom Manager in the Market will that work for us or is that a Droid only thing?
Thanks for the great advice.
Forgot to answer the nandroid backup yes did it before every new flash of a Rom they would come back weird also. Secondly how do I get my SD card back to full Fat32 and not the ext+Fat partition for A2SD mode? I never could get the A2SD to work fully.

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

CM 6.1 Stable

Hey, question. Every single CM from 6.0 I have downloaded I have had issues with. I love the rom, but every time I get the same issue. When I install the rom all worked fine. I wipe all data, clear cache, and have to reinstall of course everything, my issue is that my phone will randomly freeze. Sometimes I get an error message saying the process process.android has failed, other times it just freezes. Does anybody have any ideas?

I loved CM 6.1 best Rom I've had yet. But after a week it started acting up and having problematic auto shutdowns like 8 times a day. I then searched for another stock Rom and tried skyraider vanilla, I hate it. It's basically skinned sense. That's it. I enjoy sense but it eats battery. My favorite roms so far are the desire Hd Rom and
CM but without the shutdowns is be perfect.
Sent from my ADR6300 using XDA App

only people
So this is the only other person I have run into with this problem. Everybody else I have talked to over other forums or IRC has never heard of these issues at all.

The only time I've ever had those shut down issues is when I start screwing with themes or when I start screwing with kernels or overclocking. I'm not sure what you've got going on there though

Well...
Well I have done some of that however I have reverted to "stock" several times. I have Hboot .92 installed also, i saw something online. The latest radio is also installed. I guess has anybody else seen any issues like this?

Try formatting the system in addition to wiping. CM does not format anything when you flash it. In CWM its under mount sd section.
Sent from my Htc Incredible using XDA App

This happened to me today, I am 99% sure it was the kernel I had installed though. I put back invisiblek's #18 and had no problems before or after.

okay I can mess around with that and see what happens then.

justinmburrous said:
okay I can mess around with that and see what happens then.
Click to expand...
Click to collapse
Let us know please.

This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!

neur0tk said:
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
Click to expand...
Click to collapse
You need to be a little more specific but do this.
1. Click on the Cyanogen link in my signature and download it.
2. Download google apps
3. Reboot into recovery
4. Wipe Data/Factory Reset
5. Wipe Cache Partition
6. Wipe Dalvik Cache
7. Select install zip from SD card and choose the cyanogen ROM, let it install
8. Select install zip from SD card again and choose the google apps.
9. Reboot your phone and sign into your google account and let everything sync
This is the best way to do it. Not through ROM Manager.
If this doesn't work then I have absolutely no idea. That is the 100% correct way to flash a ROM.

neur0tk said:
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
Click to expand...
Click to collapse
I had to revert back to #18 kernel working fine now!

neur0tk said:
I had to revert back to #18 kernel working fine now!
Click to expand...
Click to collapse
Yeah I mentioned it earlier in this thread. For some reason #21 and #22 do not like cyanogen.

I'm running #21 on my phone and I haven't had any issues yet.

Yeah IDK either... I had to revert now it's running like a champ! love the Inexus theme!

ok an update, I have everything working. I an using cm6.1, latest radio (on cm site), kernel 27, hoot .92, and the very latest clockwork that just came out. I know those last two should not matter, just letting you know. As of right now my phone is not freezing and everything works fine, even faster than before. When I first turned it on the phone did freezer and after that yet took a long time for 3g to start working. On reinstall I did a total revert to stock then did a factory reset and cleared all caches and everything on the phone there is to clear. It has been afew hours. I will update this if there are any more problems
Sent from my ADR6300 using Tapatalk

Keeps rebooting more and more time to switch roms
Justinmburrous
Justinmburrous.com

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

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