Related
i tried to install villianrom and its stuck on a villainrom load screen =[
Wipe and then flash again.
ok i did that, it worked but after i went to CWM and restored my files its stuck at the boot screen again?? do i just keep trying until it works or am i doing it wrong??
Wipe cache and dalvik cache, and try again, you may not be able to restore stuff with cwm, that's what titanium is for.
Nandroid in cmw is more for full system restore.
Sent from my GT-I9100 using xda premium
so how do i restore from titanium if its not on my phone any more after rebooting =s...
ok nvm i got the titanium backup but it cant find my files to restore
edit: nvm im an idiot -_-
Why are you using clockwork to do a restore? ... - - - ...
Earlier today I tried flashing a JB ROM after doing a complete wipe/reset of my ST15i.Data,system,cache wiped.
After getting an error 7 I restored my previous ROM using TWRP but weird thing happened.
All my apps on SD don't work.
No icons in launcher,nothing.
I can see them however in the Downloaded section of the system storage menu.I cannot either run or move them back to phone.I get a message that apps don't exist.
What's happening here?
What can I do?
Restoring another TWRP backup same thing happens.
Fixing permissions didn't help.
N.
Not Sent From My ST15i.
AW: Restoring ROM went wrong?
I've noticed that, too and it's such a f**king problem. TWRP doesn't backup .android_secure (the apps on your sdcard) and when you did the wipe data/factory reset you've wiped that data
I guess there's no way to get your data back, if there is, please tell me (and OP of course). I was lucky because I had a titanium backup from these apps and I could simply restore it
Sent from my Nexus 7 running Android 4.2.1
Re: Restoring ROM went wrong?
That's what I did too.
Not THAT big of a deal,
but a PITA for sure.
N.
Not Sent From My ST15i.
aha. So twrp does have a catch.
thx
that thread really helped me thx
Re: Restoring ROM went wrong?
Try cwm backup and restore option i use that only and cwm is more reliable then twrp
Sent from my WT19i using xda app-developers app
Re: Restoring ROM went wrong?
I can also confirm this by comparing backed up ROM sizes between TWRP 2.3.3.0 and CWM 6.xx recoveries.
N.
Not Sent From My ST15i.
If I take a backup from cwm can I restore it via twrp?
Sent from my Xperia Mini Pro
I think twrp is supposed to back up .android.secure. Try hitting the sd-ext radio button under back up and see what happens.
What's that?
Not Sent From My ST15i.
No it is not possible to restore cwm backup via twrp
Sent from my WT19i using xda app-developers app
I flashed Pacman ROM but before i did i made i made a nandroid backup of my current ROM jellybam 6.6.0 with CWM touch. The ROM did not work so i decided to restore with the backup. However it always gets stuck at data and then says cant restore /data. Please Help
Hassaan.W said:
I flashed Pacman ROM but before i did i made i made a nandroid backup of my current ROM jellybam 6.6.0 with CWM touch. The ROM did not work so i decided to restore with the backup. However it always gets stuck at data and then says cant restore /data. Please Help
Click to expand...
Click to collapse
Restore without data first .
jje
R: [Q] Can't restore /data
Maybe ure using an olther recovery version. i remember i had a restore always go wrong cause something was a bit off in md5 checksum or something was keeping it from restoring anyway, as soon as i updated thru rom manager (or you can get philz recovery) i discovered recovery was theN capable of ignoring error and complete restore.
Sent from my GT-I9300 using xda app-developers app
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!!
guys im trying to fix my friends phone whici is samsung galaxy s2, heres what he did, he was on cynogen mod and then directly went to another rom without changing the bootloader and then he change it again to kitkat rom hoping it would fix things now what i did was first fix the bootloader cause im trying to restore its backup which is the original os 4.1.2 i was able to enter cwm which is 6.0.2.7 now i was able to restore the backup but still on bootloop. any tips?
rarela1234 said:
guys im trying to fix my friends phone whici is samsung galaxy s2, heres what he did, he was on cynogen mod and then directly went to another rom without changing the bootloader and then he change it again to kitkat rom hoping it would fix things now what i did was first fix the bootloader cause im trying to restore its backup which is the original os 4.1.2 i was able to enter cwm which is 6.0.2.7 now i was able to restore the backup but still on bootloop. any tips?
Click to expand...
Click to collapse
Wipe data
Sent from my GT-I9100 using xda premium
Flash stock sammy rom with odin.
If wiping data doesnt work, try flashing kernel. If that doesn't work, flash stock 4.1.2 via odin
Sent from my SGH-I317 using XDA Premium 4 mobile app
i just installed the stock firmware which is 4.1.2 and then tried wipe but theres a message in the system recovery says failed to mount /efs? any clue? thanks in advance.
flash latest philz kernel from here http://forum.xda-developers.com/showthread.php?t=1877270 ,boot to recovery,then restore your efs backup from there(you should have one in your external sd)
Sent from my blazing fast Note 2, running MIUI 5x and pleasantly surprised by it.
just installed philz kernel and went to recovery im searching for restoring the efs but cant find it though. still on bootloop.
i think this phone has other problem already tried 3 different stock firmware for this phone and then go to recovery wipe still on bootloop. tried installing kernel from philz its desame but only thing i noticed is every time i installed a new rom and go to recovery is says failed to mount efs. can it be one of the reason why its on boot loop? and also my friend didnt back up his efs thats why i think this is happening.
do you have a nandroid backup of any previous rom?
yup he has nandroid backup which has on the stock rom but i doubt cause when i installed the stocked rom then installed philz cwm which was 6.0.2.7 i was able to restore the back up but its still on bootloop so i dont know if the cwm is the ones not compatible or the rom.
after you restore your backup do a factory reset in cwm.
now i tried what you said and its showing md5 mismatch when i try to restore.
could be a corrupted backup.did you tried factory reset on your current rom?
argghh im on the blink on giving up on this phone already tried different methods.............
assuming you're now on stock 4.1.2,i suggest you to flash dorimanx 8.43 kernel,,if it doesnt boot,reboot to recovery,do a factory reset.If that doesnt help,try to restore nandroid from this cwm.Of course before restoring do a factory reset and format system and preload partitions.
ayt will try this now!!!
still no luck not working T_T..
you mean you can't restore your backup?And dont forget to wipe cache and dalvik cache when doing factory reset.As for efs,did you looked for it in internal sd too,in clockwork folder?It can be either in tar.gz,img.gz or zip formats.It's stuck at boot probably because of corrupted efs partition.If I remember well,you can restore efs partition from nandroid backup in philz touch cwm.
Have you done a stock samsung rom install usin odin? That should get you back to sqaure 1. If your backup is currupt it will never work.
Sent from my SGH-I317 using XDA Premium 4 mobile app