Hey guys, I need your advice.
When im in recovery mode and trying to install the latest release for my galaxy s I9000
im receiving this error : "
assert failed: getprop("ro.product.decive")=="galaxys" || getprop("ro.build.product") == "galaxys" ||...
...
...
E:Error in /sdcard/aokp_galaxysmtd_build-28.zip (status 7)
Installation aborted"
how do i solve this?
thanks ahead.
Try to download from other mirror. May they uploaded wrong zip
Sent from my GT-I9000 using XDA
crusader777 said:
Hey guys, I need your advice.
When im in recovery mode and trying to install the latest release for my galaxy s I9000
im receiving this error : "
assert failed: getprop("ro.product.decive")=="galaxys" || getprop("ro.build.product") == "galaxys" ||...
...
...
E:Error in /sdcard/aokp_galaxysmtd_build-28.zip (status 7)
Installation aborted"
how do i solve this?
thanks ahead.
Click to expand...
Click to collapse
I disabled the assert test at recovery menu (CWM ver 5.x.x) and was able to install, but I encountered this problem when I was flashing Slim ICS 2.9. I think may be this zip is not "signed".
I was on ics miui from iHoneyBadget. Then i went to recovery and wiped everything to flash Galaxy Note (based on MIUI-2.3.18 & CM9 nightly 18May12).
But then i got fail.
assert failed: getpro("ro.product.device") == "galaxynote" || getprop ("ro.build.produckt") == galaxynote" || getprop ("ro.product.device") == "GT-N7000)
E:error in /emmc/download/miui-2.3.18 (status 7)
Can anyone help me here? im i softbricked or hardbricked? I can go to recovery.
Thread closed
No need for duplicate threads, continue your diswcussion here.
Hi all!
(sorry for my bad english)
I have a small problem: my device is the S6500 (with nfc), first I play with the CM-10 and after with the CM-10.1, all with success flash and run.
Now I have been flashed the CM-10 and I see that in the second boot screen (with Samsung logo and model name) I see S6500D (the NON nfc version) and not the correct model name S6500.
In the Download mode the CWM (I tried in the v5 and v6) I see the correct model: PRODUCT: GT-6500 - VERSION: S6500XXLK2.
But if I do a flash (using CM-10 or CM-10.1) with CWM v6 occurs an assert error:
----
Installation update...
assert failed: getprop("ro.product.device") == "jena" || getprop("ro.build.product") == "jena" || getprop("ro.build.product") == "GT-6500"
E:Error in /sdcard/cm-10-20130506-UNOFFICIAL-jena.zip
(Status 7)
Installation aborted.
----
PS: With CWM v5 this error not occurs, and flash's runs
This error is related with the "S6500D" that I see in the boot screen? Anyone know how to fix this issue?
Thanks!
About CWM ... 5.0.2.8 Here Should Work fine with you
About Logo i think it's just from ROM nothing wrong ... It's Recovery Logo So do not panic
Hi guys, please take a minute to help a fellow Sony fan out...
I managed to unlock bootloader via flashtool, root and install recovery as on istux's guide http://forum.xda-developers.com/showthread.php?t=2798411
But when I try to flash DirtyUnicorns_Unofficial_Tsubabsa_build2, it tells me..."This package is for LT25i Tsubasa devices; this is a mint."!
I don't know if this is related at all, but when I try to wipe the cache, it says "failed to unmount /cache"
Why does it think it is a "mint" (whatever that is) and how do I fix this?
From being stuck in recovery after wiping data, the only thing I can do is flash stock 4.3 FTF (9.2.A.2.5) again using flashtool. Is there a better way out of this?
swe.rider said:
Hi guys, please take a minute to help a fellow Sony fan out...
I managed to unlock bootloader via flashtool, root and install recovery as on istux's guide http://forum.xda-developers.com/showthread.php?t=2798411
But when I try to flash DirtyUnicorns_Unofficial_Tsubabsa_build2, it tells me..."This package is for LT25i Tsubasa devices; this is a mint."!
I don't know if this is related at all, but when I try to wipe the cache, it says "failed to unmount /cache"
Why does it think it is a "mint" (whatever that is) and how do I fix this?
From being stuck in recovery after wiping data, the only thing I can do is flash stock 4.3 FTF (9.2.A.2.5) again using flashtool. Is there a better way out of this?
Click to expand...
Click to collapse
If you're completely sure you're installing the correct ROM for your phone, then you need to use 7zip to open the ROM zip file (Open Archive) and navigate to "\META-INF\com\google\android\" and extract the "updater-script" file. Edit it with Notepad++ (or use Linux, do not use Windows notepad) and delete the first command:
Code:
assert(getprop("ro.product.device") == "lt29i" || getprop("ro.build.product") == "lt29i" ||
getprop("ro.product.device") == "hayabusa" || getprop("ro.build.product") == "hayabusa" ||
getprop("ro.product.device") == "LT29i" || getprop("ro.build.product") == "LT29i" || abort("This package is for \"lt29i,hayabusa,LT29i\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
The example above is from a ROM for a TX. Yours should similar.
The first line of the script should start with:
Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/System", "/system");
Save the file and re-add it to the ROM zip file, replacing the previous updater-script, then you can connect your phone to your PC and use ADB to push the file back to the sdcard on the phone.
Also, if you only wiped /data, then you could just reboot, wait for Android to start up and copy the file normally. Then reboot back to recovery and reflash. On the other hand, if you wiped /system, ADB is your only option, unless you want to reflash a stock FTF.
I'm pretty sure this is because the command checks the phones build.prop to see if the device/product matches certain strings that identify your device, but apparently they don't always match.
Antiga Prime said:
If you're completely sure you're installing the correct ROM for your phone, then you need to use 7zip to open the ROM zip file (Open Archive) and navigate to "\META-INF\com\google\android\" and extract the "updater-script" file. Edit it with Notepad++ (or use Linux, do not use Windows notepad) and delete the first command:
Code:
assert(getprop("ro.product.device") == "lt29i" || getprop("ro.build.product") == "lt29i" ||
getprop("ro.product.device") == "hayabusa" || getprop("ro.build.product") == "hayabusa" ||
getprop("ro.product.device") == "LT29i" || getprop("ro.build.product") == "LT29i" || abort("This package is for \"lt29i,hayabusa,LT29i\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
The example above is from a ROM for a TX. Yours should similar.
The first line of the script should start with:
Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/System", "/system");
Save the file and re-add it to the ROM zip file, replacing the previous updater-script, then you can connect your phone to your PC and use ADB to push the file back to the sdcard on the phone.
Also, if you only wiped /data, then you could just reboot, wait for Android to start up and copy the file normally. Then reboot back to recovery and reflash. On the other hand, if you wiped /system, ADB is your only option, unless you want to reflash a stock FTF.
I'm pretty sure this is because the command checks the phones build.prop to see if the device/product matches certain strings that identify your device, but apparently they don't always match.
Click to expand...
Click to collapse
Antiga, thank you very much, I actually succeeded by following your advice from post #10 here http://forum.xda-developers.com/showthread.php?t=2581336
I wiped everything but just restored a nandroid backup I made in recovery before wiping and that worked when i needed to copy different files after things went wrong with the flash.
Would there be any problem caused by not being able to unmount /cache during wiping?
swe.rider said:
Antiga, thank you very much, I actually succeeded by following your advice from post #10 here http://forum.xda-developers.com/showthread.php?t=2581336
I wiped everything but just restored a nandroid backup I made in recovery before wiping and that worked when i needed to copy different files after things went wrong with the flash.
Would there be any problem caused by not being able to unmount /cache during wiping?
Click to expand...
Click to collapse
You're welcome. It's happened to me before, never known why, but after flashing a different ROM you can always try wiping /cache again; it generally works.
I have h870, i unlocked its bootloader, installed twrp, then rooted it. I then tried to flash the pixel experience rom through twrp recovery, however its fails and gives error: this rom is for h870 lucye. Now the phone has no os and is stuck on lg g6 logo.
How can i fix this?
Reboot in recovery mode and try flashing another ROM (or if you have a backup of the previous one, try restoring backup)
5warafat1 said:
I have h870, i unlocked its bootloader, installed twrp, then rooted it. I then tried to flash the pixel experience rom through twrp recovery, however its fails and gives error: this rom is for h870 lucye. Now the phone has no os and is stuck on lg g6 logo.
How can i fix this?
Click to expand...
Click to collapse
don't use the official twrp, use orangefox recovery
To avoid the error, go into
(ROM ZIP)/META-INF/com/google/android/updater-script
and delete these lines
Code:
assert(getprop("ro.product.device") == "g6" || getprop("ro.build.product") == "g6" ||
getprop("ro.product.device") == "lucye" || getprop("ro.build.product") == "lucye" ||
getprop("ro.product.device") == "h870" || getprop("ro.build.product") == "h870" ||
abort("E3004: This package is for device: g6,lucye,h870; this device is " + getprop("ro.product.device") + "."););
or if you don't want to delete too much, just delete the "abort" line.
Hope this helps
Use orange recovery project and try flashing another ROM like havocOS.