Hello guys,
I've perused your forums off the back of some Google searches trying to find some answers to my problem, to no avail. So I shall recap my situation and see what the brains have to offer.
A few days ago I got a Samsung Galaxy SII i900P upgrade through Orange. I noticed straight away my model was slightly different with it's NFC, but didn't realise until attempting to install CM7 how much of a headache it'd be to put a custom Android overlay onto.
I followed the Cyanogen Mod wiki entry, changed to an insecure kernel (got my yellow triangle), rooted using S2Root (after a Google search), and attempted to install Cyanogen. Failed. Followed one guys suggestion of changing the 'assert()' command at the top of META-INF/com/google/android/updater-script to:
assert(getprop("ro.product.device") == "galaxys2" || getprop("ro.build.product") == "galaxys2" || getprop("ro.product.board") == "galaxys2" ||
getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100" || getprop("ro.product.board") == "GT-I9100" ||
getprop("ro.product.device") == "GT-I9100M" || getprop("ro.build.product") == "GT-I9100M" || getprop("ro.product.board") == "GT-I9100M" ||
getprop("ro.product.device") == "GT-I9100T" || getprop("ro.build.product") == "GT-I9100T" || getprop("ro.product.board") == "GT-I9100T" ||
getprop("ro.product.device") == "GT-I9100P");
Click to expand...
Click to collapse
But to no avail. I tried a few more times and for about an hour I ended up with a dead handset that had ClockworkMod, until I put on a different kernel. Now I have a slightly different looking overlay which is STILL Orange branded.
Can anyone help me A) remove the branding and B) get a more attractive android version? Heck, stock Android would be preferable! And I could live without the NFC.
Cheers in advance,
Stoobie_Land
Follow the instructions in the DEBRAND thread or just simply flash a stock rom from the stock rom thread to debrand .
jje
Related
I cannot boot into my rom but I can boot into CWM however when i try to flash a rom i get this read out:
assert failed: getprop("ro.product.device") == "x10i" || getprop("ro.build.product") == "x10i" || getprop("ro.product.board") == "x10i" || getprop("ro.product.device") == "x10a" || getprop("ro.build.product") == "x10a" || getprop("ro.product.board") == "x10a" || getprop("ro.product.device") == "es209ra" || getprop("ro.build.product") == "es209ra" || getprop("ro.product.board") == "es209ra"
E:Error in /sdcard/update-cm-7.1.0-xperia-x10i-KANG-signed.zip
(status 7)
Installation aborted
What have I done wrong?
flash the stock rom - format sdcard on the phone (dont forget backup), and then once more again.
Quercus1 said:
flash the stock rom - format sdcard on the phone (dont forget backup), and then once more again.
Click to expand...
Click to collapse
Ta for the help do i flash stock ROM using flashtool then if CWM is bust?
yes - make your phone "virgin"
sorted almost worried for a sec there, nice to know the XDA communities always there for a noob
Hi,
I just tried to install this rom on my i9100p (the one with NFC) but failed the initial test... looks like it can be installed only on plain 9100, 9100M and T but not P... why is that? i've read that apart from the NFC it's just the same (in fact i had no problem installing CWM and after that when the phone boots it says i9100)...
i tried to search for the piece of code that it show on the screen as an error, but unfortunately I couldn't find where it is... the error is:
assert failed: getprop("ro.product.device") == "galaxys2" || getprop("ro.build.product") == "galaxys2" || getprop("ro.product.device") == "i9100" || getprop("ro.build.product") == "i9100" || getprop("ro.product.device") == "i9100M" || getprop("ro.build.product") == "i9100M" || getprop("ro.product.device") == "i9100T" || getprop("ro.build.product") == "i9100T"
so it should be matter of adding a couple ORs and voila... or maybe is there a way to change my model name somewhere?
Mmm some info. here, maybe help http://forum.xda-developers.com/showthread.php?t=1465816
GaboWinter said:
Mmm some info. here, maybe help http://forum.xda-developers.com/showthread.php?t=1465816
Click to expand...
Click to collapse
wel thank you, it did help, cause i understood that i had to modify the updater-script!
but now i get another error it just says error in .zip and (status 6), before it was status 7...
but i'm not really sure if i'm doing it correctly... when i'm in recovery mode, i go to install zip from sdcard->choose zip from sdcard and then i choose update-cm-9...zip
instructions only say "flash cm9"...
i have rooted the phone with CWS and nothing else...
Hello all.
I recently saw a post about cm 10.1 for xperia p and i rushed to download and install it. I am using xperia p stock jb rom with unlocked bootloader , rooted with CMW and when i tried to flash it from CWM the instalation was aborted.(status 7) can someone help me please? i really want the android 4.2.2 thanks.
Just delete in zip archive in file \META-INF\com\google\android updater-script first 3 lines and flash archive!
Thanks for your interest but i already did, installation aborted status 0.
assert(getprop("ro.product.device") == "C5502" || getprop("ro.build.product") == "C5502" ||
getprop("ro.product.device") == "C5503" || getprop("ro.build.product") == "C5503" ||
getprop("ro.product.device") == "C5506" || getprop("ro.build.product") == "C5506" ||
getprop("ro.product.device") == "dogo" || getprop("ro.build.product") == "dogo");
but there are 4 lines not 3.
Download the zip again, or flash CM10.1 kernel, then install the rom.
kostasroussis66 said:
Thanks for your interest but i already did, installation aborted status 0.
assert(getprop("ro.product.device") == "C5502" || getprop("ro.build.product") == "C5502" ||
getprop("ro.product.device") == "C5503" || getprop("ro.build.product") == "C5503" ||
getprop("ro.product.device") == "C5506" || getprop("ro.build.product") == "C5506" ||
getprop("ro.product.device") == "dogo" || getprop("ro.build.product") == "dogo");
but there are 4 lines not 3.
Click to expand...
Click to collapse
This is archive not for Xperia P!
For Xperia P need LT22i!
And wrong forum!
For Xperia P only tihs: http://forum.xda-developers.com/showthread.php?t=2341139
@dimon it was the 1st file i used and appeared a problem. I will try again and i will try removing the 3 lines.
@razorka link for cm 10.1 kernel pls?
The kernel is in the zip:
boot.img
thanks guys i just deleted the 3 lines from updeter script and now it is installed! Ty all
An another question: Is it good and stable for everyday use? And when can i insert my PIN code? :S ty
Yes, it's able for daily use, very stable and smooth!
A definite noob in the Android world , I have rooted my phone using the package ZSMSA Android 4.1.2 root package from the instructions found here from android.gs ; and then proceeded to install CyagenoMod 10.1.2 rom . After rebooting I get errors which is similar to this :
assert failed: getprop("ro.product.device") == "galaxys2" || getprop("ro.build.product") == "galaxys2" ||
getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100" ||
getprop("ro.product.device") == "GT-I9100M" || getprop("ro.build.product") == "GT-I9100M" ||
getprop("ro.product.device") == "GT-I9100P" || getprop("ro.build.product") == "GT-I9100P" ||
getprop("ro.product.device") == "GT-I9100T" || getprop("ro.build.product") == "GT-I9100T"
assert failed: getprop("ro.product.device") == "galaxys2" || getprop("ro.build.product") == "galaxys2" ||
getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100" ||
getprop("ro.product.device") == "GT-I9100M" || getprop("ro.build.product") == "GT-I9100M" ||
getprop("ro.product.device") == "GT-I9100P" || getprop("ro.build.product") == "GT-I9100P" ||
getprop("ro.product.device") == "GT-I9100T" || getprop("ro.build.product") == "GT-I9100T"
My phone is GT i9100 . Is there anything be done to fix this . I am running Jelly Bean 4.1.2 .
I had the same error when first installing CyanogenMod 10.1 on my phone. First, make sure you have the correct version of CyanogenMod for your device (make sure it is for the GT-I9100, and not the GT-I9100T or other variants) and move the files to your computer.
Extract the .zip file.
Once unzipped, browse to the META-INF/com/google/android directory.
You will find two files called “update-binary” and “updater-script”.
Rename “updater-script” to “updater-script.txt” and open with a text file editor.
Delete the line starting with “assert” to first semi-colon, including the semi-colon. Usually this is the first line or one of the first lines at the top of the text file.
Save the file and rename it back to "updater-script".
Re-zip the new, edited files and copy to your phone (make sure you copy the edited file, not the original by accident).
Install the new, edited .zip in recovery and all should be fine
Also, try using different versions of CWM if this doesn't work first time. You can use the "ROM Manager" app to install different versions of CWM, try older or newer versions if installing CyanogenMod does not work with the edited .zip file.
Sent from my GT-I9100 using xda app-developers app
But there is a more simple solution. Lucky for you, the CyanogenMod Installer Beta has recently gone up, and the GT-I9100 is a supported device follow this link
https://plus.google.com/communities/103540722025986617902
and join the community, using the Installer should avoid errors like the one you are experiencing.
Sent from my GT-I9100 using XDA Premium 4 mobile app
Afternoon all,
I have an aging ex-Orange Galaxy S2, now running Omnirom nightlies and still going strong. However, I've been experiencing really choppy audio quality on two different brands of in-car bluetooth handsfree for almost a year now, so I got looking at baseband versions.
Currently on XXMS2, I tried to update to XXMS3 and XXMS4, but it always failed on getprop assert fails. I've narrowed it down to this.
The phone is reporting...
Code:
~ # getprop | grep ro.product.device
[ro.product.device]: [i9100]
~ # getprop | grep ro.build.product
[ro.build.product]: [i9100]
~ # getprop | grep ro.product.board
[ro.product.board]: [smdk4210]
And the XXMS3 and XXMS4 flashing scripts are checking for...
Code:
assert(getprop("ro.product.device") == "galaxys2" || getprop("ro.build.product") == "galaxys2" || getprop("ro.product.board") == "galaxys2" ||
getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100" || getprop("ro.product.board") == "GT-I9100" ||
getprop("ro.product.device") == "GT-I9100M" || getprop("ro.build.product") == "GT-I9100M" || getprop("ro.product.board") == "GT-I9100M" ||
getprop("ro.product.device") == "GT-I9100T" || getprop("ro.build.product") == "GT-I9100T" || getprop("ro.product.board") == "GT-I9100T" ||
getprop("ro.product.device") == "GT-I9100P" || getprop("ro.build.product") == "GT-I9100P" || getprop("ro.product.board") == "GT-I9100P");
Clearly nothing in that list will match. I have an XXMS2 firmware file, and it doesn't perform these checks. I don't know why my phone would have a slightly out of the ordinary set of properties, other than the fact it's had a few warranty repairs by Samsung.
Thus, is it safe to edit updater-script and remove those checks in order to let it pass the test?
Any advice or scary warnings would be greatly appreciated!
Cheers
Kyle
Changing modem isn't going to fix your BT problems, BT drivers are in the kernel (with WiFi drivers).
That's a bit disappointing to hear then The problem has been apparent since the CM10 days, and persisted into Omnirom. Only affects HFP too. A2DP is fine. Will keep wishing then.
Does it happen with stock ? If it doesn't, might be worth mentioning to the developer of the custom rom(s) you're using/have tried.
Could easily be an AOSP specific issue; due to a lot of proprietary code, lots of things only work on their roms due to the skill of the coders involved - being able to 'hack' solutions/reverse engineer stuff. And that proprietary code is also the reason why some stuff doesn't work/has problems with AOSP.