Develop Bugs

TWRP Can't Mount /System - OP3 Bricks When Trying to Flash New ROM??

I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Also it seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Is this why the flashing keeps failing and does anyone know what the problem could be?
Thanks!

bronderb said:
Go into your bootloader and format system, cache, and userdata (This will wipe EVERYTHING so be sure to backup). Then latest official flash stock rom and reboot. This should fix it. If this helped hit thanks!
Click to expand...
Click to collapse
Bootloader? There is no option in the bootloader to delete everything as far as I can see, do you mean in recovery? And if I wipe everything off the phone, how do I get the stock ROM onto the phone to flash it? When you say wipe userdata do you mean wipe internal storage or am I misunderstanding and you're telling me to wipe the usual dalvik, cache and data as you would for a normal clean flash?

bronderb said:
No, go into fastboot and plug into pc. Open cmd and type "fastboot format userdata" "fastboot format cache" "fastboot format system"
Click to expand...
Click to collapse
Okay, thanks, and then what? Do I flash TWRP then push the stock ROM to the phone and flash that? And exactly how do I do that?

bronderb said:
You just go into twrp (no need to reflash) then adb sideload oxygen os
Click to expand...
Click to collapse
Thank you, I am now running OOS, hopefully everything else will go smoothly now, planning to go back to FOS again
I didn't even have to use the fastboot commands to format, just sideloading the OOS file wiped everything anyway

Turns out the issue isn't actually fixed, "system" still appears unchecked in TWRP. Could the fact that I didn't actually format everything first have made a difference, given everything was wiped in the process anyway?
Looks like I'm going to be living the sideloading life...
Edit: Sideloading freedom OS failed, ended up having to restore from my TWRP backup. I don't know what I'm going to do, my main reason for using custom ROMs is installing a black theme, and OOS doesn't support Layers or Substratum fully so I can't stay on that

Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that

frickinjerms said:
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
Click to expand...
Click to collapse
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.

evilkitty69 said:
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
Click to expand...
Click to collapse
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.

Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.

tnsmani said:
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Click to expand...
Click to collapse
I was running 3.0.2-2 when the issue started, I updated to 3.0.3 and 3.1.0-0 but nothing changed. Thanks for the suggestion, I will give it a try

null0seven said:
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
Click to expand...
Click to collapse
Help! I attempted to do this and the process failed, I didn't manage to wipe data because "/data could not be mounted as device or resource is busy"
Edit: Device now has nothing but TWRP and fastboot, no OS, no ADB, no data, no internal storage

If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )

I managed to get hold of a few factory images and attempted to flash system.img through fastboot, resulting error was
"target reported max download size of 536,870,912 bytes" (system image is 3080 MB)
"invalid sparse file format at header magi"

null0seven said:
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
Click to expand...
Click to collapse
I reflashed the modified TWRP successfully. The second suggestion wouldn't have worked, given my phone has no internal storage

You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.

null0seven said:
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
Click to expand...
Click to collapse
The recovery was working at this point, the issue turned out to be the data partition, system was formatted to ext4 but I didn't realise data was in f2fs which caused the problem in the first place. I formatted to ext4 and everything worked, I was able to install paranoid android and everything worked...
...until I flashed the wrong firmware and now I've hard bricked it! I'm going to try the hard brick toolkit
Edit: After 12 hours of being an unresponsive brick, the phone suddenly booted, system doesn't work but it has recovery. Unfortunately I seem to be back to square one, if I try to flash something it appears to succeed but then the phone doesn't boot up into system

So I am now back to the original issue of system not mounting, in terminal if I type "mount /system" I get following error:
"mounting /dev/block/sde20 on /system failed: Device or resource is busy"
Anyone know how to solve this?

I formatted everything, reflashed recovery and tried to flash OOS, got following error:
Code:
[FONT="Courier New"]"This package is for OnePlus3 devices, this is a oneplus3t" (it isn't)
"Updater process ended with ERROR: 7
Error installing zip file /sdcard/OOS3.2.6.zip" [/FONT]

Issue was "solved" by flashing PA, GApps and the correct firmware
Hopefully that's the end of all this drama, thanks to everyone for their suggestions

Hi, I'm pretty new at rooting and I seem to have a similar error. I'm getting the "can't mount /system" error in TWRP. I am able to boot into OOS 4.1.3 and run the nandroid backup but, I keep getting the same error and am unable to select "system" when choosing the mount option in TWRP.
Do I need to have all partitions in f2fs? My system partition is in ext4. Is this what solved your issue?
It seems my phone is functional even with the error active but, I've been trying to get systemless SuperSU and MagiskHide working and I think that's what is preventing me from doing so.

Really need help, google flash gone bad

At first I tried to update my existing TWRP (3.2.1-0) to the 3.2.1-2 variant. It flashed ok, but then the phone would only boot to TWRP (reason for upgrade is that 3.2.1-0 would hang). I was attempting initially to put myself on the path to a "custom rom". When this failed, I manually flashed the latest google firmware from their page and it still will not do anything other than fastboot mode. No recovery, no firmware load. When I try to do the flash-all.bat method now, all I get after it loads the archive contents is "error: Cannot generate image for userdata. Guess I got a $1000 brick at this point?? Image from the PC screen included.

See if this thread helps.
https://forum.xda-developers.com/pi...ory-image-flashing-fails-t3715350/post7649698

I am going to have to find another way to look at that thread. My ipad is getting directed to some HTC desire article about and orange and black theme.
I have tried so far very unsuccessfully to wipe everything by booting to twrp via fastboot method. Then I used the dueces script to reflash everything completely (both partitions). No matter whether I flash complete stock or flash magisk and verizon radio files, it just hangs on the white google screen now and that is as far as I have gotten. Left it at home in this mode hoping it will clear.

JoeNeckbone said:
See if this thread helps.
https://forum.xda-developers.com/pi...ory-image-flashing-fails-t3715350/post7649698
Click to expand...
Click to collapse
That link is bad. Three devices are going to an htc desire theming page.

remove the -w from the update line in flash-all.

I have got the same problem since yesterday and search for a solution.

ctradio said:
That link is bad. Three devices are going to an htc desire theming page.
Click to expand...
Click to collapse
Not sure what happened with link, https://forum.xda-developers.com/pi...ry-image-flashing-fails-t3715350/post74751631

new adb dont help for me. I cannot flash slot a and change to b and got the error message that no slot is supported.

Still need help? Have you tried Skipsoft? Sure its not been updated but it might beable to help ..
Where fastboot flashing failed for me one time it got me out of a hole....
Otherwise i can try and remote and help... BTW its not finding the userdata file in the fastboot side... Something isnt right hence why it cant create the userdata file...

I try to boot with skipsoft to temp twrp but stuck on boot.img loading. the flashed twrp stuck on twrp logo and before I have changed from slot b to a inside twrp i can boot. now I cannot flash inside fast boot or delete anything.

Have you guys tried Deuces Bootloop Recovery & Flashing Script? I'd imagine you'd run into the same issues as the script runs a lot of the same fastboot commands...but it has worked wonders for many other users so......
I also might try re-downloading the factory image and comparing the Checksums to make sure you have a whole exact download just in case that's getting in the way of properly generating the userdata image. I'd also suggest making sure you have more than 4GB of space on your C drive; I was getting similar messages about not finding or not generating system images because they couldn't be fully extracted (temporarily) because I didn't have sufficient temp space on my C drive.
But I had encountered this issue before. It was either userdata or system_other partition. I did attempt to fastboot erase and fastboot format those partitions and other tweaks; even messed with changing the size of the partition (you might have better luck). What I seemed to conclude is that I was flashing the wrong month's Full Factory image; i.e. I was manually flashing system_other image from February when the whole phone was still on January. But I believe what I ended up doing was flashing a Full Factory image with the "-w" intact; therefore, if you still have access, you should copybackcup (via TWRP or adb pull) your internal storage (/sdcard and-or /data/media) and simply flash a Full Factory image with wipe option enabled...
Just some thoughts and suggestions...hope this helps...

I figured it out finally. Even though my ADB/Fastboot tools were a later creation date than the ones posted online, the ones online worked great. Even used the dueces script to ensure the junk is gone. Thanks all! Hate pesky gotchas like that!!

Pie, TWRP and vendor partition help

So I've been running Oreo Omnirom and I'm looking at moving to Android Pie. I have never installed any of the OnePlus Beta's or any other Pie based ROM.
I am currently running TWRP version twrp-3.2.3-0-20180822-codeworkx-dumpling and from the date code, it looks like to could be a little old. When I jump into TWRP, I get errors that no vendor partition is found.. I have always ignored this as I was on Oreo and didn't need/care about a vendor partition. This also led me to believe that the version of TWRP I am using support the vendor partition.
Is there an easy way to create and format the vendor partition? Is my TWRP version too old? I tried running twrp-3.1.1-x_blu_spark_v8.55-op5_op5t as recommended in another thread (even tho it's older) and I had to re-flash TWRP via fastboot because that IMG file no worky...
I am trying to avoid formatting my data since my phone has a larger drive than my computer. If someone could point me in the right direction, it would be very much appreciated.

Flashing twrp-3.1.1-x_blu_spark_v8.55-op5_op5t or twrp-3.2.3-0-20190311-codeworkx-dumpling.img (both TWRPs for PIE) wont boot to recovery. Both boot to a blank screen with the notification LED turned blue. I assume that this is because I am still on Oreo firmwares... Seems like I have a chicken and egg sort of situation going on here....

Flashed OxygenOS_5.1.4 full OTA. /vendor partition was not created, but I only booted until I reached the lockscreen at which point told me that my password was incorrect. Do I need to remove my lockscreen password in Omni and try again?

crakerjac said:
Flashed OxygenOS_5.1.4 full OTA. /vendor partition was not created, but I only booted until I reached the lockscreen at which point told me that my password was incorrect. Do I need to remove my lockscreen password in Omni and try again?
Click to expand...
Click to collapse
Remove your security before flashing anything and then try 5.1.4 full OOS zip. If that works, great. OTA up to latest, or as far as it will allow and then use the full zip files available in the forum to get onto latest Pie. You'll need to fastboot flash latest Pie TWRP (codeworkx) when you get up to date.
If you run into security problems you might have to try a clean flash, or even format. Make sure you are in front of your PC before beginning and backup everything.

Still having no luck here.
Here is what I have done to try and get TWRP to recognize a /vendor partition:
Formatted Data
Side loaded OnePlus5TOxygen_43_OTA_037 in TWRP
Flashed OTA_037
Booted OxygenOS and completed setup
Rebooted to bootloader
Flashed twrp-3.2.3-0-20180822-codeworkx-dumpling
Rebooted to TWRP recovery
At this point I am STILL getting 'Failed to mount '/vendor' (invalid argument)'.
WTF am I doing wrong? How to I create a /vendor partition?

crakerjac said:
Still having no luck here.
Here is what I have done to try and get TWRP to recognize a /vendor partition:
Formatted Data
Side loaded OnePlus5TOxygen_43_OTA_037 in TWRP
Flashed OTA_037
Booted OxygenOS and completed setup
Rebooted to bootloader
Flashed twrp-3.2.3-0-20180822-codeworkx-dumpling
Rebooted to TWRP recovery
At this point I am STILL getting 'Failed to mount '/vendor' (invalid argument)'.
WTF am I doing wrong? How to I create a /vendor partition?
Click to expand...
Click to collapse
hi, may be this will help you, see post #2 from this thread:
"..... (because 5.1.4 creates the vendor partition and 5.1.5 fills ot)"
https://forum.xda-developers.com/oneplus-5t/help/solved-twrp-error-7-vendor-partition-t3846181

My thought process was that if 5.1.4 creates the /vendor partition, then TWRP should still be able to recognize it and mount that partition... I'm not sure if I care if it's full or empty at this point... I fear that I will download another 1.6GB of data just to find that the update wont happen because /vendor cannot be found... Unless I am completely wrong...

Well dang... I was wrong. Flashing 5.1.5 patched the /vendor partition and removed the error in TWRP.
Thanks for the help guys.
Mods please close (solved).

Can't root or install TWRP after Dec factory setting

I was rooted on 9 with Magisk. Updated to 10 via Google update on the phone. All worked. Still rooted but didn't have TWRP installed- it wouldn't work. But no worries. I was rooted which is the main thing.
Tried to do the DEC OTA with Magisk. Didn't work. Flashed factory image of December and it worked. Tried to boot img of TWRP. didn't work. Tried to use Magisk to root with the boot.img patch from PC. Didn't work. Phone wouldn't boot.
Reflashed factory image and it didn't work. Changed cord to same USB A and and got it working again. Rinse, repeat. Eventually it stopped working period. adb and fastboot were not talking to the phone.
Used different USB A port and newer cord (same as above) and was able to reinstall Dec factory and it worked. Used new cable to boot twrp.img. Worked. Used that to flash TWRP. Worked. Tried to flash Magist in TWRP. Got TWRP bootloot. Used TWRP to fix bootloop. It restored boot (so far as I can tell- what do I know? I'm just a lawyer) and phone worked but no root. Rinse repeat a number of times. Got Magisk working and THEN tried to flash TWRP. Bad plan. Broke.
Went to screen saying whole thing was broke (Their recovery sort-of screen saying files corrupted in red and I could retry or wipe in blue. But I could factory reset. I avoided that and tried to reflash (using flash-all.bat after removing -w) a number of times. It finally worked. Gave it the overnight to calm down. Me, too.
10 was working. Cord seemed to be working. Came home after work and booted image of TWRP. That worked. Flashed Magisckzip. That dumped me into TWRP which I swear to god I had not flashed, just temp booted. So tonight was rinse and repeat of yesterday's woes.
Anyhow, many attempts to reinstall Dec factory image finally worked (using various cords, USB A & C ports.)
Rinse, repeat.
I have my SD card backed up on my PC so it isn't any kind of disaster for me to do a factory rest but dammit! I don't wanna! It should work.
At the present time I am working with Dec factory image, stock recovery, and not rooted. (Although Tasker seems to be working in location-sound off circumstances. WTAF?)
Taking any and all advice. Thanks.
Aside from full wipe. If that's your only advice please just say "wipe" and move along. If you have another suggestion, please use lots of words.
(My husband says it's the testosterone sensor but I'm the one who fixes the computers, phones, and network so I think my cover is deep enough...)

janehull said:
I was rooted on 9 with Magisk. Updated to 10 via Google update on the phone. All worked. Still rooted but didn't have TWRP installed- it wouldn't work. But no worries. I was rooted which is the main thing.
Tried to do the DEC OTA with Magisk. Didn't work. Flashed factory image of December and it worked. Tried to boot img of TWRP. didn't work. Tried to use Magisk to root with the boot.img patch from PC. Didn't work. Phone wouldn't boot.
Reflashed factory image and it didn't work. Changed cord to same USB A and and got it working again. Rinse, repeat. Eventually it stopped working period. adb and fastboot were not talking to the phone.
Used different USB A port and newer cord (same as above) and was able to reinstall Dec factory and it worked. Used new cable to boot twrp.img. Worked. Used that to flash TWRP. Worked. Tried to flash Magist in TWRP. Got TWRP bootloot. Used TWRP to fix bootloop. It restored boot (so far as I can tell- what do I know? I'm just a lawyer) and phone worked but no root. Rinse repeat a number of times. Got Magisk working and THEN tried to flash TWRP. Bad plan. Broke.
Went to screen saying whole thing was broke (Their recovery sort-of screen saying files corrupted in red and I could retry or wipe in blue. But I could factory reset. I avoided that and tried to reflash (using flash-all.bat after removing -w) a number of times. It finally worked. Gave it the overnight to calm down. Me, too.
10 was working. Cord seemed to be working. Came home after work and booted image of TWRP. That worked. Flashed Magisckzip. That dumped me into TWRP which I swear to god I had not flashed, just temp booted. So tonight was rinse and repeat of yesterday's woes.
Anyhow, many attempts to reinstall Dec factory image finally worked (using various cords, USB A & C ports.)
Rinse, repeat.
I have my SD card backed up on my PC so it isn't any kind of disaster for me to do a factory rest but dammit! I don't wanna! It should work.
At the present time I am working with Dec factory image, stock recovery, and not rooted. (Although Tasker seems to be working in location-sound off circumstances. WTAF?)
Taking any and all advice. Thanks.
Aside from full wipe. If that's your only advice please just say "wipe" and move along. If you have another suggestion, please use lots of words.
(My husband says it's the testosterone sensor but I'm the one who fixes the computers, phones, and network so I think my cover is deep enough...)
Click to expand...
Click to collapse
Oh my, where to start. Definitely sounds like you've got the famous P2XL USB cable bugaboo...at least somewhat. Here's what I would do.
Extract the boot.img from the factory image, place it on your phone and patch it again, then transfer it to your platform-tools folder.
Make sure your platform tools are up to date. Latest version is 29.0.5
Have you also fastbooted the factory image to both slots? If not, do that first. You can manually change slots with..fastboot --set-active=a or b depending what slot your currently on.
If your phone is booting, then go back and fastboot your patched boot.img to both slots with...
..fastboot flash boot magisk_patched.img --slot=all..
If the phone boots you should be rooted.
If you still want twrp, download it again to your pc, put one copy in your platform-tools folder, and one on your phone, remove your screen lock and set it to swipe or none. Then fastboot the twrp 3.3.0-0.img which should boot you into twrp. If it's working, then select install, select image, then flash the twrp image to your recovery ramdisk partition. That should keep your recovery as twrp. Boot up, and you should be good to go :good:

Yes, latest platform tools. After first difficulties I dumped everything, did new downloads and upzips of of factory image, platform-tools, and got new twrp.img, twrp.zip and magisk.zip. Checkedsum on all of them I could.
No. It never occurred to me to fastboot factory image to both slots. I guess I just assumed that The Google (tm) would know what they were doing. Thank you for that. I will give it a shot in the morning. I need enough lead time to fix it if it breaks because my life and office are on that phone.
And now, after learning how to see which slot is active I can learn how to flash to both! Thanks a lot.

janehull said:
Yes, latest platform tools. After first difficulties I dumped everything, did new downloads and upzips of of factory image, platform-tools, and got new twrp.img, twrp.zip and magisk.zip. Checkedsum on all of them I could.
No. It never occurred to me to fastboot factory image to both slots. I guess I just assumed that The Google (tm) would know what they were doing. Thank you for that. I will give it a shot in the morning. I need enough lead time to fix it if it breaks because my life and office are on that phone.
And now, after learning how to see which slot is active I can learn how to flash to both! Thanks a lot.
Click to expand...
Click to collapse
Just a little additional FYI...if you want to keep twrp as your recovery, flash the same image file, NOT the twrp zip file, once you enter twrp after fastbooting it.
And, if you want to know what slot your currently on, the command is...fastboot getvar all. Best of luck to you :good:

Better and better. Now I have no USB. When I go to it in Settings ALL usb prefs are greyed out. Needless to say I haven't tried to flash anything because I can't. So I guess a factory reset is in my future. At least I copied my SD card and Titanium Backup folder. /sigh
Safe mode makes no difference.
If anyone knows how to get the USB working without wiping that would be appreciated.
Oh, and in other "It ain't workin' rite" news, it keeps going back to pixel launcher instead of Nova.
I had a crappy day and now I'm going to bed.

Welp! The Google (tm) is sending my replacement phone...

TWRP 3.3.0.0 Issue on Android 10
My phone is Google Pixel 2XL that is runnung under Android 10 and TWRP 3.3.0.0 img and installer.
I was unable to backup any ROM file under TWRP Recovery.
The error is "Backup Name is: 'PixelDust--14-59-50'
I:Backup_Folder is: '/data/media/0/TWRP/BACKUPS/710KPAE0324504/PixelDust--14-59-50'
I:Calculating backup details...
* Total number of partitions to back up: 3
* Total size of all data: 7486MB
* Available space: 46798MB
[BACKUP STARTED]
* Backup Folder: /data/media/0/TWRP/BACKUPS/710KPAE0324504/PixelDust--14-59-50
Invalid encryption mode 'ice:aes-256-heh'
Failed to mount '/system' (Invalid argument)
I:Actual block device: '/dev/block/bootdevice/by-name/system_a', current file system: 'ext4'
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/710KPAE0324504/PixelDust--14-59-50/recovery.log"
I had tried to flash Magisk.img but it did not work due to error.
The error log is "- Device platform: arm64-v8a
- Copying image to cache
1566+0 records in
1566+0 records out
1603584 bytes (1.5 M) copied, 0.006409 s, 239 M/s
1045+1 records in
1045+1 records out
1070668 bytes (1.0 M) copied, 0.004831 s, 211 M/s
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Unsupported/Unknown image format
! Installation failed"
I was unable to root on my phone.
How can I fix these issues?

Touareg2013 said:
My phone is Google Pixel 2XL that is runnung under Android 10 and TWRP 3.3.0.0 img and installer.
I was unable to backup any ROM file under TWRP Recovery.
The error is "Backup Name is: 'PixelDust--14-59-50'
I:Backup_Folder is: '/data/media/0/TWRP/BACKUPS/710KPAE0324504/PixelDust--14-59-50'
I:Calculating backup details...
* Total number of partitions to back up: 3
* Total size of all data: 7486MB
* Available space: 46798MB
[BACKUP STARTED]
* Backup Folder: /data/media/0/TWRP/BACKUPS/710KPAE0324504/PixelDust--14-59-50
Invalid encryption mode 'ice:aes-256-heh'
Failed to mount '/system' (Invalid argument)
I:Actual block device: '/dev/block/bootdevice/by-name/system_a', current file system: 'ext4'
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/710KPAE0324504/PixelDust--14-59-50/recovery.log"
I had tried to flash Magisk.img but it did not work due to error.
The error log is "- Device platform: arm64-v8a
- Copying image to cache
1566+0 records in
1566+0 records out
1603584 bytes (1.5 M) copied, 0.006409 s, 239 M/s
1045+1 records in
1045+1 records out
1070668 bytes (1.0 M) copied, 0.004831 s, 211 M/s
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Unsupported/Unknown image format
! Installation failed"
I was unable to root on my phone.
How can I fix these issues?
Click to expand...
Click to collapse
You really can't fix it until, and if, twrp is updated to deal with the new partition system that google implemented with A10. However, you can try this slightly outdated adb method that still works
https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/

Stuck in boot loop - need magisk_patched file Pixel 2 XL (QQ3A.200805.001, Aug 2020)

Dear XDA-Developers, after installing August 2020 update for my Pixel 2 XL and possibly applying incorrect Magisk bootloader version, my phone doesn't boot anymore and is constantly stuck in bootscreen animation.
What I have tried so far to no result:
- Re-flashing both May 2020 (previous working version) and August 2020 without -w flag to preserve my data that I would ideally like to recover.
- Side-loading May 2020 and August 2020 OTA versions through TWRP
- Creating and booting from Magisk-core only image as per guide called "How to Create & Boot from a Magisk Core-Only Image to Fix a Bootloop Without Custom Recovery" (since I cannot post links in here).
While unpacking and repacking Magisk-core image I noticed that "BOARD_OS_PATCH_LEVEL 2020-05" indicating that I might have had the wrong version applied to it.
So looks like my only hope is finding magisk_patched.img file for August 2020 Pixel 2 XL (image-taimen-qq3a.200805.001) and trying to patch it to disable Magisk upon startup. Would anybody be so kind to post one here?
I have also tried to make data backup using TWRP, but it fails mounting /data partition and shows that it's 0 Mb.
Any other ideas to how to save the phone without wiping all the data would be greatly appreciated.
Thank you all very much for whatever suggestions you might have to help me!

hencrow said:
So looks like my only hope is finding magisk_patched.img file for August 2020 Pixel 2 XL (image-taimen-qq3a.200805.001) and trying to patch it to disable Magisk upon startup. Would anybody be so kind to post one here?
Click to expand...
Click to collapse
Magisk doesn't touch the bootloader, only modifying the boot image. Given your description of the issue, I don't believe Magisk to be the culprit here. Based upon personal experience, flashing a stock image using flash-all.bat, whether the -w flag is present or absent, totally removes Magisk as the stock boot image overwrites the modified version created by Magisk.
It's clear though that you have an issue, but how much of it is brought about by misconceptions and incorrect knowledge is unknown and at this point irrelevant. So what do you do now? Try backing up your data using the instructions here. But be prepared for the very real possibility that you have already lost all your data, and only a stock ROM install with the -w flag present will restore the device to working order.

Strephon Alkhalikoi said:
So what do you do now? Try backing up your data using the instructions URL. But be prepared for the very real possibility that you have already lost all your data, and only a stock ROM install with the -w flag present will restore the device to working order.
Click to expand...
Click to collapse
Thanks for getting back. I'm a little confused how can adb backup can work though if the only thing I can boot into is TWRP and even it fails to decrypt /data partition (it just shows "Could not mount /data and unable to find crypto footer" upon startup).
And with my very limited Android debugging experience wondering if things are really that hopeless that it's not possible to simply copy and decrypt user data partition or there aren't even any logs from failed Android boot attempts that can be looked at to at least diagnose the issue.

hencrow said:
Thanks for getting back. I'm a little confused how can adb backup can work though if the only thing I can boot into is TWRP and even it fails to decrypt /data partition (it just shows "Could not mount /data and unable to find crypto footer" upon startup).
And with my very limited Android debugging experience wondering if things are really that hopeless that it's not possible to simply copy and decrypt user data partition or there aren't even any logs from failed Android boot attempts that can be looked at to at least diagnose the issue.
Click to expand...
Click to collapse
It may not work, and in fact it probably won't, especially if TWRP can't mount the data partition. That's why I said you should be prepared for the very real possibility that you have lost all your data. As for getting logs to diagnose the issue, the only certain way to get a catlog is to record the logcat from the device on your PC as you boot it, via USB Debugging. Something that likely will not be of much help now, given what you have tried doing to resolve the issue.
At this point, in your position I would simply cut my losses and install a factory image and let it wipe the data. Once you are back up and running, you want to get into the habit of backing up app data. There are many apps that can do this, but regardless of the app used, backing up the app data to internal storage or to a location like Mega or Dropbox will make life easier if you ever encounter this again.

An update if anybody is wondering what happened - flashing Android 11 Beta 3 brought the phone back to life with all the data intact. All versions of Android 10 haven't even reached the booting stage where adbd was started and showed no logs.