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.
Related
Hi all,
i want to start with AOSP 4.2 for our SGS3 i9300 - is anybody interested to develop and publish a AOSP based rom with me?
I'm a real application developer (C,C++,JAVA,PHP,MySQL,some Oracle PLSQL) and now its some cold out - i have time to do
some nice things
I think a team of 2 or 3 developers should be enough to develop on this rom, as we can use a lot from AOSP 4.1.2
### EDIT
As long as no one has found to help, here a short description of current progress:
- Code is pure based on AOSP 4.2 but some snippets of CyanogenMod to bring up hardware (camera,graphics,audio)
- Device is bootable (no other boot.img required anymore)
- Bootanimation is working
- Mount of partitions is working
- Deodexing is working
- adb, debuggerd and root access is working
Not working: a lot
- Graphic not working perfect, needs a kernel patch or a working gralloc/hwcomposer/hwconverter to work without laggy PMEM)
- Camera can not be activated due to a missing function call (undefined reference, maybe it can be solved with a newer driver)
- Audio: missing speaker device (Code have to reworked to work with stagefright and tinyalsa libs)
- USB/internal SDCard: cant be mounted (error message sounds like the device is mounted twice, have to find the error in init process)
- RIL not working (Java file from CM10 have to be integrated in frameworks/opt/telephony)
Currently, i'm working on the Graphic problem and USB part to bring up the device to a stable UI
Way to go man. Good luck to you!
Good luck ...!! Im waiting
Sent from my GT-I9300 using xda premium
Good evening,
Well how have you imagined that? Do you have build something like that before or would this be your first attempts to build up a rom from scratch? Do you know what's all necessary to contribute for that?
I would try to help you, but I have clearly to say that I haven't done anything like this before. I'm in the last term of my study of technical computer sciences, working in a company as application programmer for C/C++ and Java(Android). Due to my studies I have also some knowledge about hardware programming, down to read/writing some code in assembler. I would be interested to this if I get introduced to the topic and some help with the necessary tool chain wouldn't hurt too ^^.
greetings
hop3l3ss1990 said:
Good evening,
Well how have you imagined that? Do you have build something like that before or would this be your first attempts to build up a rom from scratch? Do you know what's all necessary to contribute for that?
I would try to help you, but I have clearly to say that I haven't done anything like this before. I'm in the last term of my study of technical computer sciences, working in a company as application programmer for C/C++ and Java(Android). Due to my studies I have also some knowledge about hardware programming, down to read/writing some code in assembler. I would be interested to this if I get introduced to the topic and some help with the necessary tool chain wouldn't hurt too ^^.
greetings
Click to expand...
Click to collapse
I have successfully built a rom in year 2010 for the LG-P500 device, based on CM7 and modified it in a strange way, so i included a lot of nice things
written from scratch - this rom was a unicate ... later, i developed the "Phoenix Launcher" for Gingerbread enabled devices, but its development is currently
frozen because its strange to support every or almost every device with a bugless launcher. In the last months i learned a lot about android and have to re-think about
what i'm able to do, and what i want to do. In the summer of 2011 i bought my SGS3, the first thing i was doing was to remove that samsung crap from my device and
have installed AOKP. So now it's time to do my own thing again - i want to have AOSP as i think for me its the best Android solution for myself and want to publish it
to other users who think "thats ok for me" too
In short, it doesnt matter if its your first rom - its enough if you know about basic things like "how is android doing all that nice things", "how to debug code", "how to fix
some bugs (even strange bugs)" and some experience with git and github. All other you can learn in a very short time - i've learned the most of things with try & error
andy572 said:
I have successfully built a rom in year 2010 for the LG-P500 device, based on CM7 and modified it in a strange way, so i included a lot of nice things
written from scratch - this rom was a unicate ... later, i developed the "Phoenix Launcher" for Gingerbread enabled devices, but its development is currently
frozen because its strange to support every or almost every device with a bugless launcher. In the last months i learned a lot about android and have to re-think about
what i'm able to do, and what i want to do. In the summer of 2011 i bought my SGS3, the first thing i was doing was to remove that samsung crap from my device and
have installed AOKP. So now it's time to do my own thing again - i want to have AOSP as i think for me its the best Android solution for myself and want to publish it
to other users who think "thats ok for me" too
In short, it doesnt matter if its your first rom - its enough if you know about basic things like "how is android doing all that nice things", "how to debug code", "how to fix
some bugs (even strange bugs)" and some experience with git and github. All other you can learn in a very short time - i've learned the most of things with try & error
Click to expand...
Click to collapse
This all sounds interesting for me and yes I like the idea of developing a own clean rom with some cool additional stuff, too. But what would be the first steps to a new rom? Have you begun with all the administration stuff like setting up a new gitrepo, make a to do list etc...?
I think Code debugging and writing some new stuff wouldn't be a problem for me but what are you meaning excactly with "how is android doing all that nice things"? How it build up, deep level architecture? Well, I know how the "normal" Linux system is working, how modules are getting loaded into the kernel... But how this is correctly working on android I have to learn at first and if there is a chance to do that I would do it
Currently on my S3 is SlimBean and till that there is still no update to 4.2 I'm happy with it, but exploring something new would be pretty cool
Do you have an IRC chat room or something like that? I've to go offline now, my girlfriend wants more attention.^^ But If you want, I' m willing to try to contribute to the rom
PS. I'm sorry for my bad English and hope its understandable, but outside from here you can talk to me in German ^^
If you want to help the AOSP experience on our phones the best place to do it is with the CyanogenMod guys. You'll find pretty much everything based on AOSP (including people that port Vanilla AOSP and AOKP) is using a CM kernel.
They're likely working on the merge now in terms of getting CM10.1 out (with Android 4.2) but most of our CM guys are pretty burned out on working with Samsung's subpar reference material to get basic stuff working (mostly HWC). If you think you could help with this, this would be provide a massive boost to the whole community that want to run these phones on an AOSP based ROM and they would be very grateful.
Gotta warn you though it sounds like it'll be an uphill struggle to get the rest of the stuff working right; unless Samsung release some decent sources for HWC.
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
andy572 said:
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
Click to expand...
Click to collapse
Wish i could help (just started learning JAVA ) ! gl with this awesome project
Nice to see you here, I remember you from the P500 forums.
Xda user krarvind should be able to give you some useful hints, you will have to contact him through the RD forum as his pm is locked down, or I could possibly put him in contact with you
slaphead20 said:
Xda user krarvind should be able to give you some useful hints, you will have to contact him through the RD forum as his pm is locked down, or I could possibly put him in contact with you
Click to expand...
Click to collapse
Thank you, it would be nice if you can contact him
andy572 said:
Thank you, it would be nice if you can contact him
Click to expand...
Click to collapse
Ok, will mention it to him
andy572 said:
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
Click to expand...
Click to collapse
How it's going forward?
Maybe it could be useful to publish the github link when it's ready and some more information like staus, on first post
In the next days I have some trouble with my exams ( in two weeks I'm completely finished with my studies ^^) but I think if there is something to do I'll find some time to work on.
Good Luck Dude~
I haven't tried AOSP yet.
Hope someday i can give it a go.:silly:
hop3l3ss1990 said:
How it's going forward?
Maybe it could be useful to publish the github link when it's ready and some more information like staus, on first post
In the next days I have some trouble with my exams ( in two weeks I'm completely finished with my studies ^^) but I think if there is something to do I'll find some time to work on.
Click to expand...
Click to collapse
current state:
- patched android/build so we can compile the kernel within the main compile process
- patched android/build main.mk file so we can use OpenJDK or Oracle JDK
- added android/vendor/aokp and android/vendor/samsung tree from AOKP (its the most useful directory structure)
- added android/hardware from AOKP so we have all that Exynos things that are needed, even by AOSP
- modified android/frameworks/native/include so a OMX Plugin header can be found
- modified android/libhardware and patched gralloc module
currently it compiles to the Webkit library, most of all apps, libs and binaries are building without errors - the next problem
to solve is the PRODUCT_COPY_FILES ****: nothing of proprietary files are copied to the android/out directory, seems like
a bug in android/build too.
For only 2 days trying to compile to the end without errors its a very good cut
here we go: it compiles to the end and a flashable "JOP40" zip could be created
tryed to flash, but it gives errors in CWM: have to remove the recovery folder and the recovery.sh file from etc folder in the ota zip file, but it doesnt boot up - got a black screen only.
do we need a new or patched kernel instead the CM10 smdk421x one?
Well does it have all the closed source libraries fron the phone? If not, it wont boot. Dont think i am calling you stupid, you obviously know what you are doing, but maybe you forgot. Idk. Check that. Try running a log cat and debug that.
Sent from my GT-I9300 using xda premium
b-eock said:
Well does it have all the closed source libraries fron the phone? If not, it wont boot. Dont think i am calling you stupid, you obviously know what you are doing, but maybe you forgot. Idk. Check that. Try running a log cat and debug that.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thanks for the hint, yes i have all files included - i cant connect to adb, i see only small colored point on the top left side and a sensor
is red blinking (the one to the right of the speaker.
That would be the proximity sensor near the top front speaker. Cant connect, adb binary in /system/bin or xbin?
Sent from my GT-I9300 using xda premium
EDIT: We got it! It boots. But some things like RIL and audio are not working, but we'll get this sorted out soon.
Official thread here: http://forum.xda-developers.com/opt...opment/rom-cyanogenmod-12-1-lg-l3-ii-t3297897Hey guys! It seems like Caio has left the "scene", and we're left with CM11... Is there anyone able to "take over" the development of CM12 for E430? I know a little bit, but I can't do it myself....
Alright, what do we have?
A local manifest: https://github.com/TeamVee/android_.repo_local_manifests/tree/cm-12.1 that includes:
A device tree for CM11: https://github.com/TeamVee/android_device_lge_vee3
Vendor files for CM11: https://github.com/TeamVee/android_vendor_lge
Kernel for KitKat: https://github.com/TeamHackLG/lge-kernel-lproj
Display CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_display
Media CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_media
Shared L1/L3/L7 II files for CM12.1: https://github.com/TeamVee/android_device_lge_vee-common/tree/cm-12.1
We also have a build of CM12.1 recovery for E430 by me. Nevermind, broken.
L5's device tree for CM12.1: https://github.com/aidasaidas75/android_device_lge_e610
L5's vendor propretiary files for CM12.1: https://github.com/aidasaidas75/proprietary_vendor_lge/tree/cm-12.1-new/e610
What do we probably need?
A device tree for CM12.1 for L3 IINot needed.
Vendor files for CM12.1 for L3 IINot needed.
Lollipop kernel.Not needed.
We need a skilled developer/group of developer to do this. Anyone willing to participate? Any help is appreciated
Some more details: when I build CM12.1, it stops after building surfaceflinger. If you got any questions, ask me
Feel free to join me at the IRC channel for a little mindstorm: http://webchat.quakenet.org/?channels=teamvee
EDIT: I managed to build CM12.1 for LG L3 II, but I don't know if it's working or not - download here and tell me: https://www.androidfilehost.com/?fid=24345424848488130
Everyone, if you can help us create CM12.1, PM me your Telegram username (a great IM), I'll add you to a group chat. @aidasaidas75 @IGGYVIP and other devs are welcome.
dadziokPL said:
Hey guys! It seems like Caio has left the "scene", and we're left with CM11... Is there anyone able to "take over" the development of CM12 for E430? I know a little bit, but I can't do it myself....
Alright, what do we have?
A local manifest: https://github.com/TeamVee/android_.repo_local_manifests/tree/cm-12.1 that includes:
A device tree for CM11: https://github.com/TeamVee/android_device_lge_vee3
Vendor files for CM11: https://github.com/TeamVee/android_vendor_lge
Kernel for KitKat: https://github.com/TeamHackLG/lge-kernel-lproj
Display CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_display
Media CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_media
We also have a build of CM12.1 recovery for E430 by me. It's the only thing we can build with the local manifest. Download here: https://mega.nz/#!Io0xxBrR!gCin0V8pDZ_-PqAGTC05PfUEWTbdLhgqdBBMjnBrhdI (I would put it in the attachments, but it's 0.43 MB too big... Dammit :/
What do we probably need?
A device tree for CM12.1
Vendor files for CM12.1
Lollipop kernel.
We need a skilled developer/group of developer to do this. Anyone willing to participate? Any help is appreciated
Some more details: when I build CM12.1, it stops after building surfaceflinger. If you got any questions, ask me
Feel free to join me at the IRC channel for a little mindstorm: http://webchat.quakenet.org/?channels=teamvee
Click to expand...
Click to collapse
First you forgeted https://github.com/TeamVee/android_device_lge_vee-common and second i will still here if anyone need, i builded CM12.1 but, without any reason, the ROM not boot, but i not tried again.
Possible, maybe, i try to build this again after update of MK.
And my last TWRP is from CM12.1
Caio99BR said:
First you forgeted https://github.com/TeamVee/android_device_lge_vee-common and second i will still here if anyone need, i builded CM12.1 but, without any reason, the ROM not boot, but i not tried again.
Possible, maybe, i try to build this again after update of MK.
And my last TWRP is from CM12.1
Click to expand...
Click to collapse
Yeah, it's that recovery I built Also, I can't test ROMs for L3 II anymore, I changed to Windows Phone But I think my cousin still has my old L3 II. I'll see. BTW I got a new PC, with a quad-core Intel Core i5-4460, and I set up a VM on it, so can build and build and build BTW You don't have to build, it's not building...
I can test anything I've got dev phone e430 and not scared of bricks. So dangerous builds send to me first before you flash yourself new paper weight ...
Caio where did you get drivers for kk ? What device ? Does it have lollipop?
Also I'm not sure if possible to get lollipop working at all since bootloader will need upgrade too :/
IGGYVIP said:
I can test anything I've got dev phone e430 and not scared of bricks. So dangerous builds send to me first before you flash yourself new paper weight ...
Caio where did you get drivers for kk ? What device ? Does it have lollipop?
Also I'm not sure if possible to get lollipop working at all since bootloader will need upgrade too :/
Click to expand...
Click to collapse
I'm a noob. Explain to me, why will the bootloader need an upgrade? It worked fine from 4.1 to 4.4. Has Lollipop brought some new kinda... thing? I was also wondering how Caio got the drivers... And have you tried that recovery for CM12.1? Is it working? I can't test myself since I don't have that phone anymore. Technically I do, but I can't brick it.
Need more info and need a dev
dadziokPL said:
I'm a noob. Explain to me, why will the bootloader need an upgrade? It worked fine from 4.1 to 4.4. Has Lollipop brought some new kinda... thing? I was also wondering how Caio got the drivers... And have you tried that recovery for CM12.1? Is it working? I can't test myself since I don't have that phone anymore. Technically I do, but I can't brick it.
Click to expand...
Click to collapse
The bootloader I'm not 100% sure but all older devices needed bootloader upgrade before they booted into lollipop from kk.
Something about secure boot and the new way it handles things.
Not tested the recovery yet but no point yet really
first we need more info on what we stand on in terms of bootloader / drivers
Caio99BR are you here ?
What device did you use as base for cm11 on L3II ?
Also I think this phone has already done very big jump with 4.4.4 and running over 150% intended level.
Lets face it Lollipop will never be stable enough to be daily driver specially that making custom lollipop kernel is near impossible without proper sources ... And stock one (still not existing lollipop one) will be super slow with no useful functions.
I would like to see it happen but it will take pain and broken fingers from hitting keyboards
I'm just not sure if it makes sense since screen resolution is so low and general hardware is not ready for functions brought by 5.1
Basically there will be more pain than gain good for side project but not really something for public
4.4.4 on it is great and I think it should gracefully get old here with all the tweaks we managed
IGGYVIP said:
The bootloader I'm not 100% sure but all older devices needed bootloader upgrade before they booted into lollipop from kk.
Something about secure boot and the new way it handles things.
Not tested the recovery yet but no point yet really
first we need more info on what we stand on in terms of bootloader / drivers
Caio99BR are you here ?
What device did you use as base for cm11 on L3II ?
Also I think this phone has already done very big jump with 4.4.4 and running over 150% intended level.
Lets face it Lollipop will never be stable enough to be daily driver specially that making custom lollipop kernel is near impossible without proper sources ... And stock one (still not existing lollipop one) will be super slow with no useful functions.
I would like to see it happen but it will take pain and broken fingers from hitting keyboards
I'm just not sure if it makes sense since screen resolution is so low and general hardware is not ready for functions brought by 5.1
Basically there will be more pain than gain good for side project but not really something for public
4.4.4 on it is great and I think it should gracefully get old here with all the tweaks we managed
Click to expand...
Click to collapse
Ohh, secure boot, alright. I see.
I heard that Lollipop actually runs better than KitKat, and it was optimized for devices with 512 MB of RAM.
At least we can try and get it to build. We can build a recovery, which is a first step according to the porting wiki
So, I was right, we need device files, vendor files, and a kernel for Lollipop?
If Caio could tell us where he got the files for KitKat, we could do something....
IGGYVIP said:
I can test anything I've got dev phone e430 and not scared of bricks. So dangerous builds send to me first before you flash yourself new paper weight ...
Caio where did you get drivers for kk ? What device ? Does it have lollipop?
Also I'm not sure if possible to get lollipop working at all since bootloader will need upgrade too :/
Click to expand...
Click to collapse
First only the Adreno is not updated, because of vsync is broken and new Adreno Blobs use hwcomposer and this is broken because vsync. When i tried to test in KK with new Adreno Blobs this happened:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Second from L5, and yes but @aidasaidas75 confused all commits, and not said the recipe to anyone.
And last i have thought this but no way to change this, the display driver of bootloader is hard edited by LG, yes i tried.
Note: No one build can make a brick of device, only if fstab is edited
dadziokPL said:
I'm a noob. Explain to me, why will the bootloader need an upgrade? It worked fine from 4.1 to 4.4. Has Lollipop brought some new kinda... thing? I was also wondering how Caio got the drivers... And have you tried that recovery for CM12.1? Is it working? I can't test myself since I don't have that phone anymore. Technically I do, but I can't brick it.
Click to expand...
Click to collapse
And not say drivers, say vendor blobs or kernel drivers, this not is windows
IGGYVIP said:
The bootloader I'm not 100% sure but all older devices needed bootloader upgrade before they booted into lollipop from kk.
Something about secure boot and the new way it handles things.
Not tested the recovery yet but no point yet really
first we need more info on what we stand on in terms of bootloader / drivers
Caio99BR are you here ?
What device did you use as base for cm11 on L3II ?
Also I think this phone has already done very big jump with 4.4.4 and running over 150% intended level.
Lets face it Lollipop will never be stable enough to be daily driver specially that making custom lollipop kernel is near impossible without proper sources ... And stock one (still not existing lollipop one) will be super slow with no useful functions.
I would like to see it happen but it will take pain and broken fingers from hitting keyboards
I'm just not sure if it makes sense since screen resolution is so low and general hardware is not ready for functions brought by 5.1
Basically there will be more pain than gain good for side project but not really something for public
4.4.4 on it is great and I think it should gracefully get old here with all the tweaks we managed
Click to expand...
Click to collapse
I think you wanted to say the kernel and ramdisk.
Use "@" i will see this in seconds
I used L5/L7/MSM7x27a-Common/and some others msm7x27a devices
I think this cant be able to daily usage, but with DualBootPatcher, all will be possible.
I have through this too, but the Android Wear saved us , and if this work is a good progess, btw the last.
dadziokPL said:
Ohh, secure boot, alright. I see.
I heard that Lollipop actually runs better than KitKat, and it was optimized for devices with 512 MB of RAM.
At least we can try and get it to build. We can build a recovery, which is a first step according to the porting wiki
So, I was right, we need device files, vendor files, and a kernel for Lollipop?
If Caio could tell us where he got the files for KitKat, we could do something....
Click to expand...
Click to collapse
Device tree, vendor files and kernel need someone with experience to this, like @aidasaidas75, but him left L5 CM12 support.
My english is bad and my keyboard too
Sorry for mistypes and long post.
Topic subscript agan of right way now!
---------- Post added at 10:54 PM ---------- Previous post was at 10:52 PM ----------
See DualBoot Custom ROMs on the LG L3 II (via PC) in TOP FORUM DISCUSSIONS -------------------->
Just for case
Caio99BR said:
First only the Adreno is not updated, because of vsync is broken and new Adreno Blobs use hwcomposer and this is broken because vsync. When i tried to test in KK with new Adreno Blobs this happened:
Second from L5, and yes but @aidasaidas75 confused all commits, and not said the recipe to anyone.
And last i have thought this but no way to change this, the display driver of bootloader is hard edited by LG, yes i tried.
Note: No one build can make a brick of device, only if fstab is edited
And not say drivers, say vendor blobs or kernel drivers, this not is windows
I think you wanted to say the kernel and ramdisk.
Use "@" i will see this in seconds
I used L5/L7/MSM7x27a-Common/and some others msm7x27a devices
I think this cant be able to daily usage, but with DualBootPatcher, all will be possible.
I have through this too, but the Android Wear saved us , and if this work is a good progess, btw the last.
Device tree, vendor files and kernel need someone with experience to this, like @aidasaidas75, but him left L5 CM12 support.
My english is bad and my keyboard too
Sorry for mistypes and long post.
Topic subscript agan of right way now!
---------- Post added at 10:54 PM ---------- Previous post was at 10:52 PM ----------
See DualBoot Custom ROMs on the LG L3 II (via PC) in TOP FORUM DISCUSSIONS -------------------->
Just for case
Click to expand...
Click to collapse
Thanks for clearing up some stuff Caio!
Ok, so here are propertiary files for L5(for CM12.1): https://github.com/aidasaidas75/proprietary_vendor_lge/tree/cm-12.1-new/e610
And here are device blobs for L5(also for CM12.1): https://github.com/aidasaidas75/android_device_lge_e610
Let's see what we can do, we got @IGGYVIP, he knows a lot, and he pretty much started everything with modding L3 II, we can bring CM12.1 for our L3 II together!
I am the orders! e-e
Wow! Let's see what we can do, I can help them in some respects too, and I can test whatever they want. I'm not afraid to have a paperweight, and I know it will be worth it. If they need a Tester, I am the orders!
It's great idea to build CM12 on LG L3 II, and if we need testers, I have working E430 phone, and I can test unstable versions of this ROM.
MinusThousand said:
It's great idea to build CM12 on LG L3 II, and if we need testers, I have working E430 phone, and I can test unstable versions of this ROM.
Click to expand...
Click to collapse
Okay, but we need to get it to build first. It won't build, there are errors, we need a proper device tree and proprietary blobs for CM12.1.
dadziokPL said:
Hey guys! It seems like Caio has left the "scene", and we're left with CM11... Is there anyone able to "take over" the development of CM12 for E430? I know a little bit, but I can't do it myself....
Alright, what do we have?
A local manifest: https://github.com/TeamVee/android_.repo_local_manifests/tree/cm-12.1 that includes:
A device tree for CM11: https://github.com/TeamVee/android_device_lge_vee3
Vendor files for CM11: https://github.com/TeamVee/android_vendor_lge
Kernel for KitKat: https://github.com/TeamHackLG/lge-kernel-lproj
Display CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_display
Media CAF for CM12.1: https://github.com/msm7x27a/android_hardware_qcom_media
Shared L1/L3/L7 II files for CM12.1: https://github.com/TeamVee/android_device_lge_vee-common/tree/cm-12.1
We also have a build of CM12.1 recovery for E430 by me. It's the only thing we can build with the local manifest. Download here: https://mega.nz/#!Io0xxBrR!gCin0V8pDZ_-PqAGTC05PfUEWTbdLhgqdBBMjnBrhdI (I would put it in the attachments, but it's 0.43 MB too big... Dammit :/
L5's device tree for CM12.1: https://github.com/aidasaidas75/android_device_lge_e610
L5's vendor propretiary files for CM12.1: https://github.com/aidasaidas75/proprietary_vendor_lge/tree/cm-12.1-new/e610
What do we probably need?
A device tree for CM12.1 for L3 II
Vendor files for CM12.1 for L3 II
Lollipop kernel.
We need a skilled developer/group of developer to do this. Anyone willing to participate? Any help is appreciated
Some more details: when I build CM12.1, it stops after building surfaceflinger. If you got any questions, ask me
Feel free to join me at the IRC channel for a little mindstorm: http://webchat.quakenet.org/?channels=teamvee
Click to expand...
Click to collapse
Actually device l5 is not set correctly in your tread tbh almost all l5 dependencies set wrong in op even display caf
aidasaidas75 said:
Actually device l5 is not set correctly in your tread tbh almost all l5 dependencies set wrong in op even display caf
Click to expand...
Click to collapse
Yo dude long time no see
Any chance you could make git group with correct base set of whats there that can be used to build for vee3 ? (I'm aware there will be a lot to do and missing stuffs but nice set from you would be a great start )
IGGYVIP said:
Yo dude long time no see
Any chance you could make git group with correct base set of whats there that can be used to build for vee3 ? (I'm aware there will be a lot to do and missing stuffs but nice set from you would be a great start )
Click to expand...
Click to collapse
I started building again so it might be lucky day for e430
@aidasaidas75 happy days pure cm or else ?
@freeusername
Yo santy
Would you be interested in the challenge of kernel ?
We could really use your experience with custom building this
MERRY CHRISTMAS ALL
IGGYVIP said:
@aidasaidas75 happy days pure cm or else ?
@freeusername
Yo santy
Would you be interested in the challenge of kernel ?
We could really use your experience with custom building this
MERRY CHRISTMAS ALL
Click to expand...
Click to collapse
Kernel is easy peazy lemon squizy. I was hooked on csgo but now synched cm12.1 and and started messing around it . I have new git and started everything from scratch for e610 and e430
aidasaidas75 said:
Kernel is easy peazy lemon squizy. I was hooked on csgo but now synched cm12.1 and and started messing around it . I have new git and started everything from scratch for e610 and e430
Click to expand...
Click to collapse
Cool, seems like the Optimus L series won't die so quick! Thanks to people like you, IGGYVIP or Caio the L3 II is usable. My Lumia 535 was sent to repair a MONTH ago, and they are still waiting for parts to arrive. I got a substitute device from my carrier, and surprise surprise, it's the L3 II. I know it's not my device, and that I'll have to pay if they figure out that I installed a custom ROM, but I couldn't resist. I installed CM11. The stock ROM is complete ****, it's laggy and unusable. I don't know for how much longer, but I can test. And when I'll have to return the L3 II, my cousin that got my old L3 II from me said that he'll test for me
I created this thread to encourage people to keep making ROMs for this phone, and it seems like we got our best developers back! I'll help you as much as I can, but I'm not as advanced as you guys! Although I learned how to build Cyanogenmod from source, and I got a great PC, building CM11(with cache enabled)on a VM took not even an hour! If you want me to do something, just tell me, I got lots of free time, and I'll do what I can to help!
Good luck to y'all, let's see what we can make together!
dadziokPL said:
Cool, seems like the Optimus L series won't die so quick! Thanks to people like you, IGGYVIP or Caio the L3 II is usable. My Lumia 535 was sent to repair a MONTH ago, and they are still waiting for parts to arrive. I got a substitute device from my carrier, and surprise surprise, it's the L3 II. I know it's not my device, and that I'll have to pay if they figure out that I installed a custom ROM, but I couldn't resist. I installed CM11. The stock ROM is complete ****, it's laggy and unusable. I don't know for how much longer, but I can test. And when I'll have to return the L3 II, my cousin that got my old L3 II from me said that he'll test for me
I created this thread to encourage people to keep making ROMs for this phone, and it seems like we got our best developers back! I'll help you as much as I can, but I'm not as advanced as you guys! Although I learned how to build Cyanogenmod from source, and I got a great PC, building CM11(with cache enabled)on a VM took not even an hour! If you want me to do something, just tell me, I got lots of free time, and I'll do what I can to help!
Good luck to y'all, let's see what we can make together!
Click to expand...
Click to collapse
Wow, you will gonna have a bad time if something goes wrong with you substitute device , just for case not test the CM12 builds, and i updated device tree (vee-common) and local manifests, these are the Display and Media repos used in CM12.1 by @aidasaidas75:
https://github.com/SlimLP-Y300/android_hardware_qcom_display-caf
https://github.com/SlimLP-Y300/hardware_qcom_media
Just for case (i like this phrase ), my inspiration is people like you and these awesome devs who cares for keep this device alive (but sometimes get crazy and disappear sometimes because they are also people ).
Note: i will be still here, just for case :silly::victory:
Caio99BR said:
Wow, you will gonna have a bad time if something goes wrong with you substitute device , just for case not test the CM12 builds, and i updated device tree (vee-common) and local manifests, these are the Display and Media repos used in CM12.1 by @aidasaidas75:
https://github.com/SlimLP-Y300/android_hardware_qcom_display-caf
https://github.com/SlimLP-Y300/hardware_qcom_media
Just for case (i like this phrase ), my inspiration is people like you and these awesome devs who cares for keep this device alive (but sometimes get crazy and disappear sometimes because they are also people ).
Note: i will be still here, just for case :silly::victory:
Click to expand...
Click to collapse
These are for Huawei Y300/G510. Are you sure these are gonna work?
Also, my carrier valued the phone at around 25 euro, If they figure out, I'll just have to pay it, but I can keep the phone forever, no big deal
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
Kernel source code for Mi Note 10/Mi CC9 Pro is now available on GitHub.
<https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/tucana-p-oss>
thanks
Nice! I will try to play around with building a rom... Hope I won't brick my phone.
h8Aramex said:
Nice! I will try to play around with building a rom... Hope I won't brick my phone.
Click to expand...
Click to collapse
Did you make any progress?
iSonik said:
Did you make any progress?
Click to expand...
Click to collapse
I spent quite some time on it but sadly the kernel source is just one tiny bit of the recipe.
You need a device AND vendor tree as well, and as far as I can tell you just can't rip them out of a device or anything. They just magically "appear" online. Ie.: I think someone leaks them... I don't know. I tried to talk with devs, tried various forums and communities but no dice. Wish I had a solution, I am afraid the next Android 10 update won't be too good for this device either - other people who received the Android 10 updates for Xiaomi are already complaining.
h8Aramex said:
I spent quite some time on it but sadly the kernel source is just one tiny bit of the recipe.
You need a device AND vendor tree as well, and as far as I can tell you just can't rip them out of a device or anything. They just magically "appear" online. Ie.: I think someone leaks them... I don't know. I tried to talk with devs, tried various forums and communities but no dice. Wish I had a solution, I am afraid the next Android 10 update won't be too good for this device either - other people who received the Android 10 updates for Xiaomi are already complaining.
Click to expand...
Click to collapse
So did you try compiling a custom Kernel? Also we could, instead of using the device Tree, try to Port PHHusons GSI to our device. i already started with that, trying to create overlay and so on. Alot of thinks are already working with that LOS build.
So my idea is to debloat a GSi ( so only things needed for Mi Note 10 are included) and then also using a custom kernel
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