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
Related
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
Hi guys,
I have unlocked my bootloader a few days ago, and also installed the CWM recovery, which I used to install the ATT 2.3.4 ROM (I own an International Atrix), and it was working flawlessly. Being annoyed by that bunch of bloatware, I decided to install the Alien-ROM, so I wiped data with fastboot -w, and entered CWM to erase the cache partition/dalvik cache and install Alien. The problem is, when I tried to install the .zip package, CWM threw at me "Installation Aborted", with no error message whatsoever, just before "Beginning Installation". At first I thought my .zip was corrupted, so I re-downloaded it and tried again, but got the same error.
Being unable to install the AlienROM, I fastbooted the ORFR ROM (surely a lot cleaner than ATT's) and installed the ROM manager app, and through it, updated my CWM to the latest version. And then there I was trying to install the .zip again, with no success. As a last effort, I uninstalled manually the install-recovery.sh file and the recovery partition, reinstalled Tenfar's CWM, but fell into the same error: "Installation Aborted".
Does someone have a clue of that is happening??
Thanks in advance.
Rom manager recovery does not work always.what I suggest is use tenfar recovery and then put alien zip on your ext.SD card and use tenfar recovery --- choose zip from SD card--- browse and select alien.zip and flash through it.
Hope this helps.
Well, I tried to install Tenfar's CWM, as I said at the end of my first post. I recently installed a new CWM-based recovery, and it also failed to install any .zip. Could it be because I'm using ORFR ROM? I've noticed the misbehaving os CWM when I uninstalled ATTs ROM...
Install rom racer's recovery.
I voided my warranty.
Use this link: romracer's custom CWM
Let us know if this helps
pedrohz said:
Hi guys,
I have unlocked my bootloader a few days ago, and also installed the CWM recovery, which I used to install the ATT 2.3.4 ROM (I own an International Atrix), and it was working flawlessly. Being annoyed by that bunch of bloatware, I decided to install the Alien-ROM, so I wiped data with fastboot -w, and entered CWM to erase the cache partition/dalvik cache and install Alien. The problem is, when I tried to install the .zip package, CWM threw at me "Installation Aborted", with no error message whatsoever, just before "Beginning Installation". At first I thought my .zip was corrupted, so I re-downloaded it and tried again, but got the same error.
Being unable to install the AlienROM, I fastbooted the ORFR ROM (surely a lot cleaner than ATT's) and installed the ROM manager app, and through it, updated my CWM to the latest version. And then there I was trying to install the .zip again, with no success. As a last effort, I uninstalled manually the install-recovery.sh file and the recovery partition, reinstalled Tenfar's CWM, but fell into the same error: "Installation Aborted".
Does someone have a clue of that is happening??
Thanks in advance.
Click to expand...
Click to collapse
May be you want to try installing the CWM from here... http://forum.xda-developers.com/showthread.php?t=1204500
This should most likely help you fixing the issue you are facing.
Good Luck.
Cheers!!!
Just tried the recovery mentioned above by you all... and nothing, I keep getting the same error -> "Installation aborted", right after "Beggining installation" (or something like that)
Any clues?
pedrohz said:
Just tried the recovery mentioned above by you all... and nothing, I keep getting the same error -> "Installation aborted", right after "Beggining installation" (or something like that)
Any clues?
Click to expand...
Click to collapse
How are you installing RomRacer's CWM? Flashing the .zip or via fastboot?
Sent from my MB860 using XDA Premium App
I've installed it through fastboot, as it's the only way I can do it... my problem resides solely on the fact that I can't install any .zip through it, I keep getting "Installation aborted", no matter what I try to install (Kernels/ROMs/etc)
Pedrohz... Are you using a Mac? If so do you have it set to unzip after downloading? Then are you re-zipping the file before you try to install? If so turn off the unzip feature. Just a thought... Hope it helps
Similar Issue, can't boot into anything :/ if you can help, read below :S
Ok, so I backed up using Oringinal CWM, and it said all OK. After this, I restored the backup, just to check all was working. I got the error error formatting /system. Rebooting, I found that my phone wouldn't boot. Thinking the only way out was to flash a new ROM, I flashed the new boot.img from evals Orange France 2.3.4 firmware, so that I would have the ram fix. After this, I wiped all the caches and the user data, and tried to install the ROM.
SAME FRIGGEN ERROR. no error code, just installation aborted.
Finally, I tried AGAIN with romracers cwm, but same error. Restoring from backup now gives the error - "Unable to flash new boot.img" or something along those lines.
If anyone cares, heres what my phones running
Firmware = Orange UK 4.4.20 (Android 2.2.2)
SBF= Bell_ihop (the international bootloader unlock sbf)
State= Won't boot past the big red M in the centre of the screen.
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.
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
jpp2109 said:
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
From what I've read about that issue is people have had to Odin back to stock then start over. Now maybe you could try installing another recovery like Philz maybe using Odin or try Goo for TWRP before you Odin back to mdk and go through all that.
Sent from my SCH-I545 using Tapatalk
I had a similar thing a few years ago, with what I know now I think the recovery is temporarily flashed with CWM to gain root and stock recovery is replaced after, I'd look for an actual CWM recovery to flash in.
Same applied to me using a ROM Manager, said it was v.xxx made a backup, flashed a ROM, turns out was left without a backup..... noob-old days
Bashing away at my HTC Desire C
Thank you for the solid replies, I'm interested in getting experience with the other recovery methods anyway so I'll try those and worse case I start from scratch.
I have pretty much this same issue. I was happily running 6.0.44 CWM, installed via CWM.
Then I happened to check and see there's an update to 6.0.47. I installed via ROM manager which reported success. Except that it isnt. I basically have 2 recoveries as far as ROM manager is concerned. It thinks I'm on 6.0.47, but 6.0.44 is what boots. I'm betting it's the same issue you have.
I re-flashed Twrp trying to fix it. Now twrp is what recovery always boots; but Rom manager still thinks 6.0.47 is installed. Rom manager shows BOTH recoveries in the "Recovery already installed" menu.
Seems the issue here is the 6.0.47 when flashed via Rom manager. It bugs the crap out of me that it seems like I have 2 recoveries installed somehow. Not sure how that's possible, but everything seems like it's functioning for me.
Compare the sizes of the recoveries, one thing I've come across is when you flash a new .img in because of the NAND chip process for writing/erasing I have had 'remnants' from previous files.
In one respect it is unlikely but I wouldn't rule it out until you check yourself. It could just be left on the list as a marker that it has previously been installed.
Personally I don't use ROM Managers now, it's into TWRP Recovery and backup from there
Bashing away at my HTC Desire C
Look Like I'll Have to Start From Scratch
I'm just getting back to this because work was crazy. No Matter what recovery I try always comes up with Android System Recovery 3e. Stock MDK and re-root it is.
Maybe try using GooManager to install TWRP after you've gone back to stock.
Hello I was having problems in backing up data in nandroid using cwm recovery. Some nice guy suggested me to change my recovery so I did.
Now i have messed up real bad, i flashed a philz recovery which I had used in a stock based rom and the backup was successful but then the phone couldn't boot up. So i restored the boot patrition from a previously made backup. This way i successfully booted up my phone and got previous recovery. So far so good. Now i knew that the problem is in recovery. I also had a raw kernel file which I had used to flash the cm11 rom so i flashed that kernel. But then i restated device to find out that i have now lost root access. I tried flashing super su via raw kernels twrp recovery but I saw no effect despite it being flashed. I cannot flash the recovery because the curreny twrp recovery crashes when i try to flash that.
Current situation is that I am getting constant unlimited, system process is crashed, errors and I can see no signal from mobile operator. Wifi is working fine.
Please help me, my phone is almost unusable with this error but I have access to all the apps, functions etc. in case you can suggest me to use it.
UPDATE:
Tried to flash a latest version of cm11 and now booted up correctly. root checker says I am rooted.
got latest cwm as well
Now I need to take backup to see if the initial problem is there or not.
As the issue highlighted in this thread is solved, I will mark this as solved and will reply to future problems (related to not being able to backup /data) in the following thread:
http://forum.xda-developers.com/android/help/cwms-nandroid-backup-fails-to-backup-t2899038