Moto E XT1021 GB OMNI version - can't install any rom - Moto E Q&A, Help & Troubleshooting

Phone was replaced by Motorola to a new device - after motherboard bug. A new device is UK version.
I have unlocked it and installed recovery, but I can't install any rom - I've tried with CWM and TRWP (2 different versions).
Every try ends up with "ERROR 7". In error logs:
You have an installed system that isn't signed with this build's key, aborting...
run_program: child exited with status 124
script aborted: Can't install this package on top of incompatible data. Please try another package or run a factory reset
Can't install this package on top of incompatible data. Please try another package or run a factory reset
Updater process ended with ERROR: 7
Click to expand...
Click to collapse
I've tried with:
aokp_condor_mm_nightly_2017-01-16
AospExtended-v3.1-condor-20170124-0102-OFFICIAL
lineage-14.1-20170119-UNOFFICIAL-condor
I found a solution for "Error 7" (remove first lines from update-script) but it doesn't help.
Similar problem I found here: http://www.androidpit.com.br/forum/...o-para-lollilop-da-erro-mesmo-sem-root/page/2
In my CWM log there was also something like:
Package expects build fingerprint of motorola/condor_retbr_ds/condor_umtsds:4.4.4/KXC21.5-40/49:user/release-keys or motorola/condor_retbr_ds/condor_umtsds:5.1/LPC23.13-34.8/12:user/release-keys; this device has Motorola/omni_condor/condor:4.4.2/KOT49H/eng.bigbiff.20140616.171951:eng/test-keys.
Click to expand...
Click to collapse
So the problem is "omni_condor" fingerprint of a device. Is it a different hardware then all other versions?
The fingerprint is also checked in update-script:
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
Click to expand...
Click to collapse
I can remove that lines and try to install system, but I don't want to brick it.
Any ideas? Do I need special version of CWM/TRWP or just need to "fix" update-script and it should work ok?

Official twrp causes problem with nougat ROMs ! Try squid twrp ( http://www.mediafire.com/file/ca3rjwh43qbzmw5/twrp-condor-3.0.2-r5.img ) and if you want to flash gapps then you should flash pico gapps .

xterm1 said:
Phone was replaced by Motorola to a new device - after motherboard bug. A new device is UK version.
I have unlocked it and installed recovery, but I can't install any rom - I've tried with CWM and TRWP (2 different versions).
Every try ends up with "ERROR 7". In error logs:
I've tried with:
aokp_condor_mm_nightly_2017-01-16
AospExtended-v3.1-condor-20170124-0102-OFFICIAL
lineage-14.1-20170119-UNOFFICIAL-condor
I found a solution for "Error 7" (remove first lines from update-script) but it doesn't help.
Similar problem I found here: http://www.androidpit.com.br/forum/...o-para-lollilop-da-erro-mesmo-sem-root/page/2
In my CWM log there was also something like:
So the problem is "omni_condor" fingerprint of a device. Is it a different hardware then all other versions?
The fingerprint is also checked in update-script:
I can remove that lines and try to install system, but I don't want to brick it.
Any ideas? Do I need special version of CWM/TRWP or just need to "fix" update-script and it should work ok?
Click to expand...
Click to collapse
Flash stock lollipop and then flash mm or n

vinithv said:
Official twrp causes problem with nougat ROMs ! Try squid twrp ( http://www.mediafire.com/file/ca3rjwh43qbzmw5/twrp-condor-3.0.2-r5.img ) and if you want to flash gapps then you should flash pico gapps .
Click to expand...
Click to collapse
Rajendran Rasa said:
Flash stock lollipop and then flash mm or n
Click to expand...
Click to collapse
Stock 5.1 with TRWP 3.0.2-r5 and still "error 7". It seems to be problem with fingerprint.
Looks like the only way to do it is to edit update-script and remove fingerprint check.
UPDATE/EDIT
After removing fingerprint check everything works ok - I can flash rom and it is working ok. Problem solved.

xterm1 said:
Stock 5.1 with TRWP 3.0.2-r5 and still "error 7". It seems to be problem with fingerprint.
Looks like the only way to do it is to edit update-script and remove fingerprint check.
UPDATE/EDIT
After removing fingerprint check everything works ok - I can flash rom and it is working ok. Problem solved.
Click to expand...
Click to collapse
I face the same issue.. Which line should be removed from the below
getprop("ro.build.fingerprint") == "motorola/condor_retaildsds/condor_umtsds:4.4.4/KXC21.5-40/46:user/release-keys" ||
getprop("ro.build.fingerprint") == "motorola/condor_retaildsds/condor_umtsds:5.0.2/LXC22.46-32/30:user/release-keys" ||
abort("Package expects build fingerprint of motorola/condor_retaildsds/condor_umtsds:4.4.4/KXC21.5-40/46:user/release-keys or motorola/condor_retaildsds/condor_umtsds:5.0.2/LXC22.46-32/30:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");

Related

Installing PA - Device not Scorpion

I'm trying to install the new PA rom for our tablet and I'm getting a strange error. It says "This package is for "Scorpion" devices; this is a "z3".
Has anyone else faced this issue before?
You need to be on this FW : 23.4.A.0.546.
But don't bother, there is no recovery. I can't enter it atleast.
undeniableturnip said:
I'm trying to install the new PA rom for our tablet and I'm getting a strange error. It says "This package is for "Scorpion" devices; this is a "z3".
Has anyone else faced this issue before?
Click to expand...
Click to collapse
Extract the zip, goto to "META-INF\com\google\android" open the updater script and remove this line "getprop("ro.product.device") == "scorpion_windy" || abort("This package is for "scorpion_windy" devices; this is a "" + getprop("ro.product.device") + "".");
ui_print(" ");", save it and rezip.
Otherwise try using the official TWRP recovery.
ckyy said:
You need to be on this FW : 23.4.A.0.546.
But don't bother, there is no recovery. I can't enter it atleast.
Click to expand...
Click to collapse
A workaround for this is to reboot it into fastboot, flash the official twrp and reboot, you can get into recovery but the system won't boot, when you're done go back to fastboot and flash the boot.img from the PA zip.
Installing PA in Z3 Compact Tablet
undeniableturnip said:
I'm trying to install the new PA rom for our tablet and I'm getting a strange error. It says "This package is for "Scorpion" devices; this is a "z3".
Has anyone else faced this issue before?
Click to expand...
Click to collapse
I have been trying to install three time only ending with the error message that the package is not for "scorpion" but for "Leo" I will appreciate for clarification, thanks.

failed custom rom installation everytime

hey guys,
well i have a weird issue that is whenever i try to install any custom rom on my honor 5x, it bootloops. tried many methods and followed every step but still a bootloop. whenever i reboot it into recovery after a bootloop, it shows a commandline for sometime. On that this is written:
E: Failed to map file 'Aaaaaa2.zip'
E: error installing zip
moreover i even tried different versions of twrp but still the same problem.
i tried twrp 3.0.2, 3.0.1 .
it happens with every rom for me.
Please help me....to solve this issue
i have unlocked bootloader and the device is on latest b360 update.
hrimandev said:
hey guys,
well i have a weird issue that is whenever i try to install any custom rom on my honor 5x, it bootloops. tried many methods and followed every step but still a bootloop. whenever i reboot it into recovery after a bootloop, it shows a commandline for sometime. On that this is written:
E: Failed to map file 'Aaaaaa2.zip'
E: error installing zip
moreover i even tried different versions of twrp but still the same problem.
i tried twrp 3.0.2, 3.0.1 .
it happens with every rom for me.
Please help me....to solve this issue
i have unlocked bootloader and the device is on latest b360 update.
Click to expand...
Click to collapse
Downgrade to B340 as it is known (from what I read) that no custom rom can be installed on B360.
muradulislam said:
Downgrade to B340 as it is known (from what I read) that no custom rom can be installed on B360.
Click to expand...
Click to collapse
Can u plz send me the link
hrimandev said:
Can u plz send me the link
Click to expand...
Click to collapse
You can try to find it here
http://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288/page1
Or use this tool if it's not there
http://forum.xda-developers.com/honor-7/general/huawei-firmware-finder-team-mt-t3469621/page1
hrimandev said:
Can u plz send me the link
Click to expand...
Click to collapse
just fixed this 2 posts down for another user
http://forum.xda-developers.com/showpost.php?p=69156226&postcount=53
Fail to map a file
When I try to install custom rom in honor 5x l22. It says that fail to map a file so can u help me out with steps by steps so I can fix the problem plezz
Same problm.with me how to fix step by step plz in whatspp +91 8805164341

TWRP + CM13 Error 7 ?

Hi folks, i am struggling with this issue the last 2 days,
first i kinda bricked my X, i followed this guide to bring it back on
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
i made all updates available to 3.1.4... i unlocked boot loader, flashed TWRP blu_sp★rk r175 and afterwards tryed to flash latest CM13 nightly
but with no luck, i am always receiving Error 7.. does anyone has a solution to this?
thanks in advance!
Tommyr84 said:
Hi folks, i am struggling with this issue the last 2 days,
first i kinda bricked my X, i followed this guide to bring it back on
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
i made all updates available to 3.1.4... i unlocked boot loader, flashed TWRP blu_sp★rk r175 and afterwards tryed to flash latest CM13 nightly
but with no luck, i am always receiving Error 7.. does anyone has a solution to this?
thanks in advance!
Click to expand...
Click to collapse
There's no blu spark kernel for ROMs/OOS with updated bootloader . Not sure if that's what causing the error 7 but its a start. Try using. Sultans uodated twrp I don't have any issues with it.
Exodusche said:
There's no blu spark kernel for ROMs/OOS with updated bootloader . Not sure if that's what causing the error 7 but its a start. Try using. Sultans uodated twrp I don't have any issues with it.
Click to expand...
Click to collapse
hmmm.. ok, i will give it a try! Thanks, i will tell if this works out
Tommyr84 said:
hmmm.. ok, i will give it a try! Thanks, i will tell if this works out
Click to expand...
Click to collapse
V175 is a kernel
You certainly flashed BS TWRP V41.
Kéno40 said:
V175 is a kernel
You certainly flashed BS TWRP V41.
Click to expand...
Click to collapse
so i tried sultans TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23)... also flashed SuperSU.. worked like a charm!
But when i am trying to flash CM13 (cm-13.0-20161122-NIGHTLY-onyx) i still get Error 7 ...
You tried to flash TWRP for CM13 sultan rom ?
Tommyr84 said:
so i tried sultans TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23)... also flashed SuperSU.. worked like a charm!
But when i am trying to flash CM13 (cm-13.0-20161122-NIGHTLY-onyx) i still get Error 7 ...
Click to expand...
Click to collapse
Flash twrp from here
http://forum.xda-developers.com/one...al-twrp-3-0-2-0-recovery-onyx-t3471584/page10
Fap4k said:
Flash twrp from here
http://forum.xda-developers.com/one...al-twrp-3-0-2-0-recovery-onyx-t3471584/page10
Click to expand...
Click to collapse
ok, i flashed this Twrp version, same error ! Error : 7 Error installing zip file
i realy don't know which point i am missing, i downloaded the CM13 nightly fresh from the official side...
i can't be the only one who is facing this error
Update the Boot-loader first, you can follow a post found in home page of opx, u still have to use another TWRP recovery (not official) after updating bootloader. U vil get all info in the thread.
raj.ify said:
Update the Boot-loader first, you can follow a post found in home page of opx, u still have to use another TWRP recovery (not official) after updating bootloader. U vil get all info in the thread.
Click to expand...
Click to collapse
Hi, according to your post, i followed this description http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
flashed "OPXBLUpdateOOS3.1" and new TWPR afterwards "twrp-3.0.2-2_blu_spark.v41-onyx_by-engstk.img" with no error!
rebooted into recovery, tried to install "cm-13.0-20161204-NIGHTLY-onyx" ... and guess what?! ERROR 7 again!
so i am defenetly on new bootloader, i tried all 3 options from the threat above (flashed via ADB and via SD card) no problem! also got bootloader unlocked info form ADB.
everything works, till i try to flash a CM image... then i receive ERROR 7 ;(
Hey There,
I`m stuck with the same Error.
The only Recovery i can boot ist the normal TWRP Recovery.
The blu Spark TWRP Recovery, the Stock Recovery and the CM13 Nighty Onyx Recovery wont work. I get the fastboot DTB not found Error.
And I cant install any custom ROM. I Always get the Error 7, ZIP could not be installed from Z://
If i erase the Assets it boots directly in to Bootloader (without saying Fastboot Mode on the screen, but with the OnePlus Logo).
If I flash one of the CM14 versions it gives no error 7 but boots into the Bootloader as well.
I have no custom kernel installed.
My plan was to flash the CM13 Nighty Onyx Recovery but I cant get around the DTB error,
Thanks for Help.
Greetings Clon
EDIT:
I tied the BL Update from the mentioned thread above.
aaaaand: Error 7
Here is my complete error:
Code:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
[COLOR="Red"]Updater ended with ERROR: 7
Error installing zip file '/sdcard/ROMs/cm-13.0-20161122-NIGHTLY-onyx.zip'[/COLOR]
---------- Post added at 05:33 PM ---------- Previous post was at 04:56 PM ----------
Okay I have a Solution, but I dont know how I did it.
This is what I made.
1. I did a factory reset.
2. I did a factory reset. (Why not tho)
3. I restarted the recovery.
4. I did a factory reset.
5. I changed the filesystem for data partition. (It was on ext4, but I changed it to ext4 although to get Errors out or something like that.
6. I rebooted into Bootloader.
7. I flashed and booted this recovery: http://forum.xda-developers.com/devdb/project/dl/?id=20236&task=get (and got no dtb error. yay!)
8. I installed the nightly CM, and the latest gapps (and i got no error 7. yay!)
I know its a bit random but i think the error has to do something with the data partition and the filesystem....
Void your warranty!

Error 7 while trying to flash a custom rom

I've tried to flash a custom rom with TWRP 3.1.1 (see [german] screenshot).
The device IS a E5823; in earlier times this error always points to the fact, that I'm not using the latest TWRP; but, there is no newer version for my device available.
Where can I search to fix this error?
Got it! The path /system with the file build.prop is missing in my rom, so the variable ro.product.device cannot be resolved.
This needs more work...
Berni-0815 said:
I've tried to flash a custom rom with TWRP 3.1.1 (see [german] screenshot).
The device IS a E5823; in earlier times this error always points to the fact, that I'm not using the latest TWRP; but, there is no newer version for my device available.
Where can I search to fix this error?
Click to expand...
Click to collapse
remove assert lines from updated script maybe
Shubh_028 said:
remove assert lines from updated script maybe
Click to expand...
Click to collapse
Should work, but the missing path /system in die rom-zip tells me that there are more thing going wrong while creating this rom...
Berni-0815 said:
Should work, but the missing path /system in die rom-zip tells me that there are more thing going wrong while creating this rom...
Click to expand...
Click to collapse
flash another ROM then lol
Yeah! Good idea. :angel: I'm already using LineageOS 14.1 on my device and I'm trying to build a newer version (as you can see if you take a look at the screenshot)...
And in fact this needs a lot more work...

Phone Stuck

I have a redmi 5 plus. I managed to install TWRP via ADB as suggested by the official page. Then, the phone entered the bootloop. I loaded the ZIPs of a custom rom also from ADB, because I did not have another way, I made the wipes and tried to install the rom. It is version 8.1 AOSPExtended. When I do, I get the error "Assert failed: vince.verify_trustzone (" TZ.BF.4.0.5-152683 ") ==" 1 "" Updater process ended with error: 7. Could someone help me? I can not find the solution!
Thanks in advance
You should try to install twrp_3.2.2-0 again using fastboot, reboot into recovery, mount your device storage, copy ROM you want to install and try to install it.
And you can try method described here.
Have a nice day.
Same problem
I'm having the same issue, did you solve the problem? If you have solved the problem, please can you help me.
When you want to flash AEX flash this bootloader, after this it should going to flash
https://androidfilehost.com/?fid=5862345805528046341
skrubxgt said:
When you want to flash AEX flash this bootloader, after this it should going to flash
https://androidfilehost.com/?fid=5862345805528046341
Click to expand...
Click to collapse
It's working thanks .

Categories

Resources