installing custom rom failed, what next - Nexus 10 Q&A, Help & Troubleshooting

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

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.

[H] Flashing issues

about a week ago when 4.4 roms surfaced for mako, i wanted to try one out. when i did it failed, so i read that you had to either update TWRP or use CWM. so i tried to update TWRP with goo, and goo is down i guess, so someone posted a flashable zip of the newest TWRP(2.6.3.2) and CWM(6.0.4.4) so i got them both, and flashed the TWRP, and it flashed the 4.4 roms. and i used my nandroid to go back to 4.3(Carbon ROM) and now it fails when i try to flash a new nightly (i facrtory resetted) and it failed on my backup too, so i flashed CWM, and rebooted and it fails on everything too. (new nightly, and a copuple of roms i had been meaning to try) and i just fastbooted the official image from teamw.in website (2.6.3.3) and its failing on nightlies, but restored my backup.
what can i do to make it flash again?
should i downgrade to TWRP 2.6.3.0, i think that is where i was and it would flash, I THINK. lol.
please help.

[Q] CM 11 Issues a plenty

Verizon VS980, TWRP 2.6.3.3
Finally, upgraded to the above TWRP, and was able to flash a CM 11 nightly. and Gapps for 4.3.0, 20130813 and to have that finally flash successfully is great! BUT it's not, when I boot into it I get an android system error and the keyboard AOSP error every time, I can't make it past the screen where I enter in my account.
I have wiped and tried again, and again, I have installed the ROM and gapps and then wiped dalvik and cache and same result...
It seems so close.
I have installed ROM Manager as well and it says that CWM is installed yet I cannot seem to boot into it, I have flashed it from the ROM Manager many times and no love. I was able to flash a zip of twrp, is there a zip of CWM that is flashable from twrp, I have heard that cwm works better with CM 11
Please help, I have no idea why going to CM 11 should be such a pain in the..
Thanks!!!
SO i figured it out
I was following/using rootz wiki for my reference of which gapps to use and it is not updated right now
got the right gapps here, and all is good now
http://d-h.st/mDt

[Q] Having trouble installing Quarx's new CM11 build

Hey guys,
As I wrote in the title I ran into a problem when installing the new CM11 nightly build from Quarx on my Defy. Here's what I did:
1) Downloaded the recovery update: http://defy.bytekiste.de/cm11-nightly-defy+/update-recovery.zip
2) Downloaded this CM11 nightly build: http://quarx2k.ru/roms/defy-cm11.0/cm-11-20140501-NIGHTLY-mb526.zip
3) Rebooted into recovery and installed the recovery update. The install seems to have finished without problems, although after another reboot my recovery still read as "JB Recovery v5.7.0-jordan".
4) Did a data and cache wipe.
5) Tried installing CM11, but the installation was aborted by a "status 0" error right after the "installing update..." part.
What am I doing wrong? I assume this has something to do with the recovery update, but since as far as I can tell it was successfully installed I don't know what could I do to fix it.
Now that I got time I started reading Quarx's CM11 thread and apparently in these cases installing CM10.2 first may help (I was using CM10), as it also updates the recovery, which is TWRP in the case of the as of now latest CM10.2 nightly. After I did this I tried installing CM11 again and this time the install went without a hitch. So if anyone else runs into this issue try this first.
For the next time remember that you've to reboot the device after installing that recovery in order to TWRP do the actualization
MaicolS said:
For the next time remember that you've to reboot the device after installing that recovery in order to TWRP do the actualization
Click to expand...
Click to collapse
I did restart my phone after installing the recovery update, I just forgot to mention it.
Since my last post I realized that the problem was that the CM10 nightly build I used before still came with the CWM recovery, not with TWRP. The reason is that some of Quarx's old builds didn't play nice with TWRP at the time. Since Quarx didn't explicitly say in his thread that the recovery update was for TWRP I just assumed that it was for his old builds that came with CWM. That doesn't seem to be the case however.
Chawitsch said:
Now that I got time I started reading Quarx's CM11 thread and apparently in these cases installing CM10.2 first may help (I was using CM10), as it also updates the recovery, which is TWRP in the case of the as of now latest CM10.2 nightly. After I did this I tried installing CM11 again and this time the install went without a hitch. So if anyone else runs into this issue try this first.
Click to expand...
Click to collapse
Easier method: just flash defy_twrp_recovery_2.6.3.0.zip, as explained in the installation guide.
Thanks for the link Proverbs, I'll do that the next time I'll need to update TWRP. Like I said, I didn't realize that Quarx's recovery update was for TWRP. If I did, I would have flashed TWRP separately and then CM11. What matters is that everything turned out OK in the end.

Can't boot to recovery.

Phone is Lenovo A6000, not plus. I installed multiple TWRPs, 3.1.0 and 2.9 something.
I even installed CWM, still couldn't boot to the recovery.
Now, I know how to flash with fastboot, and I know how to boot. Booting doesn't work at all, it says "booting" and never finishes.
Flashing says "okay" and I reboot, do a reboot to recovery, and I get put into bootloader/fastboot.
Any help? I just bought the phone today, no one messed with it.
Edit: Nevermind. CWM installed. How do I install TWRP, so it works? Also, forgot to mention that the phone has the latest stock rom, 4.4.4.
Edit#2: While trying to install "TWRP-3.1.0-Lenovo-A6000.img",
I got an error.
"Can't open /tmp/update.zip (bad)"
"Installation aborted."
Edit#3: Same error with multiple TWRP images.
First of all the twrp 3.1.0 is meant for nougat roms. Since you are flashing that recovery on KitKat rom which it won't support. So first try updating phone to stock lollipop. Then flash twrp 2.8. then take a complete backup(most important) and save it on SD card. After that flash any rom you want. If you are flashing marshmallow or nougat rom then after flashing rom flash 3.1.0 twrp.
I have long ago (10 minutes after last edit) fixed the problem already by flashing stock firmware through some weird software, and then started updating to latest lollipop firmware, and then installed TWRP 3.1 and then installed RR android version 7.1.2. But, thank you for trying to help. I hereby ask a moderator to close the thread because the problem was resolved. Thank you.

Categories

Resources