Related
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.
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
Hi Guys, New CWM 3.0 is available now from the ROM manager.
Im on sense rom.. will it bckup n restore sense rom or it is for 2.3 roms only?
Sent from my Desire HD using XDA App
override182 said:
Im on sense rom.. will it bckup n restore sense rom or it is for 2.3 roms only?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
You can find All Versions of Clockwork Mod Recoveries in ROM Manager. So if you having any problems with old Roms you can use CWM 2.5.
CWM 3 doesn't support update-script, it requires update-binary and updater-script. So there are many mods and themes available which will not work with CWM 3.0. If you know how to convert them into flashable Zips then you will be able to use it. But anyway you can always revert back to CWM 2.5.
Does nandroid backups made with CWM 2.5 work with this new version?
Restoring backups of 2.2 roms doesn't work for me. Only way I can get a 2.2 rom to boot is if I flash a fresh zip
jontelfer said:
Restoring backups of 2.2 roms doesn't work for me. Only way I can get a 2.2 rom to boot is if I flash a fresh zip
Click to expand...
Click to collapse
Just use CWM 2.5 to restore backup of 2.2 Roms. It should be working fine, I tried on my DHD and I don't have any issues.
Awesome! Makes things easier when I want to flash CM7.
I was so glad to see this. I had the non-final version installed and it meant if I wanted to go back to Sense I had flash the 2.5.1.3 recovery first. Now with this being on the ROM manager I flashed the 2.5.1.3 then recovered Sense, flashed v3 recovery and backed up Sense. With that done I can go between it and CM7 or any other ROMs that allow far more easily.
Dyonas said:
I was so glad to see this. I had the non-final version installed and it meant if I wanted to go back to Sense I had flash the 2.5.1.3 recovery first. Now with this being on the ROM manager I flashed the 2.5.1.3 then recovered Sense, flashed v3 recovery and backed up Sense. With that done I can go between it and CM7 or any other ROMs that allow far more easily.
Click to expand...
Click to collapse
True.. Makes my life more easier...
It would have beign nice if I knew this stuff about v3 yesterday...when I couldn't get back any recovery, and I was beginning to believe that is something wrong.with my SD card. But I don,t understand ,why, if is a NEW (and supposedly a better version) doesn't, support the back up made with v2.5 (I read about the .bin, and .zip file in a.upper post, but It's a little to technically for me and I dont understand how this will help me if I use CM7 and ruu 2.3).
And the question is, will v3 recover the backup made with v3 of my sense Rom,because I don,t wanna try again and if it.doesn't,t work ,I will wake up my self again in the orange menu of v3 and then I have to flash again a Rom, downgrade from Rom manager to v2.5 and restore an older backup
Neat!
CM7 official release is probably not to far away then!
Thanks...!
Argh, really, is it so hard to check for the fs during backup, and then restore it using the noted fs? Why the stupid split for ext3 on 2.5 and ext4 on 3 ? Especially since 3 has no problem reading ext3.
movikun said:
Argh, really, is it so hard to check for the fs during backup, and then restore it using the noted fs? Why the stupid split for ext3 on 2.5 and ext4 on 3 ? Especially since 3 has no problem reading ext3.
Click to expand...
Click to collapse
Obviously Koush feels it is, don't forget CWM is open source, if you feel the check of file system and appropriate restore / backup is a minor issue submit a patch implementing it for review and I am sure Koush will accept it with pleasure.
re flashed today everything is nice. Except one backup from older CWM is not recognized.
Thanks for the heads-up
Anyone knows if it'll get the right google apps as well?
gapps-gb-20110120-signed.zip
thats the latest for DHD if i am not mistaken. Will checking
the google apps box get that?
TheLawyer said:
Anyone knows if it'll get the right google apps as well?
gapps-gb-20110120-signed.zip
thats the latest for DHD if i am not mistaken. Will checking
the google apps box get that?
Click to expand...
Click to collapse
You can check available google apps on here http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps
I was using MIUI rom on my DHD and I wanted to restore a nandroid backup to return to Revolution HD, when I started Rom Manager, it told me there's an update to 3.0.x (Not 100% if it was 3.0.5 or something else), so I updated it.
Then when I tried to do a nandroid restore to my RevolutionHD backup, it went through the process properly, but it won't boot into the rom.
Can anyone help me out, please. I'm phoneless?
KDR1245 said:
I was using MIUI rom on my DHD and I wanted to restore a nandroid backup to return to Revolution HD, when I started Rom Manager, it told me there's an update to 3.0.x (Not 100% if it was 3.0.5 or something else), so I updated it.
Then when I tried to do a nandroid restore to my RevolutionHD backup, it went through the process properly, but it won't boot into the rom.
Can anyone help me out, please. I'm phoneless?
Click to expand...
Click to collapse
flash cwm 2.5.x from fastboot and reflash revolution
a few months ago i rooted and installed clockworkmod v2.5.1.0 and installed a rom on my phone, everything went smoothly until a few days ago i wanted to try another rom, so i backup my phone on clockworkmod and do what i remember i had to do, and installed the new rom, but my phone just stayed in the turning on logo, right now i cant use my phone or restore my old rom and i keep getting E:can't open /cache/recovery/log
after pretty much any command i try. i need urgent help so i can use my phone!
I'm no expert or anything but I believe if you were using clockworkmod 2.5 you are running rfs (I believe it is) and you were trying to install a new rom which most likely is ext4 which is what caused the boot loop. So to make it eaiser to understand you tried to flash a newer rom on clockwork mod 2.5 when you needed clockwork mod 3.0+ (ext4 enabled). So now your going to have to use odin and go back to a stock of your choice ec05 I would say.
Check the wiki in android development and see what you need to go back to stock with odin, that will help
Sent from my SPH-D700 using XDA Premium App
Promni said:
a few months ago i rooted and installed clockworkmod v2.5.1.0 and installed a rom on my phone, everything went smoothly until a few days ago i wanted to try another rom, so i backup my phone on clockworkmod and do what i remember i had to do, and installed the new rom, but my phone just stayed in the turning on logo, right now i cant use my phone or restore my old rom and i keep getting E:can't open /cache/recovery/log
after pretty much any command i try. i need urgent help so i can use my phone!
Click to expand...
Click to collapse
Yes, you need to Odin back to stock. There are stickies on top of the forums on how to fix a bricked epic, restore stock. My guess is you tried a ROM that required EXT4 file system. If you still wish to try these ROMs there is a sticky at top of Development for installing Clockwork Mod 3.0.0.6.
Do you BONSAI?
I'd agree. The kernel probably is what broke that down, with the ext4. Flash CWM3, make sure you have the correct modem for that ROM, and try reflashing the ROM. sometimes (SOMETIMES) that works, without having to ODIN back. I was on leaky gingerbread with ed12, which doesn't (yet) support ext4 / CWM3, i flashed the ec05 modem back in, flashed cwm3, and reflashed the SyndicateROM Frozen - without having to ODIN the stock- worked perfectly.
This may work for you-
Flash modem needed for ROM
Install CWM3
Reinstall <rom>.zip through CWM3.
there is one problem, my pc wont recognize my phone.
Ok i got it running again, thx everybody!
Promni said:
there is one problem, my pc wont recognize my phone.
Click to expand...
Click to collapse
If you can, try using a different cable. Lot of people have had this issue using the stock one.
is it possible to switch from cm7 to ics? i just rooted my nook color to run cm7 and now i want it to run ics. if there's a way to instal ics over cm7 could someone please give me instructions on how to do it please and thanks.
KushGod said:
is it possible to switch from cm7 to ics? i just rooted my nook color to run cm7 and now i want it to run ics. if there's a way to instal ics over cm7 could someone please give me instructions on how to do it please and thanks.
Click to expand...
Click to collapse
Check in Android Development the topics for double boot guide.
You could make an Sd card with both CM7 and CM9 and select which to boot every time.
For me, it doesn't worth to pass totally to CM9 as its not full stable.
Unleashed from my Nook Color at 1.2G
KushGod said:
is it possible to switch from cm7 to ics? i just rooted my nook color to run cm7 and now i want it to run ics. if there's a way to instal ics over cm7 could someone please give me instructions on how to do it please and thanks.
Click to expand...
Click to collapse
If you decide to do this, make a dual boot. I'm 100% certain you'll want to go back to CM7 after you try the CM9 kangs...
If you have CM7 on the emmc (internal) you can flash the update just like any other update eyballer has a thread about the process. On SD the verygreen install script might not have enough room in the boot partition for the CM9 nightly.
Sent from my NookColor using XDA
wmuflyer said:
If you have CM7 on the emmc (internal) you can flash the update just like any other update eyballer has a thread about the process. On SD the verygreen install script might not have enough room in the boot partition for the CM9 nightly.
Sent from my NookColor using XDA
Click to expand...
Click to collapse
Cm9 its not an update of cm7.
He will have to first wipe everything before the change to Cm9.
Unleashed from my Revolutionized Desire HD
RASTAVIPER said:
Cm9 its not an update of cm7.
He will have to first wipe everything before the change to Cm9.
Click to expand...
Click to collapse
Not true, you can install a CM9 nightly over a CM7 system. Most settings stick, but some apps won't work right under any version of ICS.
I believe Viper is correct. Can't just update CM7 to CM9 since they are totally different OS, and even worse, entire different kernels.
On SD the verygreen install script might not have enough room in the boot partition for the CM9 nightly.
Click to expand...
Click to collapse
Get the "modified" verygreen image, made by leapilar, it should be able to handle both CM7 and CM9.
votinh said:
I believe Viper is correct. Can't just update CM7 to CM9 since they are totally different OS, and even worse, entire different kernels.
Get the "modified" verygreen image, made by leapinlar, it should be able to handle both CM7 and CM9.
Click to expand...
Click to collapse
Stolenmoment is correct. You really don't have to wipe data. Many people have done it without wiping first and had no problems. But it is probably a good idea to wipe anyway, just to be sure. Backup your installed apps with Titanium Backup and restore them later.
The cm9 install zip does not back up the cm7 gapps since they are the wrong version. Then it formats /system so it starts clean before it installs itself there. And it replaces the cm7 kernel with its own. So the only risk you are taking by not wiping data first is the old system settings are still there in /data and may not play well with the new cm9 system apps. But they almost always do ok. If they don't, wipe later.
leapinlar said:
Stolenmoment is correct. You really don't have to wipe data. Many people have done it without wiping first and had no problems. But it is probably a good idea to wipe anyway, just to be sure. Backup your installed apps with Titanium Backup and restore them later.
The cm9 install zip does not back up the cm7 gapps since they are the wrong version. Then it formats /system so it starts clean before it installs itself there. And it replaces the cm7 kernel with its own. So the only risk you are taking by not wiping data first is the old system settings are still there in /data and may not play well with the new cm9 system apps. But they almost always do ok. If they don't, wipe later.
Click to expand...
Click to collapse
So, we are saying the same thing.
Just that Wipe is not needed to be performed by user, cause install of Cm9 formats anyway the system.
But settings from previous system should be cleaned in order to be sure that new system will work fine.
Unleashed from my Nook Color at 1.2G
leapinlar said:
Stolenmoment is correct. You really don't have to wipe data. Many people have done it without wiping first and had no problems. But it is probably a good idea to wipe anyway, just to be sure. Backup your installed apps with Titanium Backup and restore them later.
The cm9 install zip does not back up the cm7 gapps since they are the wrong version. Then it formats /system so it starts clean before it installs itself there. And it replaces the cm7 kernel with its own. So the only risk you are taking by not wiping data first is the old system settings are still there in /data and may not play well with the new cm9 system apps. But they almost always do ok. If they don't, wipe later.
Click to expand...
Click to collapse
Entire different OS and kernels, I don't believe we can say "CM9 is an update of CM7". They are 2 different things. Do you agree?
votinh said:
Entire different OS and kernels, I don't believe we can say "CM9 is an update of CM7". They are 2 different things. Do you agree?
Click to expand...
Click to collapse
Yes, I agree they are different. And I never said 'CM9 is an update of CM7'. But it still does not change what I said above.
I've flashed a CM9 update straight over CM7 twice by accident (I'm always shuffling backups and rearranging things on my internal dual boot). The first time I was plagued with FCs, including Market/Play, but the second time everything worked just fine. My apps, launcher and homescreens were all just as I'd left them, but ICSed. With CM7 already running on my other partition set, though, I decided I'd rather build the CM9 side from scratch, so I wiped it.
I've been using CM9 nightlies as my daily driver for a couple months, and it's not as stable or fully featured as CM7. My main reason for sticking with CM9 despite performance issues is I love the ICS Google Apps, and most of the time I find my touch response is better (though that may be due to my running Nook Screen Recalibrate at various times on CM7), especially in Mantano Reader which is usually my biggest use for the NC.
I might have trouble using CM9 as my daily driver if I didn't have CM7 a reboot away, though, and I have had to make the switch on the fly more than once.
You can check out my dual boot guide in my sig, but it's one of the more involved things you can do with the NC (short of rolling your own ROM ).