symlink some symlinks failed status 7 - Nexus 7 Q&A, Help & Troubleshooting

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.

Related

[Q] Nexus 4 won't boot after trying to update

Hello,
I am in serious problem and need your help asap
So this is the thing:
I got a nexus 4 running rooted srock 4.2.1 official ROM. I was trying to update to 4.2.2 with OTA update. The problem was it has an "assert problem (status 7)" with the file /system/app/PlusOne.apk. Maybe it was a mistake but I tried to format /system through the recovery. Again, I tried to install the update. this time, it has the same assert problem but with the build.prop file.
Since then, the nexus is stuck on the google logo and won't boot. I've tried to wipe dada/cashe/anything else and it didn't fix the problem. I also tried to install again the stock rom through the Nexus 4 Toolkit without any luck.
I have no idea what to do.. The only thing I can do is go in the fastboot/recovery menu, but can't boot in any way..
Please help me
Thanks in advance.
MasterLinuxer said:
Hello,
I am in serious problem and need your help asap
So this is the thing:
I got a nexus 4 running rooted srock 4.2.1 official ROM. I was trying to update to 4.2.2 with OTA update. The problem was it has an "assert problem (status 7)" with the file /system/app/PlusOne.apk. Maybe it was a mistake but I tried to format /system through the recovery. Again, I tried to install the update. this time, it has the same assert problem but with the build.prop file.
Since then, the nexus is stuck on the google logo and won't boot. I've tried to wipe dada/cashe/anything else and it didn't fix the problem. I also tried to install again the stock rom through the Nexus 4 Toolkit without any luck.
I have no idea what to do.. The only thing I can do is go in the fastboot/recovery menu, but can't boot in any way..
Please help me
Thanks in advance.
Click to expand...
Click to collapse
By formatting /system, you have effectively deleted Android OS. That's why your phone won't boot up. And without Android, you can't get into ADB (that's why the toolkit won't work. Reflash the stock images (guide can be found here: http://forum.xda-developers.com/showthread.php?t=2010312) and you should be fine.
Sent by carrier pigeon

Need help in flashing CM 10.2

I recently got a nexus 7 2012. I unlocked it and installed the custom recovery (CWM) according to the guides given in the forum and elsewhere. The problem comes when I install a custom ROM like CM10.2, It installs fine, but the boot does not resume after the CM animation. I tried another rom like AOKP and even TWRP as recovery, still the problem persists. My bootloader is 4.23 and flashing back to stock ROM works as normal. Please help.
What recovery you use. And what tool you use to root. For I use WUG toolkit. And install TWRP. And install CM 10.2 with no problem. Maybe you not really root. Update your superuser before that
Sent from my Nexus 7 using XDA Premium 4 mobile app
Stupid question: are you sure you are flashing grouper ROMs?
Tried a lot of combinations with ROMs and recoveries finally I solved it. CWM wasn't working with its wipe options and tried TWRP and gave the full wipe of all partitions before flashing CM and gapps and it worked!!!!

[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.

installing custom rom failed, what next

On my N10 I have TWRP 2.6.3.0
I had an old Paranoid Android Rom 4.3 3.99
I wanted to have a new 4.4.2. rom so I downloaded Omnirom & Gapps (http://forum.xda-developers.com/showthread.php?t=2487484)
In TWRP making a backup failed everytime so I took the risk of installing Omnirom without nandroid backup...
During the installing of omnirom I received a slight error:
set_metadata_recursive some changes failed
After installing I rebooted but the only thing that happens is that I get a reboot into twrp again..
Can somebody point me in the right direction? For example how to get a clean 4.4.2 zip image on my N10 and trying to flash that one?
solved: wug's toolkit did the trick

[Q] Pac rom update failed

heres my situation,
I have Custom Pac rom 4.3 nightly installed.
i have bootloader unlocked.
im trying to update it to Pac 4.4 [kit kat] rom.
PROBLEM: when i try to install the update rom, i keep getting
"Formatting system
Extracting system file...
set_metadata_recursive: some changes failed
E:Error in sdcard/0/pac_moto_msm8960-nightly-20140417.zip
(status 7)
Installation aborted.
"
any help in my situation?
Which recovery do you use..
Sent from my XT907 using xda app-developers app
AH i ended up fixing the problem on my own.
in case anybody else runs into the same problem heres the solution.
i was using CWM recovery, it was outdated so once i updated it and tryed agian to reinstall the rom. everything went well,

Categories

Resources