Develop Bugs

[Q] I want to build CM12 for my D859(ChinaTelecom)

D859 has 2sims, I can't use other g3 template, right
I already read a loi of information from cm wiki about hout to build a cm,
but I still have any clue yet,
I got D859 official rom scr code yesterday from opensource.lge.com,
I don't know how can I start for building cm,
I need some help, thank you!:laugh:
Here is the list of the files
LGD859_Lollipop_LGD859_V20a_Android_opensource/android/external: $ ls -al
drwxr-xr-x 17 578 brctl
drwxr-xr-x 21 714 dnsmasq
drwxr-xr-x 44 1496 e2fsprogs
drwxr-xr-x 7 238 ebtables
drwxr-xr-x 12 408 gcc-demangle
drwxr-xr-x 25 850 iproute2
drwxr-xr-x 21 714 iptables
drwxr-xr-x 31 1054 iputils
drwxr-xr-x 15 510 junit
drwxr-xr-x 41 1394 libexif
drwxr-xr-x 20 680 libnetfilter_conntrack
drwxr-xr-x 16 544 libnfnetlink
drwxr-xr-x 18 612 libnl
LGD859_Lollipop_LGD859_V20a_Android_opensource/android/vendor/lge: $ ls -la
drwxr-xr-x 3 102 apps
drwxr-xr-x 3 102 build
drwxr-xr-x 5 170 external
drwxr-xr-x 3 102 factory
drwxr-xr-x 4 136 frameworks
drwxr-xr-x 3 102 prebuilt
drwxr-xr-x 4 136 system
LGD859_Lollipop_LGD859_V20a_Android_opensource/kernel: $ ls -al
-rw-r--r-- 1 5935 AndroidKernel.mk
-rw-r--r-- 1 18693 COPYING
-rw-r--r-- 1 94984 CREDITS
drwxr-xr-x 237 8058 Documentation
-rw-r--r-- 1 2536 Kbuild
-rw-r--r-- 1 252 Kconfig
-rw-r--r-- 1 210475 MAINTAINERS
-rw-r--r-- 1 53855 Makefile
-rw-r--r-- 1 364155 Module.symvers
-rw-r--r-- 1 17459 README
-rw-r--r-- 1 3371 REPORTING-BUGS
drwxr-xr-x 31 1054 arch
drwxr-xr-x 38 1292 block
drwxr-xr-x 89 3026 crypto
drwxr-xr-x 112 3808 drivers
drwxr-xr-x 55 1870 firmware
drwxr-xr-x 149 5066 fs
drwxr-xr-x 26 884 include
drwxr-xr-x 14 476 init
drwxr-xr-x 17 578 ipc
drwxr-xr-x 133 4522 kernel
drwxr-xr-x 150 5100 lib
drwxr-xr-x 79 2686 mm
drwxr-xr-x 62 2108 net
drwxr-xr-x 14 476 samples
drwxr-xr-x 91 3094 scripts
drwxr-xr-x 18 612 security
drwxr-xr-x 28 952 sound
drwxr-xr-x 14 476 tools
-rw-r--r-- 1 37204 tuxera_update.sh
drwxr-xr-x 9 306 usr
drwxr-xr-x 3 102 virt
and its readme file said
1. Android build
- Download original android source code ( L 5.0 ) from source.android.com
- Untar opensource packages of LGD859_L_V20a_Android.tar.gz into downloaded android source directory
a) cat LGD859_L_V20a_Android.tar.gza* | tar zxvpf -
- And, merge the source into the android source code
- Run following scripts to build android
a) source build/envsetup.sh
b) lunch 1
c) make -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain) into the android directory.
- After build, you can find output at out/target/product/generic
2. Kernel Build
- Uncompress using following command at the android directory
tar xvzf LGD859_L_V20a_Kernel.tar.gz
- When you compile the kernel source code, you have to add google original prebuilt source(toolchain) into the android directory.
- Run following scripts to build kernel
a) cd kernel
1) D859
b) make ARCH=arm CROSS_COMPILE=../prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi- g3-ctc_cn-perf_defconfig zImage -j4
* "-j4" : The number, 4, is the number of multiple jobs to be invoked simultaneously.
- After build, you can find the build image(zImage) at arch/arm/boot
3. how to build chromium34_lge (vendor\lge\external\chromium34_lge\src),
please refer to README.txt at the folder mentioned above.

Where is stored the raw file for the User Dictionary of HTC Sense Input keyboard ?

Hello.
Where is stored the raw file for the User Dictionary of HTC Sense Input keyboard ? It's obviously not the classic /data/data/com.android.providers.userdictionary/databases/user_dict.db ... because I wiped the file, rebooted, and HTC SI still kept memories of some words. After using backup restaure tools like UDM, HTCSI also can't see new words.
Thanks.

State of art:
For every one: the classic user dictionary is in /data/data/com.android.providers.userdictionary/databases/user_dict.db as SQLite3 . It's very easy to extract:
echo "SELECT word FROM words;" | sqlite3 /data/local/tmp/user_dict.db | sort | uniq | sed ':a;N;$!ba;s/\n/\|/g' > /data/local/tmp/PersonalDictionary.htcudb
providing you have SQLite3 somewhere in your PATH.
The base HTC IME dictionary is here: /data/data/com.htc.sense.ime/app_db/dlm_export
The SD backup is not on emulated (I have asked for emulated SD from internal memory), but on real physical external SD:
/storage/ext_sd/.data/HTC_IME/PersonalDictionary
The method to find the two last files were:
- touch /data/local/tmp/plop
- make a change in the dic, or a backup
- find /storage/ext_sd/ -newer /data/local/tmp/plop
or
- find /data/data -newer /data/local/tmp/plop
You have to re-touch the plop each time.
Once /data/data/com.android.providers.userdictionary/databases/user_dict.db is exported into /data/local/tmp/PersonalDictionary.htcudb, two things are possible:
- copy the file into /storage/ext_sd/.data/HTC_IME/PersonalDictionary, and make a manual import from HTC Sense Input dictionary manager
- attach the file to an email, and open the attachement from HTC-Mail, what will restaure the attached backup.
I have found the following command to ask for restauring the backup:
Code:
am start -a android.intent.action.VIEW -d "content:" -t "application/ime-config" -n com.htc.sense.ime/.ui.RestoreUDB -f "0x00080001"
But I do not get the confirmation toast. Because I don't find where the cache file is stored by HTC-Mail, for IME. Since I run stuff from scripts, that command does not work as is; in my case, I have to run it in this context:
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
adb connect 127.0.0.1
adb shell id
adb shell su -c id
adb shell su -c am start [...]
otherwise I get a nasty error about permission issues:
Starting: Intent { act=android.intent.action.VIEW dat=content: typ=application/ime-config flg=0x80001 cmp=com.htc.sense.ime/.ui.RestoreUDB }
java.lang.SecurityException: Permission Denial: starting Intent { act=android.intent.action.VIEW dat=content: typ=application/ime-config flg=0x10080001 cmp=com.htc.sense.ime/.ui.RestoreUDB } from null (pid=29007, uid=2000) requires com.htc.permission.APP_DEFAULT
Click to expand...
Click to collapse
Work for an other day:
- try to construct the am start call for backup restauration from SD (previous line was for email attachement) => give up
- find how to export and rebuild (via script) /data/data/com.htc.sense.ime/app_db/dlm_export
- find if this dictionary is gaining, or loosing any word => stats now on way: cron is recording daily the size of files
- remove dups from /data/data/com.android.providers.userdictionary/databases/user_dict.db (clean PROVIDER file)
- during export, I want to inject Contact details (first name, name, town name)
*** *** ***
The base problem I have is that HTC Sens keyboard is very good, for daily use, but randomly looses settings, and parts of the dics (some times words added the last days; some times 98% of it, only keeping 10 or 15 words).
I want to monitor the IME dic, and produce a system alert when this dic is found to have lost words, and after user confirmation, restaure the IME dic (with an older version of the file, or by rebuilding it).
Some other files may be interesting, in the same folder: mdb_contact_name seem to be a raw text version of com.android.providers.userdictionary/databases/user_dict.db . stm_dump is also very large. IME dictionary has a concept of alias (and auto-replace); but I don't know where this is stored. I also wonder where the word usage statistics are stored (for suggestions).
The big minus I found in this keyboard is that suggestions are always limited to 3 words on the first line (the one always available) (in portrait); Gingerbread and Hackers offer up to 12 words: as much as they can print on screen. Also, suggestions only include literal words: words with letters only; it never suggests words with numbers (unless I already typed one in currect word) or punctuation (statistics show that some words are very often followed by question mark, comma, or full stop).
Now that I am used to the height of HTC Sens keyboard, I make many typos with smaller boards; but smaller boards leave much more screen space for chat. Sens is very good for writing emails; but instant messaging like Skype and Yahoo use too much screen space, and smaller kbd would leave more chat history visible. But Sens has a better word prediction for intuitive chat ...
***
Recoding daily stats of files:
Code:
find /data/data/com.htc.sense.ime/app_db/dlm_export.history -mtime 0 | grep "e" || {
for i in dlm_export mdb_contact_name stm_dump
do
{ echo -n "$(date +%Y-%m-%d_%H-%M-%S) : " ; ls -l /data/data/com.htc.sense.ime/app_db/$i | awk '{print $4}' ; } >> /data/data/com.htc.sense.ime/app_db/${i}.history
done
This code will work even with non existing history. Then wait history is 1D old .... I have found that one history per file is easier to re-read than one for all. Injecting date this way date +%Y-%m-%d_%H-%M-%S ; echo -n " : " used to introduce an undesired NL..

Proof that stupid dictionary bugs:
Code:
-rw------- 1 root root 0 2016-01-24 23:40 dlm_export
-rw------- 1 root root 1274 2015-09-02 10:15 kdb_0c09.cfg
-rw------- 1 root root 1274 2016-01-24 02:29 kdb_0c0c.cfg
-rw------- 1 root root 1281 2014-10-08 14:56 kdb_0d03.cfg
-rw------- 1 root root 1250 2015-12-20 18:18 kdb_0d09.cfg
-rw------- 1 root root 1250 2016-01-24 23:48 kdb_0d0c.cfg
-rw------- 1 root root 28902 2016-01-25 17:01 mdb_contact_name
-rw------- 1 root root 20 2016-01-25 17:01 sc_mdb_contact_name
-rw------- 1 root root 0 2016-01-24 23:40 stm_dump
-rw------- 1 root root 0 2016-01-25 17:01 tc_mdb_contact_name
-rw------- 1 root root 83251 2016-01-29 20:01 dlm_export
-rw------- 1 root root 1274 2015-09-02 10:15 kdb_0c09.cfg
-rw------- 1 root root 1274 2016-01-29 07:30 kdb_0c0c.cfg
-rw------- 1 root root 1281 2014-10-08 14:56 kdb_0d03.cfg
-rw------- 1 root root 1250 2015-12-20 18:18 kdb_0d09.cfg
-rw------- 1 root root 1250 2016-01-29 19:48 kdb_0d0c.cfg
-rw------- 1 root root 28954 2016-01-29 20:57 mdb_contact_name
-rw------- 1 root root 20 2016-01-29 20:57 sc_mdb_contact_name
-rw------- 1 root root 225751 2016-01-29 09:57 stm_dump
-rw------- 1 root root 0 2016-01-29 20:57 tc_mdb_contact_name
-rw------- u0_a39 u0_a39 145060 2016-02-04 23:44 dlm_export
-rw------- root root 29 2016-02-05 01:01 dlm_export.history
-rw------- u0_a39 u0_a39 1274 2015-09-02 10:15 kdb_0c09.cfg
-rw------- u0_a39 u0_a39 1274 2016-02-04 21:20 kdb_0c0c.cfg
-rw------- u0_a39 u0_a39 1281 2014-10-08 14:56 kdb_0d03.cfg
-rw------- u0_a39 u0_a39 1250 2015-12-20 18:18 kdb_0d09.cfg
-rw------- u0_a39 u0_a39 1250 2016-02-05 00:32 kdb_0d0c.cfg
-rw------- u0_a39 u0_a39 29036 2016-02-05 00:32 mdb_contact_name
-rw------- root root 57 2016-02-05 01:01 mdb_contact_name.history
-rw------- u0_a39 u0_a39 20 2016-02-05 00:32 sc_mdb_contact_name
-rw------- u0_a39 u0_a39 225751 2016-02-04 16:07 stm_dump
-rw------- root root 59 2016-02-05 01:01 stm_dump.history
-rw------- u0_a39 u0_a39 0 2016-02-05 00:32 tc_mdb_contact_name
Clearly: dlm_export and stm_dump were empty 2 weeks ago. Due to the nature of cheap backup, I was wondering if by huge hasard, those files were empty due to rsync glitches (if wifi is lost during file transfert, and glitch occurs while working on THIS file ... one chance in a trillion): such a glitch may produce an empty file; one, and ONE ONLY. Not two: rsync can't have corrupted dlm_export AND stm_dump at the same time. Thus, they are both empty due to a HTC Sens bug. The one that often makes the IME forget about second lang, and no vibrator.

Nobody knows if the loss of content of dlm_export could be related to HTC Sense keyboard issues ?

Someone with Stock rooted and correct IMEi help please

Dear all members,
The member @NZedPred is trying to solve the imei problem for the people who lost it so we need some with:
1-Correct IMEI
2-Stock Nougat or Oreo
3-rooted
If you are willing to help please screenshot or copy paste the result from these commands (adb or shell)
su
ls -l /persist
Thank you all

AhmedtSadek said:
Dear all members,
The member @NZedPred is trying to solve the imei problem for the people who lost it so we need some with:
1-Correct IMEI
2-Stock Nougat or Oreo
3-rooted
If you are willing to help please screenshot or copy paste the result from these commands (adb or shell)
su
ls -l /persist
Thank you all
Click to expand...
Click to collapse
Hi there, I'm on stock nougat 7.0 ( debloated rom )

Chekm8Qc said:
Hi there, I'm on stock nougat 7.0 ( debloated rom )
Click to expand...
Click to collapse
Are you rooted and the IMEI is visible correctly?

I posted a screenshot..might not be showing for some reason. Here is the result anyways.
cedric:/ $ su
cedric:/ # ls -l /persist
total 168
drwxrwx--- 2 system system 4096 1969-12-31 19:02 alarm
drwxr-xr-x 2 mot_pwric mot_pwric 4096 1969-12-31 19:02 batt_health
drwxrwx--- 2 bluetooth bluetooth 4096 2017-03-10 08:45 bluetooth
drwx------ 2 root system 4096 1969-12-31 19:02 bms
drwxr-xr-x 2 mot_tcmd bluetooth 4096 1969-12-31 19:02 bt
drwxr-xr-x 4 mot_tcmd mot_tcmd 4096 1969-12-31 19:02 camera
-rw-r--r-- 1 mot_tcmd mot_tcmd 12 2017-03-10 08:45 captouch_basedata.bin
drwx------ 6 system system 4096 2018-03-15 01:31 datadrwxrwx--- 2 system system 4096 1969-12-31 19:02 drm
drwxr-xr-x 5 mot_tcmd mot_tcmd 4096 2017-03-10 08:46 factory
drwxrwx--- 3 rfs rfs_shared 4096 1969-12-31 19:02 hlos_rfs
drwx------ 2 root root 4096 1969-12-31 19:00 lost+found
drwxrwx--- 2 radio radio 4096 2017-03-10 08:45 mdm
drwxrwx--- 2 system system 4096 1969-12-31 19:02 miscdrwxr-xr-x 8 mot_tcmd mot_tcmd 4096 1969-12-31 19:02 public
drwx------ 6 rfs rfs 4096 1969-12-31 19:02 rfs
drwxrws--- 2 mot_tpapi mot_tpapi 4096 2018-03-15 01:31 security
drwxrwxr-x 2 root root 4096 2017-03-10 08:57 sensors
drwxrwx--- 2 system system 4096 2017-05-26 08:04 timedrwxr-xr-x 2 mot_tcmd mot_tcmd 4096 1969-12-31 19:02 wifidrwxrwxr-x 2 mot_drm mot_drm 4096 1969-12-31 19:02 wmdrm
---------- Post added at 09:41 PM ---------- Previous post was at 09:41 PM ----------
Yeah my imei is fine ( also rooted )

Chekm8Qc said:
I posted a screenshot..might not be showing for some reason. Here is the result anyways.
cedric:/ $ su
cedric:/ # ls -l /persist
total 168
drwxrwx--- 2 system system 4096 1969-12-31 19:02 alarm
drwxr-xr-x 2 mot_pwric mot_pwric 4096 1969-12-31 19:02 batt_health
drwxrwx--- 2 bluetooth bluetooth 4096 2017-03-10 08:45 bluetooth
drwx------ 2 root system 4096 1969-12-31 19:02 bms
drwxr-xr-x 2 mot_tcmd bluetooth 4096 1969-12-31 19:02 bt
drwxr-xr-x 4 mot_tcmd mot_tcmd 4096 1969-12-31 19:02 camera
-rw-r--r-- 1 mot_tcmd mot_tcmd 12 2017-03-10 08:45 captouch_basedata.bin
drwx------ 6 system system 4096 2018-03-15 01:31 datadrwxrwx--- 2 system system 4096 1969-12-31 19:02 drm
drwxr-xr-x 5 mot_tcmd mot_tcmd 4096 2017-03-10 08:46 factory
drwxrwx--- 3 rfs rfs_shared 4096 1969-12-31 19:02 hlos_rfs
drwx------ 2 root root 4096 1969-12-31 19:00 lost+found
drwxrwx--- 2 radio radio 4096 2017-03-10 08:45 mdm
drwxrwx--- 2 system system 4096 1969-12-31 19:02 miscdrwxr-xr-x 8 mot_tcmd mot_tcmd 4096 1969-12-31 19:02 public
drwx------ 6 rfs rfs 4096 1969-12-31 19:02 rfs
drwxrws--- 2 mot_tpapi mot_tpapi 4096 2018-03-15 01:31 security
drwxrwxr-x 2 root root 4096 2017-03-10 08:57 sensors
drwxrwx--- 2 system system 4096 2017-05-26 08:04 timedrwxr-xr-x 2 mot_tcmd mot_tcmd 4096 1969-12-31 19:02 wifidrwxrwxr-x 2 mot_drm mot_drm 4096 1969-12-31 19:02 wmdrm
---------- Post added at 09:41 PM ---------- Previous post was at 09:41 PM ----------
Yeah my imei is fine ( also rooted )
Click to expand...
Click to collapse
Could you please try to upload the screenshot somewhere else as it cant be viewed here or post the result between code tags

Working now ?

Thanks, that helps. And hopefully the debloated rom is still a fairly good representation of stock. I'll work with the OP and see if the fix for Potter also works with Cedric.

Need persist partition

Hi!
I need persist parition from oneplus 5T. The same as here but for oneplus 5T. Or anybody know that op5 persist is the same in op5t?
Therefore i would like to ask someone to perform the following adb actions and share the persist partitions image file with me.
Click to expand...
Click to collapse
Code:
adb shell
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
exit

Hi,
I've used the persist.img file from this thread on Oneplus 5T (8/128GB) and worked for me.
Now there's only the "no LTE" problem to fix.

Hi, I would like the persist.img file for OP 5t please if any one with root could kindly share here it would be great.
The OP5 version does not seem to be working for me.
Original issue was after using SMT mode on MSM download tool, I ost efs and message
invalid VIP NV 447, 1943, 4678, 6855.
I had a back up of efs and modem using TWRP and that has been restored but cannot seem to fix the invalid VIP NVs error which I cannot understand what they are. Searching has got me to a similar post in OP3/3t and a resolution was to delete and then reinstall the persist.img file.
THanks in advance guys.

So I installed Magisk for root thanks @topjohnwu
I then ran some commands to see what my current persist.img has
OnePlus5T:/ # ls -l /mnt/vendor/persist
total 204
drwxr-xr-x 2 system system 4096 1970-01-01 20:03 OPDiagnose
drwxrwx--- 2 system system 4096 1970-01-01 20:03 alarm
drwxrwx--- 2 bluetooth bluetooth 4096 1970-01-01 20:03 bluetooth
drwxr-xr-x 2 system system 4096 1970-01-01 20:03 camera
drwx------ 2 system system 4096 1970-01-01 20:03 data
-rw-rw-r-- 1 bluetooth bluetooth 29 2019-04-19 12:34 date
drwxrwx--- 2 system graphics 4096 1970-01-01 20:03 display
drwxrwx--- 2 system system 4096 1970-01-01 20:03 drm
drwxrwxrwx 2 system system 4096 1970-01-01 20:03 dual_camera_calibration
drwxr-xr-x 2 system system 4096 1970-01-01 20:03 engineermode
drwxrwxrwx 2 system system 4096 1970-01-01 20:03 goodix
drwxrwxr-x 3 media mediadrm 4096 1970-01-01 20:03 hdcp
drwxrwx--- 3 vendor_rfs vendor_rfs_shared 4096 1970-01-01 20:03 hlos_rfs
drwxrwx--- 2 root system 4096 1970-01-01 20:03 hvdcp_opti
drwx------ 2 root root 16384 2019-04-19 12:34 lost+found
drwxrwx--- 2 system system 4096 1970-01-01 20:03 misc
drwxrwx--- 2 system system 4096 1970-01-01 22:24 properties
drwx------ 6 vendor_rfs vendor_rfs 4096 1970-01-01 20:03 rfs
drwxrwx--- 2 system system 4096 1970-01-01 20:03 secnvm
drwxrwxr-x 2 system system 4096 1970-01-01 20:03 sensors
drwxrwxrwx 2 system system 4096 1970-01-01 20:03 silead
drwxrwx--- 2 system system 4096 2018-01-01 10:08 time
drwxrwx--- 2 media media 4096 1970-01-01 20:03 vpp
-rw------- 1 wifi wifi 120 2019-07-04 23:10 wlan_mac.bin
OnePlus5T:/ # find /mnt/vendor/persist -type f
/mnt/vendor/persist/date
/mnt/vendor/persist/time/ats_13
/mnt/vendor/persist/time/ats_1
/mnt/vendor/persist/time/ats_12
/mnt/vendor/persist/time/ats_2
/mnt/vendor/persist/time/ats_16
/mnt/vendor/persist/time/ats_15
/mnt/vendor/persist/sensors/sns.reg
/mnt/vendor/persist/sensors/als_rgb_cal_parameter
/mnt/vendor/persist/sensors/sensors_settings
/mnt/vendor/persist/wlan_mac.bin
/mnt/vendor/persist/rfs/shared/server_info.txt
/mnt/vendor/persist/rfs/msm/mpss/server_check.txt
OnePlus5T:/ # ls-l /persist
The .img file is around 32,768 KB, so even if some one could share this info so I can compare if I have the complete files or not, I would really appreciate it
Thanks

Did you finally fix it? Did a persist.img file from another 5T work? I'm having the same problem.

I've made a backup but I'm afraid of giving someone the same IMEI etc..
My persist.img contains this:
Code:
:/data/data/com.termux/files/home # cd /
:/ # ls -l /mnt/vendor/persist
total 136
drwxr-xr-x 2 system system 4096 1970-11-19 21:37 OPDiagnose
drwxrwx--- 2 system system 4096 2018-12-28 02:13 alarm
drwxrwx--- 2 bluetooth bluetooth 4096 1970-01-01 01:00 bluetooth
drwx------ 2 root system 4096 1970-01-01 01:00 bms
drwxr-xr-x 2 system system 4096 1970-11-19 21:37 camera
-rwsrwsrwt 1 root root 33 2017-03-01 06:06 cplc
drwx------ 2 system system 4096 1970-01-01 01:00 data
-rw-r--r-- 1 root root 29 2017-11-15 16:23 date
drwxrwx--- 2 system graphics 4096 1970-01-01 01:32 display
drwxrwx--- 2 system system 4096 1970-01-01 01:00 drm
-rwxrwxrwx 1 cameraserver audio 17 2020-04-25 16:20 dual_cam_module_id.bin
-rwxrwxrwx 1 cameraserver audio 512 2020-04-25 12:59 dual_cam_otp.bin
-rwxrwxrwx 1 cameraserver audio 29 2020-04-25 12:59 dual_cam_stero_otp.bin
drwxrwxrwx 2 system system 4096 2017-03-01 06:27 dual_camera_calibration
drwxr-xr-x 2 system system 4096 2018-11-18 19:53 engineermode
-rw------- 1 system system 644 2017-03-01 06:06 engineermode_config
drwxrwxrwx 2 system system 4096 1970-11-19 21:37 goodix
drwxrwxr-x 3 media mediadrm 4096 1970-11-19 21:37 hdcp
drwxrwx--- 3 vendor_rfs vendor_rfs_shared 4096 1970-01-01 01:00 hlos_rfs
drwxrwx--- 2 root system 4096 1970-11-19 21:37 hvdcp_opti
drwx------ 2 root root 4096 1970-01-01 01:00 lost+found
drwxr-xr-x 2 root root 4096 2020-04-25 12:58 magisk
drwxrwx--- 2 system system 4096 1970-01-01 01:00 misc
-rw------- 1 system system 7808 1970-11-19 21:13 opdiagnose
-rw------- 1 cameraserver audio 12 2017-03-01 06:24 rear_camera_dual_led_calibration
drwx------ 6 vendor_rfs vendor_rfs 4096 1970-01-01 01:00 rfs
drwxrwx--- 2 system system 4096 1970-01-01 01:32 secnvm
-rw------- 1 cameraserver audio 12 2017-03-01 06:24 second_rear_camera_dual_led_calibration
drwxr-xr-x 3 system system 4096 1970-03-11 20:10 sensors
drwxrwxrwx 2 system system 4096 1970-11-19 21:37 silead
drwxrwx--- 2 system system 4096 2018-02-06 15:55 time
drwxrwx--- 2 media media 4096 1970-01-01 01:32 vpp
-rw------- 1 wifi wifi 120 2020-05-01 07:25 wlan_mac.bin

LamarrCZ said:
I've made a backup but I'm afraid of giving someone the same IMEI etc..
My persist.img contains this:
Code:
:/data/data/com.termux/files/home # cd /
:/ # ls -l /mnt/vendor/persist
total 136
drwxr-xr-x 2 system system 4096 1970-11-19 21:37 OPDiagnose
drwxrwx--- 2 system system 4096 2018-12-28 02:13 alarm
drwxrwx--- 2 bluetooth bluetooth 4096 1970-01-01 01:00 bluetooth
drwx------ 2 root system 4096 1970-01-01 01:00 bms
drwxr-xr-x 2 system system 4096 1970-11-19 21:37 camera
-rwsrwsrwt 1 root root 33 2017-03-01 06:06 cplc
drwx------ 2 system system 4096 1970-01-01 01:00 data
-rw-r--r-- 1 root root 29 2017-11-15 16:23 date
drwxrwx--- 2 system graphics 4096 1970-01-01 01:32 display
drwxrwx--- 2 system system 4096 1970-01-01 01:00 drm
-rwxrwxrwx 1 cameraserver audio 17 2020-04-25 16:20 dual_cam_module_id.bin
-rwxrwxrwx 1 cameraserver audio 512 2020-04-25 12:59 dual_cam_otp.bin
-rwxrwxrwx 1 cameraserver audio 29 2020-04-25 12:59 dual_cam_stero_otp.bin
drwxrwxrwx 2 system system 4096 2017-03-01 06:27 dual_camera_calibration
drwxr-xr-x 2 system system 4096 2018-11-18 19:53 engineermode
-rw------- 1 system system 644 2017-03-01 06:06 engineermode_config
drwxrwxrwx 2 system system 4096 1970-11-19 21:37 goodix
drwxrwxr-x 3 media mediadrm 4096 1970-11-19 21:37 hdcp
drwxrwx--- 3 vendor_rfs vendor_rfs_shared 4096 1970-01-01 01:00 hlos_rfs
drwxrwx--- 2 root system 4096 1970-11-19 21:37 hvdcp_opti
drwx------ 2 root root 4096 1970-01-01 01:00 lost+found
drwxr-xr-x 2 root root 4096 2020-04-25 12:58 magisk
drwxrwx--- 2 system system 4096 1970-01-01 01:00 misc
-rw------- 1 system system 7808 1970-11-19 21:13 opdiagnose
-rw------- 1 cameraserver audio 12 2017-03-01 06:24 rear_camera_dual_led_calibration
drwx------ 6 vendor_rfs vendor_rfs 4096 1970-01-01 01:00 rfs
drwxrwx--- 2 system system 4096 1970-01-01 01:32 secnvm
-rw------- 1 cameraserver audio 12 2017-03-01 06:24 second_rear_camera_dual_led_calibration
drwxr-xr-x 3 system system 4096 1970-03-11 20:10 sensors
drwxrwxrwx 2 system system 4096 1970-11-19 21:37 silead
drwxrwx--- 2 system system 4096 2018-02-06 15:55 time
drwxrwx--- 2 media media 4096 1970-01-01 01:32 vpp
-rw------- 1 wifi wifi 120 2020-05-01 07:25 wlan_mac.bin
Click to expand...
Click to collapse
https://mega.nz/file/fTIzVKSI#vFazpD-qa3Q5S2DJTHUwAJb_kFBcd0_OmHRfwCb2BxE
---------- Post added at 05:07 PM ---------- Previous post was at 05:06 PM ----------
rafciowis1999 said:
Hi!
I need persist parition from oneplus 5T. The same as here but for oneplus 5T. Or anybody know that op5 persist is the same in op5t?
Code:
adb shell
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
exit
Click to expand...
Click to collapse
Download frm link below
https://mega.nz/file/fTIzVKSI#vFazpD-qa3Q5S2DJTHUwAJb_kFBcd0_OmHRfwCb2BxE

I used the one from the OP5 and it worked fine in the end. Thanks for the help anyway.

Rare directory listing in my Pixel 3 XL

Hi,
My apologies if this post in wrong place.
I already play with adb tool on my pixel 3 xl and I notice me rare directory listing.
Code:
adb shell ls -l
total 68
drwxr-xr-x 2 root root 4096 2008-12-31 22:00 acct
drwxr-xr-x 54 root root 1140 2022-12-10 11:14 apex
lrw-r--r-- 1 root root 11 2008-12-31 22:00 bin -> /system/bin
lrw-r--r-- 1 root root 50 2008-12-31 22:00 bugreports -> /data/user_de/0/com.android.shell/files/bugreports
l????????? ? ? ? ? ? cache -> ?
drwxr-xr-x 4 root root 0 1969-12-31 21:00 config
lrw-r--r-- 1 root root 17 2008-12-31 22:00 d -> /sys/kernel/debug
drwxrwx--x 49 system system 4096 2022-12-02 08:56 data
d????????? ? ? ? ? ? data_mirror
drwxr-xr-x 2 root root 4096 2008-12-31 22:00 debug_ramdisk
drwxr-xr-x 23 root root 6180 2022-12-02 09:02 dev
lrw-r--r-- 1 root root 11 2008-12-31 22:00 dsp -> /vendor/dsp
lrw-r--r-- 1 root root 11 2008-12-31 22:00 etc -> /system/etc
l????????? ? ? ? ? ? init -> ?
-????????? ? ? ? ? ? init.environ.rc
d????????? ? ? ? ? ? linkerconfig
drwx------ 2 root root 16384 2008-12-31 22:00 lost+found
d????????? ? ? ? ? ? metadata
drwxr-xr-x 15 root system 320 1974-03-10 02:54 mnt
drwxr-xr-x 2 root root 4096 2008-12-31 22:00 odm
drwxr-xr-x 2 root root 4096 2008-12-31 22:00 odm_dlkm
drwxr-xr-x 2 root root 4096 2008-12-31 22:00 oem
lrw-r--r-- 1 root root 19 2008-12-31 22:00 persist -> /mnt/vendor/persist
d????????? ? ? ? ? ? postinstall
dr-xr-xr-x 963 root root 0 1969-12-31 21:00 proc
drwxr-xr-x 14 root root 4096 2008-12-31 22:00 product
lrw-r--r-- 1 root root 21 2008-12-31 22:00 sdcard -> /storage/self/primary
drwxr-xr-x 2 root root 4096 2008-12-31 22:00 second_stage_resources
drwx--x--- 4 shell everybody 80 1974-03-10 02:54 storage
dr-xr-xr-x 12 root root 0 1974-03-10 02:54 sys
drwxr-xr-x 12 root root 4096 2008-12-31 22:00 system
drwxr-xr-x 9 root root 4096 2008-12-31 22:00 system_ext
drwxr-xr-x 20 root shell 4096 2008-12-31 22:00 vendor
drwxr-xr-x 2 root root 4096 2008-12-31 22:00 vendor_dlkm
Anyone could light me what mean '??????? ?? ? ? " directory ?
Regards.