What is the difference between CM10 Preview and Nightly?
// Sorry for dumb question. In case someone wouldn't know: Preview was unofficial build and currently the only one meant to be used is Nightly.
vibrant nightlys nto working on vibrant device
I have 2 samsung galaxy S i9000 vibrant's. None of the vibrant nightlys work on my device. I get an error message that the file is
getprop("ro.product.device") == "vibrant" || getprop("ro.product.device") == "vibrant" || getprop("ro.product.device") == "vibrantmtd" || getprop("ro.product.device") == "vibrantmtd" || getprop("ro.product.device") == "SGH-T959" || getprop("ro.product.device") == "SGH-T959" ||
E:error in /external_sd/cm-10.0.0-vibrantmtd.zip(status 7)
This is the last stable version however i have tried the last 3 nightlys (27,28,29 dec) same thing
The galaxymtd works but the reception is sh*t
I dont care to get the vibrant version working, but is there a modem that i can flash that is the equilivant of the JL2 modem (i have jsut the modem file and have flashed with odin but then it wont connect al all)
cm rules but if i can connect it defeats the purpose
ITRADSK
2x Samsung galaxy S vibrant
1X cm9 + darkys 11.0 - daily runner
1X Dev phone--currently CM10 weak modem
itradsk said:
I have 2 samsung galaxy S i9000 vibrant's. None of the vibrant nightlys work on my device. I get an error message that the file is
getprop("ro.product.device") == "vibrant" || getprop("ro.product.device") == "vibrant" || getprop("ro.product.device") == "vibrantmtd" || getprop("ro.product.device") == "vibrantmtd" || getprop("ro.product.device") == "SGH-T959" || getprop("ro.product.device") == "SGH-T959" ||
E:error in /external_sd/cm-10.0.0-vibrantmtd.zip(status 7)
This is the last stable version however i have tried the last 3 nightlys (27,28,29 dec) same thing
The galaxymtd works but the reception is sh*t
I dont care to get the vibrant version working, but is there a modem that i can flash that is the equilivant of the JL2 modem (i have jsut the modem file and have flashed with odin but then it wont connect al all)
cm rules but if i can connect it defeats the purpose
ITRADSK
2x Samsung galaxy S vibrant
1X cm9 + darkys 11.0 - daily runner
1X Dev phone--currently CM10 weak modem
Click to expand...
Click to collapse
Toggle script assertions off.
Edit
And I still got love for the streets..
Related
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 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
I tried to flash JellyBam and a MIUI ROM, but both failed with status 7.
I saved a log from Aroma installer after trying to flash the MIUI ROM:
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : M1UI
ROM Version : 2.10.26.v2
ROM Author : a1exander
Device : Samsung Galaxy S2
Start at : Sun Dec 23 16:11:05 2012
script aborted: 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") == "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") == "i9100" || getprop("ro.build.product") == "i9100" ||
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"
Installer Error (Status 7)
End at : Sun Dec 23 16:11:05 2012
EDIT: Did some more digging and found that the ROMs that failed to flash had an assert command in the beginning of the script,
while the ROMs that worked didn't have an assert command. Is it safe to disable assert command from recovery or remove it from the script?
Or what should I do to flash these ROMs?
Flash a dorimanx kernel http://forum.xda-developers.com/showthread.php?t=1617219 (don't boot) then reboot recovery (in advanced), wipe data (backup with titanium) then flash rom, wipe cache and devlik cache and then reboot
Thanks, that worked.
P990 - same issue
Will this solution work for the Optimus 2x as well?
Thanks.
ilovefls said:
Will this solution work for the Optimus 2x as well?
Thanks.
Click to expand...
Click to collapse
A kernel for the i9100 has ZERO chance of working on an Optimus 2x.
ctomgee said:
A kernel for the i9100 has ZERO chance of working on an Optimus 2x.
Click to expand...
Click to collapse
Then what solution do you recommend for the same issue encountered on the P990?
ilovefls said:
Then what solution do you recommend for the same issue encountered on the P990?
Click to expand...
Click to collapse
Maybe a solution found in the forum for that device?
This thread is in the forum for the GT-i9100 Galaxy S II. Chances of you finding a solution for whatever problem you're having on your Optimus 2x in this forum are pretty small.
ctomgee said:
Maybe a solution found in the forum for that device?
This thread is in the forum for the GT-i9100 Galaxy S II. Chances of you finding a solution for whatever problem you're having on your Optimus 2x in this forum are pretty small.
Click to expand...
Click to collapse
OMG! Can someone at least try to give an answer that is useful?
The reason I posted it here was because it is the exact same problem I have that has been described here. I am fully aware this is an S II thread, thanks for pointing that out!
The error shared is because the update script is c comparing the value of the device identity with a pre-set value in the update (Galaxys2 & Gt-I9100) another solution would to be open the update file hash the lines for the assert and continue to flag bit that would mean disabling a security feature that was put there to prevent faulty flashs.
And yes you re far from where you need to be and I'm no expert in Optimus.
Sent from my GT-I9300 using xda app-developers app
ilovefls said:
OMG! Can someone at least try to give an answer that is useful?
The reason I posted it here was because it is the exact same problem I have that has been described here. I am fully aware this is an S II thread, thanks for pointing that out!
Click to expand...
Click to collapse
Seeing as how I am an i9100 user, and know nothing about the Optimus 2x, my suggestion for you to go to the Optimus 2x forum to ask other Optimus 2x users is perfectly useful.
Just because you got the same error doesn't mean the solution is the same.
And it didn't seem like you knew where you were, because you asked if flashing an i9100 kernel would fix your problem on your Optimus 2x. Kernels for specific devices do not typically work on other devices. Especially if there are major hardware differences. There is a piece of useful information you apparently did not know.
@ilovefls - More to the point, if you flash something meant for the I9100 on whatever the hell phone you have (didn't notice/don't particularly care), there's a fair chance you'll brick it.
So....You can either take the well intentioned advice (and it was well intentioned; nobody told you to get nicked like I am now) you were given & ask in the forum specific to your device, or you can break your phone. No skin off our nads either way.
Actually, the latter would be pretty funny given how dopey you obviously are. I figure it would be just deserts.
So....You can either take the well intentioned advice (and it was well intentioned; nobody told you to get nicked like I am now) you were given & ask in the forum specific to your device, or you can break your phone. No skin off our nads either way.
Actually, the latter would be pretty funny given how dopey you obviously are. I figure it would be just deserts.
OWNED
Sorry very childish of me ..
1Chef said:
Flash a dorimanx kernel http://forum.xda-developers.com/showthread.php?t=1617219 (don't boot) then reboot recovery (in advanced), wipe data (backup with titanium) then flash rom, wipe cache and devlik cache and then reboot
Click to expand...
Click to collapse
Worked for me, thanks for this information now my phone is back up and running.
1Chef said:
Flash a dorimanx kernel http://forum.xda-developers.com/showthread.php?t=1617219 (don't boot) then reboot recovery (in advanced), wipe data (backup with titanium) then flash rom, wipe cache and devlik cache and then reboot
Click to expand...
Click to collapse
thanks...finally on JellyBAM......
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