Hi everyone
First of all, some infos about my device
Security Level Patch: 2019-05-01
MIUI Version: Global Stable 10.3.3 (oCBMIXM)
Android Version: 8.1.0 O11019
Unlocked: True
Root: True (Magisk)
TWRP: twrp-3.3.1-0-cactus
RAM: 2GB
Storage: 16GB
Everything seems to work well except one thing... I can't flash any Custom rom.
The error :
Checking for Digest file...
Skipping Digest check: no Digest file found
Updater process ended with ERROR: 255
I wanted to Try pixel Experience or Lineage OS 15.1. I tried to flash both of them via TWRP but I've got the same error for the two of them .
I've already tried in several ways
Flashing again the TWRP
Installing from internal storage
Installing from the external storage
Wiping cache/dalvik
Wiping data
re-flashing the stock rom (using the MiFlasher tool)
The thing is i'm not a total newbie in flashing roms (I'm an entusiast since the Samsung Ace era), but this time I'm kinda flattered because I can't understand the reason of the problem and can't figure out how to solve it.
Any tips?
Thanks in advance.
Related
Hello to all of you. I followed the Cyanogenmod guide about how to flash CM on Moto E (https://wiki.cyanogenmod.org/w/Install_CM_for_otus ) . I unlocked the cell, installed TWRP 2.8.7 (forum.xda-developers.com/devdb/project/dl/?id=14164&task=get), uploaded the rom, wiped and start the install.
I have no errors and the process started but it never end ! I have always the "Flashing file 1 of 1" message and the bar, but the process is endless.
I try with the snapshot 12.1 and the nightly 13, it's the same.
What it's wrong ?
reboot and system problem
After 2 hours I forced a reboot into recovery. Now I have error on /system (it's not mounted).
If I format all (advanced wipe) I can mount /system and restart installation of the ROM. But the same happens: "detected filesystem ext4 on /dev/block/platform/msm_sdcc.1/by-name/system Patching system image unconditionally... Flashing file 1 of 1..." and never finished please someone can help me ?
twrp-otus-3.0.0-r2.img
I flashed with fast boot the new twrp-otus-3.0.0-r2.img.
Reboot in recovery mode, /system mount error, so Advanced wipe and reformatted system cache dalvik and data.
Loaded cm12 and start install.
Same problem: no error, but the process never end.
Please help.
PAC-ROM LP-MR1 same "patching system image unconditionally"
I check md5 and sha1 of files. All right.
I dowloaded a different ROM : http://forum.xda-developers.com/moto-e-2015/orig-development/rom-pac-rom-moto-e-2015-3g-t3122422
Same message and same endless install process...
Anyone has some suggestions ?
SOLVED!
My problem was that I choose the wrong model of Moto-E (finally it was not Otus).
I installed a TWRP for Otus but it gave no error in any step so I never consider this kinf of problem.
Then I discover that the output of ./adb devices -l (that show Otus as model) was different from that of ./fastboot getvar all (that show Condor as model).
So I installed a TWRP for Condor and a CM13 for Condor and now I am up and running.
Now I have some other problems as for example I can't format the sd as internal (error on final step of moving some data report a problem and a sd in corrupted state...) but I think is a CM nightly build problem.
I have an ascend mate 2. I have unlocked the bootloader, installed TWRP 3.1.1 and have updated my bios via Huawei site and currently have Android 5.1. I have tried uploading CyanogenMod 13 and lineage 14. Both times I get error 7 when uploading. Does anyone have any suggestions?
Batk138 said:
I have an ascend mate 2. I have unlocked the bootloader, installed TWRP 3.1.1 and have updated my bios via Huawei site and currently have Android 5.1. I have tried uploading CyanogenMod 13 and lineage 14. Both times I get error 7 when uploading. Does anyone have any suggestions?
Click to expand...
Click to collapse
You may want to provide your detailed procedure so others could help.
Batk138 said:
I have an ascend mate 2. I have unlocked the bootloader, installed TWRP 3.1.1 and have updated my bios via Huawei site and currently have Android 5.1. I have tried uploading CyanogenMod 13 and lineage 14. Both times I get error 7 when uploading. Does anyone have any suggestions?
Click to expand...
Click to collapse
I am experiencing the same issue. I did the advance wipe from TWRP 3.1.1 and install lineage 14. It stucks and gave this error message "This package supports bootloader(s) MSM8226C00B322_BOOT; This device has bootloader unknown. ". I had B322 built and Android 5.1.1 Lollipop on my Huawei Ascent Mate 2. I read from other forum and even tried to modify the line "assert(getprop("ro.bootloader") == "MSM8226C00B322_BOOT" || abort("This package supports bootloader(s): MSM8226C00B322_BOOT; this device has bootloader " + getprop("ro.bootloader") + ".");" in the file updater-script under META-INF\com\google\android directory and still not working. Please help
I am getting the same error. Full wipe of the device except for internal storage as I do not currently have a microSD card inserted (it's being used in my new phone, an S7 edge). I bought a new microSD card and used that to restore the stock ROM.
Exact text, copied from recovery.log:
Code:
Installing zip file '/sdcard/Download/lineage-14.1-20170302-nightly-mt2-signed.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Update binary zip
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
script aborted: This package supports bootloader(s): MSM8226C00B322_BOOT; this device has bootloader unknown.
This package supports bootloader(s): MSM8226C00B322_BOOT; this device has bootloader unknown.
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
I:Install took 0 second(s).
Error installing zip file '/sdcard/Download/lineage-14.1-20170302-nightly-mt2-signed.zip'
Edit: So, I just reinstalled the stock ROM, B322, with no problems. Then I flashed TWRP 3.1.0, again, with no problems.
But I keep getting error 7, and it keeps saying that "this device has bootloader unknown". What gives? I can't stand the ridiculously large UI elements of the stock ROM, so I'm not going back to that.
EDIT: Alright, so I think I fixed it. Simply remove the "asserts" line from update-script in the ROM zip that deals with the bootloader (leave the device line if you wish) and it should work.
I used the instructions in this thread.
Hi all,
I am currectly running SoLdieR9312's Pie Beta rom on my S9+ (G965F/DS) and I am attempting to install a GSI but I get the following error in TWRP:
[IMAGE FLASH STARTED]
Image to flash: '/sdcard/download/GSI's/AOSP Extended GSI.img'
Calculating restore details...
Flashing system Image...
simg2img 'sdcard/Download/'AOSP Extended GSI.img' '/dev/block/sda18' process ended with ERROR: 2
[IMAGE FLASH COMPLETED].
I am using the ARM64 a-only GSI and I am flashing image to system image partition. I have wiped data, dalvik, system and cache prior to installation as well as trying to flash without wiping anything prior to installation. I have attempted to install multiple ARM64 a-only GSI's but all return the same error as above. I have also attempted installing with firmware and vendor BRE5, Vendor-27_ARI9, BRJ8 and ZRKA. I have also attempted installing after being on multiple different custom roms. All of my normal Custom roms (.zip) flash and work perfectly.
I am relatively new to GSI's so forgive me if it's a juvenile question, all help will be greatly appreciated. (Just incase anyone is concerned - I have searched everywhere for an answer to this but I can't seem to find an answer anywhere).
LDP12 said:
Hi all,
I am currectly running SoLdieR9312's Pie Beta rom on my S9+ (G965F/DS) and I am attempting to install a GSI but I get the following error in TWRP:
[IMAGE FLASH STARTED]
Image to flash: '/sdcard/download/GSI's/AOSP Extended GSI.img'
Calculating restore details...
Flashing system Image...
simg2img 'sdcard/Download/'AOSP Extended GSI.img' '/dev/block/sda18' process ended with ERROR: 2
[IMAGE FLASH COMPLETED].
I am using the ARM64 a-only GSI and I am flashing image to system image partition. I have wiped data, dalvik, system and cache prior to installation as well as trying to flash without wiping anything prior to installation. I have attempted to install multiple ARM64 a-only GSI's but all return the same error as above. I have also attempted installing with firmware and vendor BRE5, Vendor-27_ARI9, BRJ8 and ZRKA. I have also attempted installing after being on multiple different custom roms. All of my normal Custom roms (.zip) flash and work perfectly.
I am relatively new to GSI's so forgive me if it's a juvenile question, all help will be greatly appreciated. (Just incase anyone is concerned - I have searched everywhere for an answer to this but I can't seem to find an answer anywhere).
Click to expand...
Click to collapse
You should ask it in treble forums as it is based on gsi firmwares... or you can just report to the dev of aosp extended in details
Fix
Nevermind, found a fix, my GSI images were in a containing folder so therefore not being read as being in the root directory/folder of my device. My bad :|
This thread can be closed.
Mod edit: Thread closed as duplicate of
Stuck installing ROM on Mi A2 Lite (daisy) - ERROR 1, ERROR 7
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...
forum.xda-developers.com
Oswald Boelcke
Senior Moderator
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...
I'm an absolute noob, I've got to the point where twrp is installed, wiped the cache etc.. trying to install the lineageos 17.1 rom and getting 'Error 1' installation failed... I can't find error 1 on google, only error 7 and 4...
Device is a Xiaomi Mi A2 lite, and I have downloaded the appropriate rom for that device from AndroidFileHost.com
any help appreciated... cheers
On further Googling, it appears I need to flash boot.img ... any ideas where to find this.. Not in the ROM .zip folder as suggested???
Edit.. I found the thread from @reujea0 for installing his latest ROM 18.1... awesome thx