Related
Hello,
I Have a Nexus 5 with root, stock rom, Franco Kernel and the custom recovery is TWRP. I accomplished this by following a guide around this forum, I know very little about Android. The Android version i'm running is the 4.4.2 and the phone keeps asking me to update do the newer version, however, when I try to do it, it takes me to the TWRP menu, and when I try to install it there, I get this error:
"/system/bin/thermal-engine-hh" has unexpected contents
E: Error executing updater binary in zip
Error flashing zip
How can I update the phone to the newer version of android? Can anyone help me? Thanks.
D5R said:
Hello,
I Have a Nexus 5 with root, stock rom, Franco Kernel and the custom recovery is TWRP. I accomplished this by following a guide around this forum, I know very little about Android. The Android version i'm running is the 4.4.2 and the phone keeps asking me to update do the newer version, however, when I try to do it, it takes me to the TWRP menu, and when I try to install it there, I get this error:
"/system/bin/thermal-engine-hh" has unexpected contents
E: Error executing updater binary in zip
Error flashing zip
How can I update the phone to the newer version of android? Can anyone help me? Thanks.
Click to expand...
Click to collapse
That is the faulty zip, or the zip is not meant for your device! Maybbe, you should post this in Nexus 5 forum!
http://forum.xda-developers.com/google-nexus-5/help
lionelsuyog said:
That is the faulty zip, or the zip is not meant for your device! Maybbe, you should post this in Nexus 5 forum!
http://forum.xda-developers.com/google-nexus-5/help
Click to expand...
Click to collapse
Thanks, i'll do that!
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
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!
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...
Thread Closed
Thread Closed
@TheHitMan Thank you so much, this port is perfect! But I think I made a mistake... When, in TWRP, need to flash "no-verity-opt-encrypt.zip" I tryed to flash the lastest (6.0) but it says "FAIL" or something like that...
Long story short, When I turn on the device says "your device has been unlocked and can't be trusted" , "Your device will boot in 5 seconds" (After the 5 seconds the device boot normally)
What can I do to fix that little detail???
WaLt-B.F. said:
@TheHitMan Thank you so much, this port is perfect! But I think I made a mistake... When, in TWRP, need to flash "no-verity-opt-encrypt.zip" I tryed to flash the lastest (6.0) but it says "FAIL" or something like that...
Long story short, When I turn on the device says "your device has been unlocked and can't be trusted" , "Your device will boot in 5 seconds" (After the 5 seconds the device boot normally)
What can I do to fix that little detail???
Click to expand...
Click to collapse
Nothing bad with this warning. Its a bootloader unlock warning.
Officia TWRP is available
shagul said:
Officia TWRP is available
Click to expand...
Click to collapse
No difference, until this build works fine.
Hey bro, can you belive I just do the OTA update with twrp and my phone boot to twrp but not to system???
What can I do??? =\
WaLt-B.F. said:
Hey bro, can you belive I just do the OTA update with twrp and my phone boot to twrp but not to system???
What can I do??? =\
Click to expand...
Click to collapse
Reflash system partition again. First wipe then install.
TheHitMan said:
Reflash system partition again. First wipe then install.
Click to expand...
Click to collapse
I´ve tryed but that doesn´t worked... Long story short, I restarted the phone in flashboot mode, at least in my case i had to install adb bootloader drivers manually, and then use the "flashall.bat" of the stock rom... I was worried...
Thank you!
WaLt-B.F. said:
I´ve tryed but that doesn´t worked... Long story short, I restarted the phone in flashboot mode, at least in my case i had to install adb bootloader drivers manually, and then use the "flashall.bat" of the stock rom... I was worried...
Thank you!
Click to expand...
Click to collapse
You can't install OTA updates with a custom recovery. You need stock recovery to perform OTA update operation.
TheHitMan said:
You can't install OTA updates with a custom recovery. You need stock recovery to perform OTA update operation.
Click to expand...
Click to collapse
Tell me about it xD
I didn´t know that until yesterday, what a noob, lol. Thanks for you help and for answer so soon! :good:
Hi, do u have a version for MT6735 variant?
My device details:
Model: Moto e4 plus
SKU: xt1772
variant: MT6735
i can successfully flash and boot this twrp version, but twrp recognizes my device as codename "woods" (thats moto e4).
Anyway, i tried to install roms for moto e4 "woods" but they all loop the bootloader.
DanielBrownM said:
Hi, do u have a version for MT6735 variant?
My device details:
Model: Moto e4 plus
SKU: xt1772
variant: MT6735
i can successfully flash and boot this twrp version, but twrp recognizes my device as codename "woods" (thats moto e4).
Anyway, i tried to install roms for moto e4 "woods" but they all loop the bootloader.
Click to expand...
Click to collapse
Its "MT6735" the SOC (system-on-chip) not the variant. Do not install moto e4 roms into moto e4 plus you will always ended up with bootloop. Can you please elaborate futher, How it recognize your device as wood ?
Because when i tried to intall the roms, they all returned an error saying: this rom is for nicklaus and this device is woods (not the exact words).
And in twrp home screen, top left of the corner (where usually shows the cpu temperature) says: 3.2.1-opr1-woods
DanielBrownM said:
Because when i tried to intall the roms, they all returned an error saying: this rom is for nicklaus and this device is woods (not the exact words).
And in twrp home screen, top left of the corner (where usually shows the cpu temperature) says: 3.2.1-opr1-woods
Click to expand...
Click to collapse
Thanks for reporting.
I will fix this soon and for now use 3.1.1 build floating around here.
TheHitMan said:
Thanks for reporting.
I will fix this soon and for now use 3.1.1 build floating around here.
Click to expand...
Click to collapse
Thanks but already tried with 3.1.1.
In that version the problem is similar, but instead of woods recognizes the device just as "e4".
DanielBrownM said:
Thanks but already tried with 3.1.1.
In that version the problem is similar, but instead of woods recognizes the device just as "e4".
Click to expand...
Click to collapse
I double check out the 3.1.1 XT1772 thread and no one report about the error you mentioned here.
I have installed v3.1.1 right now, after reading your post, just to be sure.
The output is the next when triting to install roms (dot and aosp) for nicklaus:
Code:
E004: This package is for: nicklaus, e4plus; this device is e4.
DanielBrownM said:
I have installed v3.1.1 right now, after reading your post, just to be sure.
The output is the next when triting to install roms (dot and aosp) for nicklaus:
Code:
E004: This package is for: nicklaus, e4plus; this device is e4.
Click to expand...
Click to collapse
What i have seen from error is not the recovery problem at all. Probably you need to upload META-INF from dotos or aosp rom. It looks like assert command problem.
TheHitMan said:
What i have seen from error is not the recovery problem at all. Probably you need to upload META-INF from dotos or aosp rom. It looks like assert command problem.
Click to expand...
Click to collapse
I just checked updater-script in META-INF file of the rom and probably is assert problem.
When i run ro.product.device in adb the command return this:
Code:
C:\Users\admin>adb shell getprop ro.product.model
Moto E (4) Plus
C:\Users\admin>adb shell getprop ro.product.device
nicklaus_f
C:\Users\admin>adb shell getprop ro.build.product
nicklaus
But, when trying to install the rom in twrp, the return of that command is "wood" for twrp v3.2.1 and "e4" in twrp 3.1.1.
Maybe i should try to delete assert line in updater-script of the rom and install.
----edited---
Actually when i write getprop ro.build.product in twrp terminal returns "woods"