Hi All!
Is there a way to get lineage 14.x on le pro 3 Elite (X722)? I've been searching online, but all information seems to be related to X720 model, and there is basically nothing (or very little) regarding the X722... I was hoping to be able to root my device, Install lineage OS, and then un-root (due to using some corporate apps which don't allow devices to be rooted).
Please let me know in case you have some info. I will greatly appreciate your help!
Thanks!
Mick
Hey
As far as i know Leeco didn't released their open source code for x722 and that's why there is no custom roms. I'm a little bit confused because they shared their open source code for many models and i don't know why they didn't do that for x722 :C
tried booting this rom
Otojestemja said:
Hey
As far as i know Leeco didn't released their open source code for x722 and that's why there is no custom roms. I'm a little bit confused because they shared their open source code for many models and i don't know why they didn't do that for x722 :C
Click to expand...
Click to collapse
I want to know did u tried this rom because the specs are similar except for nfc and slow processor on chinese version sd820 instead of sd821
Ab20000 said:
I want to know did u tried this rom because the specs are similar except for nfc and slow processor on chinese version sd820 instead of sd821
Click to expand...
Click to collapse
I didn't tried any rom and at the moment i don't have this phone. I think different processor than in leeco x720/x727 make it useless to use the 720/727 rom for this device and can only lead to brick phone.
So why does TWRP for x720/x727 work flawlessly on x722?
Also lineage OS developer for lepro3 asked if anyone can give him log files from lineage boot on x722 then he can probably make it work. It seems the issue is not CPU (i guess it is same linux kernel and drivers anyway), but somehow changed boot sequence of the x722 then x720/x727, but i don't really understand this stuff.
evlo said:
So why does TWRP for x720/x727 work flawlessly on x722?
Also lineage OS developer for lepro3 asked if anyone can give him log files from lineage boot on x722 then he can probably make it work. It seems the issue is not CPU (i guess it is same linux kernel and drivers anyway), but somehow changed boot sequence of the x722 then x720/x727, but i don't really understand this stuff.
Click to expand...
Click to collapse
thats why I dislike this company. They have placed very small batteries in their phones and removed headphone jacks and no sdcard slot. Plus they are not releasing sources of these China specific models.
evlo said:
So why does TWRP for x720/x727 work flawlessly on x722?
Also lineage OS developer for lepro3 asked if anyone can give him log files from lineage boot on x722 then he can probably make it work. It seems the issue is not CPU (i guess it is same linux kernel and drivers anyway), but somehow changed boot sequence of the x722 then x720/x727, but i don't really understand this stuff.
Click to expand...
Click to collapse
huh, if he can guide me I will provide him with the logs that he needs. It would make this phone sooooooo much better if we could put lineage os on it.
Ab20000 said:
thats why I dislike this company. They have placed very small batteries in their phones and removed headphone jacks and no sdcard slot. Plus they are not releasing sources of these China specific models.
Click to expand...
Click to collapse
I don't agree regarding the battery, but an sd slot I definitely miss... the phone itself is good, but it really sucks that we can't put lineage on it. I wish I did proper research before buying it, as I would probably go for a different one.
mick_novi said:
I don't agree regarding the battery, but an sd slot I definitely miss... the phone itself is good, but it really sucks that we can't put lineage on it. I wish I did proper research before buying it, as I would probably go for a different one.
Click to expand...
Click to collapse
yea you are right . I saw x626 with 4/64gb on gearbeast for less than 140. But I cancelled the order because there is no ROM support. This model was not released outside of China so it has no google play store originally and no MTK model was made for market outside CN like the 1s thus flashing Indian/Russian or other international ROM is not a possibility.
did anyone update a lineage ROM on the Le Pro x722?
Ab20000 said:
yea you are right . I saw x626 with 4/64gb on gearbeast for less than 140. But I cancelled the order because there is no ROM support. This model was not released outside of China so it has no google play store originally and no MTK model was made for market outside CN like the 1s thus flashing Indian/Russian or other international ROM is not a possibility.
Click to expand...
Click to collapse
could anyone try and test the lineage at this page download.lineageos.org/zl1 and try it with the x722 and check if it all works good? or do you have any similar hint?
diegosum said:
could anyone try and test the lineage at this page download.lineageos.org/zl1 and try it with the x722 and check if it all works good? or do you have any similar hint?
Click to expand...
Click to collapse
The problem is that the bootloader is locked and there is currently no root for the device... and as it seems like there will never be. one...
It would make this phone so much better if we had the chance to put lineage on it, as LeEco is going under (if not already), and there will be no future updates to the software, even though there are so many bugs... such as you can't change default browser, expand notifications, and so on....
mick_novi said:
The problem is that the bootloader is locked and there is currently no root for the device... and as it seems like there will never be. one...
It would make this phone so much better if we had the chance to put lineage on it, as LeEco is going under (if not already), and there will be no future updates to the software, even though there are so many bugs... such as you can't change default browser, expand notifications, and so on....
Click to expand...
Click to collapse
yes, and the camera not auto-focusing when changing from a far to a closer focus or the contrary and you have to be tapping on the screen every time
so in the end maybe the lineage 14 for the x720 and x727 might work fine but the point is that the x722 has a locked door about bootloader and can't open and enter to work on it?
diegosum said:
yes, and the camera not auto-focusing when changing from a far to a closer focus or the contrary and you have to be tapping on the screen every time
so in the end maybe the lineage 14 for the x720 and x727 might work fine but the point is that the x722 has a locked door about bootloader and can't open and enter to work on it?
Click to expand...
Click to collapse
Yes, exactly. This lineage for x720 might work, but currently there is no way to install it.... I really hope that sometime in the future, installing lineage will be possible, that someone figures it out (fingers crossed it happens sometime soon)
diegosum said:
could anyone try and test the lineage at this page download.lineageos.org/zl1 and try it with the x722 and check if it all works good? or do you have any similar hint?
Click to expand...
Click to collapse
If you have American single sim model then you have to unlock bootloader first then try. I heard most roms are compatible but I am not sure about NFC status.
Hi guys, can you provide any working TWRP and guide how to root my X722?
Thanks
mick_novi said:
huh, if he can guide me I will provide him with the logs that he needs. It would make this phone sooooooo much better if we could put lineage os on it.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=73318157&postcount=760
https://forum.xda-developers.com/showpost.php?p=73323157&postcount=762
I will also be able to help once my phone arrives. Wondering what firmware i'll get it with (from BangGood).
When I scanned xda I saw official lineage for x72x so i assumed it was supported - the title is a bit misleading. Probably wouldn't have ordered it if I read the whole thread.
That said, I'm in it for the long haul now, and might actually be a good opportunity for me to actually give something back to the xda community (besides $).
Too many wrong infos in this topic.
- Bootloader is locked ONLY in 026s stock rom and it CAN be unlocked by flashing 001d dev release.
- You DON'T flash x720 roms to x722 since you will easily get a nice brick.
- You DON'T flash stock 026s through TWRP (especially from geekbuying vendor 020s rom with twrp)
- x722 has root in tora33 custom rom - this is a fresh stuff so check that thoroughly
dakok said:
Too many wrong infos in this topic.
- Bootloader is locked ONLY in 026s stock rom and it CAN be unlocked by flashing 001d dev release.
- You DON'T flash x720 roms to x722 since you will easily get a nice brick.
- You DON'T flash stock 026s through TWRP (especially from geekbuying vendor 020s rom with twrp)
- x722 has root in tora33 custom rom - this is a fresh stuff so check that thoroughly
Click to expand...
Click to collapse
I used the tora33 no root custom in x722, but the fingerprint sensor stoped, so i put the Dev ROM again
dakok said:
- x722 has root in tora33 custom rom - this is a fresh stuff so check that thoroughly
Click to expand...
Click to collapse
Do you have a link for this ROM?
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.
I am curious if anyone is currently working on getting CM (or any custom ROM) working for our devices. I'm not trying to bug anyone or get an ETA, but I was thinking about attempting to port CM with their tutorial.
If anyone is working on porting a ROM, or has any tips for me I'd love to talk. Thanks.
I've just started looking into porting CM over to the 5x. I've never built a port before and I'm a bit lost in the CM documentation for it. Feel free to PM me or post below with any tips or advice.
jmiller99 said:
I've just started looking into porting CM over to the 5x. I've never built a port before and I'm a bit lost in the CM documentation for it. Feel free to PM me or post below with any tips or advice.
Click to expand...
Click to collapse
I have only built unofficial builds before, but hopefully since we have source and other Huawei devices with CM, it should be fairly easy.
If you haven't built CM for a device that it's already been ported to, I'd recommend doing that before you attempt to port it.
Good luck. I'll post any progress I make.
Am too eagerly waiting for cm on 5x .fed up of bad performance from stock .heating up too much .I was really disappointed by the heating problem .
What else I had hopes On was the on cm12.1 or 13 .
I usually check for a thread if anyone build one cm ROM for our device but still the development haven't started !
gopinaidu77 said:
Am too eagerly waiting for cm on 5x .fed up of bad performance from stock .heating up too much .I was really disappointed by the heating problem .
What else I had hopes On was the on cm12.1 or 13 .
I usually check for a thread if anyone build one cm ROM for our device but still the development haven't started !
Click to expand...
Click to collapse
I'm *trying* to get CM 12.1 to work for our device, but I've never ported before so don't expect anything soon
gopinaidu77 said:
Am too eagerly waiting for cm on 5x .fed up of bad performance from stock .heating up too much .I was really disappointed by the heating problem .
What else I had hopes On was the on cm12.1 or 13 .
I usually check for a thread if anyone build one cm ROM for our device but still the development haven't started !
Click to expand...
Click to collapse
It's still early. The fact that Huawei makes bootloader unlock codes available and has provided the amount of source code for the kernel that they have has allowed development here to happen much more rapidly than many devices do (particularly devices that lie out side of "volume" interest -- like an S5 or S6). I'm pretty optimistic.
The flip side is that life is so busy for me at the moment that it makes patience pretty easy (as in, if a stable cm13 suddenly became available I still would take my sweet time in getting around to flashing it). If I had more time on my hands it would probably be different.
Yes lets see how long we need to wait !
Can someone (hopefully a dev like @deadman96385, @EarlyMon @cyrusalmighty) confirm/agree that the Honor 5X's (I have KIW-24, US ver.) vendor = HONOR and codename = HNKIW-Q. I'm a little perplexed by what the codename is since HNKIW-Q doesn't seem right. I got that name from the build.prop ro.product.device like CM recommends.
Can anyone confirm that I have the vendor and codename right? Thanks.
EDIT: After looking at similar Huawei devices (Ascend Mate 2) it looks like the codename should just be "kiw". The Mate 2's actual ro.product.device = hwMT2LO3, but it's CM codename is "mt2." Because of this, I think for the CM codename should be "kiw". Does that sound right?
Bandit Development said:
Can someone (hopefully a dev like @deadman96385, @EarlyMon @cyrusalmighty) confirm/agree that the Honor 5X's (I have KIW-24, US ver.) vendor = HONOR and codename = HNKIW-Q. I'm a little perplexed by what the codename is since HNKIW-Q doesn't seem right. I got that name from the build.prop ro.product.device like CM recommends.
Can anyone confirm that I have the vendor and codename right? Thanks.
EDIT: After looking at similar Huawei devices (Ascend Mate 2) it looks like the codename should just be "kiw". The Mate 2's actual ro.product.device = hwMT2LO3, but it's CM codename is "mt2." Because of this, I think for the CM codename should be "kiw". Does that sound right?
Click to expand...
Click to collapse
In theory but the kiw stands for kiwi this info is directly from Huawei and we all like Kiwi more lol. You also do have a L24 US variant
deadman96385 said:
In theory but the kiw stands for kiwi this info is directly from Huawei and we all like Kiwi more lol. You also do have a L24 US variant
Click to expand...
Click to collapse
Thanks. So any custom ROM development for this device will be like Huawei/kiwi? I'm just wondering, because I'd like to know how I should be naming my files specific to Honor 5X ROM development.
EDIT:
Also, @deadman96385 do you mind sharing the partition sizes you used for building TWRP?
Name it kiwi .it sounds really great ! Moreover i dont what others are thinking on naming this device ,but kiwi is maximum minds .Go for it !
Bandit Development said:
Thanks. So any custom ROM development for this device will be like Huawei/kiwi? I'm just wondering, because I'd like to know how I should be naming my files specific to Honor 5X ROM development.
EDIT:
Also, @deadman96385 do you mind sharing the partition sizes you used for building TWRP?
Click to expand...
Click to collapse
https://github.com/Huawei-Kiwi
deadman96385 said:
https://github.com/Huawei-Kiwi
Click to expand...
Click to collapse
I didn't realize you had already started working on a CM port. I guess I can't really help out then. :/
Don't get me wrong, I do really appreciate all the work you do for this device.
Bandit Development said:
I didn't realize you had already started working on a CM port. I guess I can't really help out then. :/
Don't get me wrong, I do really appreciate all the work you do for this device.
Click to expand...
Click to collapse
That cm tree was just to build cm recovery we are still in the very early stages of a full cm tree.
Hey guys I am seriously considering buying the Note 10 (mojito) and I would like to know your opinions on custom ROMs for it. The Note 10 ticks all the boxes for me, but I worry that phones like the Note 10 PRO and PRO MAX will take most of the attention of Devs and therefore custom ROM development in mojito will not receive much attention. Do you think this is a valid worry?
I want my next phone to run deGoogled ROMs (like LOS), is mojito going to be a good choice for this?
Right now in my country its price is very good, while the PRO/MAX variants haven't arrived yet. It will be some time before they do, and even more before their price drops. So mojito is a very strong contender for me.
To clarify, I am not complaining there isn't a deGoogled custom ROM yet, only asking if you guys think it will get them.
I already use a custom ROM without Google, dotOS 5.0.1.
Installation of the Vanilla Version (without Google Services/Apps) via PE/AOSP or Lineage Recovery and ADB sideload.
Here are the instructions:
Install PixelExperience on mojito - PixelExperience Wiki
Install PixelExperience on mojito - PixelExperience Wiki
wiki.pixelexperience.org
Just take dotOS ROM from here (instead of Pixel Experience ROM).
Afterwards the APKs for microG:
Download - microG Project
Activate all checkboxes in microG settings, reboot and disable battery optimization for all components.
F-Droid and Aurora Store working, from there you can get the MozillaNLPbackend and NomatimNLPbackend and Deja Vu for location services without using Google.
There is no need to worry. It's will claim a lot of development. the most reason was to not see a lot and lazy at the beginning is on our Device (mojito/sunny) we don't have Recovery partition! which let our development slow but we have a good stuff of developers that's works hard and got us on the road as you see the roms are coming till now we got 6 roms and 3 recoveries and Orangefox soon.
UniNick said:
I already use a custom ROM without Google, dotOS 5.0.1.
Installation of the Vanilla Version (without Google Services/Apps) via PE/AOSP or Lineage Recovery and ADB sideload.
Here are the instructions:
Install PixelExperience on mojito - PixelExperience Wiki
Install PixelExperience on mojito - PixelExperience Wiki
wiki.pixelexperience.org
Just take dotOS ROM from here (instead of Pixel Experience ROM).
Afterwards the APKs for microG:
Download - microG Project
Activate all checkboxes in microG settings, reboot and disable battery optimization for all components.
F-Droid and Aurora Store working, from there you can get the MozillaNLPbackend and NomatimNLPbackend and Deja Vu for location services without using Google.
Click to expand...
Click to collapse
Amazing man, this is awesome. I was not aware that there was a deGoogled ROM for it already, nor that dotOS existed and was so slick. I will definitely take a look at this.
Does it pass SafetyNet?
Would you happen to know who the developer/maintainer for that unofficial ROM is? I looked around and couldn't find a page for it here on XDA.
Nevermind, saw here that there isn't an XDA page for some ROM for the the time being. Since I have never flashed a custom ROM on any phone, I will wait for one to see what are people's experiences with it.
Abdullah.Csit said:
There is no need to worry. It's will claim a lot of development. the most reason was to not see a lot and lazy at the beginning is on our Device (mojito/sunny) we don't have Recovery partition! which let our development slow but we have a good stuff of developers that's works hard and got us on the road as you see the roms are coming till now we got 6 roms and 3 recoveries and Orangefox soon.
Click to expand...
Click to collapse
Sweet, this is comforting. I am really looking forward to deGoogling my phone, but am a little hesitant since I have zero experience flashing ROMs hahaha. Was going to go for a phone with Official LOS support but models available to me are the same price as the Note 10, but nowhere near as good.
syntheticdingo said:
Does it pass SafetyNet?
Click to expand...
Click to collapse
On unrooted dotOS with just microG: no.
However, 2 out of 3 banking apps work.
After testing dotOS (vanilla) with microG for a couple of days and with a lot of apps, I'd say it's not usable as a daily driver yet.
There are problems with most apps that use maps, like Uber or Wolt or DHL parcel service.
They generate error messages that google services are not properly installed and quit or malfunction.
However, microG and the corresponding locations services install perfectly and don't show any errors.
I didn't have such problems with other ROMs on other phones (but always using microG), e.g. crDroid or ArrowOS or LineageOS.
Thanks for the feedback. Is that the only issue with the ROM?
I am really sold on DotOS, it is very close to stock and has very beautiful customizations. My problem with the one that is available so far is that it doesnt look very transparent (at least to me). No source code available, no page here. And I dont know how serious the Dev is about maintaining it, nor how credible he is as well.
Not really trying to test every ROM, just find one that is stable, deGoogled and maintained.
I think you're a couple of months too early with your questions, the phone is pretty new and the ROMS and recoveries in a very early state.
hahaha yes, I am afraid so.
My phone's battery is starting to act up, so I will have to make a purchase soon. May take a leap of faith on this phone and see how much attention it gets from the dev community
Thanks for your feedback!
[email protected]@@@@ said:
Please provide gaming rom in redmi note 10
Click to expand...
Click to collapse
or you could install smartpack kernel manager and tweak the kernel parameter to give the best fps for your phone .. try it
[email protected]@@@@ said:
Please provide gaming rom in redmi note 10
Click to expand...
Click to collapse
Gaming ROMs does not exist
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
Hi guys,
I am forced to upgrade my moto G5 plus due to a network update
In my moto G5 plus I have installed dotOS with android 11 and I am really happy with it, and I would like "clone" it on a Moto G Power.
Here are some questions:
1) since Moto G Power (2021) is not listed on dotOS but a GSI ARM64 available, has anyone experienced with that? I am also open to other custom ROMS (also Lineage OS doesnt have this devicelisted)
2) I also noticed that TWRP is not available for Moto G Power (2021), is there a good alternative or I have to use adb fastboot?
Thanks!
Edit:
I just found the thread:
[RECOVERY][UNOFFICIAL] TWRP 3.6.0-11 [BORNEO] Android 11 Based (updated 12/11/2021)
I can try that for question 2
Efone said:
Hi guys,
I am forced to upgrade my moto G5 plus due to a network update
In my moto G5 plus I have installed dotOS with android 11 and I am really happy with it, and I would like "clone" it on a Moto G Power.
Here are some questions:
1) since Moto G Power (2021) is not listed on dotOS but a GSI ARM64 available, has anyone experienced with that? I am also open to other custom ROMS (also Lineage OS doesnt have this devicelisted)
Click to expand...
Click to collapse
Presently I don't believe it is possible to have a custom rom as we need the kernel be released for it to have a chance, or a compatible similar device and its kernel.
Hi Onoitsu and thank you for the reply,
so I guess I could go with the stock ROM. I noticed that I can use https://mirrors.lolinet.com/firmware/moto/borneo/ has an official and blankflash (not sure what the difference is). If I understand the process correctly I could:
1) unlock bootloader
2) flash twrp in recovery
3) flash blankflash.zip (or official?) through twrp
4) flash magisk through twrp
5) restore my old phone dotOS android 11 backup through twrp
and I should have all the apps and data as in the old device?
Efone said:
Hi Onoitsu and thank you for the reply,
so I guess I could go with the stock ROM. I noticed that I can use https://mirrors.lolinet.com/firmware/moto/borneo/ has an official and blankflash (not sure what the difference is). If I understand the process correctly I could:
Click to expand...
Click to collapse
The blankflash is only if you can no longer flash anything by usual methods
Blankflash and EDL Mode
Is my device in EDL Mode?
How to boot into EDL Mode
Thanks for the info!
Should the reasoning above work if I use official instead of blankflash?
Efone said:
3) flash blankflash.zip (or official?) through twrp
Click to expand...
Click to collapse
Neither the blank flash nor official firmware are twrp compatible.
Thanks sd_shadow for the info, it is really helping me out.
I saw your post for using LSMA, but I couldnt find a Linux version. Is there one? Or the only other option I have is going through the fastboot process?
Can anyone tell me if there is going to be custom roms made for Borneo?
Hatrackman said:
Can anyone tell me if there is going to be custom roms made for Borneo?
Click to expand...
Click to collapse
Still the reason I cite in post 2 above, indeterminate, sadly.
Onoitsu2 said:
Still the reason I cite in post 2 above, indeterminate, sadly.
Click to expand...
Click to collapse
Mostly concerned because google has said they're going to stop their 'less secure app' thing at the end of this month and it might mean textnow will stop working outright for people that don't use play services.
Hopefully anyone working on making a custom rom for Borneo will see this thread and maybe give an idea if its going to happen.
Does this help?
If I wanted to start from scratch what would I need to know to make my own custom rom? Don't need a phone, will only ever use wifi. Just need microg basically.
The following statement is on the dotOS FAQs:
Q: My device is not supported! What should I do?!A: First reason can be that our development team doesn't have your device to support it or we no maintainer applied for this device. You can always use our GSI builds if your phone supports Treble Project.
Here we have this statement:
... Google requires every Certified Android device launching with Android 8.0 Oreo and above to support Treble.
Here borneo is listed as a supported device.
Does this mean dotOS GSI supports MotoGPower 2021 without the need of vendor blobs?
Onoitsu2 said:
Presently I don't believe it is possible to have a custom rom as we need the kernel be released for it to have a chance, or a compatible similar device and its kernel.
Click to expand...
Click to collapse
@sd_shadow
Two sites that potential rom developers may want to check out:
1) https://github.com/moto-common
check out: https://github.com/moto-common/andr...ernel/blob/12/dtb/bengal-moto-base-borneo.dtb
2) https://github.com/moto-sm6115
Scroll through the list of repositories, particularly in the moto-common site
@sdembiske that looks promising, I am willing to give it a shot and contribute to the community. Is there a good guide on how to build the kernel with vendor tree/blobs etc...?
Reference "Moto G Power 2021 XT2117-4 Firmware Extractions" - You will find the extracted kernel etc. in the boot.img extracted link that you can download - there are many other extractions that you hopefully can use to build a custom or AOSP rom.
Your best bet would be to add a pre-built kernel in the build - you can google that for how-to's.
Onoitsu2 said:
Presently I don't believe it is possible to have a custom rom as we need the kernel be released for it to have a chance, or a compatible similar device and its kernel.
Click to expand...
Click to collapse
The Xiaomi poco m3 has the same SoC and other innards as the Moto G Power 2021 and it also has unofficial Lineage OS 19 support. I am considering hitting them up and using their code as part of the build. I'm also requesting Motorola Mobility LLC to release the kernel source for Android 11. I already have a device tree for Borneo on my github. Me and Fazwalrus have a telegram chat set up for the ROM development here