Install LineageOS 20 on SM-T290 and SM-T295 with Google Apps (MindTheGapps)
* Your warranty is now void. (It might already been)
* I am not responsible for any damage that it may do to your device. I WARNED YOU
* It's your choice to do it. Not mine. I just made it as I wanted to do it, but you have the choice to do so. If you choose to do it, you know that it may have consequences.
Click to expand...
Click to collapse
WARNING! This won't work on a bootloader with version U4! Flashing won't work and so you will not be able to use this guide. Unfortunately, you can also currently not downgrade the bootloader, making it impossible to get any custom stuff (custom recovery, custom ROM, etc.) on your device...
Hello there! This is another guide from me here on XDA Developers! Today, I will show you how to install LineageOS 20 on an SM-T290 and SM-T295, and yes, it works on both! Let's get started:
PrerequisitesBut first, make sure you have all of this:
An SM-T290 or SM-T295 tablet
TWRP (v3.7.0 recommended for SM-T290 and v3.5.2 for SM-T295)
Unlocked bootloader
1. Download LineageOS 20 ZIP from here (There stands it is for gtowifi, but it also works on the LTE model).
2. Choose the nightly build for the ZIP, it is very stable even though it is nightly.
3. OPTIONAL BUT I DO NOT RECOMMEND: You could also choose the recovery, but that's more like the stock recovery and I recommend you to keep TWRP as it has better features.
4. Download the ZIP that has the format 'lineage-20.0-YYYYMMDD-nightly-gtowifi-signed.zip'
- OPTIONAL: Download the recovery image for LineageOS 20 with the format 'lineage-20.0-YYYYMMDD-recovery-gtowifi.img'.
5. Download MindTheGapps from here.
6. Choose the one with the format 'MindTheGapps-13.0.0-arm64-YYYYMMDD_BBBBBB.zip'
7. Follow the links to download the ZIP file.
8. Place the LineageOS and MindTheGapps ZIP to an SD card or USB drive. If you choose to also take LineageOS recovery, you will also need to place the .IMG to an SD card or USB drive.
9. Insert the SD card or USB drive into your tablet.
10. Boot the device into TWRP.
11. Go to 'Wipe' > 'Swipe to Wipe'.
12. Then go once again to 'Wipe' > 'Format data' > 'Swipe to format'.
13. Go to install, make sure that it is not install image but as flash ZIP!
14. Use the select storage button to choose the storage where the ZIPs are saved.
15. Choose the LineageOS 20 ZIP and swipe to install.
16. Wait until it is done and now install MindTheGapps.
17. Optional step (depending on whether you have the following things):
- Install Magisk (root) ZIP if you have it. You could also do this later on.
- Install LineageOS recovery ZIP if you have chosen to use it. This can also be done later.
17. Click on 'Reboot system' or go to 'Reboot' > 'System'.
18. Wait until the boot is done.
19. Go through the setup, but WAIT! First read the step below.
20. Depending on whether you have LineageOS recovery or TWRP, you need to enable the option 'Auto-update LineageOS Recovery/LOS Recovery' in the setup if you have LineageOS/LOS Recovery and disable that if you have TWRP.
21. Once the setup completed, you are done!
That was easy to follow. Thank you.
Heeni said:
That was easy to follow. Thank you.
Click to expand...
Click to collapse
No problem!
Heeni said:
That was easy to follow. Thank you.
Click to expand...
Click to collapse
Nice. Guess you have LineageOS 20 right now.
Minionguyjpro said:
Nice. Guess you have LineageOS 20 right now.
Click to expand...
Click to collapse
Yes. I was previously running a GSI, but I like this better.
I'm not using Gapps, so I just skipped para. 16. I did install Magisk.
Does OTA update work with TWRP, or only with Lineage recovery?
Heeni said:
Yes. I was previously running a GSI, but I like this better.
I'm not using Gapps, so I just skipped para. 16. I did install Magisk.
Does OTA update work with TWRP, or only with Lineage recovery?
Click to expand...
Click to collapse
It does work with TWRP. It uses an OpenRecoveryScript. If you have Gapps (which you don't have), you need to reflash them afterwards. Also Magisk needs to be reflashed, but it is much easier to do than the stock!
How does this tablet with LineageOS work now?
Has it become more responsive than the original Samsung ROM or does it continue to suffer from the same exasperating slowness that characterized it?
dequadim said:
How does this tablet with LineageOS work now? Has it become more responsive than the original Samsung ROM or does it continue to suffer from the same exasperating slowness that characterized it?
Click to expand...
Click to collapse
I'm not sure, but it has some good features though. Some parts are a bit buggy, but most are not. It's also much faster.
Hello, thank you for the installation guide. Used my T290 and everything was working perfectly fine... I then decided to use LineageOS for MicroG and also everything ist working...
LineageOS 20 for MicroG:
gtowifi
My other SM-T295 is now on Bootloader5 (T295XXS5CWA1) so I think there is no way anymore to get LineageOS 20 on it. I now ordered a "new" SM-T295, which is supposed to be on Android 9. When I use the Guide above, is the cellular modul and LTE working with the CustomRom? Or should I use the GSI? Why is it such a different between those two devices?
SGX22 said:
Hello, thank you for the installation guide. Used my T290 and everything was working perfectly fine... I then decided to use LineageOS for MicroG and also everything ist working...
LineageOS 20 for MicroG:
gtowifi
My other SM-T295 is now on Bootloader5 (T295XXS5CWA1) so I think there is no way anymore to get LineageOS 20 on it. I now ordered a "new" SM-T295, which is supposed to be on Android 9. When I use the Guide above, is the cellular modul and LTE working with the CustomRom? Or should I use the GSI? Why is it such a different between those two devices?
Click to expand...
Click to collapse
Hello there! LTE will not be included, but you have 2 workarounds:
Make a hotspot over Wi-Fi with your phone or any other SIM device
Use the GSI ROM, which may have support
Well, LTE doesn't work, because of this: LineageOS is made on base of the drivers and packages of the device. And, they are almost the same I think, that's why the other stuff will or should work. But, the SM-T295 also has a driver and/or package for the SIM, LTE and so. And because it was originally made for the SM-T290, instead of an SM-T295, it will not include those drivers and so the support for it. You could try a GSI, although I had issues with it. But I may have done it wrong or so.., I always say: if there is an official custom ROM, use that over GSI, because it was really made for the device and includes the drivers and packages for the device. Although I don't really know whether GSI is bad, it may also work correctly..., if you try GSI, and it doesn't work, you could take a look at this: https://forum.xda-developers.com/t/gsi-lte-fix.3925151/
dequadim said:
How does this tablet with LineageOS work now?
Has it become more responsive than the original Samsung ROM or does it continue to suffer from the same exasperating slowness that characterized it?
Click to expand...
Click to collapse
In my opinion it is much faster and very responsive. It is really an improvement!
SGX22 said:
In my opinion it is much faster and very responsive. It is really an improvement!
Click to expand...
Click to collapse
Well, I will install it as soon as I can.
I flashed TWRP on my T295 But unfortunately i got this eroor SECURE CHECK FAIL : recovery.img)
nima2005com said:
I flashed TWRP on my T295 But unfortunately i got this eroor SECURE CHECK FAIL : recovery.img)
Click to expand...
Click to collapse
That's I think because your bootloader version is 4 or higher, instead of 3..., this updates after an update, and it can also not be downgraded for now. Bootloader version 3 has not got this protection that disallows flashing custom things like TWRP. Bootloader version 4 and higher do have...
Minionguyjpro said:
That's I think because your bootloader version is 4 or higher, instead of 3..., this updates after an update, and it can also not be downgraded for now. Bootloader version 3 has not got this protection that disallows flashing custom things like TWRP. Bootloader version 4 and higher do have...
Click to expand...
Click to collapse
ok i haved installed this rom on T295 Android 9 Bootloader 3 And everything works .Thanks for making this awesome rom . the only bug i noticed is low brightness . i think oneui max brightness was higher than this rom
nima2005com said:
ok i haved installed this rom on T295 Android 9 Bootloader 3 And everything works .Thanks for making this awesome rom . the only bug i noticed is low brightness . i think oneui max brightness was higher than this rom
Click to expand...
Click to collapse
Note: as i experienced you cant install Twrp on android 10 bootloader 3
nima2005com said:
I flashed TWRP on my T295 But unfortunately i got this eroor SECURE CHECK FAIL : recovery.img)
Click to expand...
Click to collapse
You can repair it quickly. Please search on youtube.
Deleted, need to search some further to make sure it is correct...
nima2005com said:
ok i haved installed this rom on T295 Android 9 Bootloader 3 And everything works .Thanks for making this awesome rom . the only bug i noticed is low brightness . i think oneui max brightness was higher than this rom
Click to expand...
Click to collapse
Hello, I ordered a "new" T295 with Android 10, but it is T295XXU4BUD3 as well, like my old T295. Is there still no way to get LineageOS on it.
I must say I am very disappointed now. I tried so many things bought 3!!! Devices.. It is just to much work to get LineageOS on a tablet. Is there any (small Tablet) that I can put LineageOS on with LTE which is working. Man, I am trying this for 2 years now..... What about Sony Tablets?
SGX22 said:
Hello, I ordered a "new" T295 with Android 10, but it is T295XXU4BUD3 as well, like my old T295. Is there still no way to get LineageOS on it.
I must say I am very disappointed now. I tried so many things bought 3!!! Devices.. It is just to much work to get LineageOS on a tablet. Is there any (small Tablet) that I can put LineageOS on with LTE which is working. Man, I am trying this for 2 years now..... What about Sony Tablets?
Click to expand...
Click to collapse
Well, an old Samsung Galaxy Tab 4 with LineageOS 18.1 (Android 11). I helped someone today to get it on his device! It was very easy to do, so.
Related
Hi all after trying hundreds of different roms on my old nexus. I think i have found the best way to boost the speed. I'm using xenonhd 5.1.1 with parrot mod and M-kernels. ??
Trying it out right now and it seems snappy. But I am using f2fs version of Xenonhd without the M kernel.
Give the xenonhd please...
Links please
GrandLuLu said:
Give the xenonhd please...
Click to expand...
Click to collapse
Sab3elbromba said:
Links please
Click to expand...
Click to collapse
A little "search" goes along ways......
https://forum.xda-developers.com/showthread.php?t=1826484
https://www.androidfilehost.com/?a=show&w=files&flid=23229
"Lightning fast" and "Nexus 7 2012" are not normally used in the same sentence.
Maybe I'll have to give this a try. I've kept mine on stock KitKat, and it's dog slow.
Are you using SuperSU as recommended by ParrotMod, or does it work with Magisk? Thanks.
Edit: To answer my own question, it seems to work fine with Magisk.
so, you have to downgrade the bootloader to use this?
beside that, in the xenonhd thread someone said .. after u install some apps you'll get the same slow down like on every other rom
https://forum.xda-developers.com/showpost.php?p=69949425&postcount=1817
I just got myself a new Nexus 7 and all i've done is run the updates up to 5.1 as 5.1.1 fails to install.
It is pretty slow and crashes a lot, I don't remember it being this laggy and slow when I first got one in 2012. Is it just a function of the new OS's or the new apps? What is the best build to be in for speed? I don't mind losing some of the newer features of the OS. Would just prefer something I can use without being frustrated...
Thanks
Sorry to ask this, but can the nexus 7 2012 roms be used on a nexus 7 3g 2012? are they the same? I am new to this model, I am about to buy one (just as ereader), but would like to have the best rom on it.
jbaumert said:
A little "search" goes along ways......
https://forum.xda-developers.com/showthread.php?t=1826484
https://www.androidfilehost.com/?a=show&w=files&flid=23229
Click to expand...
Click to collapse
The latest version update-XenonHD-09-13-15 is not available anymore. If anyone that has the files could share.
I was also pointed to try this rom: https://forum.xda-developers.com/nexus-7/development/rom-android-7-aosp-grouper-t3467514
And this one, but again no working links https://forum.xda-developers.com/showthread.php?t=2784244
I will buy today a Nexus 7 3G 2012 very cheap, so I will try some roms on it.
skinniezinho said:
Sorry to ask this, but can the nexus 7 2012 roms be used on a nexus 7 3g 2012? are they the same? I am new to this model, I am about to buy one (just as ereader), but would like to have the best rom on it.
Click to expand...
Click to collapse
To use a "Grouper" ROM on the "Tilapia / 3g" device, you just need to flash the Grouper ver of TWRP recovery. Granted, you will not have use of the 3g radio, but otherwise it will function normally.
jbaumert said:
To use a "Grouper" ROM on the "Tilapia / 3g" device, you just need to flash the Grouper ver of TWRP recovery. Granted, you will not have use of the 3g radio, but otherwise it will function normally.
Click to expand...
Click to collapse
Thanks. The device comes with 4.2.2 should I flash first 5.1.1 (in order to update radios and stuff) and then root=>recovery=>rom? Or should I just root it in 4.2.2?
If anyone have the older files that I pointed I would appreciate, I will test them and leave my feedback.
I would download the last "official" update from Google for your device (Tilapia I'm assuming), and manually flash the radio and bootloader with fastboot. (Granted, you could install the entire update, but why bother if you're going to put on a custom ROM anyways) Then, unlock the bootloader (if not already done) install TWRP recovery and flash away.
Anyone tested this ROM yet (with a bunch of apps installed to see if slows down or not) ?
jbaumert said:
A little "search" goes along ways......
https://forum.xda-developers.com/showthread.php?t=1826484
https://www.androidfilehost.com/?a=show&w=files&flid=23229
Click to expand...
Click to collapse
The download links are dead. :crying:
Jaguar10301 said:
I just got myself a new Nexus 7 and all i've done is run the updates up to 5.1 as 5.1.1 fails to install.
It is pretty slow and crashes a lot, I don't remember it being this laggy and slow when I first got one in 2012. Is it just a function of the new OS's or the new apps? What is the best build to be in for speed? I don't mind losing some of the newer features of the OS. Would just prefer something I can use without being frustrated...
Thanks
Click to expand...
Click to collapse
Root it and load RootBooster and choose the last option..
andynroid said:
Root it and load RootBooster and choose the last option..
Click to expand...
Click to collapse
I have a 2012 Nexus 7 running Resurrection Remix M (Android 6.0.1), and I can say that RootBooster *does* help. My N7 was *very* laggy and slow to respond when tapping on anything. I chose "Basic Mode -- Speed", re-booted and it's a LOT faster now. Time will tell if it lasts.
I've had MultiROM and TWRP on this tablet for quite awhile, so I also have RR-N installed as a secondary ROM. I'm going to try RootBooster on that ROM also.
I have a Nexus 7 2012 wifi model and need it strictly for Chromecast audio to control Pandora and Spotify.
What's the best rom for that?
Don't care for anything else really...
I installed the setup mentioned by the OP on my Nexus 7 2012, and it is working well so far. Thank you OP.
Initially I tried to use the kernel that is included with the XenonHD ROM, but it seemed to have issues with lag, not waking from sleep, etc. Then I switched to M Kernel and it was much better, so switching the kernel is necessary in my opinion.
Links:
Main XenonHD thread:
https://forum.xda-developers.com/showthread.php?t=1826484
XenonHD download:
The main download link in post #2 of the above thread doesn't seem to contain the download anymore. But if you go to the "Older builds" link, you can find the 08-20-15 build there. Here is a direct link.
https://androidfilehost.com/?fid=24052804347797659
M kernel:
I used the latest a77 version available from the main M Kernel thread here:
https://forum.xda-developers.com/showthread.php?p=38551156
ParrotMod:
I used the universal version available from the main ParrotMod thread here.
https://forum.xda-developers.com/ne...arrotmod-speed-2012-nexus-7-emmc-fix-t3300416
GApps:
I used the "nano" version from Open GApps:
http://opengapps.org/
Magisk:
Main thread and downloads here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
My Procedure:
I was starting with stock rooted Android 4.4.4. I had previously used the WugFresh toolkit to root and install twrp. If you have something older or custom, you may need to flash a recent stock rom first to update your bootloader.
1) Update to current version of twrp. I used the twrp app from the play store.
2) Boot into twrp. Factory reset.
3) Boot into Android.
4) Download XenonHD, M Kernel, ParrotMod, and GApps files to PC, transfer to tablet via USB. (or download on tablet)
5) Boot into twrp. Wipe everything except internal storage.
6) Install XenonHD, M Kernel, ParrotMod, GApps
7) Boot into Android. Be patient, first boot takes a while
I also replaced SuperSU with Magisk, because I don't consider recent non-Chainfire versions of SuperSU to be trustworthy. To do this:
1) Download Magisk and Magisk Manager to PC, transfer to tablet via USB. (or download on tablet)
2) Open SuperSU settings, select option to uninstall and prepare for alternate su manager.
3) Reboot to TWRP. Flash Magisk. Wipe cache/davlik (not sure this is necessary). Reboot to Android. IMPORTANT: If twrp says device does not appear to be rooted and prompts you to install SuperSU, you must decline.
4) In Android, install Magisk manager.
Hope this helps someone else.
spocko said:
I installed the setup mentioned by the OP on my Nexus 7 2012, and it is working well so far. Thank you OP.
Initially I tried to use the kernel that is included with the XenonHD ROM, but it seemed to have issues with lag, not waking from sleep, etc. Then I switched to M Kernel and it was much better, so switching the kernel is necessary in my opinion.
Links:
Main XenonHD thread:
https://forum.xda-developers.com/showthread.php?t=1826484
XenonHD download:
The main download link in post #2 of the above thread doesn't seem to contain the download anymore. But if you go to the "Older builds" link, you can find the 08-20-15 build there. Here is a direct link.
https://androidfilehost.com/?fid=24052804347797659
M kernel:
I used the latest a77 version available from the main M Kernel thread here:
https://forum.xda-developers.com/showthread.php?p=38551156
ParrotMod:
I used the universal version available from the main ParrotMod thread here.
https://forum.xda-developers.com/ne...arrotmod-speed-2012-nexus-7-emmc-fix-t3300416
GApps:
I used the "nano" version from Open GApps:
http://opengapps.org/
Magisk:
Main thread and downloads here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
My Procedure:
I was starting with stock rooted Android 4.4.4. I had previously used the WugFresh toolkit to root and install twrp. If you have something older or custom, you may need to flash a recent stock rom first to update your bootloader.
1) Update to current version of twrp. I used the twrp app from the play store.
2) Boot into twrp. Factory reset.
3) Boot into Android.
4) Download XenonHD, M Kernel, ParrotMod, and GApps files to PC, transfer to tablet via USB. (or download on tablet)
5) Boot into twrp. Wipe everything except internal storage.
6) Install XenonHD, M Kernel, ParrotMod, GApps
7) Boot into Android. Be patient, first boot takes a while
I also replaced SuperSU with Magisk, because I don't consider recent non-Chainfire versions of SuperSU to be trustworthy. To do this:
1) Download Magisk and Magisk Manager to PC, transfer to tablet via USB. (or download on tablet)
2) Open SuperSU settings, select option to uninstall and prepare for alternate su manager.
3) Reboot to TWRP. Flash Magisk. Wipe cache/davlik (not sure this is necessary). Reboot to Android. IMPORTANT: If twrp says device does not appear to be rooted and prompts you to install SuperSU, you must decline.
4) In Android, install Magisk manager.
Hope this helps someone else.
Click to expand...
Click to collapse
The Gapps don't seem to fit on the standard storrage anymore. Did you enlarge the system storage?
Nevermind, found what I didn wrong. Thanks for your post where you gather all the info
Strormrage said:
The Gapps don't seem to fit on the standard storrage anymore. Did you enlarge the system storage?
Nevermind, found what I didn wrong. Thanks for your post where you gather all the info
Click to expand...
Click to collapse
What was it in your case?
Introduction
This is aimed to be a complete but simple guide for users which want to know what works in the Treble-World on the Mate 10 Pro and 'how to get there', based on other guides and my own findings
Disclaimer: I am not responsible for what you do with your device, you are free, probably old enough to know what you are doing and intelligent enough to read this through.
For the moment I will only speak about my own tests on a BLA L29 as I don't have the possibility to test everything.
Feel free to share your own discoveries via PM (just reuse the same formatting to make things easy)
Requirement
1. PC/Laptop running Windows 10 with adb and fastboot drivers installed
2. Original Huawei USB Type-C Cable
3. Being able to read and use search when a question arises
Summary
0. General Information
I. Unlock the Bootloader
II. Choose your ROM (a.k.a "What works on what")
III. Install your ROM
IV. Miscellaneous / Secondary stuff
V. Bonus : What to do if I am stuck / Bootlooping
0. General Information
To make things easier for everybody, here are some basic informations about your device and some common knowledge :
How do I get in Download / Bootloader / Fastboot Mode ?
Shut down your device, insert your USB cable. Keep the Volume DOWN button pressed and press the Power button, wait.
PRO TIPP : You may also get there from within android, first enable ADB debugging in developer options, then, on your PC open a command prompt and type "adb reboot-bootloader"
How do I get in Recovery Mode ?
While in Download / Bootloader / Fastboot Mode, take the USB cable out, keep the Volume UP button pressed and press the Power button until the phone reboots.
I. Unlock the Bootloader
We allready have a thread by @otonieru perfectly discussing this point, don't forget the Windows 10 fix :
https://forum.xda-developers.com/mate-10/how-to/how-to-huawei-mate-10-pro-standard-t3709535
II. Choose your ROM (a.k.a "What works on what")
This section isn't complete and should be detailed with time. None of these ROMs is specific for the Mate 10 Pro, but thanks to Treble, most images will work. Device-specific modifications are still needed in future, ask your local dev
1. Generic AOSP (Android 8.0 and 8.1) by Phhusson
Link : https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
Description : Really basic ROM (basically pure AOSP) which serves as a basis for most of the other ROMs.
What's working : Everything basic
What's not working : VoLTE, SuperSU and Magisk, Signal strength is reported incorrectly, error message at each start, Play Store tends to hang (solution : wipe the Play Store from recents or force close it)
Actual status : Barebones, can be customized in some ways with overlays.
2. LineageOS 15.1 (Android 8.1) by LuK1337
Link : https://forum.xda-developers.com/honor-view-10/development/rom-lineageos-15-1-t3753000
Description : If you don't know LineageOS, you should have heard about CyanogenMod (CM). This is a super clean, customizable version of Android, based on AOSP
What's working : Everything basic
What's not working : VoLTE, SuperSU and Magisk (system crashes), Signal strength is reported incorrectly,
root works thanks to addon-su (see Miscellaneous)
Actual status : Working as a daily driver (at least in my case) if you can live with some very small drawbacks.
III. Install your ROM
Once you have unlocked your Bootloader and chosen the ROM your heart desires follow these steps :
1. BACK UP YOUR DATA ! -> You will certainly have to do a factory reset and backing up data should be something natural when flashing something on your phone, even before updates.
2. Download the ROM (latest is probably best, but it's best to read what is said in the respective threads before jumping in the hole.
3. Reboot to the Download / Bootloader / Fastboot Mode (see above)
4. Flash the ROM by opening a command prompt and typing :
Code:
fastboot flash system system.img
where "system.img" is the filename of the ROM you downloaded
5. Reboot the phone by typing :
Code:
fastboot reboot
6. The phone will probably get in a bootloop. Don't panic. This should be normal.
After 4-5 reboot the phone will go in Recovery mode. Make a Factory Reset
7. Reboot
8. Profit
IV. Miscellaneous / Device-Specific stuff
This is probably the more interesting part as it is quite hard to find the correct information for our device concerning these points.
Root
ROMs as Lineage don't come prerooted. To root your phone the only viable solution seems to be addon-su for the moment.
To install you will need to install TWRP (follow the instructions in this link by @Dees_Troy : https://forum.xda-developers.com/mate-10/development/recovery-twrp-3-2-1-0-touch-recovery-t3752399 ), boot to TWRP (same as booting to Recovery, as TWRP is the new Recovery). go to advanced -> adb sideload. Connect your phone to your PC and flash the file using
Code:
adb sideload addonsu-15.1-arm64.zip
finally reboot, go to 'developer options' and chose the desired option under 'root options'. Done.
Camera
When flashing a ROM it will probably come with the stock AOSP or Lineage camera which, just say it, sucks on our device form a quality point of view. Here are the answers found to this problem for the moment. Sadly, there isn't one solution which works for everything and everyone.
Google Camera - GCam
Photos work - Gallery works - Videos don't work
Right now his is probably the best compromise if you want something that works, easy to install, while not wanting every little gimmick (in that case you should probably stay on EMUI - The definition of gimmick). Simply install the apk.
Note : there are probably other versions of GCam that work or will work in future, feel free to inform me / us about better working versions.
Link : https://drive.google.com/file/d/1Rw2lXtSHvOUalpA8YKg_kW2Xj_Gu746M/view
More information / discussion :
https://forum.xda-developers.com/mate-10/help/gcam-mod-mate-10-t3729078
Camera Port from the Mate 9 - needs root
Photos work - Videos don't work - Gallery doesn't work - Most filters and gimmicks work
A bit more complicated to install. The easiest way found for now is to root first using addon-su and then copy the system folder inside this zip into the respective folders using a root enables explorer like solid explorer
Link : https://mega.nz/#!7hQDhQAK!p2s7jQp9-nhp2-O1U2s2GrBB9UVBhgKDtFfHTq_CHvI
More information / discussion : https://forum.xda-developers.com/pr...huawei-stock-camera-app-treble-roms-t3735169/
V. Bonus : What to do if I am stuck / Bootlooping
Remember when I said to back up ? Well I hope you did, because if you are really bootlooped and a reflash of the system image hasn't helped. you will have to reflash the whole device, which isn't quick.
Gladly @mankindtv has got you covered with his great guide : https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
I hope I could help a bit. Feel free to add your own findings, simply PM me.
Credits -
@otonieru for the great Bootloader unlocking thread
@phhusson for his many efforts to make Treble awesome
@LuK1337 for his many efforts to get things working on the Lineage side as well as for addon-su
@Dees_Troy for his awesome work on TWRP
@mankindtw for his great guide on recovering from the loops of boots
reserved
It's gonna be one of the most helpful threads for the novices.
---------- Post added at 02:41 AM ---------- Previous post was at 02:39 AM ----------
If possible, please add how to go back to stock rom in simplified form.
mdjishadk said:
It's gonna be one of the most helpful threads for the novices.
Click to expand...
Click to collapse
I have lost three days to get out of bootloops and gather the info... I hope nobody else will have to live the same thing (and maybe this can become a dedicated thread to fix the last missing blocks to have a complete experience)
good job
You can also root Lineageos with magisk. I did it and it works.
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956
good job on this one OP btw, video on mate 9 camera port is only broken on 8.1, on 8.0 all camera features work fine except opening of the picture from the camera app itself
Good job man!
Gryphie said:
You can also root Lineageos with magisk. I did it and it works.
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956
Click to expand...
Click to collapse
It might be android 8.1. It worked fine for me when using 20180225 version, didn't test later ones.
What version are you on?
Gryphie said:
You can also root Lineageos with magisk. I did it and it works.
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956
Click to expand...
Click to collapse
It crashed everything on my 8.1 build (and the developer himself recommended me addon-su) maybe a tad harder to use, but at least you learn something at the same time
You should add that the stereo speakers don't work.
Timate5 said:
You should add that the stereo speakers don't work.
Click to expand...
Click to collapse
"Stereo"... When coming from a Nexus 6P this Sally doesn't sound stereo at all... But you're right !
Android Auto doesn't work also on these ROMs. Phone says its incompatible because of some OMX codec issues
timo.helfer said:
Android Auto doesn't work also on these ROMs. Phone says its incompatible because of some OMX codec issues
Click to expand...
Click to collapse
That's too bad, android auto uses h264 streaming codec I think. I think this issue will have something to do with hardware acceleration. Have you tried messing around with the acceleration option found in the developer options to see if it might work?
Nice guide! Thank you @ChriKn!
Can you add to the "Generic AOSP (Android 8.0 and 8.1) by Phhusson"'s part that we need to use A-ONLY version of this rom?
I will try as soon as I have my PC.
Sad news, I got a good opportunity on a Pixel 2 XL and sold my Mate 10 Pro (I need my Pure Android AND Quality Camera)
Does someone want to take the thread over ?
ChriKn said:
I will try as soon as I have my PC.
Sad news, I got a good opportunity on a Pixel 2 XL and sold my Mate 10 Pro (I need my Pure Android AND Quality Camera)
Does someone want to take the thread over ?
Click to expand...
Click to collapse
Sure i can write some impressions. I just installed Carbon ROM.
I did flash but is not booting at all.
Hello, I did everything as mentioned. And phone is not booting it just bootloops.
i can't do a reset is sends me directly back to recovery and just ask to reboot or shutdown phone...
What do I have to do ?
Can i go to stock rom again ?
Thanks
triconix555 said:
Hello, I did everything as mentioned. And phone is not booting it just bootloops.
i can't do a reset is sends me directly back to recovery and just ask to reboot or shutdown phone...
What do I have to do ?
Can i go to stock rom again ?
Thanks
Click to expand...
Click to collapse
Let it Bootloop until it goes to erecovery and than factory reset it
Timate5 said:
Let it Bootloop until it goes to erecovery and than factory reset it
Click to expand...
Click to collapse
I did that but it is just boolooping again, I did all tge steos over and over and it just bootloops every tipe even after factory resete, it actualy asked le once to resete since then after a couole of reboots it goes straight to te erecovery, wherz it ask to login on a wifi to download latest bootloader and rom or reboot or shutdown device...
XZ/KAGURA/F8331 OmniROM BUILDS
PIE 9.0
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (If coming from an 8.1 ROM) Fix /dsp SELinux labels with the dsp-label-fixer.zip
4. (Optional) Flash a gapps package
5. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. Device wakes up by itself every 5 seconds, reason unknown
2. Camera quality is suboptimal
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-9.0
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
[ROM][XZ][P][9.0][WEEKLY]OmniROM, ROM for the Sony Xperia XZ
Contributors
oshmoun, humberos, local__hero
Source Code: https://github.com/omnirom
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: latest stock ftf
Version Information
Status: Beta
Created 2019-03-17
Last Updated 2019-05-31
Thank you for the separate this from the other pie roms.
I will flash it after I arrive home.
Thank you all for the hard work!
Sent from my kagura using XDA Labs
I'm loving the fact Omnipie is official. I will be flashing this right now. Thank you so much.
Finally flashed! been using it for less than an hour, i can say that its definitely good for daily use. Camera seems better and hasnt crashed yet (like it use to), mic actually picks up audio properly, brightness slider is finally proportional to the brightness level, and its pie
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent), app opening times seem a little longer than 8.1, and 120HZ still doesnt work
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
anyways, thanks dev! (may be editing this thread after more use for battery etc)
XxperexX said:
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent)
Click to expand...
Click to collapse
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
XxperexX said:
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
Click to expand...
Click to collapse
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.
sinivalas23 said:
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.
Click to expand...
Click to collapse
Ah, your correct it does say 8.1 my bad
opps
I saw this version from delta updater (using 8.1 omni) and immediately downloaded flashed oem for pie and downloaded omni 9 but it stucked new omni animated logo. Waited like 10 minutes but nothing happened then rebooted phone but same thing happened. Should i wait more or something went wrong?
Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.
KikiGames said:
Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.
Click to expand...
Click to collapse
you need to do a full wipe before upgrading to p
Just as @oshmoun said; before flashing new ROMs, it's imperative to do full wipe (if you don't want to lose all your data, then do a full backup in TWRP), as flashing without full wiping can cause TONS of problems. Don't be lazy and follow the instructions properly.
oshmoun said:
you need to do a full wipe before upgrading to p
Click to expand...
Click to collapse
I used the same rom before but the last update. I updated through OpenDelta.
Hello !
It's cool to see our XZ is alive !
I have some problems with this rom after a full wipe and update to oem V6 :
- no sounds during calls, no mic, no earphone, no sounds on speaker
- Magisk 18.1 not working
- With official camera app, while using the flash, only the autofocus led is lit, the second and much powerful led is never triggered resulting on dark shots
For now that's all
Thx
Performance is somewhat distressed and the camera does not work for the sound is not working after restarting the device is improving
KikiGames said:
I used the same rom before but the last update. I updated through OpenDelta.
Click to expand...
Click to collapse
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread
Flashed data, cache and dalvik, factory reset. And installed latest nightly with gapps and magisk 18.1.
Only reason I did it this way is because I was on a unofficial build on Omni. Everything is working as it should. Very snappy and no lag. Still have to see how the ROM handles after it's settled for a couple day, but right off the bat it's amazing. Thank you very much Dev, and happy to see you back on XDA.
XxperexX said:
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread
Click to expand...
Click to collapse
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/
KikiGames said:
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/
Click to expand...
Click to collapse
You need a PC to flash this. Follow all steps in order and it'll work. Always remember, unless you have a messaging app that backups texts, you will lose them flashing a cfw. Always always backup anything you don't want to lose.
---------- Post added at 12:56 AM ---------- Previous post was at 12:28 AM ----------
I've had a reoccurring issue on the unofficial and official builds so far. I do not have the option to use my phone when calling unless speaker phone or a Bluetooth headset. I cannot put the phone to my head and use normally. Is there any kind of option to fix this nuisance. Any feedback is truly appreciated
Every 9.0 ROM I ever flash, I always seem to have the same problem. Whether its dirty flashing, or starting with flashtool, to CMD, and then to TWRP, the same problem seems to happen. After the ROM has settled, audio quality through calls becomes a huge problem. I'm not sure if I'm doing something wrong, but it has been a persistent bug, next chance I get for the next nightly ill send a logcat, kinda cant not since back on stock. I need good call quality for work lol. Either way, thank you for bringing OMNI to 9.0 official
anyone having problems with video playback? videos dont play on instagram, youtube or snapchat. using magisk 18.1 and latest omni 9 rom
edit: nvm, found out that the Google camera fix module for magisk was the problem
** Standard Disclaimer: Unlocking your Bootloader will Void your Warranty. I take no responsibility for this or for any bricked devices. These thing should go without saying at this point, but there they are. If you are here, I assume you are familiar with LineageOS, TWRP, and moving from MIUI to AOSP-based ROMs**
I've built a clean version of LineageOS 17.1 for Mi 9 that includes Signature Spoofing, but no other modifications.
This will allow those who are interested to get full MicroG support without the need of using any sort of Patcher or Magisk/XPosed Module. YOu all may have used my previous LineageOS Clean,Stock ROM and this is just an updated build of that ROM + Signature Spoofing to make life easier for those who want MicroG.
I flashed this and followed the simple steps of installing F-Droid, adding the MicroG Repo, and Installing the necessary packages via F-Droid and confirmed MicroG Self-check passes all the tests (once you finish granting the necessary permissions for each).
I prefer this over the NanoDroid or other patching methods as a much cleaner way to use MicroG with LineageOS.
Proprietary Blobs/Device Tree are DRG-Developer's as referenced in their post: here
Kernel source is by DRG-Developer: here
Xiaomi Hardware package used is the primary LineageOS from their github here
My reason for this is that there does not seem to be an officially-supported build for our device on the LineageOS for MicroG project or a recent, unofficial build.
What Works:
Pretty much everything from what I can tell
Fingerprint Sensor it working like a champ so far.
DT2W/DT2S
NFC Seems to be working but I don't have a device to test against
Known Issues:
You tell me...
Download:
849.98 MB file on MEGA
mega.nz
Prerequisite:
Make sure you are running a current AOSP/MIUI ROM with the latest firmware flashed and TWRP Installed
Install:
From TWRP:
1) Wipe Date (standard wipe)
2) Format Date ---> 'yes'
3) push ROM zip to /sdcard/
4) Flash ROM zip
4b) - OPTIONAL - Flash Magisk Zip for Root
5) Reboot to system
If you want to to install MicroG, just follow the steps outlined here in the "Install" section to get F-Droid installed, add the MicroG Repo, and install the handful of apps needed. No need for any of the patching steps.
DRG-Developer's device trees were last updated on 2020-10-18 so expect this build to reflect that. So far everything seems to function very well.
Does it support GApps too or it's only for MicroG?
Edit:
I test it and It's working well with GApps
Thanks for your build.
Vogie said:
Does it support GApps too or it's only for MicroG?
Edit:
I test it and It's working well with GApps
Thanks for your build.
Click to expand...
Click to collapse
Thanks for testing! If you find any bugs, please post them here. I may not be able to troubleshoot everything but at least other users will be aware.
What changes between your older release of LineageOS 17.1? https://forum.xda-developers.com/t/...ineageos-17-1-clean-stock-2020-07-10.4041523/
ICanTrollU said:
What changes between your older release of LineageOS 17.1? https://forum.xda-developers.com/t/...ineageos-17-1-clean-stock-2020-07-10.4041523/
Click to expand...
Click to collapse
Later/updated device trees and built-in Signature Spoofing that you don't get with stock Lineage.
photonmedia said:
Thanks for testing! If you find any bugs, please post them here. I may not be able to troubleshoot everything but at least other users will be aware.
Click to expand...
Click to collapse
Sure,
I'm using this ROM for daily use since yesterday and seems like very stable since now and battery life is good.
I missed `Internet Band-with Speed indicator` and `three finger swipe screen shot gesture` that I think these features are not available in LineageOS.
Vogie said:
Sure,
I'm using this ROM for daily use since yesterday and seems like very stable since now and battery life is good.
I missed `Internet Band-with Speed indicator` and `three finger swipe screen shot gesture` that I think these features are not available in LineageOS.
Click to expand...
Click to collapse
Yes, I do not believe those are included in stock LineageOS.
photonmedia said:
Yes, I do not believe those are included in stock LineageOS.
Click to expand...
Click to collapse
I didn't find any issue that relate to ROM, it's quite stable
I just have a issue on ANXCamera self camera that force close the ANXCamera that I think is not related to ROM
photonmedia said:
...
What Works:
...
NFC Seems to be working but I don't have a device to test against
Click to expand...
Click to collapse
This morning I checked NFC by sending a picture from my MI 9 to my wife's Mi 9T (also equipped with LOS). The transfer was successfull!
Thank you very much for providing this clean (stock) ROM!
Hi,
I've just unlocked my device and flashed Mauronofrio's TWRP afer that, i've installed this rom. And everytime it seems to be bootlooping. Showing the MI logo and after that it turns off and goes back to the Mi logo again. I've tried flashing it a few times, wiping data / system ETC. At the moment I'm restoring it with flashtool to get it back working. But am I doing something wrong?
nico445 said:
Hi,
I've just unlocked my device and flashed Mauronofrio's TWRP afer that, i've installed this rom. And everytime it seems to be bootlooping. Showing the MI logo and after that it turns off and goes back to the Mi logo again. I've tried flashing it a few times, wiping data / system ETC. At the moment I'm restoring it with flashtool to get it back working. But am I doing something wrong?
Click to expand...
Click to collapse
Did you wipe data AND "Format" Data? When you Format data is asks you to confirm by typing "yes" in the TWRP Recovery. Try Wiping and Formatting data, then push the ROM to the phone and Flash.
Ah that was probably it. ADB Sideload wasn't co-operating so i've flashed the rom first and after that wiped + formatted the data. Thanks! I've just restored the phone but will try this later again.
nico445 said:
Ah that was probably it. ADB Sideload wasn't co-operating so i've flashed the rom first and after that wiped + formatted the data. Thanks! I've just restored the phone but will try this later again.
Click to expand...
Click to collapse
Also, be sure you are coming from an updated ROM running current firmware.
Thank for your build ;-)
Are NFC Payements working on it?
john_matrix said:
Thank for your build ;-)
Are NFC Payements working on it?
Click to expand...
Click to collapse
I have not tested payments. Another user confirmed that file transfer via NFC works. I do not use NFC for payments so cannot test.
Hi, does screen off fod work?
Your rom is really simple stock rom, but there is something that I can't make it work. Waze has been my pain, the map dont load and I cant make it run. Anyway you did a good job. You discovered how can we put updates in the rom?
theandroid02 said:
Hi, does screen off fod work?
Click to expand...
Click to collapse
No, you have to double-tap to wake or hit the power button to wake the screen before you can use the fingerprint scanner.
Vinicius7 said:
Your rom is really simple stock rom, but there is something that I can't make it work. Waze has been my pain, the map dont load and I cant make it run. Anyway you did a good job. You discovered how can we put updates in the rom?
Click to expand...
Click to collapse
After installing, did you Install F-Droid and enable the Magisk repositories to install the necessary Magisk Modules and Location Backends? Then in the MicroG settings ensure all the checkboxes are checked?
Thanks for making this ROM. Really appreciate it.
The only small issue I am noticing is that my finance apps (example: banking apps, stock trading apps) popup an alert saying that my device is rooted (even though it is not) and this could be a security risk. The apps do still function but its a bit annoying to see this alert every time I launch the app.
Is this because the ROM has been signed with public keys? This alert does not appear when I used the iode OS ROM for Mi 9 or when I use the official Lineage OS for MicroG ROM on my Mi 8.
dmahtani said:
Thanks for making this ROM. Really appreciate it.
The only small issue I am noticing is that my finance apps (example: banking apps, stock trading apps) popup an alert saying that my device is rooted (even though it is not) and this could be a security risk. The apps do still function but its a bit annoying to see this alert every time I launch the app.
Is this because the ROM has been signed with public keys? This alert does not appear when I used the iode OS ROM for Mi 9 or when I use the official Lineage OS for MicroG ROM on my Mi 8.
Click to expand...
Click to collapse
I'm not sure. It could be the Signature Spoofing aspect. I don't think iode has that and I know stock LIneage does not.
Do you have Magisk installed?
October security patch.
You MUST be on Android 12 to use this!!!!!
If your already on Android 13, you can not go back to Android 12, so don't try flashing this!!!
Your bootloader must also be unlocked to install custom firmware.
To do this, reboot to bootloader and type the following: fastboot flashing unlock
The custom kernel of this ROM hides the unlocked bootloader. The device will pass Safetynet and the Play Store will report the device as certified. Based on this, root, magisk and the modules are not needed to pass device certification.
This is based on the Android Open Source Project. It includes various proprietary hardware-specific code.
All the source code is available in the Github repo here.
Basic requirements
Read through the instructions at least once before actually following them, so as to avoid any problems due to any missed steps!
Make sure your computer has adb and fastboot. Setup instructions can be found here.
Enable USB debugging on your device.
Thanks go to Github and Pixel Experience for their source code and device specific code. I couldn't have built this without it!!!
The ROM uses the Pixel Experience source code, device specific code. I made other minor changes and used compression to lower the file size of the ROM, creating more space in the internal storage with minor reduction in performance. Updated every week with minor changes.
GAPPS ARE ALSO INCLUDED WITH THIS ROM
DO NOT DOWNLOAD OR FLASH GAPPS ON THIS ROM!!!!!
DOWNLOAD RECOVERY FLASHER HERE
DOWNLOAD ROM HERE
#1 REBOOT TO BOOTLOADER
#2 FACTORY RESET: fastboot -w
#3 Have all the recovery flasher files in the same folder
Simply double click on flash.bat to install recovery
#4 REBOOT TO RECOVERY THEN ADB SIDELOAD
adb sideload PixelExperience_barbet-13-20221107-BETA-UNOFFICIAL.zip
#5 REBOOT TO SYSTEM
#6 REBOOT TO RECOVERY AGAIN IF YOU WISH TO ROOT AND ADB SIDELOAD
adb sideload magisk.apk
#7 REBOOT TO SYSTEM
Screen call and Google assistant works.
If you are already on this ROM, you can dirty flash updates without wiping data. Simply set to inactive slot in bootloader. Reboot to bootloader then
fastboot --set-active=other
Then repeat all steps except #2
YOU MUST WIPE WHEN COMING TO THIS ROM THE FIRST TIME!!!
Hello, thanks for for new custom rom. Can you please post screenshots with which customizations available in this ROM? For example double tap on status bar to go sleep, etc?
[email protected] said:
Hello, thanks for for new custom rom. Can you please post screenshots with which customizations available in this ROM? For example double tap on status bar to go sleep, etc?
Click to expand...
Click to collapse
Thank you.
Installed this rom with gapps and magisk, everything working fine.
[email protected] said:
Installed this rom with gapps and magisk, everything working fine.
Click to expand...
Click to collapse
how is the FP sensor, does phone have slow unlock when you are not using AOD? Google introduced that stupid bug in March, and they still didn't fix it.
predragiPredrag said:
how is the FP sensor, does phone have slow unlock when you are not using AOD? Google introduced that stupid bug in March, and they still didn't fix it.
Click to expand...
Click to collapse
Works very quick, much more quicker than latest stock
[email protected] said:
Thank you.
Click to expand...
Click to collapse
Thanks for the info. Any bugs let me know.
I'm having a issue right now getting the updates pushed through the updater. For now you can manually update without wiping by the following method until I get it fixed. Reboot to bootloader and check what your active slot is. Switch to opposite slot by the following. Example, active slot is b. fastboot --set-active=a Reboot to recovery and sideload update file. Reboot to recovery and sideload Gapps file. Reboot to system. You will then have to reboot to recovery to sideload magisk and root again. Updates are always installed in opposite slot or you will be stuck at bootanimation. This will hopefully be temporary until I get the issue resolved.
TheSayaMan said:
I'm having a issue right now getting the updates pushed through the updater. For now you can manually update without wiping by the following method until I get it fixed. Reboot to bootloader and check what your active slot is. Switch to opposite slot by the following. Example, active slot is b. fastboot --set active=a Reboot to recovery and sideload update file. Reboot to recovery and sideload Gapps file. Reboot to system. You will then have to reboot to recovery to sideload magisk and root again. Updates are always installed in opposite slot or you will be stuck at bootanimation. This will hopefully be temporary until I get the issue resolved.
Click to expand...
Click to collapse
Hello, if there some critical updates, or fixes? I think everything working fine on current ROM.
[email protected] said:
Hello, if there some critical updates, or fixes? I think everything working fine on current ROM.
Click to expand...
Click to collapse
Ok thank you. Someone sent me a personal PM saying that phone calls were dropping for no reason and all text messages were not being received to their phone. I can't seem to see any issue from the logcat they sent me. Any truth to this from you or anyone else? I am using this myself and don't have such issues. Maybe it's carrier related. I have Verizon. I will check with him and see what carrier he is using. I will give him the benefit of doubt.
TheSayaMan said:
Ok thank you. Someone sent me a personal PM saying that phone calls were dropping for no reason and all text messages were not being received to their phone. I can't seem to see any issue from the logcat they sent me. Any truth to this from you or anyone else? I am using this myself and don't have such issues. Maybe it's carrier related. I have Verizon. I will check with him and see what carrier he is using. I will give him the benefit of doubt.
Click to expand...
Click to collapse
Hello, I haven't such issues. I use 2 sims, 1 esim and 1 sim, everything working fine with SMS and calls.
TheSayaMan said:
I'm having a issue right now getting the updates pushed through the updater. For now you can manually update without wiping by the following method until I get it fixed. Reboot to bootloader and check what your active slot is. Switch to opposite slot by the following. Example, active slot is b. fastboot --set active=a Reboot to recovery and sideload update file. Reboot to recovery and sideload Gapps file. Reboot to system. You will then have to reboot to recovery to sideload magisk and root again. Updates are always installed in opposite slot or you will be stuck at bootanimation. This will hopefully be temporary until I get the issue resolved.
Click to expand...
Click to collapse
Hello, do you plan to release Android 12.1, as I understand this linage is Android 12
[email protected] said:
Hello, I haven't such issues. I use 2 sims, 1 esim and 1 sim, everything working fine with SMS and calls.
Click to expand...
Click to collapse
Great, thanks!!!
[email protected] said:
Hello, do you plan to release Android 12.1, as I understand this linage is Android 12
Click to expand...
Click to collapse
This is 12.1. If you look in System, it will show Lineage 19.1
TheSayaMan said:
This is 12.1. If you look in System, it will show Lineage 19.1
Click to expand...
Click to collapse
No, for me it says, Android version 12
Lineage version 19-20220504-UNOFFICIAL-barbet
[email protected] said:
No, for me it says, Android version 12
Lineage version 19-20220504-UNOFFICIAL-barbet
Click to expand...
Click to collapse
The file name is irrelevant. Look in System, updater.
I didn't install latest your update, maybe because of it, it using Android 12?
TheSayaMan said:
The file name is irrelevant. Look in System, updater.
Click to expand...
Click to collapse
So you see, there Android is 12
[email protected] said:
So you see, there Android is 12
Click to expand...
Click to collapse
Lineage 19.1 is same as Android 12.1