Related
Let's collect and share some developer relevant infos about the h60.
KERNEL TOOLBOX:
http://forum.xda-developers.com/honor-6/orig-development/honor-6-kernel-toolbox-t3011000
Latest kernel sources and various stock ramdisks included.
Kernel sources for L01, L02, L03, L11, L12 and L21 are identical.
L04 doesn't boot using a kernel built from sources from above variants.
Seems to be different.
Code:
Kernel address 0x608000
Ramdisk address 0x300000
Secondary address 0x1500000
Kernel tags address 0x200000
Flash page size 2048
Command line "vmalloc=384M [email protected] psci=enable mmcparts=mmcblk0:p1(vrl),p2(vrl_backup),p7(modemnvm_factory),p18(splash),p22(dfx),p23(modemnvm_backup),p24(modemnvm_img),p25(modemnvm_system),p26(modem),p27(modem_dsp),p28(modem_om),p29(modemnvm_update),p30(3rdmodem),p31(3rdmodemnvm),p32(3rdmodemnvmbkp)"
Base: 0x00000000 || 0x001FFF00
Kernel offset: 0x00608000 || 0x00408100
Ramdisk offset: 0x00300000 || 0x00100100
Second offset: 0x01500000 || 0x00D00100
Tags offset: 0x00200000 || 0x00000100
RIL:
libbalong-ril.so and libbalong-ril-1.so are different across variants.
Everything else is identical.
SYSTEM:
build.prop - 6.94 KB from H60-L02V100R001CHNC00B310
PARTITIONS:
Code:
ls -al /dev/block/platform/ff1fe000.dwmmc0/by-name
lrwxrwxrwx root root 2015-01-16 16:33 3rdmodem -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-01-16 16:33 3rdmodemnvm -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-01-16 16:33 3rdmodemnvmbkp -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-01-16 16:33 boot -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-01-16 16:33 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 2015-01-16 16:33 cust -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2015-01-16 16:33 dfx -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-01-16 16:33 dts -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-01-16 16:33 fastboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-01-16 16:33 fw_hifi -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-01-16 16:33 fw_lpm3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-01-16 16:33 hibench -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-01-16 16:33 hisitest0 -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-01-16 16:33 hisitest1 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-01-16 16:33 misc -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-01-16 16:33 modem -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2015-01-16 16:33 modem_dsp -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-01-16 16:33 modem_om -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-01-16 16:33 modemnvm_backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-01-16 16:33 modemnvm_factory -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-01-16 16:33 modemnvm_img -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-01-16 16:33 modemnvm_system -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-01-16 16:33 modemnvm_update -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-01-16 16:33 nvme -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-01-16 16:33 oeminfo -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-01-16 16:33 recovery -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-01-16 16:33 recovery2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-01-16 16:33 reserved1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-01-16 16:33 reserved2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-01-16 16:33 secure_storage -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-01-16 16:33 sensorhub -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-01-16 16:33 splash -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-01-16 16:33 splash2 -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-01-16 16:33 splash3 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-01-16 16:33 system -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2015-01-16 16:33 teeos -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-01-16 16:33 userdata -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 2015-01-16 16:33 vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-01-16 16:33 vrl_backup -> /dev/block/mmcblk0p2
Code:
cat /proc/partitions
major minor #blocks name
7 0 13545 loop0
7 1 49928 loop1
179 0 15267840 mmcblk0
179 1 128 mmcblk0p1
179 2 128 mmcblk0p2
179 3 1664 mmcblk0p3
179 4 1792 mmcblk0p4
179 5 256 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 4096 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 4096 mmcblk0p9
179 10 2048 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 8192 mmcblk0p13
179 14 15360 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 32768 mmcblk0p16
179 17 32768 mmcblk0p17
179 18 8192 mmcblk0p18
179 19 8192 mmcblk0p19
179 20 32768 mmcblk0p20
179 21 20480 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 4096 mmcblk0p23
179 24 8192 mmcblk0p24
179 25 4096 mmcblk0p25
179 26 61440 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 12288 mmcblk0p28
179 29 24576 mmcblk0p29
179 30 131072 mmcblk0p30
179 31 32768 mmcblk0p31
179 32 16384 mmcblk0p32
179 33 65536 mmcblk0p33
179 34 2048 mmcblk0p34
179 35 2048 mmcblk0p35
179 36 524288 mmcblk0p36
179 37 1572864 mmcblk0p37
179 38 262144 mmcblk0p38
179 39 12339200 mmcblk0p39
179 120 4096 mmcblk0rpmb
179 80 4096 mmcblk0boot1
179 40 4096 mmcblk0boot0
31 0 128 mtdblock0
31 1 128 mtdblock1
31 2 4096 mtdblock2
31 3 4096 mtdblock3
31 4 4096 mtdblock4
31 5 61440 mtdblock5
31 6 4096 mtdblock6
31 7 24576 mtdblock7
179 160 15646720 mmcblk1
179 161 15642624 mmcblk1p1
31 8 4096 mtdblock8
253 0 13545 dm-0
253 1 49927 dm-1
@codeworkx Very useful information for the developers...! Have you tried to build a CM. Or at least a cwm recovery...?
root-expert said:
@codeworkx Very useful information for the developers...! Have you tried to build a CM. Or at least a cwm recovery...?
Click to expand...
Click to collapse
1st step: unpack stock boot image, repack it, boot it
2nd step: build kernel from sources, pack it with stock ramdisk, boot it
3rd step: start brewing cm
Just to make it clear.
I don't own a honor 6 so i'll not do any development.
It's up to the community.
Had a look at their kernel sources and tried to build it.
This is a pure mess. I've never seen such a chaos before.
Is it even worse than mtk?
Sent from my H60-L02 using Tapatalk
Problem is that the community for this device is really small, at least the potential developer part of it. Additionally, I'm trying to build CM for it but damn is it a hassle as a newbie..
codeworkx said:
Just to make it clear.
I don't own a honor 6 so i'll not do any development.
It's up to the community.
Had a look at their kernel sources and tried to build it.
This is a pure mess. I've never seen such a chaos before.
Click to expand...
Click to collapse
Thanks very much for your interest!!
I'm reading more guides about CM buildilng from source and I started to set up my computer.
Than I signed on Github and I found your dir.
I googled you before I'he found this thread: I'm really honored of Your concern about Honor 6!
We started a petition too, in order to involve our community and devs and start the development of this device.
Like @panamera2011 said, it would be really great if someone like you, began to support our work!
You're right, almost all developers continue to buy the same devices because with cpu Qualcom is easier to build rom cm
nrpetonr said:
Is it even worse than mtk?
Sent from my H60-L02 using Tapatalk
Click to expand...
Click to collapse
for me it's all the same.
mtk, rockchip, hisilicon....
their kernel sources are a pure accident und the community support is below zero.
and it seems that huawei doesn't make it better.
panamera2011 said:
You're right, almost all developers continue to buy the same devices because with cpu Qualcom is easier to build rom cm
Click to expand...
Click to collapse
Maybe not easier, but there's documentation and sourcecode available.
That's a huge difference.
codeworkx said:
for me it's all the same.
mtk, rockchip, hisilicon....
their kernel sources are a pure accident und the community support is below zero.
and it seems that huawei doesn't make it better.
Click to expand...
Click to collapse
What do you mean by pure accident ? As in really messy coding ?
Didn't have a close look at their code.
The way the hisilocon drivers are organized is messy. And it seems they've copied parts of the userspace into the kernel. That stuff doesn't belong there.
And they've copied samsungs exfat driver from one of the i9100 custom kernels.
I'm not able to build the kernel with enabled balong modem stuff because of their mess.
codeworkx said:
Didn't have a close look at their code.
The way the hisilocon drivers are organized is messy. And it seems they've copied parts of the userspace into the kernel. That stuff doesn't belong there.
And they've copied samsungs exfat driver from one of the i9100 custom kernels.
I'm not able to build the kernel with enabled balong modem stuff because of their mess.
Click to expand...
Click to collapse
Sounds like chaos as you described earlier.. Its too bad that things have been built this way. Would getting information from honor (aka huawei) help ? And if so what information would that be ?
Honor is quite close to the community over on a French forum I'm a member of and they seem to be eager to make a good impression for their phones on the European market so I'm pretty sure they wouldn't mind sharing information as custom ROM development is quite a big deal for android devices and if they get into that their market shares would explode considering how well the phone has been doing so far..! What's missing is really this customisation ..!
Dervisk said:
Sounds like chaos as you described earlier.. Its too bad that things have been built this way. Would getting information from honor (aka huawei) help ? And if so what information would that be ?
Honor is quite close to the community over on a French forum I'm a member of and they seem to be eager to make a good impression for their phones on the European market so I'm pretty sure they wouldn't mind sharing information as custom ROM development is quite a big deal for android devices and if they get into that their market shares would explode considering how well the phone has been doing so far..! What's missing is really this customisation ..!
Click to expand...
Click to collapse
I've already written a mail to huawei. let's see how it goes.
some more information.
@codeworkx
some more information to complete OP that user @spanorg could collect following that thread http://forum.xda-developers.com/showthread.php?t=2450045.
http://pastebin.com/xSuphPVT
http://pastebin.com/pwknz0FA
i attached them in that post as zip cos pastebin is not eternal. xD
desalesouche said:
@codeworkx
some more information to complete OP that user @spanorg could collect following that thread http://forum.xda-developers.com/showthread.php?t=2450045.
http://pastebin.com/xSuphPVT
http://pastebin.com/pwknz0FA
i attached them in that post as zip cos pastebin is not eternal. xD
Click to expand...
Click to collapse
@desalesouche what model of Honor 6 uses?
I use H60-L02
panamera2011 said:
@desalesouche what model of Honor 6 uses?
I use H60-L02
Click to expand...
Click to collapse
from what i know @spanorg use L02
just 4 info:
the kernel sourcecode release from huawei is incomplete and broken.
they didn't release needed tools which they've used to build the kernel and there are some missing vxworks headers.
if you've managed to build a kernel, then baseband and audio will be dead.
i've written a mail. let's see what happens.
Is it possible to built a cm version and use the available compiled kernel?
Julsen1985 said:
Is it possible to built a cm version and use the available compiled kernel?
Click to expand...
Click to collapse
yes, but radio and audio might be broken.
can't say for sure. i've still no honor 6.
I was wondering where init.d might be located on 5X? Not able to find it in /system/etc/ like most devices.
Basically trying to include a new init.d script but not sure where to put it.
Thanks in advance!
catharsis724 said:
I was wondering where init.d might be located on 5X? Not able to find it in /system/etc/ like most devices.
Basically trying to include a new init.d script but not sure where to put it.
Thanks in advance!
Click to expand...
Click to collapse
Try placing in /su/su.d/ if you're rooted with superSU
Sent from my SHIELD Tablet K1 using Tapatalk
Exile1975 said:
Try placing in /su/su.d/ if you're rooted with superSU
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
Might not have that because I have systemless phh Superuser.
Code:
bullhead:/ # ls
...
drwxr-xr-x 3 0 2016-11-28 00:38 res
drwx------ 2 0 2016-11-07 18:55 root
drwxr-xr-x 3 4.0K 2016-11-28 11:20 sbin
lrwxrwxrwx 1 21 2016-11-28 00:38 sdcard -> /storage/self/primary
-rw-r--r-- 1 758 2016-11-28 00:38 seapp_contexts
-rw-r--r-- 1 68 2016-11-28 00:38 selinux_version
-rw-r--r-- 1 203K 2016-11-28 00:38 sepolicy
-rw-r--r-- 1 11K 2016-11-28 00:38 service_contexts
drwxr-xr-x 4 80 2016-11-28 11:20 storage
dr-xr-xr-x 13 0 1971-01-18 11:50 sys
drwxr-xr-x 17 4.0K 2016-11-27 15:50 system
...
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.
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.
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: