Database Users

Cant install custom Room's

Hello, i just bought Nexus S i9020 from Carphone Warehouse UK, and just cant install ICS rooms. in ClockworkMod Recovery 3 it says:
assert failed: get.prop("ro,product.device") == "crespo" || get.prop("ro.build.product") == "crespo"
E:Error in /sdcard/cm_crespo-ota-eng.kalimochoaz.a20.p1.zip
Status 7
This is: [ROM] [i9020/23] CyanogenMod 9 v4.0.3 Alfa 20p1 room
Also tried MIUI: http://miuiandroid.com/2012/01/miui-rom-2-1-6-ics-v4-0-miuiandroid-english-version/
Update: just tried office stable build CM7.1, same...
I searched and found on other forum that this could be wrong device. But how is this possible, i know that it's Nexus S and not Nexus S 4G, and on the back where is SN it says i9020
And when going to ClockworkMod Recovery it takes about 1min to get there? for example booting to bootloader and then going to Recovery, and it loads CWM about 1min maybe longer. I also tried differenced recovery it also takes about 1 min to load, can’t remember how it called but i used Root Guide from this source: http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
I hope some one will know what is the problem. Thank you for your time.

Update your recovery. CWM is on version 5.
Also make sure you are installing via the install zip from SD card method and not the install update.zip
Sent from my Nexus S 4G using xda premium

you need to update your clockworkmod recovery to v5.X.X.X , your version is old.

Fast responce thank you

[Q] [L7] Can't install CM, Status 7

I've been trying to install the April 7th Nightly of CM 10 on my L7, but the installation aborts on the product check.
Code:
assert failed: getprop("ro.product.device") == "p700" || getprop ("ro.build.product") == "p700"
The phone is a P700, not a 705 or 708 and is currently running the pre-rooted V20a with CWM v6.0.2.8.
Any advice?

Sorry, found out in the meantime that this seems to be a bug in the touch-based CWM.

Eismagier said:
Sorry, found out in the meantime that this seems to be a bug in the touch-based CWM.
Click to expand...
Click to collapse
Had this problem too, just edit the updater-script and remove that specific line.

Download ROM Manager and install the official CWM recovery and then flash CM. Then you won't get any error.
Sent from my GT-I9070 using xda premium

Thanks, I'll keep that in mind for next time. For now, I'm using the non-touch CWM.

[Q] cyanogenmod failed to install, stuck in recovery

I've searched for a good three hours now and can't find a solution. Here's my problem, I got root, I got TWRP, I tried to install cyanogenmod, when it's installing it just stops and says FAILED in big red letters. The small letters say error executing update binary in "cyanogenmod.zip" I tried rebooting into android it just goes back to twrp. ive tried reflashing the .zip, same error. I've tried every flash to stock method I could find and those get stuck on the attached picture's step. I'm really close to giving up and am very frustrated. please help thanks. Oh and i have the att version.

I'm having a very similar problem. I was able to install TWRP just fine. However, during the installation of Cyanogenmod 10.2, it gave me these error messages: "assert failed: run_program("/sys/bin/loki.sh," "E:Error executing updater binary in zip '/sdcar", and "Error flashing zip '/sdcard/cm-10.2.0-d800.zip.'" Now, whenever I turn my phone on, it displays the LG logo with "Security Error" written underneath it. I tried doing a factory reset in TWRP, but that didn't fix the problem.
Here's loki.sh:
Code:
#!/sbin/sh
#
# This leverages the loki_patch utility created by djrbliss which allows us
# to bypass the bootloader checks on jfltevzw and jflteatt
# See here for more information on loki: https://github.com/djrbliss/loki
#
export C=/tmp/loki_tmpdir
mkdir -p $C
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=$C/aboot.img
/system/bin/loki_patch boot $C/aboot.img /tmp/boot.img $C/boot.lok || exit 1
/system/bin/loki_flash boot $C/boot.lok || exit 1
rm -rf $C
exit 0
Edit:
I ended up using this guide to revert my G2 to its original state. While I'm not sure why Cyanogenmod failed to install, I suspect it may be because the version I used was not designed for the most recent OTA update (10o).

jtmaher said:
I'm having a very similar problem. I was able to install TWRP just fine. However, during the installation of Cyanogenmod 10.2, it gave me these error messages: "assert failed: run_program("/sys/bin/loki.sh," "E:Error executing updater binary in zip '/sdcar", and "Error flashing zip '/sdcard/cm-10.2.0-d800.zip.'" Now, whenever I turn my phone on, it displays the LG logo with "Security Error" written underneath it. I tried doing a factory reset in TWRP, but that didn't fix the problem.
Here's loki.sh:
Code:
#!/sbin/sh
#
# This leverages the loki_patch utility created by djrbliss which allows us
# to bypass the bootloader checks on jfltevzw and jflteatt
# See here for more information on loki: https://github.com/djrbliss/loki
#
export C=/tmp/loki_tmpdir
mkdir -p $C
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=$C/aboot.img
/system/bin/loki_patch boot $C/aboot.img /tmp/boot.img $C/boot.lok || exit 1
/system/bin/loki_flash boot $C/boot.lok || exit 1
rm -rf $C
exit 0
Edit:
I ended up using this guide with the AT&T files mentioned in this guide to revert my G2 to its original state. However, I still have no idea why Cyanogenmod failed to install.
Click to expand...
Click to collapse
Did you use flashtool 1.8 or 1.5? I'll try this out today. thanks.

Bjangles said:
I've searched for a good three hours now and can't find a solution. Here's my problem, I got root, I got TWRP, I tried to install cyanogenmod, when it's installing it just stops and says FAILED in big red letters. The small letters say error executing update binary in "cyanogenmod.zip" I tried rebooting into android it just goes back to twrp. ive tried reflashing the .zip, same error. I've tried every flash to stock method I could find and those get stuck on the attached picture's step. I'm really close to giving up and am very frustrated. please help thanks. Oh and i have the att version.
Click to expand...
Click to collapse
I just had the same problem, on the T-Mo. I was able to restore from the back up I had just created. I saw today the cm had an m release of cm11. Tried installing and it failed. Tried rebooting went right back into recovery. Scared the crap out of me. But I'm back up and running. A little sad that it didn't work I miss cm. Is it possible that my Loki I flashed not 30 minutes ago didn't work?

chasingeuphoria said:
I just had the same problem, on the T-Mo. I was able to restore from the back up I had just created. I saw today the cm had an m release of cm11. Tried installing and it failed. Tried rebooting went right back into recovery. Scared the crap out of me. But I'm back up and running. A little sad that it didn't work I miss cm. Is it possible that my Loki I flashed not 30 minutes ago didn't work?
Click to expand...
Click to collapse
I think it was just a bad download. Unfortunately, I wasn't smart enough to make a backup before I tried to install CM. I tried the other guys fix and it worked for me.

I can't find anything, anywhere else about this. I would like to find more information before I do it again. Not sure if I could handle that again. I've never had this happen before.
Sent from my LG-D801 using XDA Premium 4 mobile app

Bjangles said:
I think it was just a bad download. Unfortunately, I wasn't smart enough to make a backup before I tried to install CM. I tried the other guys fix and it worked for me.
Click to expand...
Click to collapse
I don't think it was a bad download. I think it has something to do with the recovery. But I've searched and searched can't find anything. Don't want to ask here because if it has been asked here before it would cause an uproar. Lol. Anyway prolly going to give up. I do miss CyanogenMod. But I'm obviously not smart enough

I posted in a Q&A thread last week about the same issue. Once you take an update (10o for at&t) your boot.img is changed and won't be recognized when trying to flash. If you revert back to stock, you should be able to regain root, install recovery and flash.
Edit: found the thread. datechnerd even posted some modified roms for 10o. I think he did same for other variants.
http://forum.xda-developers.com/showthread.php?t=2589381
Sent from my LG-D800 using xda app-developers app

[GUIDE] [SOLVED] HOW TO FLASH CM11 ON BRAVO (Previously "Cm11 Issue, Status 0 Error")

[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

[SOLVED!] Unable to flash MIUI - Status 7

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.