Just a quick question,
I'm thinking of going back to 4.1.11 from the latest Cyanogen (4.1.9999). It's been by far the fastest of the mods but i was just wondering if i need to flash anything before going back since i did flash that HTC image.
Thanks in advance
most likey a wipe and then A FLASH OF 4.1.11., make a nandroid backup and flash 4.1.11 if you have any problems than wipe and reflash
If you have a backup of your NAND while in 4.1.1 then you could just restore.
Basket Lotioner said:
If you have a backup of your NAND while in 4.1.1 then you could just restore.
Click to expand...
Click to collapse
I just had to pop in and say ROTFL @ your screen name.
Put the freaking lotion in the basket!.....classic....
If you have a nandroid backup I find it always works flawlessly if you wipe before restore
i have to agree with you jndd, i have also noticed that a wipe before a nandroid always does work great otherwise i notice at least 3 fc
I NANDroided back to 4.0.4 from 4.1.999 without wiping and I haven't gotten any force closes.
@ DirectMatrix - Thanks man. Best thing ever!
Related
im using the cdma hero with fresh 2.4 rom on it i wanted to move to the new cm6.0.
and i assume the nightly rom on the cm site is for my phone...right? buttttt
i deleted the files for what i believe is my nandroid back up and apparently never put them on my computer....is there a way to get around this? or am i screwed?? do i have to unroot? then root, flash?
is there a 1 click root?
AND idk how to get out of root..so a link to a guide or maybe a quick way to do it would be nice...thank you for all the help. if you need more info in order to assist ill be glad to tell you.
I'm confused. Did you already flash CM6 or do you want to? If you haven't why don't you just do another nandroid backup. If you already flashed CM 6 and are trying to get back to Fresh, then you are SOL.
Yes, there is a 1-click root, but I forgot where I saw it at.
Thread moved in Hero CDMA Q&A.
Well I'm on fresh right now. I want to move to cm 6. Do I always have to do a nandroid restore when flashing a new Rom? I assumed you did.
But I cannot do a nandroid restore bc it tell me "cannot open directory no files found"
Sent from my HERO200 using XDA App
crazyninjah1992 said:
Well I'm on fresh right now. I want to move to cm 6. Do I always have to do a nandroid restore when flashing a new Rom? I assumed you did.
But I cannot do a nandroid restore bc it tell me "cannot open directory no files found"
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
No these are the steps to move to cm6
1. Nandroid backup (when people say nandroid first they mean a backup).
1.5 update your prl, radio, profile if they are out of date (optional)
2. wipe dalvik and factory wipe phone.
3. flash new rom.
4. enjoy.
Here are the CM6 nightlies for the CDMA Hero. If you perform a nandroid backup you are copying your system in the exact state that it is so that if something happens you can revert back to it. When you perform a nandroid restore you are reverting back to the state at which you ran the nandroid backup. Most people recommend doing a nandroid backup before flashing a new rom. You do not do a nandroid restore when flashing a new rom. Just make sure you do a full wipe and wipe dalvik before flashing a new rom.
Ooh okay wow that's gonna help! can i update the prl and all that by just going system updates? and updating there?
Sent from my HERO200 using XDA App
thank you!
am i better off downloading the cm 6 rc1 froyo build? thats more stable then the nightlies? ccan i use rom manager to update the nightly?
crazyninjah1992 said:
Ooh okay wow that's gonna help! can i update the prl and all that by just going system updates? and updating there?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Yes but only in Sense Roms CM6 and AOSP roms dont have this functionality (keep your last fresh nandroid for this purpose). Before you move to CM6 update all of that and then flash CM6. Then anytime you need to update any of that stuff in the future (prl, pri, profile) you can do a nadroid and then go back to your Fresh backup and restore then update it and then restore back to cm6.
okay! thank you very much!
and the nightlies? i dont mind using experimental roms as long as i can use like rom manager to just update it i dont wanna flash a new rom every day..
So im wondering, what is the standard practise, or based on your own experiences. What is the best way to flash over an existing rom using CWM? What do you do to prepare the fone for new rom, wipe user data, dalvik cache, before or after flashing. Just trying to get a good idea of how to do it.
Sent from my SAMSUNG-SGH-I897 using XDA App
going from rom to rom:
put rom.zip on /sdcard/
reboot to recovery
install zip from sdcard
point to rom.zip
flash
reboot
any rom that has been properly done will wipe user data and dalvik cache for you. no need to do it manually
i always flash back to eclair and master clear with odin one click to make sure all files from previous roms are gone then CWM flash new ROM
Pirateghost said:
going from rom to rom:
put rom.zip on /sdcard/
reboot to recovery
install zip from sdcard
point to rom.zip
flash
reboot
any rom that has been properly done will wipe user data and dalvik cache for you. no need to do it manually
Click to expand...
Click to collapse
+1
Except I do clear the caches manually, but that's just because I have OCD.
CremeFraiche said:
i always flash back to eclair and master clear with odin one click to make sure all files from previous roms are gone then CWM flash new ROM
Click to expand...
Click to collapse
lets look at the master clear function shall we?
when you flash to stock...your entire / is stock (RFS, eclair 2.1, /data /system, etc)
essentially, you have just reformatted your root, think of it like formatting your C drive and your sdcard is like a secondary internal drive that contains storage
master clear at this point will only delete items off your /sdcard
roms dont care about your /sdcard, master clear is worthless when you are stock
there was a time where it was necessary to flash to stock to reset the filesystem and then flash the rom. it has not been needed in months, but it continues to get preached as gospel.
even flashing to stock isnt necessary unless you are trying to come from CM7 or MIUI....or if something goes horribly wrong
Thx for info guys, I have flashed a few times and it seemed like now and then my fone must became bogged down and needed to be fully wiped, sound didnt work or lagfix folders bunch of text docs, just seemed cluttered. So if wanted to really clear out junk what would be a good way without having to flash back to stock?
Sent from my SAMSUNG-SGH-I897 using XDA App
Just flash. If you have a problem then back to stock Ans a MC. I have flashed hundreds of time back to stock once.
Sent from my SGH-I897 using XDA Premium App
Pirateghost said:
lets look at the master clear function shall we?
when you flash to stock...your entire / is stock (RFS, eclair 2.1, /data /system, etc)
essentially, you have just reformatted your root, think of it like formatting your C drive and your sdcard is like a secondary internal drive that contains storage
master clear at this point will only delete items off your /sdcard
roms dont care about your /sdcard, master clear is worthless when you are stock
there was a time where it was necessary to flash to stock to reset the filesystem and then flash the rom. it has not been needed in months, but it continues to get preached as gospel.
even flashing to stock isnt necessary unless you are trying to come from CM7 or MIUI....or if something goes horribly wrong
Click to expand...
Click to collapse
I would definitely agree. I have also seen people say to disable lagfix before flashing. I have not done that either and never had any problem.
Would just like to amend the advice already given with the following:
Pre-flashing:
1. Titanium Backup of apps and data
2. Nandroid backup in case something goes boom.
Post-flashing (assuming success):
TB restore of user apps/data only. NEVER RESTORE SYSTEM FILES.
They may not apply to some people, but I feel those are necessary steps for anyone that actually uses their phone daily.
modest_mandroid said:
Would just like to amend the advice already given with the following:
Pre-flashing:
1. Titanium Backup of apps and data
2. Nandroid backup in case something goes boom.
Post-flashing (assuming success):
TB restore of user apps/data only. NEVER RESTORE SYSTEM FILES.
They may not apply to some people, but I feel those are necessary steps for anyone that actually uses their phone daily.
Click to expand...
Click to collapse
why not restore system files? Does this apply if coming from flashing back to stock first, or just flashing from one rom to another?
Glad to hear the advice about not flashing back to stock, that's been one of the major reasons I haven't flashed quite as many rom's as I want, too time consuming.........not to say that i'm not flashing a couple rom's a week, but there's just so many options to try
neophile said:
why not restore system files? Does this apply if coming from flashing back to stock first, or just flashing from one rom to another?
Click to expand...
Click to collapse
Making "search" a standard practice would be very helpful.
Restoring system is known to mess up ROMs in all cases. Though may not be mandatory, but make it a standard practice to flash stock. Takes hardly 10 mins, and helps save big headaches later.
neophile said:
why not restore system files? Does this apply if coming from flashing back to stock first, or just flashing from one rom to another?
Click to expand...
Click to collapse
Incompatibilities across rom versions, mostly. As the guy above me said, restoring system files tends to mess up a rom because you are overwriting part of it with files from a different rom.
There is one caveat, however. If you're flashing back to a rom you originally performed the backup on, you can safely restore system files. For example, if you were running Cog 4.3 and did a full TB backup, then decided to flash Serendipity 6.3, you would want to restore only your user apps and user data. However, if you decided to flash back to Cog 4.3 at some point, you could do a full TB restore without worrying about incompatibilities.
I agree with everyone else. Flashing over another rom seldom causes issues. I make s nandroid backup of my favorite rom with everything setup the way i like it. then flash away trying different roms. When i am done, i just restore my backup and all is good!
I have done a search, couldn't find the specific answer I needed, hence my asking. Could be I wasn't phrasing the search correctly......but here I am.....
To clarify, what do you dpo to get your system settings back after flashing a new rom? I flashed to serendipty 6.4 last night, as per the advice, I didn't restore system files, just apps and data, but that didn't work so well for me. I lost my data connection, could only use my wifi, and had no contacts, or any sms msgs. I don't know what else was missing, but I then went and restored system files, everything came back as needed, and there seems to be no issue......
How do I get my info setting back, or do I just need to manually re-set everything after flashing? Apart from wireless info, msgs and contacts, what else do you lose by not restoring?
Appreciate your help
havent flashed a new rom in a while and forgot if anything extra was needed when flashing a rom over a rom
thx!
I was wondering how perfect of a restore a CWM restore is.
I was running a custom GB ROM (rocket rom to be exact) and it was running flawlessly. I then decided I might try this new CM9 ICS ROM.
So to be sure about the CM9 install, I figure I'd install from a stock GB Rom. So I first did a CWM backup of my current rocket rom and then I restored an older stock (rooted) ROM. It seemed to work fine. Then.... after reading about the (few) issues wit this new CM9 rom I decided I'd wait a bit longer until a few more of the quirks are worked out.
So I then restored back my Rocket rom backup and even doing the flash cache and davik cache also. But now I notice my once working Rocket ROM is experiencing a lot of SODs.
So now I'm wondering how perfect my restore was. I really don't have a lot of apps or wireless networks and can easily restore my contact list. For that reason, do you think it'll help if I do a factory reset wipe and then reinstall everytyhing....or even go so far as reinstall rocket rom and then reinstall everything else manually without any restores...would that be really the best clean install....or would any of this not make a difference at all and wiping/reinstall a toatl waste of time and my prob is actuaully something else....
Thanks
I could do with knowing the answer to these questions too.
It would be good to get a detailed idiots guide to CWM, do's and don't's etc.
Well a clean install will surely get you rid of the SODs. There is some app and its data that is conflicting with the system and crashes the whole phone. So if you are ready to clean install everything that will fix everything
abhisahara said:
Well a clean install will surely get you rid of the SODs. There is some app and its data that is conflicting with the system and crashes the whole phone. So if you are ready to clean install everything that will fix everything
Click to expand...
Click to collapse
Sorry for the noob question.... what are SOD's?
adrok76 said:
Sorry for the noob question.... what are SOD's?
Click to expand...
Click to collapse
sleep of death, its the device not waking up properly from sleep
Pus it doesnt include efs, so its not complete backup. Handy if yu stay n same rom version, but thats likely not.
Squicky clean install is always best. Even only app and data recovering thought titanium can mess things up. Make it laggy and nonfunctional etc, Blegh
Sent from my GT-N7000 using Tapatalk 2
1. Install abyssnote42
2. Factory wipe, cache, dalvik
3. Restore your rocketrom backup
That's what i do with my rocketrom v23 backup
Zapped through server hops to XDA forums
its not perfect but its the best so far
all i can say is that cwm is the best and simple thing for me so far and if u get trouble some times while trying to shift from CM9 to normal ics or from gb to ics all I suggest is use redpill recovery from abbysnote
Richy99 said:
sleep of death, its the device not waking up properly from sleep
Click to expand...
Click to collapse
Yeah, mine does that from the clock on Dragon ICS 2.4 when charging it didn't use to, started since I started Dual Booting. 2.5 is out in the next hour or so according to the Dev page. Hope it fixes an otherwise awesome ROM.. Otherwise it's back to single booting and possibly on to Omega 12 until CheckROM is released..
Hey all,
I installed CM10 Helly Bean (DerTeufel) port for Captivate V10 with full wipe.
It seemed to be working fine... fooled around a bit, tried out Google Now, etc.
Was restoring apps (not data) w/ Titanium Backup.. forget if it had finished or not...
Didn't try to run any of these programs or anything, just tried to unlock and the touchscreen was not responsive... Tried wiping cache+dalvik + fixing permissions... tried reinstalling ROM and GAPPS...
All are in a non-responsive bootloop.
I'm starting over now with another factory wipe... as of now it is stuck on "Welcome" Screen and touchscreen is not responding... AND.. it just restarted
Any ideas as to the problem... Was it Titanium Backup related? Should I resist running that again (assuming this ever works)?
I would post this on Development thread but I still don't have my 10 posts, heh, mostly a long-time lurker...
Thanks!
Worse than I thought!
So It's worse than I thought... I gave up and re-flashed slim (ICS)... and the same problem still exists... boots up, looks normal, can't touch anything.... eventually it reboots....
Suggestions?
Would ODIN flash do anything different? I9000 bootloaders?
ScruffMcG said:
Hey all,
I installed CM10 Helly Bean (DerTeufel) port for Captivate V10 with full wipe.
It seemed to be working fine... fooled around a bit, tried out Google Now, etc.
Was restoring apps (not data) w/ Titanium Backup.. forget if it had finished or not...
Didn't try to run any of these programs or anything, just tried to unlock and the touchscreen was not responsive... Tried wiping cache+dalvik + fixing permissions... tried reinstalling ROM and GAPPS...
All are in a non-responsive bootloop.
I'm starting over now with another factory wipe... as of now it is stuck on "Welcome" Screen and touchscreen is not responding... AND.. it just restarted
Any ideas as to the problem... Was it Titanium Backup related? Should I resist running that again (assuming this ever works)?
I would post this on Development thread but I still don't have my 10 posts, heh, mostly a long-time lurker...
Thanks!
Click to expand...
Click to collapse
sorry I'm just going to post twice so I can post to development...
yeah... 10char
What I can suggest is, go back to GB. Download a one click Odin w/ bootloaders, you can search that in the dev forum. After that flash it with a corn kernel so you can have a working CWM. And then Go to recovery, have a full wipe (data,cache,dalvik) TWICE and flash this--
Slimmed Down V10 by cbalt
Wipe Data/Factory Reset/Wipe Dalvik
Flash http://www.mediafire.com/?9p212pempybwnj3
Then Flash http://www.mediafire.com/download.php?bdjabcmobz6aw6k
Then Fix Permissions
Then Reboot
Click to expand...
Click to collapse
I can recommend you that one because it's the one the I'm currently using right now and I can say that it's working like a charm.
The method above is the one I'm using everytime I flash a ROM. I always do a full wipe so I won't be encountering any issues or whatsoever.
About TiBu, I am not sure if that's where the issue coming from because I've been using TiBu for a long time and haven't encountered that. Just always remember, if you are using backup using TiBu, just backup the User Apps+Data, DO NOT INCLUDE THE SYSTEM APP. Goodluck!
So you think w/bootloaders will help?
I have flashed every odin w/o bootloaders that I have access too and all get me stuck at ATT bootscreen....
Little hesitant to reflash my bootloaders since I was/am already on GB bootloaders, but if it might help I may have to do it...
I actually was on that JB version (but with the normal gapps b/c I wanted google now...)... now I'm on no version of anything hahah
takeoutttt said:
What I can suggest is, go back to GB. Download a one click Odin w/ bootloaders, you can search that in the dev forum. After that flash it with a corn kernel so you can have a working CWM. And then Go to recovery, have a full wipe (data,cache,dalvik) TWICE and flash this--
I can recommend you that one because it's the one the I'm currently using right now and I can say that it's working like a charm.
The method above is the one I'm using everytime I flash a ROM. I always do a full wipe so I won't be encountering any issues or whatsoever.
About TiBu, I am not sure if that's where the issue coming from because I've been using TiBu for a long time and haven't encountered that. Just always remember, if you are using backup using TiBu, just backup the User Apps+Data, DO NOT INCLUDE THE SYSTEM APP. Goodluck!
Click to expand...
Click to collapse
I met a problem. I do not know wether or not it is common. The phone will reboot by itself sometimes.
Do you have the same problem?
same here
seems as though many of the problems experienced by one are shared by the other
this is logical as they share many common points including the same partition and both jellybean derivations
I was having issues... accelerometer and audio issues.
All came out right as rain after flashing back to stock and reflashing
ScruffMcG said:
yeah... 10char
Click to expand...
Click to collapse
Basically I'm using ICS333 which is great and to do I was trying to make some changes to the stock contacts apps. Anyway, I did a nandroid backup via CWM 5.5 so that I can restore if anything went wrong and sure enough I flashed something meant for JB. I went to restore my backup and afterwards rebooted... except now it is stuck in a loop when it reaches the ICS loading screen.
The only way to make it boot in ICS now is to wipe all personal data... which makes the backup meaningless.
In all honesty, the only thing I really want to keep is my whatsapp and texts. I'm currently trying to restore individual bits of the backup to see what causes the problem but can I extract data from a Nandroid backup?
This day gets better, now my home button doesn't work!
Ultraman1966 said:
can I extract data from a Nandroid backup?
Click to expand...
Click to collapse
yes, download a nandroid browser from play store, and try My Android solutions (link below) for a suitable remedy
For for the tips, I used Titanium backup to retrieve some of the info but didn't to junk the rest. Less crap on the phone means it runs like butter again!