I tried, unfortunately I got the same errorAfter rm -rf, reboot recovery and format data again without check rm-rf. I tested it on my op5 and it worked.
Mine is a 5t
I tried, unfortunately I got the same errorAfter rm -rf, reboot recovery and format data again without check rm-rf. I tested it on my op5 and it worked.
Your logs are showing this info "I:recv error on uevent" which apparently occurs on devices with some partition failure.
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?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.
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 happensFirst 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.
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.
Use pastebin instead https://pastebin.com/That's exactly what I did with the attach file.
It is also uploaded, but it is not attached to the post.
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.
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.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 logcatC:\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:
by-name
entries: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
/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)/system
is accessible when booted (Currently using CrDroid v7.21 A11). Rebooting to recovery too doesn't help.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/systemThanks @faoliveira for maintaining TWRP for Oneplus 5T, I tried3.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 usingadb logcat -c
. After that I started collecting logs and from TWRP's "Mount" option, mounteddata, 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 theby-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
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
find / -name 'webview' -type d
to find the location of any app/folder which I know would be present in the system official 3.6.2_9.0
still mounts at /system
location3.6.2-v2
today and confirmed the location in recovery. It seems this change was made for version _11.0
and up which is why I was not able to find it yesterday.My trees are already on Teamwin's github, but A12 builds have not yet been released for any device, it looks like they will be released very soon. I'll let you know in this thread when there's an official release.Thanks a lot for maintaining TWRP for our devices! Great!
Would you please tell me if the official on TWRP website is out of your hands as well, are all changes from V8 test version included there?
I was informed of this a few days ago, I already have a solution, but unfortunately I couldn't send it in time and the new official version, which should be released in the next few days, will not come out with this fix. I'm just waiting for this release to make an alternative version available for anyone using LOS20 or another A13 Rom that uses the same kernel with these modifications. I just ask to wait a few more days, anyway thanks for letting me know.Hello,
Would it be possible to implement into TWRP the change in the ext4 mount options from Lineage as it is mentioned in this post https://xdaforums.com/t/rom-13-0-on...5-4-october-2022.4480549/page-8#post-87527169 ?
Kernel source: https://github.com/roberto-sartori-gl/kernel_oneplus_msm8998
Thank you very much for your work. I really appreciate it.
For some reason the decryption process is starting late on your device, in the end it decrypts and despite the red messages you shouldn't have any problems performing any function in TWRP. Did you happen to do a dirty flash between installing the different ROMs? The ideal is always to do a clean flash when changing ROMs.I have some strange issue. I updated to the latest version just to be sure, but I'm getting the same.
On opening I get a lot of red text with these messages:
Bash:Updating partition details... Error opening: '/data/data/S2NA3BATPQx7yQYFTtLuwUICgpQvgzp,2Y3rpzYXwTI/2QUNnMlm2Lzsszj3jihli3bvY+qOQTan/sOA+sQ5c59i7W1T2pLryop75d8lkTLwCI0CYiD/+t,MrNGJcfPsD1RoudFUfTjb+jUauDrRcvLCyvgIO49qjJ8Z3XYmBYOKKg9SvX5Ai4kiVhwxdbt8Wq0uNF8xu1XQgaDs8o7bvXXsb,ravgHTbOrpyMfZ06wJRrprSo,LtajOgYZxPDzUQ95kgLadbcSAmRvqzqvSFd1JqaAD+lJk6aVSP7gcjYXFF8aZ942q8jpBS9JXVA6YlaAi8J6vAFhcaDomoAVBjG5WK22HhvOKkfy6loc7RByaGuFO' (No such file or directory) I:Real error: Unable to stat
For some reason my data partition is also seen as 1061063MB, making it impossible to backup.
View attachment 6091142
I have already formatted the data partition since the problem first showed up. Before I was on Derp, now on Elixir 4.1 - so same kind off base -> A14, 4.4 kernel.
Any idea?
The issue of not mounting the /data partition is due to AOSP14 which has some patches in the kernel that are not compatible with previous versions of TWRP, this was one of the reasons that led me to update the recovery. 3.7.1_12-1 should mount the partition normally.Ah yes, I remember reading some command like that and it was the issue. It's backing up now.
I was using Apatch before, so I'll remember to runbefore a backup. Got it.Code:ksud module shrink
To complete the story: I was running latest derp 18/04, but had some issues with maintaining a stable bluetooth connection to my Garmin Edge. I went over to AOSP14, I don't remember if I tried Xkernel directly but that did something funky to my /data partition. I was unable to mount it in recovery.
I was happy to have the most important folders backed up and wiped data, but apparently it didn't solve all the problems.
Do you think that removing/readding pin and/or wiping data again would help - although it doesn't really seem a problem in the end?
* If you want to test these recoveries
fastboot boot twrp-3.7.1_12-1-cheeseburger_dumpling.img
* If you want to use then
fastboot flash recovery twrp-3.7.1_12-1-cheeseburger_dumpling
Problem solved, if you want, you can now use version A12.1 v.5Fails to mount Data on my OP5T F2FS switched to old recovery and now OK
Using LineageOS 19.1
In the end I got the sense that I can cancel decrypt attempt and flash from /data/lineage_updates
But anyway I tried sideload again.
I'm using a macbook pro (m1) and found that if I connect to port on the right side it won't do `adb devices` in recovery or `fastboot devices` in fastboot.
but if I connect to the left it did manage to do it. (using A11 3.6.2-v1).
when using A12 3.6.2-12-v4
This is what I tried, and what it produced.
Code:❯ adb devices * daemon not running; starting now at tcp:5037 * daemon started successfully List of devices attached 10499fc7 device ❯ adb reboot recovery ❯ adb devices List of devices attached ❯ adb kill-server ❯ adb devices * daemon not running; starting now at tcp:5037 * daemon started successfully List of devices attached ❯ adb sideload lineage-19.1-20220606-nightly-cheeseburger-signed.zip adb: sideload connection failed: no devices/emulators found adb: trying pre-KitKat sideload method... adb: pre-KitKat sideload connection failed: no devices/emulators found