Jeter/Aljeter Pie Kernel Sources

Spaceminer

Senior Member
Sep 9, 2016
1,159
546
113
Olympus Mons
G6 Play Sources

A huge thanks to the anonymous user who sent this post to Motorola. This issue is fixed. We can now clone all the Jeter kernel sources in one shot!!!

For Oreo:
Code:
git clone -b oreo-8.0.0-release-jeter https://github.com/MotorolaMobilityLLC/kernel-msm jeter
For Pie:
Code:
git clone -b pie-9.0.0-release-pcp29 https://github.com/MotorolaMobilityLLC/kernel-msm jeter
This will clone the kernel sources into a folder named "jeter".

Deprecated Information:
In an effort to combat Motorola's anti open source practices, I've collected all available kernel sources for the G6 Play and placed them into a single zip. Inside this zip are 43 gzips which contain all parts needed to build the kernel for our device.


Back story:

For those of you who don't know, Motorola has split the kernel sources into many parts. There is no easy way to grab them, sync them, or pull them. GitHub also lacks the ability to search for specific release tags.

Example: You can't search for "MMI-OCPS" in all of Motorola's repos, and you can't search like this inside of a single repo either.

So you have to manually open each repo one by one, and scan every page for the tag that matches the release you need. Sometimes there's nothing. Sometimes it's 5 pages down. Then you have to unpack all the kernel parts you found, and some of them need to be merged into the same folder. There is no explanation on what gets merged where. You have to try building it, get an error, then find the part you're missing in one of the zips and add it. Then repeat the process.

This is the most anti open source practice I've ever seen. I'm hoping this spurs some development for our device.

Link is now void.
 

Attachments

Last edited:

Spaceminer

Senior Member
Sep 9, 2016
1,159
546
113
Olympus Mons
Nice work putting all of these together.
I almost have a tree going! I clobbered one together so I can rebuild twrp using Omni 9.0 sources. I'm stuck at 99% but I'm slowly chomping the bit. It seems like I can easily build a 64bit twrp if I get the last kinks out. A complete build is slowly inching closer and I can finally taste it!
 

Spaceminer

Senior Member
Sep 9, 2016
1,159
546
113
Olympus Mons
Good news and bad news. I finally got the build to complete. However, it's not booting because for some reason, it's not building the ramdisk. I can't figure out why. No amount of searching has helped me with this. I can't find any information about it. It shouldn't even be possible as far as I can tell. It produces a recovery.img, kernel, and dt.img but no ramdisk. I'm really lost on this one.
 

Attachments

Sands207

Senior Member
Oct 13, 2014
1,275
669
0
Portland,Maine
Good news and bad news. I finally got the build to complete. However, it's not booting because for some reason, it's not building the ramdisk. I can't figure out why. No amount of searching has helped me with this. I can't find any information about it. It shouldn't even be possible as far as I can tell. It produces a recovery.img, kernel, and dt.img but no ramdisk. I'm really lost on this one.
Did you have any luck figuring this out?
 

madbat99

Senior Member
Mar 1, 2014
5,539
3,285
113
G6 Play Sources

In an effort to combat Motorola's anti open source practices, I've collected all available kernel sources for the G6 Play and placed them into a single zip. Inside this zip are 43 gzips which contain all parts needed to build the kernel for our device.


Back story:

For those of you who don't know, Motorola has split the kernel sources into many parts. There is no easy way to grab them, sync them, or pull them. GitHub also lacks the ability to search for specific release tags.

Example: You can't search for "MMI-OCPS" in all of Motorola's repos, and you can't search like this inside of a single repo either.

So you have to manually open each repo one by one, and scan every page for the tag that matches the release you need. Sometimes there's nothing. Sometimes it's 5 pages down. Then you have to unpack all the kernel parts you found, and some of them need to be merged into the same folder. There is no explanation on what gets merged where. You have to try building it, get an error, then find the part you're missing in one of the zips and add it. Then repeat the process.

This is the most anti open source practice I've ever seen. I'm hoping this spurs some development for our device.

Release Tag:MMI-PPP29.55-25 Pie (281mb)
I can't find Jeter pie source anywhere on their GitHub.
Mind throwing up a link?
 

Spaceminer

Senior Member
Sep 9, 2016
1,159
546
113
Olympus Mons
Can you link me to the kernel source? I'll repo sync and try it on my dev machine
I can't find Jeter pie source anywhere on their GitHub.
Mind throwing up a link?
They don't exist in a single location on GitHub. There's literally no way to sync their sources that I'm aware of. I had to untar all the files that I have zipped together in the OP, into a rudimentary tree I found. Here's the closest thing we have.

https://github.com/SyNtheticNightmar3/android_device_motorola_jeter
 

Sands207

Senior Member
Oct 13, 2014
1,275
669
0
Portland,Maine
They don't exist in a single location on GitHub. There's literally no way to sync their sources that I'm aware of. I had to untar all the files that I have zipped together in the OP, into a rudimentary tree I found. Here's the closest thing we have.

https://github.com/SyNtheticNightmar3/android_device_motorola_jeter
Did the g6 play start out on Nougat? I have been out of development since i got sick last year. I wish between us all we could get this mess sorted out. I'm bummed Moto doesn't have an open source website besides github where we could just download the source code and build from scratch.
 

ninjakira

Senior Member
Nov 6, 2016
539
244
33
29
batavia, ohio
Did the g6 play start out on Nougat? I have been out of development since i got sick last year. I wish between us all we could get this mess sorted out. I'm bummed Moto doesn't have an open source website besides github where we could just download the source code and build from scratch.
No. It came shipped with Oreo which means its treble compatible which is why you don't have to do the stuff people with phones before oreo need to do to "make" there phone treble compatible so they could flash gsi
 

ninjakira

Senior Member
Nov 6, 2016
539
244
33
29
batavia, ohio
Then why is the nougat branch cloned for omni sources?
Hmmm I honestly couldn't even tell you why at this point ?? the development for this phone has been absolute hell from people stealing twrps to people trying to sell overpriced source and tress to making fake trees ?? like it's one giant "bruh, what the hell" moment
 
Last edited: