Related
NEED HELP
Hello guys, I'm working on a generic tree for our beloved device Honor 7, but not getting enough success, so each and every of you are invited to help me create a new device tree for AOSP 5.1 ROM or CM 12.1, so that we can taste the Stock Android too.
The benefits of these ROMs are that the device will get more fast and stable as there will be minimum apps and bloatwares installed.
So, it is a humble request, that whosoever have any knowledge about creating a tree from scratch please help me.
I have created a skeleton of the tree but it is not a success too as there are many things we still have to consider.
@sminki and @kenshiwara, we will setup an organization on GitHub so everyone can contribute there only.
Hi,
It will be wonderfull to have CM on our honor7.
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
sminki said:
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
Click to expand...
Click to collapse
Thanks, this will help enough and I was not aware of your troubles
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Is there any whatsapp group of honor 7.I want to join it.
udayraj99 said:
Is there any whatsapp group of honor 7.I want to join it.
Click to expand...
Click to collapse
Stop spamming
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Mee too
omkarpranavxxx said:
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Click to expand...
Click to collapse
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
asiekierka said:
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Click to expand...
Click to collapse
Hello, did any of the CM compiled fully to be a flashable zip? if yes, then have you flashed it and took logcat?
Nishadan said:
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
Click to expand...
Click to collapse
Yup lesson learnt snapdragon or nothing frm now on
maybe you know
I post link - http://download-c.huawei.com/downlo...oadId=62086&version=204465&siteCode=worldwide
Honor 7 Open Source（PLK-L01_Android5_0_2_EMUI3_1_kernel_EN)
Any progress?
I hope I can do something,it is nice to see cm for honor 7.
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
cycovision said:
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
Click to expand...
Click to collapse
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
DigiGoon said:
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
Click to expand...
Click to collapse
good luck with your exams
Until then you can use this
New ROM for Honor 7 PLK-L01.
DigiGoon said:
Until then you can use this
New ROM for Honor 7 PLK-L01.
Click to expand...
Click to collapse
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
muhammad Shohayeb said:
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
Click to expand...
Click to collapse
I will be developing AOSP 6.0, if others can give it a try then maybe we can get it.
I am curious if anyone is currently working on getting CM (or any custom ROM) working for our devices. I'm not trying to bug anyone or get an ETA, but I was thinking about attempting to port CM with their tutorial.
If anyone is working on porting a ROM, or has any tips for me I'd love to talk. Thanks.
I've just started looking into porting CM over to the 5x. I've never built a port before and I'm a bit lost in the CM documentation for it. Feel free to PM me or post below with any tips or advice.
jmiller99 said:
I've just started looking into porting CM over to the 5x. I've never built a port before and I'm a bit lost in the CM documentation for it. Feel free to PM me or post below with any tips or advice.
Click to expand...
Click to collapse
I have only built unofficial builds before, but hopefully since we have source and other Huawei devices with CM, it should be fairly easy.
If you haven't built CM for a device that it's already been ported to, I'd recommend doing that before you attempt to port it.
Good luck. I'll post any progress I make.
Am too eagerly waiting for cm on 5x .fed up of bad performance from stock .heating up too much .I was really disappointed by the heating problem .
What else I had hopes On was the on cm12.1 or 13 .
I usually check for a thread if anyone build one cm ROM for our device but still the development haven't started !
gopinaidu77 said:
Am too eagerly waiting for cm on 5x .fed up of bad performance from stock .heating up too much .I was really disappointed by the heating problem .
What else I had hopes On was the on cm12.1 or 13 .
I usually check for a thread if anyone build one cm ROM for our device but still the development haven't started !
Click to expand...
Click to collapse
I'm *trying* to get CM 12.1 to work for our device, but I've never ported before so don't expect anything soon
gopinaidu77 said:
Am too eagerly waiting for cm on 5x .fed up of bad performance from stock .heating up too much .I was really disappointed by the heating problem .
What else I had hopes On was the on cm12.1 or 13 .
I usually check for a thread if anyone build one cm ROM for our device but still the development haven't started !
Click to expand...
Click to collapse
It's still early. The fact that Huawei makes bootloader unlock codes available and has provided the amount of source code for the kernel that they have has allowed development here to happen much more rapidly than many devices do (particularly devices that lie out side of "volume" interest -- like an S5 or S6). I'm pretty optimistic.
The flip side is that life is so busy for me at the moment that it makes patience pretty easy (as in, if a stable cm13 suddenly became available I still would take my sweet time in getting around to flashing it). If I had more time on my hands it would probably be different.
Yes lets see how long we need to wait !
Can someone (hopefully a dev like @deadman96385, @EarlyMon @cyrusalmighty) confirm/agree that the Honor 5X's (I have KIW-24, US ver.) vendor = HONOR and codename = HNKIW-Q. I'm a little perplexed by what the codename is since HNKIW-Q doesn't seem right. I got that name from the build.prop ro.product.device like CM recommends.
Can anyone confirm that I have the vendor and codename right? Thanks.
EDIT: After looking at similar Huawei devices (Ascend Mate 2) it looks like the codename should just be "kiw". The Mate 2's actual ro.product.device = hwMT2LO3, but it's CM codename is "mt2." Because of this, I think for the CM codename should be "kiw". Does that sound right?
Bandit Development said:
Can someone (hopefully a dev like @deadman96385, @EarlyMon @cyrusalmighty) confirm/agree that the Honor 5X's (I have KIW-24, US ver.) vendor = HONOR and codename = HNKIW-Q. I'm a little perplexed by what the codename is since HNKIW-Q doesn't seem right. I got that name from the build.prop ro.product.device like CM recommends.
Can anyone confirm that I have the vendor and codename right? Thanks.
EDIT: After looking at similar Huawei devices (Ascend Mate 2) it looks like the codename should just be "kiw". The Mate 2's actual ro.product.device = hwMT2LO3, but it's CM codename is "mt2." Because of this, I think for the CM codename should be "kiw". Does that sound right?
Click to expand...
Click to collapse
In theory but the kiw stands for kiwi this info is directly from Huawei and we all like Kiwi more lol. You also do have a L24 US variant
deadman96385 said:
In theory but the kiw stands for kiwi this info is directly from Huawei and we all like Kiwi more lol. You also do have a L24 US variant
Click to expand...
Click to collapse
Thanks. So any custom ROM development for this device will be like Huawei/kiwi? I'm just wondering, because I'd like to know how I should be naming my files specific to Honor 5X ROM development.
EDIT:
Also, @deadman96385 do you mind sharing the partition sizes you used for building TWRP?
Name it kiwi .it sounds really great ! Moreover i dont what others are thinking on naming this device ,but kiwi is maximum minds .Go for it !
Bandit Development said:
Thanks. So any custom ROM development for this device will be like Huawei/kiwi? I'm just wondering, because I'd like to know how I should be naming my files specific to Honor 5X ROM development.
EDIT:
Also, @deadman96385 do you mind sharing the partition sizes you used for building TWRP?
Click to expand...
Click to collapse
https://github.com/Huawei-Kiwi
deadman96385 said:
https://github.com/Huawei-Kiwi
Click to expand...
Click to collapse
I didn't realize you had already started working on a CM port. I guess I can't really help out then. :/
Don't get me wrong, I do really appreciate all the work you do for this device.
Bandit Development said:
I didn't realize you had already started working on a CM port. I guess I can't really help out then. :/
Don't get me wrong, I do really appreciate all the work you do for this device.
Click to expand...
Click to collapse
That cm tree was just to build cm recovery we are still in the very early stages of a full cm tree.
Can i possibly know why devices owning the 6795 like the rn3 won't upgrade to CM13 ? What do the devs require so much that they can't port CM13 to the mediatek version ? I'm afraid i'm not aware of this version so much, but does it properly need android M in order to run ?
Mediatek phones are generally far more difficult to develop for because they don't like to release kernel sources and they are built for generic phones so they don't work as well
Mediatek development most currently are porting roms that is the same base as the original. If it came out with 5.0.2 then the max version for a custom rom is probably 5.1.1 and its harder to port higher android OS without any sources.
Oh, i see.. So mostly is because of the phone devs that won't release certain codes and whatever you need in order to develop the rom, right ?
Yeah blame the chipset manufacturer.
I'm no developer, but what about this info?
https://github.com/rmtew/MediaTek-HelioX10-Kernel
Will we get android pie roms?
i am really interested in the pixel experience.
I was a mtk user and a porter ...can i port other pie rom like xiaomi note 4's with same kernel version ?
i am new so treat me like a noob:good:
mona356 said:
Will we get android pie roms?
i am really interested in the pixel experience.
I was a mtk user and a porter ...can i port other pie rom like xiaomi note 4's with same kernel version ?
i am new so treat me like a noob:good:
Click to expand...
Click to collapse
I'm very sad to see R5+ development is currently dead. I was hoping someone would build a Pixel Experience or any AOSP based ROM for our device but even the oreo roms are dead or finalized already. So i don't think people have anymore interest in R5+..
bdogan1912 said:
I'm very sad to see R5+ development is currently dead. I was hoping someone would build a Pixel Experience or any AOSP based ROM for our device but even the oreo roms are dead or finalized already. So i don't think people have anymore interest in R5+..
Click to expand...
Click to collapse
The real problem is lack of updated Oreo kernel sources (how much less Pie). This means, for example, that certain display panels (eg, ebbg) cannot be supported by custom ROMs (you might have to go back to Nougat kernels for that).
Why not write to Xiaomi to release up-to-date Oreo kernel sources for vince in the first instance? If enough people make a fuss, perhaps something will happen ...
DarthJabba9 said:
The real problem is lack of updated Oreo kernel sources (how much less Pie). This means, for example, that certain display panels (eg, ebbg) cannot be supported by custom ROMs (you might have to go back to Nougat kernels for that).
Why not write to Xiaomi to release up-to-date Oreo kernel sources for vince in the first instance? If enough people make a fuss, perhaps something will happen ...
Click to expand...
Click to collapse
Xiaomi however isn't listening their customers. A big example is ARB system which absolutely destroys devices. So i guess we are gonna stay dead until something shows up..
This is unofficial lineageos 16 for Motorola Clark. It is only compatible with nougat firmware - you must have the nougat bootloader and modem flashed on your device.
Tons of thanks to hashbang for all of his work
Kernel Source-
https://github.com/randomblame/android_kernel_motorola_msm8992
Device tree-
https://github.com/randomblame/android_device_motorola_clark
Current status of rom-
Daily Driver
Broken-
Camera post processing- rotation is not accounted for in hal with latest round of hacks credit to AgathosAnthropos for fixing image capture by disabling the calls to pp, hold device in landscape for photos
Tethering - it works but device will soft reboot when tethering stops
Dual sim variants are NOT supported! I do not have the hardware to test and fix at this time - bugreports appreciated
Working - everything else?
Try it yourself (Requires Nougat Firmware and as always wipe data+cache)
Latest Releases:
1/12/2020 https://www.androidfilehost.com/?fid=4349826312261700035
8/1/2019 https://www.androidfilehost.com/?fid=6006931924117928331
Don't forget to grab a compatible version of gapps for 9.0
https://opengapps.org
Once again this rom REQUIRES that the stock nougat firmware was properly flashed to work correctly... It will check before installation that you have the correct modem version installed.
*If your radio does not work you may have the wrong modem
*If you can not switch lockscreen to pin or pattern you may have the wrong modem.
*Modem flashes fail quietly sometimes please make sure you have properly flashed it before reporting issues.
Great! [emoji6]
Enviado desde mi Nexus 5X mediante Tapatalk
I'll be happy to test once there is a working rom
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Can't wait to see more from this
We wait impatiently.
Spent a couple more hours going through init narrowing it down failure happens just before zygote startsI currently have my pure propped up in charging position so I can work more on it it's had a hard life
Thank You so much
randomblame said:
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Click to expand...
Click to collapse
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Moto X Pure XT1575 said:
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Click to expand...
Click to collapse
Hi, I have the Lineague 14.2 installed. What I did to eliminate the bootloader check was to edit the uptader-script
Fixing error caused by missing taskstats kernel feature
Hi randomblame,
A quick review please, could you tell us the intended purpose of your project.
Meaning like I'm thinking it's for a "Moto X Pure 2015 (clark)" device isn't it?
Would that be for everyone on this XT1575 device which has upgraded to a stock Nougat kernel and modem?
Or could/would others benefit from it as well with your research here - other moto's?
Any and all answers - thoughts are welcome in understanding the project...
Thanks for the lady power on XDA,
RIF
This device can have a new future. Think about it !
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
randomblame said:
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
Click to expand...
Click to collapse
I'm trying to follow along with your posts best as is possible for me - but, so sorry I and as well many others are lame to understand the under-the-hood workings of Android.
Are you saying in such a way that the Moto Pure XT1575, will maybe and with your research efforts move forward to a true PIE OS possibly?
Maybe I'm reading to much into your words.
But, as I follow your posts, you'll advance us Pure device owners beyond the Nougat kernel - or at least try too?
Or yet with your efforts will this yield something like HashBang did for the XT1575 device when a Nougat OS wasn't even a thought of possibility from Motorola for us.
Back then, HashBang had worked the Nougat OS on the Marshmallow kernel and modem - I'm very green to all of this - but that's what I understood.
Still that's good none the less if that will come here from you with PIE on Nougat internals...
Beings Motorola support is dead for our device for anything future of an OS update - not to mention security patches.
If you would spell it out better as any interested XT1575 owners now could grasp the concept here in your efforts - create a buzz for a greater community following. More MXP owners to jump on board as gained support from well wishers.
Is it to early yet for that? Is there a fear that someone could steal it out from under you? Unexpected negativity, or is it just the way you wish to present this to us for the present.
I'm still going to watch and support this project with high hopes no matter what may come in the end...
Could you benefit knowledge from a LineageOS 16 for Moto Z. download?
https://www.cyanogenmods.org/forums/topic/download-moto-z-lineage-os-16-android-9/
For people like me,
Device Tree = https://source.android.com/devices/architecture/dto
and on XDA
https://forum.xda-developers.com/android/software/guide-how-to-make-device-tree-phone-t3698419
As for any active developers still left for the XT1575 a big thank you to you all, seems to me like a daunting task to crawl inside of android moreless understand things once your there...
Kernels are only loosly linked to Android versions, Google maintains the Android-common kernel repos which are usually quite far behind mainline Linux, and caf who maintains Qualcomm specific kernels are further behind in general. Literallyany feature required by Android can be backported to an old kernel I'm sure 2.6.27 could run pie but it would need so many patches it would be an unrecognizable mess. It will become progressively more of a nuisance as time goes on to keep patching up 3.10 Pie "requires" 4.4 for new devices but only needs kernel features from 3.18 which I've backported to 3.10. with each new version of Android more assumptions are made about how modern the devices kernel is and what features it has so moving to a newer kernel would be nice and like I said 3.18 seems doable but it will still be quite a bit of work.
Thank you @randomblame I was able to grasp most of that...
Maybe it's too early but, how does Googles Android security patches figure into this - if they are possible to bring us forth from Oct 2017?
Remembering I'm a laymen to the nuts and bolts of android.
I understand your post #16 - Super !
Security patch version is irrelevant when you are building from the latest source
Obnoxiously after a few builds the dedicated 250gb SSD is full and I have to make clean which takes ages, I nooped every thing but the basics didn't include telephony or wifi, ril, audio, Bluetooth GPS nfc etc and left it to build overnight will test after work trying to narrow down the problem
Surface flinger is the culprit
I have the device laying around and getting no use. Will sure donate some $$$. Seeing a los16 with all working hardware would be great.
Only got a couple hours to work on it this weekend, there is an issue where /system/vendor is not symlinked to /vendor early enough and calls for things in /vendor fail thus the issue, since we don't have a physical /vendor partition it can not be mounted immediately via the kernel. Tis annoying. I can change the calls to /system/vendor or maybe make it symlinked earlier when I get a chance