search

xxroot / android_device_motorola_pokerp

1 stars 1 forks source link

The ROM of this device is convenient for everyone to study and decrypt FBE #1

Open xxroot opened 3 years ago

xxroot commented 3 years ago

The ROM of this device is convenient for everyone to study and decrypt FBE E6 plus rom.7z

lopestom commented 3 years ago

Downloaded file. Now i need time to unpack and looking files about enc/dec. Wait patiently... Ah. You need invite me as contributor or collaborate in your device tree.

xxroot commented 3 years ago

Ok, let me know how to invite you

lopestom commented 3 years ago

Ok, let me know how to invite you

Great. How you see I adc very files and informations in the device tree. I need time for including more information but need write correctly informations about enc/dec. Unfortunately I not have much time and you need wait my free time.

Cheers.

xxroot commented 3 years ago

Ok, let me know how to invite you

Great. How you see I adc very files and informations in the device tree. I need time for including more information but need write correctly informations about enc/dec. Unfortunately I not have much time and you need wait my free time.

Cheers.

ok,I haven't had much time lately

Cheers.

lopestom commented 3 years ago

Ok, let me know how to invite you

Great. How you see I adc very files and informations in the device tree. I need time for including more information but need write correctly informations about enc/dec. Unfortunately I not have much time and you need wait my free time. Cheers.

ok,I haven't had much time lately

Cheers.

Maybe you want test compiled file?! https://github.com/lopestom/android_device_motorola_pokerp/releases/tag/1479606770

Good luck. 😏

xxroot commented 3 years ago

Does not work, stays in the TWRP page cannot enter.

xxroot commented 3 years ago

`logcat

--------- beginning of main 07-18 02:09:37.193 322 323 I adbd : initializing functionfs 07-18 02:09:37.193 322 323 I adbd : opening control endpoint /dev/usb-ffs/adb/ep0 07-18 02:09:37.200 322 323 I adbd : functionfs successfully initialized 07-18 02:09:37.200 322 323 I adbd : registering usb transport 07-18 02:09:37.202 322 324 E cutils-trace: Error opening trace file: No such file or directory (2) 07-18 02:09:31.221 321 321 W auditd : type=2000 audit(0.0:1): initialized 07-18 02:09:31.912 321 321 I auditd : type=1403 audit(0.0:2): policy loaded auid=4294967295 ses=4294967295 07-18 02:09:31.912 321 321 W auditd : type=1404 audit(0.0:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 07-18 02:09:31.960 1 1 W init : type=1400 audit(0.0:4): avc: denied { setcheckreqprot } for scontext=u:r:init:s0 tcontext=u:object_r:kernel:s0 tclass=security permissive=0 07-18 02:09:31.964 1 1 W init : type=1400 audit(0.0:5): avc: denied { write } for name="kernel_init_done" dev="sysfs" ino=11709 scontext=u:r:init:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=0 07-18 02:09:32.144 1 1 W init : type=1400 audit(0.0:6): avc: denied { setattr } for name="system" dev="rootfs" ino=8588 scontext=u:r:init:s0 tcontext=u:object_r:rootfs:s0 tclass=lnk_file permissive=0 07-18 02:09:32.148 1 1 W init : type=1400 audit(0.0:7): avc: denied { mounton } for path="/mnt/vendor/persist" dev="tmpfs" ino=9253 scontext=u:r:init:s0 tcontext=u:object_r:mnt_vendor_file:s0 tclass=dir permissive=0 07-18 02:09:32.152 1 1 W init : type=1400 audit(0.0:8): avc: denied { module_request } for kmod="fs-functionfs" scontext=u:r:init:s0 tcontext=u:r:kernel:s0 tclass=system permissive=0 07-18 02:09:32.156 1 1 W init : type=1400 audit(0.0:9): avc: denied { write } for name="bootprof" dev="proc" ino=4026532169 scontext=u:r:init:s0 tcontext=u:object_r:proc:s0 tclass=file permissive=0 07-18 02:09:32.156 1 1 W init : type=1400 audit(0.0:10): avc: denied { write } for name="bootprof" dev="proc" ino=4026532169 scontext=u:r:init:s0 tcontext=u:object_r:proc:s0 tclass=file permissive=0 07-18 02:09:37.180 321 321 I init : type=1400 audit(0.0:42): avc: denied { entrypoint } for path="/sbin/logd" dev="rootfs" ino=8441 scontext=u:r:logd:s0 tcontext=u:object_r:rootfs:s0 tclass=file permissive=1 07-18 02:09:37.180 321 321 I logd : type=1400 audit(0.0:43): avc: denied { read execute } for path="/sbin/logd" dev="rootfs" ino=8441 scontext=u:r:logd:s0 tcontext=u:object_r:rootfs:s0 tclass=file permissive=1 07-18 02:09:37.184 321 321 I logd : type=1400 audit(0.0:44): avc: denied { getattr } for path="/sbin/logd" dev="rootfs" ino=8441 scontext=u:r:logd:s0 tcontext=u:object_r:rootfs:s0 tclass=file permissive=1 07-18 02:09:37.184 321 321 I logd : type=1400 audit(0.0:45): avc: denied { open } for path="/sbin/ld.config.txt" dev="rootfs" ino=8344 scontext=u:r:logd:s0 tcontext=u:object_r:rootfs:s0 tclass=file permissive=1 07-18 02:09:37.192 1 1 I init : type=1400 audit(0.0:46): avc: denied { write } for name="saving" dev="sysfs" ino=12883 scontext=u:r:init:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1 07-18 02:09:37.192 1 1 I init : type=1400 audit(0.0:47): avc: denied { open } for path="/sys/devices/platform/mt_usb/saving" dev="sysfs" ino=12883 scontext=u:r:init:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1`

`recovery.log

pokerp:/tmp # cat recovery.* Starting TWRP 3.6.0_9-0-7671140b on Sat Jul 18 02:09:32 2020 (pid 293) I:=> product model: 'Moto E6 Plus' I:=> using device id: 'Moto_E6_Plus' RECOVERY_SDCARD_ON_DATA := true I:Lun file '/sys/class/android_usb/android0/f_mass_storage/lun0/file' does not exist, USB storage mode disabled TW_INCLUDE_CRYPTO := true I:Find_File: Error opening '/sys/class/backlight' I:Found brightness file at '/sys/class/leds/lcd-backlight/brightness' I:Got max brightness 255 from '/sys/class/leds/lcd-backlight/max_brightness' I:TWFunc::Set_Brightness: Setting brightness control to 255 I:LANG: en Starting the UI... setting DRM_FORMAT_RGB565 and GGL_PIXEL_FORMAT_RGB_565 cannot find/open a drm device: No such file or directory fb0 reports (possibly inaccurate): vi.bits_per_pixel = 32 vi.red.offset = 0 .length = 8 vi.green.offset = 8 .length = 8 vi.blue.offset = 16 .length = 8 setting GGL_PIXEL_FORMAT_RGBA_8888 double buffered framebuffer: 0 (720 x 1560) Using fbdev graphics. I:TWFunc::Set_Brightness: Setting brightness control to 255 TW_SCREEN_BLANK_ON_BOOT := true I:TWFunc::Set_Brightness: Setting brightness control to 0 I:TWFunc::Set_Brightness: Setting brightness control to 255 I:Loading package: splash (/twres/splash.xml) I:Load XML directly I:PageManager::LoadFileToBuffer loading filename: '/twres/splash.xml' directly I:Checking resolution... I:Scaling theme width 0.666667x and height 0.812500x, offsets x: 0 y: 0 w: 0 h: 0 I:Loading resources... I:Loading variables... I:Loading mouse cursor... I:Loading pages... I:Loading page splash I:Switching packages (splash) => Linking mtab => Processing /etc/recovery.fstab for SAR-detection I:Reading /etc/recovery.fstab I:Done processing fstab files I:SAR-DETECT: SAR System detected => Processing /etc/recovery.fstab I:Reading /etc/recovery.fstab I:Processing '/boot' I:Processing '/recovery' I:Processing '/dtbo' I:Processing '/system_image' I:Processing '/vendor_image' I:Processing '/vbmeta' I:Processing '/metadata' I:Processing '/persist' I:Created '/persist' folder. I:Processing '/persist_image' I:Processing '/misc' I:Processing '/system_root' I:Processing '/vendor' I:Processing '/cache' I:Processing '/data' I:FBE contents 'aes-256-cts', filenames '' I:Processing '/external_sd' I:Created '/external_sd' folder. I:Processing '/usb_otg' I:Created '/usb_otg' folder. I:Done processing fstab files I:Setting up '/data' as data/media emulated storage. I:mount -o bind '/data/media' '/sdcard' process ended with RC=0 I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0 I:File Based Encryption is present e4crypt_initialize_global_de Determining wrapped-key support for /data fbe.data.wrappedkey = false calling retrieveAndInstallKey Key exists, using: /data/unencrypted/key `

lopestom commented 3 years ago

Does not work, stays in the TWRP page cannot enter.

Device wiped cache&Davilk and Data with stock recovery? Maybe Format Data with first TWRP and install img has any lucky?

We need confirm with device reset. If not work so we need look any "problem" with files and scripts.

xxroot commented 3 years ago

Yeah, I did what you asked, and he's still not working,

lopestom commented 3 years ago

. I:Processing '/usb_otg' I:Created '/usb_otg' folder. I:Done processing fstab files I:Setting up '/data' as data/media emulated storage. I:mount -o bind '/data/media' '/sdcard' process ended with RC=0 I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0 I:File Based Encryption is present e4crypt_initialize_global_de Determining wrapped-key support for /data fbe.data.wrappedkey = false calling retrieveAndInstallKey Key exists, using: /data/unencrypted/key

You gave me recovery.bin files and the kernel [8,21 MB (8.617.518 bytes)] of this file is different from the kernel [9,12 MB (9.571.180 bytes)] that is in your initial device tree. So the question is: What is the real version of your device? Moto E6 Plus or moto e(6) plus??

lopestom commented 3 years ago

New attempt: https://github.com/lopestom/android_device_motorola_pokerp/releases/tag/1483556241

xxroot commented 3 years ago

New attempt: https://github.com/lopestom/android_device_motorola_pokerp/releases/tag/1483556241

This version does not boot at all. Not even a TWRP LOGO

xxroot commented 3 years ago

New attempt: https://github.com/lopestom/android_device_motorola_pokerp/releases/tag/1483556241 This is where the problem is likely to arise TW_INCLUDE_FBE_METADATA_DECRYPT := true

lopestom commented 3 years ago

New attempt: https://github.com/lopestom/android_device_motorola_pokerp/releases/tag/1483556241 This is where the problem is likely to arise TW_INCLUDE_FBE_METADATA_DECRYPT := true

The recovery.bin that you send from first message not the same configuration of BoardConfig. The cmdline of bin file has 64S3,32S1,32S1. The BoardConfig has 64S3,32N2,64N2. Again, what information, file is correct?! Try it: https://github.com/lopestom/android_device_motorola_pokerp/releases/tag/1483854526

lopestom commented 3 years ago

Again, but now I had a new way/ideia. Read about: https://github.com/lopestom/android_device_motorola_pokerp/releases/tag/PBRP_TWRP-9.0

xxroot commented 3 years ago

I can guarantee that the ROM is backed up from my mobile phone. There is no mistake in this. I have swiped the recovery provided by you, which seems to be no different from what I released in XDA

xxroot commented 3 years ago

Decryption is still not working

lopestom commented 3 years ago

Decryption is still not working

What file the TWRP started?

xxroot commented 3 years ago

解密仍然无效

TWRP 启动的文件是什么？

FBRP recovery https://forum.xda-developers.com/attachments/img_20211116_100158-jpg.5459477/ It's exactly the same as the TWRP page I posted

lopestom commented 3 years ago

解密仍然无效

TWRP 启动的文件是什么？

FBRP recovery https://forum.xda-developers.com/attachments/img_20211116_100158-jpg.5459477/ It's exactly the same as the TWRP page I posted

I need know what file started: https://github.com/lopestom/android_device_motorola_pokerp/releases/tag/PBRP_TWRP-9.0

Or https://github.com/lopestom/android_device_motorola_pokerp/releases/tag/1483854526

xxroot commented 3 years ago

1：github.com/lopestom/android_device_motorola_pokerp/releases/tag/PBRP_TWRP-9.0 This is the same as the one I posted in XDA, without decryption

2：github.com/lopestom/android_device_motorola_pokerp/releases/tag/1483854526 This is the cannot be started to TWRP, TWRP logo will not appear at all

lopestom commented 3 years ago

1：github.com/lopestom/android_device_motorola_pokerp/releases/tag/PBRP_TWRP-9.0 This is the same as the one I posted in XDA, without decryption

2：github.com/lopestom/android_device_motorola_pokerp/releases/tag/1483854526 This is the cannot be started to TWRP, TWRP logo will not appear at all

This file was described for testing as the intention to compile a new TWRP was not possible. This is all due to the difference between the recovery.bin file and the "moto e(6) plus-TWRP-9.0" file (Which is actually PBRP) on your device. Therefore, your device tree should be based on the recovery.bin file coming from the [E6 plus rom.7z] file. So notice that the TWRP-9 you have is configured with 64S3,32N2,64N2. But the recovery.bin file is configured with 64S3.32S1.32S1. So there is a disparity of information and this can make TWRP start or not on the device.

I won't worry about it. I'm going to take your TWRP-9 file and try to get enc/desc to work. But your TWRP-9 doesn't have settings like we inserted in the device tree. So files to encrypt/decrypt are missing.

The solution: try to get the device tree to create a TWRP to start. With that we can get something with the encrypt/decrypt. See the differences for recovery.bin and TWRP-9: recovery.bin bootopt=64S3,32S1,32S1 buildvariant=user ro.product.model=moto e(6) plus | ro.product.brand=motorola | ro.product.name=pokerp_reteu | ro.product.device=pokerp | ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete | use ro.product.cpu.abilist instead. | ro.product.cpu.abi=armeabi-v7a | ro.product.cpu.abi2=armeabi | ro.product.cpu.abilist=armeabi-v7a,armeabi | ro.product.cpu.abilist32=armeabi-v7a,armeabi | ro.product.cpu.abilist64= | ro.vendor.product.cpu.abilist=armeabi-v7a,armeabi | ro.vendor.product.cpu.abilist32=armeabi-v7a,armeabi | ro.vendor.product.cpu.abilist64= | persist.sys.dalvik.vm.lib.2=libart.so | dalvik.vm.isa.arm.variant=cortex-a53

TWRP-9.img = PBRP bootopt=64S3,32N2,64N2 buildvariant=eng ro.product.model=Moto E6 Plus | ro.product.brand=motorola | ro.product.name=omni_pokerp | ro.product.device=pokerp | ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete | use ro.product.cpu.abilist instead. | ro.product.cpu.abi=arm64-v8a | ro.product.cpu.abilist=armeabi-v7a,armeabi | ro.product.cpu.abilist32=armeabi-v7a,armeabi | ro.product.cpu.abilist64= | persist.sys.dalvik.vm.lib.2=libart.so | dalvik.vm.isa.arm64.variant=cortex-a53 | dalvik.vm.isa.arm64.features=default | dalvik.vm.isa.arm.variant=cortex-a53

So I'm going to require a fully functional device tree like the TWRP-9(PBRP) and so we'll go further. But with a device tree with bad information and which is not based on the TWRP-9 file (PBRP). I know this because I see two situations in the device tree:

# Architecture
TARGET_ARCH := arm
TARGET_ARCH_VARIANT := armv7-a-neon
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_CPU_VARIANT := generic
# Kernel
BOARD_KERNEL_CMDLINE := bootopt=64S3,32N2,64N2

I can only help when you REALLY have a TWRP coming from a device tree that can REALLY create a file that boots on the device. I proposed to help with the encrypt/decrypt. But I won't help fix or create a device tree from scratch for you! Surprise me: create your TWRP/PBRP and put your name on it as "xxroot 2022". Send me a photo of the TWRP working and the file.

Then we will continue with our messages.

xxroot commented 3 years ago

TWRP/PBRP tree

lopestom commented 3 years ago

TWRP/PBRP tree

Acess blocked.

xxroot commented 3 years ago

TWRP/PBRP tree

Acess blocked. https://drive.google.com/file/d/1RoEkfkTqjoGChho3vZv81WCRnkV_fzFJ/view?usp=sharing

xxroot commented 3 years ago

your Telegram?

lopestom commented 3 years ago

your Telegram?

Sorry. I haven't.

xxroot commented 3 years ago

https://github.com/xxroot/android_device_motorola_pokerp/blob/main/devices%20version.png

lopestom commented 3 years ago

About this OrangeFox Recovery Project for the Moto E6 Plus. This device tree compile any img file? Start in your device?

I'm only curious.

xxroot commented 3 years ago

I just added some files for decryption, nothing else was changed

lopestom commented 3 years ago

I just added some files for decryption, nothing else was changed

First: you added the files from MRMAZAK with device tree for A10. Not good! 2nd: I not know if I can help. But I go try. I'll add necessary files from your stock ROM. But If recovery compiled not start in your device or enc/dec not work so the problem is device tree vs files frm stock ROM.

I'll try only 3 attempts. Wait my time now.

Cheers

xxroot commented 3 years ago

thank

lopestom commented 3 years ago

thank

I think the enc/dec maybe not work. But my goal here is see the PBRP working in your device. If yes and the enc/dec not work so we can look that for any solve.

Try: https://github.com/lopestom/android_device_motorola_pokerp/releases/download/1495020234/recovery.img It's based in your device tree TWRP/PBRP tree files shared before.

xxroot commented 3 years ago

Test result picture, I put in the device tree in the test directory The TWRP logo is not displayed. The TWRP page cannot be displayed

lopestom commented 3 years ago

Test result picture, I put in the device tree in the test directory The TWRP logo is not displayed. The TWRP page cannot be displayed

I know the language is not being easy for us to understand. So I will repeat and hope you understand.

The device tree you sent me is interesting and sends the TWRP-9 information you have. But it is separate and not set up correctly to compile correctly. This penultimate time it was compiled, the file came from my attempt to unify and make the device tree cleaner. This is ideal. But since I asked you about this and asked you to compile the file yourself, with one and only one modification to prove that TWRP-9 works on the device and can be recompiled the same way, you didn't! Instead, you gave me the partial device tree and another part of MTK/commonmt676 which is for the A10.

So am I trying to help with having a TWRP? PBRP? Am I going to make the file for you?

As long as YOU don't prove that a new TWRP pu PBRP file is on your device and get the device tree to WORK, I will stop. I can't perform miracles or repeat some unsuccessful compilation that somehow worked. I'm not seeing a device tree correctly.

Again I will try. I took your files and put them on github. I asked to compile. Many mistakes. Tried to put relevant information from the shortcuts. Mistakes and lots of mistakes.

It's time for you to show me a TWRP or PBRP on the screen of your device that has xxxroot_2022 and send me the file so I can analyze if it was really compiled. My question now is whether the file was actually compiled or ported! Prove that a new build can succeed and show the new TWRP/PBRP on your device.

Here the errors from your device tree: https://github.com/lopestom/android_device_motorola_pokerp/runs/4314760889?check_suite_focus=true#step:9:12377

brunopsass commented 2 years ago

is it possible for you to compile some rom for moto e6 plus

brunopsass commented 2 years ago

and why in gsi when I turn off the cell phone it doesn't go to the screen that animates cell phone charging

xxroot commented 2 years ago

以及为什么在 gsi 中，当我关闭手机时，它不会转到为手机充电设置动画的屏幕

I don't understand what you mean

KatoTempest commented 2 years ago

Maybe I'm not the guy who had to send the link to his device tree, but I'll attach mine Almost everything is functional except for the encryption, the DT is somewhat dirty, but at least I think it is acceptable, when starting the recovery with the memory encrypted it stays on the TeamWin screen, I understand that blobs are missing, but I'm not very sure which ones are missing

https://github.com/KatoTempest/motorola_pokerpatas/tree/wip-9.0

I will also attach a link on how this device tree is compiled, in that same link the build is downloadable in case someone is interested in reviewing it

https://github.com/Licht-testing/Recovery-Builder-NoKernel/runs/4549701454?check_suite_focus=true

lopestom commented 2 years ago

Maybe I'm not the guy who had to send the link to his device tree, but I'll attach mine Almost everything is functional except for the encryption, the DT is somewhat dirty, but at least I think it is acceptable, when starting the recovery with the memory encrypted it stays on the TeamWin screen, I understand that blobs are missing, but I'm not very sure which ones are missing

https://github.com/KatoTempest/motorola_pokerpatas/tree/wip-9.0

I will also attach a link on how this device tree is compiled, in that same link the build is downloadable in case someone is interested in reviewing it

https://github.com/Licht-testing/Recovery-Builder-NoKernel/runs/4549701454?check_suite_focus=true

I haven't free time now. But I'll see this the next year if someone not help.

KatoTempest commented 2 years ago

do not worry about that, I just wanted to comment on my experience in this in case it is useful to someone

lopestom commented 2 years ago

do not worry about that, I just wanted to comment on my experience in this in case it is useful to someone

Is good to knew other user with same device and DT with custom recovery file working. So every attempts is better than nothing.

lopestom commented 2 years ago

do not worry about that, I just wanted to comment on my experience in this in case it is useful to someone

You can look the binaries and config here: https://github.com/lopestom/android_device_motorola_pokerp/tree/android-9.0/recovery/root

Try other branch. I think you need reorganizing the structure to 3.5/3.6 TWRP version as same my DT. Compile img file and test.

KatoTempest commented 2 years ago

I had made some similar changes in the wip-9.0 branch, but I will make another one using those binaries just in case

xxroot commented 2 years ago

I had made some similar changes in the wip-9.0 branch, but I will make another one using those binaries just in case

Does it now support decryption?

KatoTempest commented 2 years ago

not yet, the furthest I've come is that the recovery doesn't get stuck on the home screen, but the files have random names (because it's encrypted) I'm trying in orangefox, apparently the recovery still can't find the keymaster , although I already have it there, I want to assume that it is related to some recovery prop or similar

xxroot commented 2 years ago

I have the same problem as you, also can't get the Keymaster We can communicate to accomplish this work https://t.me/Magiskuser

KatoTempest commented 2 years ago

At the moment I had managed to get the recovery to start correctly, although without decrypting yet, if I'm not mistaken what is currently wrong could be 2 or 3 things which I am going to mention: 1-Blobs are missing or misplaced 2-The blobs are fine but the keymaster does not recognize them 3-you have to use a common blob that does not have the device or something in the settings is wrong

Also note that twrp needs an init.recovery.vold_uncrypt.rc as a file to decrypt, I have generated it but it is probably not very well configured internally, I have used other mtk with android 9 as a reference (cereus and begonia to be exact) But from my point of view, the archivp is wrongly configured, perhaps the vendor files referring to the drm or the attestation keystore have to be used

lopestom commented 2 years ago

At the moment I had managed to get the recovery to start correctly, although without decrypting yet, if I'm not mistaken what is currently wrong could be 2 or 3 things which I am going to mention: 1-Blobs are missing or misplaced 2-The blobs are fine but the keymaster does not recognize them 3-you have to use a common blob that does not have the device or something in the settings is wrong

Also note that twrp needs an init.recovery.vold_uncrypt.rc as a file to decrypt, I have generated it but it is probably not very well configured internally, I have used other mtk with android 9 as a reference (cereus and begonia to be exact) But from my point of view, the archivp is wrongly configured, perhaps the vendor files referring to the drm or the attestation keystore have to be used

Maybe can help?! Try: https://github.com/Teracube-Inc/twrp_teracube_yk673v6_lwg62_64/blob/android-10.0/recovery/root/init.recovery.mt6762.rc

Look about vold need mount first to uncrypt all partitions. Vold is used in process system and have permissions since android have. But obviusly the company can change something. You need import teei_daemon to init.recovery and change 'start teei_daemon' & 'stop teei_daemon' in process.

PS: I not know about but since I can the teei (\vendor\thh) not have these files. Only in your device firmware I observed this: libTeeCA.so; libtee_interface.so, others dependecies??

KatoTempest commented 2 years ago

dependencies for the teei_daemon, I'm not totally sure which dependencies exist on this device, but note that drm files are used in some xml in etc / vinft, In any case I will attach a dump of the last stock that I made a few days ago, probably later I will review in detail what refers to the teei_daemon

https://github.com/KatoTempest/motorola_pokerp_dump