Developer infos

codeworkx · Jan 17, 2015

Let's collect and share some developer relevant infos about the h60.

KERNEL TOOLBOX:
http://xdaforums.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 mem=2044m@0x200000 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

root-expert · Jan 17, 2015

@codeworkx Very useful information for the developers...! Have you tried to build a CM. Or at least a cwm recovery...?

codeworkx · Jan 17, 2015

root-expert said:
@codeworkx Very useful information for the developers...! Have you tried to build a CM. Or at least a cwm recovery...?

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

codeworkx · Jan 18, 2015

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.

nrpetonr · Jan 18, 2015

Is it even worse than mtk?

Sent from my H60-L02 using Tapatalk

Dervisk · Jan 18, 2015

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..

aaaa00 · Jan 18, 2015

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.

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!

panamera2011 · Jan 18, 2015

You're right, almost all developers continue to buy the same devices because with cpu Qualcom is easier to build rom cm

codeworkx · Jan 19, 2015

nrpetonr said:
Is it even worse than mtk?

Sent from my H60-L02 using Tapatalk

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.

codeworkx · Jan 19, 2015

panamera2011 said:
You're right, almost all developers continue to buy the same devices because with cpu Qualcom is easier to build rom cm

Maybe not easier, but there's documentation and sourcecode available.
That's a huge difference.

Dervisk · Jan 19, 2015

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.

What do you mean by pure accident ? As in really messy coding ?

codeworkx · Jan 19, 2015

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.

Dervisk · Jan 19, 2015

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.

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 ..!

codeworkx · Jan 19, 2015

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 ..!

I've already written a mail to huawei. let's see how it goes.

desalesouche · Jan 19, 2015

some more information.

@codeworkx
some more information to complete OP that user @spanorg could collect following that thread http://xdaforums.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

panamera2011 · Jan 20, 2015

desalesouche said:
@codeworkx
some more information to complete OP that user @spanorg could collect following that thread http://xdaforums.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 what model of Honor 6 uses?

I use H60-L02

desalesouche · Jan 20, 2015

panamera2011 said:
@desalesouche what model of Honor 6 uses?

I use H60-L02

from what i know @spanorg use L02

codeworkx · Jan 21, 2015

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.

Julsen1985 · Jan 22, 2015

Is it possible to built a cm version and use the available compiled kernel?

codeworkx · Jan 22, 2015

Julsen1985 said:
Is it possible to built a cm version and use the available compiled kernel?

yes, but radio and audio might be broken.
can't say for sure. i've still no honor 6.

Developer infos

Senior Recognized Developer

Inactive Recognized Developer

Senior Recognized Developer

Senior Recognized Developer

Senior Member

Senior Member

Senior Member

Senior Member

Senior Recognized Developer

Senior Recognized Developer

Senior Member

Senior Recognized Developer

Senior Member

Senior Recognized Developer

Senior Member

Attachments

Senior Member

Senior Member

Senior Recognized Developer

Senior Member

Senior Recognized Developer

Similar threads

Top Liked Posts