Hello,
is there any way to restore back my last rom before installing CM10.1
bebo911 said:
Hello,
is there any way to restore back my last rom before installing CM10.1
Click to expand...
Click to collapse
Why do you want to restore your last ROM when you're going to flash CM again??
Please explain more clearly what ROM you are on now, and what you want to do.
immortalneo said:
Why do you want to restore your last ROM when you're going to flash CM again??
Please explain more clearly what ROM you are on now, and what you want to do.
Click to expand...
Click to collapse
Hello
srry for the misunderstanding
if i am running CM10.1 and i want to fallback to my old ROM which is JB4.1.2
how can i do so
Did you make a nandroid bkup before you flashed cm? If not flash stock with odin or flash a custom 4.1.2 based rom through recovery
--------------
alliances+siyah
andrewwright said:
Did you make a nandroid bkup before you flashed cm? If not flash stock with odin or flash a custom 4.1.2 based rom through recovery
--------------
alliances+siyah
Click to expand...
Click to collapse
I have a Nandroid backup before I flashed to CM10.1. Can I just reboot to recovery and restore my jelly bean back up?
Thanks!
Yep as long as you have the preload backed up it will restore
Hi guys, I read on this forum that, in order to do a succesfull restore of nandroid, the restore should be done with the same version of CWM.. but when I flash CM, it overwrite my CWM (6.0.3.7) with the version included in the CM.. so how can I be sure that i can restore from cyano?
I'm sorry if this is a too noob question, but I'm going to do my first flash of a custom rom.. and I want to be sure I can go back!!
albidema said:
Hi guys, I read on this forum that, in order to do a succesfull restore of nandroid, the restore should be done with the same version of CWM.. but when I flash CM, it overwrite my CWM (6.0.3.7) with the version included in the CM.. so how can I be sure that i can restore from cyano?
I'm sorry if this is a too noob question, but I'm going to do my first flash of a custom rom.. and I want to be sure I can go back!!
Click to expand...
Click to collapse
If you have made a Bk up of you're rom with v6.0.3.7 then CM cwm will restore it. BUT do you have a Bk up of you're preload?? If not it won't restore. What rom/firmwear are you on?
Sent from my GT-I9300 using XDA Premium 4 mobile app
andrewwright said:
If you have made a Bk up of you're rom with v6.0.3.7 then CM cwm will restore it. BUT do you have a Bk up of you're preload?? If not it won't restore. What rom/firmwear are you on?
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, thank you for your answer! I am on stock 4.1.2 firmware.. XLSW.. with Philz recovery.. i clicked on "backup preload" in recovery, so I think I had preload in my backup!
Sorry, but another question have just come out: this is also true with the CM11? I heard it needs another version of CWM (6.0.4.x)..
You can look at at you're nandroid in you're sd card to see if it's bked up. Best thing to do to get cm11 is look at Android development and then look for neatrom 4.4.2 and flash the recovery in the first post then REBOOT RECOVERY and then do the wipes and flash rom/gapps in that recovery. To restore you're nandroid just flash philz kernel and then REBOOT RECOVERY! Once you're Bk in philz cwn do the wipes and restore you're nand.
Sent from my GT-I9300 using XDA Premium 4 mobile app
andrewwright said:
You can look at at you're nandroid in you're sd card to see if it's bked up. Best thing to do to get cm11 is look at Android development and then look for neatrom 4.4.2 and flash the recovery in the first post then REBOOT RECOVERY and then do the wipes and flash rom/gapps in that recovery. To restore you're nandroid just flash philz kernel and then REBOOT RECOVERY! Once you're Bk in philz cwn do the wipes and restore you're nand.
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So, to upgrade to KK, I should flash a compatible recovery and then, without trying booting the system, flash the KK rom.. and then to restore my JB nandroid I should flash the philz and, again rebooting directly in recovery, do the restore..
For CM 10.1 to JB I should do nothing instead.. just restore the nandroid from CM recovery.. I understood right?
That's right. Always do the format of system, data, cache and preload before restoring a nand.
Sent from my GT-I9300 using XDA Premium 4 mobile app
andrewwright said:
That's right. Always do the format of system, data, cache and preload before restoring a nand.
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok.. I thought there was no need of wipes before a restore, because it overwrites everything.. but I was wrong!
Thank you very much for your support!! :good:
Any time mate.
Sent from my GT-I9300 using XDA Premium 4 mobile app
Related
I turn the flash Cyanogenmod7 and before I made a backup of the previous rom ... After date wipe, wipe the flash cache and the cel Cyanogenmod7 all good ... As I was driving and could not deal well because I gave him and wipe wipe data cache and gave him back the backup restore I did and then I went back pal rom q na had .......... And now I come home and do the same procedure I did to flash the Cyanogenmod7 and I do not go up
Sent from my GT-I9100 using xda premium
What?
Sent from my GT-I9100 using xda premium
I'm sorry but not speak English - i translated
Sent from my GT-I9100 using xda premium
Could you try another translater?
What languages do you speak? You might find someone who can help you speaking your language.
delbert3mil said:
I'm sorry but not speak English - i translated
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Im not sure if i got what you mean but so far this is what i got:
1. You did a nandroid backup of your old rom (CWM 4)
2. You flashed the Cyanogenmod Stable and everything went well, the Cyanogen worked fine.
3. You did a Cyanogenmod Stable nandroid backup (cwm 5)
4. You restored the old rom (working) from the nandroid backup
5. You wanted to restore Cyanogenmod nandroid backup but you cant'.
So far i discovered CWM 5 can restore old backups (from cwm 4) but when you are in cwm 4, you cant find anymore backups done with cwm 5.
That's the problem is it?
It's just because, you cant resetore a cwm 5 backup, when you go back to cwm 4
I am currently on CM7 RC1 and planning to go back STOCK ROM.
I have my back-up stock rom via CWM. Would it possible if I flashed my stock rom back-up(via CWM) even if I am currently on CM7 ROM?? Please help to verify. Thank you.
droidtwoseven said:
I am currently on CM7 RC1 and planning to go back STOCK ROM.
I have my back-up stock rom via CWM. Would it possible if I flashed my stock rom back-up(via CWM) even if I am currently on CM7 ROM?? Please help to verify. Thank you.
Click to expand...
Click to collapse
Backup your CM7 in case it ****s up .
-Factory reset
-Wipe both caches
-Format /system
-Restore Stock
-Reboot
Sent from my GT-S5830 using XDA App
EmoBoiix3 said:
Backup your CM7 in case it ****s up .
-Factory reset
-Wipe both caches
-Format /system
-Restore Stock
-Reboot
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
Did this but I'm stuck on "GT-S5830 Galaxy Ace" Screen. Please help.
try to wipe caches..
i remember this happened with me also...
download same fresh rom from sammobile and flash it first with odin and try to restore now..
haven't tried this but may work
madman_amit said:
try to wipe caches..
i remember this happened with me also...
download same fresh rom from sammobile and flash it first with odin and try to restore now..
haven't tried this but may work
Click to expand...
Click to collapse
Do you mean ill wipe caches after I restore??
droidtwoseven said:
Do you mean ill wipe caches after I restore??
Click to expand...
Click to collapse
Try flashing Cf-root
Sent from my GT-S5830 using XDA App
EmoBoiix3 said:
Try flashing Cf-root
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
How come this will help?
Do wiping caches after I restore will solved this? Please help to confirm.
I don't want to do Odin for now
Surefire way to work will be to
1.) Factory reset
2.) ODIN flash stock ROM of same baseband
3.) Flash CWM
4.) Flash stock ROM backup
I just want to confirm that I have the same problem: when I restored my stock-rom-backup using CWM from C7.1, the phone got stuck in the same point as droidtwoseven said.
I also confirm that I restored the previous C7.1 and the phone is working now. However, I would like to know how to restore the stock rom from CWM.
I hope we can find a solution because this seems to be a problem that everyone will have.
Maybe the problem has something to do with the partitions that C7.1 creates (I'm not sure about this, I'm just a noob).
Thank you.
davidteleco said:
I just want to confirm that I have the same problem: when I restored my stock-rom-backup using CWM from C7.1, the phone got stuck in the same point as droidtwoseven said.
I also confirm that I restored the previous C7.1 and the phone is working now. However, I would like to know how to restore the stock rom from CWM.
I hope we can find a solution because this seems to be a problem that everyone will have.
Maybe the problem has something to do with the partitions that C7.1 creates (I'm not sure about this, I'm just a noob).
Thank you.
Click to expand...
Click to collapse
It could well be that stock ROMs are based on rfs file system while CM7.1 is based on ext 4. Maybe a script has to be implemented to convert the file system back to rfs. I am just hazarding a guess.
happily1986 said:
It could well be that stock ROMs are based on rfs file system while CM7.1 is based on ext 4. Maybe a script has to be implemented to convert the file system back to rfs. I am just hazarding a guess.
Click to expand...
Click to collapse
This is a critical issue that I would like to resolve. I can assume that I will have to flash a stock rom with ODIN but I am afraid that ODIN will brick my phone because of problems with the partitions/file system (RFS vs EXT4).
I don't really know if installing cyanogenmod7.1 by clockworkmod4-recovery has change my phone partitions so I am not sure if ODIN can restore a stock rom by the usual way.
Any help with this?
Thank you so much!
By flashing with ODIN, system file system will revert do rfs.
Most of the Custom ROMs are running on ext4 now, and I flashed several times back to Stock with ODIN after running a Custom ROM with ext4fs.
story: I was running the original android 4.0.3 everything was ok until I tried to instal busybox and somehow I lost the root so I said why I dont upgrade to the latest version and that what I did but the version I installed (4.0.4 nordic countries) have problems with Bluetooth , camera and video player so I want to downgrade to an older version
Q : is it okay to downgrade
if not I think I can wait for JB if samsung is going to release that any time soon
aminov said:
story: I was running the original android 4.0.3 everything was ok until I tried to instal busybox and somehow I lost the root so I said why I dont upgrade to the latest version and that what I did but the version I installed (4.0.4 nordic countries) have problems with Bluetooth , camera and video player so I want to downgrade to an older version
Q : is it okay to downgrade
if not I think I can wait for JB if samsung is going to release that any time soon
Click to expand...
Click to collapse
Yes, of course it's possible, otherwise people would be stuck if they update and don't like what they flashed.
Sent from the Matrix
thank you for your fast reply
Sent from my GT-I9100 using xda app-developers app
If your having all those issues your probably flashing an incompatible rom or kernel version.
Go to sammoble.com, grab your stock 4.0.4 rom, flash it in ODIN, flash Siyak kernel and then reboot into recovery and wipe data/factory reset.
TheATHEiST said:
If your having all those issues your probably flashing an incompatible rom or kernel version.
Go to sammoble.com, grab your stock 4.0.4 rom, flash it in ODIN, flash Siyak kernel and then reboot into recovery and wipe data/factory reset.
Click to expand...
Click to collapse
but i dont want to wipe so im going back to the older version
How do i know the compatible rom/kernel version my kernel i9100XWLPG
aminov said:
but i dont want to wipe so im going back to the older version
How do i know the compatible rom/kernel version my kernel i9100XWLPG
Click to expand...
Click to collapse
Why not? Surely you made backups of apps/appdata or even a nandroid backup before installing new rom?
If you made app/app data backup simply restore after wiping/flashing new rom.
If you made a nandroid backup simply use app extractor to extract/install apps/appdata to new rom.
You can also backup/restore SMS with SMS Backup from store and your contacts will auto sync when you enter googole account.
If you go back and forth between roms you will keep on running into issues. Plus flashing stock roms in ODIN wipes your apps/app data anyway so its not as if using the wipe data/factory reset in CWM is going to lose your apps as you will have already lost them.
TheATHEiST said:
Why not? Surely you made backups of apps/appdata or even a nandroid backup before installing new rom?
If you made app/app data backup simply restore after wiping/flashing new rom.
If you made a nandroid backup simply use app extractor to extract/install apps/appdata to new rom.
You can also backup/restore SMS with SMS Backup from store and your contacts will auto sync when you enter googole account.
If you go back and forth between roms you will keep on running into issues. Plus flashing stock roms in ODIN wipes your apps/app data anyway so its not as if using the wipe data/factory reset in CWM is going to lose your apps as you will have already lost them.
Click to expand...
Click to collapse
i did a nandroid but ODIN didnt wipe anything what app u recommend me to backup with titanium backup??
aminov said:
i did a nandroid but ODIN didnt wipe anything what app u recommend me to backup with titanium backup??
Click to expand...
Click to collapse
What he meant was that if you flash a rom with Odin, you don't have to do the wipes manually through CWM again.
TB is a good app (and the most used by people as far as I know) to back up your USER apps (don't back up system apps). After flashing you can restore them, even with your app data included.
Sent from the Matrix
Donnie Sins said:
What he meant was that if you flash a rom with Odin, you don't have to do the wipes manually through CWM again.
TB is a good app (and the most used by people as far as I know) to back up your USER apps (don't back up system apps). After flashing you can restore them, even with your app data included.
Sent from the Matrix
Click to expand...
Click to collapse
the problems i was having is because i didn't wipe thnx anyway
Hello guys. I am currently using Slimbean RC1 and I made a backup of my rooted stock 4.0.4 with Siyah kernel so that when I restore my backup anytime in future then will not have any super brick risks. But I have a confusion. Do I need to do a full wipe in CWM before restoring backup? Or it will wipe automatically?
Sent from my GT-I9100 using xda premium
Hey guys,
I have a confusion. Currently on Slimbean rc1 official and don't like this ROM. The graphics are not as good as stock. I do have the backup of stock 4.0.4 with Siyah v5.0.1. If I restore with a wipe first will I lose my efs folder?? I don't see any reason of losing it as it must be there in the backup. And if I flash 4.0.3 or Spain Jellybean 4.1.2 using mobile Odin pro then what are the chances that I will lose efs folder?
Please guide. Thanks in advance.
Sent from my GT-I9100 using xda premium
shahrozeumar said:
Hey guys,
I have a confusion. Currently on Slimbean rc1 official and don't like this ROM. The graphics are not as good as stock. I do have the backup of stock 4.0.4 with Siyah v5.0.1. If I restore with a wipe first will I lose my efs folder?? I don't see any reason of losing it as it must be there in the backup. And if I flash 4.0.3 or Spain Jellybean 4.1.2 using mobile Odin pro then what are the chances that I will lose efs folder?
Please guide. Thanks in advance.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
no u will not lose ur efs folder..
Sent from my GT-I9300 using xda app-developers app
You will not loose it but it is a good idea to have a backup of EFS anyway stuff happens and backups never hurt.
A Backup can save you lots of hassles later
One more thing. Does a full wipe mean format everything including precious folders like efs?
Sent from my GT-I9100 using xda premium
No it does not get formated. By a full wipe do you mean factory reset? If so that is just Data and cache.
If you plan to move between roms often there is a very goos script that wipes all the things you would want to wipe just read and understand first what is does
http://forum.xda-developers.com/showthread.php?t=2100558
What I read about full wipe is:
Factory reset
Wipe cache
Wipe dalvik cache
Format system under mount
I followed these steps with Siyah v5.0.1 while on rooted stock 4.0.4 and that backed up efs folder automatically now am using slimbean. But not sure if I do a full wipe again to install another custom ROM then slimbean kernel will do the backup automatically or not. I want to try cyanogenmod 10.1 now. Please guide.
Sent from my GT-I9100 using xda premium
shahrozeumar said:
What I read about full wipe is:
Factory reset
Wipe cache
Wipe dalvik cache
Format system under mount
I followed these steps with Siyah v5.0.1 while on rooted stock 4.0.4 and that backed up efs folder automatically now am using slimbean. But not sure if I do a full wipe again to install another custom ROM then slimbean kernel will do the backup automatically or not. I want to try cyanogenmod 10.1 now. Please guide.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Format system will wipe your current ROM slicky clean, make a manually back up.
Not sure if it's mandatory or not.
When you change between roms it is always best to wipe that is why some people use wipe scripts as it is easier. Not all kernels or roms will do a backup of efs but it does not change so you just need one good backup every now and again.
If you use a stock based rom on JB like alliance or neat you will have to wipe preload after as well
Sent from my GT-I9100 using xda app-developers app
What if I flash Siyah kernel everytime from cwm recovery and reboot into recovery so that I can wipe fully and freely? :/
One more thing. If I use mobile Odin to flash latest 4.1.2 stock or any other ICS 4.0.3 then would it keep the efs folder intact?
Sent from my GT-I9100 using xda premium
How come you are so worried about EFS? Back it up with HC kTool.
Sent from the little guy
Okay done. One more thing please. If like I have reset my counter to zero using triangle away app and I dont see the triangle anymore when my phone boots up. And now if I flash a stock official firmware like XWLS8 using PC Odin then will the counter increase?
Sent from my GT-I9100
shahrozeumar said:
Okay done. One more thing please. If like I have reset my counter to zero using triangle away app and I dont see the triangle anymore when my phone boots up. And now if I flash a stock official firmware like XWLS8 using PC Odin then will the counter increase?
Sent from my GT-I9100
Click to expand...
Click to collapse
No I don't think it will as you're only flashing official firmware. The counter increases when you flash an insecure kernel via odin. Not sure how counter is affected when installing via CMW
Sent from my GT-I9100 using xda premium
It isn't.
HANDSY said:
Not sure how counter is affected when installing via CMW
Click to expand...
Click to collapse
Hello, Here is my little story, i hope you can help me:
I was testing ROMs and having fun doing this, but i have an issue. At first i had this config:
Mobile : Samsung galaxy S2 - I9100
Base band : I9100XXMS2
Rom : Jelly bean 4.1.2 I9100XWLSW
Kernel : Siyah v6.0 beta5+
I did a nandroid backup using CWM 6.x and then stored the backup on external SD.
I then flashed cyanogenmod, latest nightly from 24/06/2013. Then i did wipe data/wipe cache.
Cyano was working, no issue. I decided to go backup to the stock rom (because i was only testing cyanogen, i dont want to stay with it). So i go back into CWM and do "restore" and then choose my jelly bean backup. Restore is sucessfull!
But after the boot, i'm now stucked in a bootloop at the moment of the samsung animation logo.
I tried another thing, did the wipe data/cache and THEN restore the jelly bean backup. I had the same result: BOOTLOOP.
Do you have any idea what's going on?
I have to mention that i did lots of backup/restore with CWM without issue.
Another thing to mention, i've reseted the flash counter with triangle away during the evening (i dont think there is a link, but i prefer mention it).
Also, i tried to restore the nandroid backup of cyanogenmod (i did one backup for this rom as well), and it's restoring well, so it's not bricked.
Thank you for your help!
Jellybean firmwares use a partition called preload.....I'd say with certainty that cwm didn’t backup this partition.....you have to enable the option before you make the nandroid.....
Without the preload backup, any firmware restore will bootloop.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Hi keith have deleted that post. Lol far to slow. Have you seen that thread for firmware in cwm format. Iv read it and its good but I cant find it now if you cone across it could you pm me a link. Many thanks and have a good day.:thumbup:
I vaguely remember reading something about that too......
I'll have to have another look. ..
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Dont put yourself out mate just if you come across it :thumbup:
I am also in this situation, I made a backup of stock ROM using Philz recovery. Then did a wipe to install new rom. Flashed new westcrip RR zip. Played with it (still on it now...) Then decided I want to go back. Wiped EVERYTHING (data,cache,delvik & fixed permissions.)
Retored backup successfully.
Boot loop.
So now I've had to reflash the RR zip so I can write this!
There is a way round this but it involves being at my computer and I'm out. ..
1.download the official stock firmware from sammobile again (unless u have it already) .
2.Put firmware and latest cwm/philz recovery zip on you phone.
3.Flash firmware with mobile odin (enable everroot).
4.Then goto stock recovery & flash cwm.
5.Then in that recovery find 'advanced restore', then you have the ability to only flash the DATA from your 'bootlooping' backup!
I will probably end up doing this but I'm not home so I'm still looking for a possible way to avoid this long method.
Holla back if anyone finds a quick way...
Sent from my GT-I9100 using XDA Premium HD app
keithross39 said:
Jellybean firmwares use a partition called preload.....I'd say with certainty that cwm didn’t backup this partition.....you have to enable the option before you make the nandroid.....
Without the preload backup, any firmware restore will bootloop.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse
Hello keithross39 and ty for your help.
Are you sure there is an option related to this into CWM? I've never seen this. And i wonder why i have this problem now although i restored jelly bean with sucess in the past? It's weird.
match_stick said:
I am also in this situation, I made a backup of stock ROM using Philz recovery. Then did a wipe to install new rom. Flashed new westcrip RR zip. Played with it (still on it now...) Then decided I want to go back. Wiped EVERYTHING (data,cache,delvik & fixed permissions.)
Retored backup successfully.
Boot loop.
So now I've had to reflash the RR zip so I can write this!
There is a way round this but it involves being at my computer and I'm out. ..
1.download the official stock firmware from sammobile again (unless u have it already) .
2.Put firmware and latest cwm/philz recovery zip on you phone.
3.Flash firmware with mobile odin (enable everroot).
4.Then goto stock recovery & flash cwm.
5.Then in that recovery find 'advanced restore', then you have the ability to only flash the DATA from your 'bootlooping' backup!
I will probably end up doing this but I'm not home so I'm still looking for a possible way to avoid this long method.
Holla back if anyone finds a quick way...
Sent from my GT-I9100 using XDA Premium HD app
Click to expand...
Click to collapse
hello match_stick, ty for your help as well,
I still wonder how to troubleshoot this issue, it's common issue , i've google many things about this.
I dont understand why you have to do all those things, (which i dont want to do), to restore a simple backup, it's supposed to be reliable. I fear nothing's reliable in Android world...
Definitely the 'preload problem'.
I've found the setting by flashing Philz stock kernel (still bootloop). It's inside:
PhilZ Touch 5 CWM Base version: 6.0.3.2
Philz settings=>Custom backup & restore=>Misc Nandroid Settings=> and then tick "Include/preload"
I did the backup with Siyah CWM, and it didnt ask me about this at the backup moment, so i dont know if it's saving this partition automatically/transparently.
I will try now.
Try it out and let me know you break the boot loop!
Sent from my GT-I9100 using XDA Premium HD app
match_stick said:
Try it out and let me know you break the boot loop!
Sent from my GT-I9100 using XDA Premium HD app
Click to expand...
Click to collapse
Bad news, it didn't work. During the advanced restore i saw a message "the preload partition was not saved into this backup"....So i guess the nandroid i did didnt include it automatically! I wonder why. I will try to restore another Jelly bean backup i have on my HDD.
In the meantime i tried to restore an old ICS 4.0.4 nandroid backup and it's ok with this one.
The problematic nandroid backup was done with JB+Siyah 6 beta5+ and it's associated CWM recovery. Is there any special backup settings to tell it to backup the Preload partition? I've never enable/disable such a thing...
EDIT: in the meantime i've read this:http://forum.xda-developers.com/showthread.php?t=2099292&nocache=1
Conclusion, CWM from Siyah is broken for jelly bean. Philz CWM is ok for jelly bean.
As i understand Cyanogen overwrite my /preload partition that was not backed up by CWM from Siyah. This is really bad. Now i'm kinda ****ed.
I have to find a working CWM nandroid done with Philz CWM, then i can restore it properly with Philz CWM. Then i can backup the /preload partition using the cwm script from [email protected] Then i can restore it and remove the bootloop maybe?
God knows....
Sent from my GT-I9100 using XDA Premium HD app
---------- Post added at 04:06 PM ---------- Previous post was at 03:32 PM ----------
I used Philz and I'm still boot loop...
Sent from my GT-I9100 using XDA Premium HD app
In philz you have to set the option to save preload. Why because more phone models dont use preload. Philz isnt just working on i9100. Cwm from dori and siyah dont restore or bk up preload even if you save on philz and restore on cwm 6. Whatever I Was on dori. But you can save with hawkerpauls bkup preload and restore scripts. Reason why you other jb nandroids are restore is because there not using preload.
---------- Post added at 04:24 PM ---------- Previous post was at 04:18 PM ----------
So if no preload was made when nandroid was made on either with siyah dori or philz you will get boot loop. If you did bkup preload and have problems format data system cache and preload. Then wipe dalv cache in advanced restore nand wipe cache and dalv cache and reboot. Still problem wipe/factory reset but nit on or going to any were near ics 4.0.4 :thumbup:
Keith I found it that thread :thumbup:
andrewwright said:
In philz you have to set the option to save preload. Why because more phone models dont use preload. Philz isnt just working on i9100. Cwm from dori and siyah dont restore or bk up preload even if you save on philz and restore on cwm 6. Whatever I Was on dori. But you can save with hawkerpauls bkup preload and restore scripts. Reason why you other jb nandroids are restore is because there not using preload.
---------- Post added at 04:24 PM ---------- Previous post was at 04:18 PM ----------
So if no preload was made when nandroid was made on either with siyah dori or philz you will get boot loop. If you did bkup preload and have problems format data system cache and preload. Then wipe dalv cache in advanced restore nand wipe cache and dalv cache and reboot. Still problem wipe/factory reset but nit on or going to any were near ics 4.0.4 :thumbup:
Keith I found it that thread :thumbup:
Click to expand...
Click to collapse
Questions:
1)Where can i get the package for CWM 6.0.3.2 that is included into Philz, but i want it as standalone! I saw it exists only for galaxy s4, will the package from S4 work on S2?
2)I've tried tons of things to restore the CWM nandroid (the one from backed up with Siyah CWM WITHOUT /preload), with no luck. Finally i used the solution gave by match_stick member (ty dude):
I did the wipes, i flash stock ROM, and went into CWM and advanced restore, restore DATA partition.
What will happen if i just restore DATA without restoring /System? What is exactly into /system?
int0x13 said:
Questions:
1)Where can i get the package for CWM 6.0.3.2 that is included into Philz, but i want it as standalone! I saw it exists only for galaxy s4, will the package from S4 work on S2?
2)I've tried tons of things to restore the CWM nandroid (the one from backed up with Siyah CWM WITHOUT /preload), with no luck. Finally i used the solution gave by match_stick member (ty dude):
I did the wipes, i flash stock ROM, and went into CWM and advanced restore, restore DATA partition.
What will happen if i just restore DATA without restoring /System? What is exactly into /system?
Click to expand...
Click to collapse
I am not sure about the standalone version for that particular version but standalone recovery is available just keep searching harder.
If you just restore /data you're restoring only the apps you installed, /system contains all the core files which makes the OS function. /preload acts as an extension for /system partition, as /system for the S2 is too small to hold all the necessary system files, therefore absence of /preload in a nandroid can cause a bootloop.
Try using the apps "Nandroid Manager" and "Online Nandroid Backup" both by the same developer, these app's will make the life of noobs as well as flashaholics easier, and yeah the backup script of Online Nandroid Backup takes backup of all the usual default cwm partitions and also includes /preload and /efs also.
Sent from my GT-I9100 using xda app-developers app
king_below_my_lord said:
I am not sure about the standalone version for that particular version but standalone recovery is available just keep searching harder.
If you just restore /data you're restoring only the apps you installed, /system contains all the core files which makes the OS function. /preload acts as an extension for /system partition, as /system for the S2 is too small to hold all the necessary system files, therefore absence of /preload in a nandroid can cause a bootloop.
Try using the apps "Nandroid Manager" and "Online Nandroid Backup" both by the same developer, these app's will make the life of noobs as well as flashaholics easier, and yeah the backup script of Online Nandroid Backup takes backup of all the usual default cwm partitions and also includes /preload and /efs also.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Ok. /system is read only partition. So if i install the stock ROM /system should be the same than the /system i had from my nandroid backup, is it right? So if i install the stock and rom and do advanced restore and select the /data partition, it should be the same than restoring the entire nandroid backup. Right or wrong? That's what i did and it's working. Install the stock rom didnt restore the /preload partition, but maybe it's creating one with default parameter. Anyway, not restoring /preload doesn't seem to be an issue with /data restore.
About CWM 6.0.3.2 standalone package,i found this:
http://forum.xda-developers.com/showthread.php?t=2201860
I ask about that CWM version, because i know only the latest version customized by Philz supports the /preload backup (as non default option). As Philz say it's the only recovery that is supporting full JB migration/restore.
Thanks .. Now will always remember to keep Include Preload checked before Nandroid
match_stick said:
I am also in this situation, I made a backup of stock ROM using Philz recovery. Then did a wipe to install new rom. Flashed new westcrip RR zip. Played with it (still on it now...) Then decided I want to go back. Wiped EVERYTHING (data,cache,delvik & fixed permissions.)
Retored backup successfully.
Boot loop.
So now I've had to reflash the RR zip so I can write this!
There is a way round this but it involves being at my computer and I'm out. ..
1.download the official stock firmware from sammobile again (unless u have it already) .
2.Put firmware and latest cwm/philz recovery zip on you phone.
3.Flash firmware with mobile odin (enable everroot).
4.Then goto stock recovery & flash cwm.
5.Then in that recovery find 'advanced restore', then you have the ability to only flash the DATA from your 'bootlooping' backup!
I will probably end up doing this but I'm not home so I'm still looking for a possible way to avoid this long method.
Holla back if anyone finds a quick way...
Sent from my GT-I9100 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks this Helped!!