Related
I bought a g1 off of craigslist and it already had root. JF 1.4 ....
Around the time cupcake was released I updated it to jf 1.51
Now since there will be no more JF updates I wish to switch to Cyan builds.
I'm unsure of the proper way of doing this?
Should I go back stock .. unroot and then go thru the steps to load cyan?
Or is there a better way? A wipe?
I'm asking to be clear because internet access is strictly from my g1.
Although I can download all the files I need, I do not have constant access.
I'd appreciate any tips or pointing me to the proper thread.
Check the threads in Dream >Dream Android Development look for Cyanogen's thread on his release of 4.1.999, follow the instructions and you will be fine. I'd also suggest at least flashing Cyanogen's v1.4 Recovery Image over JF's, easier to flash any .zip on sdcard. So, new recovery image (use search option in forums, or look in the same thread i mentioned for cyanogen recovery image 1.4) then update to cyanogen's latest rom build
So simply flash a new recovery, then follow the cyan steps?
Cool, easy as pie.
I certainly appreciate it.
Thank you
Yup. just be careful that you dont boot off the htc recovery rom, or the steps to get to cyans rom become much, much harder
B-man007 said:
Yup. just be careful that you dont boot off the htc recovery rom, or the steps to get to cyans rom become much, much harder
Click to expand...
Click to collapse
that is why there is a full update made for it.
haha o right i forgot about that one... no one asked questions about a bad all-in-one flash, only those who messed up while flashing the htc rom
i need sleep lol
B-man007 said:
haha o right i forgot about that one... no one asked questions about a bad all-in-one flash, only those who messed up while flashing the htc rom
i need sleep lol
Click to expand...
Click to collapse
sleep is for the weak. also it is really hard to flash two things while in recovery it causes hemorrhoids and anal fissures.
haha trust me...someone somewhere will make something incredibly easy look like rocketscience
B-man007 said:
haha trust me...someone somewhere will make something incredibly easy look like rocketscience
Click to expand...
Click to collapse
you mean rocketsurgery
david1171 said:
you mean rocketsurgery
Click to expand...
Click to collapse
*sigh*
yes its true.
B-man007 said:
*sigh*
yes its true.
Click to expand...
Click to collapse
lmao me went to smart person learning place
I'd like to chime in here as well since I'm having such a hard time searching for info on the conversion from jf1.51 to the latest build of CM. The amount of posts are staggering!
So, I vaguely remember setting up apps2sd following the guide at the bottom of this page - http://yokohead.com/2009/06/how-to-root-android-g1-with-cupcake-and-appstosd/
Will CM automatically detect this partition?
Also, will I lose the google experience? I'm still confused as to where we are on that.
Thanks for your time! If anyone knows an updated post on this process, please point me to it.
TJ
Well the sticky by fingerlickin at the top of this section is a good place to start....
all you have to do is find the singleflash update in the dev section, backup and clear everything off your ext3, and wipe+flash the single update. you can restore the ext backup then.
also you should upgrade to cyan 1.4 recovery
to do so
su
cd /sdcard
wget http://n0rp.chemlab.org/android/cm-recovery-1.4.img
flash_image recovery /sdcard/cm-recovery-1.4.img
Click to expand...
Click to collapse
you wont lose the google experience
Thanks B-Man007,
After a couple attempts, all is working well. I'm thoroughly impressed with the snappiness of this build. Although it's only my second time updating a ROM, I'm going to blame the amount of posts for my hesitation and confusion. It was easy to just go in and do it.
I actually updated to the latest Amon-Ra(sp?) recovery. At first my Rom was running real slow and the recovery allowed me to update my ext2 to ext3. Loving it now!
The amount of posts does make it quite confusing i agree, especially with the high amount of conflicting posts
Ya ext3 is a must, but you could have upgraded from cyans too haha
cyan usually has the fastest builds out there though at times it can get very slow.
Another noob here. A few months ago I rooted and flashed to xrom 1.5. When I do a reboot, my recovery screen tells me its "CyanogenMod v1.4 + JF".
Since xRom is experiencing some problems w/ updates, I figured I might try the latest build of Cyanogen. I re-booted, went to recovery mode. Wiped. Then flashed the latest Cyan and even found the 1.6 ota on another site. Flashed both zips, then did a re-boot and it hangs now.
I tried it over and over a few times, wiping then flashing again. Wiping, then re-booting, then flashing the rom, etc. Over and over with the same results.
Then as a test, I tried flashing back to xRom... perfectly fine.
As another test, I tried wiping and flashing to another rom, the rooted stock option (the HTC rom version)... and got the same results as when I tried Cyan... just hangs.
Wiped and flashed again back to xRom... works fine.
So at this point, I'm thinking I need a more updated recovery rom? Any other possible problems? Yes, I did a search all over and this was the best thread that matched my problem.
If it helps... I have a T-mo G1, firmware 1.5, JACxROMv1.5, kernel version 2.6.29.6-jac-ski root. And I know many will slap their foreheads when I say this: But the SD is NOT partioned at all (kept trying and trying with zero success, so I eventually gave up).
Can this new recovery be used to flash CyanogenMod 6.1.1??? I just got the new recovery update on rom manager and was going to flash cyanogenmod 6.1.1 and just checking. I thought the new recovery was for flashing Gingerbread roms?? Any help would be appreciated.
Thanks,
Vinny
I don't see why not. You can try and if it don't work you can flash an older version in ROM Manager
vinnyjr said:
Can this new recovery be used to flash CyanogenMod 6.1.1??? I just got the new recovery update on rom manager and was going to flash cyanogenmod 6.1.1 and just checking. I thought the new recovery was for flashing Gingerbread roms?? Any help would be appreciated.
Thanks,
Vinny
Click to expand...
Click to collapse
I am not sure about that. But one thing for sure is it is not good for MM's CM7. I have loop-reboot problem with this. I cannot even restore to any custom roms except my froyo stock. :-( Now, I have to downgrade to 2.5.x.x to see if my custom roms work again.
See development section.
EDIT: I successfully restore other custom roms using lower version of Clockworkmod. But the loop-reboot problem of MM's CM7 remains the same.
I guess I won't find out until I try. Newly rooted and going to give CyanogenMod a try. Know I am going to be happy as hell with it.
Thanks
The new recovery should be fine with flashing any roms. As for any standing problems with it, im am uncertain. You may want to wait 2 weeks or so to see if their are any problems from people using it. Personally I like Amon ra so i cant say.
ricky9237 said:
I am not sure about that. But one thing for sure is it is not good for MM's CM7. I have loop-reboot problem with this. I cannot even restore to any custom roms except my froyo stock. :-( Now, I have to downgrade to 2.5.x.x to see if my custom roms work again.
See development section.
Click to expand...
Click to collapse
A full wipe is necessary to upgrade to gingerbread roms from any lower android versions. Did u full wipe? + Dalvik cache wipe?
mikeacela said:
A full wipe is necessary to upgrade to gingerbread roms from any lower android versions. Did u full wipe? + Dalvik cache wipe?
Click to expand...
Click to collapse
Yes. I did full wipe on everything. I even fix permission. No luck at all.
ricky9237 said:
I am not sure about that. But one thing for sure is it is not good for MM's CM7. I have loop-reboot problem with this. I cannot even restore to any custom roms except my froyo stock. :-( Now, I have to downgrade to 2.5.x.x to see if my custom roms work again.
See development section.
EDIT: I successfully restore other custom roms using lower version of Clockworkmod. But the loop-reboot problem of MM's CM7 remains the same.
Click to expand...
Click to collapse
I used it to flash and install tonight's build successfully...
I have a "side question".
To flash any GingerBread flavor, do we need 3.x.x.x ou 2.5.x.x is working?
I haven't give CM7 a try yet, but I'm not sure if I need/want to upgrade to 3.x.x.x, 2.5.1.4 work well for me.
DumbUglyDragon said:
I used it to flash and install tonight's build successfully...
Click to expand...
Click to collapse
I got it too. No more crazy rebooting. I solve it by reformatting my SD card and recreating ext3. I guess 3.0.0.5 recovery messed up my ext3 partition. Now, MM CM14 is working pretty well. FYI, I am using 2.5.1.4 recovery.
Yeah it was working good till I try to do a restore, lets just say I;m up all night trying to restore my phone. I think my EXT partition messed up too as DTa2sd is giving me all kinda of headache.
doesn't work with MIUI for me!
don't understand that, but luckily its not a big deal flashing older versions!
baseballfanz said:
Yeah it was working good till I try to do a restore, lets just say I;m up all night trying to restore my phone. I think my EXT partition messed up too as DTa2sd is giving me all kinda of headache.
Click to expand...
Click to collapse
I hear you there! That was me last night! DON'T USE 3.0.0.5! The only fix I found to actually work was to completely format my SD card and then re-partition it, then use RA and a fresh install. What a pain in the arse!
Same thing here. Switched to 3.0.0.5, and the next thing, my ext was fried and I had to reformat the entire card. Could be coincidence, but...
Sent from my Nexus One using XDA App
So, currently I run Firerat's script on CM 6.1 and have quite a few apps on EXT3. I know there's a few ROMS that have the nightly CM7's (not RC1) running a different A2SDEXT script.
Basically, I want to know what I'd have to do to upgrade to CM7, and not have anything happen to the apps I've got on EXT. If I wind up running a different ROM with a different script, would it still pick up the EXT stuff? Has anyone tried something like this before? I'd hate to reinstall ****-tons of apps but I guess if I've got to, then I've got to. I'm a huge n00b on these A2SDEXT scripts, so excuse my n00berosity
Backup your apps with Titanium, and do a full wipe.
Install ROM and your a2sd, and then restore your apps with Titanium, and they will restore to ext...
Sent from my Nexus One using XDA App
Also make sure you aren't using clockwork mod 3.0.0.5. There is a chance it will screw up your ext. you can downgrade to the older one in rom manager.
Not saying it will definitely, but if you do get problems, they can be difficult, you may be as unlucky as me http://forum.xda-developers.com/showthread.php?t=958057
Hi All,
Just joined the forums today after a few weeks browsing. I must say I am very impressed with the level of knowledge here and how helpful people are to others, especially noobs like me
Anyway, I got a nook color, but I am in Ireland, so I can't register it, that didn't worry me too much, because I wanted to root it, and after much reading on these forums I decided to use CM7.
My build at the moment is as follows, built with Clockwork,
CM7 RC4,
Dalingrins's OC kernel emmc 0413A,
Alsa 041411
First thanks to all the people who made the mods/ kernels etc Your work is really appreciated I am loving the nook color now with the mods.
I just have a few very basic questions, lol and I am still getting to grips with the right terminology
1. Does it matter which way I install mods/kernels etc? I understood that you had to install the CM7 mod first, but, for Dalingrin's OC kernel and Alsa, I installed the kernel first than Alsa, or does it matter?
2. If a new kernel comes out, or an update to Alsa, do I have to uninstall the old one? Or can I just boot into recovery mode wipe the caches and install the updates?
3. Same question for the CM7 mod, If I want to try some of the nightlies, can I just put the nightly on an SD card, wipe caches and install it the same way I did the RC4 version? will I have to reinstall the other kernels if I do this?
4. What happens my data and apps if I do update CM7?
5. I made a backup on the SD card using clockwork. Is this just a backup of the system files? or is it a backup of data and apps as well?
6. I am trying to learn more about this, in performance settings there is a thing called VM heapsize. Is there a recommended value for this?
7. And in the CPU settings there are a number of options available under "available governors" what are govenors? and which one is best? Is there an explaination available for each one?
That's all the questions I have for now. Very sorry if these have been answered a million times already!!
reaper12 said:
Hi All,
Just joined the forums today after a few weeks browsing. I must say I am very impressed with the level of knowledge here and how helpful people are to others, especially noobs like me
Anyway, I got a nook color, but I am in Ireland, so I can't register it, that didn't worry me too much, because I wanted to root it, and after much reading on these forums I decided to use CM7.
My build at the moment is as follows, built with Clockwork,
CM7 RC4,
Dalingrins's OC kernel emmc 0413A,
Alsa 041411
First thanks to all the people who made the mods/ kernels etc Your work is really appreciated I am loving the nook color now with the mods.
I just have a few very basic questions, lol and I am still getting to grips with the right terminology
1. Does it matter which way I install mods/kernels etc? I understood that you had to install the CM7 mod first, but, for Dalingrin's OC kernel and Alsa, I installed the kernel first than Alsa, or does it matter?
Click to expand...
Click to collapse
Although I haven't installed Alsa, I doubt that the order matters.
2. If a new kernel comes out, or an update to Alsa, do I have to uninstall the old one? Or can I just boot into recovery mode wipe the caches and install the updates?
Click to expand...
Click to collapse
You should be able to upgrade with CWR. I have CM7 on a SD card and just add the new kernel and boot into recovery mode.
3. Same question for the CM7 mod, If I want to try some of the nightlies, can I just put the nightly on an SD card, wipe caches and install it the same way I did the RC4 version? will I have to reinstall the other kernels if I do this?
Click to expand...
Click to collapse
Since the nightly has its own kernel, you will need to reinstall the OC kernel.
4. What happens my data and apps if I do update CM7?
Click to expand...
Click to collapse
They shouldn't be affected.
I'll leave your other questions to someone else, since I haven't dealt with these issues.
thanks for tthe reply Bob.
Can anyone add anything for the last few questions?
will i lose all settings, files, apps?
is there a way to keep everything and change rom?
I would say it is good practice to do full wipe when switching to different ROM generation.
Once you are on CM7 upgrading to never version is OK with just caches cleanup.
In your case I would use TitaniumBackup or any similar app to backup all the apps. In theory you could try to restore the app data but may not work properly. Use as much as possible backup/recovery build in the apps.
BTW consider app2ext - I do not known if such a feature is available in FM - search the forum how to create separated partition on your SD card
well i gave it a try.
updated OR, did all 3 wipes, installed the latest CM7 and rebooted.
i just got the M sign no matter what i did.
had to nandroid back to my latest backup.
never had that in any froyo mod.
is it hopeless?
should i try again?
When you wipe, go into the partitions menu and format boot and system too.
Sent from my Droid using XDA App
how exactly?
didn't find it in the OR menus.
Don't do that!
There's no data of /boot in CM7 packages!
Switching from Stock 2.2.1 to CM7 worked flawlessly for me back then.
Try downloading the CM7 .zip again, apply it and do all 3 wipes afterwards.
tried again, like you said.
didnt work. back to froyo.
bummer.
ok, tried the HO NO mod of this rom and its working!
looking great. thanks for your help.
this HO NO is a version of the original CM7. meaning if there are future updates to the original CM7 i will be able to update, correct?
i wont have to necessarily wait for a "HO NO" version?
It's not that easy.
HO!NO! is a CM7 mod - that's right.
But if you mix updates from both HO!NO! and CM7 you will very likely end up with the M-screen or bootloops again.
Usually it's like this:
Update the ROM you're on: flash zip, wipe caches
Change to a different ROM: flash zip, wipe everything