faoliveira said:

After rm -rf, reboot recovery and format data again without check rm-rf. I tested it on my op5 and it worked.

I tried, unfortunately I got the same error
Mine is a 5t

nguyenlucky said:

I tried, unfortunately I got the same error
Mine is a 5t

Your logs are showing this info "I:recv error on uevent" which apparently occurs on devices with some partition failure.
Doing some searching I found the following correction suggestions:
- Trying to format without decrypting the device first (when decryption screen appears, press cancel);
- Use MSMTOOL to go back to stock and start the whole unlocking process again; or
try performing following steps:
1. Go to recovery and wipe cache, system, & data.
2. Then go to repair and repair system & data.
3. Now try to format
I hope one of these solutions works.

yaladag said:

Hello all,
I need our help.
I can`t install any zip-files on my devices.
What is the problem ?
I habe install the v8 test recovery.

You need to provide more details. What message do you get when you try to install? Ideally, you should generate your logs (recovery and logcat) immediately after trying and posting here. Using ADB sideload can you install? What rom are you using?

yaladag said:

First of all, thank you for your answer.
I have installed the [STABLE] [12.0] Official Pixel Experience 12 - OnePlus 5 & 5T [DUMPLING + CHEESEBURGER].
I get the message in Recovery when I try to install that I have an invalid zip file format.
I have not yet tried it via ADB Sideload. I have attached the recovery log.

Well, while you can't upload, does it happen with any zip file? Try downloading a fresh copy of the file or installing via adb to see what happens

yaladag said:

How can I upload a file here ?

By using the button that says "Attach files" if you want to add a log, or by simply clicking on the "Insert Image" icon next to the emoji one.

yaladag said:

That's exactly what I did with the attach file.
It is also uploaded, but it is not attached to the post.

Use pastebin instead https://pastebin.com/

faoliveira said:

A11 - Last update 3.6.2-v2 (06/07/2022)
5/5T - twrp_cheeseburger_dumpling_3.6.2_11-v2.img

Bugs:
A11:
- Only decrypts A12 or A13 data, If screen lock is removed.

C:\Users>adb logcat
--------- beginning of kernel
09-07 18:56:39.226     0     0 D [20220907_18:56:39.226289]@2 logd: logdr: UID=0 GID=0 PID=689 b tail=0 logMask=99 pid=0 start=0ns timeout=0ns
09-07 18:56:46.087     0     0 E [20220907_18:56:46.087219]@1 synaptics,s3320: all finger up
09-07 18:56:46.105     0     0 I         : [20220907_18:56:46.104874]@5 EXT4-fs (sda13): mounted filesystem with ordered data mode. Opts: barrier=1,noauto_da_alloc
09-07 18:56:46.701     0     0 I         : [20220907_18:56:46.701015]@5 EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: barrier=1
09-07 18:56:48.971     0     0 I         : [20220907_18:56:48.970800]@6 EXT4-fs (sde21): mounted filesystem without journal. Opts:
09-07 18:56:49.498     0     0 I         : [20220907_18:56:49.498293]@4 EXT4-fs (sdf6): mounted filesystem without journal. Opts:

dumpling:/dev/block/platform/soc/1da4000.ufshc/by-name # ls -l | grep -e 'sda13' -e 'sda3' -e 'sde21' -e 'sdf6'
lrwxrwxrwx 1 root root 15 1970-08-17 09:36 cache -> /dev/block/sda3
lrwxrwxrwx 1 root root 16 1970-08-17 09:36 system -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 1970-08-17 09:36 userdata -> /dev/block/sda13
lrwxrwxrwx 1 root root 15 1970-08-17 09:36 vendor -> /dev/block/sdf6

M4Master96 said:

Thanks @faoliveira for maintaining TWRP for Oneplus 5T, I tried 3.6.2-v2 build but somehow I am unable to access /system partition when in recovery. Sorry for long post as I am trying to provide as much info as I can.

For testing, I unmounted all partitions from recovery and also cleared logcat using adb logcat -c. After that I started collecting logs and from TWRP's "Mount" option, mounted data, cache, system and vendor partitions and the same was visible in logcat

Code:

C:\Users>adb logcat
--------- beginning of kernel
09-07 18:56:39.226     0     0 D [20220907_18:56:39.226289]@2 logd: logdr: UID=0 GID=0 PID=689 b tail=0 logMask=99 pid=0 start=0ns timeout=0ns
09-07 18:56:46.087     0     0 E [20220907_18:56:46.087219]@1 synaptics,s3320: all finger up
09-07 18:56:46.105     0     0 I         : [20220907_18:56:46.104874]@5 EXT4-fs (sda13): mounted filesystem with ordered data mode. Opts: barrier=1,noauto_da_alloc
09-07 18:56:46.701     0     0 I         : [20220907_18:56:46.701015]@5 EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: barrier=1
09-07 18:56:48.971     0     0 I         : [20220907_18:56:48.970800]@6 EXT4-fs (sde21): mounted filesystem without journal. Opts:
09-07 18:56:49.498     0     0 I         : [20220907_18:56:49.498293]@4 EXT4-fs (sdf6): mounted filesystem without journal. Opts:

The mount points also matched with the by-name entries:

Code:

dumpling:/dev/block/platform/soc/1da4000.ufshc/by-name # ls -l | grep -e 'sda13' -e 'sda3' -e 'sde21' -e 'sdf6'
lrwxrwxrwx 1 root root 15 1970-08-17 09:36 cache -> /dev/block/sda3
lrwxrwxrwx 1 root root 16 1970-08-17 09:36 system -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 1970-08-17 09:36 userdata -> /dev/block/sda13
lrwxrwxrwx 1 root root 15 1970-08-17 09:36 vendor -> /dev/block/sdf6

But somehow when I try to access /system partition via TWRPs "File Manager" or via shell, it doesn't show any actual folders like 'app', 'priv-app', 'product', etc (Attaching Screenshot as reference)

Not sure what I am missing as the /system is accessible when booted (Currently using CrDroid v7.21 A11). Rebooting to recovery too doesn't help.

Can you please help (if there is anything) ?

Regards,
M4Master96

Click to expand...

Inside recovery the system folder is where some files are needed for recovery to work: init, decryption, etc. The system partition you are looking for is inside /system_root/system