Related
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.
Does anyone know if a cyanogenmod rom for mipad 2 is available?
Envoyé de mon Mi-4c en utilisant Tapatalk
+ 1
Dear Developers and Hackers of XDA,
I just bought this tablet. I looked around on the MIUI forum for MI Pad 2 and see that there are ways to root a developer MIUI ROM for this tablet. I also see that there are also instructions to unlock the bootloader and install a custom recovery. I am big fan of Cyanogemod and am hoping to have it on the tablet. Has anybody tried and/succeeded to port Cyanogenmod to this tablet?
Hoping for the best
Sincerely
dspati
Hi dEvasEnApati I'm in your situation! I hope to recive news as soon as possible because i want to install cyano!
Xda dev have you got some news?
Hi,
Following the instructions from the miui forum I managed to unlock the bootloader, root , install TWRP and AOSP rom. I was wondering what are the requirements to have a cyanogen mod for it? Are there CMs for devices with intel x86_64 hardware?
I'll get my mipad 2 soon! I think in a week or two then I'll Start heavy development on it ? i think of aosp is possible cm will be possible too :] I'll keep u guys updated
Hi Nailyouh,
Thank you very much for doing this!
Maybe this may help: As paul_ro21 mentioned, a working AOSP rom, which was most probably developed by Xiaomi is available on the miui forums. I have it on my mi pad 2 as well and it's working fine. I am looking forward to a CM rom for this tablet and I will be happy to help with testing!
Sincerely
dspati
Nailyouh said:
I'll get my mipad 2 soon! I think in a week or two then I'll Start heavy development on it �� i think of aosp is possible cm will be possible too :] I'll keep u guys updated
Click to expand...
Click to collapse
Nailyouh said:
I'll get my mipad 2 soon! I think in a week or two then I'll Start heavy development on it �� i think of aosp is possible cm will be possible too :] I'll keep u guys updated
Click to expand...
Click to collapse
Waiting for your work on CM
Im too tired with stupid MIUI on this awesome tablet :
Stupid ram management, it has 2gb ram but it cannot run multi-tasking !
Im facing a big Problem i was not aware about..the Kernel of the MiPad2 is not open source so we are pretty f**ed by xiaomi. In fact the Kernel source has to be released but xiaomi don't care about Copyright infringements. I regret the decision buying this Tab. I like the Dualboot thingy and the aosp Rom runs smooth as butter but without the source we'll stuck on 5.1.1. really sad if you ask me, the Tablet is really beautyful and I love the outstanding Display. I'll try to figure around with the kernel from the aosp Rom next week I'll keep u informend and will make a thread if I suceed.
Cheers
Naily
Nailyouh said:
Im facing a big Problem i was not aware about..the Kernel of the MiPad2 is not open source so we are pretty f**ed by xiaomi. In fact the Kernel source has to be released but xiaomi don't care about Copyright infringements. I regret the decision buying this Tab. I like the Dualboot thingy and the aosp Rom runs smooth as butter but without the source we'll stuck on 5.1.1. really sad if you ask me, the Tablet is really beautyful and I love the outstanding Display. I'll try to figure around with the kernel from the aosp Rom next week I'll keep u informend and will make a thread if I suceed.
Cheers
Naily
Click to expand...
Click to collapse
Too sad, I know this will happens becoz Xiaomi released just some models ( Mi4 ... )
Hope You will find a way to solve this
The hardware is awesome, but the OS is SUCK !
Any news?
any news?
@Vihru there is some progress in the MIUI forums, I'm using MIRU 7 and currently waiting MIRU 8 to finish downloading. It's like a whole new tablet, amazing what they've done with it
Remix 2.0: http://en.miui.com/thread-329758-1-1.html
MIRU 7: http://en.miui.com/thread-325531-1-1.html
MIRU 8: http://en.miui.com/thread-353077-1-1.html
If anyone on MI Forum as registered, please assist here:
http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=424803&pid=7862023
See if I gave him all correct links and processes..
vdbhb59 said:
If anyone on MI Forum as registered, please assist here:
http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=424803&pid=7862023
See if I gave him all correct links and processes..
Click to expand...
Click to collapse
Is this good news for you:
http://en.miui.com/thread-411400-1-1.html
CyanogenMod 13 x86 6.0.1 on MiPad 2 Intel x5 z-8500
xposed will work too. Right now the audio is under construction (not working, yet).
Xiaomi added kernel souces for Mi Pad 2
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/latte-l-oss
datorprofessor said:
Is this good news for you:
http://en.miui.com/thread-411400-1-1.html
CyanogenMod 13 x86 6.0.1 on MiPad 2 Intel x5 z-8500
xposed will work too. Right now the audio is under construction (not working, yet).
Click to expand...
Click to collapse
Thanks mate.
Checking it.
Kernel source is out (github)
Nailyouh said:
Im facing a big Problem i was not aware about..the Kernel of the MiPad2 is not open source so we are pretty f**ed by xiaomi. In fact the Kernel source has to be released but xiaomi don't care about Copyright infringements. I regret the decision buying this Tab. I like the Dualboot thingy and the aosp Rom runs smooth as butter but without the source we'll stuck on 5.1.1. really sad if you ask me, the Tablet is really beautyful and I love the outstanding Display. I'll try to figure around with the kernel from the aosp Rom next week I'll keep u informend and will make a thread if I suceed.
Cheers
Naily
Click to expand...
Click to collapse
Kernel source is now out on github. Any thoughts about it?
Hi guys, does anyone know where I can get stock ROM for ZTE Obsidian?
plectr said:
Hi guys, does anyone know where I can get stock ROM for ZTE Obsidian?
Click to expand...
Click to collapse
Or any custom ROM? Just any ROM?
The source code was published on http://opensource.ztedevice.com/. Is it "too hard" to make ROM out of this? Can I do it without special skills, just following a tutorial?
+1 ...
plectr said:
Hi guys, does anyone know where I can get stock ROM for ZTE Obsidian?
Click to expand...
Click to collapse
+1 any provider T-mobile or metroPcs...
Any luck? I'm in need of this myself.
Me, too! (+1)
Please, will someone with a proper kit dump the ROM? I, uh... over-rooted mine. But all is not lost! I still can get to recovery mode and it has flashing options! (With device in OFF state, hold VOL. UP + POWER + HOME. Navigate to RECOVERY MODE with VOL. UP, then VOL. DN to select. The green "sick Android" logo with a "!" appears. Press VOL. UP + POWER for approx. 5 seconds, then release both simultaneously. This should display all the recovery options.) We would be eternally grateful, and I promise lots of :good:'s! Because really, let's be honest: we're all here because we want one of those nifty "SENIOR MEMBER" badges. When I get one, I'm gonna have it tatooed on my arm. (Everyone knows chicks dig rooting skills.) In the meantime, I'll be trying to learn how to compile the source code from the link another member posted above...
Hey you guys... Really need this too... any progress?
Any news???
i have it but? how do y get it out of the phone
help do that and there y will have it
thanks mark
I'm a little concerned with the compile effort after carefully reading ZTE's Open-Source policies... It seems the "ROM" download for the Z820 found on their website contains only the open-source portions of the firmware. Not only am I having difficulty getting a "good" download with my backwoods Internet connection (3 attempts-all bad,) I'm afraid after compiling that I'll only have a partial OS ROM. Does anyone skilled (read: not a junior member like me) know if there's proprietary first or third party code in most OEM stock ROM's? If so, would those portions be available online to download and place in the proper partitions? ZTE's very specific wording spooked me... I mean, I ain't scared to give 'er a go as-is, but I'm curious. The thing's just collecting dust now...
Sent from my C6740 using XDA-Developers mobile app
Now I'm curious. I might have the ability to grab this little device. Let me have a look at the source code first, get my bearings, and I'll see what I can find. I've got a lot going on, so I might need a reminder or two... Hope you guys like android forums though, that's where I tend to linger
---------- Post added at 06:10 AM ---------- Previous post was at 06:05 AM ----------
Right, so I just found the sources. Downloading both the TMO and MPCS sources and will diff them tomorrow. That being said; they have only released the kernel source. Which is AMAZING considering, but not everything for a ROM. With this, I could make a custom ROM, figure out root (bootloader is covered luckily), and more! What I'm saying is; I'll give it a shot. I'll update this thread with developments as they come
I need this also!!!! PLEASE HELP ME!!! LOL THANK YOU!
crutchcorn said:
Now I'm curious. I might have the ability to grab this little device. Let me have a look at the source code first, get my bearings, and I'll see what I can find. I've got a lot going on, so I might need a reminder or two... Hope you guys like android forums though, that's where I tend to linger
---------- Post added at 06:10 AM ---------- Previous post was at 06:05 AM ----------
Right, so I just found the sources. Downloading both the TMO and MPCS sources and will diff them tomorrow. That being said; they have only released the kernel source. Which is AMAZING considering, but not everything for a ROM. With this, I could make a custom ROM, figure out root (bootloader is covered luckily), and more! What I'm saying is; I'll give it a shot. I'll update this thread with developments as they come
Click to expand...
Click to collapse
Just to keep you guys informed; I tried downloading both of the sources and couldn't get their tar.gz to extract completely in Linux - meaning we're totally stuck and that's it.
Kidding.
E-mailed the guys over there and after a few days they finally got back to me letting me know the site was down for maintenance and to try again in a few days. Doesn't sound too promising, sure, but at least we know that we don't have to post a formal legal request like the guys over at the Fire Phone threads had to do. I'll get that source for ya.
crutchcorn said:
Just to keep you guys informed; I tried downloading both of the sources and couldn't get their tar.gz to extract completely in Linux - meaning we're totally stuck and that's it.
Kidding.
E-mailed the guys over there and after a few days they finally got back to me letting me know the site was down for maintenance and to try again in a few days. Doesn't sound too promising, sure, but at least we know that we don't have to post a formal legal request like the guys over at the Fire Phone threads had to do. I'll get that source for ya.
Click to expand...
Click to collapse
FYI I already have a CWM Recovery compiled and ready to go for this device however thanks to Securelock and the 101 error any attempts at flashing via dd and no access to fastboot (tried zero'ing out the recovery partition to try to force bootloader) there is no way currently to flash to the device... I've already got a CM 12.1 build ported over also... Gonna work on a custom kernel next but only if we can get past this Securelock issue
I may be a junior member but trust I am a seasoned developer and have worked on roms such as the CM 10 port for the LG Optimus and F3 / F6.
BBQ Linux all the way!
xerolath said:
FYI I already have a CWM Recovery compiled and ready to go for this device however thanks to Securelock and the 101 error any attempts at flashing via dd and no access to fastboot (tried zero'ing out the recovery partition to try to force bootloader) there is no way currently to flash to the device... I've already got a CM 12.1 build ported over also... Gonna work on a custom kernel next but only if we can get past this Securelock issue
I may be a junior member but trust I am a seasoned developer and have worked on roms such as the CM 10 port for the LG Optimus and F3 / F6.
BBQ Linux all the way!
Click to expand...
Click to collapse
I'm out! Xero got y'all covered
xerolath said:
FYI I already have a CWM Recovery compiled and ready to go for this device however thanks to Securelock and the 101 error any attempts at flashing via dd and no access to fastboot (tried zero'ing out the recovery partition to try to force bootloader) there is no way currently to flash to the device... I've already got a CM 12.1 build ported over also... Gonna work on a custom kernel next but only if we can get past this Securelock issue
I may be a junior member but trust I am a seasoned developer and have worked on roms such as the CM 10 port for the LG Optimus and F3 / F6.
BBQ Linux all the way!
Click to expand...
Click to collapse
I can't wait for you to fix the z820 .thanks bro
xerolath said:
FYI I already have a CWM Recovery compiled and ready to go for this device however thanks to Securelock and the 101 error any attempts at flashing via dd and no access to fastboot (tried zero'ing out the recovery partition to try to force bootloader) there is no way currently to flash to the device... I've already got a CM 12.1 build ported over also... Gonna work on a custom kernel next but only if we can get past this Securelock issue
I may be a junior member but trust I am a seasoned developer and have worked on roms such as the CM 10 port for the LG Optimus and F3 / F6.
BBQ Linux all the way!
Click to expand...
Click to collapse
We're fortunate to have your expertise, zerolath! That's why I love XDA! This thing's driving me nuts! It's the only 64-bit device I have until my Raspberry Pi 3 arrives, and I hate that I was careless and didn't back it up first! Rookie error. But I have learned: my LG Leon is backed up and well rooted! I had the same issue as crutchcorn did with the kernel source code DL. Got a unexpected zero bit at #### error with multiple DL's. I'm not experienced enough to attempt flashing just the kernel anyway. I hope there's a way around the SecureLock protection!
Back-up EVERYTHING. Compulsively! ?
Cruise Elroy said:
We're fortunate to have your expertise, zerolath! That's why I love XDA! This thing's driving me nuts! It's the only 64-bit device I have until my Raspberry Pi 3 arrives, and I hate that I was careless and didn't back it up first! Rookie error. But I have learned: my LG Leon is backed up and well rooted! I had the same issue as crutchcorn did with the kernel source code DL. Got a unexpected zero bit at #### error with multiple DL's. I'm not experienced enough to attempt flashing just the kernel anyway. I hope there's a way around the SecureLock protection!
Back-up EVERYTHING. Compulsively! ?
Click to expand...
Click to collapse
Aye mate. XDA and programmer centric forums and such are pretty snazzy. Great place for people of all walks of life to learn, laugh, and grow.
I hope you can solve this... I too have this phone bricked at home, after flashing official update from ZTE...
Thank you so much for helping us!
Hi all,
Relatively am a new developer, trying to build aosp got everything figured out (I hope). Blindly following some instructions and got device tree from old nougat branch in google git. Building takes more time or just hangs not sure what is happening..
Before you guys reply like you can't do that or this, I just expect a polite answers.
Refer below!
vasanthmes said:
Hi all,
Relatively am a new developer, trying to build aosp got everything figured out (I hope). Blindly following some instructions and got device tree from old nougat branch in google git. Building takes more time or just hangs not sure what is happening..
Before you guys reply like you can't do that or this, I just expect a polite answers.
Refer below!
Click to expand...
Click to collapse
Takes more thime then what?
Perhaps you should start with a known good configuration.
Elektroschmock said:
Takes more thime then what?
Perhaps you should start with a known good configuration.
Click to expand...
Click to collapse
OK. But am having errors in several areas after doing make otapackage.
Is there any good device tree, vendor, kernel to start with?
Because the one I got is from master branch from google git and of course that is from a nougat version.
BTW I'm having a old laptop with i5 and 4Gigs of Ram. Probably that's why it is taking more time. Also running Ubuntu 18 on VM which is storing on my external hard disk of 2 TB connected through USB 3.0..
Am just curious and exploring things & trying to learn.
Thinking of giving up building 9.0 ...since I'm new to this.. May be proceeding with existing builds like 7.x.x from google or cm15.1 ..
vasanthmes said:
OK. But am having errors in several areas after doing make otapackage.
Is there any good device tree, vendor, kernel to start with?
Because the one I got is from master branch from google git and of course that is from a nougat version.
BTW I'm having a old laptop with i5 and 4Gigs of Ram. Probably that's why it is taking more time. Also running Ubuntu 18 on VM which is storing on my external hard disk of 2 TB connected through USB 3.0..
Am just curious and exploring things & trying to learn.
Click to expand...
Click to collapse
4gb of ram is your culprit, I suggest 8gb or 16gb .
Building is RAM dependent , and it also requires a fast SSD. I don't build roms, but I read a lot ?
Using Google Cloud for building now. Its amazingly fast!!!!! :fingers-crossed:
My first lineage 15.1 build stuck on Google bootscreen..
Build is successful.
anybody knows how to get log or error?
vasanthmes said:
My first lineage 15.1 build stuck on Google bootscreen..
Build is successful.
anybody knows how to get log or error?
Click to expand...
Click to collapse
If you want to build a ROM, you need to search and read a lot! This has been answered literally thousands of time on xda. Just use the search button and you would find that as a first result :fingers-crossed:
All the best for building the ROMs!
Nitin
vasanthmes said:
My first lineage 15.1 build stuck on Google bootscreen..
Build is successful.
anybody knows how to get log or error?
Click to expand...
Click to collapse
Do an -eng build, then you can debug the boot process via ADB.
Did you extract the vendor blobs, or add a repository containing them?
Elektroschmock said:
Do an -eng build, then you can debug the boot process via ADB.
Did you extract the vendor blobs, or add a repository containing them?
Click to expand...
Click to collapse
Vendor blobs I think I did, let me check once I reach home.
Thanks for advice on -eng build and by the way as nitin said I will check how to debug as well.
Been trying to build on Google Compute Engine VM... Crazy fast and best for those who are building for first time..
-Vasanth
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