Any Devs Working on H7? I'm seriously stuck... - Honor 7 Q&A, Help & Troubleshooting

Is anyone trying to work on the Honor 7? I've got the the point now where I can't continue.
Things I know:
Kernel source compiles with no issues
Boot image has secure boot for first 4095 bytes
Kernel and ramdisk can be extracted easily
Bootloader is crap! Doesn't allow fastboot boot
Things I can't do:
Repack a stock boot image! Tried countless ideas. Various unmkbootimg give differing offset values for kernel and ramdisk, tried all those, tried zeroing off the secureboot section. I either get hang on Honor or bootloader error
Superr's kitchen doesn't even recognise it as a valid boot.img, I thought that was my lifeline..
Can't create flashable zip, various update-binary's have been tried - including Huawei's own pulled from the 140 OTA, can't get any edify zip to run (I know shell scripts will work, that's how SU installs.)
It's either something I'm doing wrong (very likely), or this handset is so non-standard, we as a community are screwed! (less likely but possible)
Just to note - I'm not a dev, I'm a Linux admin by day...
Any sensible ideas welcomed :silly:

---

Hey there,
for differing Offset u tried this:
http://forum.xda-developers.com/showpost.php?p=61956115&postcount=54
For a flashable zip-file u should have a look at anykernel2 ... maybe u can find a solution here!
The secure boot shouldn't be a problem as ur bootloader is unlocked
Sent from my PLK-L01 using XDA Premium HD app

---

thanks @c0llal0 , some interesting things to look at there that I haven't tried :good:

---

Ur welcome! We all benefit from ur efforts.
In case i find some free time in the next days, i will try to help more...
Sent from my PLK-L01 using XDA Premium HD app

---

AnyKernel2 seems to be working :victory: - don't understand, as it's using still using umkbootimg and mkbootimg (arm) - need to put some debug in there to get the values it's using!
...but i've had to use use some force. I've had to disable the device check, which I'm not happy about (you know, some people may flash another device by "mistake")

---

Can u tell me where u disabled it? Maybe u could link to some code? Will have a look at those lines.
Sent from my PLK-L01 using XDA Premium HD app

---

in anykernel.sh
Code:
do.devicecheck=1
using
Code:
device.name1=HWPLK
device.name2=hi3635
as that's what is in build.prop
this is used in META-INF/com/google/android/update-binary
Code:
if [ "$(file_getprop /tmp/anykernel/anykernel.sh do.devicecheck)" == 1 ]; then
ui_print "Checking device...";
for i in 1 2 3 4 5; do
testname="$(file_getprop /tmp/anykernel/anykernel.sh device.name$i)";
if [ "$(getprop ro.product.device)" == "$testname" -o "$(getprop ro.build.product)" == "$testname" ]; then
ui_print "$testname";
match=1;
fi;
done;
ui_print " ";
if [ "$match" != 1 ]; then
abort "Unsupported device. Aborting...";
fi;
fi;
Always get unsupported device

---

I am on B170! Rooted.
My build.prop only shows HWPLK
No second device id here!
Sent from my PLK-L01 using XDA Premium HD app

---

added some extra ui_print - it's getting the value "HWGRA" ! that's not in build.prop :silly:
I had a look via TWRP and things get a little revealing
Code:
adb shell
~ # getprop
[ro.build.product]: [HWGRA]
[ro.product.device]: [HWGRA]
so, it looks as though this recovery is for the Huawei P8 / GRACE !
So now we have another job to do!

---

here's what Anykernel2 returns from unpackbootimg (also posting here for my own reference )
values here are yet again different from other unpackbootimg builds!
Code:
BOARD_KERNEL_CMDLINE mem=3072M mmcparts=mmcblk0:p1(vrl),p2(vrl_backup),p6(modemnvm_factory),p9(splash),p10(modemnvm_backup),p11(modemnvm_img),p12(modemnvm_system),p14(3rdmodemnvm),p15(3rdmodemnvmback),p17(modem_om),p20(modemnvm_update),p30(modem),p31(modem_dsp),p32(dfx),p33(3rdmodem) androidboot.selinux=enforcing
BOARD_KERNEL_BASE 00678000
BOARD_NAME
BOARD_PAGE_SIZE 2048
BOARD_KERNEL_OFFSET 00008000
BOARD_RAMDISK_OFFSET 07588000
BOARD_TAGS_OFFSET ffb88000
something else to try...
EDIT:
YESSSS! :victory: :victory: :victory:
that's the one!
Code:
mkbootimg --kernel zImage --ramdisk boot.img-ramdisk.gz --cmdline \
'mem=3072M mcparts=mmcblk0:p1(vrl),p2(vrl_backup),p6(modemnvm_factory),p9(splash),p10(modemnvm_backup),p11(modemnvm_img),p12(modemnvm_system),p14(3rdmodemnvm),p15(3rdmodemnvmback),p17(modem_om),p20(modemnvm_update),p30(modem),p31(modem_dsp),p32(dfx),p33(3rdmodem) androidboot.selinux=enforcing' \
--base 0x678000 --pagesize 2048 --ramdisk_offset 0x7588000 \
-o new_boot.img

---

Yep! There u go
Now we have a good base to start, at least, kernel development!
Great work!!!
Sent from my PLK-L01 using XDA Premium HD app

---

c0llal0 said:
Yep! There u go
Now we have a good base to start, at least, kernel development!
Great work!!!
Click to expand...
Click to collapse
thanks can you do one thing for me, as you're on 170
can you tell me what the kernel version is?
cheers :highfive:

---

Here we go
Sent from my PLK-L01 using XDA Premium HD app

---

c0llal0 said:
Here we go
Click to expand...
Click to collapse
3.10.61, cool thanks!

---

As u have a bootin' kernel, what comes out of those logfiles? U looked after drivers for sensors and stuff?
Is the phone behaviour like it should be?
Sent from my PLK-L01 using XDA Premium HD app

---

c0llal0 said:
As u have a bootin' kernel, what comes out of those logfiles? U looked after drivers for sensors and stuff?
Is the phone behaviour like it should be?
Sent from my PLK-L01 using XDA Premium HD app
Click to expand...
Click to collapse
phone is working fine, as it's the same kernel version, the module for sensors etc. are all loading and working normally

---

Hi guys,
I've been following these posts for a few weeks now als also the kernel development. Massive shout out to Sminki and the ON-OR kernel!!
But I'm really new to the development of kernels and ROMs and new to xda so I have some questions if you don't mind.
I guess you guys are working on the kernel, how long should this take since it's kind of safe to use? And can I help testing (pls keep in mind I'm not an expert, just used to flash roms and kernels on nexus 4, that's all my knowlege.)?
When you get the kernel up and running, does it take much to make roms? Like making them from scratch or just a few changes to existing roms?
And again, can I help testing those ROMs?
My buildnr is PLK-L01c432B121, as far as I understand, L01 means I have the European version and B121 stands for the firmware version (an old one i guess). What does C432 mean?
You're working on an L01 kernel, is this compatible for other versions? In other words, when there are other kernels available, should I keep in mind that I can use only L01 based kernels?
Thank you to all the people that are spending their free time and all your hard work!!!!

---

Sorry this is a long reply, i got carried away, but you did ask a lot!
Anderjax said:
Hi guys,
Massive shout out to Sminki and the ON-OR kernel!!
Click to expand...
Click to collapse
thanks
But I'm really new to the development of kernels and ROMs
Click to expand...
Click to collapse
Me too, although I have been using linux for about 13 years so I do have some understanding of the underlying system, compiling, kernel modules, etc.. However some bits of this post may be incorrect!
I guess you guys are working on the kernel, how long should this take since it's kind of safe to use?
Click to expand...
Click to collapse
It is safe, i added the experimental tag as mine went into un-wakeable sleep with bluactiv cpu governor, but it's current uptime is 85hrs using ondemand instead. i built it because i wanted to see if it would actually compile, i posted it because it worked (and no one else had, haha!)
When you get the kernel up and running, does it take much to make roms? Like making them from scratch or just a few changes to existing roms?
Click to expand...
Click to collapse
this is where it gets difficult. right now there is nothing, no AOSP, no CM, etc.. to port to
So to start from scratch you need a device tree, which is essentially a collection of files that give the rom the bits of info it needs to build for your device, roms are a little easier to build if you have a "sibling" or "ancestor" (similar/older) device with a custom ROM, one that is similar enough to use some of the device tree that custom ROM was built from.
As the CPU is Huawei's own HiSilicon Kirin, there really is nothing similar with the exception of codeworkx CM for the Honor 6, the P8 is a "sibling" (but no custom roms) and the mediapad x2, which is Kirin, but not a phone, but someone may be able to do something with the custom roms available (?)
I'm currently playing around with this when i have spare time
What does C432 mean?
Click to expand...
Click to collapse
no idea!
You're working on an L01 kernel, is this compatible for other versions? In other words, when there are other kernels available, should I keep in mind that I can use only L01 based kernels?
Click to expand...
Click to collapse
the Chinese PLK-AL10 is the PLK-L01 with more RAM - with the MarshMallow beta "blackbox" partitions flashed i was able to run the AL10 kernel and system (android 5.1.1) on the L01
The PLK-(UL/TL/CL) are all essentially the same (rom) in a smaller system partition (as I tried that too!) I've not looked into the Indian variant yet..
"blackbox" are things like "radio" that you can flash directly from fastboot on a nexus, but not on this device, this is where the problems would lie. So yes, kernel per device, unless the dev has considered the above, but there is only one kernel right now :silly:

---

sminki said:
Sorry this is a long reply, i got carried away, but you did ask a lot!
Nice one,
Thank you, this explaines a lot really. Have you ever made a tree like that?
Is there someway to help you by installing the kernel en sending you feedback errors and stuff?
Click to expand...
Click to collapse

---

Anderjax said:
Nice one,
Thank you, this explaines a lot really. Have you ever made a tree like that?
Is there someway to help you by installing the kernel en sending you feedback errors and stuff?
Click to expand...
Click to collapse
Never made a tree before, but I have something which might work, will find out soon
As for the kernel, you can try and install it but it may not work because:
a) your're on B121
b) you may have the chinese twrp
c) other
I'll post the B121 boot.img later (at work now) on the main kernel post should you need to go back to it.
However - I don't know how much I'll be able to debug as i'm not a dev, or that good at C, also the huawei source seems to be really non-standard! :silly: