hey guys i got my G5 today so i rooted it using universal androot
next step was to flash recovery so i did using odin but i didnt noticed and flashed the non rfs version first then i tried to make a nandroid backup but it failed saying it couldnt handle system partition!
so i then noticed it wasnt the correct cwm version and so i flashed the rfs one, i tried to make a back up again and this time it could mount the system but after backing it up a new error message comes up:
E: Can't Mount Cache partition!
and also the logs :s
any help to fix this will be much appreciated!
i havent flashed any ROM cause im afraid i might brick the phone, also i wanted to keep a backup of the stock ROM if i ever wanna go back to it just in case
So you flashed the latest version of CWM through odin? Only that?
Sent from my Galaxy5 using Tapatalk
flashed the non rsf version on stock ROM then i installed the rsf version pretty much but i get those errors
Related
Hello there guys.
I've done a full backup with clockwork but if i try to restore it i get a error message about the boot image...i can't restore it. now i was able to restore system..data..and so on via advanced restore...i get no boot animation but the system is up an running. i can't get the wifi to work...what can i do now?
I used a clockwork 4.0.1.4 with root enabled..i flashed it whit Odin.
Thanks guys
forgot to mention I own a Galaxy S 2
Flash a clean stock rom as your backup is corrupt.
jje
Same issue
I took a full backup with CWM (4.0.0.2) to test a Kitchen ROM. After getting it to work I wanted to switch back to my standard ROM (CF-Root KE7), but it failed with the boot image ("error flashing boot image").
If the backup was corrupt I would expect the MD5 to fail, but it didn't. Like the OP I was able to restore all the other items one by one, which now gives me a Frankenstein ROM: KE7 with the Kitchen-selected Kernel (Ninphetamine) and baseband (KH1).
I'll flash a new stock ROM with CF-Root again, but I am doubting CWM now.
Hey guys, I rooted my device with the CF-KG2 kernal and am trying to use Rom Manager with Clockwork Mod 4.0.1.5. to install Cyanogen mod.
I can't get into CWM recovery for anything after installing without getting:
Finding update package ...
Opening update package ...
Verifiyng update package ...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
I can't find a solution to this on google or anywhere on this forum.
I also tried manually wiping my data/cache and installing the cyanogen nightly 26 with the CWM 4.0 included with CF kernal. It installs fine but won't boot past the samsung logo, so I had to restore.
Any help is appreciated!
Do a fresh download of a cm7 nightly.
Put it into your internal sd card.
Boot into cwm recovery
Wipe data/cache/dalvik
Flash cm7 zip
If you get stuck at the screen flash the zip again from recovery and it should boot.
Also, don't flash it via flash update, do it via flash zip.
Sent from my GT-I9100 using XDA Premium App
Thanks a ton. Believe it or not just installing the zip twice actually installed cyanogen perfectly. Amazing.
Canadianreaper said:
Thanks a ton. Believe it or not just installing the zip twice actually installed cyanogen perfectly. Amazing.
Click to expand...
Click to collapse
It's weird, seems to be due to custom versions of cwm recovery in most kernels, the other way todo it is to flash codeworx's cwm kernel then cm7, which seems to make it work with one flash of cm, but glad to hear you got it going.
Sent from my GT-I9100 using XDA Premium App
Same Here
Canadianreaper said:
Hey guys, I rooted my device with the CF-KG2 kernal and am trying to use Rom Manager with Clockwork Mod 4.0.1.5. to install Cyanogen mod.
I can't get into CWM recovery for anything after installing without getting:
Finding update package ...
Opening update package ...
Verifiyng update package ...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
I can't find a solution to this on google or anywhere on this forum.
I also tried manually wiping my data/cache and installing the cyanogen nightly 26 with the CWM 4.0 included with CF kernal. It installs fine but won't boot past the samsung logo, so I had to restore.
Any help is appreciated!
Click to expand...
Click to collapse
I also have the same problem, errors when trying to boot CWM recovery. Did not allow me to back up anything. and now my phone is stuck on the Galaxy S 2 boot screen and keeps on looping. I think I was using lightning ROM previously. What is the next thing I should do to make the phone work again.
Once the phone works, how do I get CM7 on it? Thanks so much. I am a new user and am not really familiar with the process.
gtizon said:
I also have the same problem, errors when trying to boot CWM recovery. Did not allow me to back up anything. and now my phone is stuck on the Galaxy S 2 boot screen and keeps on looping. I think I was using lightning ROM previously. What is the next thing I should do to make the phone work again.
Once the phone works, how do I get CM7 on it? Thanks so much. I am a new user and am not really familiar with the process.
Click to expand...
Click to collapse
Pull the battery and boot to cwm again. Wipe data/factory reset, wipe cache and flash cm7 (provided u put it on ur sd card).
If not, flash a stock rom, let boot and place latest cm7 .zip on ur ad card. Flash a kernel with cwm and flash cm7 .
I also have this problem. Also I can't back up my current rom, because it gives the same message as in First post. And I want to flash MIUI -rom. What to do?
Any solutions to this? I rooted using Zedomax's Method. all went smoothly. When I went into Rom Manager to backup, it said I had to flash CWM, I said ok. Now I get the same error as the OG. Don't know if the recovery worked prior to going into ROM Manager. I'm thinking of running the Zedomax's Method again to see if it reinstalls a workable CWM.
I have made a back up with a CWM 5 (don't know exactly which one) and then again with CWM 6.0.1.2. I flashed CM10 and then when I tried to restore back to the stock ROM that I had backed up I got an error in CWM 6.0.1.2 saying that an "Error occurred while restoring /data". I checked the file size and it was well under 2GB. I don't know what to do as I don't want to lose all of this data. Is there a way to restore the backup made in CWM 6.0.1.2 or a way to find out which version of CWM 5 I used for the other backup so that I could use that one. Any help would be greatly appreciated. Thanks in advance.
Swift&B0ld said:
I have made a back up with a CWM 5 (don't know exactly which one) and then again with CWM 6.0.1.2. I flashed CM10 and then when I tried to restore back to the stock ROM that I had backed up I got an error in CWM 6.0.1.2 saying that an "Error occurred while restoring /data". I checked the file size and it was well under 2GB. I don't know what to do as I don't want to lose all of this data. Is there a way to restore the backup made in CWM 6.0.1.2 or a way to find out which version of CWM 5 I used for the other backup so that I could use that one. Any help would be greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
I think it don't care which version of CWM 5 you use cause I think you used the recovery by chainfire. It's not longer supported by him so simply try to restore your backup with his last one.
Throwing out of the window from my flying Ferrari killer S3 driven by a proud omega team member
last night I was trying to install temasek latest rom, I was coming form s4 revolution v 12 I did a factory reset as usual, but when I tried to install the rom this error pop in saying:
"set_metadata_recursive: some changes failed
E: Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/Download/cm-11-20140
Updating partition details..."
I have no idea what the problem could be but I think that I could have something to do with the su app.
the rom came with SuperSU but it gave a root problem with titanium backup app so I tried to change to Superuser app from ChainsDD, I'm not sure if anything happened in there but I was able to gain SU rights on titanium make the app backup and then the horror :crying:
so what could be the problem and what can I do.
Well seeing that nobody helped me, I will post what I did for anyone with a similar case, the rom didn't install on twrp so I switched to philz touch recovery, I could succesfully flash in there, but now I got a boot loop, so doing a bit of research I find out that it could be something bad that happened in the rom so I fully wipe the system and then flashed the rom and voila it booted. I knew it wasn't a complicated problem but to know what to do can be a bit of a headache.
Well if you had done a bit of reading before posting your thread you would knew that 4.4.2 ROMs require the latest recovery after cwm6.0.4.4..
Glad you could help yourself without any assistance...
Sent from my GT-I9300
The weird thing about this is that I had successfully flashed 4.4 roms using twrp but this time it didn't let me flash any rom so that was why I was intrigued
Sent from my GT-I9300 using Tapatalk
Hello guys, i've recently got back to stock rom just to be sure to delete every mod done to my MB860, did this via RSD (A safe method tested even after with unlocked bootloader).
Thing is, when doing a backup of the rom via CWM says the next message:
error while making a backup image of /pds!
I've installed long ago the PDS Fix but after i've replaced my touchscreen i've rolled back to my stock backed PDS, but the CMW doesn't seems to be able to back up that partition, so CWM is a no go, and i have to roll to TWRP to backup, but i wish to know if there's a fix to this issue.
Thanks.