Hello I have a cheap allwinner a23 tablet on jelly bean 4.2.2,
I want to put CyanogenMod on my tab
Does anyone know any way to get this custom rom on my tablet?
Thanks. Have a Good Day !
New to XDA
Bump Im looking for this too!
xestroyer said:
Hello I have a cheap allwinner a23 tablet on jelly bean 4.2.2,
I want to put CyanogenMod on my tab
Does anyone know any way to get this custom rom on my tablet?
Thanks. Have a Good Day !
New to XDA
Click to expand...
Click to collapse
Fortunately, I have a similar tablet too, but with 4.4.2. I have started working over it, to compile CWM. If you have link to working CWM or Sources, kindly do let me know. Will help me to speed up the compilation.
trivalent said:
Fortunately, I have a similar tablet too, but with 4.4.2. I have started working over it, to compile CWM. If you have link to working CWM or Sources, kindly do let me know. Will help me to speed up the compilation.
Click to expand...
Click to collapse
Hi, I have been working on Q8H A23 table for the past few weeks, but have not yet been able to compile a proper hwcomposer. Could you let me know you progress on CM for A23?
nann invinci said:
Hi, I have been working on Q8H A23 table for the past few weeks, but have not yet been able to compile a proper hwcomposer. Could you let me know you progress on CM for A23?
Click to expand...
Click to collapse
I had to stop the work for personal reason. I hope to start it again soon. BTW what sources you are using to compile? Can you share your CM Device tree for A23?
trivalent said:
I had to stop the work for personal reason. I hope to start it again soon. BTW what sources you are using to compile? Can you share your CM Device tree for A23?
Click to expand...
Click to collapse
I am using cm 11 to compile. I got things to boot into lock screen, apps and so on. Got the touch screen to work just now (by turning LEGACY_TOUCHSCREEN on in InputReader.cpp, after a lot of code digging). As for the device tree, I will be happy to share it once I have everything tidy up. I use the same device tree from polaris-p1 in the A23 source code, however, with all the libhardware removed since they keep crashing with the cm11 (ie. hwcomposer). As well with blobs modules and some /egl libs . Also tried to compile hwcomposer from a13 or so source (on Internet), it runs, but much slower than without hwcomposer.
Rotation sensor also works.
nann invinci said:
I am using cm 11 to compile. I got things to boot into lock screen, apps and so on. Got the touch screen to work just now (by turning LEGACY_TOUCHSCREEN on in InputReader.cpp, after a lot of code digging). As for the device tree, I will be happy to share it once I have everything tidy up. I use the same device tree from polaris-p1 in the A23 source code, however, with all the libhardware removed since they keep crashing with the cm11 (ie. hwcomposer). As well with blobs modules and some /egl libs . Also tried to compile hwcomposer from a13 or so source (on Internet), it runs, but much slower than without hwcomposer.
Rotation sensor also works.
Click to expand...
Click to collapse
Any chance of sharing that device tree?
Related
Hi, i'm trying to compile cm9 (ics) from source but i need help.
I try to create a new device tree in my source, i got it to compile after a lot of work but the device keep rebooting, and give other nasty errors, so i got the ideia of copy from another device, i ussed htc bravo this device as same processor and same type of display, i got it to compile, install in the device and it booted, it show the ics image but when i touch the display it show a circle in the screen like a cursor and the touch as a resolution that was to big, so i edit build.prop and put lcd.density=160 the image was fine it show the clock and the back, home bottons but the touch still displays the same circle cursor and does not respond very well.
Does any one know how to solve this problem ?
if any one manage to compile cm9 for s7 can share the device and vendor files ?
I like to be able to compile it from source and help to create a stable cm9 version for the s7, i have the 105 model.
thanks,
Hal_2000
I haven't bothered building, but supposedly this one works for CM10?
https://github.com/asturel
xaueious said:
I haven't bothered building, but supposedly this one works for CM10?
https://github.com/asturel
Click to expand...
Click to collapse
Hi, the asturel versions of cm9 and cm10 does not work on my s7-105, cm9 gets stuck on boot animation and cm10 the sreen gets blanck.
I have tryed with that source files from asturel, i compile it but when i install in the device, the screen gets blanck, so in my model does not work
Thanks for your reply.
hal_2000
hal_2000 said:
Hi, the asturel versions of cm9 and cm10 does not work on my s7-105, cm9 gets stuck on boot animation and cm10 the sreen gets blanck.
I have tryed with that source files from asturel, i compile it but when i install in the device, the screen gets blanck, so in my model does not work
Thanks for your reply.
hal_2000
Click to expand...
Click to collapse
asturels builds are for 201 version of S7 slim and everything forks except camera...
Hi all, solve the problem of the touch screen and the cursor, there were a few lib missing on my build, now i'm trying to solve the halt problem, after i unlock the screen the device halt and after 6 seconds reboots, maybe some more missing libs, going to do some more test.
hal_2000
first test version
hi, got it, manage to compile cm9 from source, it boot, does not hang or reboots.
test it, http://forum.xda-developers.com/showthread.php?t=2110276
hal_2000
I have a LG P350 which development has stopped but i want to keep it updated, i have my computer ready for building, also i have kernel sources, Cyanogenmod 11 and 10.1 sources too, (I don't know exactly if 10.1 sources could help) and i know that i need to apply patches to work on Armv6 but i don't know how to apply them to the source code, also i don't know if i would just need the pure source code to build or i need to do more modifications to it and finally, i don't know if the rom would work with 2.36 kernel which it's the most stable one for this device, i'm very new in this but i know that i can keep update my little phone, thank you all in advance for help.
DiegoConD said:
I have a LG P350 which development has stopped but i want to keep it updated, i have my computer ready for building, also i have kernel sources, Cyanogenmod 11 and 10.1 sources too, (I don't know exactly if 10.1 sources could help) and i know that i need to apply patches to work on Armv6 but i don't know how to apply them to the source code, also i don't know if i would just need the pure source code to build or i need to do more modifications to it and finally, i don't know if the rom would work with 2.36 kernel which it's the most stable one for this device, i'm very new in this but i know that i can keep update my little phone, thank you all in advance for help.
Click to expand...
Click to collapse
Hello, looking at your situation here is what I can conclude. First off you will need to change things for building on ARMv6 architecture, check this out for example. But your biggest problem will be that Android 4.0+ uses Linux kernel version 3.0+, and with the 2.36 kernel you have a lot of things will be broken and need fixing. That being said if your up for the challenge for it cause that's what were all about .
shimp208 said:
Hello, looking at your situation here is what I can conclude. First off you will need to change things for building on ARMv6 architecture, check this out for example. But your biggest problem will be that Android 4.0+ uses Linux kernel version 3.0+, and with the 2.36 kernel you have a lot of things will be broken and need fixing. That being said if your up for the challenge for it cause that's what were all about .
Click to expand...
Click to collapse
Well, i got this http://forum.xda-developers.com/showthread.php?t=2144790 that is the most similar phone talking about hardware, it has 3.0 kernel working well so i thought i could port it, i found this http://stackoverflow.com/questions/15961306/porting-kernel-from-another-device so i think i would have less problems due hardware similarities (Look here http://www.gsmarena.com/compare.php3?idPhone1=3516&idPhone2=3735 ) so, if i have cm11 pure sources, i add this kernel sources and some patches i would have it booting? Sorry for this very dumb question but, i didn't get at all about the armv6 part, how to apply patches, which i would need and all that, i really want to learn about this so thank you for this answer and the next ones :good:
DiegoConD said:
Well, i got this http://forum.xda-developers.com/showthread.php?t=2144790 that is the most similar phone talking about hardware, it has 3.0 kernel working well so i thought i could port it, i found this http://stackoverflow.com/questions/15961306/porting-kernel-from-another-device so i think i would have less problems due hardware similarities (Look here http://www.gsmarena.com/compare.php3?idPhone1=3516&idPhone2=3735 ) so, if i have cm11 pure sources, i add this kernel sources and some patches i would have it booting? Sorry for this very dumb question but, i didn't get at all about the armv6 part, how to apply patches, which i would need and all that, i really want to learn about this so thank you for this answer and the next ones :good:
Click to expand...
Click to collapse
The best way to start is use the ARMv6 branch of Cyanogenmod 11, replace the CM 10.1 in the previous linked build guide with cm-11.0 ("repo init -u git://github.com/androidarmv6/android.git -b cm-11.0"), and then to direct the build to use your kernel take a look at this guide on integrated kernel building with Cyanogenmod.
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.
Hello everyone, can somebody compile CM12.1 or CM13 for XOLO BLACK? I know that there is already a CM12.1 ROM out there for this device but I've heard it's buggy. So, can someone come out with a bug-free ROM?
This device has decent hardware but TBH this HIVE ROM is ****ty, laggy and also very buggy, they don't even push out any OTA updates. Also, the kernel for this device could be found here: https://github.com/hiveinside/xolo_kernel
tanujboy said:
Hello everyone, can somebody compile CM12.1 or CM13 for XOLO BLACK? I know that there is already a CM12.1 ROM out there for this device but I've heard it's buggy. So, can someone come out with a bug-free ROM?
This device has decent hardware but TBH this HIVE ROM is ****ty, laggy and also very buggy, they don't even push out any OTA updates. Also, the kernel for this device could be found here: https://github.com/hiveinside/xolo_kernel
Click to expand...
Click to collapse
I am compiling a lineage 14.1 rom and it is in process. I cant find device specific code for this device.
I need developers to help please.
dev.kasibhatla said:
I am compiling a lineage 14.1 rom and it is in process. I cant find device specific code for this device.
I need developers to help please.
Click to expand...
Click to collapse
No source code for this device. Don't waste your time. If you've just bought this phone and it's returnable then take my advice, return it.
I've already moved on from this device now I own a OP3.
tanujboy said:
No source code for this device. Don't waste your time. If you've just bought this phone and it's returnable then take my advice, return it.
I've already moved on from this device now I own a OP3.
Click to expand...
Click to collapse
Bought over a year ago. Trying to build the device tree. Lets see.
Zero support from the xolo developers. They have already removed this phone from their website.
dev.kasibhatla said:
Bought over a year ago. Trying to build the device tree. Lets see.
Zero support from the xolo developers. They have already removed this phone from their website.
Click to expand...
Click to collapse
You can use the source code of Motorola X play. It has same processor and same screen resolution. You can take its device tree from lineage github and edit it as per your phone. Its code name is lux use this name to search it on git.
chiraganeja said:
You can use the source code of Motorola X play. It has same processor and same screen resolution. You can take its device tree from lineage github and edit it as per your phone. Its code name is lux use this name to search it on git.
Click to expand...
Click to collapse
I was building the device tree. I ll try what you say if it doesn't work out.
Thanks
Hello all, where would I start in making a working twrp for this phone?
Does anyone know if Motorola has released the device tree/source code for this phone so we can make the roms? LineageOS would be ideal.
Well, I have the same phone. Couldn't find ROMs for it.
thebestofall007 said:
Hello all, where would I start in making a working twrp for this phone?
Click to expand...
Click to collapse
look in this forum here, there are a couple floating around for it, I've made one, that I was able to fully flash to mine and has touch (Android 10. there's another that is 11 on here too by another poster), but as there are multiple display options out there it seems for how they were made, that is the sticking point, as not all will behave properly when booted into a recovery like mode it seems. I have tried installing it over bootloader and it will have touch then, but when flashed to recovery the touch never activates properly. So it all likely comes to that, as we'll need combine them in, properly applying proper checks for each display type and having it use the proper driver files, since can't load them all at once or it breaks things.
Working shrp for Borneo
thebestofall007 said:
Hello all, where would I start in making a working twrp for this phone?
Does anyone know if Motorola has released the device tree/source code for this phone so we can make the roms? LineageOS would be ideal.
Click to expand...
Click to collapse
First place to start: twrpdtgen
Read the "readme"
Also check out:
[DEV]How to compile TWRP touch recovery
Device tree made from A10. Should still be relevant for A11.
Kernel for A10. Unfortunately I don't think Moto released the one for A11 yet. You can ask on their GitHub and devs might consider your request.
TWRP for A11. Touch is working.
Edit : here's a link for the device tree (in text) from A11
maybe this will work
thebestofall007 said:
Hello all, where would I start in making a working twrp for this phone?
Does anyone know if Motorola has released the device tree/source code for this phone so we can make the roms? LineageOS would be ideal.
Click to expand...
Click to collapse
maybe this will help probably https://github.com/MotorolaMobilityLLC/kernel-msm
UPDATE: I have a telegram account where we are discussing how to make a custom lineage OS. I'm at the gathering stage and in the process of porting a device tree. For starters I want to start with lineage OS 18 because its the same android version the stock OS is, to be on the safe side, and that I've never done ROMS before.
Moto G Power 2021
I now have a device tree with the help of AOSPdtgen from the stock ROM from mirrors.lolinet: https://github.com/thebestofall007/android_device_motorola_borneo
I have started the build and got the first error:
https://imgur.com/a/XZoqy8B
I've looked this error up and they say it's because of the ram, but the error recurs at the same point. I have 16gb of swap, too.
thebestofall007 said:
I have started the build and got the first error:
https://imgur.com/a/XZoqy8B
I've looked this error up and they say it's because of the ram, but the error recurs at the same point. I have 16gb of swap, too.
Click to expand...
Click to collapse
you need alot of ram to build a rom for android 36GB of RAM or more will be beater to it wont crash
KILLFIREY1389 said:
you need alot of ram to build a rom for android 36GB of RAM or more will be beater to it wont crash
Click to expand...
Click to collapse
The error turned out to be entries in the proprietary-files.text file that needed to be deleted.
@thebestofall007 If you'll suceed. please take in consideration to build \e\ (aka deGoogled Lineage) too.
Here's a couple of interesting links that may help:
https://doc.e.foundation/support-topics/build-e
https://community.e.foundation/t/howto-building-e-roms-a-beginners-guide/26371
Last but not least, we've also suggested them (check here) to setup a "build (V)Machine" by modding this colab notebook to made it device agnostic:
https://github.com/viam1-dev/colab_lineage_build
Hope can "inspire" you.
Thanks in advance.
Does anyone have a complete list of sources so far? I have some experience in the past building ROMs for Android 5 and I wouldn't mind trying. I have a lot of computer resources to dedicate to building as well.
Device tree: https://github.com/thebestofall007/android_device_motorola_borneo-old
Does anyone know if there is a kernel source? I looked on the Moto github and couldn't find one. Is everyone using prebuilt for the time being? Also, do we need a vendor tree?
Thanks