Problems flashing KatKiss 5.1_030c ROM - Eee Pad Transformer Q&A, Help & Troubleshooting

I am running an Asus TF101 B90 tablet. I have just rooted and installed KatKiss 4.4.4_036. I am using ClockworkMod v 3.2.0.1 roach2010-tf101-r1 for recovery. This appears to work fine. I have tried the defined step,s both before and after flashing the 4.4.4 ROM, to flash the 5.1 ROM without success. I have tried this with both a full wipe and without. The results are always the same. After it starts the install the system gives me the following error messages:
Set_metadata_recursive: some changes failed
E:Error in /sdcard/KatKiss-5.1_030.zip
(Status 7)
Installation aborted
I have the same issue with KatKiss-5.1_030c.zip. Yesterday was the first time I rooted an android device. Any recommendations on what and how I need to change things so I can move to Lollipop? Thanks.
John

jdwbmc said:
I am running an Asus TF101 B90 tablet. I have just rooted and installed KatKiss 4.4.4_036. I am using ClockworkMod v 3.2.0.1 roach2010-tf101-r1 for recovery. This appears to work fine. I have tried the defined step,s both before and after flashing the 4.4.4 ROM, to flash the 5.1 ROM without success. I have tried this with both a full wipe and without. The results are always the same. After it starts the install the system gives me the following error messages:
Set_metadata_recursive: some changes failed
E:Error in /sdcard/KatKiss-5.1_030.zip
(Status 7)
Installation aborted
I have the same issue with KatKiss-5.1_030c.zip. Yesterday was the first time I rooted an android device. Any recommendations on what and how I need to change things so I can move to Lollipop? Thanks.
John
Click to expand...
Click to collapse
You need to install a recent recovery
See the link in the 1st post of the rom installation instructions

Thanks!
timduru said:
You need to install a recent recovery
See the link in the 1st post of the rom installation instructions
Click to expand...
Click to collapse
Tim,
First of all thanks so much for your work keeping the ASUS TF101 alive and working! It means a great deal. I did flash the TWRP 2.8.1 recovery system. That worked fine. I was then able to flash the KatKiss-5.1_030c ROM. I am now running Lollipop 5.1.1! Two questions. I ran Root Checker Basic. It can no longer validate that I am rooted, though it could when I ran 4.4.4. Is this to be expected or is there something I need to fix? Secondly, Lollipop seems a bit slower than 4.4.4. Is this to be expected or is there something I need to change to up performance? Thanks.
John

Related

jb installation failed

mates,
I need your help on installing JB with CW 6.0.0.7. I have a 9023 with ICS 404 stock, rooted, with busy box installed. I tried to instal the jb download from google site (9ZGgDXDi.zip) and I get the following error:
installing update...
verifing current system...
assert failed: apply_patch_check("/system/build.prop", "5a11755c3b67986b1ea8beb466955e9339e3de2c1". "db469a8330031cea064b24c5ff8d7da080a79557")
E:Error in sdcard/applic utili/9ZGgDXDi.zip
(status 7).
Installation aborted.
I had the same problem installing it via ota at the same point.
I tried to change also the CW installing the 5082 but nothing.
Someone can help me to install the JB on my nexus???
thanks
Check out this post: http://forum.xda-developers.com/showpost.php?p=28734976&postcount=970
flobin said:
Check out this post: http://forum.xda-developers.com/showpost.php?p=28734976&postcount=970
Click to expand...
Click to collapse
I restored a backup of my system where busybox was not installed and I got the same problem.
Could you be so kind to link here these three files. To be honest I'm not so expert fo find them alone.
thanks
I went to stock by doing this. http://forum.xda-developers.com/showpost.php?p=29073020&postcount=1
I didn't flash the updates in the second part #1 but you could just flash instead. I logged everything in then did this to get the 4.1.1 http://forum.xda-developers.com/showpost.php?p=29067584&postcount=2817
Go into airplane with a strong wifi signal on for this to work.
I then rerooted (2nd part #2 on)
Hope this helps.

[Q] Updating to 4.1.1 OTA

I am trying to update my Nexus S i9020a (currently on stock 4.0.4) to stock Jelly Bean, but I'm running into some problems.
First, I got the notification that said there was an OTA update available for 4.1.1, so I started downloading it. After verification, it starting the countdown timer for restarting. When the counter reached 0, my phone did not update, but instead just told me that I was up to date.
I thought that was weird, so I used this thread to download the ota for manual installation. I rebooted into recovery and selected the update. I got the following:
Code:
Verifying current system...
assert failed: apply_patch_space(16570800)
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
I didn't mind losing my data since I have everything backed up, so I went to this page to download the official images. I followed the instructions to flash the stock bootloader, recovery, and 4.0.4 ROM.
The same thing happened. I got the OTA notification, it downloaded and nothing happened. I tried manual install, but got the Status 7 error.
I then downloaded Google's official Gingerbread image and flashed that. I got a notification for the 4.0.4 update. It installed without any problem. Once that was done, I got another notification for the 4.1.1 update. It didn't work, though. The countdown started, but the phone did not reset and it said the phone was up to date. I tried the manual update again and got another Status 7.
Sorry if this is a bit long, but I wanted to say everything I have tried. I have looked through other threads and they mention using CWM, but I would rather not use a custom recovery. I prefer to stay on stock for now.
Gregsaw said:
I am trying to update my Nexus S i9020a (currently on stock 4.0.4) to stock Jelly Bean, but I'm running into some problems.
First, I got the notification that said there was an OTA update available for 4.1.1, so I started downloading it. After verification, it starting the countdown timer for restarting. When the counter reached 0, my phone did not update, but instead just told me that I was up to date.
I thought that was weird, so I used this thread to download the ota for manual installation. I rebooted into recovery and selected the update. I got the following:
Code:
Verifying current system...
assert failed: apply_patch_space(16570800)
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
I didn't mind losing my data since I have everything backed up, so I went to this page to download the official images. I followed the instructions to flash the stock bootloader, recovery, and 4.0.4 ROM.
The same thing happened. I got the OTA notification, it downloaded and nothing happened. I tried manual install, but got the Status 7 error.
I then downloaded Google's official Gingerbread image and flashed that. I got a notification for the 4.0.4 update. It installed without any problem. Once that was done, I got another notification for the 4.1.1 update. It didn't work, though. The countdown started, but the phone did not reset and it said the phone was up to date. I tried the manual update again and got another Status 7.
Sorry if this is a bit long, but I wanted to say everything I have tried. I have looked through other threads and they mention using CWM, but I would rather not use a custom recovery. I prefer to stay on stock for now.
Click to expand...
Click to collapse
First to flash an update u need a custom recovery. if not u will get that error
second dont mind to use a custom recovery bcz after the update your recovery will be back to stock
if this helped dont forget to hit that thanks button
Cascabreu said:
First to flash an update u need a custom recovery. if not u will get that error
second dont mind to use a custom recovery bcz after the update your recovery will be back to stock
Click to expand...
Click to collapse
I didn't realize the update wrote over the recovery. Thanks
Gregsaw said:
I didn't realize the update wrote over the recovery. Thanks
Click to expand...
Click to collapse
on any stock rom, at each boot it will overwrite the recovery
So I could use fastboot/adb to install the custom recovery, then install the zip from sd and the phone would be exactly the same as it would be if I were to receive the update notification directly and installed it that way? Should I wipe cache and dalvik in this scenario?
TheIowaKid said:
So I could use fastboot/adb to install the custom recovery, then install the zip from sd and the phone would be exactly the same as it would be if I were to receive the update notification directly and installed it that way? Should I wipe cache and dalvik in this scenario?
Click to expand...
Click to collapse
yes it's exactly the same, if u want u can wipe cache and dalvik before flashing (that's even recomended from some devs )

[Q] T-mobile LG G2 TWRP won't install CM11 ROM

Hi Guys,
Urgent issue. I rooted the device using Kingo, installed TWRP and then transferred the zip for the CM11 nightly and the gapps. I confirmed the nightly was for the D801 model which is T-mobile and the version of the G2 I have. Like a fool I forgot to backup my previous rom and TWRP says:
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11-20140208-NIGHTLY-d801.zip'
Error flashing zip '/sdcard/cm-11-20140208-NIGHTLY-d801.zip'
Updating partition details
And there's a red ominous 'Failed' at the bottom of the prompt. Please help, I have no idea what to do, I'm a noob at this. Help is greatly appreciated, thank you!
Regards
mysticgohan_92 said:
Hi Guys,
Urgent issue. I rooted the device using Kingo, installed TWRP and then transferred the zip for the CM11 nightly and the gapps. I confirmed the nightly was for the D801 model which is T-mobile and the version of the G2 I have. Like a fool I forgot to backup my previous rom and TWRP says:
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11-20140208-NIGHTLY-d801.zip'
Error flashing zip '/sdcard/cm-11-20140208-NIGHTLY-d801.zip'
Updating partition details
And there's a red ominous 'Failed' at the bottom of the prompt. Please help, I have no idea what to do, I'm a noob at this. Help is greatly appreciated, thank you!
Regards
Click to expand...
Click to collapse
Can you restore the phone and boot back up? If so, replace TWRP with Philz Touch CWM. I had trouble flashing kit kat rom with TWRP too. But Philz Touch recovery seems to works just fine and it also has the option with restore a backup from TWRP too.
super114 said:
Can you restore the phone and boot back up? If so, replace TWRP with Philz Touch CWM. I had trouble flashing kit kat rom with TWRP too. But Philz Touch recovery seems to works just fine and it also has the option with restore a backup from TWRP too.
Click to expand...
Click to collapse
Hi, thanks for your reply. I have resolved all issues. Turns out you need TWRP 2.6.3.5 to flash any CM11 nightlies. Also was using Windows 8.1 so the adb drivers were not straightforward to install to use adb push. I pushed and installed TWRP 2.6.3.5 and then flashed CM11 and she works like a dream!

[Q] stuck on TWRP 2.5.0.0 + cannot install cm11

lets get down to business,
I'm currently running CM10.2.0 with TWRP 2.5.0.0 as recovery, I recently tried updating to latest CM11 M4 snapshot but received the following error:
"error executing updater binary"
I read that i need to update recovery (2.6.3.0 latest) but encountered a roadblock.
I downloaded the .img to internal memory in root directory and used the terminal emulator as per TWRP instructions, rebooted into recovery but it still showed 2.5.0.0. I then tried using ADB but ran into the same issue
I've thought about using CWM but when I install ROM toolbox it says only tf200 is officially supported.
lastly tried Goomanager but it gave me an error saying recovery not found.
any thoughts on this?
any ideas would be appreciated
ok, tried a different version of TWRP (4.2 as opposed to JB) and it worked though cm11 still wont flash
n00b1c1d3 said:
ok, tried a different version of TWRP (4.2 as opposed to JB) and it worked though cm11 still wont flash
Click to expand...
Click to collapse
What is your bootloader version is it 10.1.6.27.x
The last digit really does not matter...
If so you need this recovery here http://forum.xda-developers.com/showthread.php?t=2691886
Let me know if I can help you with anything else..
Thx Josh
ended up using that method and all went well.
thanks

Issue Flashing SuperSU-v2.79-201612051815, and other small issues

Hi all, I'm trying to get my TF101 up to speed so to speak. I had previously ( a year or 2 ago) installed TWRP and a Jelly Bean ROM, and decided to update to KatKiss. After some tribulation, I got TWRP updated so I could install the ROM, and I got KatKiss installed. However, I'm having issues flashing SuperSU. Whenever I install the ZIP via TWRP recovery, I get the following message:
Code:
- Placing files
********************
-Finding boot image
--- Boot image: not found, aborting
Then a warning telling me not to let TWRP install SuperSU if it asks (it doesn't) and TWRP tells me the install was Successful. But no SuperSU is installed when I boot into KatKiss. Any idea why this is happening?
Also, I flashed the Pico version of OpenGApps, and am constantly getting a message saying GooglePlay Services has stopped working. Any help on this would be appreciated to.
Thanks!
EDIT: In my frustrations, I thought maybe it would be best to go back to stock and start at square one. I used EasyFlasher to go back to the stock Asus ROM and unroot everything. I'll give installing KatKiss another go tomorrow. I guess mods can delete this thread.
mods, this thread can be locked/deleted.

Categories

Resources