Cant install custom Room's - Nexus S General

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

Related

[Q] Installation of CyanogenMod 7.2.0-RC1 aborts with (Status 7)

Hi all,
I am having difficulty installing CM 7.2.0-RC1 on my Droid 2. I have been using the official CyanogenMod wiki guide at
wiki.cyanogenmod. com/wiki/Motorola_Droid_2:_Full_Update_Guide
-phone was originally v2.3.3
-as per guide, downgraded to 2.3.2
-verified phone ok running android version 2.2
-successfully rooted with rageagainstthecage
-installed Droid 2 recovery bootstrap & ClockwordMod recovery
-verifed ClockworkMod recovery working - booted into CWM recovery and created backup
Then I tried to apply the CM7.2.0-RC1 zip update:
-put the .zips (CM7.2.0... and gapps) on my sdcard
-bootstrapped into clockworkmod via droid 2 bootstrapper
-apply update from .zip > choose zip on sdcard > chose update-cm-7.2.0-RC1-droid2-signed.zip
everything seems to go fine, then it pops the status 7 error:
Checking kernel version...
If install aborts here
make sure you are on
the OTA and not the
original GB leak!
assert failed: run_program("/tmp/check_kernel") == 0
E:Error in /sdcard/update-cm-7.2.0-RC1-droid2-signed.zip
(Status 7)
Installation aborted.
The part of the error message where it says "make sure you are on the OTA and not the original GB leak" has me confused... I was on the OTA as far as I knew, but then the wiki guide had me downgrade to 2.3.2. I assume that downgrade is a stock OTA update - am I right?
I've done quite a bit of searching, but can't figure out where I've gone wrong. Is there something else I've missed?
So are you on 2.2 or 2.3.3?
Where did you get your release candidate .zip? I would like to check the integrity of the file.
Sent from my DROID2 using xda premium
I keep banging my head against the exact same set of circumstances. I downloaded all of my files directly from the cyanogen wiki. I rooted my device first with SuperOneClick. Assuming that this might be the problem, I then SBFed it back to stock, and rerooted it verbatim per the instructions on the wiki and the cyano build... and continue to get the same results.
It took a bit of digging around in the CyanogenMod forums, but you have to be on the latest .sbf (2.3.3?). CyanogenMod 7.2 is based on the Gingerbread kernel and won't work over the top of a Froyo installation. Though I hear that you can't just flash nightlies (or any update, for that matter) over the top of it. You'll have to .sbf either way. This really sucks for me because I've got to re-flash my phone back to cricKet wireless (an hour process; manual flashing sucks) every time I .sbf as it sets everything back to the VZW defaults.
Sent from my DROID2 using xda premium

[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.

miui not flashing in n4

hello i have nexus 4 and i rooted it today to install miui......i had unlocked bootloader and flashed cwm touch 6.0.4.6 bt when i flash .zip then it provide error saying status 7 format() expect 5 arg, got 4.
i had deleted assert lines in update script bt then also it fails.
plz help....:crying:
Ankurcul said:
hello i have nexus 4 and i rooted it today to install miui......i had unlocked bootloader and flashed cwm touch 6.0.4.6 bt when i flash .zip then it provide error saying status 7 format() expect 5 arg, got 4.
i had deleted assert lines in update script bt then also it fails.
plz help....:crying:
Click to expand...
Click to collapse
I'd flash back to stock and start over.
Here's a XDA link on fixing Status 7 errors
Just make sure you have the correct ROM downloaded for your phone or you could end up with an expensive paper weight

[Q] Need Help in installing Jelly Bean on Defy+

I want to install Jelly Bean on Motorola Defy+...
I had earlier installed it with this zip cm-10.2-20130917-NIGHTLY-mb526...
But since I tried to install kit kat on it which I m not able to....
So, I began from start
1. installed DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF.sbf than,
2. installed firmwaresbf to root it. Rooted Saw Superuser In Menu. Than,
3.insatlled CyanogenDefy Recovery v5.0.3.1-jordan recovery. than
4.Try to install cm-10.2-20130917-NIGHTLY-mb526. by going in custom recovery But now I got this Error
Installing Update...
E:Error in/sdcard/cm-10.2-20130917-NIGHTLY-mb526.zip
(Status 0)
Installation aborted.
5. Also want to install Team win recovery Project....
One More thing this is a same Zip from which I installed Jelly Bean on Defy+.... I haven't deleted it... so it Can't be corrupted I think so...
Please HELP.
Provide me your valuable assistance...
Tooooo many tutorials was posted on this subject. Is enough.
In the forum rules is stipulated that first search and if you NOT found anything then ask!
can u post a link of the forum that can explain.....
pgreed said:
Tooooo many tutorials was posted on this subject. Is enough.
In the forum rules is stipulated that first search and if you NOT found anything then ask!
Click to expand...
Click to collapse
can u post a link of the forum that can explain.....that will be very helpful
&
Thanks for Answering...
Pls Help....
it would've took you less time answering him than complaining.
Mate, I've had this very problem.
You need to flash an earlier version of cm. try cm10 or 10.1.
it doesnt work because you have an outdated recovery. flashing cm10 solves this.
Good luck!
edit: after you flash cm10 make sure to get the 20 oct version of cm10.2 as the 17 sept you tried to flash is not the latest
defynoob said:
it would've took you less time answering him than complaining.
Mate, I've had this very problem.
You need to flash an earlier version of cm. try cm10 or 10.1.
it doesnt work because you have an outdated recovery. flashing cm10 solves this.
Good luck!
edit: after you flash cm10 make sure to get the 20 oct version of cm10.2 as the 17 sept you tried to flash is not the latest
Click to expand...
Click to collapse
Not necessary. If you has follow my explanation (from other post) you've found that is another simplified method.
still Help Needed
pgreed said:
Not necessary. If you has follow my explanation (from other post) you've found that is another simplified method.
Click to expand...
Click to collapse
Try to install this with recovery but still getting same error cm-11-20131229-NIGHTLY-mb526.zip
E:Error in/sdcard/cm-10.2-20130917-NIGHTLY-mb526.zip
(Status 0)
Installation aborted.
Pls Help Me
no one there to HELP!
What happen is there no one who can provide any HELP to me...
As I want it much...
Pls Help Me...
thanks in advance..
I have the same problem now with my new Defy+.I had 2 Defys+ in past and just root and install 2init then instal .zip CM9 or CM10 and love it.Now I go to kill myself.From more than week I flash,install,reboot,reflash....and have no fully working Cm10.First I have no way to install newer than cm10.0!Any try with 10.1 or 10.2 is folow ERROR in the beginning and nothing more.My custom recovery now is CWM.Any try to update recovery or try with TWRP,or try dual recovery or,or...is going to boot loop or sot brick...Now Im on CM10/Android 4.1.2 and try to get telephony functions.Im in Bulgaria and before with previous Defys I use baseband switch to 342-145.Now just after install new ROM(CM10) telephony worked first couple of minutes,not more.After dialing it come to black screen or in normal incall screen but no voice from bot sides.I switch to other bands but nothing.It come to pissed me out.Please help
I go directly to CM11, it is much stable now.
Not able to install TWRP
Not able to install TWRP Tried by installing it from CyanogenDefy Recovery v5.0.3.1-jordan recovery and it says installed successfully from SD card but not able to boot in team win recovery project and therefore not able to install any CM version Yet
trying n getting nstalling Update...
E:Error in/sdcard/cm-10.2-20130917-NIGHTLY-mb526.zip or any other cm version
(Status 0)
Installation aborted.
Need help pls help me...:crying:

[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

Categories

Resources