Related
I have been trying to install viper4android using magisk but it keeps asking for drivers installation any ideas
V4a is one of the main reasons am rooting
Iloudsan said:
I have been trying to install viper4android using magisk but it keeps asking for drivers installation any ideas
V4a is one of the main reasons am rooting
Click to expand...
Click to collapse
From what I've read in to, V4A isn't yet compatible with the Mate 9. I believe there is bug discussions on github abiut it. I'll update with a link if I find it.
I've been trying to get it working for ages and it isnt working for me. Must be a bug in the driver.
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
Ok so I've already tried the solution for Pixel 2 devices provided here:
https://forum.xda-developers.com/pixel-2-xl/help/android-q-viper4android-compatible-t3929914/page2
Unfortunately it doesn't seem to work on the OG Pixel. I've tried combining it with Audio Modification Library and Audio Compatibility Patch to no avail.
Has anyone has got it working so far on android Q? Thinking about downgrading to Pie at this point.
Thank you for any help
jgibson667 said:
Ok so I've already tried the solution for Pixel 2 devices provided here:
https://forum.xda-developers.com/pixel-2-xl/help/android-q-viper4android-compatible-t3929914/page2
Unfortunately it doesn't seem to work on the OG Pixel. I've tried combining it with Audio Modification Library and Audio Compatibility Patch to no avail.
Has anyone has got it working so far on android Q? Thinking about downgrading to Pie at this point.
Thank you for any help
Click to expand...
Click to collapse
I got it working, head over this thread. From this page, I wrote how to install it, then some others reported that selinux must be set to permissive. Than it will work :good:
TENN3R said:
I got it working, head over this thread. From this page, I wrote how to install it, then some others reported that selinux must be set to permissive. Than it will work :good:
Click to expand...
Click to collapse
What a legend, thank you very much! :victory:
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)
Hope this is a good place to ask. I had to get the old Oneplus 7 pro back and Renovate ICE is pretty much dead. I'm not sure if I want to go all the way to Android 12, since I think Oneplus only had it up to 11. On the downloads for Lineage OS though, they only go back to version(s) 19.x which is Android 12.
Help a brother out anybody?
Thanks.
teddyearp said:
Hope this is a good place to ask. I had to get the old Oneplus 7 pro back and Renovate ICE is pretty much dead. I'm not sure if I want to go all the way to Android 12, since I think Oneplus only had it up to 11. On the downloads for Lineage OS though, they only go back to version(s) 19.x which is Android 12.
Help a brother out anybody?
Thanks.
Click to expand...
Click to collapse
Lineage OS 20, based on Android 13, was only released last month. Give it some time.
Thanks for the reply, but I am asking for an older version that the link(s) for which no longer exist, that I can find.
ethical_haquer said:
Lineage OS 20, based on Android 13, was only released last month. Give it some time.
Click to expand...
Click to collapse
teddyearp said:
Thanks for the reply, but I am asking for an older version that the link(s) for which no longer exist, that I can find.
Click to expand...
Click to collapse
An older version of what?
I'm looking for version 18.x of Lineage OS which is based upon Andriod 11. It is a custom ROM for the Oneplus 7 pro.
ethical_haquer said:
An older version of what?
Click to expand...
Click to collapse
teddyearp said:
I'm looking for version 18.x of Lineage OS which is based upon Andriod 11. It is a custom ROM for the Oneplus 7 pro.
Click to expand...
Click to collapse
Yes, it looks like they now only support 19.1 and 20 on that device. All 18.1 links are dead.
teddyearp said:
I'm not sure if I want to go all the way to Android 12, since I think Oneplus only had it up to 11.
Click to expand...
Click to collapse
Part of the reason people install custom ROMs is to extend the support for their device.
ethical_haquer said:
Yes, it looks like they now only support 19.1 and 20 on that device. All 18.1 links are dead.
Part of the reason people install custom ROMs is to extend the support for their device.
Click to expand...
Click to collapse
True, but without an actual working stock ROM with the actual Android version you want to build for the device, you can no longer extract the /vendor files which leads to some things not working properly. So it's, "Hey look, I've got a version of Android on this phone you won't" with the qualifier "And everything works." Meaning it is a port. I've been using customer ROMS on all my Android phones for about 12 years or so now started with the Droid A855. Hell I used to flash different firmware on the old flip phones before.
And the whole reason for this thread is what you said. There appears to be no links for version earlier than 19.x, so I asked hopping that maybe someone had one laying around they could share or knew of a mirror or other link. I used to save and host lots and lots of ROMs on my personal server and used to link those repositories in my sig here and many other places.
So thank you for your replies.