Trying to create a nandroid backup in cement v4... (running uckj3, with boog's kj3 kernel) and every time i boot into recovery and perform a backup it gets stuck at "backup sd-ext" kinda confused as to why this is happening, also can't get the kj3 extended power menu to work, flashed the zip maybe 5 times, cleared the cache/dalvik cache and nothing, any and all suggestions are greatly appreciated. Thanks guys.
Sent from my SAMSUNG-SGH-I897, named Ginger, using XDA App.
The nandroid backup is not yet working in the Gingerbread Roms.
The extended power menu is for Deodexed Roms only.
Hope this info proves helpful.
update
Okay, so I was thinking about why it wasn't working and went to my clockworkmod folder on the SD and saw that the files were pretty large in size, all totally over 4 FBI, so i deleted some miscellaneous files to free up some additional space and tried to run cement backup again... still took a while and did think it got stuck again, but it actually finished..could i safely assume that it worked or should i not trust the files? Also, the more i think about it, do i really need a Nan backup? Meaning, if anything goes wrong with my phone i can always reflash stock and use titanium backup to restore my apps...any thoughts?
Like I said before, the Nandroid Backup does not work in the Gingerbread world. It may look like it is backing up but the restore part won't happen. If u try u may soft brick.
And yes, the fail safe is that you could always return to a Gingerbread stock of your choice and use Titanium Backup to restore your stuff.
nandroid works on gingerbread, just not I897 kernels. I9000 works fine.
although i don't use them personally.
^ Thanks for the clarification. I didn't realize that about the i9000 because I am always on i897.
It's amazing what is being accomplished on captivate kernels, reverse engineering and building "blind" but nothing beats having source code to work with, which is why the I9000 nandroid works.
So how can I tell if I'm running an I897 or I9000? Currently using UCKJ3 with boogs kernel and just flashed the samurai kernel
Sent from my SAMSUNG-SGH-I897 using XDA App
that is I897.
I897 firmwares usually start with a K
I9000 usualy a J
it will also usually say in the op of the thread...
Related
Silly noob-like question, but I wanted to make sure before I continued messing with my phone.
Does ROM Manager back up EVERYTHING on the phone? For example, I backup my rom. Move the backup file onto my pc. Then I screw around with roms, lag fixes, etc. and totally screw it up. If I "restore" the backup made by ROM Manager, will all my apps, settings, desktop, data files, etc be exactly as they were before I started screwing around?
Or, would I need to use Odin to load the same ROM as that which was backed up and then run Rom Manager Restore?
Thanks!
Yes it does
Sent from my SAMSUNG-SGH-I897 using XDA App
Here's another question regarding this thread:
I have the lagfix mod which uses the internal sdcard. When I create a backup will it and restore exactly how it was including the lagfix partition? If yes, is it the same procedures or do I have to do it a different way with the extra partition?
Thanks in advance.
Deca4 said:
Here's another question regarding this thread:
I have the lagfix mod which uses the internal sdcard. When I create a backup will it and restore exactly how it was including the lagfix partition? If yes, is it the same procedures or do I have to do it a different way with the extra partition?
Thanks in advance.
Click to expand...
Click to collapse
Actually I am trying to figure out the same thing. I made a backup before I started messing around with lag fixes, different roms and so forth. Then the other day I tried to restore a rom it didn't work. Eventually I soft bricked the phone and had to make the USB Jig to get it working again. Needless to say I am very intrigued with what exactly Rom Manager does backup and its limitations but I can't seem to find it anywhere. I am thinking the reason my backup was screwed up was because of a lag fix, only problem is I can't remember what lag fix I had on it when I did the initial recovery.
Something from my experience to add here:
Scenario 1:
-----------
I backed up the original 2.1 JH7 on my phone.
Installed 2.2 custom ROM, and played around with it.
Backed up 2.2 ROM.
Messed up with my 2.2 custom ROM.
Went to ROM manager recovery, and recovered the backed up 2.1 JH7, and ended up messing up. My phone didn't even boot up.
Then I went back to recovery, and tried restoring the backed up version of 2.2.
Phone booted up into 2.2, but, started giving a lot of FCs.
Scenario 2:
-----------
Installed 2.2 custom ROM 1.
Backed it up.
Messed it.
Restored it - worked fine.
Installed 2.2 custom ROM 2.
Backed it up.
Restored the 2.2 custom ROM 1.
Everything working fine.
Looks like as long as the core OS is of the same version, it seems to work.
Maybe there is something in the boot sequence that's probably not being restored (???)
---------------
Edit: I do not have CWM app installed. I use the CWM update.zip recovery manager since its the least intrusive way.
diablo009 said:
Something from my experience to add here:
Scenario 1:
-----------
I backed up the original 2.1 JH7 on my phone.
Installed 2.2 custom ROM, and played around with it.
Backed up 2.2 ROM.
Messed up with my 2.2 custom ROM.
Went to ROM manager recovery, and recovered the backed up 2.1 JH7, and ended up messing up. My phone didn't even boot up.
Then I went back to recovery, and tried restoring the backed up version of 2.2.
Phone booted up into 2.2, but, started giving a lot of FCs.
Scenario 2:
-----------
Installed 2.2 custom ROM 1.
Backed it up.
Messed it.
Restored it - worked fine.
Installed 2.2 custom ROM 2.
Backed it up.
Restored the 2.2 custom ROM 1.
Everything working fine.
Looks like as long as the core OS is of the same version, it seems to work.
Maybe there is something in the boot sequence that's probably not being restored (???)
---------------
Edit: I do not have CWM app installed. I use the CWM update.zip recovery manager since its the least intrusive way.
Click to expand...
Click to collapse
Interesting, it would makes sense in what you are saying. My error that I go was when I went from my original JH7 backup, installed a rom based on JH6 and then tried to install my original backup. I might have to try JH6 roms and see if I can restore to them easily or not. I will have to wait for Micro USB cables to come in as I don't have a spare since I used my only cable to make the JIG.
The kernel and modem aren't backed up, so if your backups use different ones and you try to restore them you'll have issues.
I herd a rumor that rom manager doesn't work with froyo on the captivate. But I could be totally wrong.
Sent from my SAMSUNG-SGH-I897 using XDA App
peachpuff said:
The kernel and modem aren't backed up, so if your backups use different ones and you try to restore them you'll have issues.
Click to expand...
Click to collapse
This is what I have read about it as well
Voodoo
There is also a different version of CWM Recovery (what Rom Manager uses to back things up) for the voodoo lag fix.
tnerb123 said:
I herd a rumor that rom manager doesn't work with froyo on the captivate. But I could be totally wrong.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It works. I backed up and restored a few variants of Froyo ROMs.
peachpuff said:
The kernel and modem aren't backed up, so if your backups use different ones and you try to restore them you'll have issues.
Click to expand...
Click to collapse
How do I backup these? Is there any way?
If Ron Manager does backup the kernel and modem why would so many people have problems restoring back to different Roms? This is why I am so puzzled with this software.
Sent from my SAMSUNG-SGH-I897 using XDA App
Rom Manager can backup EFS folder ??
i lost my imei and the only backup that i have its from Ron Manager
Absolutely it does there!
Maybe I'm old fashioned, but best bet is backup from recovery. Saves everything down to browser login data. Can't go wrong with a full backup! I make one every time I flash just about anything.
Sent from my SGH-I897 using xda app-developers app
Rom Manager vs CWM Recovery
yes Rom Manager can do backup of phone..but why not just do
a Nandroid Backup from CWM Recovery..
never had problem with Nandroid Backup from CWM Recovery :victory:
dobi3 said:
yes Rom Manager can do backup of phone..but why not just do
a Nandroid Backup from CWM Recovery..
never had problem with Nandroid Backup from CWM Recovery :victory:
Click to expand...
Click to collapse
Agreed!
Sent from my SGH-I897 using xda app-developers app
So I have tried many times to restore my phone from a backup made by recovery manager, but it never seems to work. It will always make it to the desktop, but either restart constantly or everything will constantly crash making it unusable. Is there something I'm doing wrong?
Sent from my SAMSUNG-SGH-I896 using XDA App
Is your back up the same base as what toy are on. Meaning 2.1 to 2.1. Are you trying to restore a stock backup over 2.2?
mcord11758 said:
Is your back up the same base as what toy are on. Meaning 2.1 to 2.1. Are you trying to restore a stock backup over 2.2?
Click to expand...
Click to collapse
No. The ROM I was running when doing the backup was Serendipity 3.0. I flashed back to Serendipity 3.0, then ran my restore. Everything constantly crashes.
EDIT: I've found uninstalling and reinstalling the applications works, but then there's no point in making a nandroid backup. I might as well just flash back to the ROM I was on and use TiBu in that case.
Anyone else have any ideas?
I'd really like to experiment more with ROMs and custom projects, but I don't want to unless I can basically go back to what I had with one click.
Get titanium backup pro. lts $5, but well worth it. Everything restores with one click.
Sent from my SAMSUNG-SGH-I897 using XDA App
sixstringsg said:
Get titanium backup pro. lts $5, but well worth it. Everything restores with one click.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yeah, I guess I'll just backup absolutely everything with TiBU Pro and keep the installation files around for each ROM, since CWM backups do not seem to work properly.
Auridran said:
Yeah, I guess I'll just backup absolutely everything with TiBU Pro and keep the installation files around for each ROM, since CWM backups do not seem to work properly.
Click to expand...
Click to collapse
CWM backups work fine as long as you have matching firmware versions (2.1-2.1, 2.2-2.2, or 2.2.1-2.2.1)
also you need to be aware of lagfixes in the rom that you may currently be running, they are not always compatible between roms
nandroid does not backup your kernel or modem which is why you need to be moving within the same firmware versions
you cant make a stock nandroid backup, flash a 2.2 rom, then restore from that backup immediately. you will need to do a couple of things first.
keep a stock 2.1 cwm flashable kernel and modem on your sdcard
revert any lagfixes your phone may have prior to trying to restore your nandroid of stock
once lagfixes are removed, flash your kernel and modem (same firmware version as your nandroid backup)(its possible to have this set up within ONE zip file)
once you are rebooted back into CWM, restore your nandroid...reboot and profit
Pirateghost said:
CWM backups work fine as long as you have matching firmware versions (2.1-2.1, 2.2-2.2, or 2.2.1-2.2.1)
also you need to be aware of lagfixes in the rom that you may currently be running, they are not always compatible between roms
nandroid does not backup your kernel or modem which is why you need to be moving within the same firmware versions
you cant make a stock nandroid backup, flash a 2.2 rom, then restore from that backup immediately. you will need to do a couple of things first.
keep a stock 2.1 cwm flashable kernel and modem on your sdcard
revert any lagfixes your phone may have prior to trying to restore your nandroid of stock
once lagfixes are removed, flash your kernel and modem (same firmware version as your nandroid backup)(its possible to have this set up within ONE zip file)
once you are rebooted back into CWM, restore your nandroid...reboot and profit
Click to expand...
Click to collapse
Well like I said, I made a backup on my Serendipity 3.0 ROM I had going, flashed to something else, then even flashed back to Serendipity 3.0 before restoring and it still didn't work properly. All the apps I had installed just force-closed until I reinstalled them, or force-closed somewhere during use.
Sorry if this has been asked before but I have searched and didn't find any answers.
I have never been able to restore a nandroid backup on the Galaxy S. I go through the restore procedure in recovery and everything seems to restore correctly, no errors reported, says restore successful, but when the phone boots up from recovery it hangs on the boot screen.
I've tried with lots of different roms/kernels. I've wiped thoroughly before restoring. I'm even trying to restore from the same version, i.e. JVH or JVP, always the same result. I'm not trying to restore between cm7/samsung roms or froyo/gingerbread or even different versions. An example is, I was on Darky 10.1re. I did a nandroid. I tried a few other roms (F1, GingerReal, Tweaky), tried to nand back to Darky's, appears to restore without problems until the reboot where it hangs on boot screen. Also tried to restore to nadroids of the above roms with the same results.
Can anyone tell me where I'm going wrong, I'm sure I'm missing something really obvious as nobody else seems to be having trouble with backups.
Thanks.
I could imagine it would be hard to point out what the exact problem is, unless someone has experienced this issue before. Which I haven't, sorry. Not on my SGS, nor on my SGS2. But it sounds like a compatibility problem to me. You say you've never been able to restore, have you had the same problem with Darky ROMs prior to 10.x, perhaps 9.5? Have you used Darky's Dark Core kernel along with it?
The same thing is happening to me. Used to nandroid restore on froyo and never had a problem. The last 2 times that I tried to restore (with Ginger 2.3.3 and 2.3.4) I had problems, both times with Criskelo´s rom and Darkcore Kernel. The restore begins normally but suddenly stops and there is no way to revert the semi-brick other than odin. BTW, I never use lagfix.
Used nandroid backup and restore successfully on gingerbread on both speedmod and galaxian kernels
Sent using geek power
I have same problem and i ended using nandorid backup which is very usefull.
I think this started at beginning of Gingerbread kernels using.
bitmaster2000 said:
I could imagine it would be hard to point out what the exact problem is, unless someone has experienced this issue before. Which I haven't, sorry. Not on my SGS, nor on my SGS2. But it sounds like a compatibility problem to me. You say you've never been able to restore, have you had the same problem with Darky ROMs prior to 10.x, perhaps 9.5? Have you used Darky's Dark Core kernel along with it?
Click to expand...
Click to collapse
Thanks for your suggestions. The first rom I installed after buying my Galaxy S was the current Darky one at the time, v10 rc something. Didn't try the older ones. At first I always used the Dark Core kernel, even with other roms. Still couldn't restore.
I've also tried a mixture of roms/kernels since then with no luck with the nandroid.
Could it be something to do with the recovery? I noticed different roms/kernels install a different recovery. Maybe it's only possible to restore using the same recovery as was used to take the backup? But if this was the case, surely other people would be having the same problem?
Thanks.
eggshaped said:
Thanks for your suggestions. The first rom I installed after buying my Galaxy S was the current Darky one at the time, v10 rc something. Didn't try the older ones. At first I always used the Dark Core kernel, even with other roms. Still couldn't restore.
I've also tried a mixture of roms/kernels since then with no luck with the nandroid.
Could it be something to do with the recovery? I noticed different roms/kernels install a different recovery. Maybe it's only possible to restore using the same recovery as was used to take the backup? But if this was the case, surely other people would be having the same problem?
Thanks.
Click to expand...
Click to collapse
Darky kernel had a restore problem once but they solved it now.
"Changelog 2.5:
Fixed Nandroid Restore through CWM" from darky forum.
yken said:
Darky kernel had a restore problem once but they solved it now.
"Changelog 2.5:
Fixed Nandroid Restore through CWM" from darky forum.
Click to expand...
Click to collapse
Yes I remember reading about that. That's what I put it down to in the beginning, but now it's been fixed and it still doesn't work for me. Not even with other kernels.
Well, it's not the end of the world I suppose. Just makes me more reluctant to try different roms as I'm too lazy to go through the whole odin/flashing/restoring process every time lol.
Thanks for your suggestions guys
With Dark Core kernel 2.7.x and 2.8 i have the same problems when i'm on rfs, backup function is ok but restore doesn't work. With ext4 conversion enabled backup and restore work as they should.
I've found a solution, just in case anyone else is having the same problem this is how I got around it.
I downloaded and installing the latest cwm using Rom Manager, so any backups are taken on 3.0.0.5. When changing roms I had to download and install the same recovery with Rom Manager and restore using the same 3.0.0.5. For some reason it only works when using rom manager. If I try to restore manually in recovery it doesn't work. If I try to restore with any other recovery version it doesn't work. So for me my nandroid backups only restore between the exact same recovery versions.
Sounds fairly obvious now, after thinking about it lol, but this has been giving me a major headache for weeks now.
I used AdamOutler 's guide to root and put a custom ROM on Captivate 2.2 found here:
http://forum.xda-developers.com/showthread.php?t=1012769
And everything went swiftly. AT THIS POINT, I MADE A NANDROID BACKUP
I then wanted to step up to an Ice Cream Sandwich ROM, which was the main purpose of my rooting in the first place. So, I downloaded the ROM found in this forum, as it is the most popular amongst the forums, so to seem. I found it here:
http://forum.xda-developers.com/showthread.php?t=1363760
Well I downloaded the ROM straight from my phone on the browser, then put it on the Root of my internal memory.
I booted into recovery, Factory Reset/Wipe Cache Partition/Wipe Dalvik Cache.
Went to install .zip from SD card, then clicked on install the ICS ROM.
Began to seem as if it was updating, then the phone shut off, started bootlooping.
No big deal I thought, just boot into recovery, right? I booted into recovery. It went from the Red CWM that i had seen before, to a Blue one.
I selected my nandroid backup, and it gave me all sorts of errors.
Got to the point where CWM was acting as if it could even find where it was supposed to work from?
Now I have the Phone>!<Computer on the black screen when I try to turn on.
Anyone else ever had this problem, or could someone tell me what went wrong? Not in a huge rush as this is just my development phone, but do I need to go ahead and use the Odin3 One Click to do a full complete restore or is there any way of saving what I had?
Thanks guys, God Bless.
LOL OOPS thought i was in the dev section.... ignore..help below.
xCaptivateRx said:
I used AdamOutler 's guide to root and put a custom ROM on Captivate 2.2 found here:
http://forum.xda-developers.com/showthread.php?t=1012769
And everything went swiftly. AT THIS POINT, I MADE A NANDROID BACKUP
I then wanted to step up to an Ice Cream Sandwich ROM, which was the main purpose of my rooting in the first place. So, I downloaded the ROM found in this forum, as it is the most popular amongst the forums, so to seem. I found it here:
http://forum.xda-developers.com/showthread.php?t=1363760
Well I downloaded the ROM straight from my phone on the browser, then put it on the Root of my internal memory.
I booted into recovery, Factory Reset/Wipe Cache Partition/Wipe Dalvik Cache.
Went to install .zip from SD card, then clicked on install the ICS ROM.
Began to seem as if it was updating, then the phone shut off, started bootlooping.
No big deal I thought, just boot into recovery, right? I booted into recovery. It went from the Red CWM that i had seen before, to a Blue one.
I selected my nandroid backup, and it gave me all sorts of errors.
Got to the point where CWM was acting as if it could even find where it was supposed to work from?
Now I have the Phone>!<Computer on the black screen when I try to turn on.
Anyone else ever had this problem, or could someone tell me what went wrong? Not in a huge rush as this is just my development phone, but do I need to go ahead and use the Odin3 One Click to do a full complete restore or is there any way of saving what I had?
Thanks guys, God Bless.
Click to expand...
Click to collapse
Different kernels have different colour recoveries. kernels change with rom.
Different CWM version recoveries are incompatible.
Almost anyone that has flashed a samsung galaxy phone has seen that screen, and it is correctly written " Phone /!\ PC " (you can choose to underline the /!\ if you want to be fancy). it is called the "soft brick screen" hint hint.. go search.
yes
yes. restore with same kernel you used to back it up.
TRusselo said:
Different kernels have different colour recoveries. kernels change with rom.
Different CWM version recoveries are incompatible.
Almost anyone that has flashed a samsung galaxy phone has seen that screen, and it is correctly written " Phone /!\ PC " (you can choose to underline the /!\ if you want to be fancy). it is called the "soft brick screen" hint hint.. go search.
yes
yes. restore with same kernel you used to back it up.
Click to expand...
Click to collapse
Very good responce...however after odin3 one clicking back to stock 2.1 eclair, I lost my clockwork mod folder that was on the internal SD, of course. Rookie mistake, I should've definately copied it on to the external SD card. Thanks for informing me of proper terminology. Also, after downloading rom manager and flashing, booting recovery, I can only access cwm through the rom manager, the three button fix doesn't work.
Why was this moved? I posted in general..
because you have a question/problem
rom manager is only used with 2.1 (for captivate). doesnt work on 2.2 or 2.3.X or 4.0.X
in all newer versions of android we "bake" cwm into the custom kernels we package into the custom roms. so there is no stock recovery and you dont need the update.zip.
dunno why you would flash all the way back to 2.1... EWWW.
in the dev section there is a sticky called odin master collection. use a newer stock rom. the master collection also has stocks versions, pre-packcaged with a custom cwm kernel so you can skip a step of getting it after going back to stock.
Do we know why this happened in the first place? Incompatible kernel? Is there a guide somewhere for moving from GB to ICS?
Sent from my SGH-I897 using XDA App
I thought you had to have GB bootloaders before you flashed any ICS roms ? I know I've read that ,then again I've read 10,000 threats and sometimes it becomes mind numbing.
Do you not have to flash back to 2.1 after having these problems? Right now my phone is at the soft brick screen, no button combo working. Not recognized by the computer either. I'm heading out to radio shack and make a USB jig in a bit. I'd love to just flash straight up to a gingerbread ROM if I can possibly get this thing in download mode. Anybody help a brotha out!
Edit: the sim is not activated, I just run it off Wi-Fi because big red is my carrier. This is my development phone. So I can't just KIES update to whatever the newest is.
Sent from my DROID X2 using XDA App
Any firmware should work, no need to go all the way to eclair...just flash gingerbread.
Don't think its been mentioned yet but when going from 2.2 to ICS, you have to flash the rom twice to get out of the bootloops. Sounds like you were at that point but when you flashed your nandroid instead of the ICS rom again, your phone must not have liked it.
aww.W.T.F? said:
I thought you had to have GB bootloaders before you flashed any ICS roms ? I know I've read that ,then again I've read 10,000 threats and sometimes it becomes mind numbing.
Click to expand...
Click to collapse
Not all ICS ROM's require GB bootloaders. I ran THS, and am now on vibranturk's AOKP and I came straight from 2.1
I think the issue was you're supposed to flash them twice. Well that fixed it for me. I dkbhave the gingerbread boot loaders now though
Sent from my SGH-I897 using xda premium
I went from bone stock Froyo 2.2 straight to THS ICS with no problems whatsoever. So some ICS Roms doesn't need GB bootloaders.
Sent from my SGH-I897 using xda premium
I'm on the same situation as the original poster: I'm on andromeda3 and now I want to upgrade to ICS. Right now my captivate has cwm 2.5.1.2 can I flash any ICS mod from there or do I need to do something else?
See this.... TRusselo's "Guide..." that is a Stickied Thread in the Q & A Forum.
I believe u will need the Gingerbread Bootloaders...
Sent from my SAMSUNG-SGH-I777 using xda premium
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