(First off, XDAFAIL. So if you have made 10 posts you instantly get smarter and get allowed to post in devolpment sub-forum section )
I edited the link (correct topic now):
[ROM][ICS 4.0.4][3G] CyanogenMod9 (29 Mar) (Cornerstone Available)
I have fully rooted transformer. At the moment I have the rooted latest official Asus version. I have cloackworkMod Recovery V.3.2.0.1 gee one-tf101-ww (is this outdated? I had the one that has the rebootloop issue).
When trying to install the zip after wiping cache (dalvik,...) it gives me the fallowing error:
Code:
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "tf101" || getprop("ro.build.product") == "tf101"
E:Error in /sdcard/cmp9/update-cm-9.0.0-RC0-tf101-KANG-29Mar-signed.zip (status 7)
Installation aborted
(the .zip file is not corrupted... md5 result is the same)
So anyone know what the problem might be? I am gona look some more into this and try and install another clockwordMod.
Why are you linking [ROM][1.APR.2012][3G]AOKP (Android Open Kang Project) *OFFICIAL* [v1.8] Build 29! when you are trying to flash update-cm-9.0.0-RC0-tf101-KANG-29Mar-signed.zip?
The 10 post rule worked really well here since you would have posted in the wrong thread anyway.
Not sure if it has anything to do with your problem but you should update to CWM 5 by Roach.
When trying to install the zip after wiping cache (dalvik,...)
Click to expand...
Click to collapse
uh.. you are coming from stock ASUS rom. To avoid possible complications, you should wipe more than just dalvik cache. Do a full wipe.
horndroid said:
Why are you linking [ROM][1.APR.2012][3G]AOKP (Android Open Kang Project) *OFFICIAL* [v1.8] Build 29! when you are trying to flash update-cm-9.0.0-RC0-tf101-KANG-29Mar-signed.zip?
The 10 post rule worked really well here since you would have posted in the wrong thread anyway.
Not sure if it has anything to do with your problem but you should update to CWM 5 by Roach.
uh.. you are coming from stock ASUS rom. To avoid possible complications, you should wipe more than just dalvik cache. Do a full wipe.
Click to expand...
Click to collapse
Hmm, no I just made a error linking the wrong topic (I wouldn't have had to do that if I could just reply to the topic at hand). And yes, I am doing a full wipe (hence the "...").
The topic this relates to is:
[ROM][ICS 4.0.4][3G] CyanogenMod9 (29 Mar) (Cornerstone Available)
Btw, damm you reCaptcha! Its sometimes hard to read :S (i keep asking for new ones )
edit:
I found the problem! It was indeed because of the clockwork version (installed the team rogue version back again (wish is way better anyways!) and it works fine now).
Related
I'm getting error with ClockworkMod v3.0.0.5 when flash roms, before I'm using RA-Tattoo-v1.6.2 and there is no problem with that.Today I try to flash CyanogenMod Gingerbread 2.3.2 RC0 so i installed ClockworkMod v3.0.0.5 from terminal and when try to flash I'm getting this error..
Findind update package..
Opening update package..
Installing update..
assert failed: getprop("ro.product.device") =="click" || getprop("ro.build.product")
"click" || getprop("ro.product.board") == "click"
E:Error in /sdcard/kalim.Ginger.11.2.zip
(status 7)
Installation aborted.
currently i have pancake rom 1.06 on my tattoo
when I try to flash HCDR.ROM_v1.7.zip I'm getting this message
Installing update..
Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in android 1.5
It was necessary to remove it when upgrading to ClockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to creat working update zip packages.
Installation aborted.
*Guys plz tell me is there any solution to install the CyanogenMod Gingerbread 2.3.2 RC0
*If i need to install any other rom do I need to flash RA-Tattoo-v1.6.2 again.
I don't understand you people.
You make a new thread to describe an error which is already discussed and solved on the thread from which you download the rom.
You just need to read the 3-4 last pages to find the answers.
dancer_69 said:
I don't understand you people.
You make a new thread to describe an error which is already discussed and solved on the thread from which you download the rom.
You just need to read the 3-4 last pages to find the answers.
Click to expand...
Click to collapse
sorry my fault i only check the 1st 3-4 pages and the last page.thanks for the reply..
I installed the modded ClockworkMod v3.0.0.5 and now I'm able to flash KalimGinger.11.3 rom.
My device is:
- 183825U
- ThinkPadTablet_A310_02_0039_0086_US I use ThinkPadTablet_A310_02_0039_0086_US_CWR_MOD.zip
- Root
- CWM-based Recovery v5.5.0.4
I download the ThinkPadTablet_A310_02_0039_0089_US.zip try install by CWM
Show this:
assert failed: getprop("ro.product.device") ++ "Indigo" || getprop("ro.bluid.product") == "Indigo"
E:Error in /sdcard/ThinkPadTablet_A310_02_0039_0089_US.zip
(Status 7)
Instalattion aborted
I think you have to edit the update script. There is a thread in the general section.
One question: are you US, WE, or ROW? You have to use Device specific rom.
Moved To General​
This is a development section, its not for questions​
why not just flash stock recovery to udpate?
rangercaptain said:
I think you have to edit the update script. There is a thread in the general section.
One question: are you US, WE, or ROW? You have to use Device specific rom.
Click to expand...
Click to collapse
Hi rangercaptain,
I've the same problem but I use ROW ROM. Could you please advise where can I find the mentioned update script?
emerson - you've updated to 0086 using a tweaked update that works with CWM Recovery as well as skips checking for a few specifics.
You can now use the next tweaked update to get you all the way to 0089/OTA2.5 - since you tried with the official Lenovo update, it failed. Use this one:
ThinkPadTablet_A310_02_0039_0089_US_CWR.zip
pwstein said:
emerson - you've updated to 0086 using a tweaked update that works with CWM Recovery as well as skips checking for a few specifics.
You can now use the next tweaked update to get you all the way to 0089/OTA2.5 - since you tried with the official Lenovo update, it failed. Use this one:
ThinkPadTablet_A310_02_0039_0089_US_CWR.zip
Click to expand...
Click to collapse
This work.
I'm trying to update over OTA to ICS on my 39_0089_SC device.
The update.zip will be downloaded completed.
If a start the update installation (CWR -> install zip from sdcard) I get the following failure message:
assert failed: getprop("ro.product.device") =="Indigo" || getprop("ro.build.product")== "Indigo"
E:Error in /sdcard/update.zip (status 7)
What wrong? I have only tried to flash a ROW image... no success.:crying:
device config:
CWR 5.0.2.7 installed and rooted
original SC image
Pls read the other threads on the forum. This was solved yesterday. Anyway the error is because you have Cwm instead of the normal android recovery. The solve this, comment out the lines of the updater-script that check for "indigo".
another Problem...
now I have comment out the "indigo" lines at the updater-script and made a signed update.zip (fokke.org/site/content/howto-create-android-updatezip-package).
If a try to install the upater.zip from SD card, i get a new failure message:
Installing update...
E:Error in /sdcard/updater.zip (Status 6).....
Have Imade somthing wrong?? Problems with system apps or OTA Rootkeeper?
http://www.thinkpadtabletforums.com...lopment/guide-to-installing-ota-3-(ics-4-03)/
Go here, this is a guide to upgrading to ICS.
solved - ICS Update is working now!
Below the steps what a have done:
1) Download OTA over wifi
2) modified update.zip (indigo update failure messages)
Error 6 was coming from updater-script -> not use notepad to edit!!!
3) generate new update.zip (fokke.org/site/content/howto-create-android-updatezip-package)
4) install OTA RootKeeper (protect root)
5) update "busybox" file from lenovo image (website, system/xbin/busybox)
6) install update.zip over CWR
that's it! now I'm rocking on ICS.....
(CWR is overwritten by the ICS update )
Thanks you guys for help!!!
Good to hear you sorted out your problem. And also thanks for posting the solution that worked for you. That will help the rest of us.
[GUIDE] [SOLVED] HOW TO FLASH CM11 ON BRAVO (Previously "Cm11 Issue, Status 0 Error")
So, I tried to flash CM11 for the MB520 Bravo, found in this post:
http://forum.xda-developers.com/showthread.php?t=2515036
So I copy the ROM .zip to the SD card in my Bravo, and I reboot into CWM Recovery version 5.0.3.9, with the name "CyanogenDefy Recovery v5.0.3.9-jordan" on the top of the screen. This version of recovery came from josuearisty's one click tool for rooting and putting a recovery on the MB520 Bravo, which can be found here:
http://forum.xda-developers.com/showthread.php?t=1559109
I factory reset/clear cache like I know I am supposed to when flashing a custom ROM, but when I select the "Install zip from sd card" option and select the CM11 MB520 Nightly to flash, it gives me this:
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/cm-11-20140407-NIGHTLY-mb520.zip
(Status 0)
Installation aborted.
So then as I read on further in the CM11 install page, it says this: "For CM10,10.1,10.2 < 07.11.13 users: To install KitKat, need update recovery. Do not forget reboot, after install recovery. http://defy.bytekiste.de/cm11-nightl...e-recovery.zip". The thread is for the DEFY+ according to the title, but since I see there's also a Bravo download link, I assume that this means that I should install this updated recovery as well, since I am running the stock rooted 2.2.1, which is in fact "less than" 10.x or 4.x. I select the same "Install zip from sd card" option, and the same Status 0 is presented to me.
Then I go and try putting on CM10.x first, because then according to the thread's instructions I won't have to install this updated recovery if I am running that currently. I find a link for CM10.2 for the Bravo here:
http://forum.xda-developers.com/showthread.php?t=1779324
I download it, do the same install method, and I STILL GET A STATUS 0 saying it is unable to flash the zip!
Now I've done some research, and I THINK the status 0 means the zip is not compatible with my phone. I could see that with the updated-recovery.zip, but I don't see why that is showing up for the ROM's themselves because they are in fact made for the mb520.
Can someone please tell me what I am doing wrong, and if possible post a set of step-by-step instructions as to how I can go installing CM11 on my MB520 Bravo? Thanks.
*BUMP*
UPDATE: I seemed to get around the Status 0 issue in CM10.2 so far. First, I went from 2.2.1 to CM9 4.0.4. Then, I went from CM9 to CM10.1 in quarx2k's "archive" folder on his website. This updated my recovery to TWRP 2.6.0.0. From this new TWRP, I was able to flash the latest 10.2 nightly CM rom. I will keep this posted on how things go, in case anyone out there is actually following this
*BUMP AGAIN, PROBLEM SOLVED*
I got CM11 finally running on the Bravo. Here's the steps I took to get it on there. Some of these steps may be unnecessary, but I'm just going to list EXACTLY what I did in case all of these steps really are necessary:
1) I started out with stock 2.2.1. I rooted it, and used josuearisty's tool for one click root and recovery just to put recovery on it.
2) I flashed a build of CM9 from quarx2k's website. Here is a direct link to download it. Flashing this ROM also updated my cwm recovery. HOWEVER, this new version of recovery had scrolling issues with the volume rocker, so I just rebooted and pressed the vol. down button at the blue flashing LED light to boot into the boot menu. From there, I select to go to recovery, but instead of selecting "Custom Recovery" I select "Stable Recovery". This takes me back to the older recovery I got with the one click tool.
3) I flashed one of quarx2k's builds of CM10.1, which you can get for yourself here. Doing this updated my recovery again. It went from CWM 5 to TWRP 2 (I believe it was 2.6.0.0).
4) I flashed a CM10.2 build for the bravo from quarx2k, which I got from here. This updated my recovery YET AGAIN, to TWRP 2.6.3.0.
5) From here, I was able to flash the update-recvery.zip that is mentioned in the CM11 topic. I don't think this was necessary, because when I then booted into recovery again after flashing the update-recovery.zip, the version number for TWRP still read 2.6.3.0, the exact same as last time. But I just did it anyway to be safe. Here is a direct download link to the update-recovery ZIP mentioned on quarx's CM11 thread.
6) FINALLY, I flash the CM11 nightly zip from quarx2k's website. I get an error, but this time it's not a status 0 error, this tells me that the ZIP is not compatible with my device.
7) I give myself a facepalm, and take 3 deep breaths. "All hope is lost..." I think to myself.
7.5) A GOOGLE SEARCH TELLS ME THAT ALL HOPE IS NOT LOST!!! (that's supposed to signal you to keep reading)
8) Turns out, there is a way to disable the device compatibility check. So what I did was copy the CM11 zip to my pc, and unzip all of its contents. I go to META-INF\com\google\android\, and add a .txt ending to the "updater-script" file, which allows me to open it with Notepad++. It is possible to edit this with plain old Notepad in Windows, but it doesn't format the code very neatly like Notepad++ does. If you open the file in Notepad and Notepad++ and compare them you will see what I mean. Anyway, the line of code that reads...
assert(getprop("ro.product.device") == "mb520" || getprop("ro.build.product") == "mb520" || abort("This package is for \"mb520\" devices; this is a \"" + getprop("ro.product.device") + "\"."); (ignore that winking face in the line of code, that is supposed to be a "; )" but without the space between them.)
... was the one I deleted from the updater-script file. This should be the first line of code. I save, exit Notepad++, and remove the .txt ending from the updater-script so that it returns to an unknown filetype. Now, I take the META-INF, system, and file_contexts files that came from the original CM11 ROM zip and I create a NEW ZIP with all of the NEW files and folders.
9) I reboot to TWRP with the ROM zip copied to my phone's SD card, and I flash the new, fixed ROM zip. "Installation completed."
10) My Bravo is rebooted, it boots up, and i get a "Welcome!" bubble in my brand-new homescreen in KitKat
11) I nearly cried. Seriously.
So looking back I think it was really the recovery that was the issue for the Status 0 problem, and the only real way to update the recovery and solve the Status 0 problem is by flashing all these ROMs in the order I mentioned, but that's as far as I know, there may be a better and quicker way to do this that I just don't know about.
So basically this thread turned into a how-to. I wanted to post the instructions here because on the CM11-for-the-Defy-and-Bravo topic did NOT have any instructions whatsoever for flashing the Bravo CM11 build on the Bravo. If anyone has questions about what I wrote, then you can certainly post them below and I'll respond to them as soon as I can, and I'll answer them to the best of my abilities.
Thanks for the Guide
I just wanted to thank you for this well-written, step-by-step guide. I haven't tried it since I'm a beginner and need some more reading to do. I'm glad you overcame those issues, though.
Anyway, I wanted to ask you how smooth it ran and if it was worth it. Also I'm starting with Android 2.1, would that make a difference?
Gastnow said:
I just wanted to thank you for this well-written, step-by-step guide. I haven't tried it since I'm a beginner and need some more reading to do. I'm glad you overcame those issues, though.
Anyway, I wanted to ask you how smooth it ran and if it was worth it. Also I'm starting with Android 2.1, would that make a difference?
Click to expand...
Click to collapse
I think you should upgrade to 2.2.1 to make sure the one-click tool works with it because I do not know if the one click root and recovery works with 2.1. Upgrade to 2.2.1 just to be safe.
Sent from my SAMSUNG-SGH-I847
Thanks for the guide
Appreciate the work. What gapps are you using.
Doesn't have much support
I tried it. A lot slower then CM7.2 and very difficult to get my most important apps working (and I don't use many).
I would not recommend it for a daily (as mentioned on the Defy link). But, has potential if a developer takes up the task.
ilikepcs said:
Appreciate the work. What gapps are you using.
Click to expand...
Click to collapse
ilikepcs said:
I tried it. A lot slower then CM7.2 and very difficult to get my most important apps working (and I don't use many).
I would not recommend it for a daily (as mentioned on the Defy link). But, has potential if a developer takes up the task.
Click to expand...
Click to collapse
The gapps for this KitKat ROM can be found here. This came from the 4.4 thread:
QUARX2K'S KITKAT GAPPS
I used this as a daily driver for a little bit, until an update (I believe was from April 10th) with the Android 3.0 kernel broke the Camera. Whenever you would try to open the camera it would say "Can't connect to Camera". I'm not sure if this issue was fixed since then, and I know the versions before this had the 2.x kernel which was fine with the camera. I lent my Bravo to a family member because their phone broke, so I can't really do anything with the phone because it is not in my possession.
Anyway, check back at this thread and the link that it gives to the Bravo version of 4.4 to keep up with the latest version. This thread does not give a change log for the BRAVO version, but I assume that it's basically the same as the main version that the majority of the thread is talking about:
ANDROID KITKAT FOR DEFY AND DEFY PLUS (ALSO FOR THE MOTOROLA BRAVO)
Help please
The procedure to install cm11 after October 1 is the same? Or did it change? @jasonmerc
Quarx on their website does not mention cm10 and cm10.1
Sent from my mb520 using XDA Free mobile app
@jasonmerc
You are not using CM11 anymore? Do you know if the camera problem has been solved (I assume that with the 2.6.x kernel the original motorola camera drivers were used which most likely do not work with a 3.x kernel)? What was your general experience (especially regarding performance) with CM11 on the Bravo?
Thanks,
Markus
oldschool63 said:
@jasonmerc
You are not using CM11 anymore? Do you know if the camera problem has been solved (I assume that with the 2.6.x kernel the original motorola camera drivers were used which most likely do not work with a 3.x kernel)? What was your general experience (especially regarding performance) with CM11 on the Bravo?
Thanks,
Markus
Click to expand...
Click to collapse
Its been forever since I've used my Bravo let alone CM11. From what I can remember the new CM11 was EXTREMELY FAST compared to other ROMs. The only issue was the camera.
Sent from my LG-D415 using XDA Free mobile app
can you create a backup of it because some of the downloads don't work i got cm 9 4.0.4 im 12 and i ran into
a problem on cm 10.1 i cannot download it or flash it thx
PROBLEM FOUND AND FIXED! Answer in Post #3
http://forum.xda-developers.com/showpost.php?p=53784248&postcount=3
Hey guys
I've been trying to install MIUI for hours, using both CWM or TWRP, and I'm always receiving the same error message:
Writing recovery
set-perm: some changes failed
E:Error in /sdcard/miui_i9500_4.6.20_27061504e7_4.2.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
I've flashed CM without a problem, and an original stock ROM as well.
Why is MIUI giving me a hard time?
**I already followed this guide: http://en.miui.com/thread-13226-1-1.html**
Thank you!
Omga4000 said:
Hey guys
I've been trying to install MIUI for hours, using both CWM or TWRP, and I'm always receiving the same error message:
I've flashed CM without a problem, and an original stock ROM as well.
Why is MIUI giving me a hard time?
**I already followed this guide: http://en.miui.com/thread-13226-1-1.html**
Thank you!
Click to expand...
Click to collapse
Use Philz recovery (just flash zip attch in rec) it's something to do with the older binary code-that's why it's status 7 ?
Well, after deciding to fix this problem once and for all, I added a "ui_print" after
every (well not every) line, to see exactly where is the installation failing.
The discovery? It fails at:
set_perm(0, 0, 0555, "/data/local/tmp/relink");
Click to expand...
Click to collapse
The solution?
Change all "/data/local/tmp/relink" into "/tmp/relink" like so:
package_extract_file("META-INF/com/miui/relink", "/tmp/relink");
set_perm(0, 0, 0555, "/tmp/relink");
run_program("/tmp/relink");
delete("/tmp/relink");
Click to expand...
Click to collapse
Problem solved - clean installation with no errors
Hi Anyone having issue with offline charging in MIUI ROM ?
Sent from my GT-I9500 using XDA Premium 4 mobile app
Omga4000 said:
Well, after deciding to fix this problem once and for all, I added a "ui_print" after
every (well not every) line, to see exactly where is the installation failing.
The discovery? It fails at:
The solution?
Change all "/data/local/tmp/relink" into "/tmp/relink" like so:
Problem solved - clean installation with no errors
Click to expand...
Click to collapse
Hi! sorry
Please how can I clearly follow your guide I'm Noob and dont really know about this. So can you please guide me with a step by step.
Thanks for understanding
mckalyster said:
Hi! sorry
Please how can I clearly follow your guide I'm Noob and dont really know about this. So can you please guide me with a step by step.
Thanks for understanding
Click to expand...
Click to collapse
1) Extract "updater-script" from the ROM file (using winrar for example)
It's located in META_INF > COM > GOOGLE > ANDROID
2) Change the parts I wrote in the previous post
3) paste the "updater-script" file inside the rom
Good luck
i9500 MIUI Flashing Error
After downloading the MIUI ROM, open with winrar and locate the updater-script
\META-INF\com\google\android\updater-script
and remove the first line of code
getprop("ro.product.device") == "ja3g" || getprop("ro.product.device") == "ja3g" || abort("This package is for "ja3g" devices; this is a "" + getprop("ro.product.device") + "".");
save and update from the winrar app.
Try flashing again but disable the zip verification......Done
Big ups to Edwin270
i have installed cwm recovery in my mi4 and forgot which rom i have installd just to update the android version from kitkat to marshmallow(6.0)after installed it converted into completely android phone there is no sign of miui rom so plz tell me how to get it back. even i have tried to installed miui 8 rom bt it showing 'installation aborted' i have tried many times in a differnt way i have tried everything but still i am not able to install zip file that is miui 8 rom. please help anyone wht to do now?
Don't use cwm, use twrp to flash custom roms.