Develop Bugs

[Q] Unable to install CM 7.2 installed due to build.prop error...

Hi guys, need some help here.
Trying to get the CM 7.2 installed on my Verizon R800x. I updated the firmware to .89 (had to relock by bootloader to do so). I then tried to do the fastboot flash boot boot.img and got the kernel to load, but now when I try to install the update.zip from the CWM download I get the following. I unlocked my bootloader again (using the original method from ashergray like fastboot -i oem unlock 0xfce... etc) and tried again. Same result. Any ideas?
CWM-based Recovery v5.0.2.7-nAa-r2
-- Installing: /sdcard/update.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "R800x" || getprop("ro.build.product") == "R800x" || ("ro.product.board") == "R800x" || ("ro.product.device") == "zeusc" || getprop ("ro.build.product") == "zeusc" || getprop(ro.product.board") == "zeusc"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.

Found the answer in
http://forum.xda-developers.com/showpost.php?p=21721347&postcount=147
Just waiting for my Market to start downloading things so I can edit the file

[Q] CM10 Status 7 Error

I have searched forums and tried all the fixes listed.
My CWM recovery is 6.0.1.5 - the newest i can find.
I rooted and running stock Rogers (I'm a canadian rogers user)
I have downloaded multiple times (using the net and file transfer/Rommanager/and directly to my sdcard (internal and external):cm-10.0.0-d2att.zip (i would like to run the stable version rather than a nightly until i am used to it)
I always wipe data as well i have tried wiping the cache and dalvik cache as well
and still every time I try to install CM 10 on my phone, it just says:
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att"
assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att"
E:Error in /sdcard/cm-10.0.0-d2att.zip
(Status 7)
The complete and total log from when i installed using RomManager is also something i can post if needed?

CWM 6.0.1.5 is not the one you should be using. You need CWM 6.0.1.4 for the sgs3 att.

Try using twrp

check this out I had the same issue on telus
http://forum.xda-developers.com/showpost.php?p=30331732&postcount=2
hope that helps

mrhaley30705 said:
Try using twrp
Click to expand...
Click to collapse
TWRP did the trick. thanks everyone!

[Q] TWRP installation on T999 Galaxy S3 - which file?

Hello - I have just downloaded TWRP Manager and am preparing to install the custom recovery on a Canadian Wind Galaxy S3 (model number SGH-T999V). I would appreciate it if someone could confirm which file I should use for this purpose. Is it the d2can file?
Thanks,
Mvt926

You can use d2can, d2tmo or d2lte.
I recommend d2tmo if you plan on flashing any if the roms we have. Ensures better chances of successful flashing.

DocHoliday77 said:
You can use d2can, d2tmo or d2lte.
I recommend d2tmo if you plan on flashing any if the roms we have. Ensures better chances of successful flashing.
Click to expand...
Click to collapse
Thanks. I used d2tmo and it seems to have worked.
Mvt926

mvt926 said:
Thanks. I used d2tmo and it seems to have worked.
Mvt926
Click to expand...
Click to collapse
I've just completed my first system backup under TWRP and,owing to space limitations, excluded the data option. How useful is the backup with this exclusion? If I need to re do the backup with data included, is there a way to delete the first backup before completing the second?
Thanks,
Mvt926

Data includes your apps/data and settings. It should be under the TWRP folder on your sd card.

DocHoliday77 said:
Data includes your apps/data and settings. It should be under the TWRP folder on your sd card.
Click to expand...
Click to collapse
Thanks - as I have already run a titanium backup on all apps and data, would it be safe to assume that I can exclude the data option under TWRP backup?
Another thing I have found is that choosing the restore option under TWRP (to see whether the backup I have made is available for restore) causes an immediate crash (of TWRP).
Thanks,
Mvt926

That is up to you. Backing up system and boot partitions is basically just backing up the rom, just so you know. I make a clean nandroid before doing anything, and keep it on my computer. Then I generally just backup the data partition and keep the rom handy. At least I used to. I don't do it much anymore because I use titanium and it kinda seemed a little redundant to me. I still keep an initial backup on my computer though....just in case.
Everyone is different. Its boils down to what you are most comfortable having as your backup.

DocHoliday77 said:
That is up to you. Backing up system and boot partitions is basically just backing up the rom, just so you know. I make a clean nandroid before doing anything, and keep it on my computer. Then I generally just backup the data partition and keep the rom handy. At least I used to. I don't do it much anymore because I use titanium and it kinda seemed a little redundant to me. I still keep an initial backup on my computer though....just in case.
Everyone is different. Its boils down to what you are most comfortable having as your backup.
Click to expand...
Click to collapse
Thanks. I have realized that TWRP permits backups to the external SD card so will use that for a full backup, including data, and then make a duplicate on my computer for additional security.
Mvt926

I need some help please
This might not be the best place to post this but I am stuck.
I have been forced to update after my GS3 took a dump. The power control chip went bad. I have now taken over my wife's old GS3. I had not rooted and installed a custom rom in so long it took me a while to figure it out. I have rooted it. I have superuser. I installed CWM. However, I cannot get CM 10.2.1 to install. I have 4.3.1 on my device and wanted to stick with that os. I did not want to go to kit kat. I try to install through cwm and keep getting installation aborted. I uninstalled KNOX as I thought that might be the issue but I am guessing from reading this that it is a bootloader issue. I don't know how to fix/change any of that and very much need someones help. I am on a TMO SGH T999 build number JSS15J.T999UVUENC2. Kernel 3.0.31. I would very much like someone to help me figure out how to get CM 10.2.1 to install on my device. Please if you or if you know someone who can help me.
Thanks,
TIDE
[email protected]

Flash the rom again and when it fails go back and copy log to sd. The info you'll want will be towards the bottom. Let us know what it says is the reason for failure.

follow up
DocHoliday77 said:
Flash the rom again and when it fails go back and copy log to sd. The info you'll want will be towards the bottom. Let us know what it says is the reason for failure.
Click to expand...
Click to collapse
Please excuse my ignorance, how do I create the log to copy. Is that done with a specific app?
I think I figured out how to create a log. Please see my follow up post.

I think I found the log
DocHoliday77 said:
Flash the rom again and when it fails go back and copy log to sd. The info you'll want will be towards the bottom. Let us know what it says is the reason for failure.
Click to expand...
Click to collapse
I think this is what you wanted. I know I am flashing the correct version for my phone sgh t999 which from what I understand a status 7 error could mean that I was not. I was thinking it had something to do with the boot loader and knox on this version 4.3.1.
-- Installing: /sdcard/0/0/cm-10.2.1-d2tmo.zip
Finding update package...
I:Update location: /sdcard/0/0/cm-10.2.1-d2tmo.zip
I:using /data/media for /sdcard/0/0/cm-10.2.1-d2tmo.zip.
Opening update package...
Installing update...
Warning: No file_contexts
script aborted: assert failed: getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999UVUEMJC" ||
getprop("ro.bootloader") == "T999VVLDLL1" ||
getprop("ro.bootloader") == "T999LUVAMB7" ||
getprop("ro.bootloader") == "T999VVLDMF2" ||
getprop("ro.bootloader") == "T999VVLUEMK5"
assert failed: getprop("ro.bootloader") == "T999UVDLJA" || getprop("ro.bootloader") == "T999UVDLJC" || getprop("ro.bootloader") == "T999UVDMD5" || getprop("ro.bootloader") == "T999UVUEMJC" || getprop("ro.bootloader") == "T999VVLDLL1" || getprop("ro.bootloader") == "T999LUVAMB7" || getprop("ro.bootloader") == "T999VVLDMF2" || getprop("ro.bootloader") == "T999VVLUEMK5"
E:Error in /sdcard/0/0/cm-10.2.1-d2tmo.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/0/0/cm-10.2.1-d2tmo.zip")
I:using /data/media for /sdcard.

Yup. Thsts what I thought we'd see. Open the rom and find the updater script. Using Notepad++, edit it by replacing any of those builds with T999UVUENC2. If the one you choose to replace is listed more than once, replace it in all instances.
Delete the 3 signature files in the meta-inf folder, rezip and flash.

additional question
DocHoliday77 said:
Yup. Thsts what I thought we'd see. Open the rom and find the updater script. Using Notepad++, edit it by replacing any of those builds with T999UVUENC2. If the one you choose to replace is listed more than once, replace it in all instances.
Delete the 3 signature files in the meta-inf folder, rezip and flash.
Click to expand...
Click to collapse
Please excuse my ignorance, but I have never modified a script. I figured out how to pull out just the updater script file but I want to make sure I modify it correctly. Here is what the top bunch of lines look like in my script. If I understand correctly I am just going to replace any one of the "T999….." with "T999UVUENC2" It should make no difference which one? Also What are the signature files? I have three files in the META-INF folder, CERT.RSA, CERT.SF, and MANIFEST.MF. I presume you are talking about those three files? Please confirm that I am correct. If I need to modify anything else in the script below please let me know.
Thank you once again.
assert(getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo");
assert(getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999UVUEMJC" ||
getprop("ro.bootloader") == "T999VVLDLL1" ||
getprop("ro.bootloader") == "T999LUVAMB7" ||
getprop("ro.bootloader") == "T999VVLDMF2" ||
getprop("ro.bootloader") == "T999VVLUEMK5");

You are correct on both. To make it even easier, replace the build ending in MJC. All you'd have to do is change MJC to NC2.
And don't worry too much about any of this. If you happen to do something wrong it would most likely fail w/o flashing anything.

DocHoliday77 said:
You are correct on both. To make it even easier, replace the build ending in MJC. All you'd have to do is change MJC to NC2.
And don't worry too much about any of this. If you happen to do something wrong it would most likely fail w/o flashing anything.
Click to expand...
Click to collapse
I got through that and now I get a status 4 error. I know I have more than enough internal memory. I did store the CM file on the internal memory to flash it. Would that have anything to do with it? Do I have to install it from an external sd?
Here is the log file. I think also for some reason my changes are not getting saved to the name when I change EMJC to ENC2 based upon what I'm seeing below. The signature files also don't seem to delete and when I remove the .txt at the end of the file name to save it back to the zip file I also think it stays there regardless.
-- Installing: /sdcard/0/0/cm-10.2.1-d2tmo.zip
Finding update package...
I:Update location: /sdcard/0/0/cm-10.2.1-d2tmo.zip
I:using /data/media for /sdcard/0/0/cm-10.2.1-d2tmo.zip.
Opening update package...
Installing update...
Warning: No file_contexts
script aborted: assert failed: getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999UVUEMJC" ||
getprop("ro.bootloader") == "T999VVLDLL1" ||
getprop("ro.bootloader") == "T999LUVAMB7" ||
getprop("ro.bootloader") == "T999VVLDMF2" ||
getprop("ro.bootloader") == "T999VVLUEMK5"
assert failed: getprop("ro.bootloader") == "T999UVDLJA" || getprop("ro.bootloader") == "T999UVDLJC" || getprop("ro.bootloader") == "T999UVDMD5" || getprop("ro.bootloader") == "T999UVUEMJC" || getprop("ro.bootloader") == "T999VVLDLL1" || getprop("ro.bootloader") == "T999LUVAMB7" || getprop("ro.bootloader") == "T999VVLDMF2" || getprop("ro.bootloader") == "T999VVLUEMK5"
E:Error in /sdcard/0/0/cm-10.2.1-d2tmo.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/0/0/cm-10.2.1-d2tmo.zip")
I:using /data/media for /sdcard.

Can you get the log and paste the error here again? Not familiar with status 4 right off hand.
It shouldn't matter if its on internal or external sd. But you can try flashing from external.

DocHoliday77 said:
Can you get the log and paste the error here again? Not familiar with status 4 right off hand.
It shouldn't matter if its on internal or external sd. But you can try flashing from external.
Click to expand...
Click to collapse
I did , see above message. I am definitely not doing something right. I am on a Mac and using text editor to modify the file. That was my second try, the first time I did get a status 4 and I remodified and tried again and now I got a status 7 again.

It looks like the edit you made didnt take. Did you unzip the rom, make the edit and then rezip into a new file?
I don't know what text editor you should use on a mac. Go to Notepad++ website to see if they support it. If not you will have to find an editor that preserves the EOL formatting (End of Line) as Unix style. Not sure if a mac is able to do that with a built in editor.
You could make the edits on device I suppose, but its just a little more time consuming and easier to make mistakes.

DocHoliday77 said:
It looks like the edit you made didnt take. Did you unzip the rom, make the edit and then rezip into a new file?
I don't know what text editor you should use on a mac. Go to Notepad++ website to see if they support it. If not you will have to find an editor that preserves the EOL formatting (End of Line) as Unix style. Not sure if a mac is able to do that with a built in editor.
You could make the edits on device I suppose, but its just a little more time consuming and easier to make mistakes.
Click to expand...
Click to collapse
I found a way to edit the file and I know it is taking the edit. I have tried again and it still fails. However, when I view the log and it says saved in the CWM folder and I go to retrieve it, it is not there. There is no saved log that I can upload. Any thoughts?
Can I install kitkat on the SGH T999, it is the older model, not the LTE. And have you tried CM for KitKat? How is it, reasonably stable? Would that resolve my issues?

Can't install new omnirom?? (also not with cyandelta)

Trying to update my omnirom with the newest one without luck... Can anybody help me what to do??
(also tried updating with cyandelta with no luck either)
Here's the log I get when I try to install the zip from recovery:
I:Copying file /cache/recovery/log to /cache/recovery/last_log
I:Attempt to load settings from settings file...
I:Loading settings from '/data/media/0/TWRP/.twrps'.
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/04e90d970c90d684'
I:Copying file /etc/recovery.fstab to /cache/recovery/recovery.fstab
I:Version number saved to '/cache/recovery/.version'
I:Switching packages (TWRP)
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Installing '/sdcard/Download/omni-4.4.4-20140921-geehrc-NIGHTLY.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Verifying zip signature...
I:read key e=3 hash=20
I:1 key(s) loaded from /res/keys
I:comment is 1477 bytes; signature 1459 bytes from end
I:failed to verify against key 0
I:i: 0, eocd_size: 1499, RSANUMBYTES: 256
E:failed to verify whole-file signature
E:Zip signature verification failed: 1
Error flashing zip '/sdcard/Download/omni-4.4.4-20140921-geehrc-NIGHTLY.zip'
Updating partition details...
Iata backup size is 1343MB, free: 9694MB.
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log

Anybody?

Still trying.....
This is what I get:
Installing '/sdcard/Download/omni-4.4.4-20140922-geehrc-NIGHTLY.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: This package is for "mako,geeb,gee_a,e970,gee,geebus,e971,e973,e975,geehrc" devices
this is a "geehrc4g".
This package is for "mako,geeb,gee_a,e970,gee,geebus,e971,e973,e975,geehrc" devicesthis is a "geehrc4g".
E:Error executing updater binary in zip '/sdcard/Download/omni-4.4.4-20140922-geehrc-NIGHTLY.zip'
Error flashing zip '/sdcard/Download/omni-4.4.4-20140922-geehrc-NIGHTLY.zip'
Updating partition details...
Iata backup size is 1388MB, free: 7744MB.
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log

niknik76 said:
Still trying.....
This is what I get:
Installing '/sdcard/Download/omni-4.4.4-20140922-geehrc-NIGHTLY.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: This package is for "mako,geeb,gee_a,e970,gee,geebus,e971,e973,e975,geehrc" devices
this is a "geehrc4g".
This package is for "mako,geeb,gee_a,e970,gee,geebus,e971,e973,e975,geehrc" devicesthis is a "geehrc4g".
E:Error executing updater binary in zip '/sdcard/Download/omni-4.4.4-20140922-geehrc-NIGHTLY.zip'
Error flashing zip '/sdcard/Download/omni-4.4.4-20140922-geehrc-NIGHTLY.zip'
Updating partition details...
Iata backup size is 1388MB, free: 7744MB.
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log
Click to expand...
Click to collapse
From error message, your phone model is not in asseted list validation. If old version work on your phone you can use zip program to add your model to update-script by
1. Open META-INF\com\google\android\updater-script in zip file.
2. Add getprop("ro.product.device") == "geehrc4g" to that file, it should look like this
Code:
(getprop("ro.product.device") == "mako" || getprop("ro.build.product") == "mako" ||
getprop("ro.product.device") == "geeb" || getprop("ro.build.product") == "geeb" ||
getprop("ro.product.device") == "gee_a" || getprop("ro.build.product") == "gee_a" ||
getprop("ro.product.device") == "e970" || getprop("ro.build.product") == "e970" ||
getprop("ro.product.device") == "gee" || getprop("ro.build.product") == "gee" ||
getprop("ro.product.device") == "geebus" || getprop("ro.build.product") == "geebus" ||
getprop("ro.product.device") == "e971" || getprop("ro.build.product") == "e971" ||
getprop("ro.product.device") == "e973" || getprop("ro.build.product") == "e973" ||
getprop("ro.product.device") == "e975" || getprop("ro.build.product") == "e975" ||
[COLOR="Red"]getprop("ro.product.device") == "geehrc4g" || getprop("ro.build.product") == "geehrc4g" || [/COLOR]
getprop("ro.product.device") == "geehrc" || getprop("ro.build.product") == "geehrc") || abort("This package is for \"mako,geeb,gee_a,e970,gee,geebus,e971,e973,e975,geehrc\" devices
this is a \"" + getprop("ro.product.device") + "\".");
3. repack zip and flash rom.

Thanks!!!!!!!!!!!!!!!
I did what you said - now I get this:
¨Installing '/sdcard/Download/omni-4.4.4-20140922-geehrc-NIGHTLY.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/sdcard/Download/omni-4.4.4-20140922-geehrc-NIGHTLY.zip'
Updating partition details...
Iata backup size is 1419MB, free: 9814MB.
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log

niknik76 said:
Thanks!!!!!!!!!!!!!!!
I did what you said - now I get this:
¨Installing '/sdcard/Download/omni-4.4.4-20140922-geehrc-NIGHTLY.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/sdcard/Download/omni-4.4.4-20140922-geehrc-NIGHTLY.zip'
Updating partition details...
Iata backup size is 1419MB, free: 9814MB.
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log
Click to expand...
Click to collapse
No error message so I cannot figure out what is the problem. Maybe there are more information in /data/media/0/recovery.log
Did you ever flash older omnirom successfully on your phone?

@niknik76, I can install latest omnirom without any problem, may be it is your recovery that has problem with latest omnirom.

Thanks a lot artit!
I got it working! Very funky workaround.. Changed recovery to CWM and used adb sideload (which didn't work for me with TWRP) and it worked..
So is there any way you can change your device name or somehow get things working more smooth?? For example I tried to update with opendelta after I got omni installed - and I get the same error about the device being a geehrc4g:
Installing zip file '/data/media/0/OpenDelta/omni-4.4.4-20140925-geehrc-NIGHTLY.zip'
Installing '/data/media/0/OpenDelta/omni-4.4.4-20140925-geehrc-NIGHTLY.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Verifying zip signature...
I:read key e=65537 hash=20
I:1 key(s) loaded from /res/keys
I:comment is 1477 bytes; signature 1459 bytes from end
I:whole-file signature verified against key 0
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: This package is for "mako,geeb,gee_a,e970,gee,geebus,e971,e973,e975,geehrc" devices
this is a "geehrc4g".
This package is for "mako,geeb,gee_a,e970,gee,geebus,e971,e973,e975,geehrc" devicesthis is a "geehrc4g".
E:Error executing updater binary in zip '/data/media/0/OpenDelta/omni-4.4.4-20140925-geehrc-NIGHTLY.zip'
E:Error installing zip file '/data/media/0/OpenDelta/omni-4.4.4-20140925-geehrc-NIGHTLY.zip'
Done processing script file

niknik76 said:
Thanks a lot artit!
I got it working! Very funky workaround.. Changed recovery to CWM and used adb sideload (which didn't work for me with TWRP) and it worked..
So is there any way you can change your device name or somehow get things working more smooth?? For example I tried to update with opendelta after I got omni installed - and I get the same error about the device being a geehrc4g:
Installing zip file '/data/media/0/OpenDelta/omni-4.4.4-20140925-geehrc-NIGHTLY.zip'
Installing '/data/media/0/OpenDelta/omni-4.4.4-20140925-geehrc-NIGHTLY.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Verifying zip signature...
I:read key e=65537 hash=20
I:1 key(s) loaded from /res/keys
I:comment is 1477 bytes; signature 1459 bytes from end
I:whole-file signature verified against key 0
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: This package is for "mako,geeb,gee_a,e970,gee,geebus,e971,e973,e975,geehrc" devices
this is a "geehrc4g".
This package is for "mako,geeb,gee_a,e970,gee,geebus,e971,e973,e975,geehrc" devicesthis is a "geehrc4g".
E:Error executing updater binary in zip '/data/media/0/OpenDelta/omni-4.4.4-20140925-geehrc-NIGHTLY.zip'
E:Error installing zip file '/data/media/0/OpenDelta/omni-4.4.4-20140925-geehrc-NIGHTLY.zip'
Done processing script file
Click to expand...
Click to collapse
I'm not sure but I think device name is depend on which recovery you used. You should install recovery for geehrc or e975 to change your phone device name in recovery mode. Maybe other member can give your more information.

[Q] Can't flash rom on my KF.

My KF was miui 4.22.
When I using TWRP to flash another rom.
it can't flash it and notice like this.
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/sdcard/update.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
assert failed: getprop("ro.product.device") == "blaze" || getprop("ro.build.product") == "blaze"
E:Error executing updater binary in zip '/sdcard/update.zip'
Error flashing zip '/sdcard/update.zip'
Updating partition details...
What should i do for it?
please help me.