Yesterday I wanted to re-flash my ROM (did that about 4 times before without complication) because of a random wifi bug. All things did quite fine , i wiped data/system/cache/dalvik-chache/sd-ext but after i said install .zip from sd, there was the error - lavine.
Log:
-- Installing: /sdcard/update.zip
Finding update package...
Openning update packge...
Installing update...
assert failed: getprop("ro.product.device") == "ST18i" || getprop("ro.build.product") == "ST18i" || getprop("ro.product.board") == "ST18i" || getprop("ro.product.device") == "ST18a" || getprop("ro.build.product") == "ST18a" || getprop("ro.product.board") == "ST18a" || getprop("ro.product.device") == "urushi" || getprop("ro.build.product") == "urushi" || getprop("ro.product.board") == "urushi"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
What am i using:
-Sony Ericcson Xperia ray (rooted)
-FreeXperia boot.img (worked the last 4 times)
-official CM7 build for ST18i (worked last 4 times)
i even reflashed the boot.img twice, but nothing changed.
I cant even access Android because i formatted the whole device + sdcard
What am i doing wrong and what can i do now?
Please help me as fast as possible (I need my goddamn phone >.<)
Greetings
~Jay
Really don't know if that helps but once I got exactly the same error. The reason was that the file system of my SD-card was corrupted somehow. Formatting the card several times via PC didn't help. There was the same error message. Finally the solution was to flash stock firmware via Flashtool and format the card from the phone menu afterwards. After that everything worked like expected. I even don't know how the file system got corrupted but the card itself seems to be OK.
Nope. it did not work. Ain't able to flash it with flashtool even after driver updates because falshtool doesn't recognize my phone. Blargh >.<
EDIT: Okay, got Flashtool working now. Have flashed original ROM, currently backing up all things and then trying to flash CM7 or MIUI again
EDIT2: Formatted, reflashing now
EDIT3: Working again! Thank you very much!!! All i need to do now is running titanum backup all over it :3
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 to all!!! After a long time spent on this forum and on google searching solutions to my problem i didn't find anything yet. I have updated my SGA with Kies to ver.2.3.6 build XWKT7 and tried to root again failing.... some videos on youtube.com assure that i can root my phone with "upd_1.zip" package used also in 2.3.3/2.3.4/2.3.5 versions, result the following code:
Code:
Opening update package....
installing update...
assert failed: getprop("ro.product.device") == "GT-S5830" || getprop("ro.build.product") == "GT-S5830" || getprop("ro.product.device") == "GT-S5570" || getprop("ro.build.product") == "GT-S5570" || getprop("ro.product.device") == "GT-S5670" || getprop("ro.build.product") == "GT-S5670" || getprop("ro.product.device") == "GT-B7510" || getprop("ro.build.product") == "GT-B7510"
E:Error in sdcard/upd_1.zip (Status 7)
Installation aborted.
Also tried with DoomLord's Zerglings exploit but failed (Hellions with BLUE flames), anyone could help me? is there the possibility to root again the device?
I have the exact same problem. Any solution yet?
root
Hey Guy`s... i have tiered an rom and flsh it via odin... soo no root probs... or take te cwm and install it.. it must bee root after install..
else
use root prog... there are many in these forum..
good luck..
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......