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.
Related
Hi guys I got Xperia T3 D5102 few days back.
I rooted it & deodexed rom & now making few mods.
I tried making advance reboot Mod with restart options to recovery, system restart & soft reboot.
Reboot & soft reboot option is working fine but reboot to Recovery is not working. It ends up in just normal reboot of phone.
Also I tried to go the hardware way by trying key combinations in many ways
Power + Volume up/down doesn't work
Power + Volume both btns also didn't work.
Also tried using ADB commands for Advance power menu . But no luck then too.
I suspect there is no recovery partition and hence didn't boot.
The below table shows the partition table
Code:
Number Start End Size File system Name F
1 131kB 2228kB 2097kB TA
2 2228kB 2753kB 524kB sbl1
3 2753kB 3015kB 262kB s1sbl
4 3015kB 3080kB 65.5kB dbi
5 3080kB 3604kB 524kB aboot
6 3604kB 4129kB 524kB rpm
7 4129kB 4653kB 524kB tz
8 4653kB 5177kB 524kB alt_sbl1
9 5177kB 5439kB 262kB alt_s1sbl
10 5439kB 5505kB 65.5kB alt_dbi
11 5505kB 6029kB 524kB alt_aboot
12 6029kB 6554kB 524kB alt_rpm
13 6554kB 7078kB 524kB alt_tz
14 8389kB 9961kB 1573kB fsg
15 12.6MB 14.2MB 1573kB modemst1
16 16.8MB 18.4MB 1573kB modemst2
17 21.0MB 37.7MB 16.8MB ext4 persist
18 37.7MB 105MB 67.1MB fat16 modem
19 105MB 126MB 21.0MB boot
20 126MB 136MB 10.5MB fat32 ramdump
21 136MB 153MB 16.8MB FOTAKernel
22 153MB 153MB 32.8kB DDR
23 153MB 170MB 16.8MB ext4 LTALabel
24 172MB 180MB 8389kB apps_log
25 180MB 2248MB 2068MB ext4 system
26 2248MB 2458MB 210MB ext4 cache
27 2458MB 7818MB 5360MB ext4 userdata
(parted)
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 2048 mmcblk0p1
179 2 512 mmcblk0p2
179 3 256 mmcblk0p3
179 4 64 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 256 mmcblk0p9
179 10 64 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1536 mmcblk0p15
179 16 1536 mmcblk0p16
179 17 16384 mmcblk0p17
179 18 65536 mmcblk0p18
179 19 20480 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 32 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 8192 mmcblk0p24
179 25 2019328 mmcblk0p25
179 26 204800 mmcblk0p26
179 27 5234671 mmcblk0p27
179 32 512 mmcblk0rpmb
179 64 7761920 mmcblk1
179 65 7760896 mmcblk1p1
[email protected]:/ $
Need help from developers /modders on how to proceed further and lemme know some hint to proceed.
I suspect recovery partition missing. Anyone can confirm the same ? The above table would give a clear layout of the memory partitions of the phone.
Request someone to throw light on this !
Thanks
Hello, just a question : how did you root your T3 ? are you allways on .14 ?
dan15 said:
Hello, just a question : how did you root your T3 ? are you allways on .14 ?
Click to expand...
Click to collapse
Yes my Android version is 4.4.2 build version is 18.2.A.1.14
ok, as my D5103 is ugrade to .17, i have to wait for a solution, if i don't want to downgrade, but i'm not sure that the rot will stay if i upgrade after root on .14...
Xperia devices don't have a recovery partition. Neither do they have any stock recovery.
AJ
Abhinav2 said:
Xperia devices don't have a recovery partition. Neither do they have any stock recovery.
AJ
Click to expand...
Click to collapse
You wrong, only a few xperia devices does NOT have a recovery partition, all others have it
CreasingMass Dev said:
You wrong, only a few xperia devices does NOT have a recovery partition, all others have it
Click to expand...
Click to collapse
None of them has AFAIK. Can u give some example of device which might have? Because recovery is basically flashed in FOTA partition
AJ
Al parecer no existe recovery
Xenon1978 said:
Hi guys I got Xperia T3 D5102 few days back.
I rooted it & deodexed rom & now making few mods.
I tried making advance reboot Mod with restart options to recovery, system restart & soft reboot.
Reboot & soft reboot option is working fine but reboot to Recovery is not working. It ends up in just normal reboot of phone.
Also I tried to go the hardware way by trying key combinations in many ways
Power + Volume up/down doesn't work
Power + Volume both btns also didn't work.
Also tried using ADB commands for Advance power menu . But no luck then too.
I suspect there is no recovery partition and hence didn't boot.
The below table shows the partition table
Code:
Number Start End Size File system Name F
1 131kB 2228kB 2097kB TA
2 2228kB 2753kB 524kB sbl1
3 2753kB 3015kB 262kB s1sbl
4 3015kB 3080kB 65.5kB dbi
5 3080kB 3604kB 524kB aboot
6 3604kB 4129kB 524kB rpm
7 4129kB 4653kB 524kB tz
8 4653kB 5177kB 524kB alt_sbl1
9 5177kB 5439kB 262kB alt_s1sbl
10 5439kB 5505kB 65.5kB alt_dbi
11 5505kB 6029kB 524kB alt_aboot
12 6029kB 6554kB 524kB alt_rpm
13 6554kB 7078kB 524kB alt_tz
14 8389kB 9961kB 1573kB fsg
15 12.6MB 14.2MB 1573kB modemst1
16 16.8MB 18.4MB 1573kB modemst2
17 21.0MB 37.7MB 16.8MB ext4 persist
18 37.7MB 105MB 67.1MB fat16 modem
19 105MB 126MB 21.0MB boot
20 126MB 136MB 10.5MB fat32 ramdump
21 136MB 153MB 16.8MB FOTAKernel
22 153MB 153MB 32.8kB DDR
23 153MB 170MB 16.8MB ext4 LTALabel
24 172MB 180MB 8389kB apps_log
25 180MB 2248MB 2068MB ext4 system
26 2248MB 2458MB 210MB ext4 cache
27 2458MB 7818MB 5360MB ext4 userdata
(parted)
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 2048 mmcblk0p1
179 2 512 mmcblk0p2
179 3 256 mmcblk0p3
179 4 64 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 256 mmcblk0p9
179 10 64 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1536 mmcblk0p15
179 16 1536 mmcblk0p16
179 17 16384 mmcblk0p17
179 18 65536 mmcblk0p18
179 19 20480 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 32 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 8192 mmcblk0p24
179 25 2019328 mmcblk0p25
179 26 204800 mmcblk0p26
179 27 5234671 mmcblk0p27
179 32 512 mmcblk0rpmb
179 64 7761920 mmcblk1
179 65 7760896 mmcblk1p1
[email protected]:/ $
Need help from developers /modders on how to proceed further and lemme know some hint to proceed.
I suspect recovery partition missing. Anyone can confirm the same ? The above table would give a clear layout of the memory partitions of the phone.
Request someone to throw light on this !
Thanks
Click to expand...
Click to collapse
No se si alguno de ustedes o tengo instalar un gestor de recuperación (Recovery) anteriormente a este modelo
Ahora he intentado hacerlo y puff.. el paquete ABD me dice que no EXISTE
Code:
FAILED <remote: Recovery partición doesn't founded>
After flashing xposed 64bit the H815 will not boot. We need someone to dump the system partion so we have a way to restore system until kdz is available.
After someone dumps and uploads the system.img we should just be able to flash via fastboot.
Mine is coming tomorrow. I'll gladly do it if you tell me how to dump it.
IlyaKol said:
Mine is coming tomorrow. I'll gladly do it if you tell me how to dump it.
Click to expand...
Click to collapse
Sure here's a guide.. http://forum.xda-developers.com/showthread.php?t=2450045
If you need help pm me
macdaddie87 said:
Sure here's a guide.. http://forum.xda-developers.com/showthread.php?t=2450045
If you need help pm me
Click to expand...
Click to collapse
I'm a system engineer (server support, etc.) so I should be able to handle it. Just needed to be pointed in the right direction. I shall post up tomorrow.
macdaddie87 said:
After flashing xposed 64bit the H815 will not boot. We need someone to dump the system partion so we have a way to restore system until kdz is available.
After someone dumps and uploads the system.img we should just be able to flash via fastboot.
Click to expand...
Click to collapse
Scratch that, evidently root is only available for the EU H815 and mine is the Taiwan one, from what I know. I'll see if I get lucky somehow, but by the looks of it I won't be able to provide the dump since I can't achieve root.
Some help
http://forum.xda-developers.com/g4/development/rom-docs-testrom-t3126728
Code:
major minor #blocks name
253 0 721772 zram0
179 0 30535680 mmcblk0
179 1 88064 mmcblk0p1
179 2 512 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 512 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 2048 mmcblk0p14
179 15 512 mmcblk0p15
179 16 512 mmcblk0p16
179 17 512 mmcblk0p17
179 18 512 mmcblk0p18
179 19 512 mmcblk0p19
179 20 512 mmcblk0p20
179 21 1536 mmcblk0p21
179 22 16384 mmcblk0p22
179 23 32768 mmcblk0p23
179 24 1536 mmcblk0p24
179 25 1536 mmcblk0p25
179 26 1536 mmcblk0p26
179 27 512 mmcblk0p27
179 28 512 mmcblk0p28
179 29 512 mmcblk0p29
179 30 2048 mmcblk0p30
179 31 512 mmcblk0p31
259 0 512 mmcblk0p32
259 1 512 mmcblk0p33
259 2 512 mmcblk0p34
259 3 2048 mmcblk0p35
259 4 4096 mmcblk0p36
259 5 49152 mmcblk0p37
259 6 40960 mmcblk0p38
259 7 40960 mmcblk0p39
259 8 8192 mmcblk0p40
259 9 8192 mmcblk0p41
259 10 32768 mmcblk0p42
259 11 47104 mmcblk0p43
259 12 10240 mmcblk0p44
259 13 4096 mmcblk0p45
259 14 4096 mmcblk0p46
259 15 4239360 mmcblk0p47
259 16 262144 mmcblk0p48
259 17 1261568 mmcblk0p49
259 18 24313856 mmcblk0p50
259 19 12271 mmcblk0p51
179 32 4096 mmcblk0rpmb
DDR -> /dev/block/mmcblk0p30
aboot -> /dev/block/mmcblk0p8
abootbak -> /dev/block/mmcblk0p14
apdp -> /dev/block/mmcblk0p18
boot -> /dev/block/mmcblk0p38
cache -> /dev/block/mmcblk0p49
cust -> /dev/block/mmcblk0p48
devinfo -> /dev/block/mmcblk0p17
po -> /dev/block/mmcblk0p20
drm -> /dev/block/mmcblk0p40
eksst -> /dev/block/mmcblk0p33
encrypt -> /dev/block/mmcblk0p32
factory -> /dev/block/mmcblk0p43
fota -> /dev/block/mmcblk0p44
fsc -> /dev/block/mmcblk0p27
fsg -> /dev/block/mmcblk0p26
grow -> /dev/block/mmcblk0p51
hyp -> /dev/block/mmcblk0p6
hypbak -> /dev/block/mmcblk0p12
keystore -> /dev/block/mmcblk0p29
laf -> /dev/block/mmcblk0p37
limits -> /dev/block/mmcblk0p16
misc -> /dev/block/mmcblk0p22
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p24
modemst2 -> /dev/block/mmcblk0p25
mpt -> /dev/block/mmcblk0p42
msadp -> /dev/block/mmcblk0p19
persist -> /dev/block/mmcblk0p23
pmic -> /dev/block/mmcblk0p2
pmicbak -> /dev/block/mmcblk0p10
raw_resources -> /dev/block/mmcblk0p45
raw_resourcesbak -> /dev/block/mmcblk0p46
rct -> /dev/block/mmcblk0p34
recovery -> /dev/block/mmcblk0p39
rpm -> /dev/block/mmcblk0p7
rpmbak -> /dev/block/mmcblk0p13
sbl1 -> /dev/block/mmcblk0p3
sbl1bak -> /dev/block/mmcblk0p9
sdi -> /dev/block/mmcblk0p5
sdibak -> /dev/block/mmcblk0p15
sec -> /dev/block/mmcblk0p31
sns -> /dev/block/mmcblk0p41
spare1 -> /dev/block/mmcblk0p21
spare2 -> /dev/block/mmcblk0p36
ssd -> /dev/block/mmcblk0p28
system -> /dev/block/mmcblk0p47
tz -> /dev/block/mmcblk0p4
tzbak -> /dev/block/mmcblk0p11
userdata -> /dev/block/mmcblk0p50
I can't unlock the BL as I'm a TW phone not an EU phone. Sorry OP.
Nokia X Partition
Partition - Mount - Alias
INTERNAL Storage
mmcblk0p16 - /persist - p16
mmcblk0p18 - /system - p18
mmcblk0p19 - /cache - p19
mmcblk0p21 -/storage/sdcard-p21
mmcblk0p22 -/data - p22
mmcblk0p23 -/variant - p23
mmcblk0p25 -/preload - p25
mmcblk0p3 - /bootloader - p3
mmcblk0p17 - /boot - p17
EXTERNAL STORAGE
mmcblk1p1 - /storage/sdcard1 - p1
mmcblkxpxx where XX is the number of the persist partition.
Rest of the blocks(XX) occupy little amount of space and by default they are NOT MOUNTED.
This post is only for knowledge purpose for those (ofcourse people like me,noob)who are confused or don't know the right partition for flashing
matrixex said:
can you help me i just wanted to flash Persist.img but don't know the partition
I'm currently on Jellybean 4.1.2 and
which partition i should choose i have tried
package_extract_file("pesrist.img", "/dev/block/platform/msm_sdcc.1/by-num/p1");
on updater script but results corrupted files in memory card
so please help me
thanks-matriex
Click to expand...
Click to collapse
A few points:
1) you have a typo in your command. You wrote pesrist instead of persist.
2) what device are you using?
3) try either this: package_extract_file("persist.img", "/dev/block/platform/msm_sdcc.1/by-name/persist");
or this, which I typically use:
package_extract_file("persist.img", "/tmp/persist.img");
run_program("/sbin/busybox", "dd", "if=/tmp/persist.img", "of=/dev/block/platform/msm_sdcc.1/by-name/persist");
delete("/tmp/persist.img");
efrant said:
A few points:
1) you have a typo in your command. You wrote pesrist instead of persist.
2) what device are you using?
3) try either this: package_extract_file("persist.img", "/dev/block/platform/msm_sdcc.1/by-name/persist");
or this, which I typically use:
package_extract_file("persist.img", "/tmp/persist.img");
run_program("/sbin/busybox", "dd", "if=/tmp/persist.img", "of=/dev/block/platform/msm_sdcc.1/by-name/persist");
delete("/tmp/persist.img");
Click to expand...
Click to collapse
Thanks
I am on Nokia x RM-980
I just flashed persist.img to persist
Partition but I flashed it in wrong partition "Dev/block/platform/msm_sdcc.1/by-num/p1"
After this my IMIE vanished
Again Thanks it is really pleasure to talk to a dev
matrixex said:
[snip]
Hey last question
fastboot -i 0x0421 flash persist persist.img
For flashing from adb this command is for my device
I found it on xda nokia x topic
But can you explain whay does 0x0421
Means
Click to expand...
Click to collapse
According to fastboot syntax, the "-i" option is for specifying a custom USB vendor ID, so 0x0421 is the USB vendor ID for your device. Are you using using Linux? I don't think it does anything on Windows.
Sent from my HTC One M9 using Tapatalk
efrant said:
According to fastboot syntax, the "-i" option is for specifying a custom USB vendor ID, so 0x0421 is the USB vendor ID for your device. Are you using using Linux? I don't think it on Windows
Click to expand...
Click to collapse
No I am on windows using fastboot.exe and adb.exe on a folder
efrant said:
A few points:
package_extract_file("persist.img", "/tmp/persist.img");
run_program("/sbin/busybox", "dd", "if=/tmp/persist.img", "of=/dev/block/platform/msm_sdcc.1/by-name/persist");
delete("/tmp/persist.img");
Click to expand...
Click to collapse
But there is no persist file or folder in my root(see attached img)
"Dev/block/platform/msm_sdcc.1/by-name/persist"
So I don't think your script will work for me
matrixex said:
But there is no persist file or folder in my root(see attached img)
"Dev/block/platform/msm_sdcc.1/by-name/persist"
So your code will work for me?
Instead this persist folder is located at root
(See 2nd attached img)
Click to expand...
Click to collapse
No, it will not work. You need to get the partition list to find out where to write the persist.img file. You can likely find it by searching, or you cun run "ls -lR /dev/block" from a terminal.
In any case, this is now off-topic, as it has nothing to do with edify syntax. I will move the relevant posts to the Nokia X section.
EDIT: Moved from Galaxy Nexus section.
efrant said:
No, it will not work. You need to get the partition list to find out where to write the persist.img file. You can likely find it by searching, or you cun run "ls -lR /dev/block" from a terminal.
In any case, this is now off-topic, as it has nothing to do with edify syntax. I will move the relevant posts to the Nokia X section.
EDIT: Moved from Galaxy Nexus section.
Click to expand...
Click to collapse
pls help me Cause I am noob.
I tried ls -lR /dev/block but I can't identify partitions
partitions List
[email protected]:/ $su
1|[email protected]:/ # ls -lR /dev/block
/dev/block:
brw------- root root 7, 0 2016-02-04 13:09 loop0
brw------- root root 7, 1 2016-02-04 13:09 loop1
brw------- root root 7, 2 2016-02-04 13:09 loop2
brw------- root root 7, 3 2016-02-04 13:09 loop3
brw------- root root 7, 4 2016-02-04 13:09 loop4
brw------- root root 7, 5 2016-02-04 13:09 loop5
brw------- root root 7, 6 2016-02-04 13:09 loop6
brw------- root root 7, 7 2016-02-04 13:09 loop7
brw------- root root 179, 0 2016-02-04 13:09 mmcblk0
brw------- root root 179, 1 2016-02-04 13:09 mmcblk0p1
brw------- root root 179, 10 2016-02-04 13:09 mmcblk0p10
brw------- root root 179, 11 2016-02-04 13:09 mmcblk0p11
brw------- root root 179, 12 2016-02-04 13:09 mmcblk0p12
brw------- root root 179, 13 2016-02-04 13:09 mmcblk0p13
brw------- root root 179, 14 2016-02-04 13:09 mmcblk0p14
brw------- root root 179, 15 2016-02-04 13:09 mmcblk0p15
brw------- root root 179, 16 2016-02-04 13:09 mmcblk0p16
brw------- root root 179, 17 2016-02-04 13:09 mmcblk0p17
brw------- root root 179, 18 2016-02-04 13:09 mmcblk0p18
brw------- root root 179, 19 2016-02-04 13:09 mmcblk0p19
brw------- root root 179, 2 2016-02-04 13:09 mmcblk0p2
brw------- root root 179, 20 2016-02-04 13:09 mmcblk0p20
brw------- root root 179, 21 2016-02-04 13:09 mmcblk0p21
brw------- root root 179, 22 2016-02-04 13:09 mmcblk0p22
brw------- root root 179, 23 2016-02-04 13:09 mmcblk0p23
brw------- root root 179, 24 2016-02-04 13:09 mmcblk0p24
brw------- root root 179, 25 2016-02-04 13:09 mmcblk0p25
brw------- root root 179, 26 2016-02-04 13:09 mmcblk0p26
brw------- root root 179, 3 2016-02-04 13:09 mmcblk0p3
brw------- root root 179, 4 2016-02-04 13:09 mmcblk0p4
Again thanks
matrixex said:
So here is my partitions generated by ls -lR /dev/block
export PATH=/data/local/bin:$PATH:.
[email protected]:/ $ export PATH=/data/local/bin:$PATH:.
[email protected]:/ $su
[email protected]:/ # ls -LR /dev/block
ls: Unknown option '-L'. Aborting.
1|[email protected]:/ # ls -lr /dev/block
ls: Unknown option '-r'. Aborting.
1|[email protected]:/ # ls -lR /dev/block
/dev/block:
brw------- root root 7, 0 2016-02-04 13:09 loop0
brw------- root root 7, 1 2016-02-04 13:09 loop1
brw------- root root 7, 2 2016-02-04 13:09 loop2
brw------- root root 7, 3 2016-02-04 13:09 loop3
brw------- root root 7, 4 2016-02-04 13:09 loop4
brw------- root root 7, 5 2016-02-04 13:09 loop5
brw------- root root 7, 6 2016-02-04 13:09 loop6
brw------- root root 7, 7 2016-02-04 13:09 loop7
brw------- root root 179, 0 2016-02-04 13:09 mmcblk0
brw------- root root 179, 1 2016-02-04 13:09 mmcblk0p1
brw------- root root 179, 10 2016-02-04 13:09 mmcblk0p10
brw------- root root 179, 11 2016-02-04 13:09 mmcblk0p11
brw------- root root 179, 12 2016-02-04 13:09 mmcblk0p12
brw------- root root 179, 13 2016-02-04 13:09 mmcblk0p13
brw------- root root 179, 14 2016-02-04 13:09 mmcblk0p14
brw------- root root 179, 15 2016-02-04 13:09 mmcblk0p15
brw------- root root 179, 16 2016-02-04 13:09 mmcblk0p16
brw------- root root 179, 17 2016-02-04 13:09 mmcblk0p17
brw------- root root 179, 18 2016-02-04 13:09 mmcblk0p18
brw------- root root 179, 19 2016-02-04 13:09 mmcblk0p19
brw------- root root 179, 2 2016-02-04 13:09 mmcblk0p2
brw------- root root 179, 20 2016-02-04 13:09 mmcblk0p20
brw------- root root 179, 21 2016-02-04 13:09 mmcblk0p21
brw------- root root 179, 22 2016-02-04 13:09 mmcblk0p22
brw------- root root 179, 23 2016-02-04 13:09 mmcblk0p23
brw------- root root 179, 24 2016-02-04 13:09 mmcblk0p24
brw------- root root 179, 25 2016-02-04 13:09 mmcblk0p25
brw------- root root 179, 26 2016-02-04 13:09 mmcblk0p26
brw------- root root 179, 3 2016-02-04 13:09 mmcblk0p3
brw------- root root 179, 4 2016-02-04 13:09 mmcblk0p4
brw------- root root 179, 5 2016-02-04 13:09 mmcblk0p5
brw------- root root 179, 6 2016-02-04 13:09 mmcblk0p6
brw------- root root 179, 7 2016-02-04 13:50 mmcblk0p7
brw------- root root 179, 8 2016-02-04 14:11 mmcblk0p8
brw------- root root 179, 9 2016-02-04 13:09 mmcblk0p9
brw------- root root 179, 32 2016-02-04 13:09 mmcblk1
brw------- root root 179, 33 2016-02-04 13:09 mmcblk1p1
drwxr-xr-x root root 2016-02-04 13:09 platform
drwx------ root root 2016-02-04 13:09 vold
brw------- root root 253, 0 2016-02-04 13:09 zram0
/dev/block/platform:
drwxr-xr-x root root 2016-02-04 13:09 msm_sdcc.1
drwxr-xr-x root root 2016-02-04 13:09 msm_sdcc.3
/dev/block/platform/msm_sdcc.1:
drwxr-xr-x root root 2016-02-04 13:09 by-num
lrwxrwxrwx root root 2016-02-04 13:09 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root root 2016-02-04 13:09 mmcblk1p1 -> /dev/block/mmcblk1p1
/dev/block/platform/msm_sdcc.1/by-num:
lrwxrwxrwx root root 2016-02-04 13:09 p1 -> /dev/block/mmcblk1p1
/dev/block/platform/msm_sdcc.3:
drwxr-xr-x root root 2016-02-04 13:09 by-num
lrwxrwxrwx root root 2016-02-04 13:09 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx root root 2016-02-04 13:09 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-02-04 13:09 mmcblk0p10 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-02-04 13:09 mmcblk0p11 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-02-04 13:09 mmcblk0p12 -> /dev/blo
Can you explain which is persist partition
And it will be grateful if you explain some information about other
Partitions like system,boot etc
Again thanks
Click to expand...
Click to collapse
Hmmm. Someone else more knowledgeable on Nokia devices will have to chime in. In all the other Android devices I've used, the name of the partition is shown along with the number. In this case, it only shows the number.
You'll need to ask someone (maybe one of the devs that worked on a custom recovery) which number the persist partition is. Then just use this command from terminal (with a root prompt and persist.img saved in /sdcard or whatever folder you choose):
dd if=/sdcard of=/dev/block/mmcblk0pXX where XX is the number of the persist partition.
Or you could use an edify script in recovery:
package_extract_file("persist.img", "/tmp/persist.img");
run_program("/sbin/busybox", "dd", "if=/tmp/persist.img", "of=/dev/block/mmcblk0pXX");
delete("/tmp/persist.img");
But sorry, I can't help you with the number of the persist partition because I have no idea. The info might be in the forums somewhere (need to search or ask someone).
Hi
Finally I found it ,partitions just see 1st post
efrant said:
According to fastboot syntax, the "-i" option is for specifyina custom USB vendor ID, so 0x0421 is the USB vendor ID for your device. Are you using using Linux? I don't think it does anything on Windows.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Hi
Can you please delete all the post here I don't want it anymore
I have got answers so please delete this thread
matrixex said:
Hi
Can you please delete all the post here I don't want it anymore
I have got answers so please delete this thread
Click to expand...
Click to collapse
We typically don't delete threads - - if we delete this thread, it would make it difficult for someone having the same issue as you did.
You found the solution, and by posting here, you are helping others.
Sent from my HTC One M9 using Tapatalk
efrant said:
We typically don't delete threads - - if we delete this thread, it would make it difficult for someone having the same issue as you did.
You found the solution, and by posting here, you are helping others.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Sorry for the comment instead of this I will continue to post my resources as I dig
Code:
HWANE:/ $ cat /proc/partitions
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
254 0 2293760 zram0
179 0 61071360 mmcblk0
179 1 256 mmcblk0p1
179 2 256 mmcblk0p2
179 3 256 mmcblk0p3
179 4 768 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 6144 mmcblk0p7
179 8 65536 mmcblk0p8
179 9 4096 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 4096 mmcblk0p12
179 13 32768 mmcblk0p13
179 14 2048 mmcblk0p14
179 15 2048 mmcblk0p15
179 16 2048 mmcblk0p16
179 17 14336 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 65536 mmcblk0p19
179 20 2048 mmcblk0p20
179 21 24576 mmcblk0p21
179 22 61440 mmcblk0p22
179 23 4096 mmcblk0p23
179 24 2048 mmcblk0p24
179 25 16384 mmcblk0p25
179 26 12288 mmcblk0p26
179 27 24576 mmcblk0p27
179 28 32768 mmcblk0p28
179 29 16384 mmcblk0p29
179 30 24576 mmcblk0p30
179 31 16384 mmcblk0p31
179 32 32768 mmcblk0p32
179 33 16384 mmcblk0p33
179 34 28672 mmcblk0p34
179 35 4096 mmcblk0p35
179 36 98304 mmcblk0p36
179 37 1024 mmcblk0p37
179 38 1024 mmcblk0p38
179 39 2048 mmcblk0p39
179 40 16384 mmcblk0p40
179 41 4096 mmcblk0p41
179 42 131072 mmcblk0p42
179 43 131072 mmcblk0p43
179 44 2048 mmcblk0p44
179 45 2048 mmcblk0p45
179 46 4096 mmcblk0p46
179 47 32768 mmcblk0p47
259 0 2048 mmcblk0p48
259 1 16384 mmcblk0p49
259 2 14336 mmcblk0p50
259 3 5767168 mmcblk0p51
259 4 196608 mmcblk0p52
259 5 32768 mmcblk0p53
259 6 802816 mmcblk0p54
259 7 196608 mmcblk0p55
259 8 53043200 mmcblk0p56
179 144 4096 mmcblk0rpmb
179 96 4096 mmcblk0boot1
179 48 4096 mmcblk0boot0
179 192 62367744 mmcblk1
179 193 62366720 mmcblk1p1
253 0 4724684 dm-0
253 1 790064 dm-1
253 2 128924 dm-2
253 3 32172 dm-3
253 4 193424 dm-4
253 5 193424 dm-5
Code:
HWANE:/ $ ls -l /dev/block/platform/hi_mci.0/by-name/
[I][B]User friendly display[/B][/I]
/dev/block/mmcblk0p48 -> bootfail_info
/dev/block/mmcblk0p42 -> cache
/dev/block/mmcblk0p52 -> cust
/dev/block/mmcblk0p40 -> dfx
/dev/block/mmcblk0p35 -> dto
/dev/block/mmcblk0p34 -> dts
/dev/block/mmcblk0p27 -> erecovery_kernel
/dev/block/mmcblk0p28 -> erecovery_ramdisk
/dev/block/mmcblk0p38 -> erecovery_vbmeta
/dev/block/mmcblk0p29 -> erecovery_vendor
/dev/block/mmcblk0p5 -> fastboot
/dev/block/mmcblk0p4 -> frp
/dev/block/mmcblk0p26 -> fw_hifi
/dev/block/mmcblk0p3 -> fw_lpm3
/dev/block/mmcblk0p44 -> hisitest0
/dev/block/mmcblk0p45 -> hisitest1
/dev/block/mmcblk0p46 -> hisitest2
/dev/block/mmcblk0p30 -> kernel
/dev/block/mmcblk0p20 -> misc
/dev/block/mmcblk0p36 -> modem_fw
/dev/block/mmcblk0p18 -> modem_om
/dev/block/mmcblk0p17 -> modem_secure
/dev/block/mmcblk0p10 -> modemnvm_backup
/dev/block/mmcblk0p6 -> modemnvm_factory
/dev/block/mmcblk0p11 -> modemnvm_img
/dev/block/mmcblk0p12 -> modemnvm_system
/dev/block/mmcblk0p21 -> modemnvm_update
/dev/block/mmcblk0p7 -> nvme
/dev/block/mmcblk0p43 -> odm
/dev/block/mmcblk0p8 -> oeminfo
/dev/block/mmcblk0p47 -> patch
/dev/block/mmcblk0p16 -> persist
/dev/block/mmcblk0p55 -> product
/dev/block/mmcblk0p31 -> ramdisk
/dev/block/mmcblk0p32 -> recovery_ramdisk
/dev/block/mmcblk0p37 -> recovery_vbmeta
/dev/block/mmcblk0p33 -> recovery_vendor
/dev/block/mmcblk0p22 -> reserved2
/dev/block/mmcblk0p9 -> reserved3
/dev/block/mmcblk0p14 -> reserved4
/dev/block/mmcblk0p15 -> reserved5
/dev/block/mmcblk0p39 -> reserved8
/dev/block/mmcblk0p50 -> reserved9
/dev/block/mmcblk0p49 -> rrecord
/dev/block/mmcblk0p13 -> secure_storage
/dev/block/mmcblk0p25 -> sensorhub
/dev/block/mmcblk0p19 -> splash2
/dev/block/mmcblk0p51 -> system
/dev/block/mmcblk0p23 -> teeos
/dev/block/mmcblk0p24 -> trustfirmware
/dev/block/mmcblk0p56 -> userdata
/dev/block/mmcblk0p41 -> vbmeta
/dev/block/mmcblk0p54 -> vendor
/dev/block/mmcblk0p53 -> version
/dev/block/mmcblk0p1 -> vrl
/dev/block/mmcblk0p2 -> vrl_backup
Hello,
I want to flash a firmware for downgrade.
How i can make it without a dload method?
I can't downgrade my phone with this method, always a warning appear "error checking files" or anything like that...
Yes me to dload not downgrade
Gesendet von meinem ANE-LX1 mit Tapatalk
Manflack said:
Hello,
I want to flash a firmware for downgrade.
How i can make it without a dload method?
I can't downgrade my phone with this method, always a warning appear "error checking files" or anything like that...
Click to expand...
Click to collapse
SirusX said:
Yes me to dload not downgrade
Gesendet von meinem ANE-LX1 mit Tapatalk
Click to expand...
Click to collapse
This is a partition layout it can't help you with downgrade.
To downgrade without brick the phone you have to find a roll back firmware. In the picture is an example for p20 pro.
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: