As you all V20 owners know, there's only one kernel available for Rooted Stock Oreo ROM and it is MK2000. However it's a good kernel and its developer has put a great effort on it but unfortunately it doesn't function properly on H990DS variant. Some problems like intensive lags and battery draining are two major examples.
If you remember we had a good DOTS kernel in nougat. If someone could fork it for Oreo it would be great as well.
Anyways, here's what we need:
[*]Stock kernel based on H990ds Oreo sources (20a or 20b)
[*]Dirty Santa fixes applied (You can read about this in H990* root thread under TECHNICAL DISCUSSION section)
[*]RCTD, Triton and whatever related removed
[*]"ForceEncryption" and "dm(avb)verity" removed
[*]KCAL, EXFAT and USB Quick Charge support
[*]More CPU governors (We will talk about this in the group)
[*]Overclocked
[*]Make the project Open Source
If you think you can do something, PM me! I'll send you additional information required.
Also I'll give you a link for a Telegram group where you can share what you have and it can be tested out.
Anyone interested in testing potential builds, also contact me for the Telegram link.
The current list of supporters:
----------------------------------------------------
$15 -- @Daved+
$15 -- @mikekote666
$5 -- @Chucknorris1975
$10 -- @aygross1929
$5 -- Uditha
$5 -- @rivaldo21
$5 -- @giriraj121
$5 -- Taufik Kusuma
$15 -- @tapir1505
$10 -- @albaniax
$10 -- @henrylar
$10 -- @DrugsBunny
$10 -- @lefffen1
$5 -- @bronze_eye
$5 -- @Blissv
$20 -- @Qron
$20 -- @NoName!
----------------------------------------------------
Total: $170
Due to some problems I can't manage this thread soon enough, so please contact @Daved+ for more information.
He will also collect the bounties and release the kernel when ready. Stay tuned!!!
Last update: 2020-3-26 /// 16:16 (GMT +3:30)
After the H990DS variant, we can ask for the other variants if people support it!
So we are looking for money to pay a dev to make a good H990DS kernel (And after that for more models). This is important! Thanks for your collaboration.
Good work creating the thread.
Hope more people jump in
Thanks for pushing this, let's get some more life outta this phone and make rooted oreo usable.
Commenting as a reminder to add to donation list
how do I financially support?
henrylar said:
how do I financially support?
Click to expand...
Click to collapse
Please write the amount of your donation, you can transfer the money when the stable release of the kernel will be ready.
10$
10$
$10
reza_xdv said:
We want the kernel to populate custom NTCODE (Being able to change ntcode for region changes)
Click to expand...
Click to collapse
Hey there
What exactly does this mean? Aren't you able to change the NT-code as it is?
I've actually been wanting to change the region of one of my G5's, but simply changing the code did not do the trick.
I used the hidden menu method btw, where you can also change mac address IIRC.
I also fiddled with the two partitions; cust and OP. Doesn't seem to be it either. Probably something needed to be edited in misc partition or something as well.
And BTW, I'm not offering to make this new stock kernel. Though I did just now re-upload the v2.2 kernel, here:https://www.androidfilehost.com/?w=files&flid=297449
With some fixes and stuff. Not saying it's gonna fix 990ds problems, but at least it's out there for V20 users to be aware.
askermk2000 said:
Hey there
What exactly does this mean? Aren't you able to change the NT-code as it is?
I've actually been wanting to change the region of one of my G5's, but simply changing the code did not do the trick.
I used the hidden menu method btw, where you can also change mac address IIRC.
I also fiddled with the two partitions; cust and OP. Doesn't seem to be it either. Probably something needed to be edited in misc partition or something as well.
And BTW, I'm not offering to make this new stock kernel. Though I did just now re-upload the v2.2 kernel, here:https://www.androidfilehost.com/?w=files&flid=297449
With some fixes and stuff. Not saying it's gonna fix 990ds problems, but at least it's out there for V20 users to be aware.
Click to expand...
Click to collapse
Hey,
the AutoMID option in h990ds hidden menu doesn't allow to modify anything. OP partition in v20 is a complete waste of space and full of junk stuff. We have edited the ntcode in misc by hex editor and have addressed the custom ntcode in cust to use the desired path, but the phone reads the ntcode from the modem as we can still see the factory ntcode in the hidden menu (SVC, Version Info). If we populate the custom ntcode at the kernel level (smem) maybe we can overcome this obstacle. Read this post: https://forum.xda-developers.com/v20/how-to/bounty-thread-lg-v20-root-h990ds-t3493062/post72323004
And thanks for the Re-uploaded kernel. It's more stable than the previous stable 2.2 build.
Personally I was using 2.2 beta 26 as it was working better than other builds, but I can confirm that the new re-uploaded build is slightly better than beta 26. Benchmarks: Antutu -> 2.2 beta 26 (156K) --- 2.2 Stable Re-uploaded (161K)
We would greatly appreciate if you could help us to fix some issues regarding the development of the stock kernel as you know how to deal with the dirty santa stuff. (We've found out that it's causing more issues than expected) If you're willing to guide us and tell us the steps I can send you the Telegram kernel development group link.
A noob question - to update the kernel, I just need to flash it followed by magisk, right?
henrylar said:
A noob question - to update the kernel, I just need to flash it followed by magisk, right?
Click to expand...
Click to collapse
If you're upgrading the current kernel just dirty flashing the new version over the old version followed by magisk is enough.
But if wanna flash a different kernel, you should first flash a clean bootimage then flash the custom kernel followed by magisk.
Question- how much do we need to raise to make this happen?
Additionally, can we specify that this not be specific to a single variant? You might get more donors.
(btw there's already enough bounty to send a dev a used unit to experiment with too! LOL)
Dishe said:
Question- how much do we need to raise to make this happen?
Additionally, can we specify that this not be specific to a single variant? You might get more donors.
(btw there's already enough bounty to send a dev a used unit to experiment with too! LOL)
Click to expand...
Click to collapse
We need to get something working first, then we will open the game to the other variants but we need help raising money to get this done, so if you care about a new kernel for your v20 please help us with the money now.
We have about $130 now. But it isn't enough for an expert dev to make this happen.
Currently we are dealing with touchscreen issue. LG sources are trash and a real dev knows how to deal with them.
i95swervin said:
Curious is anyone on a h990 has tried alpha kernel from my rom project. If you have let me know what was working and what wasnt.
Also why not mk2k kernel ? The dev has done a lot of work for this device.
Click to expand...
Click to collapse
No we haven't tried that kernel. Kindly send me the boot image so I can test it.
About the mk kernel. It's the only kernel available for us, but we have some problems with it like general lagging, apps getting killed and memory problems. And these problems are more severe for h990ds variant.
I the end, if you can help us with kernel development (building or just helping to fix few issues), I can send you the group link.
UPDATE:
I flashed the h910 stock kernel inside the AO rom.
It has static screen issue. However I fixed it by covering the proximity sensor for some seconds. (However this trick won't work on h990ds kernels.)
Sims do not being read.
The UI was smoother comparing to MK kernel but it started lagging after a few minutes.
I can tell stuff were crashing in the background.
Hi Guys,
I am ready to become beta tester for this kernel. I have this device with root and its H990DS India version. I know bit about android and give you crash reports. Please post me link of telegram. I have already replaced its thermal paste to make it cooler and this mod really worked as now device lot better than earlier hot pot condition. Even with mk2000 kernel (great respect for developer) its standby battery sucks. I have Lenovo Z2 plus which also does have same Qc 820 and poor software but due to developer efforts now it is smooth as butter. Hope this kernel solves most of the problems and I am ready to dive into depths of kernel development to save this last of its kind removable battery super phone. Kudos to all developers.
I m also ready to become a tester
Count me in. I'll donate $20.
Related
Found post about VegaComb being released for Adam on TabletRoms.com. Due to the similarities and the fact that there exists ROMs for G-Tab based on Adam. Do we know if there is an effort to port this ROM to G-Tab? Any info would be appreciated as this looks to be THE ROM, with the possibility of fixing camera and hardware acceleration.
A kernel is being worked on ; on the slatedroid forum. The hardware is different so a kernel has to be made for it to work
[email protected]: Posted Today, 09:31 AM
Unfortunately the Vega is not a hardware match for our beloved g-tab, they are very similar however they are not the same hardware exactly, little things like the wireless controller and the camera are different. They also have a different mainboard in their system. I'm pretty sure that the rom that works on theirs is not going to work on ours until we have a working kernel to work from. They have worked very hard on rewriting the drivers to get their tablet to work as well as it is in 3.2 and they don't seem to be slowing down now that it is working. I know that the group that is working on the kernel is working very hard to get it running as quickly as we can, I don't think that most of us have much experience in kernel coding and so it is taking some time to even get it to boot. However I can tell you that we are working diligently to get through the problems and get a kernel out to the community so that we can join the ranks of the Vega in making Google cry by hacking our way to victory. On a side note I want to say how impressed I am by the level of assistance that everyone in this community has for the new members and old members alike. I don't know of another rom that has this level of support from it's users out there. Thanks to all of you that are helping people overcome their issues and enjoy this fantastic rom.
Click to expand...
Click to collapse
.
[email protected] Posted 14 August 2011 - 09:01 PM
Hello all, Ch3vr0n5 here
The GTab Kernel Dev Team would like to chronicle our kernel development process for everyone to enjoy. The Gtablet 2.6.36 kernel project is based on the work done by Eduardo/RaYmAn on the Adam kernel. The biggest thanks goes out to them and anyone else who works on that project because it has made our work possible.
The Dev team is currently: Myself, Icewyng, Mayday_Jay, WayneMasta, Treznorx
[8/25/2011]
We know that we are hanging on init.rc and have a few ideas one how to proceed. Mayday_Jay (Give him and Icewyng a big thank you because they have made this project viable) is working on getting all the developers a proper update.zip that will help those with out a usb to serial converter get some useful debug information.
Don't fret when it takes a couple days for us to update. If you want bleeding edge news, join us on the kernel dev irc channel which is found further on in the thread. We are still working! =)
[8/23/2011]
Linux (BT5) will boot without Touchscreen working. Work is progressing slowly to get this working with Android. Mayday_Jay, with the use of USB -> serial converter has been able to get some useful dmesg output as well as some other debug information that is giving us new ideas on how to proceed.
[8/19/2011]
Starting to modify the adam files to mach the correct values for our device. Our current config gets us passed the birds and to the second boot image and the usb device registers. Trying to get it connected to adb to get some dmesg output.
[8/14/2011]
The resulting kernel did not boot and this is more than likely due to the fact that there are quite a few new config options that need to be set. I have run a diff to find differences between Pershoot's and Rayman's kernel and will be trying a new config either tonight or tomorrow hopefully. Gotta sift through new and deprecated options as well as any they both have but are set differently (and why)
Part 2
The kernel compiled with the additions from rayman's config in pershoots got it past the birds to the "Android 3.0" screen. Tomorrow I will be able to hookup adb and see where it is crashing from there.
[8/15/2011]
Still running through different configurations. Need to ask pershoot what modifications he made to make the .32 kernel boot on the 1.2 bootloader. IE Which files use the NEWBL config option and what the changes are.
[8/16/2011]
I received the source for the Vega kernel from rebel1. I may not update for a few days as I try out different configs and such but I will still be here.
[8/17/2011]
Decided to go with the Adam kernel because of hardware compatibility. Put up the github repo.
GitHub.com Repo
git://github.com/ch3vr0n5/android-tegra-2.6.36-gtablet.git
-----------------------
All thoughts, idea, comments and criticisms are welcome (Please be kind). Just remember, most of us are not programmers or software engineers by trade. I got my degree in network security so I generally play with routers, firewalls and the like and do this as a hobby. If you find anything wrong with what I or any of the Dev team have written please tell me... just don't point and laugh. LOL
Cheers
Click to expand...
Click to collapse
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.
Since everyone kept asking and I myself wanted it, I decided to start this project. The main reason why I didn't do it earlier was because I needed Asus to release the Oreo build already so I could get the required files. So for now I leave you with this, hope I made your day a bit better and have a great day!
Note: the build you see here is just so I could get the compiler working.
Sweet!! Looking forward to seeing the progress on this.
Nice. Do you think the build will have camera quality issues though?
kekley said:
Nice. Do you think the build will have camera quality issues though?
Click to expand...
Click to collapse
We'll see once I get a debuggable build running. I hope it's smooth sailing, but I can't guarantee anything.
First build?
Is this the first build?
If you want tester I am always available.
Naman Vashishth said:
Is this the first build?
If you want tester I am always available.
Click to expand...
Click to collapse
Nice to hear that you want to test the rom, but unfortunately I still don't have a flashable build. I try to work on it whenever I can to get one out as soon as possible. Do keep in mind I do this in my free time when I'm not busy with school. When I do get a debuggable build out, I'll let this forum know so I can get some testers to test it out (other than myself).
+)KEV1N(+ you are a savior , please help us get rid this sick twisted ASUS stock firmware , it's a mess in every aspect , heat, poor battery life, muffled sound via headphones, enormous amount of services running in the background (loses 20% overnight), complete failure in both firmware and kernel wise cause they massively overclocked that S625 , i can live with a rom without the main camera app , OpenCam will do just fine , just take care of that power consumption please cause on paper it should deliver 12-16h SOT , it's 5000mah with s625 and AMOLED screen for god sake !
Thank you in advance for your effort.
Kevin,
Thanks so much for taking on this project!
Not many have the skills or time to do a project like this. I think I can speak for all Z3Z owners when I say that your work will not go unappreciated.
I am simply observing the work of the gentlemen, let us continue in this to create a lineage.
rinampa said:
I am simply observing the work of the gentlemen, let us continue in this to create a lineage.
Click to expand...
Click to collapse
It is a slow process, especially since this is my daily driver. I just came back from holidays back home and now I'll continue to work on it whenever I get the chance. I'll get a working test build running eventually. Can't guarantee when, just know that as a new developer it'll take time to fix things and put them in place since porting is also not easiest of projects.
I visit this thread multiple times a day, it gives me hope)
Thank u Sir
I'm grateful that you are working on this project.
Take your time & carry on.
I want do downgrade form Oreo to MM, Q: will i need to extract recovery.img form MM zip and flash it separately or the stock Oreo recovery will work with all raw asus builds ?
Build# : ww-11.41.87.2 this is the latest MM update before Nougat update, i'm a little confused cause every build has it's own method so any advice for the safest fastest way to :
1-Downgrade to MM from Oreo
2-Flash Magisk to root and install greenify , viper4android cause i'm done with this Oreo.
3-Do i need to unlock the bootloader ?
4-Do i need twrp to flash migisk?
5-Does twrp work with all versions of android ?
3-What are the cons of this procedure if a custom ROM would fall from heaven and i would want to flash it after i flash MM?
sam.fisher190 said:
I want do downgrade form Oreo to MM, Q: will i need to extract recovery.img form MM zip and flash it separately or the stock Oreo recovery will work with all raw asus builds ?
Build# : ww-11.41.87.2 this is the latest MM update before Nougat update, i'm a little confused cause every build has it's own method so any advice for the safest fastest way to :
1-Downgrade to MM from Oreo
2-Flash Magisk to root and install greenify , viper4android cause i'm done with this Oreo.
3-Do i need to unlock the bootloader ?
4-Do i need twrp to flash migisk?
5-Does twrp work with all versions of android ?
3-What are the cons of this procedure if a custom ROM would fall from heaven and i would want to flash it after i flash MM?
Click to expand...
Click to collapse
Guess what !!!
https://forum.xda-developers.com/ze...nbrick-flash-stock-mm-asus-zenfone-3-t3840702
Its more than 100days now since this "little something" post.
Is there any progress dear KEVIN?
or shall I switch to some other device?
Aditya Tiple said:
Its more than 100days now since this "little something" post.
Is there any progress dear KEVIN?
or shall I switch to some other device?
Click to expand...
Click to collapse
I started at the end of my school year a couple of months back. I had a month-long hiatus in July due to me going back to my family back home. I came back in August and am working on it as a side project. Naman's helping me with this right now and so far we got till the boot animation. And then you have those times when we fix something and you go one step back. It's a slow process since the two of us aren't like 24/7 busy on the project. I usually work on it during weekends, but lately I've been needing my phone more and more since I'm very very busy with other priorities. Again, this is a side project I'm doing because I like coding and I like learning new things. So, I can't say for certainty when we can get a release out, but I work eagerly every time hoping it gets past the boot animation or even gets there if I fix something.
I hope this clears out any misconceptions you may have of me and this project. Have a further great day sir
It's nice to hear from you.
That's d very reason I visit this thread.
Keep ur good work going.
Keep us updating.
All d best
Hello mate, you know the whole world is waiting for this build from xda to 4pda to every other android community so what's the news my friend? can you post the bugs maybe we can help with some of them and learn about the Lineage route you chose.
The midterm examination is about to start and you'll be too busy with the study!
My full appreciation to your work.
Instead of quenching our thirst, op made it worse... Shame no developer decided to code for this device.
Mrkblo said:
Instead of quenching our thirst, op made it worse... Shame no developer decided to code for this device.
Click to expand...
Click to collapse
There is a developer who is willing to port lineage if people will crowdfund the purchase of a Z3Z for them.
https://forum.xda-developers.com/zenfone-3-zoom/help/search-developer-custom-rom-t3793680/page2
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
Is there a custom kernel patched for Nethunter available for the v30?
A moderate browsing suggests that there isn't one already available. How difficult would it be to do this on my own? Im decent on a command line, I've got the time to teach myself how it is done, and Im not too afraid of borking my phone.
Are there guides, kitchens, or the like for doing this? Is there anyone who can point me in the right direction, and doesn't mind the occasional question or two (I don't really want someone to do it for me- I'd like to learn a skill I can use in the future as well)?
Thanks.
This is leading nowhere
First you guys asking for kali nethunter "custom kernel" need to clarify what Nethunter even is (the differences from e.g. a LineageOS 15.1 or dot os 2.6 Android Oreo custom ROM build) and what it would require to get it running in the V30
Also: why changes or features are needed from the kernel side
otherwise it's like turning in circles and the dog chasing its tail ...
zacharias.maladroit said:
This is leading nowhere
First you guys asking for kali nethunter "custom kernel" need to clarify what Nethunter even is (the differences from e.g. a LineageOS 15.1 or dot os 2.6 Android Oreo custom ROM build) and what it would require to get it running in the V30
Also: why changes or features are needed from the kernel side
otherwise it's like turning in circles and the dog chasing its tail ...
Click to expand...
Click to collapse
being flippant certainly will get you the answers you are looking for.
furthermore your reading ability is a bit sub-par, to be honest. I asked for a couple pointers on how to begin going about patching a kernel, myself.. Just pointers, or someone willing to let me bounce a couple questions off them. Being a **** is pointless here. I literally cannot tell you what is needed to get it up and running. Im starting at square one, chief.
Nethunter is Linux that runs in a chroot on top of android. It'll run as-is with a unmodified kernel, but to be able to put an external wifi adapter into monitor mode, you need a kernel patched to allow this.
If you don't have something constructive to offer, maybe next time g-g-go kick rocks dude. It takes soooo much *less* time to just not respond, than it does to fire off some half-assed reply because your reading context sucks eggs.
elijah420 said:
[snip]
Nethunter is Linux that runs in a chroot on top of android. It'll run as-is with a unmodified kernel, but to be able to put an external wifi adapter into monitor mode, you need a kernel patched to allow this.
[snap]
Click to expand...
Click to collapse
lol - sorry for the venting - there was lots of built-up anger at all the folks who just ask ask ask and don't do research on their own (probably not even knowing what kali is),
even with a custom kernel we won't get far thus more is needed - OP5 folks might have just what we need (as a good basis)
that's exactly what I needed (sorry my ranty post was kinda like venting anger and getting a reasonable answer to not lose faith in humanity, XDA isn't what it used to be)
pie_I_6_WIP9_11
the last 2 commits are what to be added to the kernel.
I've looked around but haven't found anything related to qcacld (our wifi driver) that would indicate it supports packet injection (perhaps need to look more) in any case thus OTG and usb-powered WiFi adapters would be needed
OP5 elementalx kali defconfig is the diff for OP5 elementalx kernel to get kali wifi drivers
with e.g. lunar kernel base other changes would be needed
When using Markus' kernel base (lineage-15.1 vanilla) - it probably would be easier for you to get there quickly: lineage-15.1
https://medium.com/@ruvoteka/how-to...-android-device-universal-method-32e58660d084
is a somewhat better explanation on how to install kali (non-func on our device currently)
https://forum.xda-developers.com/oneplus-5/development/burgerhunter-t3638810
should offer lots of valuable groundwork and git repos to work with
A good "training" would be to attempt to build a custom ROM (e.g. lineageOS 15.1) and a standalone kernel (either for LG stock or lineage-15.1) and see if both are able to boot
zacharias.maladroit said:
lol - sorry for the venting - there was lots of built-up anger at all the folks who just ask ask ask and don't do research on their own (probably not even knowing what kali is),
even with a custom kernel we won't get far thus more is needed - OP5 folks might have just what we need (as a good basis)
that's exactly what I needed (sorry my ranty post was kinda like venting anger and getting a reasonable answer to not lose faith in humanity, XDA isn't what it used to be)
pie_I_6_WIP9_11
the last 2 commits are what to be added to the kernel.
I've looked around but haven't found anything related to qcacld (our wifi driver) that would indicate it supports packet injection (perhaps need to look more) in any case thus OTG and usb-powered WiFi adapters would be needed
OP5 elementalx kali defconfig is the diff for OP5 elementalx kernel to get kali wifi drivers
with e.g. lunar kernel base other changes would be needed
When using Markus' kernel base (lineage-15.1 vanilla) - it probably would be easier for you to get there quickly: lineage-15.1
https://medium.com/@ruvoteka/how-to...-android-device-universal-method-32e58660d084
is a somewhat better explanation on how to install kali (non-func on our device currently)
https://forum.xda-developers.com/oneplus-5/development/burgerhunter-t3638810
should offer lots of valuable groundwork and git repos to work with
Click to expand...
Click to collapse
no problem. I understand. tone doesn't carry well via text sometimes, so things can get muddled.
I have a couple wifi adapters that support monitor mode. One uses the ath9k driver, and the other uses the rtl8812 driver. I had intended to use one of them (I use them currently with Kali in vbox on my desktop/laptop, so they are known good/working), whichever works best. one is a 11ac, the other 11n.
Does the stock kernel need recompiling with built in support for the wifi adapter/s? Is this the desired end result- a recompiled kernel with support for my particular wifi adapter?
Im going thru the links you posted, currently.
zacharias.maladroit said:
A good "training" would be to attempt to build a custom ROM (e.g. lineageOS 15.1) and a standalone kernel (either for LG stock or lineage-15.1) and see if both are able to boot
Click to expand...
Click to collapse
Im willing to learn how to do this, first. Are there some decent up to date guides that I can follow? Is there a subforum here for this, that I can follow/subscribe to for this?
elijah420 said:
no problem. I understand. tone doesn't carry well via text sometimes, so things can get muddled.
I have a couple wifi adapters that support monitor mode. One uses the ath9k driver, and the other uses the rtl8812 driver. I had intended to use one of them (I use them currently with Kali in vbox on my desktop/laptop, so they are known good/working), whichever works best. one is a 11ac, the other 11n.
Does the stock kernel need recompiling with built in support for the wifi adapter/s? Is this the desired end result- a recompiled kernel with support for my particular wifi adapter?
Im going thru the links you posted, currently.
Click to expand...
Click to collapse
thanks for understanding, agreed - solely text can be pretty prone for misunderstandings
yeah, that's the gist of it
however from the looks of it e.g. SYSVIPC is deprecated and not sure if relay fs (config_relay) is really needed, also options below CONFIG_QCA_CLD_WLAN probably don't need changes at all (might break the wifi of the phone itself)
also CONFIG_USB_G_ANDROID isn't selected in the new config and the f_hid.o and usb_f_hid.o might clash/broken with the patched up state without that config entry being selected
besides that the other config changes might be okay ( OP5_elementalx_kali_defconfig.diff )
elijah420 said:
Im willing to learn how to do this, first. Are there some decent up to date guides that I can follow? Is there a subforum here for this, that I can follow/subscribe to for this?
Click to expand...
Click to collapse
dotfiles that include needed mkbootimg and unpack_bootimg
copy over to ~/bin/
build_lunar.sh
lines out the steps to build a kernel as standalone
Sample steps for lineageos:
https://wiki.lineageos.org/devices/cheeseburger/build
steps are valid until "Download the source code" (including repo sync)
needed git repos for "joan" (V30) have lge in their name:
https://github.com/SGCMarkus?tab=repositories
mostly up to "Updated on May 27" (from the top = newest)
the repos below shouldn't be needed
Those need to be added to .repo/local/manifest.xml (or so, hope that is correct path & file name)
in xml syntax
XDA Y U NO MERGE POSTS ?
edit:
steps for current LineageOS 16.0 related source are:
Code:
export USE_CCACHE=1
export CACHE_DIR=~/.ccache
export KBUILD_BUILD_USER=zacharias.maladroit
export KBUILD_BUILD_HOST=BuildHost
export ARCH=arm64
export CROSS_COMPILE=aarch64-linux-gnu-
export PATH=~/android/toolchains/gcc-arm-8.2-2018.08-x86_64-aarch64-linux-gnu/bin/:$PATH
fakeroot make lineageos_h930_defconfig
fakeroot make -j8
Code:
mkbootimg --kernel arch/arm64/boot/Image.gz-dtb --ramdisk ~/android/final_files/ramdisks_V30_8.0/boot_lineage-16.0_20181118_h930_unpack_b/ramdisk --second /dev/null --cmdline "androidboot.hardware=joan user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 sched_enable_hmp=1 sched_enable_power_aware=1 service_locator.enable=1 rcupdate.rcu_expedited=1 swiotlb=2048 androidboot.configfs=true androidboot.usbcontroller=a800000.dwc3 androidboot.selinux=permissive buildvariant=userdebug" --base 0x00000000 --kernel_offset 0x00008000 --ramdisk_offset 0x02200000 --second_offset 0x00f00000 --os_version 9.0.0 --os_patch_level 2018-11 --tags_offset 0x00000100 --board "" --pagesize 4096 --out ~/android/final_files/ramdisks_V30_8.0/test/H930_lineageOS-16.0_18.11.2018/boot
ramdisk from "stock" (LineageOS default) kernel was extracted via unpack_bootimg , mkbootimg is used to re-assemble the kernel
both are from dotfiles: https://github.com/luca020400/dotfiles/tree/master/bin
zacharias.maladroit said:
dotfiles that include needed mkbootimg and unpack_bootimg
copy over to ~/bin/
build_lunar.sh
lines out the steps to build a kernel as standalone
Sample steps for lineageos:
https://wiki.lineageos.org/devices/cheeseburger/build
steps are valid until "Download the source code" (including repo sync)
needed git repos for "joan" (V30) have lge in their name:
https://github.com/SGCMarkus?tab=repositories
mostly up to "Updated on May 27" (from the top = newest)
the repos below shouldn't be needed
Click to expand...
Click to collapse
thanks for the starting place. I've got plenty to chew on now for the time being.
elijah420 said:
being flippant certainly will get you the answers you are looking for.
furthermore your reading ability is a bit sub-par, to be honest. I asked for a couple pointers on how to begin going about patching a kernel, myself.. Just pointers, or someone willing to let me bounce a couple questions off them. Being a **** is pointless here. I literally cannot tell you what is needed to get it up and running. Im starting at square one, chief.
Click to expand...
Click to collapse
You're replying to a V30 custom kernel developer. The ONLY custom kernel developer for V30, right now. He can be as (seemingly) flippant as he wants, as he has the information you need. He doesn't know yet how much you know or if you can handle full detailed information. Insulting him would not be the best strategy...
I see you two have worked it out. I was starting from the beginning of the thread.
ChazzMatt said:
You're replying to a V30 custom kernel developer. The ONLY custom kernel developer for V30, right now. He can be as (seemingly) flippant as he wants, as he has the information you need. He doesn't know yet how much you know or if you can handle full detailed information. Insulting him would not be the best strategy...
I see you two have worked it out. I was starting from the beginning of the thread.
Click to expand...
Click to collapse
idk, that's a bit extreme
XDA is/was made for developers and thus it's supposed to be fun (if you remember the previous threads where devs were scared off by people with a salient arrogant attitude)
however in this discussion it just seemed that we both might have taken things a bit too personal - so it's fine.
Also - I might not be the only custom kernel dev anymore - jollaman999 is working on a great custom kernel (each custom kernel is unique with its own goals)
not sure if he's ready to release it already though or if it's for personal use.
There are also other devs or users working on the V30 which might not have released their stuff (or are not willing to release it [again] for whatever reason - such as tattedup, etc. )
zacharias.maladroit said:
idk, that's a bit extreme
XDA is/was made for developers and thus it's supposed to be fun (if you remember the previous threads where devs were scared off by people with a salient arrogant attitude)
however in this discussion it just seemed that we both might have taken things a bit too personal - so it's fine.
Also - I might not be the only custom kernel dev anymore - jollaman999 is working on a great custom kernel (each custom kernel is unique with its own goals)
not sure if he's ready to release it already though or if it's for personal use.
There are also other devs or users working on the V30 which might not have released their stuff (or are not willing to release it [again] for whatever reason - such as tattedup, etc. )
Click to expand...
Click to collapse
Well, I wasn't saying you were arrogant. I was saying even if you seemed that way (you didn't seem that way to me, you seemed to be asking legitimate questions about how much detailed information he could handle), still why would he call the person names like "****" or other offenses -- who just might be extremely important resource?
It's all straightened out now, I was reading from beginning of thread.
ChazzMatt said:
You're replying to a V30 custom kernel developer. The ONLY custom kernel developer for V30, right now. He can be as (seemingly) flippant as he wants, as he has the information you need. He doesn't know yet how much you know or if you can handle full detailed information. Insulting him would not be the best strategy...
I see you two have worked it out. I was starting from the beginning of the thread.
Click to expand...
Click to collapse
I understand *exactly* who I was conversing with. I also understand the questions I asked. He/she can certainly be as flippant as they want. It's within their rights to be. Likewise, I can tell him/her to pound sand. To be perfectly blunt, it doesn't bother me.
He is a great dev. I've used his stuff on my v20. Doesn't change the fact that he made some incorrect assumptions and acted on them. Dont attempt to chide me for someone else's goof. It's not correct, and you aren't contributing anything relevant to the actual question. Besides, it was obviously put to bed well before you decided you have to chuck in your two pennies.
elijah420 said:
Besides, it was obviously put to bed well before you decided you have to chuck in your two pennies.
Click to expand...
Click to collapse
As I've said at least twice. So you're not adding anything either. Or you can't read.
Sent via open market LG US998 V30/V30+
zacharias.maladroit said:
lol - sorry for the venting - there was lots of built-up anger at all the folks who just ask ask ask and don't do research on their own (probably not even knowing what kali is),
even with a custom kernel we won't get far thus more is needed - OP5 folks might have just what we need (as a good basis)
that's exactly what I needed (sorry my ranty post was kinda like venting anger and getting a reasonable answer to not lose faith in humanity, XDA isn't what it used to be)
pie_I_6_WIP9_11
the last 2 commits are what to be added to the kernel.
I've looked around but haven't found anything related to qcacld (our wifi driver) that would indicate it supports packet injection (perhaps need to look more) in any case thus OTG and usb-powered WiFi adapters would be needed
OP5 elementalx kali defconfig is the diff for OP5 elementalx kernel to get kali wifi drivers
with e.g. lunar kernel base other changes would be needed
When using Markus' kernel base (lineage-15.1 vanilla) - it probably would be easier for you to get there quickly: lineage-15.1
https://medium.com/@ruvoteka/how-to...-android-device-universal-method-32e58660d084
is a somewhat better explanation on how to install kali (non-func on our device currently)
https://forum.xda-developers.com/oneplus-5/development/burgerhunter-t3638810
should offer lots of valuable groundwork and git repos to work with
A good "training" would be to attempt to build a custom ROM (e.g. lineageOS 15.1) and a standalone kernel (either for LG stock or lineage-15.1) and see if both are able to boot
Click to expand...
Click to collapse
The last two including
"sched/core: Allow __sched_setscheduler() in interrupts when PI is not..."?
I've never built a kernel but I'd like to have the option of mobile pentesting. If you find yourself with the time and inclination I'd be interested. I'm still learning Java, struggling with recursion, so custom kernels is probably out of my reach.
tooandrew said:
The last two including
"sched/core: Allow __sched_setscheduler() in interrupts when PI is not..."?
I've never built a kernel but I'd like to have the option of mobile pentesting. If you find yourself with the time and inclination I'd be interested. I'm still learning Java, struggling with recursion, so custom kernels is probably out of my reach.
Click to expand...
Click to collapse
nope - I moved the commits to a dedicated branch:
pie_I_6_WIP9_11_kali
so it's
HID patch
Wireless packet injection & selinux patch
the related wifi drivers from the kernel diff need to selected though - since specific wireless adapters are needed which support packet injection functionality