Tested on my Mi Pad 5 Pro 12.4"(dagu) using elish's ROM.
Step to install:
1. Download FastbootEnhance.
2. Download ArrowOS ROM (Xiaomi/elish), and unzip it. There should be a payload.bin inside.
As elish (Mi Pad 5 Pro) and dagu (Mi Pad 5 Pro 12.4") uses the same SoC, it should be fine. But still, unverified if further problems occurs.
3. Either backup the boot and vendor_boot, or download a stock firmware and extract from it.
小米社区
web.vip.miui.com
4. Under fastbootd (fastboot boot fastboot), use FastbootEnhance to flash the payload.bin.
5. Re-enter to fastbootd, use
Code:
fastboot flash boot boot_stock.img
to flash the boot img back to the vendor one.
6. fastboot reboot, and then unplug the cable.
Then, fastboot reboot. And the ArrowOS should boot.
Current issue:
camera not working
NOTE:
not sure if
fastboot --disable-verity --disable-verification flash vbmeta_ab vbmeta.img
is needed
What do you think are the major changes now with the ArrowOS?
CauAguiar said:
What do you think are the major changes now with the ArrowOS?
Click to expand...
Click to collapse
I just found that the UI and overall experience is better than LineageOS.
And also the Pad is on the official support list of ArrowOS.
I have flashed on my mipad 5 pro 12.4 , however, sound is missing from the system.
spacezmonkey said:
I have flashed on my mipad 5 pro 12.4 , however, sound is missing from the system.
Click to expand...
Click to collapse
Same for me. Tried TrebleApp, using
Code:
am start -n me.phh.treble.app/.TopLevelSettingsActivity
to call at adb shell, but still not working.
does this work for enuma as well?
Does the Xiaomi Pen work on this Rom?
niveZz said:
does this work for enuma as well?
Click to expand...
Click to collapse
I am also very much interested using this on my: Mi Pad 5 Pro 5G "Enuma".
@All If this doens´t work on "Enuma" - can this be adapted?
@kokomicat
Really interested in this. Any news? Also I dont quiete understand, "no system sounds" means no notification sounds etc. or no sound at all like from youtube spotify etc...?
Thx
FastbootEnhance can be used to flash stock firmware of recovery version. The recovery one is more updated then the fastboot one. So more benefits on fixing firmware issues.
For those who have problems with sound issues, try disable the sound effect by following these steps:
1. Go to Settings
2. Enter Phh Treble Settings
3. Under Qualcomm features, click off all the audio and sound related functions.
4. Under Misc features, click off Disable audio effects.
The above solutions work for uncompatible features of the firmware being used by the ROM system.
Hope this helps.
Thank you for the nice tutorial of how to flash GSI ROM with FastbootEnhance.
I Tried the steps, No Errors, but after Last fastbook reboot it just Boots to normal MIUI?
Any Tips?
siamese007 said:
FastbootEnhance can be used to flash stock firmware of recovery version. The recovery one is more updated then the fastboot one. So more benefits on fixing firmware issues.
For those who have problems with sound issues, try disable the sound effect by following these steps:
1. Go to Settings
2. Enter Phh Treble Settings
3. Under Qualcomm features, click off all the audio and sound related functions.
4. Under Misc features, click off Disable audio effects.
The above solutions work for uncompatible features of the firmware being used by the ROM system.
Hope this helps.
Thank you for the nice tutorial of how to flash GSI ROM with FastbootEnhance.
Click to expand...
Click to collapse
Hello, I wasn't able to find the setting for "Phh Treble Setting". there is no such option in my "setting". Anyway i have flashed Gapp version of Arrow OS.
spacezmonkey said:
Hello, I wasn't able to find the setting for "Phh Treble Setting". there is no such option in my "setting". Anyway i have flashed Gapp version of Arrow OS.
Click to expand...
Click to collapse
It means this ROM is modified to suit elish device. So you need to use some apps to modify the system settings manually to fix the audio effects that are not compatible with the stock firmware.
I am using A13 Arrow GSI ROM. Everything works fine after disabling all the audio effect features of the ROM system. Except Xiaomi peripherals are not compatible.
update on my attempt..
i tried quite a few GSI rom with phh treble setting, after i disable the audio effects, it is still not working.
spacezmonkey said:
update on my attempt..
i tried quite a few GSI rom with phh treble setting, after i disable the audio effects, it is still not working.
Click to expand...
Click to collapse
You may try to flash the new Stock ROM that is compatible with the custom ROM. It seems the firmware you installed has sound conflicts with the installed firmware. Try the stable version of the firmware. The dev versions are still under development.
If the sound issues persist, I think you may wanna try the new custom ROM.
Related
Project Treble For Xperia XBased on Sony Open DevicesThanks to Pavel's KernelI am not responsible for bricked devices, dead SD cards,.Suitable for F5121 and F5122Reboot after your first boot please!
请中文用户遵守XDA规则，使用双语留言
If Your Camera doesn't work, see #141 please
Required files:
Our treble file could support Erfans's Android Q GSI, You need to flash this fix.
If you meet crash, you need to delete vendor/overlay.
If you meet endless bootanimite, Try to force reboot.
[New SODP Kernel version]
V20190812:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.zip
V20190811:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.zip
[Pavel's Kernel versions]
V20190702:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.zip
V20190503:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v8_loire.zip
V20190501:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v8_loire.zip
[Old SODP Kernel versions]
V20190429:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v8_loire.zip
V20190323:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v7_loire.zip
V20190210:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v5_loire.zip
[OEM-File]
DownloadLink
[TWRP-Q]
DownloadLink
How to go Treble?
First: Flash Twrp I built which supports a Vendor Partition
Code:
fastboot flash recovery < Path of recovery.img >
Second:Wipe Data and Cache, then flash Treble-X-sjll-XXX.zip in Twrp .
Notice:If you failed when flashing Treble-X-sjll-XXX.zip in Twrp or can't boot into desktop. Please do follwing command:
Code:
fastboot flash boot < Path of boot.img >
Code:
fastboot flash cache < Path of vendor.img >
Third: flash SW_binaries provided by Sony.
You can download it from Sony official website.
Code:
fastboot flash oem < Path of OEM.img >
Optional step If treble file without system
Fourth: Flash a GSI compatible System image and boot!
Code:
fastboot flash system < Path of GSI-System.img >
Google Camera Guide:
1.Gcam must work with Google play services.
2. Suzu doesn't support raw Format Raw10, we should set raw Format to Raw Sensor .
3.We should set Viewfinder Format to YUV_420_888
4.Please enable: Buffer Fix to Fix viewfinder lags.
5. Suzu only support Init SlowMo at 120 FPS
Recommend Gcam Version:
ARNOVA8G2 Link
Gcam_6.1.021_Advanced_V1.7beta3.190707.0105.apk
Gcam_6.2.030_Advanced_V2.2beta5.190704.1015.apk
Update and known BUG:
20190812:
Update:
1. Thermal back, you will not hot in this summer.
2. CPU quiet back, suzu will be cold as ice.
3. F2FS support for cache(Qnovo) and userdata partitions.
20190811:
Update:
1. Go back to SODP kernel.
2. Performance and stability improve.
3. A lot of Fixes of SODP.
20190716:
Update:
1. New twrp-Q uploaded.
V20190702:
Fixes:
1. Cancel OverClock.
2.New CAF imported in kernel.
3.Forcecryptable canceled. If you upgrade from old version, you need to format userdata and use new TWRP-Q.
Bugs:
Need feedback.
V20190503:
Fixes:
1. New PowerHAL.
Bugs:
Need feedback.
V20190501:
Fixes:
1. Use Pavel's kernel source codes.
2. Quick Charge 3.0 works fine.
Bugs:
Need feedback.
V20190210:
Bugs:
1. Quick Charge is broken, you can use computer USB port charge.
2. Camera doesn't work on first boot, you need to reboot.
Source Codes
Sjll
Kernel
Contributors
Sjll @Cubbins
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Paypal
I am very happy to receive your donation.
Version Information
Status: Testing
Created 2019-02-10
Last Updated 2019-08-12
Hi! And it is possible to flash system.img via TWRP?
Since the latest TWRP (3.2.2.2) can flash those partitions, can we flash through it?
realthrash said:
Since the latest TWRP (3.2.2.2) can flash those partitions, can we flash through it?
Click to expand...
Click to collapse
no, I tried
Is it A Only or A/B type?
sebasrock156 said:
Is it A Only or A/B type?
Click to expand...
Click to collapse
A only.
[email protected] said:
Hi! And it is possible to flash system.img via TWRP?
Click to expand...
Click to collapse
realthrash said:
Since the latest TWRP (3.2.2.2) can flash those partitions, can we flash through it?
Click to expand...
Click to collapse
Use the twrp provided by me, it can flash these partition with an img file.
After install this ROM..I dont have root acces and how to enter the treble twrp because I cant enter it after flashed this ROM:crying:
So I just installed the ROM.
On my first try, it just did not boot. Stuck at Sony logo. I then flashed the latests stock .ftf, did the installation again and managed it to boot. Seems that I did not have the latest bootloader
After the initial boot, I wanted to enter recovery again, but could not get into it. I then flashed TWRP 3.2.3.2 and could install the gapps from there. The system also runs with this recovery.
What I already tested:
- camera shows only up to 17,1 Megapixels, but works
- front camera works
- camera button works
- WIFI works
- mobile data wiht LTE work, but I had to type in the APN manually
- phone calls work
- fingerprint works
- bluetooth works, but I cannot pair with my Garmin watch (have the same problem when using lineage OS)
Overall the system looks and feels really great! Added some screenshots too!
Well done, @Sjll ; Thank you very much!
Thelooks14 said:
After install this ROM..I dont have root acces and how to enter the treble twrp because I cant enter it after flashed this ROM:crying:
Click to expand...
Click to collapse
Just using fastboot flash a GSI in system partition.
Please use the twrp I privide for treble.
If you want to go to recovery, just shutdown and hold power and Vol-.
sessions04 said:
So I just installed the ROM.
On my first try, it just did not boot. Stuck at Sony logo. I then flashed the latests stock .ftf, did the installation again and managed it to boot. Seems that I did not have the latest bootloader
After the initial boot, I wanted to enter recovery again, but could not get into it. I then flashed TWRP 3.2.3.2 and could install the gapps from there. The system also runs with this recovery.
What I already tested:
- camera shows only up to 17,1 Megapixels, but works
- front camera works
- camera button works
- WIFI works
- mobile data wiht LTE work, but I had to type in the APN manually
- phone calls work
- fingerprint works
- bluetooth works, but I cannot pair with my Garmin watch (have the same problem when using lineage OS)
Overall the system looks and feels really great! Added some screenshots too!
Well done, @Sjll ; Thank you very much!
Click to expand...
Click to collapse
You can flash a GSI to get better experience. Thanks for your feedback!
Sjll said:
Just using fastboot flash a GSI in system partition.
Please use the twrp I privide for treble.
If you want to go to recovery, just shutdown and hold power and Vol-.
Click to expand...
Click to collapse
Where I can download GSI?
sessions04 said:
So I just installed the ROM.
On my first try, it just did not boot. Stuck at Sony logo. I then flashed the latests stock .ftf, did the installation again and managed it to boot. Seems that I did not have the latest bootloader
After the initial boot, I wanted to enter recovery again, but could not get into it. I then flashed TWRP 3.2.3.2 and could install the gapps from there. The system also runs with this recovery.
What I already tested:
- camera shows only up to 17,1 Megapixels, but works
- front camera works
- camera button works
- WIFI works
- mobile data wiht LTE work, but I had to type in the APN manually
- phone calls work
- fingerprint works
- bluetooth works, but I cannot pair with my Garmin watch (have the same problem when using lineage OS)
Overall the system looks and feels really great! Added some screenshots too!
Well done, @Sjll ; Thank you very much!
Click to expand...
Click to collapse
can you still enter recovery mode now?
I could only enter recovery with TWRP 3.2.3.2!
So I jused Sjll's recovery vor initial installation and then changed to 3.2.3.2
But I am not sure, if the Treble updates will work with this TWRP...
I used your guide to install another treble ROM
Thanks
One question:
I can root without any problem, but if I reboot the phone the data partition gets encrypted, ¿what can I do to solve this?
Today I made a lot of pictures with the front camera and with the back camera. . AF just doesn't get a sharp picture. Front camera is totaly useless for selfies, even with perfect light conditions.
I downloaded Google Camera app, which makes it a little bit better, but still not comparable to the stock Sony Camera App. Oh, and it just shows 13 MPx max res.
Too bad!
Anyone here with better results?
sessions04 said:
Today I made a lot of pictures with the front camera and with the back camera. . AF just doesn't get a sharp picture. Front camera is totaly useless for selfies, even with perfect light conditions.
I downloaded Google Camera app, which makes it a little bit better, but still not comparable to the stock Sony Camera App. Oh, and it just shows 13 MPx max res.
Too bad!
Anyone here with better results?
Click to expand...
Click to collapse
These are bugs of SODP. only waitting for their fix.
where to get boot.img?I can't flash zip
There is a Link in the first post, next to
"[Tested]
V20190210 Link... "
You find the "twrp-Q.img" there.
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup.
Notes
The idea of this project treble is to separate the device-dependent part and the system.
The project treble requires a separate /vendor partition for device-dependent part. But unfortunately we do not have it. But we have a /cache partition, which takes about 200mb and there is a /hidden partition, which takes 50-60mb. 200mb is not enough for us, our vendor is about 450mb.
In the first edition I maded for the 825 tablet, I implement an original solution using separate files for the system and the vendor. But this solution was very difficult to understand. Now my good friend @bonuzzz suggested an idea to me using a compressed partition (squashfs with lz4 compression). With this method, our vendor takes 190-195mb and it is possible to write it to the /cache partition. And use the /hidden partition as a /cache.
Now the installation has become much easier, almost like installing the usual lineage.
Installation
1. install twrp version with treble support (this is my special twrp, based on 9.0 with my latest caf kernel with squashfs support)
2. download treble zip and flash it as usual zip. It will flash boot.img and /vendor partition (in /cache)
3. download any treble system (64bit System A-only) image from: https://forum.xda-developers.com/project-treble
extract, you should get .img file, then copy to sdcard/extsd card and then flash image as system_image in twrp (Install - switch to Install Image and flash as System Image)
4. if you wanna back to stock firmware or lineage - you need flash normal twrp version and make full wipe or just flash stock firmware via odin
Links
Firmware
[SM-T820]
1. 20190404: https://drive.google.com/file/d/1hOPdO9UajY7AlJ5lE859Tr6Y7sEpwhTf/view?usp=sharing
[SM-T825]
1. 20190408: https://drive.google.com/file/d/1DokV37D8f2s9OtoAJTCURfdx88tNW788/view?usp=sharing
TWRP
[SM-T820]
1. 20190404: https://drive.google.com/file/d/1gJ50Sg75Vh7PKyiWfejiCPSD0SYCL5p2/view?usp=sharing
[SM-T825]
1. 20190408: https://drive.google.com/file/d/1x_MKQ1PDM6eEbSPsDyFk0DABjXnZfyB4/view?usp=sharing
System images
You can use almost any system image from https://forum.xda-developers.com/project-treble
Our version is: arm64 and a-only image
Magisk
You should use only latest 19.0 beta version from: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Do not use 18.1 or early version - it's dnw, it will corrupt firmware or may be even corrupt recovery (need flash recovery again via odin)
Almost all firmware say about wrong vendor version. This is normal, just press OK.
let's experiment together!
Version for SM-T825 hope will come soon too. I have some ril issues.
Update boot.img
Wow! Thank you for the amazing work. I seriously can't believe no one hasn't gone crazy over this already.
How would I go about adding some libraries to my /vendor partiton now? I want to try a Samsung OneUI GSI image on my tablet but it requires additional libraries.
The files I want to add are in here: https://mega.nz/#!oi52TSTY!2Qy3WU7DjVmafs4zENPF6dlOsbY06JG5NuvsNeDTRn4
How did you build this file in the first place?
EDIT: I noticed that video playback does not work. I see the video starts to buffer, then some ghosting appears, and finally the app crashes (both YouTube and Vimeo). Also, camera apps seem to crash.
cephasara said:
EDIT: I noticed that video playback does not work. I see the video starts to buffer, then some ghosting appears, and finally the app crashes (both YouTube and Vimeo). Also, camera apps seem to crash.
Click to expand...
Click to collapse
With me, YouTube and YouTube Vanced I run without problems and also the camera app works (only the switching times to the front cam take some time).
GSIs
rainman74 said:
With me, YouTube and YouTube Vanced I run without problems and also the camera app works (only the switching times to the front cam take some time).
Click to expand...
Click to collapse
Maybe my /hidden & /cache partitions got corrupt somehow. I tried several GSIs and had the same issue. Thanks for confirming though.
Have you tried an GSIs from non AOSP-based images? Like OneUI or Xperia? I had trouble with those.
rainman74 said:
With me, YouTube and YouTube Vanced I run without problems and also the camera app works (only the switching times to the front cam take some time).
Click to expand...
Click to collapse
Could you let us know which treble rom you used, as I have the same issues with video playback on youtube.
I also want to throw out there I was on the Nougat bootloader when I tried this and had video playback issues. I have not tried it out on Oreo. I would imagine that could make a big difference.
deleted (it sucks none of the sensors function properly)
just installed RR but i think gps not working
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
This is great!
Hey everyone, this project is big news! I am so happy that we can use Treble GSI, using the cache partition via squashfs is a really elegant way for this.
Almost everything works on my T820! I am using Phh-Treble AOSP 9.0 v112, MindTheGapps and Magisk. Even adoptable storage works, I have 256GB for internal storage now (it displays as 256/512 used when empty, but whatever).
The device is certified with magisk and custom prop value.
Contrary to the old Lineage OS from last year, there is no crazy wifi jitter, so Steam Link just works fine. I did not try out the recent Lineage 20190331, so I don't know if it was due to Lineage.
The rotation sensors are not working, for now I am using "Rotation Quick Setting" app from Play Store. Also, the camera app crashes, but I am not using it anyway.
Thank you so much @bonuzzz and @Valera1978 for making this possible! It is stable enough for daily use for me.
BTW, I came from Oreo bootloader, and have no problems regarding video playback (but I use MX Player, not stock)
Mhh.. I get constantly soft reboots if i try to install third party apps or restore my titanium backup on Havoc for treble. Fingerprint is also not working. Seems to be very unstable...
How could I go about adding files to this treblized /vendor partition? Presumably through the zip? If this is the case, how could I do that?
Fair warning to those wanting to try this: treble roms do install and run, but sensor support appears to be lacking. I can't get any input from gps, accelerometer, gyro, or light sensor.
@Valera1978 If anybody has any idea on how to add support for these to the (I'm assuming) vendor partition, I'd love any hint or direction.
usb otg not working
alegru said:
Hey everyone, this project is big news! I am so happy that we can use Treble GSI, using the cache partition via squashfs is a really elegant way for this.
Almost everything works on my T820! I am using Phh-Treble AOSP 9.0 v112, MindTheGapps and Magisk. Even adoptable storage works, I have 256GB for internal storage now (it displays as 256/512 used when empty, but whatever).
The device is certified with magisk and custom prop value.
Contrary to the old Lineage OS from last year, there is no crazy wifi jitter, so Steam Link just works fine. I did not try out the recent Lineage 20190331, so I don't know if it was due to Lineage.
The rotation sensors are not working, for now I am using "Rotation Quick Setting" app from Play Store. Also, the camera app crashes, but I am not using it anyway.
Thank you so much @bonuzzz and @Valera1978 for making this possible! It is stable enough for daily use for me.
BTW, I came from Oreo bootloader, and have no problems regarding video playback (but I use MX Player, not stock)
Click to expand...
Click to collapse
Does Netflix work?
I get a bootloop after installing image and reboot to system. I have followed the instructions and got an error "Updater process ended with ERROR:7" installing the treble-16.0.zip. I flashed the custom TWRP using odin and using stock Pie. Did I do something wrong?
Hey all. Flashed all the relevant files in the relevant order and currently have a tablet sitting on the Tab S3 splash screen. How long does this normally take?
I flashed the custom TWRP,
Rebooted into Recovery,
Flashed the Treble .zip file,
Rebooted into Recovery,
Flashed the latest Havoc OS, then Magisk v20.3
then rebooted and it's stuck here.
Strange thing is, Windows has flashed up saying that it is "setting up Samsung_Android" while it's on the splash screen.
I come from the tweaked T825 ROM.
Anyone else had this issue? Should I have flashed stock first?
ianrobbie said:
Hey all. Flashed all the relevant files in the relevant order and currently have a tablet sitting on the Tab S3 splash screen. How long does this normally take?
I flashed the custom TWRP,
Rebooted into Recovery,
Flashed the Treble .zip file,
Rebooted into Recovery,
Flashed the latest Havoc OS, then Magisk v20.3
then rebooted and it's stuck here.
Strange thing is, Windows has flashed up saying that it is "setting up Samsung_Android" while it's on the splash screen.
I come from the tweaked T825 ROM.
Anyone else had this issue? Should I have flashed stock first?
Click to expand...
Click to collapse
Well I've hard-bricked my tab by flashing the Treble zip so consider yourself lucky. I think you should flash ODIN stock and start from scratch. Flash ashyx's TWRP, follow the instructions there. DO NOT FLASH MAGISK. Then flash Treble TWRP, flash zip, reboot recovery, DO A WIPE DATA / FACTORY RESET, NOT FORMAT, Then flash Havoc OS a only or whatever. After that wipe cache/dalvik and let it boot to ROM, AND THEN flash magisk and stuff.
I hard bricked my tab because Magisk was installed on the device while I flashed Treble. So yeah DON'T DO THAT EITHER
By the way im so sorry for being 2 months late i saw this just now
Looking dangerous. I'd like to try it but uncertain procedures
NullCode said:
Well I've hard-bricked my tab by flashing the Treble zip so consider yourself lucky. I think you should flash ODIN stock and start from scratch. Flash ashyx's TWRP, follow the instructions there. DO NOT FLASH MAGISK. Then flash Treble TWRP, flash zip, reboot recovery, DO A WIPE DATA / FACTORY RESET, NOT FORMAT, Then flash Havoc OS a only or whatever. After that wipe cache/dalvik and let it boot to ROM, AND THEN flash magisk and stuff.
I hard bricked my tab because Magisk was installed on the device while I flashed Treble. So yeah DON'T DO THAT EITHER
By the way im so sorry for being 2 months late i saw this just now
Click to expand...
Click to collapse
would some of the issues seen by others be fixed if one started with non-rooted stock 9.0 and 9.0 bootloader (if it is different from that for Oreo)? thanks anyone
Has anyone been able to successfully install a treble enabled GSI e.g AOSP onto the A80? Also if so, what current issues are there with this device running a treble GSI and is there anyone maintaining it? Thanks.
yes havoc 2.9 workod for me
blackbuga said:
yes havoc 2.9 workod for me
Click to expand...
Click to collapse
how did you install?
Yes would be great to know how you flashed it? I noticed they now have twrp working for our device but I wonder how easy it is to flash a gsi and to what extent things work e.g fingerprint and camera mainly?
any feedback since we now have a functional twrp?
I would say the TWRP made is not that functional, you can’t transfer files through TWRP once you wipe data for some reason. I tried wiping data before flashing a GSI and my computer would then literally not read the phone storage, nothing would come up. Also other ways I tried to do it without transferring over TWRP did not work. Once I got passed it and flashed a gsi, I would just get a bootloop...
So I’m not entirely sure where to go from there to be honest. I re flashed stock and am staying in stock till TWRP is more functional and a GSI is able to be booted.
danielfrancisarthurs said:
I would say the TWRP made is not that functional, you can’t transfer files through TWRP once you wipe data for some reason. I tried wiping data before flashing a GSI and my computer would then literally not read the phone storage, nothing would come up. Also other ways I tried to do it without transferring over TWRP did not work. Once I got passed it and flashed a gsi, I would just get a bootloop...
So I’m not entirely sure where to go from there to be honest. I re flashed stock and am staying in stock till TWRP is more functional and a GSI is able to be booted.
Click to expand...
Click to collapse
did u tried transfer files through adb sideload?
I could not get adb sideload to work, my computer would not recognise the device at all through adb
Hey guys, was wondering if anyone has been able to successfully flash a GSI on the A80? If so, how and which one/s?
LDP12 said:
Hey guys, was wondering if anyone has been able to successfully flash a GSI on the A80? If so, how and which one/s?
Click to expand...
Click to collapse
From A80XDA Telegram Group:
1) Make sure Magisk is properly installed (patch AP) and running on your device first, likely because we need it to disable dm-verity
2) Download any ARM64 AB GSI and rename the image (*.img) to system.img.ext4
3) Pack it into tar format (e.g. 7-zip)
4) Flash via Odin
5) Enter stock recovery and wipe data
Havoc OS
EJYM said:
likely because we need it to disable dm-verity
Click to expand...
Click to collapse
How did you do this?
Captain Beretta said:
How did you do this?
Click to expand...
Click to collapse
I just properly installed Magisk. I did not do anything else.
EJYM said:
I just properly installed Magisk. I did not do anything else.
Click to expand...
Click to collapse
So you have Havoc GSI running on your Samsung Galaxy A80?
Is that Android 9 or 10 version?
Captain Beretta said:
So you have Havoc GSI running on your Samsung Galaxy A80?
Is that Android 9 or 10 version?
Click to expand...
Click to collapse
Yes, Havoc-OS v3.6.
Android 10
EJYM said:
Yes, Havoc-OS v3.6.
Android 10
Click to expand...
Click to collapse
Thanks, it worked!
Takes some time to setup up and configure things... like corner roundness and some bluetooth disconnect bugs, but all running fine now: even TWRP and root!
Too bad fingerprint scanner does not work, but cool that now face unlock does work!
After some time playing around with Havoc:
I really miss fingerprint unlock and the Always On Display. Did you manage to enable Pixel's built in Ambient Display (always on) and use fingerprint unlock? Some 3rd party always on apps are no option for me, I tested them all and they are no good.
Captain Beretta said:
Thanks, it worked!
Takes some time to setup up and configure things... like corner roundness and some bluetooth disconnect bugs, but all running fine now: even TWRP and root!
Too bad fingerprint scanner does not work, but cool that now face unlock does work!
After some time playing around with Havoc:
I really miss fingerprint unlock and the Always On Display. Did you manage to enable Pixel's built in Ambient Display (always on) and use fingerprint unlock? Some 3rd party always on apps are no option for me, I tested them all and they are no good.
Click to expand...
Click to collapse
You're welcome. I did not try, I don't use Ambient Display. Haven't been able to get fingerprint unlock working yet.
Are you able to transfer files using USB and use USB headphones?
EJYM said:
Are you able to transfer files using USB and use USB headphones?
Click to expand...
Click to collapse
Nope, now that you mention it, USB file transfer does not work. USB-headset also does not work, audio just keeps playing over phone speakers.
Bluetooth audio (bluetooth speaker and bluetooth headset) did not work (kept disconnecting/connecting), but after fiddling with some settings it works now.
So all USB things fail, bluetooth is ok now.
its doesnt work
EJYM said:
From A80XDA Telegram Group:
1) Make sure Magisk is properly installed (patch AP) and running on your device first, likely because we need it to disable dm-verity
2) Download any ARM64 AB GSI and rename the image (*.img) to system.img.ext4
3) Pack it into tar format (e.g. 7-zip)
4) Flash via Odin
5) Enter stock recovery and wipe data
Havoc OS
Click to expand...
Click to collapse
I tried to do your method, but it didn't work, and I tried the same method, but using TWRP, but it didn't work.
I made a complete formatting and it didn't work, and I deleted the system and it didn't work too. Please give me a solution
kkmmee94 said:
I tried to do your method, but it didn't work, and I tried the same method, but using TWRP, but it didn't work.
I made a complete formatting and it didn't work, and I deleted the system and it didn't work too. Please give me a solution
Click to expand...
Click to collapse
Did you extract the .img file from the .xz file before you packed it into .tar file?
The fact that usb doesn't work means that the adapter from type-c to 3.5 also doesn't work?
So, since there is not alot of development going on for our device, i thought we could maybe work together to get something done four our Mi Note 10.
Android Q (10) Guide
1) Flash Miui 12 beta
2) Flash Latest OrangeFox Recovery
3) Format Data
4) Wipe dalvik and cache
5) Reboot to Recovery
6) Flash an GSI of your choice (Arm64-AB)
7)Resize the system partition
8) Optional: Flash Opengapps
9) Optional: Flash Magisk
Restart system
Enjoy
(Big thanks to deathhall)
For me Havoc Q works really well, also face unlock works with Havoc
Havoc specific bugs: SMS doesnt work with 4G, Gcam works only with the main lens and frontfacing lens
Havoc 3.6
Android Pie (9) Guide
How to flash these on the Mi Note 10?
1) Flash Orange Fox TWRP
2) Factory reset in TWRP / format Data!
4) Fastboot: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5) Download the ARM64-AB version of your desired rom
6) Flash AB system.img of your GSI in TWRP
7) Flash magisk
8) reboot
That worked for me with both GSIs
Lineage OS 16.0
HAVOC OS 2.9
Whats not working?
- Fingerprint (Needs custom overlay)
- Automatic Brightness (Needs custom overlay)
- Camera works fine, but Video seems a little bit weird
- NFC, but this can be fixed with a magisk module
NFC FIX
Kind of a fix for automatic brightness
Video fix
If you have weird notification sounds delete the SoundFX folder from /Vendor/lib and /Vendor/lib64
Framework-res.apk (Provided by ChriZer)
Great work my friend, hopefully these will be the stepping stones to development and we can get the ball rolling on more in the future!
Sent from my MI CC9 Pro using Tapatalk
- flash an Xiaomi OTA update like 1.0.1.0 (around 2,5gb)
Link please.
ztocker said:
- flash an Xiaomi OTA update like 1.0.1.0 (around 2,5gb)
Link please.
Click to expand...
Click to collapse
Try with 11.0.12
Couldnt get either to actually boot, couldn't get any OTA's to actually flash with OrangeFox.
I flashed:
miui_TUCANAEEAGlobal_V11.0.11.0.PFDEUXM_9fa3ae20ce_9.0
then tried to flash:
miui-blockota-tucana_eea_global-V11.0.11.0.PFDEUXM-V11.0.12.0.PFDEUXM-ecf4ee46b2-9.0
and just get an error.
I tried following your steps written in the OP, but the BlockOTA fails to flash. Or if I just use a fresh install and Format data, and try to install the GSI's it rewrites the system to system_root and magisk won't install and it just bootloops.
deathhall said:
Couldnt get either to actually boot, couldn't get any OTA's to actually flash with OrangeFox.
I flashed:
miui_TUCANAEEAGlobal_V11.0.11.0.PFDEUXM_9fa3ae20ce_9.0
then tried to flash:
miui-blockota-tucana_eea_global-V11.0.11.0.PFDEUXM-V11.0.12.0.PFDEUXM-ecf4ee46b2-9.0
and just get an error.
I tried following your steps written in the OP, but the BlockOTA fails to flash. Or if I just use a fresh install and Format data, and try to install the GSI's it rewrites the system to system_root and magisk won't install and it just bootloops.
Click to expand...
Click to collapse
Maybe try 11.0.1. since its alot bigger than 12 and 11
Android 11 GSi is out can you give it a shot?
Status?
Is anybody using the LOS GSI as a daily driver?
If there is just the small amount of bugs like in the description, it might be fine for now. At least for me.
Or are there other small bugs 'not worth mentioning' ?
In another parallel thread 'Will there be a custom ROM?', two heros decided to work on our phone... I wish them the best!
Hi all, I have spent a good few weeks testing almost all Android 10 (Q) GSIs for tucana (our device). My findings are relatively positive and are as follows:
I got Pixel Experience as well as EvolutionX from @expressLukeGSI to boot and both seem to work with minimal bugs... The main bug I found was an audio bug commoly associated with GSIs; the audio sounds as if the device is underwater. A simple fix to this bug was flashing audiofix for GSIs.
I also got OxygenOS to boot from @erfanGSI as well as others but these had major bugs (e.g. device reboots automatically, immediately after connecting to WIFI).
Other Android Q GSIs that booted include LineageOS, CAOS, AOSP, Descendant as well as Havoc (from GSI page - Android Q Section - on Github). With regards to LineageOS, once rooted with magisk it will NOT boot.
Under Display Fingerprint does NOT work on any GSIs currently and Face Unlock only works on specific GSIs.
If you'd like more info on the GSIs I have tested or would like me to test further please don't hesitate to contact me via private message, I'll be glad to help wherever possible.
LDP12 said:
Hi all, I have spent a good few weeks testing almost all Android 10 (Q) GSIs for tucana (our device). My findings are relatively positive and are as follows:
I got Pixel Experience as well as EvolutionX from @expressLukeGSI to boot and both seem to work with minimal bugs... The main bug I found was an audio bug commoly associated with GSIs; the audio sounds as if the device is underwater. A simple fix to this bug was flashing audiofix for GSIs.
I also got OxygenOS to boot from @erfanGSI as well as others but these had major bugs (e.g. device reboots automatically, immediately after connecting to WIFI).
Other Android Q GSIs that booted include CAOS, AOSP, Descendant as well as Havoc (from GSI page - Android Q Section - on Github).
If you'd like more info on the GSIs I have tested or would like me to test further please don't hesitate to contact me via private message, I'll be glad to help wherever possible.
Click to expand...
Click to collapse
No fingerprint right?
Fingerprint on GSIs
iSonik said:
No fingerprint right?
Click to expand...
Click to collapse
Unfortunately no fingerprint on any GSIs currently
LDP12 said:
Unfortunately no fingerprint on any GSIs currently
Click to expand...
Click to collapse
Thats not a minor bug imo
iSonik said:
Thats not a minor bug imo
Click to expand...
Click to collapse
Completely opinion based; I can live without it.
I have edited my original post to include this.
LDP12 said:
Completely opinion based; I can live without it.
I have edited my original post to include this.
Click to expand...
Click to collapse
Yeah thats why i said "imo". But that also means no autobrightness
iSonik said:
Yeah thats why i said "imo". But that also means no autobrightness
Click to expand...
Click to collapse
Sorry, I never saw the "imo" part of your reply.
That is correct, once again this is minor for me but maybe not for some. Although I can confirm that battery drain is significantly decreased when using GSIs. Even without the auto brightness battery life is much better.
I am currently using/testing the Evolution X GSI from ExpressLukeGSI.
LDP12 said:
Sorry, I never saw the "imo" part of your reply.
That is correct, once again this is minor for me but maybe not for some. Although I can confirm that battery drain is significantly decreased when using GSIs. Even without the auto brightness battery life is much better.
I am currently using/testing the Evolution X GSI from ExpressLukeGSI.
Click to expand...
Click to collapse
Yeah batterylife on GSIs is insane, maybe ill try one again. But the missing fingerprint and faceunlock bother me quite alot
BTW are you using Q GSIs?
iSonik said:
Yeah batterylife on GSIs is insane, maybe ill try one again. But the missing fingerprint and faceunlock bother me quite alot
BTW are you using Q GSIs?
Click to expand...
Click to collapse
Yes, I am using Q GSIs
Interesting, i cant get GSIs to boot, did you do something different?
Are you wiping Dalvik, System, Data and Cache, and then flashing the preferred GSI?
If the above method is not working, search "Download the MIUI 12 Closed Beta for Xiaomi and Redmi devices XDA" on google, download MIUI 12 beta for tucana/Mi Note 10 (our device) and flash it in TWRP. Then perform a wipe as usual and flash preferred GSI.
iSonik said:
Interesting, i cant get GSIs to boot, did you do something different?
Click to expand...
Click to collapse
I was on MIUI 20.6.11 -MiRoom when I flashed the Bliss GSI, my exact steps where:
Flash Latest OrangeFox Recovery
Formata Data
Format dalvik and cache
Reboot to Recovery
Flash GSI -Arm64-AB or BvN depending on the owner
Go to Data in the manage partition menu and resize partition
Flash Opengapps, I used 10.0 Pico
Restart system
Admittedly, I flashed the GSI but not the gapps first, just to see if it would boot, which it did. then I formatted only cache and dalvik, then resized and flashed Gapps. and it booted and took me right into the setup from the notification that came up when it booted.
So this is not my work some developers had done unofficial build of lineageos 18.1 Android 11 based rom at oneplus nord 2 community I am just tested and sharing it at here.
All credit goes to SakilMondal from nord 2 telegram channel.
Bugs:
1)autobrighness is not working.
2)alert slider is not working.
3)NFC not working.
Prerequisites:
1) Working TWRP
2) You must be on latest OOS A15 or Elixir custom rom.
Steps:
1)If you are on custom rom elixir os download lineageos 18.1 and gapps and place them in pendrive
If you are on oxygenos A15 place both files in internal storage.
2)Now boot your device in to TWRP by using advance reboot if you are on stock oos use adb command
adb reboot recovery.
3)when we booted in to TWRP now connect USB OTG and go to mount and checkmark usb storage,after click to select storage and select usb storage.(skip otg process for oxygen os A15 users)
4)Now click install and select lineageos zip flash then falsh gapps now click reboot and select bootloader.
5)when phone boots to bootloader connect to pc and go to folder where we placed A15 stock boot emmc open command prompt there and type following commands.
fastboot devices
fastboot flash boot boot.emmc.win
For EU user inhave given boot as boot.img so cmd command will be as below
fastboot flash boot boot.img
fastboot -w
fastboot reboot
Phone will boot it May stuck at 1+ logo but don't worry it will boot to lineageos 18.1 within 10min so wait atleast for 10min.
Downloads:
Download LineageOS 18.1:
lineage-18.1-20211228-UNOFFICIAL-denniz.zip
drive.google.com
Gapps:
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
Download Indian boot img (emmc.win.format):
{Mod edit: Link removed}
fastboot flash boot boot.emmc.win
Download boot img for EU:
{Mod edit: Link removed}
cmd command:
fastboot flash boot boot.img
Cmd command to erase data:
fastboot -w
Google camera stable app:
https://1-dontsharethislink.celsoazevedo.com/file/filesc/MGC_8.1.101_A9_GV1x_MGC.apk
If you are still want some video instructions here is a guide.
Hi OP, if you are sharing other's work, please give them proper credit, for example, mentioning their ID (even they are not on XDA).
Thanks.
Ok
jerryhou85 said:
Hi OP, if you are sharing other's work, please give them proper credit, for example, mentioning their ID (even they are not on XDA).
Thanks.
Click to expand...
Click to collapse
I will do
What do you guys prefer? Lineage or Elixir?
Eastw1ng said:
What do you guys prefer? Lineage or Elixir?
Click to expand...
Click to collapse
LineageOS but elixir is love because of android 12
OTA eu device at A14 with clean install.
Installed Gapps and boot.emmc.win from my twrp backup(A14 stock boot).
Installed magisk.
Current bugs:
- Fingerprint not working.
- Device vibration is insanely high(maxed). Turning off "Touch vibration" does not stop vibrations when typing on the keyboard.
Hopefully the next build would be stable.
Fi
vince30 said:
OTA eu device at A14 with clean install.
Installed Gapps and boot.emmc.win from my twrp backup(A14 stock boot).
Installed magisk.
Current bugs:
- Fingerprint not working.
- Device vibration is insanely high(maxed). Turning off "Touch vibration" does not stop vibrations when typing on the keyboard.
Hopefully the next build would be stable.
Click to expand...
Click to collapse
Fingerprint is working vibrations are also OK for me but after some days when u rebooted it cause that vibration bug
vince30 said:
Hopefully the next build would be stable.
Click to expand...
Click to collapse
Stable and bug-free enough for official would be nice.
Give him some time, i find its already good enough for a daily driver on my Nord 2
Thanks for this great build @pankspoo
Lineage 19.0 Beta Android 12 released, check telegram channel.
Why are GApps bundled with this release?
Fixed:
Device vibration bug seems to be fixed.
Auto brightness seems to work.
Update more bugs:
- Fingerprint not working.(perist image intact).
- Ringtone doesn't change after changing in sound settings.
- Slider still broken.
- Changing background startscreen/lockscreen with own photo will crash.
vince30 said:
Lineage 19.0 Beta Android 12 released, check telegram channel.
Why are GApps bundled with this release?
Device vibration bug seems to be fixed.
Alert slider still broken.
Click to expand...
Click to collapse
I will upload video and update this thread to arrow for now I can tell vibration fixed didn't know about later slider
pankspoo said:
I will upload video and update this thread to arrow for now I can tell vibration fixed didn't know about later slider
Click to expand...
Click to collapse
Why are GApps added to this new build(LOS 19) it sucks. I wish the developers give the user the freedom to install GApps /MicroG themself if they want.
LOS 18.1 is still preffered no GApps just clean LOS.
Found another bug with this build bluetooth scanning and connecting headsets work. But no sound output. Output is send to phone speakers.
vince30 said:
Why are GApps added to this new build(LOS 19) it sucks. I wish the developers give the user the freedom to install GApps /MicroG themself if they want.
LOS 18.1 is still preffered no GApps just clean LOS.
Found another bug with this build bluetooth scanning and connecting headsets work. But no sound output. Output is send to phone speakers.
Click to expand...
Click to collapse
U can use vanilla build if your don'ts want gapps inbuilt. If your not able to here sound then disable A2DP developer setting and Reboot your phone and see
vince30 said:
LOS 18.1 is still preffered no GApps just clean LOS.
Click to expand...
Click to collapse
How do you clean GAPPS from LOS?
exis_tenz said:
How do you clean GAPPS from LOS?
Click to expand...
Click to collapse
18.1 is without GApps included.
To remove them from LOS 19 you can use adb:
adb shell pm uninstall --user 0 package_name
Wifi Is not detecting
Pls Help
I am stucked
Turboisonfire said:
Wifi Is not detecting
Pls Help
I am stucked
Click to expand...
Click to collapse
We already got latest android 13 roms please use them