It is now
Oh cool! :good:It is now
Q comes with a read only ext4 file system to prevent /system being modified.
Sooo. . . . .
- Boot into Twrp
- Backup System Image
- Enter Wipe > Advanced Wipe & Select System > Repair or Change File System > Change File System > Select EXT4 > Swipe to Change. This will format /system to good old standard , writable EXT4 file system.
- Restore System Image
Next time you boot twrp you can mount (and modify) /system:highfive:
I ran the scripts/codes manually in the trwp root shell (with the no working touch screen).
Yep, running the script earlier (permissive.sh) did the trick (*.ko files in the ramdisk).
And 3 is the output of the panel_id (that's why I removed the 3 from the preptouch.sh).
Edit: I've noticed this...
The permissions of the libs copied from vendor to sbin (preptouch), as you could see here
-rw------- 1 root root 1070630 1972-01-22 17:46 clearpad_core.ko -rw------- 1 root root 251702 1972-01-22 17:46 clearpad_i2c.ko -rw------- 1 root root 296934 1972-01-22 17:46 clearpad_rmi_dev.ko
-rwxrwxrwx 1 root root 1070902 2020-04-02 21:48 clearpad_core.ko -rwxrwxrwx 1 root root 251830 2020-04-02 21:48 clearpad_i2c.ko -rwxrwxrwx 1 root root 297054 2020-04-02 21:48 clearpad_rmi_dev.ko
Edit 2: chmod on copied files did the trick (preptouch.sh) - but sometimes still not working (need to boot twice, three times...):
Maybe you find out a more elegant way to handle with that!Code:
#XZ2 "3" XZ2C "4" Clearpad if [[ "$touch_id" == "3" ]] || [[ "$touch_id" == "4" ]]; then cp /v/lib/modules/clearpad_rmi_dev.ko /sbin/ cp /v/lib/modules/clearpad_core.ko /sbin/ cp /v/lib/modules/clearpad_i2c.ko /sbin/ [B]chmod 777 /sbin/clearpad_rmi_dev.ko chmod 777 /sbin/clearpad_core.ko chmod 777 /sbin/clearpad_i2c.ko[/B] insmod /sbin/clearpad_rmi_dev.ko insmod /sbin/clearpad_core.ko insmod /sbin/clearpad_i2c.ko echo 1 > /sys/devices/virtual/input/clearpad/post_probe_start fi
I also got it permanently installed on kernel (combo keys does work, too), it's a bit tricky I gotta say, but it works.
You know, twrp's ramdisk.cpio kernel hack (old install procedure).
my story -> updated my xz2 to "52.1.A.0.618_R5C" after that i unlocked the boot loader....
# i went into fastboot mode by holding vol up and inserted the cable... blue light it and i was in fastboot mode from there i (twrp stock)
"fastboot boot twrp-xz2.img" i booted into twrp now from here i flashed the pixel experience rom but after successful installation of the rom i rebooted my device but it now stuck at sony logo i tried this many times... even flashed the stock rom using flashtool and retried everything but no luck please can anyone tell me what im doing wrong....
i came from z2 force (motorola) which was quite easy to handle but cant handle this xz2
thankyou and stay safe.......
check check and check!
#include <std_disclaimer.h> /* * * We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at us for messing up your device, we will laugh at you. * */
logcat -b all
thanks to the fixes in 3.4.0 we got now a twrp with the following enhancements for stock and sodp:
- this twrp will work with future 10.0 roms, you don't need a new build matching the security patch level of your rom.
- you can install this twrp again with the buildin ramdisk patcher. Please follow the installation instructions.
switch to twrp 3.4.0
sodp twrp 2020-06 security patch level
stock twrp 2020-05 security patch level for firmware 52.1.a.2.1
now both twrp should work without a rom being installed (empty system/vendor/oem partitions) and still be able to decrypt your userdata.
Also the stock twrp touch should now always work instead of playing russian roulette.
sodp twrp for 2020-03 security patch level
installing in ramdisk (to make it persistent) is impossible at the moment, because it is a 9.0 twrp which makes its ramdisk incompatible to the rom.
Of course monthly twrp releases in sync with the current patch level need to be released or i would need to remove the userdata decryption completely.
The stock twrp will follow, after it became ready.