Need persist partition - OnePlus 5T Questions & Answers

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.

Related

[Q] Problems with Play Store & Google Sync after 4.2 update. What's wrong?

Ever since my phone got the OTA update to JB 4.2, my phone has had an error communicating with the Play Store. When the phone first boots, I get an error message for each app that I've downloaded in my notifications screen.
Edit: Just discovered that this seems to be an issue with my Google account, in general. Calendar isn't syncing, and it says that "Sync will be back shortly" when I pull up my account on the phone. Weird?
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also can't download any new apps from the Play Store itself. Screenshot:
Anyone else having the same problem?
I'm still on 4.1.2 however I have this message too. Do you by any chance have two google accounts linked with your phone?
Heres the fix:
Simply remove the Google account, reboot, and then re-enter your Google account. Takes a couple of minutes, but fixes the issue instantly.
chasmanz28 said:
Heres the fix:
Simply remove the Google account, reboot, and then re-enter your Google account. Takes a couple of minutes, but fixes the issue instantly.
Click to expand...
Click to collapse
I have the same issue.
Can I remove my Google accont since it's the only one I entered, considering my Nexus 7 isn't rooted?
If so, could you please tell me how to do?
I'm trying to avoid factory reset, but I fear I have to do it.
Hi,
Go to Settings > Accounts
Click on Google Account and select account by clicking on email address
Select Menu > Remove Account
Now, reboot the phone and enter Google account details on restart.
You should be good to go.
Click on thanks if I helped you!
Now
Gato_Diaz said:
I have the same issue.
Can I remove my Google accont since it's the only one I entered, considering my Nexus 7 isn't rooted?
If so, could you please tell me how to do?
I'm trying to avoid factory reset, but I fear I have to do it.
Click to expand...
Click to collapse
DZYR said:
Hi,
Go to Settings > Accounts
Click on Google Account and select account by clicking on email address
Select Menu > Remove Account
Now, reboot the phone and enter Google account details on restart.
You should be good to go.
Click on thanks if I helped you!
Now
Click to expand...
Click to collapse
Thanks DZYR, it was so easy
Anyway, I already entered a new account without deleting the previous one, setting it as back up. Now everything works fine.
Gato_Diaz said:
Thanks DZYR, it was so easy
Anyway, I already entered a new account without deleting the previous one, setting it as back up. Now everything works fine.
Click to expand...
Click to collapse
Hi guys, I've tried this procedure 2 times but I still have the same issue.
Please consider I've a N7 with root, I've re-installed superSU (as per suggestion on a XDA thread), I normally use an external internet key for 3G data connection and the application PPP widget.
I've issue to surf on chrome but it is impossible to update application from play store, download mails both on gmail and mail app.
Thank you in advance for your help
Had this issue yesterday. I figured out, that my permission in the fs are messed up, so I repaired it. Also the permission for all Files and Folders on the virtual SD was messed up, I need to repair it manually as follows:
1st. I temp booted TWRP and attached my phone to an adb console.
2nd. At the adb shell:
cd /data/media
chown -R media_rw:media_rw .
find . -type d -exec chmod 770 {} \;
find . -type f -exec chmod 660 {} \;
sync
reboot
After This, the Phone is operating as usual.
Hint: the path to virtual ad card (/data/media/) may vary..
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
TrusterX said:
Had this issue yesterday. I figured out, that my permission in the fs are messed up, so I repaired it. Also the permission for all Files and Folders on the virtual SD was messed up, I need to repair it manually as follows:
1st. I temp booted TWRP and attached my phone to an adb console.
2nd. At the adb shell:
cd /data/media
chown -R media_rw:media_rw .
find . -type d -exec chmod 770 {} \;
find . -type f -exec chmod 660 {} \;
sync
reboot
After This, the Phone is operating as usual.
Hint: the path to virtual ad card (/data/media/) may vary..
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
Click to expand...
Click to collapse
Hi TrusterX,
what do you mean for ADB console? Is the nexus toolkit usable as well?
Yeah just temp boot into TWRP, than perform permission repair. When finished, bring up a console for manual input (menu 24), type adb-toolkit shell
Now you're attached to the Shell.
Oh, and wait, you have to install the adb drivers. I'm sure, you did it already.
Good luck!
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
edit: this is, what i did:
Code:
C:\Galaxy Nexus ToolKit>adb-toolkit.exe shell
~ # ←[6ncd /data/media/
cd /data/media/
/data/media # ←[6nls
ls
0 fix_permissions.log obb
TWRP legacy
/data/media # ←[6ncd 0
cd 0
/data/media/0 # ←[6nls -la
ls -la
drwxrwx--- 39 media_rw media_rw 4096 Nov 16 06:22 .
drwxrwx--- 6 media_rw media_rw 4096 Nov 15 13:16 ..
drwxrwxr-x 2 media_rw media_rw 4096 Nov 15 13:56 .AlarmDroid
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 12:02 .premier_temp_pro
drwxrwx--- 3 media_rw media_rw 4096 Nov 15 12:02 .widgetsoid
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 12:02 AI Factory Stats
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 11:57 Alarms
drwxrwx--- 5 media_rw media_rw 4096 Nov 15 12:51 Android
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 12:03 CallLogBackupRestore
drwxrwx--- 5 media_rw media_rw 4096 Nov 15 13:32 DCIM
drwxrwx--- 4 media_rw media_rw 4096 Nov 15 16:32 Download
drwxrwx--- 4 media_rw media_rw 4096 Nov 15 12:08 MODS
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 12:09 Movies
drwxrwx--- 5 media_rw media_rw 4096 Nov 15 12:12 Music
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 12:13 Notifications
drwxrwx--- 9 media_rw media_rw 4096 Nov 15 12:15 Pictures
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 11:57 Podcasts
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 11:57 Ringtones
drwxrwxr-x 2 media_rw media_rw 4096 Nov 15 23:01 SMSBackupRestore
drwxrwx--- 3 media_rw media_rw 4096 Nov 15 12:20 TWRP
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 12:59 Video
drwxrwx--- 6 media_rw media_rw 4096 Nov 15 19:03 WhatsApp
drwxrwx--- 5 media_rw media_rw 4096 Nov 15 12:20 Widgetsoid
drwxrwx--- 4 media_rw media_rw 4096 Nov 15 12:20 _Daten
drwxrwx--- 3 media_rw media_rw 4096 Nov 15 12:02 adlayoutcache
drwxrwx--- 8 media_rw media_rw 4096 Nov 15 13:39 airdroid
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 12:02 albumthumbs
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 12:03 btcontroller
drwxrwxr-x 2 media_rw media_rw 4096 Nov 16 06:22 bugreports
drwxrwx--- 3 media_rw media_rw 4096 Nov 15 12:03 com.mictale.gpsessentials
drwxrwx--- 4 media_rw media_rw 4096 Nov 15 12:03 data
drwxrwx--- 6 media_rw media_rw 4096 Nov 15 12:08 droidsound
drwxrwx--- 3 media_rw media_rw 4096 Nov 15 12:08 lightflow
drwxrwx--- 8 media_rw media_rw 4096 Nov 15 12:13 navigator
drwxrwx--- 3 media_rw media_rw 4096 Nov 15 12:13 openfeint
drwxrwx--- 6 media_rw media_rw 4096 Nov 15 14:28 osmand
drwxrwxr-x 2 media_rw media_rw 4096 Nov 15 13:33 panoramas
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 12:15 temp
drwxrwx--- 3 media_rw media_rw 4096 Nov 15 12:20 viber
/data/media/0 # ←[6nchown -R media_rw:media_rw .
chown -R media_rw:media_rw .
/data/media/0 # ←[6nfind . -type d -exec chmod 770 {} \;
find . -type d -exec chmod 770 {} \;
/data/media/0 # ←[6nfind . -type f -exec chmod 660 {} \;
find . -type f -exec chmod 660 {} \;
/data/media/0 # ←[6nsync
sync
/data/media/0 # ←[6nreboot
as you can see, the path to my virtual sdcard is /data/media/0, it may differs on your device.
The ADB Server need some time after booting TWRP, so if the command "adb-toolkit shell" says "device not found" (or simmilar), just repeat it again..
Good Luck
i had this problem with ICS actually. clearing play store data/cache didn't work. you have to remove and reapply account as mentioned above.
but on the note of permiossions - how would the permissions become messed up in the 1st place?
TrusterX said:
Yeah just temp boot into TWRP, than perform permission repair. When finished, bring up a console for manual input (menu 24), type adb-toolkit shell
Now you're attached to the Shell.
Oh, and wait, you have to install the adb drivers. I'm sure, you did it already.
Good luck!
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
edit: this is, what i did:
Code:
C:\Galaxy Nexus ToolKit>adb-toolkit.exe shell
~ # ←[6ncd /data/media/
cd /data/media/
/data/media # ←[6nls
ls
0 fix_permissions.log obb
TWRP legacy
/data/media # ←[6ncd 0
cd 0
/data/media/0 # ←[6nls -la
ls -la
drwxrwx--- 39 media_rw media_rw 4096 Nov 16 06:22 .
drwxrwx--- 6 media_rw media_rw 4096 Nov 15 13:16 ..
drwxrwxr-x 2 media_rw media_rw 4096 Nov 15 13:56 .AlarmDroid
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 12:02 .premier_temp_pro
drwxrwx--- 3 media_rw media_rw 4096 Nov 15 12:02 .widgetsoid
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 12:02 AI Factory Stats
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 11:57 Alarms
drwxrwx--- 5 media_rw media_rw 4096 Nov 15 12:51 Android
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 12:03 CallLogBackupRestore
drwxrwx--- 5 media_rw media_rw 4096 Nov 15 13:32 DCIM
drwxrwx--- 4 media_rw media_rw 4096 Nov 15 16:32 Download
drwxrwx--- 4 media_rw media_rw 4096 Nov 15 12:08 MODS
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 12:09 Movies
drwxrwx--- 5 media_rw media_rw 4096 Nov 15 12:12 Music
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 12:13 Notifications
drwxrwx--- 9 media_rw media_rw 4096 Nov 15 12:15 Pictures
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 11:57 Podcasts
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 11:57 Ringtones
drwxrwxr-x 2 media_rw media_rw 4096 Nov 15 23:01 SMSBackupRestore
drwxrwx--- 3 media_rw media_rw 4096 Nov 15 12:20 TWRP
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 12:59 Video
drwxrwx--- 6 media_rw media_rw 4096 Nov 15 19:03 WhatsApp
drwxrwx--- 5 media_rw media_rw 4096 Nov 15 12:20 Widgetsoid
drwxrwx--- 4 media_rw media_rw 4096 Nov 15 12:20 _Daten
drwxrwx--- 3 media_rw media_rw 4096 Nov 15 12:02 adlayoutcache
drwxrwx--- 8 media_rw media_rw 4096 Nov 15 13:39 airdroid
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 12:02 albumthumbs
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 12:03 btcontroller
drwxrwxr-x 2 media_rw media_rw 4096 Nov 16 06:22 bugreports
drwxrwx--- 3 media_rw media_rw 4096 Nov 15 12:03 com.mictale.gpsessentials
drwxrwx--- 4 media_rw media_rw 4096 Nov 15 12:03 data
drwxrwx--- 6 media_rw media_rw 4096 Nov 15 12:08 droidsound
drwxrwx--- 3 media_rw media_rw 4096 Nov 15 12:08 lightflow
drwxrwx--- 8 media_rw media_rw 4096 Nov 15 12:13 navigator
drwxrwx--- 3 media_rw media_rw 4096 Nov 15 12:13 openfeint
drwxrwx--- 6 media_rw media_rw 4096 Nov 15 14:28 osmand
drwxrwxr-x 2 media_rw media_rw 4096 Nov 15 13:33 panoramas
drwxrwx--- 2 media_rw media_rw 4096 Nov 15 12:15 temp
drwxrwx--- 3 media_rw media_rw 4096 Nov 15 12:20 viber
/data/media/0 # ←[6nchown -R media_rw:media_rw .
chown -R media_rw:media_rw .
/data/media/0 # ←[6nfind . -type d -exec chmod 770 {} \;
find . -type d -exec chmod 770 {} \;
/data/media/0 # ←[6nfind . -type f -exec chmod 660 {} \;
find . -type f -exec chmod 660 {} \;
/data/media/0 # ←[6nsync
sync
/data/media/0 # ←[6nreboot
as you can see, the path to my virtual sdcard is /data/media/0, it may differs on your device.
The ADB Server need some time after booting TWRP, so if the command "adb-toolkit shell" says "device not found" (or simmilar), just repeat it again..
Good Luck
Click to expand...
Click to collapse
I'll try this.
Thank you so much

Mounting ext4 formatted sdcard?

I upgraded from the Note 1 with cyanogenmod 11 to the Note 4 (910C) with stock android (rooted).
I want to use the ext4 formatted external sdcard, but Samsung does not added ext4 support for the extSdCard (WHY???????????). Anyway, I managed to mount it, but I am only able to use it as root.
I used this script for this:
REALMNT=/mnt/media_rw/extSdCard
mount -t ext4 -o rw,noatime /dev/block/mmcblk1p1 "$REALMNT"
sdcard "$REALMNT" /storage/extSdCard 1023 1023 &
This script does mount the card, but with the wrong permissions.
I also changed the permissions in system/etc/permissions/platform.xml, no luck.
Some permissions:
# ls -la /storage (notice 1015 instead of 1028)
....
drwxrwxr-x 13 0 1015 4096 Jan 29 02:52 extSdCard
# ls -la /mnt/media_rw
drwx------ 9 1023 1028 0 Jan 29 03:30 .
drwxrwxr-x 7 0 1000 0 Jan 29 03:30 ..
drwx------ 2 1023 1023 0 Jan 29 03:30 UsbDriveA
drwx------ 2 1023 1023 0 Jan 29 03:30 UsbDriveB
drwx------ 2 1023 1023 0 Jan 29 03:30 UsbDriveC
drwx------ 2 1023 1023 0 Jan 29 03:30 UsbDriveD
drwx------ 2 1023 1023 0 Jan 29 03:30 UsbDriveE
drwx------ 2 1023 1023 0 Jan 29 03:30 UsbDriveF
drwxrwxrwx 13 1023 1023 4096 Jan 29 02:52 extSdCard
Clues?
Thanks!

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.

Rooting Samsung Galaxy Watch Active

Hey guys!
I'm searching around and I couldn't find a way to root SM-R500 Samsung Galaxy Watch Active (Tizen 4.0.0.3). I found a lot of firmware on different websites, but I couldn't find a rooted one. Any suggestions ...
Thanks
Depend what you expect...
Factory/Service Firmware called Combination Firmware is rooted...
I am using Combination Firmware as base... as Engineer sboot.bin (Bootloader) Engineer Kernel is inside...
From Stock Firmware only rootfs.img is modified... to have su Binary...
Problem...
SM-R500 nor other Galaxy variant tested...
Sugestion for you...
Flash Combination Firmware to see what kind of Root you can expect...
I could help you to modify Firmware Files... but OWN RISK...
Best Regards
adfree said:
Depend what you expect...
Factory/Service Firmware called Combination Firmware is rooted...
I am using Combination Firmware as base... as Engineer sboot.bin (Bootloader) Engineer Kernel is inside...
From Stock Firmware only rootfs.img is modified... to have su Binary...
Problem...
SM-R500 nor other Galaxy variant tested...
Sugestion for you...
Flash Combination Firmware to see what kind of Root you can expect...
I could help you to modify Firmware Files... but OWN RISK...
Best Regards
Click to expand...
Click to collapse
I don’t mind to give it a try. Please share what you have?
Sorry.
I waste tooo much time with Tizen...
I have limited time... and energy...
The long way is here:
https://forum.xda-developers.com/smartwatch/gear-s3/gear-s3-android-wear-port-wip-t3584588
Somewhere inside this Thread are infos how to play with rootfs.img...
The "faster" way for you or both of us... is.
Flash Combination Firmware for SM-R500 to see if this is what you want...
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
COMBINATION-FT40_R500XXU1ASG1.tar.md5
These 2 FT40 seems leaked and available... maybe somewhere in public...
I am too lazy to search for you.
TRy hard enough and in 2 days you can pm me... if you not able to find it...
Maybe I will upload for you...
But again.
What kind of magic you expect from Rooting of your SM-R500?
So I can make decission to help you... or maybe waste my time with other things.
Best Regards
Edit 1.
Code:
COMBINATION-FT40_R500XXU1[B]ASA5[/B].tar.md5
ASA5 I have on my HDD... I could upload...
Edit 2.
Uupsi.. I have both FT40...
Still no idea if somewhere public Link available...
Edit 3...
Lesson 1.
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
You "need" netOdin Tool for Flashing Firmware...
I will upload for you:
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
Need some time for upload...
Plese remember:
Own risk!
Best Regards
---------- Post added at 04:28 AM ---------- Previous post was at 03:35 AM ----------
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
https://www.file-upload.net/download-13786815/COMBINATION-FT40_R500XXU1ASA5.tar.md5.7z.html
Own risk!
Best Regards
adfree said:
Sorry.
I waste tooo much time with Tizen...
I have limited time... and energy...
The long way is here:
https://forum.xda-developers.com/smartwatch/gear-s3/gear-s3-android-wear-port-wip-t3584588
Somewhere inside this Thread are infos how to play with rootfs.img...
The "faster" way for you or both of us... is.
Flash Combination Firmware for SM-R500 to see if this is what you want...
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
COMBINATION-FT40_R500XXU1ASG1.tar.md5
These 2 FT40 seems leaked and available... maybe somewhere in public...
I am too lazy to search for you.
TRy hard enough and in 2 days you can pm me... if you not able to find it...
Maybe I will upload for you...
But again.
What kind of magic you expect from Rooting of your SM-R500?
So I can make decission to help you... or maybe waste my time with other things.
Best Regards
Edit 1.
Code:
COMBINATION-FT40_R500XXU1[B]ASA5[/B].tar.md5
ASA5 I have on my HDD... I could upload...
Edit 2.
Uupsi.. I have both FT40...
Still no idea if somewhere public Link available...
Edit 3...
Lesson 1.
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
You "need" netOdin Tool for Flashing Firmware...
I will upload for you:
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
Need some time for upload...
Plese remember:
Own risk!
Best Regards
---------- Post added at 04:28 AM ---------- Previous post was at 03:35 AM ----------
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
https://www.file-upload.net/download-13786815/COMBINATION-FT40_R500XXU1ASA5.tar.md5.7z.html
Own risk!
Best Regards
Click to expand...
Click to collapse
Sorry for the late reply and thank you adfree for your effort, but I already have and tested the combination firmware and It is not what I'm looking for! Now I'm trying to figure the pinout so I can connect it directly.
Done first attempt with DSL1 Firmware...
Waiting for feedback...
Meanwhile...
A
To enable Root access... SDB Tool required...
Code:
sdb root on
A.1
To enable su from Shell...
Additional steps required...
Code:
sdb root on
sdb shell
mount -vo remount,rw /
chmod -v +sx /usr/bin
Code:
sdb root off
Then you can su from shell...
Code:
su
then it asks for password... password is:
Code:
tizen
B
To check if you can now play with rootfs.img "on the fly"...
Code:
sdb root on
Or you have enbled the other way...
Code:
sdb shell
Code:
mount -vo remount,rw /
Now you can for instance delete poweron poweroff Animation... you can do more but this is safe... nothing will explode.
Code:
sdb root on
Switched to 'root' account mode
sdb shell
sh-3.2# cd /usr/share/edje
sh-3.2# ls -a1l
total 1280
drwxr-xr-x 5 root root 4096 Jun 27 2019 .
drwxr-xr-x 131 root root 4096 Jun 27 2019 ..
-rw-r--r-- 1 root root 322470 Apr 19 2019 360x360_PowerOff.edj
-rw-r--r-- 1 root root 227171 Apr 19 2019 360x360_PowerOn.edj
-rw-r--r-- 1 root root 6065 Apr 19 2019 csc-ani.edj
-rw-r--r-- 1 root root 6221 Apr 19 2019 factory-reset-util.edj
drwxr-xr-x 2 root root 4096 Jun 27 2019 images
drwxr-xr-x 2 root root 4096 Jun 27 2019 include
-rw-r--r-- 1 root root 295340 Apr 19 2019 poweroff.edj
-rw-r--r-- 1 root root 411726 Apr 19 2019 poweron.edj
-rw-r--r-- 1 root root 5656 Apr 19 2019 voice-control-elm.edj
drwxr-xr-x 2 root root 4096 Jun 27 2019 xwalk
Code:
rm poweron.edj
and/or
Code:
rm poweroff.edj
Be carefully what you remove or replace...
Best Regards
Seems to work... DSL1 rooted... tested in coop with:
Code:
COMBINATION-FT40_R500XXU1[B]ASL2[/B]
For some dump action I need some infos about partition layout...
Code:
[B]cat /proc/partitions[/B]
Example output from SM-Z130H and SM-R760...
Code:
major minor #blocks name
7 0 10052 loop0
7 1 17408 loop1
254 0 146152 zram0
179 0 3817472 mmcblk0
179 1 1024 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 9216 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2048 mmcblk0p12
179 13 2048 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 8192 mmcblk0p18
179 19 4096 mmcblk0p19
179 20 2048 mmcblk0p20
179 21 32768 mmcblk0p21
179 22 131072 mmcblk0p22
179 23 2641920 mmcblk0p23
179 24 917504 mmcblk0p24
179 96 512 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 128 7749632 mmcblk1
179 129 7748608 mmcblk1p1
Code:
sh-3.2# ls -l /dev/disk/by-partlabel
total 0
lrwxrwxrwx 1 root root 15 Apr 6 09:52 boot -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Apr 6 09:52 cm -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Apr 6 09:52 cpnvcore -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 15 Apr 6 09:52 csa -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 16 Apr 6 09:52 csc -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 16 Apr 6 09:52 module -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Apr 6 09:52 param -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk1 -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk2 -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 15 Apr 6 09:52 recovery -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 16 Apr 6 09:52 rootfs -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Apr 6 09:52 steady -> ../../mmcblk0p15
lrwxrwxrwx 1 root root 16 Apr 6 09:52 system-data -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 15 Apr 6 09:52 tup -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 16 Apr 6 09:52 user -> ../../mmcblk0p13
Code:
sh-3.2# ls -l /dev/disk/by-label
total 0
lrwxrwxrwx 1 root root 16 Apr 6 09:52 modules -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 10 Apr 6 09:52 ramdisk -> ../../ram0
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk-recovery -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Apr 6 09:52 rootfs -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Apr 6 09:52 tizen -> ../../mmcblk0p13
Code:
sh-3.2# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 320K 1 loop /opt/share/zoneinfo
loop1 7:1 0 13.6M 1 loop /usr/share/locale
zram0 254:0 0 279.3M 0 disk [SWAP]
mmcblk0rpmb 179:24 0 512K 0 disk
mmcblk0boot0 179:8 0 4M 1 disk
mmcblk0boot1 179:16 0 4M 1 disk
mmcblk0 179:0 0 3.7G 0 disk
|-mmcblk0p1 179:1 0 32M 0 part
|-mmcblk0p2 179:2 0 8M 0 part /csa
|-mmcblk0p3 179:3 0 2M 0 part
|-mmcblk0p4 179:4 0 20M 0 part
|-mmcblk0p5 179:5 0 8M 0 part
|-mmcblk0p6 179:6 0 8M 0 part
|-mmcblk0p7 179:7 0 3M 0 part
|-mmcblk0p8 259:0 0 16M 0 part
|-mmcblk0p9 259:1 0 16M 0 part
|-mmcblk0p10 259:2 0 16M 0 part /usr/lib/modules
|-mmcblk0p11 259:3 0 190M 0 part /opt/system/csc
|-mmcblk0p12 259:4 0 158M 0 part /opt
|-mmcblk0p13 259:5 0 1.9G 0 part /opt/usr
|-mmcblk0p14 259:6 0 1.3G 0 part
| `-rootfs 253:0 0 1.2G 1 crypt /
`-mmcblk0p15 259:7 0 256K 0 part
Thanx in advance.
Best Regards
Here the answer.
Thanx. :good:
SM-R500 DSL1
Code:
sh-3.2# cat /proc/partitions
major minor #blocks name
1 0 20480 ram0
1 1 20480 ram1
7 0 34240 loop0
7 1 384 loop1
254 0 284980 zram0
179 0 3817472 mmcblk0
179 1 8192 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 28160 mmcblk0p6
179 7 20480 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 2048 mmcblk0p9
259 2 6144 mmcblk0p10
259 3 3072 mmcblk0p11
259 4 18432 mmcblk0p12
259 5 18432 mmcblk0p13
259 6 10240 mmcblk0p14
259 7 4096 mmcblk0p15
259 8 194560 mmcblk0p16
259 9 172032 mmcblk0p17
259 10 1873408 mmcblk0p18
259 11 1439744 mmcblk0p19
259 12 256 mmcblk0p20
179 24 512 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
Code:
sh-3.2# ls -l /dev/disk/by-partlabel
total 0
lrwxrwxrwx 1 root root 16 Feb 8 11:11 afpc -> ../../mmcblk0p15
lrwxrwxrwx 1 root root 16 Feb 8 11:11 boot -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 16 Feb 8 11:11 cm -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 15 Feb 8 11:11 csa -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 16 Feb 8 11:11 csc -> ../../mmcblk0p16
lrwxrwxrwx 1 root root 15 Feb 8 11:11 module -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 16 Feb 8 11:11 nad_fw -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 15 Feb 8 11:11 nad_refer -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 15 Feb 8 11:11 param -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 15 Feb 8 11:11 ramdisk1 -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Feb 8 11:11 ramdisk2 -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 16 Feb 8 11:11 recovery -> ../../mmcblk0p13
lrwxrwxrwx 1 root root 16 Feb 8 11:11 rootfs -> ../../mmcblk0p19
lrwxrwxrwx 1 root root 15 Feb 8 11:11 smsn -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Feb 8 11:11 steady -> ../../mmcblk0p20
lrwxrwxrwx 1 root root 16 Feb 8 11:11 system-data -> ../../mmcblk0p17
lrwxrwxrwx 1 root root 15 Feb 8 11:11 tup -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Feb 8 11:11 tyd -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 16 Feb 8 11:11 up_param -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 16 Feb 8 11:11 user -> ../../mmcblk0p18
Code:
sh-3.2# ls -l /dev/disk/by-label
total 0
lrwxrwxrwx 1 root root 15 Feb 8 11:11 ramdisk -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Feb 8 11:11 ramdisk-recovery -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 16 Feb 8 11:11 tizen-csc -> ../../mmcblk0p16
lrwxrwxrwx 1 root root 16 Feb 8 11:11 tizen-rootfs -> ../../mmcblk0p19
lrwxrwxrwx 1 root root 16 Feb 8 11:11 tizen-system-da -> ../../mmcblk0p17
lrwxrwxrwx 1 root root 16 Feb 8 11:11 tizen-user -> ../../mmcblk0p18
Code:
sh-3.2# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 33.4M 1 loop /usr/share/locale
loop1 7:1 0 384K 1 loop /opt/share/zoneinfo
mmcblk0 179:0 0 3.7G 0 disk
|-mmcblk0p1 179:1 0 8M 0 part /csa
|-mmcblk0p2 179:2 0 2M 0 part
|-mmcblk0p3 179:3 0 1M 0 part
|-mmcblk0p4 179:4 0 512K 0 part
|-mmcblk0p5 179:5 0 512K 0 part
|-mmcblk0p6 179:6 0 27.5M 0 part
|-mmcblk0p7 179:7 0 20M 0 part
|-mmcblk0p8 259:0 0 8M 0 part
|-mmcblk0p9 259:1 0 2M 0 part
|-mmcblk0p10 259:2 0 6M 0 part
|-mmcblk0p11 259:3 0 3M 0 part
|-mmcblk0p12 259:4 0 18M 0 part
|-mmcblk0p13 259:5 0 18M 0 part
|-mmcblk0p14 259:6 0 10M 0 part
|-mmcblk0p15 259:7 0 4M 0 part
|-mmcblk0p16 259:8 0 190M 0 part /opt/system/csc
|-mmcblk0p17 259:9 0 168M 0 part /opt
|-mmcblk0p18 259:10 0 1.8G 0 part /opt/usr
|-mmcblk0p19 259:11 0 1.4G 0 part /
`-mmcblk0p20 259:12 0 256K 0 part
mmcblk0boot0 179:8 0 4M 1 disk
mmcblk0boot1 179:16 0 4M 1 disk
mmcblk0rpmb 179:24 0 512K 0 disk
zram0 254:0 0 278.3M 0 disk [SWAP]
Code:
mmcblk0p1 CSA
mmcblk0p2 TYD
mmcblk0p3 NAD_REFER
mmcblk0p4 SMSN
mmcblk0p5 MODULE
mmcblk0p6 TUP
mmcblk0p7 RAMDISK-RECOVERY
mmcblk0p8 RAMDISK
mmcblk0p9 PARAM
mmcblk0p10 UP_PARAM
mmcblk0p11 CM
mmcblk0p12 BOOT
mmcblk0p13 RECOVERY
mmcblk0p14 NAD_FW
mmcblk0p15 AFPC
mmcblk0p16 CSC
mmcblk0p17 SYSTEM-DATA
mmcblk0p18 USR
mmcblk0p19 ROOTFS
mmcblk0p20 STEADY
mmcblk0boot0 BOOT0
mmcblk0boot1 BOOT1
mmcblk0rpmb RPMB --->protected... NOT readable
mmcblk0 Full 4 GB eMMC
Best Regards
SM-R500 DSL1 summary for dd action... dump partitions... :angel:
We have 20 partitions p1 - p20
+ 3 additional
We are writing to USR partition p18... remember limited space... ca, 1500 MB free
Code:
dd if=/dev/mmcblk0boot0 of=/opt/usr/media/bootloader0.bin
dd if=/dev/mmcblk0boot1 of=/opt/usr/media/bootloader1.bin
[COLOR="Red"][B]dd if=/dev/mmcblk0rpmb of=/opt/usr/media/rpmb.bin[/B][/COLOR]
dd if=/dev/mmcblk0p1 of=/opt/usr/media/csa.bin
dd if=/dev/mmcblk0p2 of=/opt/usr/media/tyd.bin
dd if=/dev/mmcblk0p3 of=/opt/usr/media/nad_refer.bin
dd if=/dev/mmcblk0p4 of=/opt/usr/media/smsn.bin
dd if=/dev/mmcblk0p5 of=/opt/usr/media/module.bin
dd if=/dev/mmcblk0p6 of=/opt/usr/media/tup.bin
dd if=/dev/mmcblk0p7 of=/opt/usr/media/ramdisk-recovery.bin
dd if=/dev/mmcblk0p8 of=/opt/usr/media/ramdisk.bin
dd if=/dev/mmcblk0p9 of=/opt/usr/media/param.bin
dd if=/dev/mmcblk0p10 of=/opt/usr/media/up_param.bin
dd if=/dev/mmcblk0p11 of=/opt/usr/media/cm.bin
dd if=/dev/mmcblk0p12 of=/opt/usr/media/boot.bin
dd if=/dev/mmcblk0p13 of=/opt/usr/media/recovery.bin
dd if=/dev/mmcblk0p14 of=/opt/usr/media/nad_fw.bin
dd if=/dev/mmcblk0p15 of=/opt/usr/media/afpc.bin
dd if=/dev/mmcblk0p16 of=/opt/usr/media/csc.bin
dd if=/dev/mmcblk0p17 of=/opt/usr/media/system-data.bin
[COLOR="Red"][B]dd if=/dev/mmcblk0p18 of=/opt/usr/media/usr.bin[/B][/COLOR]
[COLOR="Red"][B]dd if=/dev/mmcblk0p19 of=/opt/usr/media/rootfs.bin[/B][/COLOR]
dd if=/dev/mmcblk0p20 of=/opt/usr/media/steady.bin
Red marked Commands...
rootfs to dump is not really usefull... remember free space...
usr is written to usr partition... so never possible to dump in 1 step...
rpmb read protected,,, found no way on Wearables...
To pull all files from Media folder...
Code:
sdb pull /opt/usr/media/
Or pull file by file with filename... example:
Code:
sdb pull /opt/usr/media/[B]csa.bin[/B]
Best Regards
To dump "whole" eMMC...
Limitation we have only maximum 1,8 GB... so we have tiny problem to put whole 4 GB...
To check free space...
Example taken from my SM-R760...
Code:
sh-3.2# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 1.3G 1.1G 200M 84% /
devtmpfs 340M 0 340M 0% /dev
/dev/mmcblk0p14 1.3G 1.1G 200M 84% /
/dev/mmcblk0p12 139M 85M 51M 63% /opt
/dev/mmcblk0p10 14M 253K 13M 2% /usr/lib/modules
tmpfs 352M 24K 352M 1% /dev/shm
tmpfs 352M 2.6M 349M 1% /run
tmpfs 352M 0 352M 0% /sys/fs/cgroup
tmpfs 352M 60K 352M 1% /tmp
/dev/loop0 384K 384K 0 100% /opt/share/zoneinfo
/dev/loop1 34M 34M 0 100% /usr/share/locale
/dev/mmcblk0p11 183M 101M 80M 56% /opt/system/csc
/dev/mmcblk0p2 6.8M 1.2M 5.0M 20% /csa
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr
tmpfs 71M 80K 71M 1% /run/user/5001
tmpfs 71M 0 71M 0% /run/user_ext/5001
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr/media
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr/apps
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr/home/owner/media
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr/media
sh-3.2# df -a
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 1298824 1064480 204612 84% /
devtmpfs 347224 0 347224 0% /dev
none 0 0 0 - /proc
sysfs 0 0 0 - /sys
/dev/mmcblk0p14 1298824 1064480 204612 84% /
/dev/mmcblk0p12 141376 86868 51276 63% /opt
/dev/mmcblk0p10 13847 253 13287 2% /usr/lib/modules
securityfs 0 0 0 - /sys/kernel/security
smackfs 0 0 0 - /sys/fs/smackfs
tmpfs 359712 24 359688 1% /dev/shm
devpts 0 0 0 - /dev/pts
tmpfs 359712 2628 357084 1% /run
tmpfs 359712 0 359712 0% /sys/fs/cgroup
cgroup 0 0 0 - /sys/fs/cgroup/systemd
pstore 0 0 0 - /sys/fs/pstore
cgroup 0 0 0 - /sys/fs/cgroup/net_cls
cgroup 0 0 0 - /sys/fs/cgroup/cpu,cpuacct
cgroup 0 0 0 - /sys/fs/cgroup/freezer
cgroup 0 0 0 - /sys/fs/cgroup/memory
debugfs 0 0 0 - /sys/kernel/debug
tmpfs 359712 60 359652 1% /tmp
configfs 0 0 0 - /sys/kernel/config
/dev/loop0 384 384 0 100% /opt/share/zoneinfo
/dev/loop1 34176 34176 0 100% /usr/share/locale
/dev/mmcblk0p11 187373 102462 81020 56% /opt/system/csc
/dev/mmcblk0p2 6907 1218 5117 20% /csa
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr
tmpfs 71940 80 71860 1% /run/user/5001
tmpfs 71940 0 71940 0% /run/user_ext/5001
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr/media
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr/apps
vip_cgroup 0 0 0 - /sys/fs/cgroup/vip
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr/home/owner/media
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr/media
Taken from here:
https://opensource.com/article/18/7/how-check-free-disk-space-linux
First attempt:
Code:
dd if=/dev/mmcblk0 of=/opt/usr/media/full4GB_eMMC.bin
dd stopps if usr partition is full...
Could lead to sideeffect...
But could be enough to pull result...
Code:
sh-3.2# dd if=/dev/mmcblk0 of=/opt/usr/media/full4GB_eMMC.bin
dd: writing to `/opt/usr/media/full4GB_eMMC.bin': [COLOR="Red"][B]No space left on device[/B][/COLOR]
3596569+0 records in
3596568+0 records out
1841442816 bytes (1.8 GB) copied, 151.265 s, 12.2 MB/s
Code:
sh-3.2# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 1.3G 1.1G 200M 84% /
devtmpfs 340M 0 340M 0% /dev
/dev/mmcblk0p14 1.3G 1.1G 200M 84% /
/dev/mmcblk0p12 139M 83M 53M 61% /opt
/dev/mmcblk0p10 14M 253K 13M 2% /usr/lib/modules
tmpfs 352M 24K 352M 1% /dev/shm
tmpfs 352M 2.5M 349M 1% /run
tmpfs 352M 0 352M 0% /sys/fs/cgroup
tmpfs 352M 60K 352M 1% /tmp
/dev/loop0 384K 384K 0 100% /opt/share/zoneinfo
/dev/loop1 34M 34M 0 100% /usr/share/locale
/dev/mmcblk0p11 183M 101M 80M 56% /opt/system/csc
/dev/mmcblk0p2 6.8M 1.2M 5.0M 20% /csa
[COLOR="Red"][B]/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr[/B][/COLOR]
tmpfs 71M 80K 71M 1% /run/user/5001
tmpfs 71M 0 71M 0% /run/user_ext/5001
[COLOR="Red"][B]/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr/media
/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr/apps
/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr/home/owner/media
/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr/media[/B][/COLOR]
Code:
sdb pull /opt/usr/media/full4GB_eMMC.bin
pulled full4GB_eMMC.bin 100% 1756MB
1 file(s) pulled. 0 file(s) skipped.
/opt/usr/media/full4GB_eMMC.bin 552 KB/s (1841442816 bytes in 3255.896s)
Pull seems 1 hour...
Best Regards
Code:
sh-3.2# dd if=/dev/mmcblk0 | gzip > /opt/usr/media/full4GB_eMMC.bin.gz
gzip: stdout: No space left on device
Creates corrupt/unfinished archive file... but have 2200 MB inside... few more as uncompressed...
Better we split... and find other way for user partition...
.
.
.
Best Regards
Maybe found something...
Code:
sdb shell dd if=/dev/mmcblk0boot1>testme11.bin
sdb shell dd if=/dev/mmcblk0boot0>testme11more.bin
sdb shell dd if=/dev/mmcblk0rpmb>testme11moreAA.bin
Now need more time for next attempt...
Code:
sdb shell dd if=/dev/mmcblk0>FULLeMMCoverSDB_WiFi.bin
4 GB !
IMHO 1 - 2 hours...
Best Regards
Rooted SM-R500 DSL1 Firmware is here:
https://forum.xda-developers.com/showpost.php?p=81762345&postcount=838
If Questions... better ask BEFORE...
Best Regards
Hmmm... I don't know why...
But if I direct dump to PC... then additional crap is written...
2 Bytes...
Code:
0D0D
I have Tizen handset... SM-Z130H... with Tizen 2.4...
Here this work as it seems, tested with Command:
Code:
sdb shell dd if=/dev/mmcblk0boot1>Z1_boot1.bin
This partition is ever empty... contains only 00... so IMHO good reference...
But my Z1 is connected via USB cable...
No idea if 0D0D cames because some TCP problem...
Best Regards
With SM-R760 we have luck...
Combination Firmware not mandatory for Tizen 4 Root...
Only RAMDISK taken from Combination Firmware...
Maybe this is also working for SM-R500... need to be tested.
Attached is ramdisk.img from FT40 ASL2 for SM-R500...
Best Regards
I0T said:
Hey guys!
I'm searching around and I couldn't find a way to root SM-R500 Samsung Galaxy Watch Active (Tizen 4.0.0.3). I found a lot of firmware on different websites, but I couldn't find a rooted one. Any suggestions ...
Thanks
Click to expand...
Click to collapse
Hey there! Could you finally root the SM-R500? Is it still alive? Have the same model here... I used to root all Samsung I had but this is my very first watch so I do not want to mess it yet without anyone proofs
Your Firmware Version?
I have only rooted DSL1 for SM-R500...
Best Regards
adfree said:
Your Firmware Version?
I have only rooted DSL1 for SM-R500...
Best Regards
Click to expand...
Click to collapse
Hi adfree, It seems DSL1, lastest Samsung update.. I have read about combination firmwares etc.. but not tired anything without being sure cause is the most expensive watch i ever bought..
The most combinations firms seems for others than R500, I don't know either about knox on watch if will be tripped too and will left samsung pay useless or it works different than phones..
Yesterday I downloaded all tizen SDK tools etc... and sideloaded tpk apps to watch, they install but could not run them propperly.. but I guess all this is about to test yet as it is a "new watch" ...sorry my ignorance but I come from a LG watch from 2015 omg I had to update myself... xD
Thank you and have a nice day !
@Albayeah
Sorry.
In main I am talking with my self... about Rooting...
No idea why user not confirm in public...
I know he used the old method with Combination Firmware first... then my rooted rootfs,img...
The new way... is to flash only RAMDISK from Combination Firmware, then my rooted files.
So Round 1:
with netOdin
https://forum.xda-developers.com/showpost.php?p=81799723&postcount=15
Round 2.
with netOdin
IGNORE the Combination Firmware files
https://forum.xda-developers.com/showpost.php?p=81762345&postcount=838
Only this:
https://www.file-upload.net/download-13891175/2020_DSL1_smR500_ROOT_v1.7z.html
Own Risk!
But I am 99,9 % sure this is working. :angel:
Best Regards
adfree said:
@Albayeah
Sorry.
In main I am talking with my self... about Rooting...
No idea why user not confirm in public...
I know he used the old method with Combination Firmware first... then my rooted rootfs,img...
The new way... is to flash only RAMDISK from Combination Firmware, then my rooted files.
So Round 1:
with netOdin
https://forum.xda-developers.com/showpost.php?p=81799723&postcount=15
Round 2.
with netOdin
IGNORE the Combination Firmware files
https://forum.xda-developers.com/showpost.php?p=81762345&postcount=838
Only this:
https://www.file-upload.net/download-13891175/2020_DSL1_smR500_ROOT_v1.7z.html
Own Risk!
But I am 99,9 % sure this is working. :angel:
Best Regards
Click to expand...
Click to collapse
Many thanks! I am going to save your files by the moment because I am still afraid of messing something definetly on the watch with no reverse..
Maybe I have to do more research..
I hope I dont bother you with my questions but if you already rooted.. could you use samsung apps as usual..? Like samsung health, samsung pay.. won't prompt a security message or disable any functions, any apps..?
Sorry cause i am kinda confused with that details..
On phone I use Samsung apps hiding with magisk etc... cause it is rooted but it is Android, but what about watch with tizen and no magisk..? Will disable the apps just like in the phone, or is it knox unrecoverable? :silly:
Sorry for my inexperience maybe all this sounded silly to you XDD
Best wishes to all on these hard times :good:

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.

Categories

Resources