Hello. This is my first post in this forum, so forgive me if i post this in a wrong category.
I have Zenfone 2 ZE500CL, flashed with LineageOS 14.1 20180127 Nightly Build from this.
I've tried to install the latest Magisk from here : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445, also the one from here : https://forum.xda-developers.com/zenfone2/development/magisk-14-0-root-universal-zenfone-2-t3669137. None of them working. Both of them prints output that says : "Unable to Detect Boot Image".
I've tried to extract the boot.img from my device build of LineageOS, and then use Magisk Manager to patch the boot image manually, and failed miserably. I've even tried to extract the boot.img to test if it's even readable with Android Kitchen, and sure it is it can't read the file while outputting : "Unsupported Format".
Can anyone help me at this?
same here tried everything i know but still unsupported for our device, i'm using mokee rom for asus zen2 500cl
i found that we need a boot image signature just like the others try to look at this https://forum.xda-developers.com/zenfone2/development/script-boot-recovery-image-signature-t3690522
Related
Hi, Devs!
i'm having problem with flashable zips. :crying:Every time i flash a zip in TWRP
which is not specially made for Zenfone 2 x86 devices it shows me an error
"updater process ended with error 255":crying:
I also changed the 'update-binary' file from METAF folder from the Zenfone to firmware. But again it shows me another error of "updatre process ended
with error 6".:crying:
Someone can please tell me how could i make zips X86 device compitable?
There is a TWRP available for the Zenfone 2. May not be the latest but it works, its in either Android Developement or Original Android Developement.
i have TWRP
But i have TWRP version 3.0.0.0?
But let me know that the above problem is becouse of TWPR or the ZIP file?
I can't flash Lineage OS 17 or anything after wiped the datas, it gives me error 1 and error 7, I don't know how to fix them. Please
Are you using the correct version:
TWRP Daisy 3.3.1 Offain?
Hi,
I am "building" (first had to fix the LCD etc.) a de-googled DAISY. I managed to unlock the bootloader, install TWRP, and root the original OS (Android One 10).
The problems started when I tried to install a custom ROM (at first Havoc, but other gave the same results). Just as instructed (YT, other pages, here...) I:
- formatted via TWRP
- REBOOT to TWRP
- wipe all except SD
- install ROM from zip
...and at this point I came across an error message
Error applying update: 7 (Error code: : kInstallDeviceOpenError)
Updater process ended with ERROR: 1
Many solutions suggest flashing boot.img from the ROM package, but (WHY?!?) all ROM's ((Havos, crDroid etc.) for daisy have no such file, although other devices have boot.img in their package.
I'm pretty much clueless... :/
Help, and thanks in advance...
mothzart said:
Hi,
I am "building" (first had to fix the LCD etc.) a de-googled DAISY. I managed to unlock the bootloader, install TWRP, and root the original OS (Android One 10).
The problems started when I tried to install a custom ROM (at first Havoc, but other gave the same results). Just as instructed (YT, other pages, here...) I:
- formatted via TWRP
- REBOOT to TWRP
- wipe all except SD
- install ROM from zip
...and at this point I came across an error message
Error applying update: 7 (Error code: : kInstallDeviceOpenError)
Updater process ended with ERROR: 1
Many solutions suggest flashing boot.img from the ROM package, but (WHY?!?) all ROM's ((Havos, crDroid etc.) for daisy have no such file, although other devices have boot.img in their package.
I'm pretty much clueless... :/
Help, and thanks in advance...
Click to expand...
Click to collapse
Error 1 usually means wrong install package or wrong TWRP.
Are you using TWRP by offain?
[SOLVED]
The whole problem was that TWRP was wrong (not even offain as far as I remember). But I got a HUUUUGE amount of help (MANY THANX!!!!) from opal06 (main maintainer for crDroid on daisy) on Telegram channel dedicated to crDroid on daisy.
So If anyone hase similar problems - go to Telegram group - they will help you!
After flashing right (modified) TWRP versions, evrthng went fine, although I got to admit it was pretty complicated for [unlock + TWRP + custom rom + root] combo. On lavender it was much easier
cya all, good luck!
I tried to install the evolution x rom on my Redmi 8A phone I can confirm that I downloaded the right file then proceed to flash it on orange fox recovery project (sideloaded it) then suddenly it throws back the error code
Updater process ended error : 255
Tried multiple times reflashed the recovery changing to twrp ( I used the official recovery) on my previous device I also experienced this problem and there was an unofficial twrp image that solved this they say it's because I tried to flash a 64 bit Rom on a 32 bit recovery plus I can't find any "64 bit" version for my device any help????
If you need any information comment it down I won't reply instantly but I will
Hello guys. So, i want to install an unofficial lineage os to my Xiaomi redmi 6 (cereus). But th problem is the custom rom file format is img.xz and it's not detected by the TWRP recovery. I've tried to extract the img.xz into a img file. And it actually detected with the TWRP, so i tried to install it and locate the rom to System Image. It's tecnically got the rom image installed succesfully, but when i tried to boot it up, it's just got to the xiaomi logo and then it's just restarted repeatedly to the xiaomi logo again and again. So at this point, I don't know what can i do?
Note : Gapps and magisk installed without any issues because they're zip files. So i don't think the problem is in the magisk or Gapps.
Device : Xiaomi Redmi 6 ( Cereus )
TWRP Version : 3.6.2_9.0
Lineage OS ROM : Lineage OS Unofficial cereus (a64 and ab rom ) ( I got it from Andy Yan's Personal Builds SourceForge ).
NarenTheNoobFlasher said:
Hello guys. So, i want to install an unofficial lineage os to my Xiaomi redmi 6 (cereus). But th problem is the custom rom file format is img.xz and it's not detected by the TWRP recovery. I've tried to extract the img.xz into a img file. And it actually detected with the TWRP, so i tried to install it and locate the rom to System Image. It's tecnically got the rom image installed succesfully, but when i tried to boot it up, it's just got to the xiaomi logo and then it's just restarted repeatedly to the xiaomi logo again and again. So at this point, I don't know what can i do?
Note : Gapps and magisk installed without any issues because they're zip files. So i don't think the problem is in the magisk or Gapps.
Device : Xiaomi Redmi 6 ( Cereus )
TWRP Version : 3.6.2_9.0
Lineage OS ROM : Lineage OS Unofficial cereus (a64 and ab rom ) ( I got it from Andy Yan's Personal Builds SourceForge ).
Click to expand...
Click to collapse
Its Feb 2023 and I've just done EXACTLY the same thing trying to put lineageOS 20 onto a Galaxy TAB A 8..0 LTE. Hope I find a solution as my device is resting in download mode just to stop it from looping/buzzing.