Related
So, I have been having some major problems with my phone. Tons of force closes, major lag times and things like that. I have tried a handful of different ROMs, including CM7, the nightlys, Miui and a few others. I hear great stories about people and rooting and I want to be one of them. I am tired of all the hassles. So, when talking to someone in the office who has had no issues with his Droid 2, he suggested, and said he has read, the best thing to do is go back to stock, unroot, as they will remove all possible conflicting files that could be causing problems. Then, re-root, and install whatever.
Any thoughts on that? Generally, my process for installing a new ROM, I boot into recovery manually, clean cache, clean Dalvik, then install ROM. Then, I restore apps and data from Titanium and restore the Nandroid from Rom Manager. The past couple times, I have done the factory reset, but eventually, a day or 2, it goes back to the same problems. Maybe, I should just try it without the restoring the Nandroid (even though it is a backup from when there was no problems) and the app data from Titanium. I assume, you know what happens when you assume, that both the Nandroid and Titanium backups are clean as I backed up when I was having no issues.
So, any thoughts here? Unroot, then re-root or is there something else I should try to wipe everything clean to solve the problems? Currently, on the original Droid Incredible (got it on the release day, so the first screen), running 2.2 when I rooted, currently on Miui 1.9.16, but just installed it 10 minutes ago and was running the Cyanogen nightly's before hand..
Thanks in advance
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
Try not restoring apps and data from Titanium, as restoring the app is okay, but restoring data can cause unwanted things to happen more times than not.
When you say restore nandroid from ROM Manager, what do you mean here? A nandroid is backing up your ROM via ROM Manager, which gets stored to your clockworkmod/backups folder...you shouldn't be pulling anything from that...
If you flash the RUU to return to stock and re-root, make sure you use the 2.2 RUU. If you use the 2.3, you need to be s-off to get rooted again. If you use the 2.3 RUU and you're s-on, no root for you...come back one year.
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
As for Titanium, I restore apps with data all the time, but system data should almost never be restored as it's OS and app version specific. Basically, if it's green, it's safe. If it's red, don't mess with it. If it's white, like a user app, app and data are usually safe to restore.
ROM Manager is a bigger pain in the ass than it's worth and is useless for anything more than flashing a new recovery. If my recovery is working reliably, I never install ROM manager. Most devs will tell you to never flash with ROM manager anyways. Any function that ROM Manager performs can be performed in recovery in a safer, more reliable fashion.
loonatik78 said:
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
As for Titanium, I restore apps with data all the time, but system data should almost never be restored as it's OS and app version specific. Basically, if it's green, it's safe. If it's red, don't mess with it. If it's white, like a user app, app and data are usually safe to restore.
ROM Manager is a bigger pain in the ass than it's worth and is useless for anything more than flashing a new recovery. If my recovery is working reliably, I never install ROM manager. Most devs will tell you to never flash with ROM manager anyways. Any function that ROM Manager performs can be performed in recovery in a safer, more reliable fashion.
Click to expand...
Click to collapse
Thanks for the correction, I forgot to put system in there...restoring system data is not good.
+1 on ROM Manager issues, always get a zip file of the ROM, and flash through recovery.
RMarkwald said:
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
When you say restore nandroid from ROM Manager, what do you mean here? A nandroid is backing up your ROM via ROM Manager, which gets stored to your clockworkmod/backups folder...you shouldn't be pulling anything from that....
Click to expand...
Click to collapse
That is pretty much what I do, except for the Mounts and Storage parts.
For the Nandroid part, maybe I have my terminology mixed up. I do a restore from Rom Manager...which I thought was called the Nandroid backup. It seems to me, that it makes sure the launcher and things are set up right.
loonatik78 said:
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
Click to expand...
Click to collapse
I rarely use the ROM Manager to do anything, just restore (what I thought was called the Nandroid) to make the launcher the way things were..
But it seems like that is my problem. I am installed the new ROM, then just restoring a back up of all the problems. DUH.. Guess I should try it all without restoring anything from the ROM Manager and see how it all works. That will be my project tonight..
Thanks
MikeDaub said:
That is pretty much what I do, except for the Mounts and Storage parts.
For the Nandroid part, maybe I have my terminology mixed up. I do a restore from Rom Manager...which I thought was called the Nandroid backup. It seems to me, that it makes sure the launcher and things are set up right.
I rarely use the ROM Manager to do anything, just restore (what I thought was called the Nandroid) to make the launcher the way things were..
But it seems like that is my problem. I am installed the new ROM, then just restoring a back up of all the problems. DUH.. Guess I should try it all without restoring anything from the ROM Manager and see how it all works. That will be my project tonight..
Thanks
Click to expand...
Click to collapse
If you want to restore your launcher, try it through Titanium Backup. If that doesn't do it, and I can't promise you it will work correctly, you're probably SOL on restoring a launcher unless some other backup app does the job better.
loonatik78 said:
If you want to restore your launcher, try it through Titanium Backup. If that doesn't do it, and I can't promise you it will work correctly, you're probably SOL on restoring a launcher unless some other backup app does the job better.
Click to expand...
Click to collapse
I am fine with not restoring it, I just thought "that is what you should do".
I don't venture too far from the regular settings, so it isn't a pain to do, just thought I should...
RMarkwald said:
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
Click to expand...
Click to collapse
One more quick question since I am thinking of it....is this same process if doing nightly updates from Cyanogen, or just is I change from say, Cyanogen to Miui or something??
Thanks again for all the help..
MikeDaub said:
One more quick question since I am thinking of it....is this same process if doing nightly updates from Cyanogen, or just is I change from say, Cyanogen to Miui or something??
Thanks again for all the help..
Click to expand...
Click to collapse
Generally, CM nightlies can be flashed over top of each other without a wipe since the vast majority of the code is identical. However, if an issue crops up, a wipe and flash might be a good thing to try. Probably won't help though, since nightlies, by definition, are experimental.
Always wipe and flash when moving from one ROM type to another.
loonatik78 said:
Generally, CM nightlies can be flashed over top of each other without a wipe since the vast majority of the code is identical. However, if an issue crops up, a wipe and flash might be a good thing to try. Probably won't help though, since nightlies, by definition, are experimental.
Always wipe and flash when moving from one ROM type to another.
Click to expand...
Click to collapse
That's kinda what I figured, but I thought it was worth asking so I don't completely wipe the whole thing every time I install an update. The nightly I am on now seems to be working, so the new plan is keep whats working until it doesn't work anymore, or some major update comes along..
Thanks again for the help. I really appreciate it.
If the issue continues you can try copying everything off of your SD card to your PC and reformatting your SD card. Remember to use FAT32 format. Then copy everything back to your SD card. I've read threads were this helped the force close issues for many people - Just a thought.
jackbtha1 said:
If the issue continues you can try copying everything off of your SD card to your PC and reformatting your SD card. Remember to use FAT32 format. Then copy everything back to your SD card. I've read threads were this helped the force close issues for many people - Just a thought.
Click to expand...
Click to collapse
Certainly worth a thought. The card that is in it now came from a different phone. I am pretty sure I formatted it when I first plugged it in, but it can't hurt to try...
Thanks
few days ago I just flashed cwm recovery and made a backup for every partition, after that I flashed the cm7.2.
but now when I want to go back to stock, I cannot restore the backup. it seemed that the recovery cannot format the partitions into rfs. (even I used the rfs+ext4 recovery)
anyone has any ideas?
Did you have an ext4 partition when you did the backup? I've experienced problems with the CWM backup a couple of times because it's not getting along well with ext4 partitions so I had to go from scratch a couple of times because I couldn't do a restore. For Galaxy Gio, I would recommend you to use Titanium Backup instead of CWM Recovery from now on if don't want to get into trouble with backups and stuff.
Just flash a new firmware via ODIN.
LegoGabi said:
Just flash a new firmware via ODIN.
Click to expand...
Click to collapse
thanks for replies but my original firmware contains chinese which cannot available here
Try this:
1) flash some stock multi-package firmware (that would format your FS to rfs from ext4); shouldn't matter much what firmware you flash, just something Gingerbread-ish to allow CWM to work, as you only need it to format partitions
2) flash CWM (or install via update.zip method from recovery) that works with stock firmware (I believe it's the one with rfs+ext4 support but you better check in CWM thread)
3) restore your stock ROM backup
Have you checked Samsung firmware websites like samfirmware to see if they had yours?
If not, there are instructions here on creating an Odin flashable backup, which you could do if you have access to another, unmodified Gio.
Otherwise, look into the workings of CWM. You may be capable of DD'ing the nandroid files manually, but don't take my word for it.
thanks everyone who replied, i finally figured out what's wrong.
It turned out to be the problem that no CWM for gio could format the partitions into rfs therefore they kept giving me errors when i tried to restore.
and after some trials, I found that the CWM for CM7 (cwm-v2.zip) can actually restore my backup, but with the system, data, cache formated in ext3. Therefore with the stock kernel, it won't boot.
Final remedy: use CWM for CM7 to restore the backup, then flash a custom kernel for stock rom.
crescal said:
thanks everyone who replied, i finally figured out what's wrong.
It turned out to be the problem that no CWM for gio could format the partitions into rfs therefore they kept giving me errors when i tried to restore.
and after some trials, I found that the CWM for CM7 (cwm-v2.zip) can actually restore my backup, but with the system, data, cache formated in ext3. Therefore with the stock kernel, it won't boot.
Final remedy: use CWM for CM7 to restore the backup, then flash a custom kernel for stock rom.
Click to expand...
Click to collapse
Which kernel? Im in your exact situation, i got the cwm you mention and it restored the back up and flashing the kernel for stock rom with lots of options claiming to support ext4 i get boot loops. If you can tell me what kernel you booted with i will be very grateful. Tomorrow is my daughters bday and i need my korean gio with different wifi hardware to tether to my tablet for ideo chat, which only works with stock. Thank you.
hi guys i recently downgraded my recovery from revolutionary to CWM v2.5.0.7.
now i can't do a backup of my CM 7.2 ROM.
backing up boot...
backing up recovery...
backing up system...
it freezes at backing up system..i waited for 20 mins but it doesn't move a inch..
some apps in my sd n some are in my internal storage.
i also tried upgrading to revolutionary and still the same problem persists..:crying:
Can you guys help me out here?
sorry for my bad english.
eddykuhan said:
hi guys i recently downgraded my recovery from revolutionary to CWM v2.5.0.7.
now i can't do a backup of my CM 7.2 ROM.
backing up boot...
backing up recovery...
backing up system...
it freezes at backing up system..i waited for 20 mins but it doesn't move a inch..
some apps in my sd n some are in my internal storage.
i also tried upgrading to revolutionary and still the same problem persists..:crying:
Can you guys help me out here?
sorry for my bad english.
Click to expand...
Click to collapse
Looks like you're messing up the terms a bit...: "Revolutionary" doesn't really have to do something with your "Recovery" (Clockworkmod). Same goes for "upgrading to revolutionary" - I have no clue what you tried to do there
Let's try to get some useful information:
- If you've downgraded your recovery I assume your phone is rooted and has S-OFF and worked well before?
- for what reason did you downgrade? to flash a radio?
- if yes: did that work well?
I have suggestions what you could do but it would be better if you'd provide above information first
eddykuhan said:
hi guys i recently downgraded my recovery from revolutionary to CWM v2.5.0.7.
now i can't do a backup of my CM 7.2 ROM.
backing up boot...
backing up recovery...
backing up system...
it freezes at backing up system..i waited for 20 mins but it doesn't move a inch..
some apps in my sd n some are in my internal storage.
i also tried upgrading to revolutionary and still the same problem persists..:crying:
Can you guys help me out here?
sorry for my bad english.
Click to expand...
Click to collapse
Clockwork mod and revolutionary are two different things.
Try flashing another CWM version through fastboot or pc49img.zip method. You can find the links in wildfire index thread in development section.
Sent from my HTC Wildfire using XDA
saadislam said:
Clockwork mod and revolutionary are two different things.
Try flashing another CWM version through fastboot or pc49img.zip method. You can find the links in wildfire index thread in development section.
Sent from my HTC Wildfire using XDA
Click to expand...
Click to collapse
i tried the latest version of ClockWorkMod v5.0.2.0.but the same problemstill persists
eventcom said:
Looks like you're messing up the terms a bit...: "Revolutionary" doesn't really have to do something with your "Recovery" (Clockworkmod). Same goes for "upgrading to revolutionary" - I have no clue what you tried to do there
Let's try to get some useful information:
- If you've downgraded your recovery I assume your phone is rooted and has S-OFF and worked well before?
- for what reason did you downgrade? to flash a radio?
- if yes: did that work well?
I have suggestions what you could do but it would be better if you'd provide above information first
Click to expand...
Click to collapse
yes, my phone is rooted and s-offed n work well before this and sorry guys previously I was using ClockWorkMod v3.2.0.0..i downgraded to ClockWorkMod v2.5.0.7 to flash radio..but it didn't succeed..So, i flashed through fastboot method and it succeeded.i was able to do a backup after flashing the radio..all went well and 1 day wen i try 2 make a backup in the same ClockWorkMod v2.5.0.7 it stucked in backing up system..
eddykuhan said:
i tried the latest version of ClockWorkMod v5.0.2.0.but the same problemstill persists
(...)
i was able to do a backup after flashing the radio..all went well
Click to expand...
Click to collapse
I see. I already thought that it doesn't have to do with recovery - just wanted to make sure
I suggest you to try reflashing the ROM first - but better make sure that you avoid leftovers of your current "system":
- put the ROM and gapps (20110828) into root of your sd card
- boot into recovery
- format "system" (in "mounts and storage")
- wipe "cache"
- flash CM7
- flash gapps 20110828
- reboot
try a nandroid backup again afterwards
if this doesn't help either my suggestion would be to do a complete wipe:
- put the ROM and gapps (20110828) into root of your sd card
- boot into recovery
- wipe all / factory reset
- (I usually do an additional format "system", "data" as well - just to make sure)
- wipe "cache"
- wipe "dalvik-cache"
- flash CM7
- flash gapps 20110828
- reboot
see, if everything went ok then reboot in recovery and do a partial restore of your data (backup & restore/advanced)
reboot again (see if everything works) and reboot into recovery again to try your nandroid backup
There's another thing coming to my mind: do you have enough space left on your sdcard? I never had that problem so I'm not sure if CWM spits out an error about that...
Just for the info, Cwm doesnt give any error if low on space. It just keeps going on with backup.
Sent from my HTC Wildfire using XDA
So what you meant was .... you downgraded from revolutionarys cwm version to 2.5.0.7 ? Did you use revolutionary to do this or other method?
You couldn't backup with 2.5.0.7 cwm so upgraded back to revolutionarys version with same backup issues afterwards ?
You upgraded cwm to 5.0.2.0 and your still not able to backup ?
Can you restore a nandroid ?
Do you have custom mtd set up ?
Ive not come across the won't back up issue but have had the same issue during restores after flashing a new cwm ?
Some cwm restores are not compatible with some other cwm versions but your problem is backing up so this can't be the case lol.
Have you got the Rom up and running before trying to back it up,and your NOT wiping anything prior to attempting the back up ?
1st I would try wipe dalvik cache from advanced and format cache from mounts and storage then try a backup.
If that fails........ (your gonna lose your current Rom setup with the following but 1 of these methods should get your cwm functioning again.)
Try restoring an old backup then if that is successful try a backup again as this could just kickstart your cwm backup into gear.
Failing that.........,
then I think your gonna have to do a full wipe and reinstall Rom.
Forum fishing.... Who's biting!
Agreed. This is very strange. Have you flashed anything else we should know about that has anything to do with the system partition? Tweaks ect?
Sent from my HTC Sensation using xda premium
slymobi said:
So what you meant was .... you downgraded from revolutionarys cwm version to 2.5.0.7 ? Did you use revolutionary to do this or other method?
You couldn't backup with 2.5.0.7 cwm so upgraded back to revolutionarys version with same backup issues afterwards ?
You upgraded cwm to 5.0.2.0 and your still not able to backup ?
Can you restore a nandroid ?
Do you have custom mtd set up ?
Ive not come across the won't back up issue but have had the same issue during restores after flashing a new cwm ?
Some cwm restores are not compatible with some other cwm versions but your problem is backing up so this can't be the case lol.
Have you got the Rom up and running before trying to back it up,and your NOT wiping anything prior to attempting the back up ?
1st I would try wipe dalvik cache from advanced and format cache from mounts and storage then try a backup.
If that fails........ (your gonna lose your current Rom setup with the following but 1 of these methods should get your cwm functioning again.)
Try restoring an old backup then if that is successful try a backup again as this could just kickstart your cwm backup into gear.
Failing that.........,
then I think your gonna have to do a full wipe and reinstall Rom.
Forum fishing.... Who's biting!
Click to expand...
Click to collapse
hi,
-after upgraded cwm to 5.0.2.0 and i'm still not able to backup
-im using custom mtd
-in matter fact i can restore my old nandroid backup
the story like this after i restore my old nandroid i cannot do backup same ROM again.
and i also tried to wipe dalvik cache from advanced and format cache from mounts and storage then tried a backup and it still fails..:crying:
guys thanks for your feedback im going to do a full wipe and reinstall Rom.!!
eddykuhan said:
-im using custom mtd
Click to expand...
Click to collapse
just to make sure: have you flashed the bravoboot file after the nandroid backup?
If you did, well, a full wipe might be a good idea anyway - but: have you tried my initial suggestion - to format just system? if this is the point where the nandroid backup fails this could be enough to solve your problem...
- put the ROM and gapps (20110828) into root of your sd card
- boot into recovery
- format "system" (in "mounts and storage")
- wipe "cache"
- flash CM7
- flash gapps 20110828
- flash the bravoboot file
- reboot
If everything works again you could try to do a partial restore of "data" (in CWM / Backup and Restore / Advanced Restore)
But don't forget to flash the bravoboot file after that one again - and better don't try to restore system again - just data (and sd-ext, .android-secure whatever you like)
Maybe you can try to do backup in 3.x.x.x version of cwm? I had similar problem to yours (I was on 2.5.x.x v CWM) and after it everything worked
I currently have the same problem (CWM5028) and have not solved it yet.
Interesting to note is that the time noted in the title for the stalling backup is 3 hours off. A clue to the cause?
cweijden said:
I currently have the same problem (CWM5028) and have not solved it yet.
Interesting to note is that the time noted in the title for the stalling backup is 3 hours off. A clue to the cause?
Click to expand...
Click to collapse
Got it solved... I also use MTD partitioning (http://forum.xda-developers.com/showthread.php?t=1233340) and probably have forgotten to flash a required zip after restoring a backup. According to the instructions this should have left me with a white screen. That didn't happen, but it left me unable backing up my system for a while. After repartitioning as suggested by eventcom I was able to make backups again.
Hello to all,
I have Arc with ICS .587 installed and rooted, CWM is Also installed. Whenever i try to restore my Backup i end up in bootloop, sometines its restored but somethings are not working like no service, some widgets are Gone, cant get into Phone settings as the setting button is completly gone from phone.
Please can good Samaritan help me
Thanking All in Advance
Do you Wipe Data/Factory Reset/Cache etc before restore?
did you changed kernel?
if you chanege the name of the backup, things will not work.
gabimx said:
did you changed kernel?
if you chanege the name of the backup, things will not work.
Click to expand...
Click to collapse
yes....not change the name of backup...
moreover if you have flashed a zip and it didn't go fine....there is a possibility that the istallation have spoiled the backup or file of kernel...(for all I know it happened to me in this way)
Yes Guys i do make a full wipe before restore, and after making a backup i transfer it to pc for Safe storage, so whenever i need it i transfer it back to cloclworkmod folder
centi50 said:
Yes Guys i do make a full wipe before restore, and after making a backup i transfer it to pc for Safe storage, so whenever i need it i transfer it back to cloclworkmod folder
Click to expand...
Click to collapse
If u flash custom kernel, u need to also flash wifi modules before rebooting after restore...
I dont Flash custom Kernel, everything is stock, by the way My Arc is Bootlocked so customs kernels
While you make backup does cwm show any errors? have you checked the log ? Does the restore process complete without errors ? And do you fix permissions and mount system /data etc before restoring ?
nikufellow said:
While you make backup does cwm show any errors? have you checked the log ? Does the restore process complete without errors ? And do you fix permissions and mount system /data etc before restoring ?
Click to expand...
Click to collapse
Backup Completes without Error, and no i do not Fix permission or Mount System/Data before restore.
centi50 said:
Backup Completes without Error, and no i do not Fix permission or Mount System/Data before restore.
Click to expand...
Click to collapse
Then do it ! and try again .
This is what is happening to me. Lets say am Running on GB Rom e.g X-Gamer, now i want to try lets say Optimax Rom, i backup my Current ROM which is X-Gamer, then i try to restore it to see if its works, and i find that it works. so Flash ICS Original Sony ROM and root it. in the end i Have Sony Stock ROM.587 and CWM installed. So far am ok.
Now i Install ICS based ROM like Optimax or JellySandwhich. Everything goes Fine, so i Backup That ROM too and keep a copy on my Laptop. Now i decide to go to my old backup of X-Gamer, i Boot to recovery do a full wipe + i mount data/system and fix permission as i have CWM 5.5.0.4. which has permission option in it. i continue to restore my X-Gamer Backup. After Finnishing of course without error. i reboot the phone and Bam!!. Bootloop.
I reflash GB.42 with Flashtool, root it and install CWM. Boot to recovery and try to restore my X-Gamer backup, and WOLA!! it's restored.
same with ICS Backup. Reflash Stcok Rom root it and restore the ICS backup i made, and it works.
As i know i may be wrong (am a noob) The backup is a snapshot of the rom, so regardless of what rom someone is running when he restores the Backup, he should be back to that ROM in the backup and not to reflash first the corresponding Stock ROM in order for the Backup to work.
Please somebody help and shade some light
Have you used the same recovery all the time? Switching recoveries can "sometimes" not flash backups properly. Either that or it didn't back it up properly in the first place. TBH there's not much we can can do. The backup is corrupted and for that it is causing bootloops and braking things. All I can suggest to you is to reinstall a fresh install of the ROM and then try an advanced restore of your applications and data just not the Boot.img or the system.img
Sent from my Galaxy Nexus using xda premium
Jessie-James said:
Have you used the same recovery all the time? Switching recoveries can "sometimes" not flash backups properly. Either that or it didn't back it up properly in the first place. TBH there's not much we can can do. The backup is corrupted and for that it is causing bootloops and braking things. All I can suggest to you is to reinstall a fresh install of the ROM and then try an advanced restore of your applications and data just not the Boot.img or the system.img
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I have tried to use same recovery, but same result. restoring backup across different ROM does not work for me it seems. I have to have a working corresponding rom as the backup am trying to Resotre. for example if i want to restore my backup of GB ROM, i have to have a working GB Rom already on Phone. I Can't restore an ICS Rom while my Phone is On GB and vice verser.
centi50 said:
Please somebody help and shade some light
Click to expand...
Click to collapse
Flashing an ftf also flashes the kernel, so restoring a GB backup when you originally installed ICS or vice versa will give you issues as CWM doesn't backup your kernel.
XperienceD said:
Flashing an ftf also flashes the kernel, so restoring a GB backup when you originally installed ICS or vice versa will give you issues as CWM doesn't backup your kernel.
Click to expand...
Click to collapse
Thanks XperienceD for Clarifying. now i undersatnd. Just wanted to ask is it possible to flash A GB Sock Kernel on an ICS ROM or vice versa, then using the backup to restore thru CWM, as this will save time than to reflash the ftf, root it and install CWM just only to restore your backup.
centi50 said:
as this will save time than to reflash the ftf, root it and install CWM just only to restore your backup.
Click to expand...
Click to collapse
This is why it's better to unlock your BL, then it's just a flash of a kernel then restoring your backup.
Hi
I seem to be having a strange problem making a backup with CWM. Everytime i try to make a backup itll go through all the steps successfully but when backing up /data it'll say error while backing up data. Im running stock 4.0.4 and i never had a problem backing stuff up in the past, this is the first time i've had an issue. My CWM version is 6.0.12 and i also had the same problem on the older 5.something
Any advice would be greatly appreciated thanks
Sent from my SGH-I747M using Tapatalk 2
Sounds like either your cwm or ROM is corrupt. I'd reinstall cwm with ROM manager. If that doesn't work try wiping data/factory reset (will delete all your apps)