Hi!
I would like to present you Android Boot Manager dualboot solution.
For now we have 4 work in progress devices:
Volla Phone
F(x)tec Pro 1/X
Moto G5
Galaxy S3 neo (nothing done yet)
Our wiki
Why new solution?
There is a lot of them already, such as: efidroid, multirom, dualboot patcher.
Now all of them are dead, because google implemented SAR, A/B, super partition.
We aim to support all that.
How it work?
ABM consists of 2 parts: bootloader and app+ sh scripts.
App with sh scriptes is used to install bootloader and add new roms.
Bootloader is used to display list of roms and load linux kernel with right dtb and optionally initrd.
What is used as BL:
Anything that can boot kernel. It coud be either 2nd stage bl, or in some cases even phones main bl.
For now:
Volla Phone (MTK's lk based bl)
F(x)tec Pro1/X (custom abl + uefi app)
Moto G5 and S3 neo (lk2nd)
Thanks to:
nift4 (Android app dev, co-creator of project)
LVGL team (GUI library)
lk (little kernel, used as bootloader on some platforms)
Fxtec (HW)
Volla (HW)
Reserved
Reserved#1
i am looking forward for your project ,Good work and hope if support come also for xiaomi poco F2 pro
bilalrajput said:
i am looking forward for your project ,Good work and hope if support come also for xiaomi poco F2 pro
Click to expand...
Click to collapse
It is possible, but i dont have that device.
What u need from my phone to do that,i think its very interesting,keep it up.Cheers!!!!
-CALIBAN666- said:
What u need from my phone to do that,i think its very interesting,keep it up.Cheers!!!!
Click to expand...
Click to collapse
What device, what soc?
I have a F(x)tec Pro1 ready for some stunts, I'm happy to serve as a test pilot as soon as I can find some instructions!
You call it Android Boot Manager. Does that mean it is made specifically to boot things that are based on Android, like Stock, AICPQ, LineageOS, or is that true for any ported OS that runs on libhybris with the Android kernel (plus some patches sometimes), like hybris-mobian, ArchARM, SFOS, etc.?
kewbak said:
I have a F(x)tec Pro1 ready for some stunts, I'm happy to serve as a test pilot as soon as I can find some instructions!
You call it Android Boot Manager. Does that mean it is made specifically to boot things that are based on Android, like Stock, AICPQ, LineageOS, or is that true for any ported OS that runs on libhybris with the Android kernel (plus some patches sometimes), like hybris-mobian, ArchARM, SFOS, etc.?
Click to expand...
Click to collapse
Hi!
Android Boot Manager will support Ubuntu touch, SFOS, and other too i hope. Currently i am working on fxtec bringup. I got gui in uefi already, tho lvgl have problems with font.
luka177 said:
What device, what soc?
Click to expand...
Click to collapse
Redmi 9,MTK Helio G80 64bit,Cheers!!!
Hi, now we have work in progress wiki https://www.wiki.abmanager.tech/index.php/Main_Page
We plan to implement no-bootloader-workaround that will work on devices without 2nd or 1st stage opesource bootloader. And we plan support for Das U-boot
Great news! I see that the Pro1 msm8998 is not listed among supported devices, but count me in as a tester as soon as it is. Curious if it would be possible to dualboot mainline + libhybris OSes too, but I reckon this would be difficult.
kewbak said:
Great news! I see that the Pro1 msm8998 is not listed among supported devices, but count me in as a tester as soon as it is. Curious if it would be possible to dualboot mainline + libhybris OSes too, but I reckon this would be difficult.
Click to expand...
Click to collapse
It is not listed as wiki is really WIP. And yes it will be possible to dualboot libhybris based OSes with mainline based.
how is the project going? think that your android boot manager will be a cool thing!!
Phitschhd said:
how is the project going? think that your android boot manager will be a cool thing!!
Click to expand...
Click to collapse
About 7 people have an working tripleboot on the Volla Phone
nift4 said:
About 7 people have an working tripleboot on the Volla Phone
Click to expand...
Click to collapse
that sounds cool...with A11?
Phitschhd said:
that sounds cool...with A11?
Click to expand...
Click to collapse
The Volla Phone has no Android 11 yet.
Strange... there is an post in my inbox that I can't see with the web ui?
oh ok that sounds cool..do you know if they are also working on an „universal“ solution for „all“ phones?
Click to expand...
Click to collapse
I am one of the developers, and well we are working on something easy to port, it isn't totally generic.
nift4 said:
Strange... there is an post in my inbox that I can't see with the web ui?
I am one of the developers, and well we are working on something easy to port, it isn't totally generic.
Click to expand...
Click to collapse
that‘s because i deleted the post. It was logic anyway that it will be (hopefully ) a universal solution, bc its also in the topic android development. But nice that you working on that! I also have Dualboot on my Poco F1 because the dev vasishath brought Multirom to this device.
Hi Luka,
any info on the progress of dualboot for the f(x)tec pro1 x? ABM would definetely be great for this device.
Related
It's true.
@Razziell left the ship some days ago.
Xiaomi is the devil. Left us with F*CKING BUGGED source codes.
Yeah, that is sad, there is basically no one left for our good old Redmi 4 Prime.
Does anyone knows how @jacoghi is doing ? We haven't see the man in a long time and I would like to know if he is doing well in his life.
Title is misleading. He compiled the ROMs not ported them.
LokaX2 said:
Yeah, that is sad, there is basically no one left for our good old Redmi 4 Prime.
Does anyone knows how @jacoghi is doing ? We haven't see the man in a long time and I would like to know if he is doing well in his life.
Click to expand...
Click to collapse
I believe is everything okay...
psykkuno said:
Title is misleading. He compiled the ROMs not ported them.
Click to expand...
Click to collapse
Whatever, he was a great DEV! <3
thomasginn said:
Whatever, he was a great DEV! <3
Click to expand...
Click to collapse
How can you say that when you use epic rom? Lmao
psykkuno said:
How can you say that when you use epic rom? Lmao
Click to expand...
Click to collapse
ayo, I used his roms xD
thomasginn said:
ayo, I used his roms xD
Click to expand...
Click to collapse
xD
It's really sad
Question for devs, Is it possible to use source code from Redmi 4 Note with SD (code name: mido)? Hardware is quite similar and they have real strong dev community. Maybe quickest way is to use custums Roms for Redmi 4 Note, adjusted hardware differences and compile Rom for R4P?
Blackeyed73 said:
Question for devs, Is it possible to use source code from Redmi 4 Note with SD (code name: mido)? Hardware is quite similar and they have real strong dev community. Maybe quickest way is to use custums Roms for Redmi 4 Note, adjusted hardware differences and compile Rom for R4P?
Click to expand...
Click to collapse
Always though 'bout that. it WAS to be possible, a few differences.
thomasginn said:
It's true.
@Razziell left the ship some days ago.
Xiaomi is the devil. Left us with F*CKING BUGGED source codes.
Click to expand...
Click to collapse
Can you elaborate on what is exactly wrong? Was this done on purpose or...?
Jejking said:
Can you elaborate on what is exactly wrong? Was this done on purpose or...?
Click to expand...
Click to collapse
Xiaomi doesn't release kernel source for building AOSP or CAF based rom, kernel source only work for MIUI at most. Also most proprietary vendor driver not available as sources (only blob). It's pain to build custom rom from Android fork.
Compared to Samsung, Sony, Lenovo, Oneplus etc, almost all abandoned xiaomi devices suffered same fate, the custom rom will always missing something. We were very lucky if we had such a great developer.
My previous device, redmi 1s never get update beyond kitkat, but armani-dev (especially fefifofum) were a great team, they bring mostly stable nougat release (LOS, Mokee, Slim, etc).
dels07 said:
Xiaomi doesn't release kernel source for building AOSP or CAF based rom, kernel source only work for MIUI at most. Also most proprietary vendor driver not available as sources (only blob). It's pain to build custom rom from Android fork.
Compared to Samsung, Sony, Lenovo, Oneplus etc, almost all abandoned xiaomi devices suffered same fate, the custom rom will always missing something. We were very lucky if we had such a great developer.
My previous device, redmi 1s never get update beyond kitkat, but armani-dev (especially fefifofum) were a great team, they bring mostly stable nougat release (LOS, Mokee, Slim, etc).
Click to expand...
Click to collapse
Redmi Note 4X has many ROM's, officially.
There was idea that that device is like ours so we should talk to some devs and use its sources
Blackeyed73 said:
Question for devs, Is it possible to use source code from Redmi 4 Note with SD (code name: mido)? Hardware is quite similar and they have real strong dev community. Maybe quickest way is to use custums Roms for Redmi 4 Note, adjusted hardware differences and compile Rom for R4P?
Click to expand...
Click to collapse
That would be essentially the same proccess we are now. It can be achieved though to use the tree from Mido and modify it for our device. Make a stable tree then compile
Hello. I have a stupid idea, but it might work. What about porting ROM's from Nubia Z11 mini S? It has the same specs(i mean SP625 and Adreno 506).
Please, comment: https://forum.xda-developers.com/redmi-note-4/how-to/developers-help-t3660926
We must show how great we are
gsuzeda said:
Please, comment: https://forum.xda-developers.com/redmi-note-4/how-to/developers-help-t3660926
We must show how great we are
Click to expand...
Click to collapse
great work friend
From RN4 section:
Razziell said:
You do not need to talk about things you do not know. I had problems with the hard drive and only some people from the Russian community helped them to solve. For them, I continue to work. The rest can freely use my source, they are completely working.
Click to expand...
Click to collapse
You have problem with HDD? Why didn't say that in R4P forums, you just say that you want to stop developing because you don't have time to do it. Is that whole reson to stop sharing with R4P community ?
Just be Patient, always belive something wonderful will be happening!
Our Roms kernel are uptodate so no worry please
With HD10 (2017) unlock/TWRP available - link (thanks to @k4y0z!!!), the next natural question is a custom ROM. The subject may turn out to be slightly trickier than what appears at first sight.
Let's have a discussion thread to brainstorm on this and not wonder off-topic in other places.
I had seen @DragonFire1024 & @Rortiz2 tried to work on that, so feel free to chime in as necessary.
What we have:
HD10 (2017) chipset - MT8173 (2+2 cores), there is an beefier brother to it, MT8176 (2+4 cores). For most practical purposes both chipsets seem almost identical software-wise.
MT8173 was introduced in March 2015 (time of Lollipop domination - Android 5). MT8176 was introduced in October 2016 (getting toward Nougat - Android 7).
The efforts up to date on a custom ROM for this chipset appear to be by @Goayandi, who is still active on XDA, so his work could be used a starting point. I believe @Goayandi was working on Android 7 (Nougat). Here are some of the original links:
XDA : Mediatek MT8173 & MT8176 development
Reddit: Mediatek MT8173 & MT8176 development
Stuff from Amazon for MT8173 (both HD10 2017 and FireTV2) is Lollipop-vintage (Android 5), other devices with these chipsets seem to have reached Nougat (Android 7). It does not appear that there is any known MT8173/MT8176 device with Android 8, or 9 (or is there?). It seems that @diplomatic has an Asus like this with Nougat.
At the moment, it feels a a Nougat custom ROM might be the ceiling for the device, given the difficulties of finding proprietary pieces for MTK chipsets to get Android 8 or 9 going. Now, even Android 7 is still a bit of a challenge, given limited prior success.
More thoughts/ideas? Feel free to fill this thread with random thoughts as much as you want - that's what it's for!!!
I'm really looking forward to an AOSP experience on this tablet, to be honest. Can't wait to see what they come up with!
GuyInDogSuit said:
I'm really looking forward to an AOSP experience on this tablet, to be honest. Can't wait to see what they come up with!
Click to expand...
Click to collapse
As long as I can set up everything properly I'm ready to go. I've managed to get past script issues I think. I can get it to flash and it boots to the orange fire logo and sits for eternity. This was the same result pre and post TWRP. So at this point it's probably the installation and improper setup of the tree and files. If someone can point me to a guide or give me instructions on how to add support to my AOSP working directory, that would be great. This bit of the leg work is hard as there really aren't any guides that are detailed enough or that work anymore.
Secondly, I think if we are going to use a kernel, we either use the 7.0 source, or just use the kit I have to build our own. Amazon cherry picked the crap out of the kernel practically to the bare bones, so I think expanding from it is just a waste of time, especially since we have the kit that does a lot of the work for us, including providing signatures and the tools to sign etc.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
I wouldn't mind even if the best ROM available is a 6.0 Marshmallow one. Anything that gives AOSP on a stable base for the Fire HD10 is going to be awesome.
DragonFire1024 said:
As long as I can set up everything properly I'm ready to go. I've managed to get past script issues I think. I can get it to flash and it boots to the orange fire logo and sits for eternity. This was the same result pre and post TWRP. So at this point it's probably the installation and improper setup of the tree and files. If someone can point me to a guide or give me instructions on how to add support to my AOSP working directory, that would be great. This bit of the leg work is hard as there really aren't any guides that are detailed enough or that work anymore.
Secondly, I think if we are going to use a kernel, we either use the 7.0 source, or just use the kit I have to build our own. Amazon cherry picked the crap out of the kernel practically to the bare bones, so I think expanding from it is just a waste of time, especially since we have the kit that does a lot of the work for us, including providing signatures and the tools to sign etc.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
Click to expand...
Click to collapse
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
k4y0z said:
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
Click to expand...
Click to collapse
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
bibikalka said:
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
Click to expand...
Click to collapse
They will likely need some patches to work with newer versions, but it's a good start I'd say.
It's the most recent version amazon has published.
k4y0z said:
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
Click to expand...
Click to collapse
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Sent from my MotoG3 using XDA Labs
---------- Post added at 06:23 PM ---------- Previous post was at 06:21 PM ----------
bibikalka said:
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
Click to expand...
Click to collapse
The one I have and provided is a source to 7.0. looks nicely stocked.
Sent from my MotoG3 using XDA Labs
bibikalka said:
With HD10 (2017) unlock/TWRP available - link (thanks to @k4y0z!!!), the next natural question is a custom ROM. The subject may turn out to be slightly trickier than what appears at first sight.
Let's have a discussion thread to brainstorm on this and not wonder off-topic in other places.
I had seen @DragonFire1024 & @Rortiz2 tried to work on that, so feel free to chime in as necessary.
What we have:
HD10 (2017) chipset - MT8173 (2+2 cores), there is an beefier brother to it, MT8176 (2+4 cores). For most practical purposes both chipsets seem almost identical software-wise.
MT8173 was introduced in March 2015 (time of Lollipop domination - Android 5). MT8176 was introduced in October 2016 (getting toward Nougat - Android 7).
The efforts up to date on a custom ROM for this chipset appear to be by @Goayandi, who is still active on XDA, so his work could be used a starting point. I believe @Goayandi was working on Android 7 (Nougat). Here are some of the original links:
XDA : Mediatek MT8173 & MT8176 development
Reddit: Mediatek MT8173 & MT8176 development
Stuff from Amazon for MT8173 (both HD10 2017 and FireTV2) is Lollipop-vintage (Android 5), other devices with these chipsets seem to have reached Nougat (Android 7). It does not appear that there is any known MT8173/MT8176 device with Android 8, or 9 (or is there?). It seems that @diplomatic has an Asus like this with Nougat.
At the moment, it feels a a Nougat custom ROM might be the ceiling for the device, given the difficulties of finding proprietary pieces for MTK chipsets to get Android 8 or 9 going. Now, even Android 7 is still a bit of a challenge, given limited prior success.
More thoughts/ideas? Feel free to fill this thread with random thoughts as much as you want - that's what it's for!!!
Click to expand...
Click to collapse
Hi bibikalka,
Very good idea this thread.
What you can do, is to port a port a ROM of another MT8173 tablet to the FIRE HD10 2017.
This works and I have tested it on my BQ Aquaris M8 (MT8163) it has a similar MTK so I guess it will work. I have ported for example a ROM of an asus zenpad that uses MT8163 and at least the rom boots.
BTW: Oreo on MT8176: https://www.xda-developers.com/alldocube-x-10-5-inch-android-8-1-oreo/
DragonFire1024 said:
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Click to expand...
Click to collapse
Apparently I forgot to add the right files.
give me a moment.
---------- Post added at 06:47 PM ---------- Previous post was at 06:36 PM ----------
DragonFire1024 said:
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Click to expand...
Click to collapse
I have fixed the upload, please use amonet-suez-v1.1.1.zip
DragonFire1024 said:
The one I have and provided is a source to 7.0. looks nicely stocked.
Click to expand...
Click to collapse
But these aren't amazon sources are they?
They probably are missing some drivers then.
But if they are for mt8173 they could be used as a source to patch the amazon-sources.
k4y0z said:
Apparently I forgot to add the right files.
give me a moment.
---------- Post added at 06:47 PM ---------- Previous post was at 06:36 PM ----------
I have fixed the upload, please use amonet-suez-v1.1.1.zip
But these aren't amazon sources are they?
They probably are missing some drivers then.
But if they are for mt8173 they could be used as a source to patch the amazon-sources.
Click to expand...
Click to collapse
I'll provide a link in a few. Trying your fix now.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
Rortiz2 said:
Hi bibikalka,
Very good idea this thread.
What you can do, is to port a port a ROM of another MT8173 tablet to the FIRE HD10 2017.
This works and I have tested it on my BQ Aquaris M8 (MT8163) it has a similar MTK so I guess it will work. I have ported for example a ROM of an asus zenpad that uses MT8163 and at least the rom boots.
BTW: Oreo on MT8176: https://www.xda-developers.com/alldocube-x-10-5-inch-android-8-1-oreo/
Click to expand...
Click to collapse
Excellent find! Here is a review link:
https://forum.xda-developers.com/ge...ldocube-x-review-media-playback-king-t3902539
Alldocube X kind of has 2x of everything compared to HD10 2017, but at 2x price I wonder how fast Oreo would be on HD10 and if 2Gb of RAM would cut it. But this is definitely the device to copy if one wants latest and greatest!
And here is a thread with misc download links for ROMs:
https://forum.xda-developers.com/ge...n/10-5-inch-super-amoled-2560-x-1600-t3821327
bibikalka said:
Excellent find! Here is a review link:
https://forum.xda-developers.com/ge...ldocube-x-review-media-playback-king-t3902539
Alldocube X kind of has 2x of everything compared to HD10 2017, but at 2x price I wonder how fast Oreo would be on HD10 and if 2Gb of RAM would cut it. But this is definitely the device to copy if one wants latest and greatest!
And here is a thread with misc download links for ROMs:
https://forum.xda-developers.com/ge...n/10-5-inch-super-amoled-2560-x-1600-t3821327
Click to expand...
Click to collapse
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
This is great news! I am eagerly awaiting more info about this AOSP ROM
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
ffstudios said:
This is great news! I am eagerly awaiting more info about this AOSP ROM
Click to expand...
Click to collapse
Alright, we have both an eager developer, and a tester!!! Just remember, avoid bricking !
Very recently (March 2019) @wangyiling seems to have put together a LineageOS 15.1 ROM for MT8173/8176 - link, so hopefully we can re-purpose that for HD10. It's great to have an active developer elsewhere looking at the same thing!
It feels that if there is at least something that boots the kernel, it'd be a huge step forward.
bibikalka said:
Alright, we have both an eager developer, and a tester!!! Just remember, avoid bricking !
Very recently (March 2019) @wangyiling seems to have put together a LineageOS 15.1 ROM for MT8173/8176 - link, so hopefully we can re-purpose that for HD10. It's great to have an active developer elsewhere looking at the same thing!
It feels that if there is at least something that boots the kernel, it'd be a huge step forward.
Click to expand...
Click to collapse
If my testing on ROMs caused my brick, we have to be careful. I've been testing and flashing test ROMs for months now and never bricked like this. I think I may know what happened and if I'm right, I'm not sure what effect if any this will have on flashing a rom. According to the fstab.mt8173 file in the root directory, the partitions we flash for a rom, aren't part of the EMMC: data, system, cache are all ext4. All other partitions are however EMMC. So if I recall correctly, I did list the system as EMMC in the build script, but did intend to remove it. I made a last minute adjustment to the script and didn't change that part though.
https://forum.xda-developers.com/showpost.php?p=78542898&postcount=618
Sent from my MotoG3 using XDA Labs
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
I too am willing to test. Just let me know and I'll be sure to wear my best testing pants. [emoji41]
Sent from my SM-G9650/DS running stang5litre Pie ROM
AOSP ROM TEST 1 (suez)
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: Removed
INSTALL INSTRUCTIONS:
- Boot TWRP
- Make NANDROID BACKUP
- Make wipes
- Format data
- Install ROM
- Reboot
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Regards!
Rortiz2 said:
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: https://mega.nz/#!C5dEQIKR!14BcGTiaT-xsrPUc-AxmWrTLj92Y5A2VgeNX2VA1uUE
INSTALL INSTRUCTIONS:
- Boot TWRP
- Make NANDROID BACKUP
- Make wipes
- Format data
- Install ROM
- Reboot
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Regards!
Click to expand...
Click to collapse
Sounds good to me. Won't have a chance till later this afternoon/evening to give it a whirl, but when I do I'll definitely share my results and any information that may be useful. Thank you!
Sent from my SM-G9650/DS running stang5litre Pie ROM
Rortiz2 said:
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: https://mega.nz/#!C5dEQIKR!14BcGTiaT-xsrPUc-AxmWrTLj92Y5A2VgeNX2VA1uUE
...
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Click to expand...
Click to collapse
Which AOSP version is this? Could you try that Oreo Lineage stuff from @wangyiling at some point as well?
One of these days we'll have a ROM developer and a tester within the same person Too bad we've lost @DragonFire1024 since his tablet got bricked
Hi, since Xiaomi decided to depreciate rom support for our mi4c, everyday i try to find a replacement firmware. But here is what i found: official lineage removed mi4c since april, last rom is 0209 because they no longer support 14.1 version. AICP lastest version is 2702, no longer update. There're many unofficial roms on 4pda, but all of them now have their support ended because the devs move to new devices. There's only Mokee that support nightly 9.0 and release 8.1 version everyday and monthly. I try to find something like "mi4c treble" but no hope, the repository is created but empty, not like mi4 that has unofficial treble support. Maybe i need to buy a new phone? But my phone is still in good condition with no problem so far... :crying::crying::crying:
Yeah, sad but true. I also gave up on new rom, so i still use the 15.1 LineageOS one (20180810). Good rom, no problems here, but wouldnt mind some security updates.
The phone works nicely though and apart from battery lasting a day, i dont see any problems. I guess we will have to move to new phone if we want to see some updates rom.
I resized device partition table in order to support android treble.
I will make custom recovery image which is support android treble.
Maybe our device is ready to support android treble by then
added
I made treble-enabled recovery image now and it works well.
I will release the solution soon.
dla5244 said:
I resized device partition table in order to support android treble.
I will make custom recovery image which is support android treble.
Maybe our device is ready to support android treble by then
added
I made treble-enabled recovery image now and it works well.
I will release the solution soon.
Click to expand...
Click to collapse
Thank you, i'm waiting for your topic
AgiZ10 said:
Yeah, sad but true. I also gave up on new rom, so i still use the 15.1 LineageOS one (20180810). Good rom, no problems here, but wouldnt mind some security updates.
The phone works nicely though and apart from battery lasting a day, i dont see any problems. I guess we will have to move to new phone if we want to see some updates rom.
Click to expand...
Click to collapse
Is that the one without vibration support?
https://gitlab.e.foundation/e/wiki/en/wikis/device/libra/install
it's a fork of LineageOS, still being updated
haven't tested it yet
This is update of lineage-16.0.
https://androidfilehost.com/?w=files&flid=289411
wRAR_ said:
Is that the one without vibration support?
Click to expand...
Click to collapse
Yes, that is the one.
Tfgru said:
https://gitlab.e.foundation/e/wiki/en/wikis/device/libra/install
it's a fork of LineageOS, still being updated
haven't tested it yet
Click to expand...
Click to collapse
Anyone tested it yet? It seems /e/ is sort of microg. how is it different?
Autines said:
This is update of lineage-16.0.
https://androidfilehost.com/?w=files&flid=289411
Click to expand...
Click to collapse
Why is this not on this forum, and where is the development thread being discussed? Are there any problems with it? Anyone tested it?
dla5244 said:
I resized device partition table in order to support android treble.
I will make custom recovery image which is support android treble.
Maybe our device is ready to support android treble by then
added
I made treble-enabled recovery image now and it works well.
I will release the solution soon.
Click to expand...
Click to collapse
Great news, we're waiting for
AgiZ10 said:
Anyone tested it yet? It seems /e/ is sort of microg. how is it different?
Click to expand...
Click to collapse
/e/ is a fork of lineage and based on lineage 14.1 for our phone, with microg pre installed. They use a different default launcher, bliss
It works well and is easy to tweak if we dont like the launcher or default apps.
Anyway since our phone is no longer maintained i've decided to build lineage 14.1 for myself.
I'll do it once or twice a month when there are updates.
If anyone need it check here :
androidfilehost.com/?w=files&flid=299596
corwinux said:
/e/ is a fork of lineage and based on lineage 14.1 for our phone, with microg pre installed. They use a different default launcher, bliss
It works well and is easy to tweak if we dont like the launcher or default apps.
Anyway since our phone is no longer maintained i've decided to build lineage 14.1 for myself.
I'll do it once or twice a month when there are updates.
If anyone need it check here :
androidfilehost.com/?w=files&flid=299596
Click to expand...
Click to collapse
thanks
Mokee have a good android 9 ROM, been using it for months and no issues:
https://download.mokeedev.com/libra.html
Also WJXXBSH recently published new Lineage 16 and even 17! https://androidfilehost.com/?w=files&flid=299149
I have not tried it yet, but at least WJXXBSH is keeping our device live.
how about lineage 16 from havoic 3.1 (https://sourceforge.net/projects/havoc-os/files/libra/)
At least it work fine for me on mi4c
Does anyone know any developer who would be willing to make android-10 ROMS for our P2 or is Pie the last update for this awesome phone?
Kinngk said:
Does anyone know any developer who would be willing to make android-10 ROMS for our P2 or is Pie the last update for this awesome phone?
Click to expand...
Click to collapse
Hopefully not as the developers said that as long as they have this phone working they'll keep the development going. :fingers-crossed::fingers-crossed:
Well, I hope there will be future development for this phone too. I'm using one for more than 2 years, and battery still rocks, it sure lasts more than any flagship !
as far as i can tell, mike is working on lineage os 17.
so at least one android 10 rom might be coming soon
ryd3r89 said:
Well, I hope there will be future development for this phone too. I'm using one for more than 2 years, and battery still rocks, it sure lasts more than any flagship !
Click to expand...
Click to collapse
Yea bro same, more than 2.5 years and still i get SOT of 6-7 hours.
Whenever i think of buying a new phone, i look at my p2 and i stop. Its still so smooth cuz of the ROMS and charges under 1 hour and 15 minutes.
This phone is the best purchase i ever had. So i want development to keep going on, atleast for 1 more iteration of Android. Then i'll maybe buy Redmi K20 pro next year cuz it'll also have good development in future.
@Erazor84 that's good news brother. But I'll wait for AOSP xtended Android-10 (if it ever comes)
Bcuz i used their Oreo build and now using pie, and i found them the best among all of'em.
Erazor84 said:
as far as i can tell, mike is working on lineage os 17.
so at least one android 10 rom might be coming soon
Click to expand...
Click to collapse
My guess would be at least 2 more ROMs :fingers-crossed: one from @VladSor and second from @Fullbustah as they are consistent with porting/ developing the ROMs such as Havoc, Syberia, Bootleggers and POSP for P2.
But of course, we need a reliable vendor upgrade first.
Xiaomi redmi note 4 which has the same Specs has just got lineage 17.
mido hamdy said:
Xiaomi redmi note 4 which has the same Specs has just got lineage 17.
Click to expand...
Click to collapse
We're next, I guess :fingers-crossed:
Kinngk said:
Does anyone know any developer who would be willing to make android-10 ROMS for our P2 or is Pie the last update for this awesome phone?
Click to expand...
Click to collapse
Yus coming 10
Astridxx said:
Yus coming 10
Click to expand...
Click to collapse
You're the man buddy!:highfive:
Only sgsi are coming for our device No rom yet , and those gsi are also ****ty...
shivang_bagh said:
Only sgsi are coming for our device No rom yet , and those gsi are also ****ty...
Click to expand...
Click to collapse
Can you tell me please what is the meaning of gsi ? Or sgsi?
is there any chance for android 10 for havoc os?
As per my understanding:
HACKIMTOSH said:
Can you tell me please what is the meaning of gsi ? Or sgsi?
Click to expand...
Click to collapse
Generic System Image (GSI) is pure untouched Android released by Google for treble enabled phones with a designated vendor partition.
Semi GSI (SGSI) is a customized GSI with features and name of a custom ROM and it can also be installed on treble enabled phones with a designated vendor partition.
alirazaagha said:
Generic System Image (GSI) is pure untouched Android released by Google for treble enabled phones with a designated vendor partition.
Semi GSI (SGSI) is a customized GSI with features and name of a custom ROM and it can also be installed on treble enabled phones with a designated vendor partition.
Click to expand...
Click to collapse
Now i see , thank you bro
How is Android 10 on Lenovo P2? Is it stable? I am on stock Rom Android 7. How to get from stock to Android 10?
Thank you.
Astridxx said:
Yus coming 10
Click to expand...
Click to collapse
The following url https://forum.xda-developers.com/lenovo-p2/development/rom-aosip-derpfest-t3981193 will give You access on this forum to the thread concerning AOSiP-10-DerpFest-Alpha-kuntao-20191009.zip which is the first alpha version of the first Android 10 custom rom dedicated to the Lenovo P2.
If You are interested in testing this Android 10 rom, just follow the installation instructions given on the first page of the thread.
If I well understood, I think that someone, maybe mikeioannina ?, should now be working on a Android 10 rom LineageOS 17. If this is the case, all we can do is to be patient.
You will note that from now on we must say Android 10 instead of Q as asked by Google. So, next year, the next version of Android will be Android 11 and not R.
Below is the lineageos github page for Kuntao (Lenovo P2a42), the branch is on 17.0, but it seems it hadn't been developed on in 4 months, but i don't know how these things go...
Github Kuntao: https://github.com/LineageOS/android_device_lenovo_kuntao
Roms for kuntao
slovantes said:
Below is the lineageos github page for Kuntao (Lenovo P2a42), the branch is on 17.0, but it seems it hadn't been developed on in 4 months, but i don't know how these things go...
Github Kuntao: https://github.com/LineageOS/android_device_lenovo_kuntao
Click to expand...
Click to collapse
Hello I've tried all of the versions on my KUNTAO, at the beggining very laggy now better, there are some ROMS which you can use w/out a problem if you can live w/out some of the features like the FP GESTURES OR AA CONNECTIVITY.
HAVOC 3.0 (NOT THE TREBLE VERSION) to me is the best option till this post furthermore I don't know.
CHHERS
So, We are half a year further from the last post in this thread, any news on the stability and performance of the android 10 rom's? Im right now on Crdroid Pie ROM and except fingerprint kicking the bucket everything is working flawlessly. Any stable and well performing 10 rom's out there, or should we wait a little longer?
Update: DO NOT TRY TO PAY!!! THE GUIDE IS BADLY OUTDATED. JUST USE THE RESOURCES AND FREE METHODS.
If you want to try the paid method, you should definitely get in touch with the seller first. I don't know whether the previous sellers are active or not.
If you want to inform me of something important, please `@me`, (I missed many replies in the past years)
---
There seems to exist a new method: It is said to work on Qualcomm devices.
First, dump frp partion, then edit the value to 1 at 7fff0, finally, flash the modified frp image. then you can use fastboot command to unlock your phone.
This new method shall work for for ODM devices like 16T, 16x, 16xs and Note9 and so on. see FRP Method.
Below is the original post:
The original post has been removed, since it's outdated and I almost finished the English version tutorial on Github.
You can see it on github.
BTW, it's really difficult to use XDA's text editor.
You can download the TWRP of 16s here
it's a start, is there anyone who has already tried a gsi?
Good news for us Meizu users! Hope this is just a first step towards some good modding ?
Will this also work on Meizu Note 9?
adrxano said:
Will this also work on Meizu Note 9?
Click to expand...
Click to collapse
A new method has been released on 4pda, which supports almost all MEIZU devices using Qualcomm Proccessor. This is the original link 4pda.ru/forum/index.php?showtopic=961552&st=960#entry90949224
Loni626 said:
it's a start, is there anyone who has already tried a gsi?
Click to expand...
Click to collapse
I tried MIUI 11 and Flyme 8 , almost everything does not work on MIUI 11, it can boot into system, but the launcher doesn't work. Almost everything works fine on Flyme, except Bluetooth and Camera
I will try to rewrite an English version
The Chinese version has been moved to wiki, I'm planning to rewrite an English version similar to the Chinese version.
sukanka said:
The Chinese version has been moved to wiki, I'm planning to rewrite an English version similar to the Chinese version.
Click to expand...
Click to collapse
My firmware is 8.19.11.11 daily(16th Global device). Do i have a chance to unlock bootloader?
Lord Melkor said:
My firmware is 8.19.11.11 daily(16th Global device). Do i have a chance to unlock bootloader?
Click to expand...
Click to collapse
Sure, the new method applies to almost all devices, all versions. You can have a look at my github repository. I will edit the original post as soon as I can post links. BTW, is there any netdisk you guys use frequently? I don't know where to put the TWRP so that you can download easily.
sukanka said:
Sure, the new method applies to almost all devices, all versions. You can have a look at my github repository. I will edit the original post as soon as I can post links. BTW, is there any netdisk you guys use frequently? I don't know where to put the TWRP so that you can download easily.
Click to expand...
Click to collapse
You can use yandex.disk or google drive.
But you say about downgrade. Does the new method ignore the firmware version ?
Lord Melkor said:
You can use yandex.disk or google drive.
But you say about downgrade. Does the new method ignore the firmware version ?
Click to expand...
Click to collapse
yes, the new method applies to almost all versions, I have not updated the original post, because I have not prepared the English Version well on Github. You can have a look at github.com/sukanka/MEIZU16S_unlock_tutorial/wiki/Guide-to-Unlock-Your-MEIZU-Device
A new tutorial has been released on github
I must post in this way, as I'm not allowed to post links now. The Tutorial is at
github.com/sukanka/MEIZU16S_unlock_tutorial/wiki/Guide-to-Unlock-Your-MEIZU-Device
copy and paste this into your browser.
Any custom rom for meizu 16th without treble rom? And please add in phone cattegory meizu 16th on xda
inclr said:
Any custom rom for meizu 16th without treble rom? And please add in phone cattegory meizu 16th on xda
Click to expand...
Click to collapse
There seems to be custom ROMs for MEIZU 16th, I've seen Lineage, havoc, and mokee before. But i don't know how do these ROMs work. Anyway, I use 16s, not 16th. Besides, I don't know how to add a new phone category.
BTW, it's said that the kernel source of the 16 series will be released, maybe next year. And there are plans to upgrade the Android version of the 16 series.
sukanka said:
There seems to be custom ROMs for MEIZU 16th, I've seen Lineage, havoc, and mokee before. But i don't know how do these ROMs work. Anyway, I use 16s, not 16th. Besides, I don't know how to add a new phone category.
BTW, it's said that the kernel source of the 16 series will be released, maybe next year. And there are plans to upgrade the Android version of the 16 series.
Click to expand...
Click to collapse
Who said that?
inclr said:
Who said that?
Click to expand...
Click to collapse
a man who released some official ROMs that can be used to downgrade the firmware of the devices.
sukanka said:
I tried MIUI 11 and Flyme 8 , almost everything does not work on MIUI 11, it can boot into system, but the launcher doesn't work. Almost everything works fine on Flyme, except Bluetooth and Camera
Click to expand...
Click to collapse
You try another gsi rom? I want try pixel gsi or havoc, but I don't think was supported at 100%, probably lost taptic engine and other features... If have problems with this gsi and I want reinstall flyme stable, will be a problem?
Loni626 said:
You try another gsi rom? I want try pixel gsi or havoc, but I don't think was supported at 100%, probably lost taptic engine and other features... If have problems with this gsi and I want reinstall flyme stable, will be a problem?
Click to expand...
Click to collapse
No problem. If your phone becomes a brick, you can follow the unbrick tutorial to save your phone. But you are suggested to have glance at the tutorial before you go.
As reported by others, fingerprint and Mengine (taptic engine) don't work.
I am on havoc 2.9. Fingerprint mengine and mtp not work. But other features work fine
First telegram gruop for rom develop in meizu 16series: @Meizugsi
(nothing has been published yet, hopefully in the interest of some developers soon)