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.
It seems there has been no official TWRP releases since September despite 7.0/7.1 source dropping.
The last official build without major bugs is 3.0.2.0, BUT no support for decryption 7.X.
3.0.2.1 has major issues with EFS backups.... don't use it.
3.0.2.2 has significant issued with with 6.0 backups/restores.... don't use it.
So what's someone who is flashing between 6.0 and 7.1 to do? Well just compile their own.... so I did. With a lightly modded TWRP source everything seems to be working for the last week or so.
Get it here:
All I guarantee is it works for me.
Sorry, your link doesn't work.
Forbidden
You don't have permission to access /dho/9-Experimental-physics-lab/angler/TWRP 3.0.2.X.img on this server.
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.
DHO said:
It seems there has been no official TWRP releases since September despite 7.0/7.1 source dropping.
The last official build without major bugs is 3.0.2.0, BUT no support for decryption 7.X.
3.0.2.1 has major issues with EFS backups.... don't use it.
3.0.2.2 has significant issued with with 6.0 backups/restores.... don't use it.
So what's someone who is flashing between 6.0 and 7.1 to do? Well just compile their own.... so I did. With a lightly modded TWRP source everything seems to be working for the last week or so.
Get it here:
All I guarantee is it works for me.
Click to expand...
Click to collapse
This has already been done...
but thanks tho.
https://drive.google.com/file/d/0B2rPZYX0QKP-TjFnd09IWjJ1YTg/view
Colchiro said:
Sorry, your link doesn't work.
Forbidden
You don't have permission to access /dho/9-Experimental-physics-lab/angler/TWRP 3.0.2.X.img on this server.
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.
Click to expand...
Click to collapse
Sorry fixed.
Hi Guys,
I have found cm12.1 and cm13 for our Xperia P in a Webstite.
Cm12.1 is really stable and works like a charm.But Cm13 has more Bugs like Camera,Wlan etc.
Lets start
Installation - CyanogenMod 12.1
Next, you need the CyanogenMod ROM.zip, the appropriate GApps, and the corresponding boot.img - which also contains the Custom Recovery TWRP to flash and successfully boot the Android 5.1.1 based ROM. Copy the CyanogenMod 12.1 ROM.zip to Euner Xperia P, and reconnect it to your PC in fastboot mode, as described in the previous section. For the next step, the boot.img must be in your fastboot folder. Opens the input prompt and returns there
PHP:
Fastboot flash boot cm121_boot.img
on. Next, you reboot your Xperia P by either turning the device off and back on again. Or the command in the input prompt
PHP:
Fastboot reboot
Or use Flashtool for flashing of kernel
. Once the SONY label appears with the graphic of the CyanogenMod STE project, press the volume down and power button several times to reboot the device. Swiped at the start in the query to the right to allow changes to the system partition. Now select the menu item "Wipe> Advanced Wipe" and tick "System, Data, Cache" and "Android Secure" and confirm the selection by swiping again. To complete the installation, go back to the Install menu and navigate to the location where you previously copied the ROM and GApps. Flashes them one by one and reboots the Xperia P.
The first boat takes up to 10 minutes, and ends in the menu for the initial setup, as you are used to with a new device. Congratulations, you have successfully installed CyanogenMod on your Xperia P! Bold among you, can also try the
Installation - CyanogenMod 13
It is same as CM12.1
CyanogenMod 13, which is based on Android 6, but is still in an early development phase.
Credits
@Xperia-STE Team
@smartphone-guru.
I tried_ this version of cm12.1 its most stable than any other version but not very fluent in use.
But almost perfect for dailyuse
GAPPS error
I have flashed cm12.1 into my LT22i. But have an issue with GAPPS. Play store isn't lunching and it keeps closing up. Otherwise it's good rom, UI felt like butter
sz_ashik said:
I have flashed cm12.1 into my LT22i. But have an issue with GAPPS. Play store isn't lunching and it keeps closing up. Otherwise it's good rom, UI felt like butter
Click to expand...
Click to collapse
You have to install Gapps via cmw again. The best one is open gapps
CM12.1 Works perfectly!, I have not yet seen the first bug
jao6622 said:
CM12.1 Works perfectly!, I have not yet seen the first bug
Click to expand...
Click to collapse
is it better than cm11 final (m12)?
Hi, I gave to my brother my old Xperia P, and I wanted to upgrade to KK because is almost the most bug free (just A2DP not working that is important to me), and I wanted to know the bugs for lollipop if someone can give that information. Thanks!
Enviado desde mi Xperia Z2 mediante Tapatalk
Dagalur said:
is it better than cm11 final (m12)?
Click to expand...
Click to collapse
sorry , I don't have tested that rom :s
This ROM is old and newer build are already out but latest is 20161002 i think . There is link https://drive.google.com/drive/u/0/folders/0B4AOy62JMc5gaUpYbUFMVkdGRUk those are build by @CBNUKE i will download cm12.1 source and compile at least the latest source if it will even compile since i tried to fix cm13.0 and cannot make it to compile but i will try harder and maybe one day i will do it but for now i have holidays so i will compile cm12.1 hopefully. For now use CBNUKE build.
Bugs
Meloferz said:
Hi, I gave to my brother my old Xperia P, and I wanted to upgrade to KK because is almost the most bug free (just A2DP not working that is important to me), and I wanted to know the bugs for lollipop if someone can give that information. Thanks!
Enviado desde mi Xperia Z2 mediante Tapatalk
Click to expand...
Click to collapse
Camera Recording is Sometimes not working
A2DP totally not working
NFC not even recognized by system
but other things work.
---------- Post added at 10:21 PM ---------- Previous post was at 10:18 PM ----------
Dagalur said:
is it better than cm11 final (m12)?
Click to expand...
Click to collapse
Well its stable fast and usable for daily use but dont know if its faster but its good ROM.
---------- Post added at 10:32 PM ---------- Previous post was at 10:21 PM ----------
Dont expect that we will ever get CM13.0 on Nypon cause of hard building part and that BT is disabled because if its not u will get boot-loop.
i would need a dev that already ported a rom to help me with this.
Its not easy to port it.
Any help from a dev or porter is needed to make CM13.0 to work cannot do it on my own.
Good and bad news
First good news : i have managed to build lineage OS 13.0 and not bad news TWRP looks ugly bad text and the entire UI is not right how it should be and next problem rom is not bootable after kernel screen there is no boot animation just black screen forever . But i will try to fix it i updated TWRP to 3.0.2.0 and still the same UI problem so probably Kernel Issue but weird that i didnt even touch kernel source and still problem.
Thats it for now I will try to fix it.
And if anybody who have experience in this can help me i will be happy.
Maybe @CBNUKE will have spare time to help me with it.
Thanks.
Update on Development (Not yet working but close)
Found the problems source: I did forgot to patch the source on my first build so of course it cannot even boot. But now i little bit screwed my source code of lineage OS by trying to find solution to errors that popped out by applying patches.
So will re download source and hopefully after patches i will get working bootable ROM (Really Hopefully)
I will post a new Thread about it if i get at least basic stuff working.
And of course i will post the ROM itself if it will work.
And again any help from somebody willing to help and knows basic stuff about ROM porting will be Welcome.
OK not Working but here is it.
Test on YOUR OWN RISK.
IM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE OR IF YOU GET BOOTLOOP !!!!!!!!!!!
SO IF ANYTHING BAD HAPENS TO PHONE IM NOT RESPONSIBLE FOR IT !!!!
MAKE BOOT AND SYSTEM BACKUP BEFORE FLASHING !!!!
I have builded the ROM with patches but the same errors remain like bad UI in TWRP and not bootable system it will not even show Boot Animation but if anybody want to test it here is the ROM:
HTML:
https://ufile.io/un7oe
.
i have some patches that i havent applyed so will apply those and see what errors will it fix.
And if anybody flash it and know this errors then please tell me how to fix them
EDIT: added another patches like build patch and external_icu patch hwcomposer patch libhwui patch ste mutimedia patch (3 of them) and still not even a boot screen im woried that i will not even make this rom bootable
EDIT2: maybe found a way to fix it i probably need edited frameworks and system/core folder so going to do this few days later then will post and update if its was sucess or again a fail.
So i downloaded cm 12.1 source and will build daily build for this device until i figure out what the hell is wrong with Lineage 13.0 and cm 12.1 build will come out in few days need to configure the source for our device.
EDIT: I dont want you to be unhappy but there is like 1% change that i can fix all the problems in CM13.0 without a good team of devs and testers i cant do anything so dont expect ever daily runner baser on CM13.0 or even basic stuff working on it im student 17 years old yes i have a lot of C experience 9 years but thats doesnt change that i cannot do everything alone or with help of @AGONTUK its just lot of stuff to fix mainly boot so if anybody with some experience in this can help i will be happy.
i have all needed sources on my github so if anybody can help do it on github: My Github.
Have first build of CM 12.1 but i can see boot animation this time but it doesn't boot yet but another biiiig problem is no TWRP.
Main priority is TWRP so faster I can fix it the better: Probably will use android 5.1.1 repo TWRP and update to 3.0.2.0 TWRP if this will not help then maybe it's releated to not bootable system maybe have a fix but it needs more time.
And second priority is bootable system: I might have solution to this one but not totally sure.
Third priority after we have bootable using ROM is to make it fast:
1. Linaro instead art.
So in few days or week or so will post update how it's going. Maybe sooner if I get working build.
Haxk20 said:
Have first build of CM 12.1 but i can see boot animation this time but it doesn't boot yet but another biiiig problem is no TWRP.
Main priority is TWRP so faster I can fix it the better: Probably will use android 5.1.1 repo TWRP and update to 3.0.2.0 TWRP if this will not help then maybe it's releated to not bootable system maybe have a fix but it needs more time.
And second priority is bootable system: I might have solution to this one but not totally sure.
Third priority after we have bootable using ROM is to make it fast:
1. Linaro instead art.
So in few days or week or so will post update how it's going. Maybe sooner if I get working build.
Click to expand...
Click to collapse
Can you make a deodexed CM12.1 build? all builds from CBnuke are odexed
jao6622 said:
Can you make a deodexed CM12.1 build? all builds from CBnuke are odexed
Click to expand...
Click to collapse
Checked system/app and dont saw any odex files so yes i can make deodexed rom.
And also i have fixed TWRP error and tested just kernel and can boot rom with it now just to make system boot
Main issue with TWRP is FIXED even on CM13.0 and CM12.1 its fixed but both still dont boot up cm 12.1 atleast show me boot animation but cm 13.0 didnt do even that and its stuck at black screen i send few people message to help me with this and waiting for reply. Im looking trought my CM12.1 boot.log and i cannot find the error still what is causing it to not boot. And also i changed CM12.1 boot animation to the one included in LineageOS.
The problem was in TWRP that it choosed wrong PIXEL_FORMAT_BRGA_8888 instead of our PIXEL_FORMAT_RGB_565 so now it looks good now.
Here is link to this build: CM12.1 NOT BOOTABLE WITH FIXED TWRP FOR HELPING WITH FIX.
PLEASE IF YOU DONT KNOW WHAT YOU ARE DOING DONT INSTALL IT ITS STILL NOT BOOTABLE ROM.
Well cm12.1 still not booting at all but I'm going to delete the source and redownload by tutorial by friend (helping a lot Thanks) and if that fails I don't know then but hopefully we will get working build of cm12.1 and for now I'm deleting cm13.0 source since it needs a lot of work to be usable but will talk with SergeyL (he have device with same cpu) and will see how will that work if his work will be usable then if everything works perfectly (unlikely) then maybe cm14.1 but as I said unlikely so wait in few days for hopefully build of cm 12.1
Its working !!!
The best news i can tell you i want to share my Working build of CM12.1 !!! The build will be avaiable to download in few days in new thread (will tell the name later) but best of all is that working stuff is exactly like CBNUKE builds and the boot took 10 seconds Wooow.
Got new security patches 1.11.2016 (no newer since CM12.1 got no new updates.
Thats all i wanted to share.
---------- Post added at 11:53 PM ---------- Previous post was at 11:42 PM ----------
Its still build on CM source but will download Lineage Source and compile again but with cm source it was just test if i can build it and yes i can so after compiling Lineage will publish here
Hello,
As the thread where I originally announced this was locked for reasons apparently unrelated to my build, and the links removed, I'm creating a new thread to keep the community aware of these builds.
I've been building LineageOS 14.1 from the official LineageOS source repository for my personal devices for some time now, and it finally occurred to me that others might find them useful.
These builds are created every Saturday night from a 100% unaltered LineageOS repository, which is synchronized with upstream every day. I must stress that there are NO MODIFICATIONS at all; if it worked/didn't work in the last official Cyanogenmod/LineageOS releases, it works/doesn't work in my builds. At Apple we called these "sustaining builds" -- they keep devices in sync with the latest security patches, but receive no new features.
The build for the Asus Zenpad 8.0 Z380K[N]L (aka P024) is at https://lineageos.disavowed.jp/p024/. This appears to work on both the Z380KL (as reported in the locked thread) and my Z380KNL. There are other devices being built as well ... if you would like me to add a 14.1 or 15.1 device to the weekly build roster, please let me know.
I hope this helps out folks who want to extend the service lifetime of their gear. Share and enjoy.
Edit: per moderator request, I need to provide a link to the source repository used to generate these builds to comply with XDA's interpretation of the GPL. It is the stock LineageOS repository, located at git://github.com/LineageOS/android.git. TheMuppets binary repository was used for the vendor blobs; it is at https://github.com/TheMuppets/
Hi, I have been using your build and updated my device weekly! it' s still good and awesome. (I also use your build for my nexus7)
if you find Oreo, Pie version! please let everyone know. Thank you.
Thank's keep update bro.
Hi, I don't see your weekly build for 22 Nov 2019.
Are there any issues ?
Nice update thanks friends l.
Yeap yesterday i reported, and TS promised to update.
Argh, apparently I wasn't subscribed to my own thread. Fixed.
Sorry about the SIM recognization problem. Somehow my private dev builds were being uploaded instead of the sustaining builds. @DEV87WHY pinged me a few days ago to let me know. The newest build is from the correct tree, and hopefully this won't happen again.
Sorry about that ...
Argh, apparently I wasn't subscribed to my own thread. Fixed.
Sorry about the SIM recognization problem. Somehow my private dev builds were being uploaded instead of the sustaining builds. @DEV87WHY pinged me a few days ago to let me know. The newest build is from the correct tree, and hopefully this won't happen again.
Sorry about that ...
Question about Unofficial rom for Asus ZenPad 8.0 z380knl
How do you update device with rom without losing apps and data? Is it possible to update from unofficial lineage os 14.1 from your repository to latest unofficial lineage os 14.1 build from your repository without having to reinstall apps? My understanding is that you follow the process of normal flash of rom but you don't wipe? Is that it?
Another question:
Does MTP(file transfer) work with this ROM?
Also, did you manage to unlock bootloader(oem unlock). I know it is possible to flash the rom without bootloader unlock. Is that how you do it or you have found a way to unlock bootloader?
Thank you so much.
poka_dan said:
How do you update device with rom without losing apps and data? Is it possible to update from unofficial lineage os 14.1 from your repository to latest unofficial lineage os 14.1 build from your repository without having to reinstall apps? My understanding is that you follow the process of normal flash of rom but you don't wipe? Is that it?
Another question:
Does MTP(file transfer) work with this ROM?
Also, did you manage to unlock bootloader(oem unlock). I know it is possible to flash the rom without bootloader unlock. Is that how you do it or you have found a way to unlock bootloader?
Thank you so much.
Click to expand...
Click to collapse
Hi there,
First off -- thanks for the gift! Much appreciated.
If you're just flashing one of my newer builds on top of one of my older builds, then you shouldn't have to do anything special. Just kick the device into recovery and flash on top of the older build. If you're coming from the ancient Cyanogenmod or the stock ROM, then AFAIK you'll have to wipe.
MTP *should* work but I've never tried it. I don't have my device with me right now so I can't do a quick verification.
For unlocking the bootloader, I'm trying to remember (this was several years ago). IIRC I put it into fastboot and did a tethered recovery boot (i.e., "fastboot boot /path/to/recovery_image_on_pc.img"). Then I did a full wipe and a flash ... and bricked the device because I had a Z380KNL and the Cyanogenmod image at the time supported only the Z380KL.
I then put the stock ROM back on, and when the KNL bits hit the Cyanogen repository, I flashed it with success. At no point did I ever successfully unlock the bootloader as far as I can tell -- I downloaded the ASUS unlock but it never reported success. When booted into fastboot, there's a locked symbol at the lower right of the screen. That doesn't interfere with flashing anything from recovery.
Oh, and important safety tip: to enter recovery from fastboot after you've flashed it via the tethered recovery boot, you'll have to choose "factory reset" on the KNL.
I hope that helps.
As soon as I find out MTP is working I will flash the rom
wileyc said:
Hi there,
First off -- thanks for the gift! Much appreciated.
If you're just flashing one of my newer builds on top of one of my older builds, then you shouldn't have to do anything special. Just kick the device into recovery and flash on top of the older build. If you're coming from the ancient Cyanogenmod or the stock ROM, then AFAIK you'll have to wipe.
MTP *should* work but I've never tried it. I don't have my device with me right now so I can't do a quick verification.
For unlocking the bootloader, I'm trying to remember (this was several years ago). IIRC I put it into fastboot and did a tethered recovery boot (i.e., "fastboot boot /path/to/recovery_image_on_pc.img"). Then I did a full wipe and a flash ... and bricked the device because I had a Z380KNL and the Cyanogenmod image at the time supported only the Z380KL.
I then put the stock ROM back on, and when the KNL bits hit the Cyanogen repository, I flashed it with success. At no point did I ever successfully unlock the bootloader as far as I can tell -- I downloaded the ASUS unlock but it never reported success. When booted into fastboot, there's a locked symbol at the lower right of the screen. That doesn't interfere with flashing anything from recovery.
Oh, and important safety tip: to enter recovery from fastboot after you've flashed it via the tethered recovery boot, you'll have to choose "factory reset" on the KNL.
I hope that helps.
Click to expand...
Click to collapse
Gift was my pleasure
The info is most usefull. Thank you for that.
I am currently running my ZenPad 8.0 z380knl on Asus stock rom but ardently looking to upgrade to android 7.1.2 for security reasons as well as other reasons.
I was investigating if everything is working on the new rom. Also upgrade procedure from stock rom to lineage os and from lineage os 14.1 to latest 14.1 lineage os. Thankfully you cleared all that up. Thanks so much !
Only thing that remains for me to find out is if MTP is working on rom, so please check it for me when you have the time.
BTW, I haven't seen your new buld since last week.Will there be no update ?
Is everything working with this ROM?
Can i get confirmation from someone who is actively using it..
MTP and everything else working?
pokadan said:
Gift was my pleasure
Only thing that remains for me to find out is if MTP is working on rom, so please check it for me when you have the time.
Click to expand...
Click to collapse
I just tried MTP (using OpenMTP-2.4.1 on MacOS) and it seems to work fine.
androidlover2019 said:
BTW, I haven't seen your new buld since last week.Will there be no update ?
Click to expand...
Click to collapse
There should be an update (or two!) today. The build rooster hung about midway through last week's build for deb, and was actually still running after seven days. I killed off the deb build process and it's progressing to the other devices, although much slower than it should be. I'll troubleshoot this after the regularly scheduled build completes late tonight.
(I'm using Arch Linux on this build machine, and it seems that something in the filesystem layer in kernel > 5.4.10 doesn't like operating under sustained heavy load)
I saw your new build today and have installed it. Thank you
However, The latest security patch has not been applied yet. Hope it will come in next build.
Thank you so much for maintaining the device.
Thank you wileyc !
wileyc said:
I just tried MTP (using OpenMTP-2.4.1 on MacOS) and it seems to work fine.
Click to expand...
Click to collapse
I have put the latest available rom lineage-14.1-20200202-UNOFFICIAL-P024.zip on my device and works flawlessly!
Million thanks
I have installed the newest one (built on 08 Feb)
the Android security patch was updated to Jan 2020! Thank you very much.
I am worried how long you will keep sharing your build weekly.
Hope next 2 years Thanks again.
I have also installed the latest. Thanks so much!
Thankyou for the update :good:
What about selinux?
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