Are there any working ROMs on the Onn 8" that are running Android 10? I wanna have the latest version of Android.
antoinejr1111 said:
Are there any working ROMs on the Onn 8" that are running Android 10? I wanna have the latest version of Android.
Click to expand...
Click to collapse
All the android 10 GSI's are too large for our system partition. The only one that installs is PHH's 10 v209 but video playback isnt possible outside of YouTube. Its also very unstable, it required several resets do to even simple modifications.
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
All the android 10 GSI's are too large for our system partition. The only one that installs is PHH's 10 v209 but video playback isnt possible outside of YouTube. Its also very unstable, it required several resets do to even simple modifications.
Click to expand...
Click to collapse
Yeah we need a repartitioning utility to increase /system size. I believe some of the GSI Android 10 ROMs would be great for the Onn tablets if only the allocated /system size was larger. Has anyone tried doing this via TWRP? If /system could be formatted to a larger size, the /userdata partition could be decreased in size to compensate.
Viva La Android said:
Yeah we need a repartitioning utility to increase /system size. I believe some of the GSI Android 10 ROMs would be great for the Onn tablets if only the allocated /system size was larger. Has anyone tried doing this via TWRP? If /system could be formatted to a larger size, the /userdata partition could be decreased in size to compensate.
Click to expand...
Click to collapse
Another option would be a custom rom built for our devices. Or maybe a modified gsi with only the sruff needed for our device. The img size would be much smaller. Things like fingerprint unlock and such is just waisting space.
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
Another option would be a custom rom built for our devices. Or maybe a modified gsi with only the sruff needed for our device. The img size would be much smaller. Things like fingerprint unlock and such is just waisting space.
Click to expand...
Click to collapse
True. An image kitchen can be used to decompile the GSI so that non-essential apps and services could be deleted. A slimmed down Android !10 GSI would surely work on this device.
So i tried the new PHH 10 V214. It does install and boot in the same we we install his Pie versions. But, it still cant play video outside of youtube app/website. Still a vendor problem i would assume. Havent tested it long enough to know if the other issues exist yet or not. Im restoring my backup of bliss rom pie.
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
So i tried the new PHH 10 V214. It does install and boot in the same we we install his Pie versions. But, it still cant play video outside of youtube app/website. Still a vendor problem i would assume. Havent tested it long enough to know if the other issues exist yet or not. Im restoring my backup of bliss rom pie.
Sent from my SM-G975U1 using XDA Labs
Click to expand...
Click to collapse
I tried to install PHH 10 v215 (both A/B image and A-only) - but I cannot get it to boot. It does not go past the ONN logo and then reboots. Have made backups of all partitions using TWRP.
Tried both methods - fastboot flash system and TWRP install image.
Also tried the 9.0 pixel experience. Same result.
Any ideas what could be going wrong?
angadsg said:
I tried to install PHH 10 v215 (both A/B image and A-only) - but I cannot get it to boot. It does not go past the ONN logo and then reboots. Have made backups of all partitions using TWRP.
Tried both methods - fastboot flash system and TWRP install image.
Also tried the 9.0 pixel experience. Same result.
Any ideas what could be going wrong?
Click to expand...
Click to collapse
At the boot logo connect to adb. Make sure its recognized and issue the following command: adb shell setprop debug.stagefright.ccodec 0
Sent from my SM-G975U1 using XDA Labs
Viva La Android said:
True. An image kitchen can be used to decompile the GSI so that non-essential apps and services could be deleted. A slimmed down Android !10 GSI would surely work on this device.
Click to expand...
Click to collapse
How can I get this image kitchen with Windows 10 or Linux? And possibly how to decompress the image.
antoinejr1111 said:
How can I get this image kitchen with Windows 10 or Linux? And possibly how to decompress the image.
Click to expand...
Click to collapse
Personally, I use @SuperR.'s Kitchen for cooking Android ROMs. The kitchen allows you, for example, to toss in a system.img of an Android 10 based ROM. The kitchen decompiles the image into a workable /system folder and full filesystem. You are given options to debloat, add root, BusyBox, deodex, zipalign, etc. You can also toss in the boot.img and vendor.img from the Android 10 ROM and the kitchen will create for you the META-INF file with updater-script and update-binary. It will add your symlinks, permissions and all Edify commands needed to mete out a TWRP flashable Android 10 ROM with all the customizations you've added. The kitchen is available in both a free and a donate version (which is $15 I think). It's available for Linux and Windows based systems. Here is a link to the Windows version I use. Well worth the humble amount of money he asks for the donate version, as you'll see in the thread. https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
Viva La Android said:
Personally, I use @SuperR.'s Kitchen for cooking Android ROMs. The kitchen allows you, for example, to toss in a system.img of an Android 10 based ROM. The kitchen decompiles the image into a workable /system folder and full filesystem. You are given options to debloat, add root, BusyBox, deodex, zipalign, etc. You can also toss in the boot.img and vendor.img from the Android 10 ROM and the kitchen will create for you the META-INF file with updater-script and update-binary. It will add your symlinks, permissions and all Edify commands needed to mete out a TWRP flashable Android 10 ROM with all the customizations you've added. The kitchen is available in both a free and a donate version (which is $15 I think). It's available for Linux and Windows based systems. Here is a link to the Windows version I use. Well worth the humble amount of money he asks for the donate version, as you'll see in the thread. https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
Click to expand...
Click to collapse
Do you think you can break down a version of Android 10 that works for the Onn 8" and send it to me? Please?
antoinejr1111 said:
Do you think you can break down a version of Android 10 that works for the Onn 8" and send it to me? Please?
Click to expand...
Click to collapse
My only dilemma there is that I've got multiple projects going right now for various LG and Motorola devices. However, I fully plan on future development for the Onn series of tablets (primarily the newer Onn Surf series due to Treble support). As soon as my schedule permits, I'm on it. Here's the beauty with Project Treble: if an Android 10 GSI will boot on the Onn Surf 10.1, it is almost certain that it will also boot on the Surf 8. Out of curiosity, what is the allocated /system partition size on the Onn Surf 8? Is it the same as the Surf 10.1? Also, I noticed recently that there are some rather slim GSI builds of Android 10 (Go Edition). Some of these might be worth looking into.
Related
Hi guys!
I have noticed that developers continue to develop new Android versions for the HD2, there is always something of new (KitKat it's already avaible).
Developers make Android Roms bootable from MicroSD through a partition without delete W.M.
They can edit the Linux Kernel in any way.
Surely you know projects like XDAndroid that use the "haret.exe" file.
But which sofwares and which coding languages do they use to "build" these Roms?
I read about
-Eclipse and Android Studio
-Gedit and Nano
-Kate and Vim
...
What do you know? Help me
Mich-C said:
What do you know? Help me
Click to expand...
Click to collapse
ROMs/kernels are written in C / C++. And are built/compiled usually from the terminal in a linux OS.
More info here -> http://xda-university.com/as-a-developer/introduction-how-an-android-rom-is-built.
HypoTurtle said:
ROMs/kernels are written in C / C++. And are built/compiled usually from the terminal in a linux OS.
More info here -> http://xda-university.com/as-a-developer/introduction-how-an-android-rom-is-built.
Click to expand...
Click to collapse
So Is the procedure to make Roms for native Android phones the same of the one to make Roms for not-native Android phones?
Right?
Mich-C said:
So Is the procedure to make Roms for native Android phones the same of the one to make Roms for not-native Android phones?
Right?
Click to expand...
Click to collapse
Well, yeah...
When you compile you rom you need to imstall ot this way:
You need 3 things:
1. Ext4 partition on your sdcard
2. Some recovery build for booting over haret ( you can take sd twrp's)
3. Your rom in flashable zip.
When you have all that, make a folder in your sd card, put your android flashable zip and extract your sd recovery there. Then run haret from that folder, and flash your android trough recovery. Then reboot, and go to the folder you have made for your android build, there should be a folder called NativeSD. Go in it an run haret an you will be booting in your android
ADD: You need to install w/ NaticeSD method only
Sent from my leo using XDA Premium 4 mobile app
Mich-C said:
So Is the procedure to make Roms for native Android phones the same of the one to make Roms for not-native Android phones?
Right?
Click to expand...
Click to collapse
In a way yes. A Rom is made up of a kernel which is bundled with a ramdisk (essentially boot instructions). to make a boot image.
On top of which is the system files which make up the OS itself. During compilation device specific details are taken from the files and baked in to the files that'll be running on the device itself.
The problem with making ROMs for non-Android devices is getting the device specific stuff - the HD2 is close enough / the same as a couple android phones (Nexus One / Desire S (??)) so getting these files was relatively easy.
You've mentioned haret.exe, which i believe just needs a rearranged ramdisk, other than being able to flash an open bootlader (magldr / lk in the HD2's case) that would be the only way to run android on a WM device.
The real question is, do you have working android kernel for your device..
Sent from my leo using XDA Premium 4 mobile app
I believe the next step for the Droid Turbo are system images.
With MofoRoot, the next goal is to create a system image that is lollipop 5.1 and has root.
I've only flashed system images that were created up to this point but I'd be interested in learning how to take apart a system image and go as far as changing/manipulating it have wifi tether and root. Anyone have any good suggestions on where to start learning?
I plan to collect what I discover in this thread.
windraver said:
I believe the next step for the Droid Turbo are system images.
With MofoRoot, the next goal is to create a system image that is lollipop 5.1 and has root.
I've only flashed system images that were created up to this point but I'd be interested in learning how to take apart a system image and go as far as changing/manipulating it have wifi tether and root. Anyone have any good suggestions on where to start learning?
I plan to collect what I discover in this thread.
Click to expand...
Click to collapse
You will need a different kernel to work with a 5.1 or 5.0 system image. We cannot flash a kernel with this method yet just system images.
Right, so the only thing we can do are modified "roms" based on stock. Can't flash recovery or kernel since those are on separate partitions.
This tool, yaffy, might be of some help. I'm downloading it now to see if it works...
timmyk465 said:
This tool, yaffy, might be of some help. I'm downloading it now to see if it works...
Click to expand...
Click to collapse
Not going to work. You need to mount an ext4 image which is not what that tool is designed for. I'm currently doing so by using Linux and mounting the image as a loop device. I can create a guide for doing so if there's demand.
Ekkoria said:
Not going to work. You need to mount an ext4 image. I'm currently doing so by using Linux and mounting the image as a loop device. I can create a guide for doing so if there's demand.
Click to expand...
Click to collapse
I'd definitely be interested in a guide. I just wish there was a tool for windows that would work.
You can do it on windows but it's way easier on Linux.
I'm gonna get Linux back up and running and see what I can cook up.
Ekkoria said:
Not going to work. You need to mount an ext4 image which is not what that tool is designed for. I'm currently doing so by using Linux and mounting the image as a loop device. I can create a guide for doing so if there's demand.
Click to expand...
Click to collapse
All I want to do is build a flashable img with a modified hosts file. I've found a guide for mounting the image as a loop (which Ive done....) the issue Im running into is changing permissions to be able to actually edit the file once its mounted.
Guess I'll read more and keep tinkering..
ntxct said:
All I want to do is build a flashable img with a modified hosts file. I've found a guide for mounting the image as a loop (which Ive done....) the issue Im running into is changing permissions to be able to actually edit the file once its mounted.
Guess I'll read more and keep tinkering..
Click to expand...
Click to collapse
Open your file manager as root, then open the file.
---------- Post added at 11:49 PM ---------- Previous post was at 11:44 PM ----------
I wrote up and posted a quick guide (which probably sucks) for this purpose.
I'm proud to present the first dual boot project for the all Exynos7870 and Exynos7880-based Samsung devices. This project started off as a feature in my ROM, but not anymore. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
Donators
A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.
See all of our supporters here
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
Well, Just flash the patched zip file via recovery (Custom Recovery, like TWRP of course)
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads
Here is the latest build : https://www.androidfilehost.com/?fid=962021903579496224
XDA:DevDB Information
DualBoot Patcher APP, Device Specific App for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
lzzy12
Source Code: https://github.com/Mysteryagr/DualBootPatcher
Version Information
Status: Beta
Created 2017-12-03
Last Updated 2017-12-03
thanks bro ,Great Work
Wow Good Work Bro It Will Be Very Useful For Us Bro
??
Great
got error 1 when flashing lineage as second rom
Tried it. It works if I flash the ROM from recovery but if I want to switch to primary using DualBoot utilities it doesn't work. Fortunately I had made a buk up...
One more thing : The secondary ROM detects the SD card as corrupted and needs formatting if installed to external storage :/
Can anybody help my?
I want to install second ROM on sd card, it will be perfect on ext4 separete partition.
I'v tried it.
I install second ROM on sd card (now it have only one partition vfat), but it cycle rebooting. Helps only restore from TWRP recovery.
DualBootUtilities..zip dont work and have an ERROR 1 in TWRP both 3.2.1.0 and 3.1.1.0.
My primary ROM is last oficial Android 6.0.1. , second ROM is [ROM] Stockrom Lite SM-A520F
Primary ROM rooted SuperSu, CSC - BTU, bootloader - A520FXXU4BRC4, PDA - A520FXXS2AQH1, Radio - A520FXXU4BRC1, ROM - A520FXXS4CRE1/A520FOXA4CRD3/A520FXXU4CRD3, Kernel 3.18.14-10911830 [email protected] #1 32-bit
Here is recovery log file
---------- Post added at 12:02 PM ---------- Previous post was at 11:56 AM ----------
May be it is the reason?:
I:Legacy property environment initialized.
mount: mounting /dev/block/mmcblk0p20 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p25 on /data failed: Device or resource busy
Click to expand...
Click to collapse
I have this problem when I go to roms. Anybody know what's wrong?
iloveoreos said:
I have this problem when I go to roms. Anybody know what's wrong?
Click to expand...
Click to collapse
You need root for this to work. Do you have that?
sheepkill15 said:
You need root for this to work. Do you have that?
Click to expand...
Click to collapse
Yes, I'm rooted with magisk. I wonder if it matters what version I am running. I am running stock 8.0 on an A520W.
iloveoreos said:
Yes, I'm rooted with magisk. I wonder if it matters what version I am running. I am running stock 8.0 on an A520W.
Click to expand...
Click to collapse
Oh right. I don't know if op patched something about this, but originally touchwiz roms don't work with DualBoot, not even Hades.
Or, at least, I couldn't get it to work.
sheepkill15 said:
Oh right. I don't know if op patched something about this, but originally touchwiz roms don't work with DualBoot, not even Hades.
Or, at least, I couldn't get it to work.
Click to expand...
Click to collapse
Ok, that makes sense, I tried a different version on my note5 and it didn't work either. The OP said to set Tw rom as primary though, is there a way to do that?
Edit: Would it work to flash lineage os, install dualboot, and then flash touchwiz as primary?
Do ROMs boot normally from an SD card? Or are they a bit slow?
iloveoreos said:
Do ROMs boot normally from an SD card? Or are they a bit slow?
Click to expand...
Click to collapse
Depends on the SD Card ;p
But, in my experience, SD is slower than internal memory
Where to get the DualBootUtilities? Cant find them in this thread. Can I use the official ones from the website? Or can I just install the App and im fine?
iloveoreos said:
Do ROMs boot normally from an SD card? Or are they a bit slow?
Click to expand...
Click to collapse
Did you fixed the error when going to ROMs? Im having the same error and I dont know what to do. Im rooted with magisk on Stock ROM 8.0
simon151102 said:
Did you fixed the error when going to ROMs? Im having the same error and I dont know what to do. Im rooted with magisk on Stock ROM 8.0
Click to expand...
Click to collapse
Try a custom ROM like lineage os and it should fix that error. However, when I updated ramdisk through dual boot on lineage os 16, my internal storage would quit showing up in stock file manager and downloads would fail. Haven't tried on any other ROM s though.
DualBootUtilities.zip?
lzzy12 said:
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
Click to expand...
Click to collapse
Great job ,thanks. I did'nt find the download link "DualBootUtilities.zip"
I am getting an error 1 while flashing a patched ROM. It looks like the ROMs aren't compatible by looking at the logs. Don't know if that is the correct verdict though.
Has anyone tested the DP GSI? It's located at https://developer.android.com/topic/generic-system-image/releases
Tell me how to install it and I will test it out for you.
Can it be installed the same way a phh's via fastboot? I can try tonight possibly. Phh 10 beta didn't 100% work on my 8" due to missing library files for non-youtube video playback. It did install and boot though. Havent tried phh 10 official yet though.
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
Can it be installed the same way a phh's via fastboot? I can try tonight possibly. Phh 10 beta didn't 100% work on my 8" due to missing library files for non-youtube video playback. It did install and boot though. Havent tried phh 10 official yet though.
Sent from my SM-G975U1 using XDA Labs
Click to expand...
Click to collapse
Any luck yet with Official Android 10
antoinejr1111 said:
Any luck yet with Official Android 10
Click to expand...
Click to collapse
Both phh 10 v212 and the android 11 gsi are to large for our system partition. The normal method of getting it installed dosent work.
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
Both phh 10 v212 and the android 11 gsi are to large for our system partition. The normal method of getting it installed dosent work.
Sent from my SM-G975U1 using XDA Labs
Click to expand...
Click to collapse
Google actually mentioned this on the Android 11 GSI page.
I'm not sure if this will work on the Onn tablet and I think it might be risky to do it.
"This version of the Android 11 GSI has the following known issues:
System partition size: GSI + GMS file size (images named gsi_gms_arm64-*) might be bigger than the system partition on your device. When this happens, you might see the following error message when flashing the GSI + GMS image:
Code:
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
Use the following command to delete the product partition and free up space for the system partition. This provides extra space to flash the GSI image:
Code:
fastboot delete-logical-partition product_a
The postfix “_a” should match the slot id of the system partition, such as “system_a” in this example."
As you may know, Android 8 introduced a lot of new features
Including a new feature called "Treble" which is supposed to reduce the time taken to do updates. But how?
Now let me explain a little bit
Every Android version ever made has a folder called Vendor which has all the things needed to be able to let Android communicate to your phone's hardware.
Now after android 8 that same Vendor underwent a few changes.
First being: Now it is a partition in root not a folder in /system
Second: All phones launching with oreo should support treble.
And finally: Now android will always look for /vendor not /system/vendor
So what does this mean for us well this means that because LG and other manufacturers that don't support treble are using a symlink to /system/vendor so we can move /vendor (Copy in this case as if it dosent work I can revert back to normal). But it isn't as simple as that. As of now, I don't know how to make new partitions in the android root. So what other treble porters have done is to make /oem which is mainly empty and free as the vendor and we do have a /oem that is empty and free.
Step three(Doing the hard things)
So I made a flashable zip with only a META-INF and with a shell script to copy and the updater-script to set permissions and make the needed symlink.
Step 3.5 (flashing it)
Does it boot now?
Yes, but with a twist android undo's all my changes and proceeds to boot meaning it is like i did absolutely nothing.
And the old symlink is still there can someone please help me with these problems
In short please help in bringing unofficial treble to the LG V20 on stock oreo or any rom. I will be fine with testing it on my device no problems with that
[email protected] said:
As you may know, Android 8 introduced a lot of new features
Including a new feature called "Treble" which is supposed to reduce the time taken to do updates. But how?
Now let me explain a little bit
Every Android version ever made has a folder called Vendor which has all the things needed to be able to let Android communicate to your phone's hardware.
Now after android 8 that same Vendor underwent a few changes.
First being: Now it is a partition in root not a folder in /system
Second: All phones launching with oreo should support treble.
And finally: Now android will always look for /vendor not /system/vendor
So what does this mean for us well this means that because LG and other manufacturers that don't support treble are using a symlink to /system/vendor so we can move /vendor (Copy in this case as if it dosent work I can revert back to normal). But it isn't as simple as that. As of now, I don't know how to make new partitions in the android root. So what other treble porters have done is to make /oem which is mainly empty and free as the vendor and we do have a /oem that is empty and free.
Step three(Doing the hard things)
So I made a flashable zip with only a META-INF and with a shell script to copy and the updater-script to set permissions and make the needed symlink.
Step 3.5 (flashing it)
Does it boot now?
Yes, but with a twist android undo's all my changes and proceeds to boot meaning it is like i did absolutely nothing.
And the old symlink is still there can someone please help me with these problems
In short please help in bringing unofficial treble to the LG V20 on stock oreo or any rom. I will be fine with testing it on my device no problems with that
Click to expand...
Click to collapse
There was a thread on here awhile back about treble and as I recall it was eventually determined that treble wouldn't work on our phones
Sent from my LG-H910 using XDA Labs
cnjax said:
There was a thread on here awhile back about treble and as I recall it was eventually determined that treble wouldn't work on our phones
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Well that is really sad