i tried to flash this rom on my mi note 3 but i faced failure during flashing "no digest file found assert failed"
i faced same error for flashing lineage rom, i come from epic rom
anyone knows what i should do?
Flash latest official TWRP and try again.
zaqm said:
Flash latest official TWRP and try again.
Click to expand...
Click to collapse
Thanks, solved
Related
Please make a working guide/tutorial to install the Official Cyanogenmod 12 on Moto G XT1033 which has been converted to GPe 5.0.1.And pls provide a fix to make the sims work, even one working sim is good if not the both of them.
Thanks...
1. Take a backup of your Current rom first
2.download any cm12 rom and place it in the root of the SD card
3. Boot in to twrp recovery and do factory reset
4. Flash CM12 rom
5. Flash donkey kernel..
6.reboot and check..
7. If not working, restore your backup
But this doesn't work for the Official Cyanogenmod Nightly.
modifan14 said:
But this doesn't work for the Official Cyanogenmod Nightly.
Click to expand...
Click to collapse
How long did you wait on the first boot? It can take like...10 minutes.
modifan14 said:
Please make a working guide/tutorial to install the Official Cyanogenmod 12 on Moto G XT1033 which has been converted to GPe 5.0.1.And pls provide a fix to make the sims work, even one working sim is good if not the both of them.
Thanks...
Click to expand...
Click to collapse
I have the same problem. I have gpe 5.0.1 bootloader and all recovery can't flash cm12 nightly : flash error with twrp 2.8.3, Phil'z and CWM.
Quentinga said:
I have the same problem. I have gpe 5.0.1 bootloader and all recovery can't flash cm12 nightly : flash error with twrp 2.8.3, Phil'z and CWM.
Click to expand...
Click to collapse
Are you getting the error about mounting /system? I tried the 2.8.1.0 version of TWRP and was able to mount the /system partition successfully. I haven't had the time to flash a rom but you can try if this version works for you.
andogeek10 said:
Are you getting the error about mounting /system? I tried the 2.8.1.0 version of TWRP and was able to mount the /system partition successfully. I haven't had the time to flash a rom but you can try if this version works for you.
Click to expand...
Click to collapse
No: my log
flash history
-- Installing: /sdcard/0/cm-12-20150107-NIGHTLY-falcon.zip
Finding update package...
Opening update...
Installing update...
E: Error in /data/media/0/cm-12-20150107-NIGHTLY-falcon.zip
(Status 1)
Installation aborted.
Click to expand...
Click to collapse
cwm log
-- Installing: /sdcard/0/cm-12-20150107-NIGHTLY-falcon.zip
Finding update package...
I : Update location : /data/media/0/cm-12-20150107-NIGHTLY-falcon.zip
Opening update...
Installing update...
about to run program [/tmp/backuptool.sh] with 2 args
Not backing up files from incompatible version: 12
run_program: child exited with status 127
about to run program [/tmp/otasigcheck.sh] with 1 args
erasing 249856 blocks
blkdiscard failed: Invalid argument
writing 111672 blocks of new data
lseek64 failed: Invalid argument
E : Error in /data/media/0/cm-12-20150107-NIGHTLY-falcon.zip
(Status 1)
Installation aborted.
I : using /data/media for /sdcard/0/clockworkmod/ .last_install_path.
I : Cannot load volume /misc.
Return to menu with any key.
Click to expand...
Click to collapse
That's because of the updated partition table. I also had the same error on GPE 4.4.4. Try flashing vanir, it worked for me.
Hi,
I've got TWRP 3.0.2-0 recovery installed with CM12.1.1 YOG7DAS2K1 and am receiving the OTA update for CM13.0 ZNH0EAS2JK Incremental but the installation fails with an error message in recovery saying it's expecting "YOGDAS2K1" level but finds "YOG4PAS1N0". This happens whether I re-enable the CM Recovery update or not.
I found a thread here on XDA linking to all CM official updates. I flashed the recovery from "cm-12.1-YOG7DAS2K1-bacon-signed-fastboot" successfully and then tried the update again but it still failed. Again, happens whether I have CM Recovery update enabled or not.
Verifying current system...
system partition has unexpected contents
E : Failed to install @/cache/recovery/block.map
Click to expand...
Click to collapse
So now I flashed TWRP again. Does someone know what I should do to install the update ? Preferably without returning to stock first.
Solved
Feeling a bit stupid really...
Right under my post in the list was this post which deals with my problem exactly. I just updated my phone using that guide.
while installing zip using twrp
it is showing updater process ended with error 7 and installation failed
Tony19 said:
while installing zip using twrp
it is showing updater process ended with error 7 and installation failed
Click to expand...
Click to collapse
First check rom that it build for your model number only. If you want solution may be these guide help you.
https://forum.xda-developers.com/showthread.php?t=2522762&page=1
I have downloaded the latest official LineageOS build ( lineage-14.1-20170705-nightly-kenzo-signed.zip) for the Redmi Note 3 Kenzo. Then I tried to install this ROM from TWRP (3.0.2-2) on my Redmi Note 3 kenzo, and I got the following error message:
Code:
assert failed : xiaomi.verify_modem("MSM8976.LA.1.0.c3-30041-STD.PROD-1.77504.1.83742.1") == "1"
update process ended with error 7
I did some research on this and found out that a lot of others faced the same and one of the solutions for this is to install latest Dev Build of MIUI, which I did (MIUI 7.7.6 Global Beta) before flashing Lineage, but still failed.
From some other source, I got another solution stating that I should try by removing the assert check from the update-script in LineageOS package (zip) , but I am not sure if it will be harmless or not.
What should I do to successfully flash my device with the latest Lineage (or RessurectionRemix). I am stuck for last 2-3 days. It would be great if I am provided with some thorough procedures as I am kind of new to this whole "flashing custom rom" things.
HostileSage said:
I have downloaded the latest official LineageOS build ( lineage-14.1-20170705-nightly-kenzo-signed.zip) for the Redmi Note 3 Kenzo. Then I tried to install this ROM from TWRP (3.0.2-2) on my Redmi Note 3 kenzo, and I got the following error message:
I did some research on this and found out that a lot of others faced the same and one of the solutions for this is to install latest Dev Build of MIUI, which I did (MIUI 7.7.6 Global Beta) before flashing Lineage, but still failed.
From some other source, I got another solution stating that I should try by removing the assert check from the update-script in LineageOS package (zip) , but I am not sure if it will be harmless or not.
What should I do to successfully flash my device with the latest Lineage (or RessurectionRemix). I am stuck for last 2-3 days. It would be great if I am provided with some thorough procedures as I am kind of new to this whole "flashing custom rom" things.
Click to expand...
Click to collapse
Been facing the same issue, read somewhere that flashing latest firmware will resolve that error 7 , and I flashed but nothing happened..
Looking for a way like you..
suniluv said:
Been facing the same issue, read somewhere that flashing latest firmware will resolve that error 7 , and I flashed but nothing happened..
Looking for a way like you..
Click to expand...
Click to collapse
I have removed the assert check from the script and it worked. I am using the ROM for last 2 months and it's working smmothly.
I've tried to flash a custom rom (Corvus OS,) but it always ends in an error saying
"Updater process ended with signal: 4
Error installing ZIP file (then here's the path)
Updating partition details...
...done"
I'm not sure what to do. The phone is a Redmi Note 7 lavander, Orange Fox is the latest (I just installed it today.)
AuFox0912 said:
I've tried to flash a custom rom (Corvus OS,) but it always ends in an error saying
"Updater process ended with signal: 4
Error installing ZIP file (then here's the path)
Updating partition details...
...done"
I'm not sure what to do. The phone is a Redmi Note 7 lavander, Orange Fox is the latest (I just installed it today.)
Click to expand...
Click to collapse
Different ROM and different custom recovery but same issue:
Update Error signal 4 while installing LineageOS ROM
Here is the guide to help you Update Error signal 4 while installing lineageos rom. Follow the guide carefully to get rid of Error 4.
officiallineageos.com
A little update. Have tried other roms (Evolution X and Havoc,) and both have been successful. Is probably something about the rom (or maybe something I did wrong, or something wrong with my phone.)