Database Users

How to flash back to stock kernel after using custom kernel ?

Well, Last night i tried franco kernel over my stock rom and now i want to go back to stock kernel itself. So to flash Franco kernel, i had to unlock the bootloader and installed TWRP Recovery and also rooted the phone with normal super su from chainfire website. I dunno what is systemless root cause i'm new here and never had any issues before with my old nexus device.. i'm little in knowledge regarding the Nexus 6P. So please guide me with a proper link to follow.. I googled and coudnt find the real sources.

Flash boot.img from bootloader using fastboot flash boot boot.img

sam razzy said:
Well, Last night i tried franco kernel over my stock rom and now i want to go back to stock kernel itself. So to flash Franco kernel, i had to unlock the bootloader and installed TWRP Recovery and also rooted the phone with normal super su from chainfire website. I dunno what is systemless root cause i'm new here and never had any issues before with my old nexus device.. i'm little in knowledge regarding the Nexus 6P. So please guide me with a proper link to follow.. I googled and coudnt find the real sources.
Click to expand...
Click to collapse
Get the factory images for the correct build of your stock ROM, extract the boot.img from the archive, and flash it with fastboot:
Code:
fastboot flash boot boot.img

Heisenberg said:
Get the factory images for the correct build of your stock ROM, extract the boot.img from the archive, and flash it with fastboot:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I solved it by installing wugs toolkit on my PC.. Thank you..
Sent from my Nexus 6P using Tapatalk

Heisenberg said:
Get the factory images for the correct build of your stock ROM, extract the boot.img from the archive, and flash it with fastboot:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Should I lose TWRP by doing this command. I seem to always loose my recovery doing android updates, or now when I went back to stock kernel using your instructions, on NEXUS 6P. I just flash the recovery back, but it's still weird.

GogoAkira said:
Should I lose TWRP by doing this command. I seem to always loose my recovery doing android updates, or now when I went back to stock kernel using your instructions, on NEXUS 6P. I just flash the recovery back, but it's still weird.
Click to expand...
Click to collapse
No TWRP is in the recovery partition. This command flashes the boot partition. On losing TWRP, try flashing SU immediately following TWRP before booting to the System for the first time. Then TWRP will stick.

I did per Heisenberg's instructions, it sticks, but still I lost it after this command that's why it's weird

Heisenberg said:
Get the factory images for the correct build of your stock ROM, extract the boot.img from the archive, and flash it with fastboot:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
To keep root and the custom recovery (TWRP) you need to do additional steps
Code:
fastboot reboot-bootloader
Code:
fastboot flash recovery recovery.img
Code:
fastboot reboot-bootloader
start recovery from bootloader
install SuperSU from TWRP

Heisenberg said:
Get the factory images for the correct build of your stock ROM, extract the boot.img from the archive, and flash it with fastboot:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
What's in the boot.img? Will it not reset or do something on the rom? Because I just wanted to restore the kernel .

Pawnzer said:
What's in the boot.img? Will it not reset or do something on the rom? Because I just wanted to restore the kernel .
Click to expand...
Click to collapse
It is the kernel.

Heisenberg said:
Get the factory images for the correct build of your stock ROM, extract the boot.img from the archive, and flash it with fastboot:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Can it be executed via recovery, install>select image file (boot.img)>choose boot partition>swipe
Or must via fastboot mode?

EASIEST way:
(No need to connect to PC & use fastboot)
— Extract your stock rom .zip,
— Copy 'boot.img' somewhere else on internal or external SD,
— In TWRP select 'flash .img',
— Flash 'boot.img', (DO NOT REBOOT!)
— Now flash your 'recovery.img' again in recovery.
DONE.
Now if you 'reboot to recovery' you still have TWRP, when you 'reboot' you are using the stock boot.img (kernel) too, no need for PC/Fastboot.
KEEP IN MIND!.... After flashing stock boot.img you will need to flash root again AND (depending on device) may trigger 'DM-verity' and/or 'Forced Encryption' (Oxygen OS and others) if you reboot straight away, so make sure if you do NOT want this to flash/re-flash 'DM-verity & force encryption disabler' .zip (search google/the forums here - zackptg5)
Hope this helps anyone in the future.

ErbDroid said:
EASIEST way:
(No need to connect to PC & use fastboot)
— Extract your stock rom .zip,
— Copy 'boot.img' somewhere else on internal or external SD,
— In TWRP select 'flash .img',
— Flash 'boot.img', (DO NOT REBOOT!)
— Now flash your 'recovery.img' again in recovery.
DONE.
Now if you 'reboot to recovery' you still have TWRP, when you 'reboot' you are using the stock boot.img (kernel) too, no need for PC/Fastboot.
KEEP IN MIND!.... After flashing stock boot.img you will need to flash root again AND (depending on device) may trigger 'DM-verity' and/or 'Forced Encryption' (Oxygen OS and others) if you reboot straight away, so make sure if you do NOT want this to flash/re-flash 'DM-verity & force encryption disabler' .zip (search google/the forums here - zackptg5)
Hope this helps anyone in the future.
Click to expand...
Click to collapse
Thank you so much for your instruction, Doing it step by step and karnel restored to stock!

Zenfone 3 doesn't boot to Android

Hi guys,
I try to restore my Zenfone 3 with his original firmware downloaded from Asus website. [Version WW_V13.20.10.79]
When i restart my phone, i got the first warning to let us know the bootloader is unlocked but after i got this error.
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
If i try to flash with TWRP with Install Zip, i got this error:
Code:
...
This package is for "WW_Phone" devices; this is a "omni_ze552kl".
Updater process ended with Error: 7
Error installing zip file '/sdcard/Download/<nameOfTheZipFile>.zip'
Updating partition details...
...done
(sorry i can't post image)
when i try fastboot recovery, it stuck to <waiting for device>.
This is my first time with Android, and rooting and all this sh*t. I'm coming from iOS jailbreak side but iTunes couldn't help me.
If you need to know anything, let me know.
I would greatly appreciate if anyone could help me.
Thanks!
SuperDizor
*English is not my first language, sorry about that*

SuperDizor said:
Hi guys,
I try to restore my Zenfone 3 with his original firmware downloaded from Asus website. [Version WW_V13.20.10.79]
When i restart my phone, i got the first warning to let us know the bootloader is unlocked but after i got this error.
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
If i try to flash with TWRP with Install Zip, i got this error:
Code:
...
This package is for "WW_Phone" devices; this is a "omni_ze552kl".
Updater process ended with Error: 7
Error installing zip file '/sdcard/Download/<nameOfTheZipFile>.zip'
Updating partition details...
...done
(sorry i can't post image)
when i try fastboot recovery, it stuck to <waiting for device>.
This is my first time with Android, and rooting and all this sh*t. I'm coming from iOS jailbreak side but iTunes couldn't help me.
If you need to know anything, let me know.
I would greatly appreciate if anyone could help me.
Thanks!
SuperDizor
*English is not my first language, sorry about that*
Click to expand...
Click to collapse
I used to be difficult to use TWRP menu, then the menu advanced Wipe Wipe then select all topics except the MicroSD and then manage Otg Wipe it !! Flash Stock Recovery to be done to make Flash official rom first official rom files onto the MicroSD example, I was. UL-ASUS_Z012D-WW-13.20.10.79-user. To change its name Then insert the MicroSD MOFD_SDUPDATE Recovry Mode, then select update to zip and then choose File. "MOFD_SDUPDATE.zip" I will wait a little longer for the update firmware and set up virtually everything is not lost through the OTA.
ผมเคยเป็นแก้ไม่ยากใช้ TWRP แล้วเข้าเมนู Wipe แล้วเข้าเมนู advanced Wipe ทำการเลือกทุกหัวข้อ ยกเว้น MicroSD และ Otg แล้วจัดการ Wipe ครับ!! เสร็จแล้วให้ทำการ Flash Stock Recovery เพื่อที่จะใช้ Flash official rom ก่อนอื่นทำไฟล์ official rom ลงไปยัง MicroSD ผมยกตัวอย่างเป็น UL-ASUS_Z012D-WW-13.20.10.79-user ให้เปลี่ยนชื่อเป็น MOFD_SDUPDATE แล้วนำใส่ MicroSD แล้วเข้า Recovry Mode แล้วเลือก update to zip แล้วทำการเลือกไฟล์ "MOFD_SDUPDATE.zip" แล้วรอสักพักอาจจะนานหน่อยเพราะเป็นการ update firmware ข้อมูลและการตั้งค่าทุกอย่างจะไม่หายเสมือนอัพผ ่าน OTA

I was able to fix my phone with flashing both boot.img and recovery.img with stock image and i used WW-13.16.5.36 firmware to flash and it's worked.
Thanks for the help JadeKubPom

SuperDizor said:
I was able to fix my phone with flashing both boot.img and recovery.img with stock image and i used WW-13.16.5.36 firmware to flash and it's worked.
Thanks for the help JadeKubPom
Click to expand...
Click to collapse
I got the same issue, where did you get these files?

roosevelt84 said:
I got the same issue, where did you get these files?
Click to expand...
Click to collapse
I have the exact same error. Same here. Please someone can post download link.

SuperDizor said:
Hi guys,
I try to restore my Zenfone 3 with his original firmware downloaded from Asus website. [Version WW_V13.20.10.79]
When i restart my phone, i got the first warning to let us know the bootloader is unlocked but after i got this error.
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
If i try to flash with TWRP with Install Zip, i got this error:
Code:
...
This package is for "WW_Phone" devices; this is a "omni_ze552kl".
Updater process ended with Error: 7
Error installing zip file '/sdcard/Download/<nameOfTheZipFile>.zip'
Updating partition details...
...done
(sorry i can't post image)
when i try fastboot recovery, it stuck to <waiting for device>.
This is my first time with Android, and rooting and all this sh*t. I'm coming from iOS jailbreak side but iTunes couldn't help me.
If you need to know anything, let me know.
I would greatly appreciate if anyone could help me.
Thanks!
SuperDizor
*English is not my first language, sorry about that*
Click to expand...
Click to collapse
I found a solution, and now my ZF3 is working but its showing a second screen with a error when it boots.
1 - download a zip file rom from asus site
2 - open it with winrar or another of your choice
3 - go to \META-INF\com\google\android
4 - open the updater-script with a text editor
5 - search for all the words WW_Phone and replace it for omni_ze552kl
6 - save the change and close, update the file inside the compressed zip
7 - put the zip rom inside your phone and flash it through twrp, done!
*sorry about english, its not my native lang.

Hi SuperDizor,
The issues you are having are both caused by the installation of TWRP 3.0.2. that was compiled for the Zenfone 3 using omni_ze55kl as the device type instead of WW_ZE552KL or CN_ZE552KL. I assume that the person that compiled it tried to make TWRP as universal as possible (instead of making two different versions, one for each device type - the TWRP code would have been the same except for this string...). However, the updater checks for this device type string and fails (unless you modify the updater config file as described in the post above). This is also why flashing stock recovery solved your issue.
The second error message you have, the one with dm-verity not being in enforcing mode was caused by having you install TWRP and allowing it to modify the system partition. This was necessary in the past but not anymore. When you flash TWRP, the first time you start it, it ask for your permission the make the system read-write, and you should refuse, as TWRP will function anyway and you will not get the dm-verity error. The dm-verity thingy is a software module in the bootloader (aboot to be precise) that checks the integrity of the system partition. TWRP has to force it in non-enforcing mode since it modifies the system partition and your device would not boot if it left dm-verity in enforcing mode. When you don't let TWRP modify the system partition (ie staying read-only), it does not change the dm-verity mode and you don't get warning messages. Don't worry, TWRP will still enable you to root your device and do whatever it does even if it is in "read only" mode.
Hope this helps !

I just got this error seemingly out of the blue on my ZenFone 3 Laser. I didn't do anything, just walked up and it was showing this screen
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
Haven't rooted, unlocked bootloader, or tried to install any rom manually.

Same happened with my device too. How did you fix it? Can you please let me know the procedure for same.
---------- Post added at 03:26 AM ---------- Previous post was at 03:24 AM ----------
Niemer said:
I just got this error seemingly out of the blue on my ZenFone 3 Laser. I didn't do anything, just walked up and it was showing this screen
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
Haven't rooted, unlocked bootloader, or tried to install any rom manually.
Click to expand...
Click to collapse
Same happened with my device too. How did you fix it? Can you please let me know the procedure for same. Thanks

SuperDizor said:
I was able to fix my phone with flashing both boot.img and recovery.img with stock image and i used WW-13.16.5.36 firmware to flash and it's worked.
Thanks for the help JadeKubPom
Click to expand...
Click to collapse
but how to flash? its not booting in recovery mode.

Asus Zenfone 5 t00j a500cg | fastboot works I can not install stock or custom rom

A blessed day to all who read and many thanks to those who will help.
I will not confuse you with a long back story. My goal is to update to lollipop but this is where I am at:
fastboot works but I have no OS (having wiped out system folder)
i can install TWRP-2870_Zenfone5.img or recovery_philz_t00f.img. The stock recovery image from UL-ASUS_T00F-WW-2.22.40.53-user.zip only results in a dead droidboot logo (with red exclamation mark)
installing from firmware.zip SD card doesnt work, I will recreate the error messages
E: Unknown File System: 'osip'
E: Unknown File System: 'osip'
E: Unknown File System: 'osip'
E: Unable to find partition size for '/misc'
E: Unable to find partition size for '/splashscreen'
Updating partition details . . .
. . . done
Full SELinux support is present.
E: Unable to set bootloader message.
MTP Enabled
Installing '/external_sd/UL_ASUS_T00F-WW-2.22.40.53-user.zip'. . .
Checking for MD5 file . . .
Skipping MD5 check: no MD5 file found
Error flashing zip '/external_sd/UL_ASUS_T00F-WW-2.22.40.53-user.zip'
Updating partition details . . .
. . . done
Click to expand...
Click to collapse
installing from adb sideload doesnt work. error: closed
I need your help, I have spent 2 days in Google, Asus.com Zentalk and this amazing forum. I need to install the stock ROM and upgrade to Lollipop.
Thanks in advance.
ASUS Zenfone 5 t00j a500cg WW
IFWI 59.A1
Droidboot 2.1

UPDATE
I finally got an OS by following this: link
Quote:
Originally Posted by dgadelha
Hello,
There can be a way to solve your problem
(this solution also can be useful for any other broken systems)
ZENFONE 5 (T00F, T00J) ONLY!
Required downloads:
Jelly Bean Firmware
Intel USB Drivers
ADB+Fastboot
Offline Update Image Script
Steps:
Install the Intel USB Drivers
Rename the Jelly Bean Firmware file, changing the extension from .raw to .zip
Create a directory for all the files (e.g.: C:\zenfone)
Extract the contents of the Jelly Bean Firmware and ADB+Fastboot on the directory you just created
Copy the file of Offline Update Image Script (sec_offline_update_image.cmd) to the same directory
Shutdown your phone and start in droidboot mode (Power + Vol. Up)
Plug the USB
Assert that your device is connected, check by running the command fastboot devices on a Command Prompt
Go to the directory you created before and run the file sec_offline_update_image.cmd as administrator
When your device reboot again into bootloader, check if there was no errors (the userdata erase error can be ignored with no problems). If there was any error, I recommend you to go back and check if you done all steps correctly. If not, just use the volume buttons to select the option 'Reboot' and activate it by pressing the Power key
After this is done, you can upgrade to KitKat or Lollipop via recovery, just download the update from Asus site and sideload it via ADB.
Thanks!
Click to expand...
Click to collapse
adb sideload works
SD card to internal memory copying of stock firmware UL-ASUS_T00F-WW-2.22.40.53-user.zip works when I restart the phone, it detects the system update
but now I get the following error
E:end of footer from data/media/0/UL-ASUS_T00F-WW-2.22.40.53-user.zip failed not 0xFFFF (file exists)
E:signature verification failed
E:Install of data/media/0/UL-ASUS_T00F-WW-2.22.40.53-user.zip failed with status 2
Installation aborted.
E:Installation failed with status 2
E:Can't open tmp/update-script.log
E:Can't load volume/misc!
Click to expand...
Click to collapse
Any ideas how I can get past this?

UPDATE #2 [SOLVED]
I initially thought of going ladder steps up but then out of curiosity searched for ASUS Zenfone 5 Marshmallow and came across this.
Here is what I did:
1. Unlocked bootloader (cause it was initially locked)
fastboot flash fastboot fastboot_unlocker.img
fastboot reboot-bootloader
fastboot flash dnx dnx_fwr_ctp_a500cg.bin
fastboot flash ifwi ifwi_ctp_a500cg_unlock.bin
fastboot reboot-bootloader
Click to expand...
Click to collapse
2. Downloaded and flashed boot image. I used cm13-zenfone5-kernel.img
fastboot flash boot cm13-zenfone5-kernel.img
Click to expand...
Click to collapse
3. Downloaded and flashed recovery image. I used TWRP.img
fastboot flash recovery TWRP.img
Click to expand...
Click to collapse
4. Downloaded and flashed system image. I used cm13-zenfone5-system.img
fastboot flash system cm13-zenfone5-system.img
Click to expand...
Click to collapse
5. Erased unneeded files
fastboot erase data
fastboot erase userdata
fastboot erase cache
Click to expand...
Click to collapse
6. I installed open_gapps-x86-6.0-pico-20200207.zip (Open Google Apps Pico version)
7. I did some memory cleaning factory reset then dalvik cache and cache wipe
8. My TWRP froze on reboot system so I unplugged/replugged the USB cable then I did an adb reboot which is the same thing as Power+Volume Up button.
Click to expand...
Click to collapse
And voila! A running marshmallow OS on Asus Zenfone 5 t00j a500cg.
Overall, I spent 2 days trying to do this but it was well worth it. My son is very happy he can now play his MOBA faster than the original bloated KitKat OS. Same hardware, better software. Overall, I enjoyed the learning experience and the joy of being appreciated by my son.

Problem flashig new roms: TWRP unable to mount Data/media/twrp/.twrps

Hello everybody!
To defeat planned obsolescence of my Zenfone 3 (ZE520KL) I've decided to root it and install an alternative ROM.
With much difficulty at the end I achive root it but I've a problem flashing roms.
- Unloked OK
- To flash and fix TWRP I used Magistik (without it TWRP starded only when phone was connected to pc)
Now Root Checker says my phone is rooter, Magistik is correctly installed and TWRP seems ok. So I felt in 90% of my challenge!
But…
When I try to flash a ROM in TWRP lots of red line appear…
Data successfully decrypted, new block device: '/dev/block/dm-0'
Updating partition details…
...done
Unable to mount storage
Successfully decrypted with default password.
Updating partition details
…..done
Unable to mount storage
Failed to mount '/data? (Invalid Argumetn)
Full SELinux support is present.
Unable to mount /data/media/twrp/.twrps
MTP Enabled
Installing zip file '/external_sd/PixelExperience_zenfone3_-9.0-20190823-1844-UNOFFICIAL.zip'
Checking for MD5 file…
Skipping MD5 check: no MD5 file found
Warnink: No file_context
E3004: This package is for device: Z017, ASUS_Z017_1D, ASUS_Z012D, ASUS_Z012DC, ASUZ_Z012S; this device is .
E:unknown command [log]
Update process ended with ERROR: 7
Error installing zip file '/external_sd/PixelExperience_zenfone3_-9.0-20190823-1844-UNOFFICIAL.zip'
Updating partition details…
...done
Unable to mount storage
Click to expand...
Click to collapse
The same thing happens with Lineage OS
In addition if I try to save the log I can't find it in the storage of the phone (really I don't know where it should be).
Maybe the Recovery [treble] proposed by Giovix92 can solve my problem?
Any other suggestion?
Thanks a lot to everybody!

twin-s said:
Hello everybody!
To defeat planned obsolescence of my Zenfone 3 (ZE520KL) I've decided to root it and install an alternative ROM.
With much difficulty at the end I achive root it but I've a problem flashing roms.
- Unloked OK
- To flash and fix TWRP I used Magistik (without it TWRP starded only when phone was connected to pc)
Now Root Checker says my phone is rooter, Magistik is correctly installed and TWRP seems ok. So I felt in 90% of my challenge!
But…
When I try to flash a ROM in TWRP lots of red line appear…
The same thing happens with Lineage OS
In addition if I try to save the log I can't find it in the storage of the phone (really I don't know where it should be).
Maybe the Recovery [treble] proposed by Giovix92 can solve my problem?
Any other suggestion?
Thanks a lot to everybody!
Click to expand...
Click to collapse
Might be due to encrypted partition.
Try
Code:
fastboot format userdata
in fastboot mode.
This will, as you might expect, wipe all your data. So be sure to backup first.
Also, the flashing error
Code:
E3004: This package is for device: Z017, ASUS_Z017_1D, ASUS_Z012D, ASUS_Z012DC, ASUZ_Z012S; this device is .
E:unknown command [log]
Update process ended with ERROR: 7
is from incompatible TWRP and ROM version. Are you using the latest TWRP?
As a last resort for the flashing error, try this https://forum.xda-developers.com/showthread.php?t=2522762

vaanish said:
Might be due to encrypted partition.
Try
Code:
fastboot format userdata
in fastboot mode.
This will, as you might expect, wipe all your data. So be sure to backup first.
Also, the flashing error
Code:
E3004: This package is for device: Z017, ASUS_Z017_1D, ASUS_Z012D, ASUS_Z012DC, ASUZ_Z012S; this device is .
E:unknown command [log]
Update process ended with ERROR: 7
is from incompatible TWRP and ROM version. Are you using the latest TWRP?
As a last resort for the flashing error, try this https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
Thank you vaanish!
I solved flashing an older versione of TWRP. The 3.3.1.
Now all is right!

Installing TWRP and LineageOS ROM over stock ROM

My phone is wt86047 with stock ROM, and I want to install TWRP then LineageOS. The process I do is the following:
1. From fastboot, flash latest TWRP twrp-3.6.1_9-0-wt88047.img using fastboot flash recovery twrp-3.6.1_9-0-wt88047.img
2. Boot into recovery, flash resize_wt88047x_v6.zip
3. Reboot into fastboot, enter fastboot -w
4. Phone goes into bootloop.
5. Flash stock ROM again with MiFlash.
6. I'm now back to step #1.
What am I doing wrong?

bomberb17 said:
What am I doing wrong
Click to expand...
Click to collapse
Skip step "3. Reboot into fastboot, enter fastboot -w" and try again. Are you executing fastboot -w because the flash script wants you to do this?

WoKoschekk said:
Skip step "3. Reboot into fastboot, enter fastboot -w" and try again. Are you executing fastboot -w because the flash script wants you to do this?
Click to expand...
Click to collapse
Yes, that is what the flash script tells me. If I skip step #3, then the partition containing lineage-19.1-20220323-UNOFFICIAL-wt88047x.zip is lost. Also TWRP recovery no longer works after the partition script.

bomberb17 said:
Yes, that is what the flash script tells me. If I skip step #3, then the partition containing lineage-19.1-20220323-UNOFFICIAL-wt88047x.zip is lost. Also TWRP recovery no longer works after the partition script.
Click to expand...
Click to collapse
what about using lineage recovery as recommended in this thread?
[ROM][12.1][UNOFFICIAL][wt88047x] LineageOS 19.1
Important information: This thread is for LineageOS 19.1 opensource builds for Wingtech WT88047, marketed as Redmi 2 by Xiaomi. The following will not be supported in this thread: Custom Kernels Mods Modified system files Xposed Magisk What's...
forum.xda-developers.com
Instead of flashing any zip you have to sideload them with ADB

Lineage recovery link is broken..
And what is the way to sideload lineage-19.1-20220323-UNOFFICIAL-wt88047x.zip? And after which step?

So after I install resize_wt88047x_v6.zip, I get:
"WARNING - TWRP DETECTED
Please reboot to fastboot and run the following:
fastboot -w
Done!"
I didn't reboot to fastboot this time, and I followed this process for the lineage rom
How to Install Custom ROM on Android via ADB Sideload
In this comprehensive tutorial, we will show you the detailed steps to install a Custom ROM on Android using ADB Sideload feature of TWRP.
www.droidwin.com
and the log says:
"..
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 1
mount -o bind '/data/media/0' '/sdcard' process ended with signal: 6"
Thoughts?

bomberb17 said:
So after I install resize_wt88047x_v6.zip, I get:
"WARNING - TWRP DETECTED
Please reboot to fastboot and run the following:
fastboot -w
Done!"
I didn't reboot to fastboot this time, and I followed this process for the lineage rom
How to Install Custom ROM on Android via ADB Sideload
In this comprehensive tutorial, we will show you the detailed steps to install a Custom ROM on Android using ADB Sideload feature of TWRP.
www.droidwin.com
and the log says:
"..
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 1
mount -o bind '/data/media/0' '/sdcard' process ended with signal: 6"
Thoughts?
Click to expand...
Click to collapse
You need to sideload it only in Lineage recovery and not in TWRP.
Try this:
1. flash resize_wt88047x_v6.zip
2. reboot into fastboot and run fastboot -w
3. start TWRP and go to Wipe > Format Data
4. reboot into TWRP
5. flash the ROM
If error still exists do not reboot and start ADB. Then run adb pull /tmp/recovery.log recovery.txt. This will save a copy of the TWRP log named recovery.txt inside your ADB folder. Then upload this file here.

bomberb17 said:
Lineage recovery link is broken..
Click to expand...
Click to collapse
Extract the lineage 19.1 rom and find recovery.img
put it into platform tools folder and execute fastboot command
fastboot flash recovery recovery.img
fastboot reboot
then you have lineage recovery

I finally managed to install lineage rom by sideloading resize_wt88047x_v6.zip, then formatting data, cache and system partitions, then adb reboot recovery then sideload lineage rom.
Phew!