Related
Hi all. I keep getting this error after rooting, installing SuperSu and TWRP. When I try to flash a ROM (any ROM), I get stuck. I've tried the latest Resurrection and CM ROMS. Will someone please help me past this last hurdle? Thank you!
I can't upload or link the screenshot but here's the info:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
Which I have done several times.
Backup ==> select all ==> Swipe to Backup
Wipe ==> Advenced Wipe ==> /System + /Data + /Cache Confirm "Swipe to Wipe" . Try installing again ROM
maxprzemo said:
Backup ==> select all ==> Swipe to Backup
Wipe ==> Advenced Wipe ==> /System + /Data + /Cache Confirm "Swipe to Wipe" . Try installing again ROM
Click to expand...
Click to collapse
That did the trick! I put Resurrection OS on there and all is well except for finding a stable GAPPS build.
Not working for me, my device is KII-L21 on stock rom and I'm trying to install official CM13, my device is rooted and have twrp
If your device is wiped It isnt rooted.. Wipe it dont forget Cache partitions try again.
maxprzemo said:
Backup ==> select all ==> Swipe to Backup
Wipe ==> Advenced Wipe ==> /System + /Data + /Cache Confirm "Swipe to Wipe" . Try installing again ROM
Click to expand...
Click to collapse
Bro, me sirvió. Muchas gracias
It really works, thanks dude
I think it all boils down to doing a format /system.
Next time I will try that!
Edit: I was wrong, the format /data is needed.
If I don't to the reset I am one of those that always gets error 7.
unmount ->system, data, cache :good:
As I already posted at https://forum.xda-developers.com/showpost.php?p=70851854&postcount=534,
I am able to avoid the Error 7 (inconsistend data) by switching to gapps mini before installing the update.
Since the experiental build, I do the following within one TWRP session: install latest gapps mini, install the upgrade to latest lineage-nightly and reinstall latest gapps stock.
So far it works for me.
Do a clean install wiping system, data, cache and dalvik cache before flashing a new ROM is adviced, it will avoid most of problems. For the GApps, I recommend OpenGapps Pico version to install the minimal needed, then you can install the other Google apps you need from the Play Store.
Guys I need some help here. I'm running into the same TWRP error 7 situation. The phone is unlocked, and I've installed kiwi_twrp_3-21_recovery. The model of the device is Honor X5 (KIW-CL00)
I've tried flashing both ResurrectionRemix-M-v5.7.4-20161220-kiwi & lineage-14.1-20170419-nightly-kiwi-signed ROM, whether it's flashing from the phone's storage or from the SD card, both ROM are giving me the same error code.
I tried formatting the system, advance wipe function (Dalvik & Cache & Data & System), now I don't even have the default factory ROM on my phone, but I'm still getting the error 7 code.
Please help. Thanks in advance.
U need to edit updater script to remove assert for device check
Error7 and then "could not find meta inf..."
Huawei KIWI Honor 5x
KIW-L21 EMUI 3.1
I installed
TWRP3.0.2-0 lineage-14.1-20170607-nightly-kiwi-signed.zip ->Error 7
then
cm-13.0-20160904-NIGHTLY-kiwi.zip and cyanogen recovery the same -> Error 7
Error 7 and if I try to delete assert, the next message is "could not find meta inf/com/google/android/update-binary"
My last problem
If I unzip and zip without change anything the Install message is "could not find..." I try it whit Linux 16.4 Win10 Win7 and 7Zip. all the same.
I can not change the updater-script without unpacking the File
Can anybody Help
robert_web said:
Huawei KIWI Honor 5x
KIW-L21 EMUI 3.1
I installed
TWRP3.0.2-0 lineage-14.1-20170607-nightly-kiwi-signed.zip ->Error 7
then
cm-13.0-20160904-NIGHTLY-kiwi.zip and cyanogen recovery the same -> Error 7
Error 7 and if I try to delete assert, the next message is "could not find meta inf/com/google/android/update-binary"
My last problem
If I unzip and zip without change anything the Install message is "could not find..." I try it whit Linux 16.4 Win10 Win7 and 7Zip. all the same.
I can not change the updater-script without unpacking the File
Can anybody Help
Click to expand...
Click to collapse
Did you try this?
Backup ==> select all ==> Swipe to Backup
Wipe ==> Advenced Wipe ==> /System + /Data + /Cache Confirm "Swipe to Wipe" . Try installing again ROM
robert_web said:
Huawei KIWI Honor 5x
KIW-L21 EMUI 3.1
I installed
TWRP3.0.2-0 lineage-14.1-20170607-nightly-kiwi-signed.zip ->Error 7
then
cm-13.0-20160904-NIGHTLY-kiwi.zip and cyanogen recovery the same -> Error 7
Error 7 and if I try to delete assert, the next message is "could not find meta inf/com/google/android/update-binary"
My last problem
If I unzip and zip without change anything the Install message is "could not find..." I try it whit Linux 16.4 Win10 Win7 and 7Zip. all the same.
I can not change the updater-script without unpacking the File
Can anybody Help
Click to expand...
Click to collapse
Pleasw upgrade to TWRP 3.1.1
Sent from my Honor 8 using XDA Labs
robert_web said:
Huawei KIWI Honor 5x
KIW-L21 EMUI 3.1
I installed
TWRP3.0.2-0 lineage-14.1-20170607-nightly-kiwi-signed.zip ->Error 7
then
cm-13.0-20160904-NIGHTLY-kiwi.zip and cyanogen recovery the same -> Error 7
Error 7 and if I try to delete assert, the next message is "could not find meta inf/com/google/android/update-binary"
My last problem
If I unzip and zip without change anything the Install message is "could not find..." I try it whit Linux 16.4 Win10 Win7 and 7Zip. all the same.
I can not change the updater-script without unpacking the File
Can anybody Help
Click to expand...
Click to collapse
U need to edit and repack everything . And do remember that if u mess a single letter it will give an error
Thanks
Sure I wipe advanced by every attempt.
Twrp 3.1.1 the same problem.
But you have right, the Solution for me is not to unzip and zip the file for delete the "assert". Only the way to edit without unpack the File in the Ubuntu "ARCHIVMANAGER" works.
Now it is installed but now I am in a bootloop But this is an other Problem. One step after another.
robert_web said:
Thanks
Sure I wipe advanced by every attempt.
Twrp 3.1.1 the same problem.
But you have right, the Solution for me is not to unzip and zip the file for delete the "assert". Only the way to edit without unpack the File in the Ubuntu "ARCHIVMANAGER" works.
Now it is installed but now I am in a bootloop But this is an other Problem. One step after another.
Click to expand...
Click to collapse
try again by making a clean flash
robert_web said:
Thanks
Sure I wipe advanced by every attempt.
Twrp 3.1.1 the same problem.
But you have right, the Solution for me is not to unzip and zip the file for delete the "assert". Only the way to edit without unpack the File in the Ubuntu "ARCHIVMANAGER" works.
Now it is installed but now I am in a bootloop But this is an other Problem. One step after another.
Click to expand...
Click to collapse
So , plz upload the updater-script here . I will edit and forward u . Later repack everything as is, lets see if that works . If not , i will build a rom for u especially
Thanks its work fine now. It was my fault, I updated from Lollipop not from Nougat. So I used Huawei Firmbootextraktor extract system.img cust.img recovery.img and boot.img and on my SD I copy ../dload/update.app version B140 Android 5.1.1. Then the Handy started I updated EMUI 4.0 and Android 6.1. Now works my Handy with all zip files where I delete the asserts.
Maybe was the problem, in the assert is wrote "kiwi" and my Handy is a "KIW-L21"
I try update via recovery ( put this file to external strorage only )
1. boot to recovery mode hold Power + Volume Down button
2. Using the Volume buttons to scroll and the Power button to select, choose "Enter
recovery mode
3. Choose apply update from external storage
4. select "reboot system now after finished update
http://fota.asus.com/delta_package/.../WW_PF500KL-12.2.2.43-13.6.5.30-fota-user.zip
This screenshoot from my phone +Station
Error Status 7
I have error:
System partition has unexpected contents
E:Error in /sdcard/UL-ASUS_TOON-WW-13.6.5.30-user.zip
(Status 7)
anyone can help me?!
Same issue as well
Getting the same "System partition has unexpected contents (Status 7 )" any idea whats wrong?
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Gizoid1337 said:
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Click to expand...
Click to collapse
Thanks ! It worked for me
I reinstalled ver 12.2.2.43 which really is my current version, and then proceed to install MM 13.6.5.30 with success
Gizoid1337 said:
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Click to expand...
Click to collapse
Thanks to you I have updated my phone to marshmallow using twrp 3.0.0, which allowed me to re-unlock bootloader, and root my phone.
It can be done, you just need to remove a few lines in the updater-script file.
something with ro.fingerprint (that identifies the recovery, it was originally expecting stock).
Replace it inside the zip. Then transfer update to sd card or internal.
After that wipe system, then reflash .43, right after that flash the mm update.
Will take some time but it should work once everything is verified.
reflash bl unlock and twrp (just a precaution) , then you can leave.
It would say no os but ignore it.
First boot takes around 10-15 mins then presto you finally have it.
Haven't encountered any bugs yet and it freed up a lot of storage space. Makes me wonder why I had to wait for the update to come to me, so glad I'm done with that.
So that concludes the last major update for the padfone s.....
Can u help me pls? I've tried unroot ,wipe system data and reflash .43 which is my current rom but still got signature verification error. any suggestion to fix this? Thx
Justatechie said:
Thanks to you I have updated my phone to marshmallow using twrp 3.0.0, which allowed me to re-unlock bootloader, and root my phone.
It can be done, you just need to remove a few lines in the updater-script file.
something with ro.fingerprint (that identifies the recovery, it was originally expecting stock).
Replace it inside the zip. Then transfer update to sd card or internal.
.
Click to expand...
Click to collapse
which lines exactly ? cause i tried removing mine and im now getting an error in the zip
error 6 or something
dtgo said:
which lines exactly ? cause i tried removing mine and im now getting an error in the zip
error 6 or something
Click to expand...
Click to collapse
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
NightbladeSinX said:
Can u help me pls? I've tried unroot ,wipe system data and reflash .43 which is my current rom but still got signature verification error. any suggestion to fix this? Thx
Click to expand...
Click to collapse
Thats odd.
You should probably Re-download or transfer the ww file again. Could just be a bad transfer of data.
Make sure you have twrp 3.0.0 and that system protection off. (it pops up on the first screen, but you can find it under twrp settings)
Justatechie said:
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
Click to expand...
Click to collapse
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
dtgo said:
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
Click to expand...
Click to collapse
If it doesn't say anything about identifying the device model or checking system, then something is wrong.
Might be a bad edit or it might have gotten corrupted while transferring back into the zip.
I stick with N++ for the edits, sometimes windows file transfer can be a pain by itself while trying to replace the update script, 7zip might help.
dtgo said:
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
Click to expand...
Click to collapse
got it working thanks again man you've been a big help
Justatechie said:
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
Thats odd.
You should probably Re-download or transfer the ww file again. Could just be a bad transfer of data.
Make sure you have twrp 3.0.0 and that system protection off. (it pops up on the first screen, but you can find it under twrp settings)
Click to expand...
Click to collapse
Thx for reply. i manage to get updated to 6.0.1 but now i lost root. i did mistake not flashing twrp before 1st boot n it replace twrp to stock rec. Is there any root method available yet? I've tried latest kingroot but it was unsuccessful. Any way is there any difference between WW and TW firmware version?
NightbladeSinX said:
Thx for reply. i manage to get updated to 6.0.1 but now i lost root. i did mistake not flashing twrp before 1st boot n it replace twrp to stock rec. Is there any root method available yet? I've tried latest kingroot but it was unsuccessful. Any way is there any difference between WW and TW firmware version?
Click to expand...
Click to collapse
You could probably flash recovery through fastboot, only if your bootloader is unlocked. If not it wont allow the flash. it would say FAILED cant flash unsigned image, but theres a chance that it might have been flashed, just check to see if changes have applied.
Assuming that you have went to the fastboot portion of your phone you can check its status.
if its not unlocked, then you have to find another way to root to flash your twrp recovery back on your phone.
Did this, but kept getting errors due to (probably) my use of xposed. Managed to soft brick my phone, and recovered it using http://forum.xda-developers.com/padfone-x/help/guide-restoring-stock-rom-recovery-t3179818
After that, had to edit updater-script to remove all checks.
What tripped me up was just how long the update reboot took. Almost half an hour. I was going to give up but decided to leave it while taking a short nap.
heres the updater script for anyone having issues
Please can someone help me?
I'm trying so hard to get this to work but I'm barely getting anywhere. What I've done (thanks to ninekaw9's guide):
- unlock bootloader
- wiped everything (yet there is still stuff in the file explorer, like the su install folder)
- using fastboot boot recovery:
-- use TWRP 2.8.7.0 to transfer files from sdcard to emmc
-- with TWRP 2.7.1.1:
--- installed WW 99.99.99.0 for KK (works)
--- installed WW 12.2.2.27 for LP & stock recovery (works)
--- installed WW 12.2.2.43 for latest LP (works)
- removed every abort line from updater script to get it to stop complaining about fingerprint/unexpected system contents
- installed modified FOTA WW 13.6.5.30 for MM (no OS change)
So after all that, I'm where I started but with no apps.
Before I found out 2.8.7.0 couldn't flash stock ROMs I flashed 12.2.2.43 after a full wipe and ended up with no System UI...
Outcomes from using different recovery to flash MM update:
2.7.1.1 with unmodified: apparently my phone is TW not WW (incorrect)
2.8.7.0 with unmodified: some weird fingerprint with omni-T00N and 5.1.1, even after wipe and stock 12.2.2.43 flash. Couldn't edit or replace the default.prop file, it would just get overwritten each time
stock with unmodified: couldn't even mount my SD card, so tried ADB sideload, got the unexpected system contents message
stock with modified (no sha1): would no longer allow me to ADB sideload (0.00x message)
TWRP (either) with modified (no prop): unexpected system contents
TWRP (either) with modified (no prop/sha1): seems to work, but upon boot to system, nothing appears to have changed.
I desperately want MM so I have a smaller system partition, then I can stop pushing updates to system to save space, and therefore won't need root so I can play Pokemon GO and use Sky Q.
That or I'm going to try Magisk... Has anyone used this on a Padfone?
If anyone can guide me through which files/folders I can delete from my phone to save space, that would be great. I know most folders are mounting points, but there's a lot of .sh files and other folders that I'm not familiar with.
I've asked in another thread where I can get TWRP 3.x for Padfone S, but nobody has replied!
Please can someone help me?
Nintynuts said:
I'm trying so hard to get this to work but I'm barely getting anywhere. What I've done (thanks to ninekaw9's guide):
- unlock bootloader
- wiped everything (yet there is still stuff in the file explorer, like the su install folder)
- using fastboot boot recovery:
- use TWRP 2.8.7.0 to transfer files from sdcard to emmc
- with TWRP 2.7.1.1:
- installed WW 99.99.99.0 for KK (works)
- installed WW 12.2.2.27 for LP & stock recovery (works)
- installed WW 12.2.2.43 for latest LP (works)
- removed every abort line from updater script to get it to stop complaining about fingerprint/unexpected system contents
- installed modified FOTA WW 13.6.5.30 for MM (no OS change)
So after all that, I'm where I started but with no apps.
Before I found out 2.8.7.0 couldn't flash stock ROMs I flashed 12.2.2.43 after a full wipe and ended up with no SystemUI...
Outcomes from using different recovery to flash MM update:
2.7.1.1 with unmodified: apparently my phone is TW not WW (incorrect)
2.8.7.0 with unmodified: some weird fingerprint with omni-T00N and 5.1.1, even after wipe and stock 12.2.2.43 flash. Couldn't edit or replace the default.prop file, it would just get overwritten each time
stock with unmodified: couldn't even mount my SD card, so tried ADB sideload, got the unexpected system contents messagestock with modified (no sha1): would no longer allow me to ADB sideload (0.00x message)
TWRP (either) with modified (no prop): unexpected system contents
TWRP (either) with modified (no prop/sha1): seems to work, but upon boot to system, nothing appears to have changed.
I desperately want MM so I have a smaller system partition, then I can stop pushing updates to system to save space, and therefore won't need root so I can play Pokemon GO and use Sky Q.
That or I'm going to try hiding root Magisk...
If anyone can guide me through which files/folders I can delete from my phone to save space, that would be great. I know most folders are mounting points, but there's a lot of .sh files and other folders that I'm not familiar with.
I've asked in another thread where I can get TWRP 3.x for Padfone S, but nobody has replied!
Please can someone help me?
Click to expand...
Click to collapse
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
xantanion said:
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
Click to expand...
Click to collapse
Thanks. No wonder I couldn't find it as it doesn't mention 3.0.0.0 or 3.x or any version number at all.
I have answered my own Q&A thread with a link so hopefully others can find it. Will try it now.
xantanion said:
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
Click to expand...
Click to collapse
Thankfully it has worked many thanks. Unfortunately while Sky Q no longer complains about root, it does complain about my Padfone station being an external display, so still won't play videos
Hi guys.
I get this message in TWRP:
Failed to mount '/cpefs' (Read-only file system)
Does it mean something bad!?
Thanks guys.
Largewoodenspoon said:
Hi guys.
I get this message in TWRP:
Failed to mount '/cpefs' (Read-only file system)
Does it mean something bad!?
Thanks guys.
Click to expand...
Click to collapse
Same me
Sent from my SM-G965F using Tapatalk
what is your s9+ version?, it appear in twrp?
I have the same Problem with S9 plus G965F.
It boots permanent in Samsung Logo repeated.
even can not flash stock Firmware via Odin in download modus.
Can anyone help me please?
Flash latest twrp 3.2.1-2. This mesage "Failed to mount '/cpefs' (Read-only file system)" is gone.
Doesn't cause any issue, but updating to 3.2.1-2 fixes it as well as slow restore from backup as seen by the changelog on XDA
i have updated mine to 3.2.3-1 but it doesnt fix the problem, i tried following a couple of guides in youtube like changing the file system from ext4 to ext2 but still no luck, it didnt even let me change the file system for Data
i was on Android P when i tried that, but right now i just went back to full stock P without TWRP because i'm stuck with formatting Data (the most important part to clear out the restriction)
Any solution? i'm facing same.
I'm thinking of changing to f2fs on userdata and cache partition and use it with LOS (or crDroid) with DFE. However, I would have to format my internal storage for that. So just wondering if its worth the effort. For people already using it @ccelik97 others, please comment
Just do it, it will boost your performance a bit.
Just remember flashing the fstab file (mount vendor before).
And only format /data and /cache NOT /system
ext4 has faster reading speeds which is better for /system
I would also recommend to use Orange Fox Recovery which disables FE itself when you install a vendor package
using it just because - since it hasnt cause me any issues yet. There's almost no improvement as far as daily usage goes, but maybe it's just because I didnt spend much time with ext4 since I got the phone
VC-34 said:
Just do it, it will boost your performance a bit.
Just remember flashing the fstab file (mount vendor before).
And only format /data and /cache NOT /system
ext4 has faster reading speeds which is better for /system
I would also recommend to use Orange Fox Recovery which disables FE itself when you install a vendor package
Click to expand...
Click to collapse
Which ROM are you using with F2FS ?
Tried it with lineage OS (unofficial build) but it did not boot. Flashed Sphinx Kernel also, but again same result.
Mafioso said:
Which ROM are you using with F2FS ?
Tried it with lineage OS (unofficial build) but it did not boot. Flashed Sphinx Kernel also, but again same result.
Click to expand...
Click to collapse
Im on 9.4.12 Xiaomi.eu ROM but it works on every ROM just follow this steps when you make a clean flash:
1. flash ROM
2. mount vendor, flash fstab.zip
3. flash the other files (kernel, magisk, gapps)
and now reboot
let me know if it doesnt works:fingers-crossed:
VC-34 said:
Im on 9.4.12 Xiaomi.eu ROM but it works on every ROM just follow this steps when you make a clean flash:
1. flash ROM
2. mount vendor, flash fstab.zip
3. flash the other files (kernel, magisk, gapps)
and now reboot
let me know if it doesnt works:fingers-crossed:
Click to expand...
Click to collapse
Yeah, pretty much did the same thing. However latest version of orangefox recovery from blitzfire3 doesn't format it to f2fs by reading from fstab file. You have to change to f2fs i mean data and cache through partition options in ofox recovery wipe menu, after which it gets changed. Will try some other rom.
VC-34 said:
Just remember flashing the fstab file (mount vendor before).
Click to expand...
Click to collapse
Hey, I Can't Find An fstab File For Enabling f2fs On My Poco X3 Pro. Help
Hashman9820 said:
Hey, I Can't Find An fstab File For Enabling f2fs On My Poco X3 Pro. Help
Click to expand...
Click to collapse
Look into your boot image!
TWRP is unable to install any ROM on my G6 due to the "Digest verification failed" error.
I've updated TWRP to the latest version, which at the moment is 3.3.0.0.
I've try the [ROM][Stock] LG-H870 OPEN EU 20I ROM, Lineage and a few others, the situation is always the same.
I have placed the MD5 file next to the custom ROM file (the stock one above), I have searched for the solution for over 4 hours in youtube, (hindu-english sounds terrible...), xda, github and other sites, but haven't came up with the solution... TWRP is also showing that it is unable to read internal memory of the phone - I have to format DATA to exFat, and then back to ext4, than it can see internal storage.
I have downloaded the ROM files in SD card, and placed it into the phone, I have downloaded the ROM files directly through the phone via browser... nothing helps.
Any idea?
thread closed as per OP request