Develop Bugs

Developer infos

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.

[Q&A]Partitions list of Nokia x

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

Partition Layout for P20

Hello i tought it share my findings here
Huawei P20 Partitions
Code:
HWEML:/dev/block/platform/ff3c0000.ufs/by-name $ ls -la
total 0
drwxr-xr-x 2 root root 1300 2018-03-28 14:54 .
drwxr-xr-x 4 root root 1420 2018-03-28 14:54 ..
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 bootfail_info -> /dev/block/sdd18
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 cache -> /dev/block/sdd58
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 certification -> /dev/block/sdd5
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 cust_a -> /dev/block/sdd56
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 ddr_para -> /dev/block/sdd15
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 dfx -> /dev/block/sdd20
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 dto_a -> /dev/block/sdd43
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 dts_a -> /dev/block/sdd42
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 erecovery_kernel_a -> /dev/block/sdd35
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 erecovery_ramdisk_a -> /dev/block/sdd36
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 erecovery_vbmeta_a -> /dev/block/sdd48
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 erecovery_vendor_a -> /dev/block/sdd37
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 fastboot_a -> /dev/block/sdd28
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 frp -> /dev/block/sdc1
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 fw_hifi_a -> /dev/block/sdd32
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 fw_lpm3_a -> /dev/block/sdd22
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 hdcp_a -> /dev/block/sdd24
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 hhee_a -> /dev/block/sdd26
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 hisee_encos -> /dev/block/sdd13
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 hisee_fs_a -> /dev/block/sdd27
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 hisee_img_a -> /dev/block/sdd25
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 isp_boot_a -> /dev/block/sdd30
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 isp_firmware_a -> /dev/block/sdd31
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 kernel_a -> /dev/block/sdd38
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 misc -> /dev/block/sdd19
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 modem_fw_a -> /dev/block/sdd45
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 modem_om -> /dev/block/sdd8
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 modem_secure -> /dev/block/sdd3
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 modemnvm_backup -> /dev/block/sdd10
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 modemnvm_cust_a -> /dev/block/sdd51
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 modemnvm_factory -> /dev/block/sdd9
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 modemnvm_img -> /dev/block/sdd11
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 modemnvm_system -> /dev/block/sdd12
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 modemnvm_update_a -> /dev/block/sdd50
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 nvme -> /dev/block/sdd4
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 odm_a -> /dev/block/sdd57
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 oeminfo -> /dev/block/sdd6
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 patch_a -> /dev/block/sdd52
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 persist -> /dev/block/sdc2
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 product_a -> /dev/block/sdd55
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 ramdisk_a -> /dev/block/sdd39
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 recovery_ramdisk_a -> /dev/block/sdd40
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 recovery_vbmeta_a -> /dev/block/sdd47
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 recovery_vendor_a -> /dev/block/sdd41
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 reserved1 -> /dev/block/sdc3
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 reserved2 -> /dev/block/sdd16
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 reserved3_a -> /dev/block/sdd23
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 reserved4_a -> /dev/block/sdd46
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 rrecord -> /dev/block/sdd21
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 secure_storage -> /dev/block/sdd7
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 sensorhub_a -> /dev/block/sdd34
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 splash2 -> /dev/block/sdd17
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 system_a -> /dev/block/sdd59
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 teeos_a -> /dev/block/sdd33
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 trustfirmware_a -> /dev/block/sdd44
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 userdata -> /dev/block/sdd60
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 vbmeta_a -> /dev/block/sdd49
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 vector_a -> /dev/block/sdd29
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 vendor_a -> /dev/block/sdd54
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 veritykey -> /dev/block/sdd14
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 version_a -> /dev/block/sdd53
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 vrl -> /dev/block/sdd1
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 vrl_backup -> /dev/block/sdd2
Code:
HWEML:/system $ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 1.4G 12M 1.4G 1% /
tmpfs 1.7G 684K 1.7G 1% /dev
/dev/block/dm-0 4.3G 3.2G 1.1G 75% /system
/dev/block/dm-1 747M 688M 44M 94% /vendor
/dev/block/dm-2 120M 110M 7.2M 94% /odm
/dev/block/dm-3 27M 516K 26M 2% /version
/dev/block/dm-4 182M 114M 64M 65% /product
/dev/block/dm-5 182M 44M 134M 25% /cust
tmpfs 1.7G 0 1.7G 0% /mnt
none 1.7G 0 1.7G 0% /sys/fs/cgroup
/dev/block/sdd60 111G 3.6G 106G 4% /data
/dev/block/sdd58 122M 60K 119M 1% /cache
/data/media 111G 4.9G 106G 5% /storage/emulated
Hope it helps some one

Can you check for this? https://www.xda-developers.com/how-to-check-android-device-supports-seamless-updates/

Here we go
Cant get the unlock code from the huawei site then i would try phh AOSP

Yes the P20 Lite ANE-LX1 is also Treble enabled but is A only

crucky said:
Here we go
Cant get the unlock code from the huawei site then i would try phh AOSP
Click to expand...
Click to collapse
Hey please tell me what you did?
I just remote helped a guy to bootloader unlock his demo unit
Sent from my DUK-L09 using Tapatalk

IMEI SN Missmatch always the same on the P20 Lite Demo Unit it worked
EDIT:I Saw you posted a tutorial for unlock will try it now with my demo unit

LastStandingDroid said:
Hey please tell me what you did?
I just remote helped a guy to bootloader unlock his demo unit
Click to expand...
Click to collapse
How did you unlock the Demo Unit? Mine has OEM lock and I can't unlock it in the developer options.

Nogorka said:
How did you unlock the Demo Unit? Mine has OEM lock and I can't unlock it in the developer options.
Click to expand...
Click to collapse
Simply by enable developer options and tick oem unlock? You'd have to ask the guy who owns it
Sent from my DUK-L09 using Tapatalk

LastStandingDroid said:
Simply by enable developer options and tick oem unlock? You'd have to ask the guy who owns it
Click to expand...
Click to collapse
The owner is a Provider because it's a Demo unit from "my" shop. And i can't enable the OEM unlock option, it's grayed out. I thought you could help me with unlocking it, sorry!

Nogorka said:
The owner is a Provider because it's a Demo unit from "my" shop. And i can't enable the OEM unlock option, it's grayed out. I thought you could help me with unlocking it, sorry!
Click to expand...
Click to collapse
Greyed out? Sounds like they disabled it.
Is it the demo version which has the demo app? Because on the p20 pro it was possible to unlock. And it was demo store unit
Sent from my DUK-L09 using Tapatalk

LastStandingDroid said:
Greyed out? Sounds like they disabled it.
Is it the demo version which has the demo app? Because on the p20 pro it was possible to unlock. And it was demo store unit
Click to expand...
Click to collapse
Yeah, there ist the retail Demo on it, and a "explore P20" app too. Okay.. than ill have to wait till somebody know how to enable the OEM unlock. Thanks a lot!

Nogorka said:
Yeah, there ist the retail Demo on it, and a "explore P20" app too. Okay.. than ill have to wait till somebody know how to enable the OEM unlock. Thanks a lot!
Click to expand...
Click to collapse
Hello i own a Demo phone to EML-L29 non-pro you can enable oem unlock by factory reseting and connecting wifi also turn on developer options then and connect and disconnect the type c usb.After a while i could enable it and unlocked the bootloader of the demo unit running phh treble aosp rom

crucky said:
Hello i own a Demo phone to EML-L29 non-pro you can enable oem unlock by factory reseting and connecting wifi also turn on developer options then and connect and disconnect the type c usb.After a while i could enable it and unlocked the bootloader of the demo unit running phh treble aosp rom
Click to expand...
Click to collapse
Could you try
https://mega.nz/#!xGYSiSCS!cgkEfytbI_D8BUl2HjQB1qtGuTPc7Rw2630HIHXxGKE
Eml patched
Sent from my DUK-L09 using Tapatalk

LastStandingDroid said:
Could you try
https://mega.nz/#!xGYSiSCS!cgkEfytbI_D8BUl2HjQB1qtGuTPc7Rw2630HIHXxGKE
Eml patched
Sent from my DUK-L09 using Tapatalk
Click to expand...
Click to collapse
Yes will try it tomorrow because today i need my phone and iam currently running phh AOSP not Demo Stock

crucky said:
Yes will try it tomorrow because today i need my phone and iam currently running phh AOSP not Demo Stock
Click to expand...
Click to collapse
That shouldn't matter should work on both stock and phh
Sent from my DUK-L09 using Tapatalk

Can confirm works great Deinstalled the Demo APK

crucky said:
Can confirm works great Deinstalled the Demo APK
Click to expand...
Click to collapse
Do you mean that you're running AOSP with magisk patched boot image on Huawei P20 (EML)?

No switched back to stock. but will try it now again with phh AOSP somone here with a C432 P20 EML-L29 ? maybe you can give me a dump of CUST ? then i would try to rebrand from my demo C652. @LastStandingDroid maybe we can find a solution for rebrand ? because i modded CUST partition the only problem i have now i cant set fingerprint or faceunlock because of that its very annoying. @ectroplasma22 do you have it ? Maybe you could grab the full package firmware ? Still isnt avaible @ FF only funkyhuawei

Great news guys.
There a working twrp for you guys
Bad news I can't share since user who created it is banned.
Also decryption won't work. So it's basically useless for mate P20 pro users.
Good thing lite/regular should be good to go. If having a external Sd!
Edit it did not
Picture tells u what to Google for. Please do not ask for link!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my DUK-L09 using Tapatalk

Ok the patched ramdisk isnt working with RROS

xiaomi A3 laurel_sprout partitions table

xiaomi A3 laurel_sprout partitions table
Code:
18:29 ALIGN_TO_128K_1 -> /dev/block/sdd1
18:29 ALIGN_TO_128K_2 -> /dev/block/sdf1
18:29 abl_a -> /dev/block/sde8
18:29 abl_b -> /dev/block/sde29
18:29 apdp -> /dev/block/sde45
18:29 bk03 -> /dev/block/sde54
18:29 bluetooth_a -> /dev/block/sde5
18:29 bluetooth_b -> /dev/block/sde26
18:29 boot_a -> /dev/block/sde11
18:29 boot_b -> /dev/block/sde32
18:29 catecontentfv -> /dev/block/sde61
18:29 catefv -> /dev/block/sde60
18:29 cateloader -> /dev/block/sde51
18:29 cdt -> /dev/block/sdd2
18:29 cmnlib64_a -> /dev/block/sde13
18:29 cmnlib64_b -> /dev/block/sde34
18:29 cmnlib_a -> /dev/block/sde12
18:29 cmnlib_b -> /dev/block/sde33
18:29 ddr -> /dev/block/sdd3
18:29 devcfg_a -> /dev/block/sde14
18:29 devcfg_b -> /dev/block/sde35
18:29 devinfo -> /dev/block/sde43
18:29 dip -> /dev/block/sde44
18:29 dsp_a -> /dev/block/sde9
18:29 dsp_b -> /dev/block/sde30
18:29 dtbo_a -> /dev/block/sde18
18:29 dtbo_b -> /dev/block/sde39
18:29 frp -> /dev/block/sda5
18:29 fsc -> /dev/block/sdf5
18:29 fsg -> /dev/block/sdf4
18:29 gsort -> /dev/block/sde62
18:29 hyp_a -> /dev/block/sde3
18:29 hyp_b -> /dev/block/sde24
18:29 imagefv_a -> /dev/block/sde19
18:29 imagefv_b -> /dev/block/sde40
18:29 keymaster_a -> /dev/block/sde10
18:29 keymaster_b -> /dev/block/sde31
18:29 keystore -> /dev/block/sda4
18:29 limits -> /dev/block/sde48
18:29 logdump -> /dev/block/sde53
18:29 logfs -> /dev/block/sde50
18:29 mdtp_a -> /dev/block/sde7
18:29 mdtp_b -> /dev/block/sde28
18:29 mdtpsecapp_a -> /dev/block/sde6
18:29 mdtpsecapp_b -> /dev/block/sde27
18:29 metadata -> /dev/block/sda14
18:29 minidump -> /dev/block/sda11
18:29 misc -> /dev/block/sda3
18:29 modem_a -> /dev/block/sde4
18:29 modem_b -> /dev/block/sde25
18:29 modemst1 -> /dev/block/sdf2
18:29 modemst2 -> /dev/block/sdf3
18:29 multiimgoem -> /dev/block/sde56
18:29 multiimgqti -> /dev/block/sde57
18:29 odm_a -> /dev/block/sda8
18:29 odm_b -> /dev/block/sda9
18:29 oem -> /dev/block/sda10
18:29 persist -> /dev/block/sda2
18:29 product_a -> /dev/block/sda6
18:29 product_b -> /dev/block/sda7
18:29 qupfw_a -> /dev/block/sde15
18:29 qupfw_b -> /dev/block/sde36
18:29 rawdump -> /dev/block/sde52
18:29 rpm_a -> /dev/block/sde1
18:29 rpm_b -> /dev/block/sde22
18:29 secdata -> /dev/block/sde59
18:29 splash -> /dev/block/sde47
18:29 spunvm -> /dev/block/sde46
18:29 ssd -> /dev/block/sda1
18:29 storsec -> /dev/block/sde55
18:29 storsec_a -> /dev/block/sde21
18:29 storsec_b -> /dev/block/sde42
18:29 system_a -> /dev/block/sda12
18:29 system_b -> /dev/block/sda13
18:29 toolsfv -> /dev/block/sde49
18:29 tz_a -> /dev/block/sde2
18:29 tz_b -> /dev/block/sde23
18:29 uefisecapp_a -> /dev/block/sde20
18:29 uefisecapp_b -> /dev/block/sde41
18:29 uefivarstore -> /dev/block/sde58
18:29 userdata -> /dev/block/sda15
18:29 vbmeta_a -> /dev/block/sde17
18:29 vbmeta_b -> /dev/block/sde38
18:29 vendor_a -> /dev/block/sde16
18:29 vendor_b -> /dev/block/sde37
18:29 xbl_a -> /dev/block/sdb1
18:29 xbl_b -> /dev/block/sdc1
18:29 xbl_config_a -> /dev/block/sdb2
18:29 xbl_config_b -> /dev/block/sdc2

Rare directory listing in my Pixel 3 XL

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