A little how-to on upgrading your nexus phone without having to wipe your data if you rooted and installed some stuff onto system partition.
WARNING!
DO NOT USE THIS METHOD IF YOU ARE NOT GOOD AT USING COMMAND LINE! THIS HAS A POSSIBILITY OF BRICKING YOUR PHONE TO WHERE IT WONT BOOT.
Note:
You will loose the following when using this method:
-Custom Recovery
-Custom Kernel
-ANYTHING that is installed on the system partition including but not limited to: SU (root), Busybox, Xposed, etc.
What is needed:
-ADB (1.0.32+) and Fastboot
-Factory Image of Nexus 6 (https://developers.google.com/android/nexus/images?hl=en)
-- MUST BE THE SAME BUILD VERSION AS YOUR CURRENT VERSION!
--- Check under System > About Phone > Build Number
Step 1 (Catch the update url):
Open up command prompt/terminal and type in
Code:
adb logcat
.
From here you will get a lot of debug lines, dont worry about any of it.
What we are looking for is the url to the update file.
When adb logcat is ready, start the update for your phone. (Dont worry about restarting or whatnot, you wont be using the file it's downloaded anyway).
From the url, use that to download the update file to your computer.
Step 2 (Backup):
This is important as a just in case **** happens thing.
BACK UP YOUR PHONE if you have a custom recovery.
Don't think that this update method is foolproof.
Don't even think.
BACK IT UP!
Step 3 (Restore to "Factory"):
This is where it gets hairy.
Using the factory image you downloaded open up the "image-shamu-<build>.zip" file and extract "boot.img", "recovery.img", and
"system.img".
Restart your phone to bootloader either with adb or pressing and holding power + vol down.
From here, in a command prompt/terminal, type:
Code:
fastboot flash boot <boot.img path>
Code:
fastboot flash recovery <recovery.img path>
Code:
fastboot flash system <system.img path>
System image will take the longest and will be streamed to the phone so just wait until it's finished.
Step 4 (Upgrade):
ok, now that we are in "Factory" settings, start up your phone in recovery mode.
From the recovery screen you should see the little android with the red exclamation point icon thing.
Press and hold power and click the volume up button. Release power button.
From here, select
Code:
apply update from ADB
now in command prompt type:
Code:
adb sideload <update.zip path>
Step 5: ???
Step 6: Profit!
I have done this method twice and haven't experienced any problems myself. As stated above, this does have the possibility of mucking something up so be sure to have backups.
After everything is done, you are using your phone in stock mode.
flash your custom recovery and custom kernel if you'd like. Also reinstall root via custom recovery (twrp will let you know) and busybox.
Troubleshooting:
- Update says system partition has unexpected contents.
-- Reflash system.img.
- Get adb sideload error (xxx)
-- Make sure you have the latest version of adb and that your drivers for your phone are installed. Sometimes you have to manually install the adb drivers when in sideload mode.
Hi,
i tried to update my phone via the integrated updater. It did not start the update and now fails booting into android. it boots every time into twrp.
i tried several possible solutions:
reflash other version
reflash the latest version
flashed fulmics
factory wipe
reflashed twrp
tried to
inshadesofgrey said:
If you get into a recovery boot loop (where the phone keeps booting into the recovery, and not the OS), this will fix it without losing any data. (NO FACTORY RESET NEEDED)
Go to TWRP recovery terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PRESS ENTER
THEN TYPE
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
THEN PRESS ENTER
REBOOT
This should boot up your phone without any changes.
Click to expand...
Click to collapse
but failed
now i am out of knowledge...
has anyone an idea?
Regards!
Christian
did you tried to restore everything to stock with a kdz file? you can find it on google and you can flash it putting the device in download mode and using lgUP / uppercut to do so.. if you need help you can send me a PM
one_ctrl said:
did you tried to restore everything to stock with a kdz file? you can find it on google and you can flash it putting the device in download mode and using lgUP / uppercut to do so.. if you need help you can send me a PM
Click to expand...
Click to collapse
Is there any better solution for this problem?
I solved it once with a full reinstall an this uppercut tool.
On reddit for other phones there is the solution to boot to bootloader and do
Code:
fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.001s
But this does not work.
It seems my phone boots to twrp because the lineage os updater app set s.th. to automatically boot to twrp. How can we remove this auto-boot to twrp flag?
Sorry for bringing up this again. I did an OTA update on lineageos on my lg g6. The phone booted correctly in twrp, I installed the update but now the phone boots directly to twrp without any way to let it boot the os. How did you resolve this?
Thanks
Only solution back to stock & after install LOS and wait until bug is fixed.
I use a lg g pad x 8.0 and ran into the same issue.
fastboot continue would not work.
the dd commands did not work either
I think the "msm_sdcc.1" is device specific.
In recovery, I used the file manager to look in /dev/block/platform and notice that "msm_sdcc.1" did not exist but there was one folder in there. I went in there and there was another and kept going til I found the "by-name" folder
then I ran the dd command replacing "msm_sdcc.1" with what was on my device.
I did it for "fota" and "misc" and then my device booted
Someone else has had this problem @gnackwatschn, you can find a way to fix the boot loop here https://forum.xda-developers.com/lg-g6/help/twrp-bootloop-lineageos-ota-update-t3746014/post75488796#post75488796
WARNING [brick]
eng3 said:
I use a lg g pad x 8.0 and ran into the same issue.
fastboot continue would not work.
the dd commands did not work either
I think the "msm_sdcc.1" is device specific.
In recovery, I used the file manager to look in /dev/block/platform and notice that "msm_sdcc.1" did not exist but there was one folder in there. I went in there and there was another and kept going til I found the "by-name" folder
then I ran the dd command replacing "msm_sdcc.1" with what was on my device.
I did it for "fota" and "misc" and then my device booted
Click to expand...
Click to collapse
WARNING! I ran into the same problem on the LG G6 with the nightly update dated Nov 1, 2018. Did what you did, but wrote down the command.
After navigating to the TWRP > Advanced > Terminal, first do
Code:
ls /dev/block/platform
Mine had one entrie: soc, which had two entries: 624000.ufshc and 74a4900.sdhci
only 624000.ufshc had a by-name directory containing fota and misc, so my commands ended up being:
Code:
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/fota
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc
The commands run, saying:
Code:
dd: writing '/dev/block/platform/soc/624000.ufshc/by-name/fota': No space left on device
8193+0 records in
8193+0 records out
4194304 bytes (4.0MB) copied), 2.783000 seconds, 11.5MBs
and similar for misc.
Reboot to system gives a warning, Your device has failed a routine safety check and will not boot.
Now I'm stuck.... guess its time to start another thread.
Works only on Tank HD and Mantis 4K.
The process is really simple and requires very little effort to return back to 100% stock in case you return your device or for many reasons. Ok download and find the official latest stock image for your Fire TV, and download then install ADB and Fastboot on your computer, plug your Fire TV in to your computer, make sure ADB is on, then type in these given commands, ADB devices, ADB reboot recovery, ADB shell, twrp wipe /system, twrp sideload, ADB sideload update.zip (rename the .bin to .zip) and let it continue flashing. Once finished, take the update.zip and extract it. Find the boot.img from the folder and type this in. ADB sideload (drag and drop) boot.img /storage/emulated/0 (if this doesn't transfer while in TWRP, reboot into the /system and type in the same command again), this is where you'll need an OTG cable with a mouse (For the Fire TV Stick 4K it'll boot into TWRP on boot with OTG so cancel the rebooting in 3..2...1.. and click install in TWRP, on the lower right hand corner click on install image, boot.img and flash it as boot. Backup the boot.img and restore it with your mouse. Unplug your device, and plug it back into the computer, ADB reboot recovery, ADB shell reboot-amonet, it'll now be in hacked fastboot mode. Make sure it's recognized as a fastboot device and type in these final commands, fastboot flash boot (drag and drop) boot.img then reboot. After rebooting, type in ADB reboot recovery and you'll now see no command which means you successfully removed TWRP with stock updates now.
For those without OTG, still the same instructions (Backup the boot after flashing the stock image and restore it with these commands that can be found here):
https://twrp.me/faq/openrecoveryscript.html
Skel40 said:
Find the boot.img from the folder and type this in. ADB sideload (drag and drop) boot.img /storage/emulated/0 (if this doesn't transfer while in TWRP, reboot into the /system and type in the same command again), this is where you'll need an OTG cable with a mouse (For the Fire TV Stick 4K it'll boot into TWRP on boot with OTG so cancel the rebooting in 3..2...1.. and click install in TWRP, on the lower right hand corner click on install image, boot.img and flash it as boot. Backup the boot.img and restore it with your mouse.
Click to expand...
Click to collapse
You don't need to deal with the boot.img in TWRP, it gets flashed together with the rom. Also no need for a backup and a restore.
Simply flash the stock rom with TWRP, then reboot to the BL with 'adb shell reboot-amonet' followed by a 'fastboot flash boot boot.img'
In case someone wants to send the stick back, a 'fastboot format userdata' is a good idea, then fastboot reboot
Just at the reboot, TWRP gets replaced with the stock recovery.
Done.
Update: Finally got on the latest and greatest, no root or TWRP. I found a list of the stock ROMS in the link below. As stated above, I simply flashed the stock ROM in TWRP and then rebooted and did a factory reset followed by and update. Simple as that.
https://www.aftvnews.com/amazon-fire-tv-fire-tv-stick-software-update-history/
Where can I find an unrooted stock ROM? I'm trying to get rid of twrp on one of my firetv boxes. I started by allowing OTA updates and when I try to update, it will download and then acts like it will install it, but upon reboot it is still on the same version. Presumably because TWRP is interfering with the install process? Either way, direction yo a stock image is appreciated. All I can seem to find are rprerooted images.
For 4k
https://forum.xda-developers.com/fire-tv/general/official-stock-image-fire-tv-stick-4k-6-t4088247
First Post, rename bin to zip.
Flash with twrp.
adb push firmware.zip /sdcard/firmware.zip
adb shell twrp wipe cache
adb shell twrp wipe data
adb shell twrp wipe dalvik
adb shell twrp wipe /system
adb shell twrp install /sdcard/firmware.zip
Extract boot.img from Firmware.zip
adb shell reboot-amonet
fastboot flash boot boot.img
fastboot reboot
Now you are back at Stock.
0815hoffi said:
For 4k
https://forum.xda-developers.com/fire-tv/general/official-stock-image-fire-tv-stick-4k-6-t4088247
First Post, rename bin to zip.
Flash with twrp.
adb push firmware.zip /sdcard/firmware.zip
adb shell twrp wipe cache
adb shell twrp wipe data
adb shell twrp wipe dalvik
adb shell twrp wipe /system
adb shell twrp install /sdcard/firmware.zip
Extract boot.img from Firmware.zip
adb shell reboot-amonet
fastboot flash boot boot.img
fastboot erase userdata
fastboot reboot
Now you are back at Stock.
Click to expand...
Click to collapse
Does this remove twrp? I want to go back to stock but NOT UNISTALL TWRP because aftv-gapps are not working for me so i want to go back to stock and re-root it and install aftv gapps
ROM_gamer987 said:
Does this remove twrp? I want to go back to stock but NOT UNISTALL TWRP because aftv-gapps are not working for me so i want to go back to stock and re-root it and install aftv gapps
Click to expand...
Click to collapse
This will remove TWRP
Code:
adb shell reboot-amonet
fastboot flash boot boot.img
fastboot erase userdata
fastboot reboot
This code restores original Recovery and bootloader, if you want to keep TWRP then don't use these commands, you can use above commands to unroot.
ROM_gamer987 said:
I want to go back to stock but NOT UNISTALL TWRP because aftv-gapps are not working for me so i want to go back to stock and re-root it and install aftv gapps
Click to expand...
Click to collapse
If its a gapps system install, simply wipe system and flash a new stock bin (renamed to zip).
-----------------
Note to everyone, the guide above in OP works only for 'tank' (aka second gen stick) and 'mantis' (aka 4k stick).
SweenWolf said:
This will remove TWRP
Code:
adb shell reboot-amonet
fastboot flash boot boot.img
fastboot erase userdata
fastboot reboot
This code restores original Recovery and bootloader, if you want to keep TWRP then don't use these commands, you can use above commands to unroot.
Click to expand...
Click to collapse
Well I did these commands and twrp is still there, I guess I was lucky and the boot.img failed or something, Now I got gapps working
I might be missing something, but as far as i can see, following the steps from this thread will only flash the stock boot.img (which is not patched with amonet when using fastboot) and erase userdata (reset), but it will not remove twrp (which reside in the recovery partition).
To replace TWRP with stock recovery, the fastboot command should look like this:
fastboot flash recovery stock_recovery.img
"stock_recovery.img" filename is just an example,of course.
Pretoriano80 said:
I might be missing something
Click to expand...
Click to collapse
I don't know
k4y0z said in the 4k thread, that the stock recovery gets restored (out of the boot.img) at first boot...
Though your command should work fine obviously.
k4y0z said:
Is it possible to remove the hacked bootloader and twrp?
Click to expand...
Click to collapse
You would have to flash stock update-bin via TWRP first and then flash the stock boot.img from that same update-bin separately via hacked fastboot.
Amazon recovery should then be restored on first boot.
Click to expand...
Click to collapse
Permalink
@0815hoffi, i have followed all the mentioned command steps above and TWRP still exists. Attached is the proof. It doesn't show up during normal boots but when reset or Fire stick auto software update is performed it takes control. TWRP even installs Fire stick software update too.
@Pretoriano80 looks like you are correct. Is there a way i can completely remove TWRP since now i have restored Fire stick original OS and not going through shorting and root process again. adb doesn't work now.
TwrpFire
matrixddl said:
@0815hoffi, i have followed all the mentioned command steps above and TWRP still exists. Attached is the proof. It doesn't show up during normal boots but when reset or Fire stick auto software update is performed it takes control. TWRP even installs Fire stick software update too.
@Pretoriano80 looks like you are correct. Is there a way i can completely remove TWRP since now i have restored Fire stick original OS and not going through shorting and root process again. adb doesn't work now.
TwrpFire
Click to expand...
Click to collapse
For me it worked on TvStick2 .
You must use Stock rom , not prerooted.
Wipe System , Flash rom, Boot amonet, Flash Boot.bin with Fastboot, reboot.
Run oobe, enable ADB.
Adb shell reboot recovery.
Stock Recovery should comes up....
0815hoffi said:
For me it worked on TvStick2 .
You must use Stock rom , not prerooted.
Wipe System , Flash rom, Boot amonet, Flash Boot.bin with Fastboot, reboot.
Run oobe, enable ADB.
Adb shell reboot recovery.
Stock Recovery should comes up....
Click to expand...
Click to collapse
I have downloaded latest stock from here
Now to retry the process do i have to unlock again or anyway i can continue using existing twrp.
No if you can Boot to twrp.
Sus_i said:
I don't know
k4y0z said in the 4k thread, that the stock recovery gets restored (out of the boot.img) at first boot...
Though your command should work fine obviously.
Permalink
Click to expand...
Click to collapse
Ok, i figured how it works. Probably if the recovery signature doesn't match on first clean boot, then it will trigger the /system/bin/install-recovery.sh script and that will flash/install the stock recovery.
But if for some reason that script was removed/modified, then it will fail to replace TWRP with the stock recovery (maybe that's why this guide works for some but not for all).
0815hoffi said:
No if you can Boot to twrp.
Click to expand...
Click to collapse
I rooted again and tried to try to restore original and still TWRP exists. I have followed your steps as well as original OP's instructions still no luck.
I was on mantis-6.2.6.8-rooted_r1 and from there i used the stock update-kindle-mantis-NS6276_user_2933_0004396381572 to restore? Which version of stock rom did you use?
Pretoriano80 said:
Ok, i figured how it works. Probably if the recovery signature doesn't match on first clean boot, then it will trigger the /system/bin/install-recovery.sh script and that will flash/install the stock recovery.
But if for some reason that script was removed/modified, then it will fail to replace TWRP with the stock recovery (maybe that's why this guide works for some but not for all).
Click to expand...
Click to collapse
Is there a way to check or fix this?
Same as installed.
Try with
https://d1s31zyz7dcc2d.cloudfront.n...dle-mantis-NS6268_user_2315_0003255372676.bin
Flash it, boot, make initial Setup.
Then reboot to twrp and follow the Guide
matrixddl said:
I rooted again and tried to try to restore original and still TWRP exists. I have followed your steps as well as original OP's instructions still no luck.
I was on mantis-6.2.6.8-rooted_r1 and from there i used the stock update-kindle-mantis-NS6276_user_2933_0004396381572 to restore? Which version of stock rom did you use?
Is there a way to check or fix this?
Click to expand...
Click to collapse
I don't know why it doesn't work for you, so i have no idea how to fix.
Personally, when i went back to full factory condition, i flashed every partition with hacked fastboot.
I have it testet with my 4k Stick Installed Version 6.2.7.3.
I think the Problem is #fastboot erase userdata
dont run this.
Now i am back at Stock.
Thats the Log off my test.
https://androidfilehost.com/?fid=6006931924117923181
Installed Version 6.2.7.3
D:\FireTV2K4K>adb push ftvs4k_6.2.7.3.zip /sdcard/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
10290 KB/s (648296329 bytes in 61.522s)
D:\FireTV2K4K>adb shell reboot recovery
D:\FireTV2K4K>adb shell twrp wipe cache
Formatting Cache using mke2fs...
Done.
Done processing script file
D:\FireTV2K4K>adb shell twrp wipe data
Wiping data without wiping /data/media ...
Done.
Formatting cache using mke2fs...
Done.
Done processing script file
D:\FireTV2K4K>adb shell twrp wipe dalvik
Wiping Cache & Dalvik...
-- Dalvik Cache Directories Wipe Complete!
Done processing script file
D:\FireTV2K4K>adb shell twrp wipe /system
Formatting System using mke2fs...
Done.
Done processing script file
D:\FireTV2K4K>adb shell twrp install /sdcard/ftvs4k_6.2.7.3.zip
Installing zip file '/sdcard/ftvs4k_6.2.7.3.zip'
Checking for Digest file...
[amonet] Load microloader from recovery...
[amonet] Remove boot patch...
[amonet] OK
Target: Amazon/mantis/mantis:6.0/NS6273/2773N:user/amz-p,release-keys
Patching system image unconditionally...
Patching vendor image unconditionally...
script succeeded: result was [1.000000][amonet] Install boot patch...
[amonet] OK
[amonet] Install recovery patch...
[amonet] ALREADY_INSTALLED
Done processing script file
D:\FireTV2K4K>adb shell reboot-amonet
D:\FireTV2K4K>fastboot devices
************* fastboot
D:\FireTV2K4K>fastboot flash boot boot.img
target reported max download size of 134217728 bytes
sending 'boot' (7522 KB)...
OKAY [ 0.312s]
writing 'boot'...
OKAY [ 0.484s]
finished. total time: 0.797s
D:\FireTV2K4K>fastboot erase userdata
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
OKAY [ 0.141s]
finished. total time: 0.156s
D:\FireTV2K4K>fastboot reboot
rebooting...
finished. total time: -0.000s
D:\FireTV2K4K>
_________________________________________________
TWRP is still here
_________________________________________________
Update on initial Setup is running > auto reboot to TWRP
_________________________________________________
D:\FireTV2K4K>adb shell
~ # ^[[5;5R
~ # ^[[7;5R
~ # ^[[9;5R
~ # ^[[11;5Rexit
exit
D:\FireTV2K4K>
D:\FireTV2K4K>adb push ftvs4k_6.2.7.3.zip /sdcard/
9691 KB/s (648296329 bytes in 65.325s)
D:\FireTV2K4K>adb shell twrp install /sdcard/ftvs4k_6.2.7.3.zip
Installing zip file '/sdcard/ftvs4k_6.2.7.3.zip'
Checking for Digest file...
[amonet] Load microloader from recovery...
[amonet] Remove boot patch...
[amonet] OK
Target: Amazon/mantis/mantis:6.0/NS6273/2773N:user/amz-p,release-keys
Patching system image unconditionally...
Patching vendor image unconditionally...
script succeeded: result was [1.000000][amonet] Install boot patch...
[amonet] OK
[amonet] Install recovery patch...
[amonet] ALREADY_INSTALLED
Done processing script file
D:\FireTV2K4K>adb shell reboot-amonet
D:\FireTV2K4K>fastboot devices
************* fastboot
D:\FireTV2K4K>fastboot flash boot boot.img
target reported max download size of 134217728 bytes
sending 'boot' (7522 KB)...
OKAY [ 0.312s]
writing 'boot'...
OKAY [ 0.489s]
finished. total time: 0.801s
D:\FireTV2K4K>fastboot reboot
rebooting...
finished. total time: -0.000s
D:\FireTV2K4K>
__________________________________________________________________________________________________
After Bootup Update is running, now it reboots to Stock recovery and 6.2.7.6 will be is installed.
__________________________________________________________________________________________________
Click to expand...
Click to collapse
adb shell reboot recovery > boots now to stock Amazon recovery.
This worked.
Installed version 6276. adb reboot recovery returns "No Command".
Kudos for you help and patience.
0815hoffi said:
I have it testet with my 4k Stick Installed Version 6.2.7.3.
I think the Problem is #fastboot erase userdata
dont run this.
Now i am back at Stock.
Thats the Log off my test.
adb shell reboot recovery > boots now to stock Amazon recovery.
Click to expand...
Click to collapse
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!