[SOLVED] OTA: Status 7 - set_metadata_recursive - Nexus 7 Q&A, Help & Troubleshooting

Alright, got in a bit of a pickle here.
Tried to sideload the OTA update from JWR66Y to 4.4, but I get this bloody error and now I am stuck in a bootloop where it takes me back to the recovery mode.
Code:
set_metadata_recursive: some changes failed
E: Error in /tmp/update.zip (status 7)
I used Wugs toolkit to reflash stock recovery, but I didn't unroot (couldn't remember if I needed too).
Now, I don't want to wipe data and I cannot restore nandroid.
EDIT: Root was the culprit, managed to flash TWRP temporarily and then restore nand and unroot and the sideloading ota worked!

Related

symlink some symlinks failed status 7

Okay I'm a noob
I started with Jellybean 4.2 on my Nexus Tablet Stock I rooted it then started trying out roms. I didn't like any of the roms that are out that are on the 4.2.1 build of jellybean (not that the developers aren't doing a great job just I'm too new at this to mess with bugs too much). I decided to go back to my rooted stock 4.2 backup. Then I found out the new liquidsmooth rc9 came out and I like liquidsmooth since I have been using it on my phone(Samsung Hercules). I decided I wouldn't mind downgrading to 4.1.2 build rom until 4.2.1 builds got more bugs fixed. I couldn't get it on quite right and finally just wiped the whole thing with fastboot (total wipe install stock rom lock bootloader then unlock then root). I tried flashing liquidsmooth again and I got an error:
script aborted: symlink: some symlinks failed
symlink: some symlinks failed
E:Error in /sdcard/goomanager/pa_grouper-2.99-19NOV2012-210915.zip
(Status 7)
Installation aborted.
I thought maybe it had to do with the build I was flashing from so I used fastboot to downgrade the bootloader to 3.41 so I could flash the 4.1.2 using fastboot which worked and now I'm in stock 4.1.2 but I still get the same error when I try to flash any rom leading me to believe there is something deeper wrong with my tablet that I'm missing and I can't find anything in the forums pertaining to this error on the Nexus 7
I uploaded the CWM Recovery Log from when I was doing the flash of paranoiddroid so Hopefully somebody could help me.
Thanks in advance and Yes I know how to use the thank you button too and not shy about it.
Okay so have an update I completely wiped my nexus 7 and reinstalled the stock 4.2.1 jop40d using fastboot and locked then unlocked the bootloader just to make sure and I had no problem flashing Liquidsmooth RC9. I tried flashing paranoid android 2.99 betasix again and same errors came up again. So I tried wiping my recovery and flashing TWRP instead of clockwork mod and then flashed paranoid again and everything worked out great. So maybe something to do with clockworkmod.

[Q] Status 7 error can't flash rom

I am trying to flash the Kitkat 4.4 KRT16O from my current rom 4.3 JWR66Y and no matter what I do I keep getting the following:
Warning: No file_contextsVerifying current system...
"/system/app/YouTube.apk" has unexpected contents.
E:Error in sd/sdcard/0/Download/romfilename
(status 7)
Installation aborted.
I switches custom recovery from CWM to TWRP and I still get this error. Can someone PLEASE help me to resolve this issue. I have wiped all data and need help to get pass this error.
Thanks in advance.
akey
akey said:
I am trying to flash the Kitkat 4.4 KRT16O from my current rom 4.3 JWR66Y and no matter what I do I keep getting the following:
Warning: No file_contextsVerifying current system...
"/system/app/YouTube.apk" has unexpected contents.
E:Error in sd/sdcard/0/Download/romfilename
(status 7)
Installation aborted.
I switches custom recovery from CWM to TWRP and I still get this error. Can someone PLEASE help me to resolve this issue. I have wiped all data and need help to get pass this error.
Thanks in advance.
akey
Click to expand...
Click to collapse
OTAs can only be applied to a non modified rom. Try flashing the system partition of 4.3 JWR66Y and then run the OTA to 4.4 KRT16O.
Even better since you already wiped all data and have nothing to lose, just flash the factory image of 4.4.
Beaster said:
OTAs can only be applied to a non modified rom. Try flashing the system partition of 4.3 JWR66Y and then run the OTA to 4.4 KRT16O.
Even better since you already wiped all data and have nothing to lose, just flash the factory image of 4.4.
Click to expand...
Click to collapse
Thanks Beaster, worked like a charm.

Help needed - i9505g soft-brick/recovery boot-loop

This is my second Samsung. I have put over a dozen different ROMs on my old Exhibit II 4G. Having said that, I realize many of you know more than I could ever hope to know. That is why I'm posting here. I have searched, but most of my searches take me to announcements of new CWM and TWRP recoveries.
I've had a Samsung Galaxy S4 Google Play Edition for over a month and still did not have a nandroid backup, so last night I installed ClockworkMod ROM Manager with the intention of flashing CWM Recovery. The app did not list my phone, so I told it to show all devices, where I found the i9505 (I don't remember if it was the i9505g or not). I told it to flash ClockworkMod Recovery, and selected the option that I had not yet flashed CWMR. I then used QuickBoot to reboot into recovery, where I performed my first nandroid to the microSD card.
When I rebooted after making that nandroid, it went right back to ClockworkMod Recovery. Subsequent reboots did the same thing. I could get into Odin mode with VolumeDown+Home+Power. Using Odin v3.09 I was able to flash the stock recovery. This did not resolve the boot-loop issue. Now it boots into the stock recovery, which is less functional than CWM. To me it is behaving as if the recovery tools were flashed to the /boot/ partition, or something is telling it to always boot from the recovery partition.
-In stock recovery, it will download ADB installations (from "apply update from ADB"), but every attempt fails it's signature verification. I have tried 6+ files, all have failed. I believe that the device has USB debugging enabled, but I cannot check while in this state.
-Stock recovery does not mount the microSD card, so I cannot install from there. CWM would mount the microSD card, but I did not think to try installs from the microSD at that time. Is it possible that I installed the wrong stock recovery?
-I do not know how to perform an ADB "push" with my phone in this state. To be honest, I have never done an ADB push. If I get to that stage, where on my S4 should I send a pushed file? "/system/bin"?
-If I try an adb push in this mode
-How do I get my phone to boot from the proper partition?
-If I have the wrong data in that partition, how do I get the correct information onto that partition?
Here is what it does when I try to sideload from stock recovery:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify while-file signature
E:failed to verify while-file signature
E:signature verification failed
Installation aborted
Thank you in advance for any help!
Solved - i9505g soft-brick/boot-loop
My problem was resolved by flashing a stock recovery and ROM, found here: http://forum.xda-developers.com/showthread.php?t=2569510
The package named "I9505GUEUBML4_FULL_ROOTED.tar.md5.gz" flashed from Odin is what worked.

[Q] Malladus install fails to set permissions

both Malladus 1.2.7 and 1.2.8 fails to install on my VS980.
currently on rooted stock 11a with CWM 6.0.4.7
error is in setting perms
set_perm: some changes failed
e: error in /data/media/0/malladus-vs980-1.2.8.zip
(Status 7)
installation aborted.
imgur.com/a/J6kUx
non currently bricked as i have a good working nandroid but would like to get this installed.
back to the top.
How could I edit the install script to echo the results of the set_perm commands to determine which one is failing?
Figured i should update this:
The problem was CWM 6.0.4.7 installed by FreeGee. I am now using TWRP 2.7.0.0 with no issues.

Can't flash files on my backup Defy

I just tried to upgrade my backup Defy from 2.3 to CM11. I rooted it, installed 2ndInit and from there I'm trying to flash all the zips from Quarx' CM11 thread. The problem is it throws an error at the first one:
Code:
E:Error in /sdcard/cm11/new_bootstrap.zip
(Status 0)
Installation aborted.
Did I miss a step?

Categories

Resources