I am currently using the latest RocketROM V7.
I wanna know... if I am to backup and restore a ROM with ClockworkMod Recovery... how should I do it?
I flash Abyss Kernel 4.2, reboot recovery (so I am in the CWM modified by Abyss), backup the ROM... and when I wanna restore, I do the same?
If that's the way to go, when I restore, I'll have Abyss Kernel 4.2, and not the one that the ROM has... Erm... Can somebody shed some light?
I'm asking because I'm aware of all this talk about the eMMC bug (and the fact that it actually exists), and since CWM formats the internal memory... it'd result in a hard brick, haha...
if you backup on Abyss kernel you will be on Abyss kernel AFTER the restore, So ideally you should flash abyss BEFORE restoring, and then change the kernel AFTER (if you want to)
The brickbug is not to be taken lightly, Its a serious issue, so if you have to do things a certain way (I have a ritual for wiping lol) and it takes a little longer, So be it, at least you know you will be safe.......ish
azzledazzle said:
if you backup on Abyss kernel you will be on Abyss kernel AFTER the restore, So ideally you should flash abyss BEFORE restoring, and then change the kernel AFTER (if you want to)
The brickbug is not to be taken lightly, Its a serious issue, so if you have to do things a certain way (I have a ritual for wiping lol) and it takes a little longer, So be it, at least you know you will be safe.......ish
Click to expand...
Click to collapse
Hmm... so... forget about RocketROM for now.
Let's say I am on Half-Illusion, which has two kernels (optionally) : CM and AOKP.
-flash jBroid's Kernel Cleaning Script.
-flash Abyss 4.2 kernel.
-reboot recovery.
-backup.
When I restore, I do this :
-flash jBroid's Kernel Cleaning Script.
-flash Abyss 4.2 kernel.
-reboot recovery.
-restore.
-flash desired kernel.
azzledazzle said:
The brickbug is not to be taken lightly
Click to expand...
Click to collapse
You don't say . First time I heard about it and was about to wipe/flash for the first time, I was like http://www.youtube.com/watch?v=Y9KyBdPeKHg
-----
What's your wiping ritual? Could it better than mine ? Hope it doesn't involve summoning a lightning strike or anything like that...
Formhault said:
Hmm... so... forget about RocketROM for now.
Let's say I am on Half-Illusion, which has two kernels (optionally) : CM and AOKP.
-flash jBroid's Kernel Cleaning Script.
-flash Abyss 4.2 kernel.
-reboot recovery.
-backup.
When I restore, I do this :
-flash jBroid's Kernel Cleaning Script.
-flash Abyss 4.2 kernel.
-reboot recovery.
-restore.
-flash desired kernel.
You don't say . First time I heard about it and was about to wipe/flash for the first time, I was like http://www.youtube.com/watch?v=Y9KyBdPeKHg
-----
What's your wiping ritual? Could it better than mine ? Hope it doesn't involve summoning a lightning strike or anything like that...
Click to expand...
Click to collapse
HAHAHAAAA That video is epic, I can imagine you saying that lol, I too was like that.
And my ritual is similar to yours, Only for TW ROMs
Dont forget that your backup will be a GB ROM, so you cannot restore it if you venture on to TW ICS ROMs ! But im sure you knew that anyway !
Other than that, Your steps are spot on !
azzledazzle said:
And my ritual is similar to yours, Only for TW ROMs
Dont forget that your backup will be a GB ROM, so you cannot restore it if you venture on to TW ICS ROMs ! But im sure you knew that anyway !
Click to expand...
Click to collapse
Erm... what? Lol, explain.
What do you mean it will be a GB ROM? You mean the KERNEL, right?
What do you mean I can't restore it if I venture on to TW ICS ROMs (like RocketROM, for example)?
azzledazzle said:
HAHAHAAAA That video is epic, I can imagine you saying that lol, I too was like that.
Click to expand...
Click to collapse
Actually, it was like this.
So I first hear about the brick bug. http://tinyurl.com/69cc7we http://tinyurl.com/buvmsep
I decide oh well, can't stick with stock ROM. http://tinyurl.com/2at2ad4
So I go on with the wiping / flashing process. http://tinyurl.com/bmoff37
And once it was all done... http://tinyurl.com/4h7lp8q
Formhault said:
Actually, it was like this.
So I first hear about the brick bug. http://tinyurl.com/69cc7we http://tinyurl.com/buvmsep
I decide oh well, can't stick with stock ROM. http://tinyurl.com/2at2ad4
So I go on with the wiping / flashing process. http://tinyurl.com/bmoff37
And once it was all done... http://tinyurl.com/4h7lp8q
Click to expand...
Click to collapse
What I mean is, if your now on a gb rom such as cm9 or aokp And you create a nandroid backup, that backup is going to be a complete clone of your current set up. So you cannot restore that nandroid on a Samsung ics rom you can only restore it on a gb rom
Sent from my GT-N7000 using Tapatalk 2
azzledazzle said:
What I mean is, if your now on a gb rom such as cm9 or aokp And you create a nandroid backup, that backup is going to be a complete clone of your current set up. So you cannot restore that nandroid on a Samsung ics rom you can only restore it on a gb rom
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I didn't know AOKP had GB builds, too...
Anyway. I know what a CWM backup is, I've been in the Android world since exactly 13 months.
What do you mean I can't restore that NANDROID on a Samsung ICS ROM? As far as I know, a CWM restore erases all the contents (system, data, cache) and restores the respective data from the backup... so it's not like it would OVERWRITE on the current TW ICS ROM, for example.
What I wanna know is... I can back up everything, except for the kernel (since I'd flash Abyss 4.2 w/ recovery), and when I restore, I flash the kernel manually. That's all there is to it... right?!
When you are creating a backup...just drop into CWM and create backup. When restoring the backup you can flash the Abyss kernel first > reboot recovery > and then restore. So now when the restoring happens the kernel which was in your rom will automatically get restored and abyss will vanish once rebooted.
@azzledazzle CM9 is ICS and not a GB rom I know you know this and u just slipped your fingers while typing ...but just correcting so that no confusion arises to other readers
And if you are on any CM9 based rom or any AOKP based rom which is based on CM kernel then you dont require Abyss at all. Just forget about it when on any of the roms.
Hope this helps!
Cheers!
Yeah I know its an ICS ROM, But dont you have to be on GB to flash it ? What I mean is you cant flash it from Stock Samsung ICS can you? (thats how i understand it anyway)
And I didnt know CWM erases partitions, I thought it just overwritten the existing ones, Hence why I said dont restore a GB (AOSP ICS) on Samsung ICS (if that makes sense?)
But I guess ive learned something new from you Hopefully I can pass this new found knowledge onto someone else lol
azzledazzle said:
Yeah I know its an ICS ROM, But dont you have to be on GB to flash it ? What I mean is you cant flash it from Stock Samsung ICS can you? (thats how i understand it anyway)
Click to expand...
Click to collapse
Yeah you cant directly flash the CM9 or AOKP based on CM kernel directly over the Stock Samsung ICS. Its a sure shot brick you have in your hand if you do that. The stock ICS kernels cannot handle the "format" command in the updater script, CM is working on trying to use delete_recursive instead but still its not complete fixed. Hence you have to be on GB or on GB kernel (like Abyss) if you want to flash the CM9 based rom.
abhisahara said:
When you are creating a backup...just drop into CWM and create backup. When restoring the backup you can flash the Abyss kernel first > reboot recovery > and then restore. So now when the restoring happens the kernel which was in your rom will automatically get restored and abyss will vanish once rebooted.
Click to expand...
Click to collapse
Oh... you're right, lol. Backing up doesn't format/wipe anything. Only restoring does .
But... the CWM I have right now (was flashed among with RocketROM) is a different version, non-touch-driven, than the CWM that is included in Abyss 4.2 kernel (touch-driven). Are backups compatible?
abhisahara said:
And if you are on any CM9 based rom or any AOKP based rom which is based on CM kernel then you dont require Abyss at all. Just forget about it when on any of the roms.
Click to expand...
Click to collapse
So... you're saying that both CM9 and AOKP kernels have the eMMC thing removed, so wiping data when using those kernels is safe?
-----
Thanks for joining, abhi
abhisahara said:
Yeah you cant directly flash the CM9 or AOKP based on CM kernel directly over the Stock Samsung ICS. Its a sure shot brick you have in your hand if you do that. The stock ICS kernels cannot handle the "format" command in the updater script, CM is working on trying to use delete_recursive instead but still its not complete fixed. Hence you have to be on GB or on GB kernel (like Abyss) if you want to flash the CM9 based rom.
Click to expand...
Click to collapse
Bottom line... Better flash Abyss 4.2 before any full wipe .
-----
This thing in the Samsung ICS kernels... this brick bug... Is Samsung aware of it? Is a fix on the way? Or nobody knows?
Or perhaps it's been made on purpose
-----
Retorical question : WHY POSTS NO LONGER MERGE? -.- :headbang:
Formhault said:
Oh... you're right, lol. Backing up doesn't format/wipe anything. Only restoring does .
But... the CWM I have right now (was flashed among with RocketROM) is a different version, non-touch-driven, than the CWM that is included in Abyss 4.2 kernel (touch-driven). Are backups compatible?
The CWM you have with RocketRom comes from the kernel of ICS which is included in the rom. The Abyss 4.2 is a GB kernel hence it has it own touch recovery. Not sure what you meant by - "Are backups compatible?"
So... you're saying that both CM9 and AOKP kernels have the eMMC thing removed, so wiping data when using those kernels is safe?
Yeah its perfectly safe wiping data on these kernels.
-----
Thanks for joining, abhi
Click to expand...
Click to collapse
Formhault said:
Bottom line... Better flash Abyss 4.2 before any full wipe .
-----
This thing in the Samsung ICS kernels... this brick bug... Is Samsung aware of it? Is a fix on the way? Or nobody knows?
Or perhaps it's been made on purpose
They know. They might be fixing it. Not date from them.
-----
Retorical question : WHY POSTS NO LONGER MERGE? -.- :headbang:
Click to expand...
Click to collapse
Hope the above helps!! In bold are the answers
abhisahara said:
Hope the above helps!! In bold are the answers
Click to expand...
Click to collapse
Yup. Thanks.
What I meant by "Are backups compatible" was... are backups made with the CWM that comes with RocketROM (not touch-driven) compatible with the CWM that is included in Abyss 4.2 (touch-driven)? I mean... can I restore the backups made with one CWM, using ANOTHER CWM?
I always forget their versions...
-----
They KNOW? Good. Oh well, they also know their SAMOLED screens suck, but didn't do anything to fix it... Let's hope they're gonna fix this brick bug soon; although it seems highly unlikely... I mean, we already got 4.0.4, and that didn't fix it. The next update is probably going to be JellyBean (if we even get that officially!), some 5+ months from now on :/
This brick bug is utmost retarded. I mean... on the Note, and recently, on the SGS2 as well... they're either stupid, either it was on purpose - to prevent at least some devs on working on those devices...
Formhault said:
Yup. Thanks.
What I meant by "Are backups compatible" was... are backups made with the CWM that comes with RocketROM (not touch-driven) compatible with the CWM that is included in Abyss 4.2 (touch-driven)? I mean... can I restore the backups made with one CWM, using ANOTHER CWM?
I always forget their versions...
-----
They KNOW? Good. Oh well, they also know their SAMOLED screens suck, but didn't do anything to fix it... Let's hope they're gonna fix this brick bug soon; although it seems highly unlikely... I mean, we already got 4.0.4, and that didn't fix it. The next update is probably going to be JellyBean (if we even get that officially!), some 5+ months from now on :/
This brick bug is utmost retarded. I mean... on the Note, and recently, on the SGS2 as well... they're either stupid, either it was on purpose - to prevent at least some devs on working on those devices...
Click to expand...
Click to collapse
Yeah you can restore backup made with some other CWM while using another CWM.
Intrestin ^^
Sent from my GT-N7000 using XDA Premium App
Related
I want to try some kernels for cm 7.1 to see if ocing could help speed up some games. If I don't like them I would like to get stock kernel back and I know I can't use sgs kernel flasher to back up current kernel because cm7 is different. I think I read that you could do a Nandroid and this would back up the current complete setup. Is this true? (sorry can't seem to search efficiently on this Tapatalk and don't have access to a computer). If so does it also backup apps, data and all? Is it done on the backup rom from rom manager or recovery? Thank you for your help.
Sent from my SGH-I897 using Tapatalk
nandroid backs up everything just as it is. definitely use cwm not rom manager.
you could also just put d/l the stable kernel as a cwm flashable zip.
2 cents
fractaline said:
nandroid backs up everything just as it is. definitely use cwm not rom manager.
you could also just put d/l the stable kernel as a cwm flashable zip.
2 cents
Click to expand...
Click to collapse
Thank you for your help. Where can I find the kernel?
Sent from my SGH-I897 using Tapatalk
Don't know for sure (I don't run cm7), but I would check the op of the cm7 thread.
fractaline said:
nandroid backs up everything just as it is. definitely use cwm not rom manager.
you could also just put d/l the stable kernel as a cwm flashable zip.
2 cents
Click to expand...
Click to collapse
nandroids do not backup kernel or modem.
have you ever made a backup of one set up and tried to restore onto a completly different rom? well if you have then you know there is a high chance that it will bootloop because of a now incompatible kernel. the procedure for a proper nandroid restore is to flash the rom it was backed up on (thus flashing the kernel that is compatible with it) and THEN restoring the nandroid. then it will be like you never flashed away from that rom at all. (this is speaking of tw roms as i have never run an aosp so i could be mistaken about it not backing up kernel on cm7)
studacris said:
nandroids do not backup kernel or modem.
have you ever made a backup of one set up and tried to restore onto a completly different rom? well if you have then you know there is a high chance that it will bootloop because of a now incompatible kernel. the procedure for a proper nandroid restore is to flash the rom it was backed up on (thus flashing the kernel that is compatible with it) and THEN restoring the nandroid. then it will be like you never flashed away from that rom at all. (this is speaking of tw roms as i have never run an aosp so i could be mistaken about it not backing up kernel on cm7)
Click to expand...
Click to collapse
Yea, I kinda thought that, but thought it worked for cm7.
Sent from my SGH-I897 using Tapatalk
well i have tried the AOSP and i really like it. but there are some problems that i can´t deal with them.. like
- the screen doesn`t let me use my 5 inch widgets and for that reason most of my homescreen is with out any use.
- all my itunes music are disable, i mean i can´t play it... don´t know why.
- the lack of use of my s-pen. i really need it some times.
- some times it turns off, but then it turns on ... said that, at least 3 times a day it freeze and i need to take the battery out or wait for the phone to turn off by itself.
well, sorry that´s not the point.
what i really need, is to find a way to change to another rom. First of all when i change to AOSP the instructions i read, said that i need to be on the chinese leak frst, so i did. then i flash it with the AOSP.
my question is: what do i need to do to migrate to midnote? ´cos i was on the chinese leak, so i don´t know if it matters or if it complicates things.
hope you can help me... thanks
First go Back to GingerBread:
- go to CWM recovery (Hold Power-, VolumeUp- and Homebutton, till CWM rises)
- flash Abyss Kernel v3.9 RedPill
- restore an NANDroid Backup
Now follow the Midnote Instructions
david.huwyler said:
First go Back to GingerBread:
- go to CWM recovery (Hold Power-, VolumeUp- and Homebutton, till CWM rises)
- flash Abyss Kernel v3.9 RedPill
- restore an NANDroid Backup
Now follow the Midnote Instructions
Click to expand...
Click to collapse
thanks, btw the what is the NANDroid backup?
Before going to your current Rom, did you make a backup of your Gingerbread rom? If so that's what you restore to.
I am on the same ROM and I have no problems whatsoever. I am on v8. Anyways, if you don't like it, you can easily migrate.
Here:
http://forum.xda-developers.com/showpost.php?p=22758543&postcount=6
Lance Uppercut said:
Before going to your current Rom, did you make a backup of your Gingerbread rom? If so that's what you restore to.
Click to expand...
Click to collapse
yes i did.
have someone try this rom?
http://forum.xda-developers.com/showthread.php?t=1552554
is the stunner... it looks nice...
Was wondering if it is safe to restore NAND backup that was made with CM9 on CM9 recovery?
1st i installed CM9
2nd i made backup
3th i want to change DPI but if something goes wrong can i back up via CM9 or do i have to flash GB and CM9 and start again?
I heard that CM9 is "safe"
I'm wondering too, since I wanted to try MIUI (based on CM9) from CM9, and was thinking of doing a backup if MIUI doesn't do it for me.
My guess is that it's "safe", since once you installed CM9 with the proper instructions (from GB and all), you have a proper CWM, buuuut a second opinion would help.
Neomatt said:
I'm wondering too, since I wanted to try MIUI (based on CM9) from CM9, and was thinking of doing a backup if MIUI doesn't do it for me.
My guess is that it's "safe", since once you installed CM9 with the proper instructions (from GB and all), you have a proper CWM, buuuut a second opinion would help.
Click to expand...
Click to collapse
True that. Well at least BackUp went fine but still have no balls to try restore it. And was wondering also that should i install abyssrecovery (red touch) or can i use stock CWM on CM9...
SoonHD2 said:
True that. Well at least BackUp went fine but still have no balls to try restore it. And was wondering also that should i install abyssrecovery (red touch) or can i use stock CWM on CM9...
Click to expand...
Click to collapse
In my opinion it's safe guys. The problem with the procedures in CWM was mostly caused by Wipes. Also the cf-root kernel was definitely something to be afraid.
Therefore in CM9s' CWM there's nothing harmful.
Sent from my GT-N7000 using Tapatalk 2
SoonHD2 said:
True that. Well at least BackUp went fine but still have no balls to try restore it. And was wondering also that should i install abyssrecovery (red touch) or can i use stock CWM on CM9...
Click to expand...
Click to collapse
Well, since MIUI didn't flash (I need to look more into this), I grabbed my balls and tried the whole backup + restore thing, with the "stock" CWM.
And it all went fine. No loss of data, booting up into CM9 like before, all set.
So it's safe.
Neomatt said:
Well, since MIUI didn't flash (I need to look more into this), I grabbed my balls and tried the whole backup + restore thing, with the "stock" CWM.
And it all went fine. No loss of data, booting up into CM9 like before, all set.
So it's safe.
Click to expand...
Click to collapse
The theory is true again!!!
I told you, there was nothing dangerous there.
Sent from my GT-N7000 using Tapatalk 2
Neomatt said:
Well, since MIUI didn't flash (I need to look more into this), I grabbed my balls and tried the whole backup + restore thing, with the "stock" CWM.
And it all went fine. No loss of data, booting up into CM9 like before, all set.
So it's safe.
Click to expand...
Click to collapse
Good to know. Luckily i dont need to use it yet coz romtoolbox dpi cjange went fine and os booted normally and dpi was changed
So..
I've been playing around for a while with kernels, ROM's and so on... And I've made a decision to return the beast to it's virgin state..
Intentions are as follows;
- Flash Stock GB Firmware (Via PC Odin)
- Format internal / External SD
- Wipe cache / Dalvik
- Update to ICS 4.0.3 (Probably just do it OTA or I have the Odin file)
- Root
- Install Mobile Odin
- Install preferred kernel
From the above, Anyone have any additional advices?
Cheers
you missed out the biggest one, Factory reset :silly: lol
Obviously you just forgot to add it in
But other than that, That sounds spot on ! thats exactly the same procedure I do except reverting to GB you could just wipe on a safe kernel
azzledazzle said:
you missed out the biggest one, Factory reset :silly: lol
Obviously you just forgot to add it in
But other than that, That sounds spot on ! thats exactly the same procedure I do except reverting to GB you could just wipe on a safe kernel
Click to expand...
Click to collapse
I still find it hard to believe there are such things, even the kernel devs hesitantly use the term "SHOULD" ..
And yep, Factory reset should have been included
I dont follow ??
Anyway, Safety is the main thing and if you feel safer reverting to GB then thats fine, it only takes <10mins to flash and could be the difference between a clean note and a bricked note
ive wiped lots of times on my current kernel so i know it to be safe.
azzledazzle said:
I dont follow ??
Anyway, Safety is the main thing and if you feel safer reverting to GB then thats fine, it only takes <10mins to flash and could be the difference between a clean note and a bricked note
ive wiped lots of times on my current kernel so i know it to be safe.
Click to expand...
Click to collapse
You still running NoteCore?
I've got SpeedMod K3-9 installed on the ICS build at the moment but as you say - it's not an epic task and for super safety I'm happier wiping and formatting in GB...
I was until about 5 mins ago lol, Im just in the middle of flashing Staxxtanium
I just fancy a change lol its been a while, no doubt il be back to cleanote tomorrow but i have to satisfy the cravings
azzledazzle said:
I was until about 5 mins ago lol, Im just in the middle of flashing Staxxtanium
I just fancy a change lol its been a while, no doubt il be back to cleanote tomorrow but i have to satisfy the cravings
Click to expand...
Click to collapse
I was looking at that myself after dabbling in the PA World.. let me know what you think..
I sure will !
I really liked PA, But i was new to the Note at the time and liked the S-Pen features and apps, Now i dont really use them as much but only stayed with CleaNote to support the dev (im loyal like that )
But i get these urges to flash (in more ways than one ) and i havent flashed anything except a kernel for a few days now.
OK ran in to an issue - is standard recovery there's no format options available...hmmm
Maybe flash Abyss?
Ahh.. that's right, it's in settings ^o)
yeah flash abyss or any other CWM containing kernel, The stock one is a bag of sh!te
azzledazzle said:
yeah flash abyss or any other CWM containing kernel, The stock one is a bag of sh!te
Click to expand...
Click to collapse
Managed to clear the storage int/ext from settings so will set off on the root to gettin back to where I was..Just without SpeedMod K3-9 as Wi-Fi is unstable on that..
JBroid
Question re: Jbroid Kernel cleaning script..
- Is it worth running following the above?
- If so, can I run it under ICS ( Flash Abyss > Jbroid > Flash Kernel of choice > Reboot)?
Well that went well..
Now jus need to figure out a kernel and I'm "Back in the game"
Hi Guys.
Well, first of all, before someone jumps in and yell at me for such a question, I apologize in advance but I already know that is impossible to do it, but I still have some doubts about what could be some possible solutions for my problem.
In resume, I had my Captivate with Eclair 2.1 Stock rom, I wanted to use CM9, so I took KK4 Stock Rom from this post http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
as requested in the CM Wiki - Captivate Full Update Guide, then flashed mtcarey's Kernel with the ClockworkMod Recovery 5, at that step, before flashing CM9, I made a Nandroid Backup just in case something went wrong, and also because I liked GB, I used GB for about 2 days just to give it a try, then I flashed CM9 and everything worked great.
Now, I have made a Nandroid backup of CM9 too, both backups are in my PC too; And here it comes my problem, I know I cant use CWM to restore KK4 Nandroid Backup, cause I already tried and It throws me an error flashing boot img, and end up in a boot loop, (I think that's pretty normal isn't, Things we need to do to learn ), also, don't know if that's because different CWM versions, cause CM9 comes with a newer version of CWM than the one of mtcarey's kernel.
So, Is there anyway I can take the Stock KK4 Rom and make it CWM compatible?, Or everytime I'd like to get back to GB I'll have to do all the Odin thing, flash mtcarey's kernel again, and then use my Nandroid Backup to really get back, and then keep making Nandroid backups to keep updating my Roms.
BTW, I don't care about apps, Call logs o SMS; I only care about contacts and I have them all in my SIM; And again, apps are ok cause Nandroid backups cover them, and I don't usually have that many apps, just the necessary ones.
Note: I'd like to Switch between this Roms cause, I really like the look of GB, I prefer the Camera app too, and in the 2 days I used it, I don't know if It's just me or not, but I found GB handling my battery more efficiently; And Of course I like CM9 cause has more settings to edit, more customizable, etc.
Thanks in advance!
PS: Sorry I Didn't notice I can't post Questions in this section, can some admin move it to Q&A section? Would be very appreciated.
Once u r running CM or similar, in order to go back to GB Stock firmware or Roms based on that, you must use Odin or Heimdall to flash back to GB...because the partitions are different. Stock firmware = BML/rfs partitions and CM, AOSP, AOKP, MIUI and such like = MTD/ yaffs(2) partitions.
Flashing from GB, froyo, or eclair to CM or the like only requires u to do full wipe and then flash the Rom twice in CWM...first flash in ur current cwm. second flash of rom in that rom's cwm recovery that comes up from first flash.
U can only restore nandroid backups when u r back on that Rom u were on when u made the back up. And u need to be using the same cwm recovery/ kernel u were using when u made said backup.
Sent from my SAMSUNG-SGH-I897 using xda premium
4-2ndtwin said:
Once u r running CM or similar, in order to go back to GB Stock firmware or Roms based on that, you must use Odin or Heimdall to flash back to GB...because the partitions are different. Stock firmware = BML/rfs partitions and CM, AOSP, AOKP, MIUI and such like = MTD/ yaffs(2) partitions.
Flashing from GB, froyo, or eclair to CM or the like only requires u to do full wipe and then flash the Rom twice in CWM...first flash in ur current cwm. second flash of rom in that rom's cwm recovery that comes up from first flash.
U can only restore nandroid backups when u r back on that Rom u were on when u made the back up. And u need to be using the same cwm recovery/ kernel u were using when u made said backup.
Sent from my SAMSUNG-SGH-I897 using xda premium
Click to expand...
Click to collapse
Many Thanks man, well that entirely clear my doubts, I suppose if I just keep using both Roms time to time, of course It wont be every week but so much time more, I just need to keep my Nandroid backups of both Roms, to do all the back-to-stock-flash-again thing and restore the backup and continue using the rom from where I left it... or in any case, switch from CM9 to anther custom ROM... from now I'll stay in CM9 till CM10 reach an stable version.
Again, thanks man, really appreciated.
No prob. :thumbup:
Sent from my SAMSUNG-SGH-I897 using xda premium