Installation keeps aborting (Status 7) every time I try to install the latest CM11 nighties on my TF700. I am using CWM v6.0.3.1 (I believe the latest one). I've also tried previous versions of CM11 and they also won't flash, CM10.2 seems to work fine.
Any help would be great!
Thanks!
Update Recovery
mangcool said:
Installation keeps aborting (Status 7) every time I try to install the latest CM11 nighties on my TF700. I am using CWM v6.0.3.1 (I believe the latest one). I've also tried previous versions of CM11 and they also won't flash, CM10.2 seems to work fine.
Any help would be great!
Thanks!
Click to expand...
Click to collapse
You need to update your recovery to 6.0.4.6 recovery.
foothill17 said:
You need to update your recovery to 6.0.4.6 recovery.
Click to expand...
Click to collapse
Got it! Thanks!
Didn't know that's the latest one that supports KK.
Switched back to CM 10.2, though. CM11 is a little laggy and unresposive at times on the TF700.
Thanks for your help!
Related
When trying to "Clean" flash CM11 (cm-11-20131211-Nightly-d2vzw.zip) with CWM (newest version) I get a (status 7) error and installation is aborted. Any ideas, I search the forums and tried a couple things to no avail, first time i've ever seen this when flashing a rom. thanks in advance!
Can you flash other roms or is it just this nightly? Try flashing an older nightly and see what happens. Make sure you have cwm 6.0.4.3
DJz3r0 said:
When trying to "Clean" flash CM11 (cm-11-20131211-Nightly-d2vzw.zip) with CWM (newest version) I get a (status 7) error and installation is aborted. Any ideas, I search the forums and tried a couple things to no avail, first time i've ever seen this when flashing a rom. thanks in advance!
Click to expand...
Click to collapse
You must be on an older version of twrp. Newest fixes that
Sent from my SCH-I535 using xda app-developers app
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
Hi there,
I flashed a KitKat port to test it. However, I decided to go back to Cyanogenmod since it didn't work very well.
However, any ROM that I try to flash appears this error:
format() expects 5 args, got 3
E: Error in /storage/sdcard0/cm-7.2.0-p500.zip
(Status 7)
Installation aborted
what can I do to fix this? thanks
Athosbr99 said:
Hi there,
I flashed a KitKat port to test it. However, I decided to go back to Cyanogenmod since it didn't work very well.
However, any ROM that I try to flash appears this error:
format() expects 5 args, got 3
E: Error in /storage/sdcard0/cm-7.2.0-p500.zip
(Status 7)
Installation aborted
what can I do to fix this? thanks
Click to expand...
Click to collapse
To flash that KitKat, you had to place a newer CWM or TWRP recovery version.
To flash cm-7.2, you need to go back to the older recovery!
For KitKat ROMs a recovery equivalent to 6.0.4.5 or newer is required to flash. The newer recoveries are capable of flashing CM 10.2 to CM11. All older Android versions will require the use of an older recovery, pre 6.0.4.5, such as CWM 5.0.2.7 Touch by vivekkalady.
Dovidhalevi said:
To flash that KitKat, you had to place a newer CWM or TWRP recovery version.
To flash cm-7.2, you need to go back to the older recovery!
Click to expand...
Click to collapse
shinobisoft said:
For KitKat ROMs a recovery equivalent to 6.0.4.5 or newer is required to flash. The newer recoveries are capable of flashing CM 10.2 to CM11. All older Android versions will require the use of an older recovery, pre 6.0.4.5, such as CWM 5.0.2.7 Touch by vivekkalady.
Click to expand...
Click to collapse
nice to know that. I will try later
In other subject, I tried other kitkat roms and they gave me that same error. the only one that worked was Omega. is there any reason to that?
Athosbr99 said:
nice to know that. I will try later
In other subject, I tried other kitkat roms and they gave me that same error. the only one that worked was Omega. is there any reason to that?
Click to expand...
Click to collapse
Sorry, I honestly can't say. I no longer use this device so I've been out of the loop for some time now.
Also having same problem
Can't Flash anyother rom after kitkat port.
plz help me.
Thanks
DevG said:
Can't Flash anyother rom after kitkat port.
plz help me.
Thanks
Click to expand...
Click to collapse
Have you installed any custom kernel?
I am also faced this problem and solved by flashing stock rom with KDZ
Hi,
i'm using the official CM 11 on my XT925 and pretty much installed every new Nightly - never had any serious Problems, not even with Bluetooth (i get no Track in the Display, but at least it works ).
Since the 01.07.2014 Nightly i can't install the Nightlys anymore, because it wants a KK/ Kernel 3.4 compatible Bootloader. First, i flashed the new TWRP 2.7.1.0. Didn't work, very strange Problem (see below). So then i tried the new CWM 6.0.4.9. Also didn't work... same error message as with CWM 6.0.4.4 (which I used until now) - "no KitKat Compatible recovery detected". So I tried philz touch recovery. Also doesn't work.
Now i'm back with the 30.06.2014 Nightly.
Now the strange part: TWRP didn't recognize any touch inputs at all, I had to hard-reboot the phone. Also Philz touch recovery didn't recognize any touch inputs. CWM 6.0.4.4 hat the "Swipe-Touch" thingy, which I used, but it seems that CWM 6.0.4.9 also doesn't recognize any touch inputs! I can't swipe.
So the big questions are: What the hell have I done wrong, that no Recovery is not recognizing any touch inputs anymore?! Flashed it with fastboot, everything looked ok, only got an "ERROR: could not get pipe properties", but it flasehd it and it worked - apart from the touch.
It wouldn't even be such a big "bother" if the new CWM could install the new CM Nightly... Am I really stuck with 30.06.?
greetings,
David
Both of those recoveries are designed for the new kernel/bootloader, and CM11 now runs off the new kernel. You'll need to update to run the newer CM11.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
Both of those recoveries are designed for the new kernel/bootloader, and CM11 now runs off the new kernel. You'll need to update to run the newer CM11.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
So, to install new nightlies we have to flash the KK OTA first, right?
TYG
pbosio said:
So, to install new nightlies we have to flash the KK OTA first, right?
Click to expand...
Click to collapse
Take a look HERE.
If I were you I'd wait for the official kk bootloader....if you read the previous post the method being used is risky for our model.
Sent from my RAZR HD using XDA Free mobile app
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