Hi. Maybe some of you have these files but i'll share mod i use on custom roms and LOS 15.1.
I can add to OP more if you share on this topic
Original LOS 15.1 Thread by @OrdenKrieger https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-15-1-zte-axon-7-t3800214
Google Camera for HDR+ and Portrait Mode on Front Camera
https://drive.google.com/open?id=1CZAoa_9HQDnrM-F1qIYDpczuHmZXrfZw
Use pico gapps to use GCam.
Change buttons back and recent. Thanks @kevte89
https://drive.google.com/open?id=1SjY1-uIZ0kTayJ0vouHP2LyaKWPHN_SV
Magisk 16.4 to Root.
https://github.com/topjohnwu/Magisk/releases/download/v16.4/Magisk-v16.4.zip
To Fix Daydream. Thanks to @LuccoJ
https://forum.xda-developers.com/showpost.php?p=76806563&postcount=303
Add the addonsu to root with Magisk (and remove addonsu) https://download.lineageos.org/extras
or
Just root within twrp 3.2.17 (@NFound) - tested by @DarkQuark
@WesTD why the need to use pico gapps? Can't you choose aroma and not install Google Camera or use gapps config to disable it being installed.
@raystef66 you need to install the addonsu, remove it and then install magisk? Why can't you just install magisk?
Dodgexander said:
@WesTD why the need to use pico gapps? Can't you choose aroma and not install Google Camera or use gapps config to disable it being installed.
@raystef66 you need to install the addonsu, remove it and then install magisk? Why can't you just install magisk?
Click to expand...
Click to collapse
You can install magisk when on 3217 as i heard without addonsu but this one runs 3216.
Just use the addonsu and then flash 16.4 and you'll be good to go.
EDIT : maybe 3.2.1.6 can root too without the addonsu but i never tested that. But like said no harm done to use the addonsu
Dodgexander said:
@WesTD why the need to use pico gapps? Can't you choose aroma and not install Google Camera or use gapps config to disable it being installed.
@raystef66 you need to install the addonsu, remove it and then install magisk? Why can't you just install magisk?
Click to expand...
Click to collapse
IDK why but camera has stopped if I install mini or higher
raystef66 said:
You can install magisk when on 3217 as i heard without addonsu but this one runs 3216.
Just use the addonsu and then flash 16.4 and you'll be good to go.
EDIT : maybe 3.2.1.6 can root too without the addonsu but i never tested that. But like said no harm done to use the addonsu
Click to expand...
Click to collapse
I'll have to try when I install it and report back here.
WesTD said:
IDK why but camera has stopped if I install mini or higher
Click to expand...
Click to collapse
Very strange when mini doesn't include camera. The only apps in mini that have anything to do with the camera are face detect and photos.
WesTD said:
Google Camera for HDR+ and Portrait Mode on Front Camera
https://drive.google.com/open?id=1CZAoa_9HQDnrM-F1qIYDpczuHmZXrfZw
Click to expand...
Click to collapse
Is HDR+ and Portrait Mode only working on the front camera?
Any news about the stock camera?
There have been flashable zips in the path if I'm not mistaken, none for oreo after all I know, right?
joaocandeias said:
Is HDR+ and Portrait Mode only working on the front camera?
Click to expand...
Click to collapse
Both rear and front
Just to update here with my findings.
1. Magisk 16.4 works fine installing straight, no reason to install addonsu.
2. Installed aroma gapps from open gapps and it works fine apart from bizarre occasional "Google has stopped " messages.
3. I can't comment on the Google camera shared here but the latest recommend pixel mod camera from here: https://www.celsoazevedo.com/files/android/google-camera/dev-arnova8G2/#apk285 works relatively well, crashed on me once trying slow motion but everything else seems to work. I did not come across the problem mentioned here where certain gapps break gcam.
This is all fresh install, unencrypted, A2017U using universal bootstack and U modem and Nfound TWRP .6.
Is there any reason you chose that exact version of Gcam @WesTD ?
I have been using the latest version arnovas mod and today it crashed quite often taking photos. It also didn't work well recording UHD video and lagged during one of my recordings.
WesTD said:
Hi. Maybe some of you have these files but i'll share mod i use on custom roms and LOS 15.1.
I can add to OP more if you share on this topic
Click to expand...
Click to collapse
You should add this magisk mod to fix issues with DayDream:
https://forum.xda-developers.com/showpost.php?p=76806563&postcount=303
Liquid5n0w said:
You should add this magisk mod to fix issues with DayDream:
https://forum.xda-developers.com/showpost.php?p=76806563&postcount=303
Click to expand...
Click to collapse
Thanks, added OP
Just a general, unimportant question. What's the deal with LOS-based ROMs and cLock? cLock displays weather with the aid of weather providers since Marshmallow I think.
On Oreo none of them seem to work. They install normally but the systems don't see them as providers. Not even Chronus which also acts as a provider.
Just wondering (out loud) why cLock is still included if it's not fully functional anymore.
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HellsGate Kernel, Multiboot, Tapatalk 4.9.3
Whenever I install magisk the device can't boot in the OS. It just boots in fastboot mode every time and the only way to get it back is re-install the OS from recovery mode (TWRP). So far I have tested with version 16.0 and 16.4, and got the same results on both.
Any idea why this is happening?
laglink said:
Whenever I install magisk the device can't boot in the OS. It just boots in fastboot mode every time and the only way to get it back is re-install the OS from recovery mode (TWRP). So far I have tested with version 16.0 and 16.4, and got the same results on both.
Any idea why this is happening?
Click to expand...
Click to collapse
Yes, it's normal. It was mentionened in other threasds already, that this happens. 16.7 should work though, only hide does not work properly.
WesTD said:
Change buttons back and recent. Thanks @kevte89
https://drive.google.com/open?id=1SjY1-uIZ0kTayJ0vouHP2LyaKWPHN_SV
Click to expand...
Click to collapse
The "swap back and recent" doesn't seem to be working. I'm running the 09/25 build of Lineage 15.1. After a flash and reboot, the buttons work exactly as before.
I tried finding the source of that file, but the user you linked doesn't seem to have any posts here. Could you link the source thread?
orangeisnon said:
The "swap back and recent" doesn't seem to be working. I'm running the 09/25 build of Lineage 15.1. After a flash and reboot, the buttons work exactly as before.
I tried finding the source of that file, but the user you linked doesn't seem to have any posts here. Could you link the source thread?
Click to expand...
Click to collapse
Or try this, mount Vendor : https://androidfilehost.com/?fid=1322778262903999789
raystef66 said:
Or try this, mount Vendor : https://androidfilehost.com/?fid=1322778262903999789
Click to expand...
Click to collapse
I've been pulling my hair out for the last few days trying to get the back button on the right side. Unfortunately, this one didn't work for me either. Am I doing something wrong? I reboot into TWRP 3.2.1-8, go to mount, select vendor, go to install, select file, voila. Everything says it installs, no errors, etc, and then there's no change when I boot into system again.
orangeisnon said:
The "swap back and recent" doesn't seem to be working. I'm running the 09/25 build of Lineage 15.1. After a flash and reboot, the buttons work exactly as before.
I tried finding the source of that file, but the user you linked doesn't seem to have any posts here. Could you link the source thread?
Click to expand...
Click to collapse
bradyarz said:
I've been pulling my hair out for the last few days trying to get the back button on the right side. Unfortunately, this one didn't work for me either. Am I doing something wrong? I reboot into TWRP 3.2.1-8, go to mount, select vendor, go to install, select file, voila. Everything says it installs, no errors, etc, and then there's no change when I boot into system again.
Click to expand...
Click to collapse
It should work under /verdor
Or do it manualy in /vendor/usr/keylayout/synaptics_dsx.kl or search that file
Code:
key 158 APP_SWITCH
key 102 HOME
key 187 BACK
key 143 WAKEUP
I used it in LOS16 and all other Pie roms and working ok. Never tried it on LOS15
Related
Use Google Translator:
https://4pda.ru/forum/index.php?s=&showtopic=778560&view=findpost&p=61689325
Requirements:
- Unlock bootloader
- TWRP (3.1.x)
Download Magisk 13 fix for Axon 7
Uninstaller
Sorry my English )))
Thank you @NFound. I flashed both your B04 and magisk, magisk passes all green
For some reason everytime I try to install or download a Magisk addon the manager app just crashes. Any fix for this?
Work on A2017U?
Sent from my ZTE A2017U using Tapatalk
It works just fine for me on RR (A2017U). I flashed the uninstaller for 12 first, then I rebooted & uninstalled the magisk manager app, and lastly rebooted to recovery and flashed the zip from the op.
Thanks for this, NFound
I tried to install this on V2.0.0B01 chinese.
All passed green except the ctsProfile which returns false.
SU from magisksu works btw. what does ctsProfile mean?
Also, if I tried to enable su for apps and adb, basic integrity gives false too.
Hi, thanks for this
I'm trying this on A2017U and it doesn't seem to work. Mostly not prompting for root. Is there further progress on this?
thanks
A2017U
Click to expand...
Click to collapse
V2.0.0B01 chinese.
Click to expand...
Click to collapse
You read carefully? In title is written: for B04
If you have a different phone model, then we put the universal firmware and get rid of it!
Firmware here: https://www.androidfilehost.com/?fid=529152257862726754
Description (use translator): https://4pda.ru/forum/index.php?s=&showtopic=778560&view=findpost&p=61376493
NFound said:
You read carefully? In title is written: for B04
If you have a different phone model, then we put the universal firmware and get rid of it!
Firmware here: https://www.androidfilehost.com/?fid=529152257862726754
Description (use translator): https://4pda.ru/forum/index.php?s=&showtopic=778560&view=findpost&p=61376493
Click to expand...
Click to collapse
Thanks, sorry about that. I was linked to the thread, so I didn't notice the title. I'm reluctant to change my firmware to suit, is there possibility you could submit your changes to official magisk but also include info for A2017U? thanks either way for clearing up my misunderstanding!
Fix SafetyNet for AP
sm.bxsq said:
It works just fine for me on RR (A2017U). I flashed the uninstaller for 12 first, then I rebooted & uninstalled the magisk manager app, and lastly rebooted to recovery and flashed the zip from the op.
Thanks for this, NFound
Click to expand...
Click to collapse
i have yet to get magisk working on any rom
I don't know what to tell you. I've had it working on about all of them. I switched to AOSP Extended and is working all good still
can you please update to B05 ? Thanks
After a few failed attempts (using Audio Modification module etc.) I found a way to get Viper working on the Mi 9. installed on the rooted Xiaomi.eu rom via TWRP and Magisk.
1. Download the Viper4Android_FX-v3.4.2.zip via Magisk but don't install it via Magisk
2. Boot to TWRP and flash the Viper zip and then adhere to the following:
- Press a volume button when prompted to do so
- Volume down (to choose vol key installation method)
- Vol up (for new 2.5.0.5)
- Vol up (for material, if preferred)
- Vol up (for system app)
- Vol up (for lib workaround to be installed)
3. Reboot
4. Via Magisk find and install "Init.d injector" and then reboot
Viper4Android should now be processing your audio!
Rommco05 said:
Installation from Magisk doesn't work? Just curious
Click to expand...
Click to collapse
Not the usual way. On my Pixel 2 XL, either the magisk module would work out of the box or using the Audio Modification Library module would make it work. I tried both of these ways, with no success the driver just wouldn't install. Tried the XDA labs apk, along with the Audio Modification Library, didn't work. Was even waiting a few minutes after boot as I know sometimes/some roms it takes a few minutes to initialise.
After lots of playing around of different versions, I tried that additional installation step of the lib workaround, which states that init.d support is needed too. With the use of that extra init.d module, it works!
I spent some time doing this and figured I'd help out others when they come to do it too!
I managed to install via Magisk?? Maybe due to a Magisk update?
*justintime* said:
I managed to install via Magisk?? Maybe due to a Magisk update?
Click to expand...
Click to collapse
Ahh yeah that's fair enough! Probably flashing via TWRP isn't necessary, so long as the additional init module is there too
Rommco05 said:
Installed init and after Viper4 from Magsik and didn't work, need flash ot trough twrp, today...
Click to expand...
Click to collapse
Ah tgats handy to know! My initial istructions remain valid then
Rommco05 said:
Installed init and after Viper4 from Magsik and didn't work, need flash ot trough twrp, today...
Click to expand...
Click to collapse
Funny with twrp it wasn't working for me...... Magisk had an update. "Check updates canary build' in manager.
And it was a straight away. Flash.... Only no equalizer in usb/dock out though for Android auto
Rommco05 said:
btw after last Magisk update I was able install Viper4 over manager. I also installed that last option (fix)
Click to expand...
Click to collapse
Thanks, that's handy to know!
I simply couldn't get viper4android to work and didn't have much luck with the init.d injector... I ended up following your steps and installed a custom kernel and emulated init.d via the kernel auditor app.... Now its working perfectly!
Have any of you tried the ainur sauron mod on the mi 9?
hi is it possible to get viper4android work with magisk flash? because i don't want twrp and loosing encryption.
when i flash trough magisk viper4android app doesn't appear?
thank you
(sorry for bad english)
dffhgg said:
hi is it possible to get viper4android work with magisk flash? because i don't want twrp and loosing encryption.
when i flash trough magisk viper4android app doesn't appear?
thank you
(sorry for bad english)
Click to expand...
Click to collapse
Possibly...
Have you tried rebooting? Otherwise I'm unsure I'm afraid....
cd993 said:
Possibly...
Have you tried rebooting? Otherwise I'm unsure I'm afraid....
Click to expand...
Click to collapse
yes for sure i rebooted many times but no success..
always viper4android doesn't appear
i also tried install via apk download viper4android then install there also not work, after reboot it reask to install driver.
dffhgg said:
yes for sure i rebooted many times but no success..
always viper4android doesn't appear
i also tried install via apk download viper4android then install there also not work, after reboot it reask to install driver.
Click to expand...
Click to collapse
And this is with the init d module as well?
with init.d injector module from magisk? yes i installed it alredy
dffhgg said:
with init.d injector module from magisk? yes i installed it alredy
Click to expand...
Click to collapse
And you're on the latest eu rom?
Hmm all I can suggest is to remove fully uninstall viper, the init d module and make sure no other audio mods are installed, reboot, then install viper again (ensuring to choose yes to the lib workaround) and the init d module.
If that doesn't work, then unfortunately I'm out of ideas as I tried lots 9f things and this was the only method that worked for me.
Good luck
yes i'm on 10.2.17
i will give it a try and let you know.
hope will work thank you
dffhgg said:
yes i'm on 10.2.17
i will give it a try and let you know.
hope will work thank you
Click to expand...
Click to collapse
I'm on the latest weekly 9.4.11, if that makes any difference
can i flash this version whithout data loss?
i tried reinstall everything but no succes
hi guys my problem is solved!
what i did:
change selinux to permissive with this tool: Kernel SEPolicy patcher https://zackptg5.com/android.php
now viper4android is detect driver its full work!
dffhgg said:
hi guys my problem is solved!
what i did:
change selinux to permissive with this tool: Kernel SEPolicy patcher https://zackptg5.com/android.php
now viper4android is detect driver its full work!
Click to expand...
Click to collapse
Great! I'll save that just in case I ever need it
keep getting the following error
Checking for Digest files
Skipping Digest check: no digest file found
on twrp 3.3.0 b8 and latest EU rom
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.