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
Related
I flashed to the CyanogenMOD 4.0.4 ROM then flashed in Ted's Hero theme for that rom and then all hell broke loss. My phone is suddenly unstable. To get back to the original 4.0.4 rom do i just wipe and then load it on again?
Also, any reason why a theme should make the phone unstable? It thought that all the theme really did was to replace some of the system images.
Thanks
DaveKid
DaveKid said:
I flashed to the CyanogenMOD 1.4.1 ROM then flashed in Ted's Hero theme for that rom and then all hell broke loss. My phone is suddenly unstable. To get back to the original 1.4.1 rom do i just wipe and then load it on again?
Also, any reason why a theme should make the phone unstable? It thought that all the themes really did was to replace some of the system images.
Thanks
DaveKid
Click to expand...
Click to collapse
Well I'm not really sure why in the world you would be using a CM ROM with version 1.anything... The most recent ROM is version 4.0.4. Now if you flashed his recovery image version 1.4 that is not a ROM and a theme will mess with a ROM it was not built for. If you really are using his ROM version 1.4.1 then Ted's hero theme is built for version 4.0.4 so yes you will run into lots of issues.
Yes, just wipe and reflash.
Also questions belong in Q&A.
Title should say 4.0.4? build not 1.4.1. sorry about that.
DaveKid said:
Title should say 4.0.4? build not 1.4.1. sorry about that.
Click to expand...
Click to collapse
Did you wipe before you flashed CM 4.0.4 and the theme? You shouldnt have to but it might help resolve any issues. You also might want to reformat your ext partition.
Diceman4 said:
Did you wipe before you flashed CM 4.0.4 and the theme? You shouldnt have to but it might help resolve any issues. You also might want to reformat your ext partition.
Click to expand...
Click to collapse
try the wipe first, make sure you have the update.zip on the root of your sd card, then use the good old power off then hold home and power button and flash the update
I wiped before the 4.0.4 ROM install yes. obviously not between the 4.0.4 and the theme.
All i'm really wondering is to get back to 4.0.4 can i just wipe and reload? Wipe essentally clears the phone of anything that was on it correct?
wiped and reloaded 4.0.4 build, worked like a charm...thanks guys for help. quick side question...just need a short answer...is installing the stable hero rom that is floating around as easy as the cyanogenMod? or is it much more complicated?
DaveKid said:
wiped and reloaded 4.0.4 build, worked like a charm...thanks guys for help. quick side question...just need a short answer...is installing the stable hero rom that is floating around as easy as the cyanogenMod? or is it much more complicated?
Click to expand...
Click to collapse
You need to have the newest radio and Haykuro's Special SPL installed to run any Hero ROM. once that is on it is just as easy to flash a hero ROM. If yo install the new SPL make sure to follow the instructions exactly to avoid bricking your phone.
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).
I'm using CM 5.0.5.3 with apps2sd working great and I'm on AR 1.6.2.
What would be the benefit of flashing over that with 1.7? Would I screw anything up?
I assume I use the CM version rather than the "Normal" version but what if I want to try out enomther (my battery life sucks on 5.0.5.3)?
Thanks for the help!
no real reason.. i`m using Rom Manager.. makes things ALOT easier.. try it.. it's on the market
Flashing to an updated Recovery will not mess with the ROM... neither will flashing an updated Radio. The benefit is just that you'll have whatever extra functionality Amon_RA has built into the new version.
qiuness said:
no real reason.. i`m using Rom Manager.. makes things ALOT easier.. try it.. it's on the market
Click to expand...
Click to collapse
Same here...I can do all the same things it just makes it simpler...not to mention I'm lazy
to get support for the ap2d feature in CM 5.0.3
if you tried to wipe your partition it won't work. Also, if you tired to re flash your rom, that part becomes inaccessible and the a2sd feature will be grayed out
Well, I installed ROM Manager and now have the ClockworkMod Recovery installed. It gives me the option to download other non-Cyanogen Roms. I was under the impression that meant I had to wipe everything, Backup with nandroid and Titanium and Install everything fresh. Will the world explode if I install another different ROM from within ROM Manager or will it just not work properly (lots of FC)?
whodatfever said:
Well, I installed ROM Manager and now have the ClockworkMod Recovery installed. It gives me the option to download other non-Cyanogen Roms. I was under the impression that meant I had to wipe everything, Backup with nandroid and Titanium and Install everything fresh. Will the world explode if I install another different ROM from within ROM Manager or will it just not work properly (lots of FC)?
Click to expand...
Click to collapse
a boot loop is the most likely occurrence.
You don't need the "cyan" version either. "Normal" is the same code wise...... I was under same false impression when it was first released.
Clockwork seems lovely but I have had few problems with it. One nand got all screwed up this week that broke my confidence. Amon_RA until Clockwork can be ironed out is what I would suggest (personal preference for all).
tried g-script
i tried the g-script per some other post off another android site and it was a no go. anytips, I do like the rom manager recovery mode although i do need to update my bootloader and my recovery rom.
djsmeadly said:
i tried the g-script per some other post off another android site and it was a no go. anytips, I do like the rom manager recovery mode although i do need to update my bootloader and my recovery rom.
Click to expand...
Click to collapse
Congratulations for digging up a dead thread and bringing it back to life.
Amon RA is at 2.x now.
Every single one of them are failing @ System.
I have flashed many roms and have yet to see this issue.
I have even tried to install a nandroid and they say system.img not found, skipping restore of System
my quadrant before doing anything was ~950 so im assuming no lagfix was present.
did you flash back to stock with odin1click??
ed116 said:
did you flash back to stock with odin1click??
Click to expand...
Click to collapse
no, i typically never do.
i have a stock eclair rooted nandroid but eh.
trying to avoid using odin right this minute...
iamamp3pimp said:
no, i typically never do.
i have a stock eclair rooted nandroid but eh.
trying to avoid using odin right this minute...
Click to expand...
Click to collapse
Going back to stock is the only safe way to install a rom imo.
Do a proper stock install and watch all the roms work.
im sure it will.
im just trying to learn why. it all started when i went to install SetiroNs 1.4.6 cwm
ccdoggy said:
Going back to stock is the only safe way to install a rom imo.
Do a proper stock install and watch all the roms work.
Click to expand...
Click to collapse
+100000000
iamamp3pimp said:
im sure it will.
im just trying to learn why. it all started when i went to install SetiroNs 1.4.6 cwm
Click to expand...
Click to collapse
Because it is the phone...not the rom or kernel...unless you had a bad flash to begin with.
This is why it is recommended when switching to different roms...and even sometimes flashing updates to certain roms ...that it is the most prudent thing to do, to head off these types of issues that come up sometimes. It is also recommended to do a master clear as well...and I usually go one step further and wipe and format the drives and do a factory reset. Sometimes doing it more than just once too. It may be a royal PITA...but...the alternative is what you are experiencing it seems...
Mac
is there a way to tell which filesystem is being used?
i have CWM 2.5.1.2
my Axura restore did work.......so i at least have a phone for the moment
OK so I have been flashing the new Roms on my phone for a long time now and recently I've noticed that the market doesn't work on the newer Roms. If I go to the market and try to download something it will just say downloadIng and will stay that way. I had to keep an old version of a Rodriguez Rom on my phone, flash back to that, update my apps and then back them up to put them on the newer Roms. Long story short, the market doesn't work for me on newer Roms. Can anyone tell me what I'm doing wrong?
What new rom? You doing full wipe when going from one rom to the next?
baseballfanz said:
What new rom? You doing full wipe when going from one rom to the next?
Click to expand...
Click to collapse
all of them. Well the Miui Roms. Cyan is the only Rom that doesn't do it. And I do wipe. 5 times like it says. Still doesn't work.
Possibly a sign of corrupt data on the SD. Try running ScanDisc from your PC on the SD card, and fixing any errors...