• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root AOKP Port Project

Jaay Dogg

Jaay Dogg

Android Expert
Ok i've got the boot image we need, just gotta spilt it open & grab the zimage & put it in our files then we should have boot.:D Working on it now, splitting boot images is not my thing but i'm on it. Should'nt be long i've got a friend who's already ported this, so it won't be long.
 
take the phone that is THE closest to yours (chipset, cpu, etc.) and see if they have device files for CM7/CM9/AOKP. Then start looking through the code and changing it to better fit the Design's. this is what Gannon said to do any takers on hunting down an HTC device that's close to ours ? I'm in the middle of some many projects any help would be great:D
 
I'll make this public because you seem to have. Lol

What exactly are you trying to achieve here? Are you trying to build AOKP from source or port AOKP from a different device?
 
The closest to our phone is the inc2 & evo shift. There are device configuration/overlays for the kingdom on github (hero s us cellular / design 4G sprint). Cm7, cm9, & evervolv are all aosp for kingdom started. The Cm7 & evervolv were started on a speedy port, but I think now on the inc2 done by ss2man44 & precludedrew https://github.com/ss2man44/android_device_htc_kingdom & https://github.com/Evervolv. Kernel is here http://git.tiamat-dev.com/7x30/htc-kernel-msm7x30/log/?h=android-msm-2.6.35-ics. Both are said to boot, but have ril issues in the kernel. This project seems dead as the last work was done 2 months ago. It has been said that we are waiting on a response from cyanide (sp) the kernel dev. Cm9 was started by gu1dry & compiled by me & did not boot.

If you need anymore links or info let me know & I'll try to help. I'm sure if credit us given, you can cherry pick out of the source linked here.
 
grad061980 said:
The closest to our phone is the inc2 & evo shift. There are device configuration/overlays for the kingdom on github (hero s us cellular / design 4G sprint). Cm7, cm9, & evervolv are all aosp for kingdom started. The Cm7 & evervolv were started on a speedy port, but I think now on the inc2 done by ss2man44 & precludedrew https://github.com/ss2man44/android_device_htc_kingdom & https://github.com/Evervolv. Kernel is here 7x30/htc-kernel-msm7x30 - Tiamat Kernels for HTC devices with Qualcomm Snapdragon MSM7X30 processors. Fork of CyanogenMod/ht-kernel-msm7x30.. Both are said to boot, but have ril issues in the kernel. This project seems dead as the last work was done 2 months ago. It has been said that we are waiting on a response from cyanide (sp) the kernel dev. Cm9 was started by gu1dry & compiled by me & did not boot.

If you need anymore links or info let me know & I'll try to help. I'm sure if credit us given, you can cherry pick out of the source linked here.
Click to expand...

Was CM9 ever released for the kingdom? In another forum or anything else? But yeah, Jayydogg, if you're wanting to build AOKP, these links above are your best bet.
 
gannon5197 said:
Was CM9 ever released for the kingdom? In another forum or anything else? But yeah, Jayydogg, if you're wanting to build AOKP, these links above are your best bet.
Click to expand...

None released. Cm9 was a mess around project by gu1dry (not a cm maintainer) No other forum. Evervolv maintainer is ss2man44. All projects seem to be at a stand still for the last month or 2.
 
joshua.worth said:
Kingdom does have ICS...
Click to expand...

Not aosp. Leaked ruu from the boost mobile design 4G (android 4.0.3 Sense 3.6)




gannon5197 said:
Does it have a stable setup for device/vendor files?
Click to expand...
The device/vendor files linked above are said to boot, with ril issues. That's the last the maintainer for evervolv told me. Haven't heard from him in a while, so not real sure of all the issues or stability of the rom as I haven't put in the time yet to compile the build myself.
 
grad061980 said:
Not aosp. Leaked ruu from the boost mobile design 4G (android 4.0.3 Sense 3.6)





The device/vendor files linked above are said to boot, with ril issues. That's the last the maintainer for evervolv told me. Haven't heard from him in a while, so not real sure of all the issues or stability of the rom as I haven't put in the time yet to compile the build myself.
Click to expand...

Yeah the person I replied to didn't say we don't have AOSP he said we don't even have ICS
 
joshua.worth said:
Yeah the person I replied to didn't say we don't have AOSP he said we don't even have ICS
Click to expand...
My regards, I didn't see any on this site so I didn't know

This is how I built AOKP for my device, even though it wasn't officially supported.

1. Set up your build environment

Initializing a Build Environment | Android Open Source

2. Download AOKPs source

Code: 
repo init -u git://github.com/AOKP/platform_manifest.git -b ics 
repo sync -j16

3. Pull in your local device and/or vendor files (In this case, I would guess ss24man's)
git clone git://github.com/ss2man44/android_device_htc_kingdom.git -b ics device/htc/kingdom

4. Change some stuff in the full_device.mk and cm.mk and vendorsetup.sh files (full_kingdom) that looks sort of like the changes I did here:
https://github.com/rukin5197/androi...mmit/87c2b0f306417da75f546bc017484d14e9dd9263

5. Change some stuff in the vendor/aokp stuff. You're going to need to add your device in the vendorsetup.sh and add a kingdom.mk in products. And you're going to need to add that kingdom.mk in the AndroidProducts in the products folder. This is mine on that situation:
https://github.com/rukin5197/vendor/commit/4e7baaa697988a1a93330eb5018157643d052095
 
gannon5197 said:
My regards, I didn't see any on this site so I didn't know

This is how I built AOKP for my device, even though it wasn't officially supported.

1. Set up your build environment

Initializing a Build Environment | Android Open Source

2. Download AOKPs source

Code: 
repo init -u git://github.com/AOKP/platform_manifest.git -b ics 
repo sync -j16

3. Pull in your local device and/or vendor files (In this case, I would guess ss24man's)
git clone git://github.com/ss2man44/android_device_htc_kingdom.git -b ics device/htc/kingdom

4. Change some stuff in the full_device.mk and cm.mk and vendorsetup.sh files (full_kingdom) that looks sort of like the changes I did here:
https://github.com/gannon5197/andro...mmit/87c2b0f306417da75f546bc017484d14e9dd9263

5. Change some stuff in the vendor/aokp stuff. You're going to need to add your device in the vendorsetup.sh and add a kingdom.mk in products. And you're going to need to add that kingdom.mk in the AndroidProducts in the products folder. This is mine on that situation:
https://github.com/gannon5197/vendor/commit/4e7baaa697988a1a93330eb5018157643d052095
Click to expand...

Thanks I'll look into this when I've got some more rest and this may help others as well
 
grad061980 said:
It's for the original evo. I don't think you will have much luck with porting it over. You would be better off finding an aokp for the evo shift or incredible 2 & porting from them.
Click to expand...

Not sure about Evo shift, but the Inc2 has official AOKP if that's what you're looking for.
 
Sorry but there is no device close to ours. I don't recall a qhd screen 7x30 device right off my head. Then you are going to run into ril issues as well. Ps if you are planning on using the tiamat kernel I assume you guys have. It works in recovery, how ever be warned that I believe charging is messed up in it. Then contrary to what has been said elsewhere the shift only shares in common wimax and the cpu. Otherwise it is pretty different.
 
You must log in or register to reply here.
Back
Top Bottom