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.
Related
Ok so i have a Deisre, which is rooted.
I have the following running:
HBOOT: Alpharev Oxygen - HBoot-0.93.1000
Radio: 32.49.00.32U_5.11.05.27
Recovery: RA-desire-v2.0.0
Rom: Well currently nothing since it won't get past the initial boot image.
I have tried restoring from a nand backup but to no avail.
I can get into HBOOT, recovery and can access my phone from my pc using fastboot.
As i said earlier i have tried restoring and i have tried loading various roms but nothing. it just sits at the first image screen.
If anyone can help - that would be awesome!
try using newer recovery ? amonRA 2.0.1 or CWM 3.0.0.5 (dont use newer CWM, they cause problems)
also make sure your SD is partition well (either for a2sd+ or data2ext) and that EXT partition are working fine (mountable and formatable from recovery)
I would recommend trying to go to a stock Desire rom. If unbranded phone then this is easier to find, but if branded then you can probably find one through some searching.
Stock ROM sounds good but before try to change SD and do wipe for all what you can.
Have you tried oxygen rom? I notice you have that hboot, and I think I'm correct in saying that only oxygen (or devnull) will work with that partition table.
you can try a other SD card !it may have some mistakes on your SD card!
Random_Sheep said:
Ok so i have a Deisre, which is rooted.
I have the following running:
HBOOT: Alpharev Oxygen - HBoot-0.93.1000
Radio: 32.49.00.32U_5.11.05.27
Recovery: RA-desire-v2.0.0
Rom: Well currently nothing since it won't get past the initial boot image.
I have tried restoring from a nand backup but to no avail.
I can get into HBOOT, recovery and can access my phone from my pc using fastboot.
As i said earlier i have tried restoring and i have tried loading various roms but nothing. it just sits at the first image screen.
If anyone can help - that would be awesome!
Click to expand...
Click to collapse
From which rom do you want to restore the nandroid backup?
Alright mate.
Have you actually tried to install the Custom ROM which you were on without trying to restore the Nandroid Backup? This has happened to me a few times where the Nandroid Backup just fails to flash back on to the phone.
As annoying as it may be - Whatever was on your Nandroid may in fact be lost (well not lost, as it's on your SD Card) but download a fresh version of the ROM you were on and install it that way. Remember, even if you're flashing a ROM, factory reset + wipe everything the moment the new ROM has been flashed through the Custom Recovery Menu (whether it be AmonRA or CWM) then reboot the phone.
If that doesn't work, then luckily your phone isn't bricked per se. Just flash a Stock RUU which matches your phone and boom - You can go through the process again. Granted, you'll have to S-OFF your phone again as well.
Dan
Whoops, sorry, wrong thread.
Just wanna clear some questions asap::
1) I have back-up using clockwork mod (ROM MANAGER) is that back up is a NAN-DROID backup?
2) Is Nan-droid back actually a stock backup?
3) I'm about to install CM ROM on my desire using ROM-MANAGER, i have a rooted desire but with S-ON, does this will cause any problem?
4) What S-ON exactly is for?
5) What happens if i don't wipe cache nd other stuff (dalvik cache)?
shujaswati said:
Just wanna clear some questions asap::
1) I have back-up using clockwork mod (ROM MANAGER) is that back up is a NAN-DROID backup?
2) Is Nan-droid back actually a stock backup?
3) I'm about to install CM ROM on my desire using ROM-MANAGER, i have a rooted desire but with S-ON, does this will cause any problem?
4) What S-ON exactly is for?
5) What happens if i don't wipe cache nd other stuff (dalvik cache)?
Click to expand...
Click to collapse
1. Yes
2. The backup is a copy of your phone the way it was when you backed it up.
3. I believe you need s-off.
You should read thread along with any other tuts you can find in the development section.
http://forum.xda-developers.com/showthread.php?t=696189
shujaswati said:
Just wanna clear some questions asap::
1) I have back-up using clockwork mod (ROM MANAGER) is that back up is a NAN-DROID backup?
2) Is Nan-droid back actually a stock backup?
3) I'm about to install CM ROM on my desire using ROM-MANAGER, i have a rooted desire but with S-ON, does this will cause any problem?
4) What S-ON exactly is for?
5) What happens if i don't wipe cache nd other stuff (dalvik cache)?
Click to expand...
Click to collapse
1) Yes.
2) Nandroid backup is a backup of the rom you are currently running.
3) No.
4) S-on is a system protection. Use google for more information.
5) I guess you mean when flashing new rom?! It will cause strange and heavy system problems.
Swyped from my HTC Desire using XDA App
thanx for answering, i'm still not clear with the S-ON thingy.
Also wht if i install a rom but then i find out that a radio for it have to be installed explicitly, so if i revert to old rom by restoring from the recovery mode, would i be back on my previous mode with radio functionality?
shujaswati said:
thanx for answering, i'm still not clear with the S-ON thingy.
Also wht if i install a rom but then i find out that a radio for it have to be installed explicitly, so if i revert to old rom by restoring from the recovery mode, would i be back on my previous mode with radio functionality?
Click to expand...
Click to collapse
No matter what happens after clearing cache and factory wiping, as long as you have a nandroid backup you can return to the backed up ROM and everything is restored to the way it was.
And yes I'm pretty sure if you nandroid restore the radio functionality is restored to the way it was.
Do i have to download, install that adb shell thingy? What is it for?
OK i have done s-off, install CM 7, but had one problem, i can't install apps from Market, the download starts nd just stops with reporting any error, ny help will be appreciated.
Also if i want to go back to my previous ROM, should i just recover from the backup, can it be done using rom manager?
shujaswati said:
OK i have done s-off, install CM 7, but had one problem, i can't install apps from Market, the download starts nd just stops with reporting any error, ny help will be appreciated.
Also if i want to go back to my previous ROM, should i just recover from the backup, can it be done using rom manager?
Click to expand...
Click to collapse
I guess you mean cm7 hboot? If yes, than you cannot download anyhting from market because its cache partition is to small. But this is easy to fix:
Open terminal emulator and then enter the following commands
Code:
mkdir /mnt/sdcard/market-download-cache
su
cd /cache
mv download download.bak
ln -s /mnt/sdcard/market-download-cache download
ls -ahl
Now you should be able to download apps from market again.
I already fixed it, the market applications were freeze and had to be defrost using Titanium Backup.
Thanx for the support XDA people
If i wanna go back to stock(to which i NAND backup), should i just click restore using ROM Manager/Recovery mode or had to do some thing else. Also should all the caches again have to be wiped?
Hello everyone!
I do have a strange problem from my understanding!
I ran a Nandroid Backup with 4Ext Touch Recovery v1.0.0.4 RC3!
To do this I started the 4Ext Recovery Control and chose new backup with the Option not to stay in recovery after backup finished.
My Desire rebooted in recovery and performed the backup without any problems then rebooted and got stuck on the HTC bootscreen!? (How is that even possible? The backup itself shouldn´t change anything?)
I pulled the battery twice and restarted afterwards with no change
I then booted in recovery and only restored the boot partition of the previously created backup and stuck again!
Next step was to first format the boot partition and then restore it from the backup (possibly unnecessary because when restoring boot 4Ext does erase the boot partition before it recovers it anyway!?) and stuck again!
Now I am at a point where I do not know what to do next and I find it really disturbing that I cannot even rely on the creation of a Nandroid backup nor the recovery of it!
Is it possible that this might have something to do with the version of HBOOT I use? It is the one revolutionary flashed during S-OFF!
Is there anything else I can do now?
Kind regards,
Guido
Think some people encountered an issue with that version under certain circumstances, can't remember if it was related to wipe/format of boot or Sys partition or something else. If you can revert back to RC 2, or flash one of the newer test versions and try that.
Sent from my HTC Desire using Tapatalk 2
Kosh_ac said:
Hello everyone!
I do have a strange problem from my understanding!
I ran a Nandroid Backup with 4Ext Touch Recovery v1.0.0.4 RC3!
To do this I started the 4Ext Recovery Control and chose new backup with the Option not to stay in recovery after backup finished.
My Desire rebooted in recovery and performed the backup without any problems then rebooted and got stuck on the HTC bootscreen!? (How is that even possible? The backup itself shouldn´t change anything?)
I pulled the battery twice and restarted afterwards with no change
I then booted in recovery and only restored the boot partition of the previously created backup and stuck again!
Next step was to first format the boot partition and then restore it from the backup (possibly unnecessary because when restoring boot 4Ext does erase the boot partition before it recovers it anyway!?) and stuck again!
Now I am at a point where I do not know what to do next and I find it really disturbing that I cannot even rely on the creation of a Nandroid backup nor the recovery of it!
Is it possible that this might have something to do with the version of HBOOT I use? It is the one revolutionary flashed during S-OFF!
Is there anything else I can do now?
Kind regards,
Guido
Click to expand...
Click to collapse
I encountered this problem in CWM recovery months ago, too.
I just restored nandroid and it booted again.
So if you are in this situation try this.
If you solved, try use previous version RC2 for next nandrod backup.
paolo-red1 said:
I encountered this problem in CWM recovery months ago, too.
I just restored nandroid and it booted again.
So if you are in this situation try this.
If you solved, try use previous version RC2 for next nandrod backup.
Click to expand...
Click to collapse
Just tried a complete recovery, problem unfortunately persists
Regards,
Guido
So after a newly try to recover my latest backup this also failed :-(
I got no errors, but after reboot I got stuck again on bootscreen!
I then reflashed the ROM I am using and to my surprise that worked!
I really don't know what the problem is with recovery, but it's getting a little frustrating...
Regards,
Guido
Kosh_ac said:
So after a newly try to recover my latest backup this also failed :-(
I got no errors, but after reboot I got stuck again on bootscreen!
I then reflashed the ROM I am using and to my surprise that worked!
I really don't know what the problem is with recovery, but it's getting a little frustrating...
Regards,
Guido
Click to expand...
Click to collapse
have you changed your hboot without flashing another recovery? i've read that this can be a problem too. just give it a try, flashing a fresh recovery.
sent by an android
andy.smith said:
have you changed your hboot without flashing another recovery? i've read that this can be a problem too. just give it a try, flashing a fresh recovery.
sent by an android
Click to expand...
Click to collapse
No! I did not flash another HBOOT after S-OFF with revolutionary!
Regards,
Guido
Try updating your 4EXT recovery to the latest one available from your working ROM. Could be that your previous recovery screwed up MD5 sums of your backup, or the recovery didn't flash properly.
Sent from my HTC Desire using Tapatalk 2
SANCAH said:
Try updating your 4EXT recovery to the latest one available from your working ROM. Could be that your previous recovery screwed up MD5 sums of your backup, or the recovery didn't flash properly.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the tip!
I am using the latest RC Version! I am unsure whether I can safely use the Testing Versions over the RC ones!?!
Regards,
Guido
Kosh_ac said:
Thanks for the tip!
I am using the latest RC Version! I am unsure whether I can safely use the Testing Versions over the RC ones!?!
Regards,
Guido
Click to expand...
Click to collapse
I am using the latest version of the touch test recovery, haven't had any issues so far.
Sent from my HTC Desire using Tapatalk 2
Hello everyone!
Just wanted to give feedback about my problem!
Updated to 4Ext Recovery 1.0.0.5 RC3 prior to installing Supernova Extreme and made a Nandroid Backup without the problem I encountered before!
Did two additional Nandroid Backups after flashing the new ROM also without any problems!
So this thread can be closed
Thanks again to everyone for your helpful ideas!
Regards,
Guido
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.
[Q] Why is "fix permissions" missing from CWM? ... I can't do anything on my phone
I "broke" my phone using PhilZ CWM Touch, I don't know how?
I did a full CWM backup of my ROM / apps etc to my SDCard, it grabs /data/ /system/ all kinds of stuff into a 4gb ZIP or whatever.
I've done this many times before!
All of this so I could do some quick CM12 testing for a snapchat bug.
Then I restored the CWM backup image from my SD Card
Now, I can't save screenshots or write ANY data to the /sdcard/
"Couldn't capture screenshot: couldn't save. Storage may be in use"
Tried wiping Dalvik cache, no fix.
What do I do here? I'm baffled? ?I thought restoring a CWM backup would recover everything.
This PhilZ touch thing is missing "fix permissions" ?
wizzbang3 said:
I "broke" my phone using PhilZ CWM Touch, I don't know how?
I did a full CWM backup of my ROM / apps etc to my SDCard, it grabs /data/ /system/ all kinds of stuff into a 4gb ZIP or whatever.
I've done this many times before!
All of this so I could do some quick CM12 testing for a snapchat bug.
Then I restored the CWM backup image from my SD Card
Now, I can't save screenshots or write ANY data to the /sdcard/
"Couldn't capture screenshot: couldn't save. Storage may be in use"
Tried wiping Dalvik cache, no fix.
What do I do here? I'm baffled? ?I thought restoring a CWM backup would recover everything.
This PhilZ touch thing is missing "fix permissions" ?
Click to expand...
Click to collapse
Philz recovery is one of the best recovery ever been. Unfortunately developer abandoned
This is the message from developer
Project Status:*No Longer Updated
As I mentioned before, I have a lot of new important projects in my real life. I am very happy to abandon this project for real life alternatives.
CWM is a dead project for now, until some dev resurrects it. I was about to do, until these new projects came.
Current version will probably work a while for many devices. Some devices with new ROM installers could have issues. Just use TWRP or the CM Simple Recovery
If the current version works for you, there is no reason you don't use it though. No need to ***** in all threads because it doesn't work for you. Just move on to other alternatives
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=39433458
Latest update for n7100 was at middle of 2014 if I remember well. Probably u used an outdated recovery. I am using the version 6.48.4 at cm12.1 with no problem at all but I never made with this a nandroid backup.
Sent from my GT-N7100
If you check PHilZ FTP / Mega Upload mirror, he's clearly still updating it? ?.... I dunno
Regardless, I did some reading and the impression I get is version 6.3.xx of CWM removed the "FIX PERMISSIONS" code / option (why the @$#%^ it did this, I do not know)
Ultimately I think that's the issue with my phone, right?
wizzbang3 said:
If you check PHilZ FTP / Mega Upload mirror, he's clearly still updating it? ?.... I dunno
Regardless, I did some reading and the impression I get is version 6.3.xx of CWM removed the "FIX PERMISSIONS" code / option (why the @$#%^ it did this, I do not know)
Ultimately I think that's the issue with my phone, right?
Click to expand...
Click to collapse
I don't know about other phones but for n7100 sure abandoned.
About the issue now yes looks like permission problem, maybe you try to fix permissions with some other recovery or if you have some apps installed and for this you want to restore your backup, you can restore your nandroid backup after wipe system, cache, dalvik and install the same rom, gapps you had made backup. The installation of the rom at the end of install normally will fix permissions. Also you can try to clean install your old rom, gapps, reboot check if everything is OK and after from recovery again make selective nandroid restore the data only.
Sent from my GT-N7100