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. Better to store all partitions, at least efs and may be modem.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
Almost all
Known Issues
- mtp buggy
Links
SM-T320
12. 20210419: april security patch: https://drive.google.com/file/d/1HkZcWDD9U7D6l_EfFjc_nZ4tHyNlNnwO/view?usp=sharing
11. 20201220: december security patch: https://drive.google.com/file/d/1QxdomNPRsng-_xpBqusRyMXurusx8QOl/view?usp=sharing
10. 20200815: august security patch: https://drive.google.com/file/d/1XAMxA7fAZs5EvBFo1429AdmRybWAIHIJ/view?usp=sharing
9. 20200724: july security patch: https://drive.google.com/file/d/1IdIzEMHrJdF2Q6H9YBcBSfigEB7-UDBf/view?usp=sharing
8. 20200614: june security patch: https://drive.google.com/file/d/1mlYZh-LP0gG8PTT-Hzp8jRC6YRhDJy62/view?usp=sharing
7. 20200523: may security patch, small sources rebuild, back mixer from t320 with video recording fix: https://drive.google.com/file/d/1Bhbk06ku5Svv8MFo3ul2PdHvgRJuErOU/view?usp=sharing
6. 20200412: april security patch, kernel update: https://drive.google.com/file/d/1YgrUvgEHy9K-igM99VAaiXM6Z1SLE3qY/view?usp=sharing
5. 20200212: latest sources, February security patch: https://drive.google.com/file/d/1pbyMFiNEYn4Wqz-N5na95tJvahj5qsju/view?usp=sharing
4. 20200114: latest sources, January security patch, rollback to our old wlan driver (if you have issues with this one - please apply wlan patch): https://drive.google.com/file/d/15cLT0Re3LA5yMLVaPNdfIkG6VCJ8oxQh/view?usp=sharing
3. 20191215: https://drive.google.com/file/d/1OmUxocOWKI2ivN7SjSMrNo-QRIy5fOAh/view?usp=sharing
2. 20191210: latest sources: https://drive.google.com/file/d/16Jfe9kss4yEOhb9sVTduWAOsTlYledmw/view?usp=sharing
1. 20191204: initial build (latest code, new wlan driver (3.8.20.24, old was 3.2.3.172)): https://drive.google.com/file/d/1wrUSp-408XmDTtglvx43jM3Zcfujebkt/view?usp=sharing
SM-T325
12. 20210419: april security patch: https://drive.google.com/file/d/1GDmT5lNQtRM_2xqNHWkvlbGP6MJA6L7U/view?usp=sharing
11. 20201220: december security patch: https://drive.google.com/file/d/1JYdx4EqrJ5Jx1Qd6odjtan5N5ex6QyVK/view?usp=sharing
10. 20200815: august security patch: https://drive.google.com/file/d/19J34mHO3KKPoAUoqIAqok52zRaznrZiE/view?usp=sharing
9. 20200724: july security patch: https://drive.google.com/file/d/1WxG7KypUh4ayWwXsNqeggjDbd4Mp_72X/view?usp=sharing
8. 20200614: june security patch: https://drive.google.com/file/d/1zHz-vAbXvHeuZK5Dg19C9pzDNtxsQexv/view?usp=sharing
7. 20200523: may security patch, small sources rebuild: https://drive.google.com/file/d/10sa_B_5Zi-dSQcSRRfDFcjXjd4_OWe6y/view?usp=sharing
6. 20200412: april security patch, kernel update: https://drive.google.com/file/d/1oqyJt94VsQupRpUH--Pb9uN0TKSpWPc_/view?usp=sharing
5. 20200212: latest sources, February security patch: https://drive.google.com/file/d/1XweMgrmDbmi7_pQPSp6PdnYyn743gnfR/view?usp=sharing
4. 20200114: latest sources, January security patch:, rollback to our old wlan driver (if you have issues with this one - please apply wlan patch): https://drive.google.com/file/d/1M6T7KN6ZOZohKFQ7pYCkqeW5SWXm2yX5/view?usp=sharing
3. 20191215: fix internal speaker, bt calls: https://drive.google.com/file/d/1UP5UtOGXBNYft0WPyth4kcSnsCAb_1YB/view?usp=sharing
2. 20191210: ril + mobile data, latest sources: https://drive.google.com/file/d/1HhfoJZP7mLWpZrqx4LO8b3P6m0Br-nVQ/view?usp=sharing
1. 20191204: initial build (latest code, new wlan driver (3.8.20.24, old was 3.2.3.172)): https://drive.google.com/file/d/1GCTDMFphXYx2MLgeLsGq6QWTA60bIJ4s/view?usp=sharing
Wlan patch
if you have wifi problems in the latest firmware - please apply wifi patch: https://drive.google.com/file/d/14qcYQrs2P1x41zz3FR8uwk4nGxlTJWcf/view?usp=sharing
Gapps
https://opengapps.org
Platform: ARM
Android: 10.0
Recovery
Use official version from:
SM-T320: https://twrp.me/samsung/samsunggalaxytabpro8.4wifi.html
SM-T325: https://twrp.me/samsung/samsunggalaxytabpro8.4lte.html
Sources
Sources: https://github.com/Lineageos
Device: https://github.com/Valera1978/android_device_samsung_mondrianwifi and https://github.com/Valera1978/android_device_samsung_mondrianlte
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8974
Vendor: https://github.com/Valera1978/android_vendor_samsung_mondrianwifi and https://github.com/Valera1978/android_vendor_samsung_mondrianlte
Thanks
Thanks to LineageOS team
Thanks to @bartekm01 for helping test SM-T325.
Congratulations to @Valera1978 - working very well on my T325
@bartekm01
Does mobile data works on this Version?
Valera1978, thanks for building Q. I don't have time to download and test Q, but will after Dec 20.
I will move from Pie to Q on that date.
Outstanding job!
Any chance of an SM-T525 build of Q?
Works amazing. I changed animation scale to .5 on all 3 options and it seems speedier and not so choppy. This tablet is still amazing, GREAT JOB Valera1978.
Another happy soul here. This build works flawlessly on T320 and can imagine it will only get better and better.
A minor bug, doesn't bother me at all though. Settings > System > Status bar > battery status style, changing to circle or text doesn't change the battery icon (vertical bar) in the status bar.
Man you are amazing !
an incredible job ....
two small problems, the battery in text format does not work and the voice synthesis is inactive.
Édit: voice synthesis ok with opengapps
dirty flash?
Did you try a dirty flash (LOS and gapps), coming from your LOS 16 version?
Except for the problem that the microphone is very quiet, LOS16 works very well.
What points should be highlighted that represent an advantage of LOS17 over LOS16?
connecting my t320 to pc with usb and choosing file sharing option makes the tablet reboot
WiFi switch on not working on my SM- T 320.
If I switch WiFi on , it changes directly back to off .
I done a Clean install .
bierma32 said:
WiFi switch on not working on my SM- T 320.
If I switch WiFi on , it changes directly back to off .
I done a Clean install .
Click to expand...
Click to collapse
??? WiFi is OK for my T320, gmail and youtube are working fine here !!
or try rebooting with all cache cleared ...
Obing said:
??? WiFi is OK for my T320, gmail and youtube are working fine here !!
or try rebooting with all cache cleared ...
Click to expand...
Click to collapse
here too all working, format data before , but no root and magisk causes error on supercell games, and lockscreen still on portrait mode when in landscape. netflix 6.26.1 works too. thanks again for all effort
Awesome tried open gapps (11/14) first but it had bugs with various features (setting icon don't work in notification pulldown), setting up lockscreen and probably a bunch of other bugs.
BitGapps seem to work good so far (although no first setup screen), overall rom is fast and smooth, it doesn't pass safetynet but not a big deal, thanks again for making this happen, amazing we have 10 on this device now.
Installed all my usual apps and no apparent issues, camera, and video also work!
Wifi (5ghz) seems very stable with new driver, and even gets better range.
OK update on the safteynet issue, I found that "Petnoire's_SafetyNet_Spoofer" Magisk module made it pass both checks and also the play certification (tried some of the other modules but they failed to make it pass).
You can either use his stock module (which will set it to a xiaomi device fingerprint) or use my modification (which will make it a SM-T320), I only modified it to use the correct build fingerprint for this tablet, so yea rom is fully awesome now
(after installing the module and rebooting , don't forget to force stop the playstore and clear both cache and storage)
this might also work on the Android 9 rom too, but I have only tested it on 10 so far.
Not working on latest build: will see if I can fix.
T325 full wipe + Data format.
TWRP 3.3.1-0 (without EFS backup option although found acc to recovery log of LOS 13) to flash ROM, BitGapps + Magisk gave an error 1 for Magisk.
Had to flash it separately to get it working.
Started without logon screen to Google which was fine for me.
IMEI + SIM gone and no mobile data.
With Odin 3.13. back to Stock -> got my IMEI back with mobile data as well.
Reflashed TWRP + LOS17 gapps and, in a second flash, Magisk.
WiFi is fine but again neither SIM nor mobile data.
EFS partition still existing.
Am not able to install saved apps with totalcammnder although it's a secure source.
Always telling me it can't open the file even the freshly downloaded XDA-labs.apk.
Installations from Playstore and F-Droid working.
bierma32 said:
@bartekm01
Does mobile data works on this Version?
Click to expand...
Click to collapse
No. RIL not worka at this moment
bierma32 said:
WiFi switch on not working on my SM- T 320.
If I switch WiFi on , it changes directly back to off .
I done a Clean install .
Click to expand...
Click to collapse
I also have the same problem with my SM-T320 after a clean install. My WiFi just doesn't want to turn on.
@Valera1978 can anything be done about the microphone volume? I record video but can barely hear anything on playback.
Screencast/Miracast is also broken system softreboots when trying to connect., not sure if these are fixable but just thought id let you know
.
Related
!!! This rom has been superseded by the omnirom 9 weeklies !!!
Intro/Disclaimer:
This is an unofficial/homemade build of OmniROM 9.0 for Sony Xperia X Compact (a.k.a. 'Kugo' or 'F5321'). As OmniROM 9.0 builds are not yet officially released and the software binaries from Sony that are needed for Android Pie just recently left beta stage, bugs are to be expected. If you are unfamiliar with rom flashing, using adb and fastboot or recovering the phone after a (soft) brick, I advise against flashing this rom. If you do decide to flash this rom you acknowledge no one is responsible for any damage done to your device but you.
Rom information:
OS name: OmniROM
OS version: Android 9.0 Pie
Kernel: Linux 4.9
Security patch level: June 5, 2019
Currently known issues:
Sporadic crash/reboot when stressing GPU.
USB tethering uses data connection (3/4G) even when the phone is connected to wifi. Pay attention to your data plan when you use USB tethering. bug tracker
Connection to wifi encrypted with wpa enterprise reportedly not possible (may have improved with recent change in wifi libraries; feedback welcome).
Exfat implementation lacks (full) repairing capability.
(If you find issues missing, please let me know and I'll update the list.)
Brief installation instructions:
Backup any important files to another device.
Before first time flashing this rom, first update to / flash the latest stock rom (34.4.A.2.118), or you risk having no in-call audio.
Boot to TWRP and install the rom zip-file (and optionally opengapps).
(clean flash recommended; 'Format Data' required if device is currently encrypted, otherwise first boot will hang).
Because this is an Android Pie rom which uses a 4.9 kernel, you also need to flash a new version of Sony's software binaries to the oem partition:
Download the software binaries zip-file and unzip the image that is inside of it.
Boot to fastboot mode (power off phone; then while holding <volume up> button, connect usb cable to pc and phone. the led should turn blue.),
and flash the image to the oem partition:
Code:
fastboot flash oem SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.img
Downloads:
omni-9-20190608-kugo-HOMEMADE.zip (download directory)
software binaries (v9)
Changelog:
08-06-2019
- Security patch level updated to June 5, 2019
- Upgraded exfat to relan's v1.3.0
23-05-2019
- Fixed: Intermediate bluetooth connection
- Fixed: Night light
- Fixed: Long-press camera button
10-05-2019
- Security patch level updated to May 5, 2019
- Switched wifi libraries to qcwcn from bcmdhd
- Fixed: QC3 charging (hardware limitation = 2A)
- Fixed: 5GHz wifi tethering
- Performance improvements for ARMv8
24-03-2019
- Fixes for software binaries v7 (probably this build is backwards incompatible with software binaries v1 to v6)
05-03-2019
- Security patch level updated to March 5, 2019
17-02-2019
- Fixed cpu usage for improved stability.
07-02-2019
- Security patch level updated to February 5, 2019
- Fixed: SELinux now enforcing (If you're experiencing (in-call audio) issues, you need to reflash stock to update the dsp partition)
- Fixed: USB-tethering
22-01-2019
- SW binaries v5 are out, and this build is backwards incompatible with previous SW versions, so only flash v5 to the oem partition or boot is going to hang on the sony logo.
- Fixed: slow sim card detection (fixed with SW binaries v5)
- Fixed: (temp workaround) random boot crash
08-01-2019
- Security patch level updated to January 5, 2019
15-12-2018
- Fixed: native camera app video recording
- Fixed: recognizing proprietary fast chargers
06-12-2018
- Security patch level updated to December 5, 2018
- Fixed: wifi-tethering
- Added feature: wireguard kernel module
- Added feature: OmniGears -> Buttons -> Music control (my own tentative hackish convolution)
08-11-2018
- Security patch level updated to November 5, 2018
Special thanks to @oshmoun for giving pointers when I encountered issues during the build process.
And of course all credits go to the whole OmniROM team for their awesome work.
OmniROM source code: https://github.com/omnirom
OmniROM gerrit review: https://gerrit.omnirom.org
Kernel source code: https://github.com/sonyxperiadev/kernel
Wireguard source code: https://git.zx2c4.com/WireGuard
Wow, I was looking to buy either a cheap x compact or a cheap xz1 compact but since @harryharryharry is here... Well I might go for this one.
I am still using ur patches from the ubuntu forum since you saved my second notebook (x205ta) from being thrown in the trash at day one.
Hah thanks, looks like we have the same preference in devices then But please don't let your purchase depend on my activity here, because I'm not a developer and pretty new to rom building. The kudos should go to the OmniROM team and people like Oshmoun for helping to maintain the device.
First impressions
Hello! I know that most of you would like to see how this rom looks like.
Consequently, here are my first impressions:
Rom is very smooth and it seems stable.
Wi-Fi and Mobile data (2G, 3G, LTE) are working.
Looks good. Personally, I prefer nougat look.
I like Omni Themes, which are personable.
Battery life is acceptable. Ram consumption ~1.1 GB
So far I found few bugs, that I hope will be fixed:
Camera Recording in stock app doesn't work.
Wi-Fi Thetering doesn't work. (Won't turn on)
Making calls is impossible - you can't here anyone (Phone app bug? Speakers are working.)
Bluetooth works for ~10 seconds and then disconnects (Same as Lineage OS 14.1 unofficial.)
Sometimes few reboots until final boot (2-4 times Selinux related?)
Selinux is set to 'permissive'
And some screenshots that you guys are waiting for.
https://drive.google.com/file/d/1PCI4fryE7g73faL43uvRwVYs7PS2OFlp/view?usp=sharing
https://drive.google.com/file/d/1YQ-7sRt9xqzC0T7dF2z4VHyRiCWgfKdP/view?usp=sharing
https://drive.google.com/file/d/1Uwmu4keaVV1m6GvX76zc5rcutncS1hjr/view?usp=sharing
https://drive.google.com/file/d/1dgJ3vsWmzgFKns-kGoFHfb0XX61D7Q95/view?usp=sharing
https://drive.google.com/file/d/14a4sC7P5nWp3QIQDJN1dV0CsBZPqwwy0/view?usp=sharing
https://drive.google.com/file/d/1GfwCgbAIR5pHAszR8ts_LdxriOdiQdiY/view?usp=sharing
https://drive.google.com/file/d/1UAMTqqb8gG2NTOKdlHWZyrKIEnGeH667/view?usp=sharing
https://drive.google.com/file/d/1qr6V2aPfNHQzpPQfWWOITu59RJvC0-xd/view?usp=sharing
https://drive.google.com/file/d/1Pt1yS9Ahp6J2yetJhx4VDSylkSpjm2mC/view?usp=sharing
https://drive.google.com/file/d/1agW2vVnperEySo-kuo1dCl1vz3fVcrT0/view?usp=sharing
https://drive.google.com/file/d/1Jh8XMPoT89LRtdovxOcjzwy-YEO7Kkwy/view?usp=sharing
https://drive.google.com/file/d/1IiOLHe6XfYuPXoinnfLz1DASNxH6gfdO/view?usp=sharing
https://drive.google.com/file/d/1CPJHx_X_a-5G_b8u91r2n2i0_IDkUht1/view?usp=sharing
https://drive.google.com/file/d/1TIjFeUS1uNHkQtB36YRrpsiD_hsgrJgC/view?usp=sharing
I'm not experiencing bluetooth issues myself with my heart rate monitor. But I saw Oshmoun also has reported an intermediate bluetooth connection issue, so I've added it to the list with known issues. Thanks for the feedback.
I'm having no problem making phone calls. Are you sure it's not related to the 'enabled but not functioning' bluetooth connection ? (I saw in the screenshots you're using a JBL headphone), I can imagine android tries to pass audio through to the (not functioning) bluetooth headphone, resulting in a muted call experience.
If other people can confirm this issue I'll add it to the list, but for now if you could do some digging into the issue, that'd be of help also.
The rebooting issue is definitely not an selinux issue, as it is set to permissive (which basically means: selinux is turned off). I'm having good hopes it (and some other known issues) will be resolved with the next version of Sony's software binaries (v3).
Connecting to other phones via Bluetooth works great.
I have a problem with transmitting audio to speakers (tested 3 different speakers - same issue - ~ 10 sec and bluetooth reboots - connection lost).
And I did phone call while I wasnt connected to bluetooth speaker, as you can see in taskbar.
https://drive.google.com/file/d/1CPJHx_X_a-5G_b8u91r2n2i0_IDkUht1/view?usp=sharing
Overall, this rom is awesome. Great job!
Strange, I tested with an old pair of bluetooth in-earbuds (earin), and I can't reproduce the issue. While I've always had issue with the sound quality (which is why I don't use them) I was able to listen to music for more than 30min (with the occasional interference, but that's likely because it's a crappy prototype). Anyhow, I think this will be addressed once this issue is solved, as it sounds very similar.
I dug into the call issue some more (which is hard because I'm not experiencing it). While calling I ran a logcat and there were some interesting errors about a mic_mute function not being implemented (also mentioned in this issue), but I don't know if that is causing your issue. I think it would be most straightforward if you make a 'adb logcat' of the bug yourself and create an issue on https://github.com/sonyxperiadev/bug_tracker/issues with the logcat attached.
I'm really interested in other people's feedback about this, is @Ketrab8 the only one having this problem while making phone calls or are other people also not hearing the other side while making phone calls?
Hi, I'm using OmniRom 8.1 since Sptember, I appreciate more your work and I want upgrade to Pie finally but why the software binaries and develop branches are from loire?
Loire is just the platform name for Xperia X and Xperia X Compact.
harryharryharry said:
Loire is just the platform name for Xperia X and Xperia X Compact.
Click to expand...
Click to collapse
upload successful but I waited 15 minutes at boot animation but still didn't open
Can you describe how you tried to install the rom ?
harryharryharry said:
Can you describe how you tried to install the rom ?
Click to expand...
Click to collapse
1-wipe cache+cache +userdata+system
2-flashzip( pi9 ommi rom)
3-fastboot flash oem SW........lorie.beta
Hmm, that ought to suffice. Only thing I can think of is that your device was encrypted and this encryption was not removed during installation. The device only very seldom boots correctly when encryption is enabled (which I've already reported on github).
If you're really set on trying the rom, you might want to retry those steps after choosing 'Format Data' in TWRP (it states in TWRP that this option will remove encryption, so one could assume wiping system+data does not)
harryharryharry said:
Hmm, that ought to suffice. Only thing I can think of is that your device was encrypted and this encryption was not removed during installation. The device only very seldom boots correctly when encryption is enabled (which I've already reported on github).
If you're really set on trying the rom, you might want to retry those steps after choosing 'Format Data' in TWRP (it states in TWRP that this option will remove encryption, so one could assume wiping system+data does not)
Click to expand...
Click to collapse
I don't know the password. Is it possible for me to load this rum? and write to me?
I'm sorry for my bad english
What password are you talking about? It's not asking for a password. If you type 'yes' it'll format your device. Be aware that all data will be destroyed, so - if you haven't already - make backups of files that are important to you.
harryharryharry said:
What password are you talking about? It's not asking for a password. If you type 'yes' it'll format your device. Be aware that all data will be destroyed, so - if you haven't already - make backups of files that are important to you.
Click to expand...
Click to collapse
backup ok.
If I do the installation after doing this, will the installation be successful?
Only way to know is to try it out.
harryharryharry said:
Only way to know is to try it out.
Click to expand...
Click to collapse
I laughed.
I want to try it now I'll make a return to you
I head
:good: Good job! I'll update the first post to reflect that the encryption issue makes it look like the rom won't boot. Thanks for the feedback.
harryharryharry said:
:good: Good job! I'll update the first post to reflect that the encryption issue makes it look like the rom won't boot. Thanks for the feedback.
Click to expand...
Click to collapse
I think I helped a little.:good:
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. Better to store all partitions, at least efs and may be modem.
I'm using nano/pico gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
Almost all
Known Issues
- video record
Links
5. 20210419: april security patch: https://drive.google.com/file/d/1aXGrtLrmqAQEYMxcvzck9hJOd-f4OVke/view?usp=sharing
4. 20201220: december security patch: https://drive.google.com/file/d/1KMqFHfDORMCsNXGSrpWkh5IIZp1ZN5oJ/view?usp=sharing
3. 20200815: august security patch: https://drive.google.com/file/d/1oVmXeSfa7p9d4L2nSmiigCjNCo60So7n/view?usp=sharing
2. 20200724: july security patch: https://drive.google.com/file/d/15_4QTR5vKMRvIwXevu1QYb3WHMZsCW72/view?usp=sharing
1. 20200616: initial build, june security patch: https://drive.google.com/file/d/1is2tRwqsd7Nm9dhpkPrGbpgg7AjnOkZh/view?usp=sharing
Gapps
https://opengapps.org
Platform: ARM
Android: 10.0
Recovery
this is my build, the error with the screen off is still present, but I added an option for twrp with unlimited screen timeout, as a result, the screen does not automatically turn off.
for recovery: https://drive.google.com/file/d/1UeC4LwVEA6d46y0UPpuuipHbcjAtAo0Q/view?usp=sharing
for odin: https://drive.google.com/file/d/1WmAzhWkq9l_3d4m3Ft1xmihZaYfccUym/view?usp=sharing
Sources
Sources: https://github.com/Lineageos
Device: https://github.com/Valera1978/android_device_samsung_picassolte
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8974
Vendor: https://github.com/Valera1978/android_vendor_samsung_picassolte
Thank you for this build.
Does anybody else have the problem that picture-in-picture mode is not working?
I'm watching a video with the German sky go app. Pressing the home button takes me to home screen and does not show the video in the small window.
This was working with the Android 9 build.
The permissions are set for the app.
Thank you for this version.
Warning: I initially tried with GApps Stock (like I did with 16.0) and it totally messed up the system (Pixel Launcher crashed constantly, attempting to log in to Google account resulted in a black screen). Now, with Pico, it seems to work alright.
deleted
Can i use a t525 rom to my t520 tablet? I mean, its the same tablet but without lte? If not, pls make a android 10 rom for the t520 tablet
Tabletbungie said:
Can i use a t525 rom to my t520 tablet? I mean, its the same tablet but without lte? If not, pls make a android 10 rom for the t520 tablet
Click to expand...
Click to collapse
T520 is not just T525 without LTE. T320, T325 and T525 have Qualcomm Snapdragon SoC's inside, so most of the codebase can be shared between them. T520 has Exynos which is quite different.
help
i had an error
it says
unknown command [retry_update]
Updater process ended with ERROR: 7
What i should do?
please help me
Just updated to 20200724 with GApps Pico, Magisk and Viper4Android. Nothing out-of-the-ordinary stands out, so in all regards this appears to be a safe upgrade.
в прошивке - LineageOS 17.1 | Android 10.0 Q 202007 24 (Samsung Galaxy Tab Pro 10.1)
не работает (функция не доступна) - поверх других приложений
Valera1978 - обратите внимание на проблему! исправьте пожалуйста!
....
in the firmware - the Lineages of 17.1 | Android 10.0 Q 2007 24 (Samsung Galaxy Tab Pro 10.1)
does not work (function is not available) - on top of other apps
Valera1978-pay attention to the problem! please fix it!
I tried to flash lineageOS 17.1 & 16 but got this error in attachment
What's wrong
Witzker said:
I tried to flash lineageOS 17.1 & 16 but got this error in attachment
Click to expand...
Click to collapse
Maybe try this?
M0lle said:
Maybe try this?
Click to expand...
Click to collapse
THX for taking care but it was my fault
I have not red carefully the instruction for recovery
I had an old version
Now installed the recommended one
for recovery: https://drive.google.com/file/d/1UeC...ew?usp=sharing
Here I have another question
when I go to TWRP -Install Choose the TWRP zip I only installed image not the Option Boot.
Was This OK?
TWRP is starting correctly and I have successfully flashed the image of June (1) & PICO.
BUT I have NO sound!!
How do I install the updates?
Links
3. 20200815: august security patch: https://drive.google.com/file/d/1oVm...ew?usp=sharing
2. 20200724: july security patch: https://drive.google.com/file/d/15_4...ew?usp=sharing
1. 20200616: initial build, june security patch: https://drive.google.com/file/d/1is2...ew?usp=sharing
Just flashing the latest (3) over the old
or flashing the next update (2) then the latest (3)
OR wipe and flash the Latest (3) ?
PLS Help again
THX
Witzker said:
How do I install the updates?
Click to expand...
Click to collapse
Wipe Art/Dalvik Cache, Cache and System
Flash the ROM image (the latest one only)
Flash the GApps
(Flash Magisk if you want root)
Reboot to System
Wait...
M0lle said:
Wipe Art/Dalvik Cache, Cache and System
Flash the ROM image (the latest one only)
Flash the GApps
(Flash Magisk if you want root)
Reboot to System
Wait...
Click to expand...
Click to collapse
SO I will lose all my settings?
Witzker said:
SO I will lose all my settings?
Click to expand...
Click to collapse
No, you won't. Data and Internal Storage will stay intact. This is the procedure I follow when I update from one version of e.g. 17.1 to newer one. Only when upgrading to a new major version do I fully wipe the device.
If you're unsure, backup your stuff with "ROM Settings Backup" and "Titanium Backup" before wiping anything.
THX Great worked ok.
BUT still no sound!
How to check if there is maybe a hardware problem?
I'm going to install this Rom (thanks to developer) , is the sound problem real?
alonzimanuel said:
is the sound problem real?
Click to expand...
Click to collapse
I haven't had any sound problems with either 16.0 or 17.1.
Witzker said:
THX Great worked ok.
BUT still no sound!
How to check if there is maybe a hardware problem?
Click to expand...
Click to collapse
My tab also freezes during browsing websites or open other apps!
What can be the reason ?
Are there some settings to change??
PS: I use Microsoft launcher
Witzker said:
My tab also freezes during browsing websites or open other apps!
What can be the reason ?
Are there some settings to change??
PS: I use Microsoft launcher
Click to expand...
Click to collapse
Don't know that launcher (mine Nova Prime) but did you test turning of animations in dev settings?
Introduction
This is my personal build of LineageOS 18.1 for Pixel 4a with the microG patches applied. If you do not want / need to use microG, it may be a better idea to use the official build available here: https://download.lineageos.org/sunfish. This build is exactly the same as the official build except for the microG patch.
For discussion about the official build, please use the other thread instead: https://forum.xda-developers.com/t/rom-official-sunfish-lineageos-18-1.4255751/
Installation
Before installation, make sure your phone is updated to Android 11 firmware on both of the slots.
Whether you are installing the ROM for the first time or updating the ROM, please make sure you reboot to recovery again after `adb sideload`-ing the ROM before installing add-ons such as Magisk and GAPPS.
1. Download `boot-XXXX.img` (this contains the recovery needed for initial flashing)
2. Download `lineage-18.1-XXXX-UNOFFICIAL-petercxy-sunfish.zip`
3. Reboot your phone to fastboot mode
4. Run `fastboot flash boot boot-XXXX.img` from your PC
5. Reboot your phone into recovery mode (`fastboot reboot`, then press volume up immediately)
6. Erase data
7. Select Apply Update -> Apply Update from ADB
8. Run `adb sideload lineage-18.1-XXXX-UNOFFICIAL-petercxy-sunfish.zip` and wait for installation to finish
9. If you do not need to install any add-ons (e.g. Magisk or GAPPS), then just reboot into system
10. Otherwise, if you do need to install add-ons, reboot into recovery again (this puts your phone into the recovery of the newly-installed system), then install the add-ons using sideload. If you want to use GAPPS, they must be installed here before you boot into system for the first time (this doesn't apply to microG).
11. Enjoy
Updating
1. Download the newly released zip and reboot your phone into recovery
2. Select Apply Update -> Apply Update from ADB
3. Run `adb sideload lineage-18.1-XXXX-UNOFFICIAL-petercxy-sunfish.zip` and wait for installation to finish
4. If you did not have any add-ons installed before update (e.g. Magisk or GAPPS), then just reboot into system
5. Otherwise, if you did, you need to reboot into recovery again at this point before rebooting to system and re-flash every single one of the add-ons you had before. If you do not re-flash them before rebooting to the new system, the boot will fail and your phone will switch back to the old system automatically.
6. Reboot and enjoy.
Note: You don't need to update official firmware manually while LineageOS is installed by flashing latest official factory images. This LineageOS build now ships with latest official firmware updates which are tested to work with the ROM. Please avoid flashing the firmware manually while LineageOS is installed to avoid unnecessary issues.
Known Issues
- Use Magisk v21.4 or later if you want Magisk
- Some applications require microG to be installed in system partition to function, in which case you can consider using the Magisk microG module
- The eSIM manager only works with either GAPPS or microG installed. Without them, you can use eSIM, but you will not be able to add / remove / rename / disable your eSIM. The eSIM manager will also crash once or twice on first boot without GAPPS or microG, but after that it won't crash anymore (the system automatically disables it until you install microG or GMS)
- Disabling / Enabling eSIM may hang even with GAPPS or microG. However, rebooting normally fixes the issue and makes your action effective.
- I provide no guarantee for SafetyNet status or compatibility with any app that requires SafetyNet. Google has been tightening its SafetyNet verification and there is really not much we can do about it, and frankly most apps that require SafetyNet should not have done so in the first place. If you need SafetyNet, you are on your own.
Downloads
Note: This build has compatibility issues with MindTheGapps (just like the recent LineageOS weekly builds). It will be fixed in newer official weekly builds, but since this build is for microG users, I am not going to upload a new microG-patched build just to work around a GAPPS compatibility issue.
20210610: June 05 security update; sorry for the delay, LineageOS had some issues while merging this month's ASB.
This update also fixed some long-standing bugs, such as the initial crash dialog of the eSIM manager (when GAPPS or microG is not installed), and the extraneous battery percentage option in settings -> battery. Read the LineageOS changelog for the full update.
- boot-20210610.img: https://mega.nz/file/TVolEYKL#MrJH-AVk37JDc_iKCVJ2lFGgFLG9czrE4FnJokbjnqI
- lineage-18.1-20210610-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/uYw30SxT#CwWc0GwqMYoAT54TJqPK2U7M8Y3OzhbpPuvejkOB65o
20210507: May 05 security patches
- boot-20210507.img: https://mega.nz/file/rcJVHQYZ#KjFu84Wnqdx4Rq0fd6TZUlJuaD-RXFXmMCJM4V4z0Tc
- lineage-18.1-20210507-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/jYBTESqZ#ZRc7CkUt8aUYgZRLpF6S1_LHdUXwcUOKPsCBorcYZ1w
20210410: April 05 security patches
- boot-20210410.img: https://mega.nz/file/eYggCKba#l7QJUMkvyEBtyptVMmWVbXochJKmY__X4VIwTla1KqE
- lineage-18.1-20210410-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/bUpQhAQJ#uTe-2nHLKYsfFBKuJg0VAYISUCGMTbIpaC9qjEHFZ1c
20210308: March 05 security patches and official firmware / binary updates.
- boot-20210308.img: https://mega.nz/file/WIZxjAwA#P77ZdJ2YEed5WWmlijKcyRMLJ30KG36eL0mhQGjZWjI
- lineage-18.1-20210308-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/eRBTkYzC#iNZUA84XR80V1so7YvjQ7TyJuZKGY9BZf-MGRtgQOH8
20210222: Updated sources; Removed some non-functional LiveDisplay features; Switched to using Google's wifi_ext HAL; Reserved more space in system partitions for potentially larger GAPPS packages
- boot-20210222.img: https://mega.nz/file/KVxRDY6L#7l7oejw-XEd_m1BUdp0_Z2TyHVLE2KkaGQ6g7Op7dpk
- lineage-18.1-20210222-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/mUgzGSbC#88q95qVsI-7RJsecM8L2MHZ6EwNXrs54Xk6yi428rjU
20210207: Updated LineageOS source; Applied 2021-02-05 security patches; Added support for glove mode; Enabled support property for Google Assistant; Optimized vibration
- boot-20210207.img: https://mega.nz/file/aZxlDKgC#_9VR2ruCYUqmX8gLCBKX1KSMAsBYFDsLA6utk5EjB-g
- lineage-18.1-20210207-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/yZpFQQRJ#PZlNYzI2t2fZdf1T3v6pMRi1zJe7J26f-Eu_Pohm7p4
20200118: Updated LineageOS source; Attempted to fix GAPPS bootlooping issue
- boot-20210118.img: https://mega.nz/file/ONYSRLKC#FhRYEhfsBndqcrJrhd1F4Tv3uu3UZNDYnQe3EcrMyC0
- lineage-18.1-20210118-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/3VRgwZQQ#ynCPIDbW42hXvBWp8MoG-R9eEEzvnaQ649ULZM8lrAc
20210109: Updated LineageOS sources and updated build fingerprint to January.
- boot-20210109.img: https://mega.nz/file/qU5T2CLY#A7dkDfRS0gUaKzphT2_mm0IHW9_-3cIR76yvNV1Cs4A
- lineage-18.1-20210109-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/GNwyxb4S#UGHclk8p60QuRWrGl3LI-Hur9X_VKF46tBNfuD0Z9-o
20210107:
1) Synchronized LineageOS updates and AOSP Jan 5 security patch
2) The ROM now ships with latest official firmware, so you won't need to worry about updating firmware separately (you still need latest official firmware when installing the ROM for the first time though)
- boot-20210107.img: https://mega.nz/file/OYRnwaII#3Ipj99mG5tpXouRRKMqWDJmimH8U2q5mZ5LKj8ZEmdo
- lineage-18.1-20210107-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/aEBTFAwK#EM3fKYQG4Y2najLhRkZlPqDwPSwkV-yfsSlH7Za7UYM
20201229: Synchronized LineageOS updates and fixed biometric authentication (fingerprint) in third-party applications.
- boot-20201229.img: https://mega.nz/file/yMow3aDb#ByY4yG6LeAquqBd2vu2UnZUz2xukHYjWbIfXnlkT_XM
- lineage-18.1-20201229-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/SA5WDAZQ#fMRB9w4LLSxSAGxHOtEmN9gRBTmrnF8ozKawM34cIxU
20201227:
- boot-20201227.img: https://mega.nz/file/6cI3lKKK#p8Nq3jUOsOoPDeV6yPj4hQtXGIHu8-D54_g3gkzdi0w
- lineage-18.1-20201227-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/SdQnTaBa#83JjZojOS9JCRdYOng6Y0LLoUl8StAdrwsTbCSqAMhs
Sources
Device Tree: https://github.com/PeterCxy/android_device_google_sunfish
Kernel: https://github.com/PeterCxy/android_kernel_google_sunfish
Thanks: DirtyUnicorn sunfish contributors, SuperiorOS sunfish contributors, LineageOS coral contributors and the LineagOS community.
After some trial and error I got it up and running. After booting the ROM I returned to recovery, factory reset then side loaded Razorloves micro gapps.
Thanks for the build
Nice! Appreciate the work you've done on the trees!
@PeterCxy what vendor do you use? Can I clone it? Or should I extract myself?
Gave this a shot, everything seemed to loadup fine. Wasn't able to get call screen to show up tho, I flashed razorloves gapps, anything to do to get that to work?
ny-hardcore said:
Nice! Appreciate the work you've done on the trees!
@PeterCxy what vendor do you use? Can I clone it? Or should I extract myself?
Click to expand...
Click to collapse
I pushed the vendor blobs I extracted on my GitHub at https://github.com/PeterCxy/android_vendor_google_sunfish, but you can also extract it yourself as I have also pushed my full sunfish-proprietary-files{,-vendor}.txt
This is amazing, thanks @PeterCxy
Where the instructions state to be on A11 on both slots does that mean I can do a flash-all with the latest A11 factory image? Currently on LOS 17
xeropressence said:
Gave this a shot, everything seemed to loadup fine. Wasn't able to get call screen to show up tho, I flashed razorloves gapps, anything to do to get that to work?
Click to expand...
Click to collapse
Unfortunately I have zero clue about this, and I don't live somewhere Call Screening is supported in the first place. This would probably need to be figured out by someone other than me :/
EggZenBeanz said:
This is amazing, thanks @PeterCxy
Where the instructions state to be on A11 on both slots does that mean I can do a flash-all with the latest A11 factory image? Currently on LOS 17
Click to expand...
Click to collapse
Yes you can, but that flash-all script only flashes it on one slot, so to guarantee you have A11 on both slots you'd still need to manually switch the slot and execute that script a second time. The reason why you need A11 on both slots is that the recovery installs the new ROM to the inactive slot, so if the inactive slot is not also on A11, the ROM will probably not boot properly.
PeterCxy said:
Yes you can, but that flash-all script only flashes it on one slot, so to guarantee you have A11 on both slots you'd still need to manually switch the slot and execute that script a second time. The reason why you need A11 on both slots is that the recovery installs the new ROM to the inactive slot, so if the inactive slot is not also on A11, the ROM will probably not boot properly.
Click to expand...
Click to collapse
Thank you
EggZenBeanz said:
This is amazing, thanks @PeterCxy
Where the instructions state to be on A11 on both slots does that mean I can do a flash-all with the latest A11 factory image? Currently on LOS 17
Click to expand...
Click to collapse
You could just sideload the ota after booting the factory image as well.[/QUOTE]
10 hours so far and everything is smooth, great ROM, but I've noticed the battery consumption is less on SuperiorOS, need couple of days to confirm.
xeropressence said:
Gave this a shot, everything seemed to loadup fine. Wasn't able to get call screen to show up tho, I flashed razorloves gapps, anything to do to get that to work?
Click to expand...
Click to collapse
Considering call screen doesn't work on other Lineage pixel ROMs, this wouldn"t be any different.
Thank you very much @PeterCxy
I flash-all latest december 11 images and --set-active= slot to other partition and re flashed again. Following the instructions I now have LOS18 with micro-g running. Awesome! I would be interested in any builds with micro-g patches even when/if sunfish goes official LOS
Biometric/fingerprint unlock is not available in any apps like Bitwarden, wirex etc. Has this feature been removed in A11?
I have a working fingerprint and pattern unlock working on the phone, just no options in any usual apps
EggZenBeanz said:
Biometric/fingerprint unlock is not available in any apps like Bitwarden, wirex etc. Has this feature been removed in A11?
I have a working fingerprint and pattern unlock working on the phone, just no options in any usual apps
Click to expand...
Click to collapse
Do you have Play Services on it? I assume they use the Biometric API for that feature. And I assume that requires Play Services. Or a locked bootloader, some Trust Zone thing... basically it probably isn't designed to work on a ROM that doesn't have some integrity check or secure thingy access.
info:
Login with Biometrics on Android | Android Developers
In this codelab you will add biometric authentication to your app as part of your login process. You will not replace your current login process – users can still log in with their account password. Instead, you will augment your login process, giving users the convenience to not have to...
developer.android.com
jawz101 said:
Do you have Play Services on it? I assume they use the Biometric API for that feature. And I assume that requires Play Services. Or a locked bootloader, some Trust Zone thing... basically it probably isn't designed to work on a ROM that doesn't have some integrity check or secure thingy access.
info:
Login with Biometrics on Android | Android Developers
In this codelab you will add biometric authentication to your app as part of your login process. You will not replace your current login process – users can still log in with their account password. Instead, you will augment your login process, giving users the convenience to not have to...
developer.android.com
Click to expand...
Click to collapse
I don't use play services, but biometric unlock like autofill I think doesn't rely on play services, its part of AOSP? Both my Tab S5e and previous pixel 4a builds were LOS17 with no google services or microg installed and I have Biometric support in all usual apps
jawz101 said:
Do you have Play Services on it? I assume they use the Biometric API for that feature. And I assume that requires Play Services. Or a locked bootloader, some Trust Zone thing... basically it probably isn't designed to work on a ROM that doesn't have some integrity check or secure thingy access.
info:
Login with Biometrics on Android | Android Developers
In this codelab you will add biometric authentication to your app as part of your login process. You will not replace your current login process – users can still log in with their account password. Instead, you will augment your login process, giving users the convenience to not have to...
developer.android.com
Click to expand...
Click to collapse
I noticed the same issue with bitwarden, never had this issue before
EggZenBeanz said:
Biometric/fingerprint unlock is not available in any apps like Bitwarden, wirex etc. Has this feature been removed in A11?
I have a working fingerprint and pattern unlock working on the phone, just no options in any usual apps
Click to expand...
Click to collapse
hmmm it's also not available in my Keepass2Android. I'll look into this later -- I don't think fingerprint support is part of Play Services.
EggZenBeanz said:
Biometric/fingerprint unlock is not available in any apps like Bitwarden, wirex etc. Has this feature been removed in A11?
I have a working fingerprint and pattern unlock working on the phone, just no options in any usual apps
Click to expand...
Click to collapse
It might be an issue with the LineageOS source tree when I last synchronized. I checked some of my other devices with LOS built on the same date and they all don't have the fingerprint option available in apps.
PeterCxy said:
It might be an issue with the LineageOS source tree when I last synchronized. I checked some of my other devices with LOS built on the same date and they all don't have the fingerprint option available in apps.
Click to expand...
Click to collapse
I came from this build, https://forum.xda-developers.com/t/lineage-18-android-11-for-pixel-4a-sunfish.4199889/
And there it worked fine
I first installed with MicroG, then went with Gapps, and neither work
TELEGRAM CHANNEL ADDED: HERE
TELEGRAM CHAT GROUP: HERE
See important discussion about Kernel Updates and Security: here
Jaguar is available on locked bootloader with working root (Magisk)
VERSION 19 FIXES SAFETYNET PASSING (WITH MAGISK 24.3 and higher)
See detailed instructions here
You can actually use alarm when the phone is OFF. It would boot 2 minutes before and trigger the alarm on time
This is official build of Jaguar Rom.
I have been building Android roms since 2012 for various devices including multiple Sonys, Lenovo Zuk, Oneplus 3, Oneplus 5 and Oneplus 6, 8 and 9. You can check my Oneplus 6 or Oneplus 6T threads and browse my profile.
Jaguar rom is focused on hardening of AndroidOS and kernel. As such, the rom has hardened bionic, art, framework and tightened security.
1 Rom control with custom Power options, Statusbar, Buttons, Navbar, Quicksettings, Lockscreen, Notifications, Gestures, Themes etc...
2. Heavily modified Art, Bionic System/Vold and System/Security
3. Telephony response to Type Zero sms ('silently acknowledged') disabled
4. Toggle to disable Captive Portal logging.
5. Speakerphone proximity sensor toggle - could be set to automatically switch to speaker when not at the ear
6. IMEI and phone numbers hidden in About menu
7. Built-in encrypted DNS providers, such as: Cloudflare (US); LibreDns (Germany); AdguardDns (Cyprus); and PowerDns (Netherlands)
8. Wakelock and Alarmblocker
9. Fully working Call recording with the button visible in Dialer
10. A choice between the latest Bromite and Vanadium webview
11. Deskclock app modified to work with PowerOn alarm. The app will boot the phone 2 minutes before scheduled time to trigger the alarm on time
12. Default Dark mode
13. All regular customizations plus. You tell me which feature is missing.
14. Prebuilt Magisk. You don't have to flash it, just install Magisk manager
Install instructions:
OOS 11 in both slots required (downgrade, if needed). The best method is to use MSM tool to flash OOS 11, then transfer OOS 11 zip on your phone and do local update to populate slot B, or use Lineage's 'copy partitions' zip. Under any circumstances, do NOT change slots manually.
1. Install Jaguar recovery via fastboot: reboot in fastboot and execute the following command on your connected PC terminal:
Code:
fastboot flash recovery recovery.img
2. Download the rom to your PC. Boot the phone into recovery, set recovery for sideloading, then type on your PC terminal (which should be opened in the same directory where you had downloaded the rom):
Code:
adb sideload 'name of the rom'
3. Factory reset and reboot. You are done. If you want root, just install Magisk manager (apk) as a normal app.
All downloads are in post #3.
All subsequent releases will be in post #3
XDAevDB Information
JAGUAR R, ROM for the OnePlus 8
Contributors
optimumpro
Kernel Source Code: HERE
ROM OS Version: 11.x R
ROM Kernel: Linux 4.x
ROM Firmware Required: no lower than Android 11
Based On: AOSP/Lineage/DirtyUnicorn/Crdroid
Version Information
Status: Stable
Current Stable Version: See post #3
Stable Release Date: 2021-01-26
Created: 2021-09-29
Updated: 2023-06-06
Credit: AOSP, Lineage, DU, Crdroid, CalyxOS
The rom could be used on locked bootloader with ROOT (donate feature) with or without Gapps.
The benefits of LOCKED BOOTLOADER combined with WORKING AVB-2 protection are:
Get your DRM L1 certificate back. Most banking apps (if not all) will work with or without Magisk: you cimply get a warning 'your devices is rooted', but you can proceed to login
Security: Nobody and nothing can modify Kernel, Recovery and Virtual Partitions without triggering a red screen of death with the message 'your device is corrupted and cannot boot'.
At that point, the only option is to unlock bootloader. But, if a user had previously disabled OEM unlock in Developer settings, then unlocking becomes unavailable, and so does flashing via fastboot. In other words, if your phone gets into the hands of an adversary, their only option is to use MSM tool to make the phone work again, but no access to your data or any other partition.
Why prebuilt Magisk? Because you can't modify kernel or recovery on locked bootloader post installation, and that's exactly what Magisk does.
Also, see some screenshots attached:
For Indian Users Only: If you don't have 5G, that means that you have an older handset and Indian carriers didn't provide their modem configuration to Oneplus in time. In this case, use QPST method which has been confirmed working
June 6. New Release V-33
1. June security patches
2. Android r68
3. Kernel to .284
4. Updated webview
5. New 'about Jaguar' section
6. New system-wide accents added: total over 70
7. Forced disable AGPS toggle now disables PSDS servers too
8. Access to Radio preference in 'about phone'
9. Option for figerprint icons to take system-wide accents
10. Magisk 26 prebuilt, so, update Magisk manager
11. DocumentsUI/Files now can set homescreen shortcuts for most files
Dirty flashing on a previous release is fine
Download rom V33 VANILLA: Here
Download rom V33 FULL: Here
May 7, New Release V-32
1. May security patches
2. Android r67
3. Amoled black switch (for dark mode)
4. Sometimes missing SMS fixed
5. Kernel to .282
6.Bionic and Art updated to latest upstream (Android 13)
7. Gray accents darkened
8. Updated webview
9. InCall UI now takes selected system-wide accents
10. Battery Bar centered.
Dirty flashing is fine on a previous release
Download rom V32 Vanilla: Here
Download rom V32 Full: Here
April 11. New Release V-31
Big list:
1. April security patches.
2. Android r66
3. Toggle to disable AGPS
4. Toggle to disable Direct Share
5. Number of users increased to 32
6. Webview to 112.x
7. Kernel to .280
8. No phone ID sent to servers when AGPS used
9. Shelter integrated as Work Profile Manager
10. No more statusbar icons cut off when burnin is shifting
11. No more ghost fingerprint icon.
Dirty flashing is fine on a previous release.
Download rom V31-VANILLA: Here
Download rom V31-FULL: Here
March 21. New Release V-30.1
1. Fixes a bug (not attaching photos in messengers) introduced in V30
2. Fixes a long press on Data QS toggle.
Dirty flashing is fine on a previous release
Download rom V30.1 VANILLA: superseded
Download rom V30.1-FULL: superseded
March 15. New Release V-30
1. March security patches
2. Android r65
3. Internal Firewall icon shown in status bar when an app access is denied
4. GPS does not turn automatically during emergency call unless enabled by user
5. Webview to 111
6. Some new ringtones/alarm/notifications sounds added
7. Kernel to .275
Dirty flashing is fine on a previous release
Download rom V30 Vanilla:Removed see above
Download rom V30 Full: Removed see above
February 16. New Release fixing several issues:
1. After a phone call, all sounds switch to the upper speaker (fixed)
2. White on light gray background for some notification icons (fixed)
3. FOD icons will be visible again
4. Residual flickering on fod wake up removed
Dirty flashing is fine on a previous release
Download rom V29.1 VANILLA: go to the top for latest
Download rom V29.1 FULL: go to the top for latest
February 7. New Release V-29
1. February Security patches
2. Android r64
3. Kernel to .271
4. Ability to display true app icons in Statusbar/Lockscreen Notification
5. Sound pulse: new placing options
6. Updated Opencamera
7. Webview to 109
8. Adaptive network connectivity (battery saving feature)
9. Fixed network traffic arrows
10. Fixed charging sounds - Connect/Disconnect
Download rom V29 VANILLA: Superseded
Download rom V29 FULL: Superseded
January 4. New release V-28
1. January security patches
2. Android r63
3. Kernel to .269
4. Bionic ported from Android 13
5. Smart pixels removed (poorly implemented and unfixable)
6. Trustcor certificates removed
Dirty flashing is fine on a previous release
Download rom V28 VANILLA: superseded
Download rom V28 FULL: superseded
December 6. New release V-27
1. December security patches
2. Android r62
3. Kernel to .267
4. Full internal Firewall (In Settings/Network & Internet
5. Multi-resolution for Gcam
6. Background notification opacity
7. Webview to 108
8. Reworked Connectivity settings: make sure it is OFF in Settings/Network & Internet, then toggle airplane mode OFF/On.
Dirty flashing is fine on a previous release
Download rom V27 VANILLA: superseded
Download rom V27 FULL: superseded
November 9. New release V-26
1. November security patches
2. Android r61
3. Kernel to 4.19.264
4. Toggle to turn on/off screenshot saving (Settings/Privacy)
Download rom V26 VANILLA: superseded
Download rom V26 FULL: superseded
Dirty flashing on top of a previous release is fine.
October 28. New release: V25-2
1. Working display colors: Vivid, Natural, Amoled, Srgb and P3
2. Dialer, Contacts, Calendar and Calculator are aligned with system-wide accents
3. Screen flickering leftovers on FOD unlock are completely gone
4. Smart pixels no longer disable permissions
5. Webview to .107
Download rom V25.2 VANILLA: Here
Download rom V25.2 FULL: Here
Dirty flashing on a previous release is fine
October 14. New release V-25.1
1. Return of prebuilt Magisk (25.2). So, no need to flash, just install Magisk Manager and let it finish setup
2. Option to disable Screenshots (in Settings/Privacy): When disabled, screenshots are taken, but not saved.
3. Updated webview
4. Kernel to .261
Download rom V25.1 VANILLA: Here
Download rom V25.1 FULL: Here
October 5. New release V-25
1. October security patches
2. Android r60
3. Kernel updated to 4.19.260 including the latest CVE
4. Fingerprint brightness flickering - addressed
5. Webview 106.x
Dirty flashing on a previous release is fine
Download rom V-25 VANILLA: Here
Download rom V25 FULL: Here
September 7. New release V-24: major update
1. September security patches
2. Android r59
3. Updated kernel with latest upstream CVE
4.Ability to change clock size in statusbar and quicksettings
5. Rom is now compatible with Magisk 25 and Lsposed
6. Fingerprint enrollment fixed
Dirty flashing is fine on previous releases
Download rom V-24 VANILLA: Here
Download rom V-24 FULL: Here
August 6. New release V-23
1. August security patches
2. Android r58
3. 5G network options in OneplusSettings
Dirty flashing is fine on a previous release
Download rom V-23 VANILLA: Here
Download rom V-23 FULL: Here
July 7. New release V-22
1. July security patches
2. Android r57
3. Clear clipboard quick setting toggle
4. Metro audio player
5. Many under the hood improvements
Dirty flashing is fine on a previous release
Download rom V-22 VANILLA: Here
Download rom V-22 FULL: Here
June 7. New release V-21:
1. June security patches
2. Android r56
3. Automatic sleep/suspend mode (scheduled by a user) in Settings/Battery
4. 'Internet permission missing' issue with several apps fixed. Now, all apps including Googleplay, as well as third party apps, have no problems connecting to the internet (no F/C)
Dirty flashing is fine on a previous release
Download rom V21 VANILLA: Here
Download rom V21 FULL: Here
Recovery: Here
May 29. New release V-20.2
1. Captive portal now On/Off
2. Addressed some apps crashing with message "missing Internet permission'
3. HBM fixed, now fully working (Auto HBM is recommended with trigger set to 50000 lux in Oneplus Settings)
4. One shot auto-brightness
5. In-call volume increased for Speaker and Headset
Dirty flashing is fine on top of a previous release
Download rom V20.2 VANILLA: Here
Download rom V20.2 FULL: Here
May 11. New release V-20.1
1. Redone adaptive brightness
2. Call recording (bug introduced in V-20) fixed
3. Captive portal: added 3 options Standard (Google), Alternative and Disabled) and moved to Settings/Network
4. Fingerprint icons and colors made more transparent, so, now fingerpint works flawlessly.
As always, dirty flashing is fine on previous releases
Download rom V-20.1 VANILLA: Here
Download rom V-20.1-FULL: Here
May 6. New release, V-20
1. May security patches
2. Google r55
3. Recovery fixed to have 'yes/no' prompt on signatures mismatch (for Magisk)
Download rom V-20 Vanilla: Here
Download rom V-20 Full: Here
Recovery: Here
May 3. New release
1. Wakelock blockers in kernel
2. Jaguar version is now displayed in About phone
3. Choice for temperature units F/C for lockscreen battery info
4. A bunch of other under the hood improvements
Download rom Full Version: Here
DOwnload rom Vanilla Version: Here
April 15. New release V-19.1
1. AOD is fully working (see screenshot Here)
2. Experimental feature: toggle to spoof Pixel to get unlimited storage for Google Photos (in Settings/Accessibility)
Dirty flashing on a previous release is fine.
Download V-19.1-VANILLA: Here
Download V-19.1-FULL: Here
Recovery: Here
April 6 New release V-19
This version fixes Safetynet with Magisk 24.3. Confirmed with screenshorts: see here
1. April security patches
2. Google r54
3. Switched to AOSP webview 100.x
4. Should work with Zgisk (confirmed)
5. Pre-root removed (users can flash Magisk 24.3 even on locked bootloader)
6. Seedvault is back
Dirty flash is fine on a previous release
Download rom V-19 Vanilla: Here
Download rom V-19 Full: Here
Download latest recovery: Here
March 23. New release.
1. From now and on there will be 2 versions of the rom Full and Vanilla
2. Updated kernel, which includes Spectre 2 implementations
3. Updated icons for Display calibration
Dirty flashing is fine on top of a previous release.
Download rom V-18 FULL: Here - this one needs nothing else to flash including Magisk
Download rom V-18 Vanilla: Here
March 8, New release, V-18
1. March security patches
2. Android r53
3. User build
4. Updated kernel
5. Options to choose between Bromite and Vanadium webivew
Dirty flashing on top of a previous release is fine.
Download rom V-18: HERE
February 17. New release
1. Another attempt to fix Safetynet
2. Torch flashing on incoming calls
3. NightDisplay renamed to Display calibration
Dirty flash is fine on a previous release
Download rom: HERE
Download recovery: HERE
February 8. New release, V-17
1. February security patches
2. Android r52
3. Regular webview, as opposed to bromite
4. Toggle to hide statusbar clock when launcher is active
5. New recovery that fixes 'not enough space' issues with some Gapps
Dirty flash on a previous release is fine
Download rom V-17: HERE
Recovery: HERE
January 12. New release
Using Android S safety net attestation: should pass without Magisk modules:
Although, I don't have Gapps, but Santander bank app and Netflix work without 'root detected' warning
Dirty flash is fine
Download rom: HERE
Download recovery: HERE
January 5, 2022. New release V-16
1. January security patches
2. Android r51
3. NightDisplay crash fixed
4. OpenCamera HDR etc. crashes fixed
5. Updated vendor blobs
Dirty flashing is fine on a previous release
Download rom V-16: HERE
Download recovery: HERE
December 20. New release, which fixes Safetynet
Dirty flashing is fine
Download rom: HERE
December 13. New Release V-15.1
1. Another attempt to fix Safetynet
2. Also fixes fingerprint enrollment on fresh install
Dirty flash is fine on a previous release
Download rom V-15.1: HERE
December 7: New Release V-15
1. December security patches
2. Android r50
3. FOD features are back
4. Nightlight and NightDisplay with picture adjustment and antiflicker are back
5. Double tap to wake is visible
6. Safetynet should pass (need to confirm)
Dirty flash is fine on top of a previous release
Download rom V-15: HERE
November 3, New release V-14
1. November security patches
2. Android r49
3. Updated vendor blobs
4. Ambient display sensor fixed
5. Snap camera replaced with Open Camera
Dirty flash is fine on top of a previous release.
Download rom V-14: HERE
October 20. New release
1. Built from scratch in a separate environment from other devices to get rid of conflicts.
2. Clean-flashed on my own Oneplus 8: everything seems to be working
Download rom: HERE
Recovery: HERE Unzip first, then install in fastboot
October 14. New release, V-13.1
1. AOD fixed for Oneplus 8 series
2. Tilt, Pulse, Pocket, Edge Light with color options, Wake on Notivications all work
3. AOD on charge only option
4. Screen unlock delay is gone
5. Statusbar brightness gesture redone
6. Padding added to statusbar left clock (away from front camera hole)
7. Nightlight tile visible now
8. Clear all recents gesture (working for gestural navigation too) in Launcher/Settings/Misc
9. Enlarged system partition to allow installation of larger Gapps
Could be flashed dirty on top of a previous release
Download Rom V13.1: HERE
October 5. New release, V-13.
1. Google r48
2. October security patches
3. Internal firewall fully working
4. Redone doze
5. Updated kernel
Could be flashed dirty on top of a previous release. Otherwise, clean flash
Download rom V-13: HERE
Download recovery: HERE
October 2. New release
1. Updated kernel
2. Updated recovery with new features: ability to change slots; wiping System partition; and allowing signature mismatch/downgrade
3. Build compatible with user installation of Gapps on locked bootloader normally
Could be flashed dirty on top of previous release. Otherwise, clean flash.
Download rom from here
Recovery from here
Magisk.apk (no flashing) from here
Don't flash Magisk, as it is prebuilt. Just install it as a normal app.
Screenshots?
k4ustu3h said:
Screenshots?
Click to expand...
Click to collapse
See in Oneplus 6 thread: HERE
Ohhhh this is something new. I have one app what is not possible to use it with unlocked bootloader. At this moment I'm on crDroid. What I need to do if I want be on this ROM with locked bootloader? Should I flash stock before that?
But on locked bootloader that will be possible to manage kernel and flash some custom Kernel?
krkhaha said:
Ohhhh this is something new. I have one app what is not possible to use it with unlocked bootloader. At this moment I'm on crDroid. What I need to do if I want be on this ROM with locked bootloader? Should I flash stock before that?
Click to expand...
Click to collapse
"I have one app what is not possible to use it with unlocked bootloader"
I am not sure what you mean. Locked bootloader doesn't affect apps, which you are free to install or uninstall.
You don't need to be on stock. You need to flash Jaguar, boot it and then you contact me: you'll get instructions and one additional file to flash. After that, you just relock.
krkhaha said:
But on locked bootloader that will be possible to manage kernel and flash some custom Kernel?
Click to expand...
Click to collapse
No way! You can't touch System, Recovery, Boot and Vendor partitions without unlocking. This is why Magisk is prebuilt and requires only Magisk manager to have root. But you can flash Gapps on locked bootloader.
Can you write about gapps? What exactly is in?
optimumpro said:
"I have one app what is not possible to use it with unlocked bootloader"
I am not sure what you mean. Locked bootloader doesn't affect apps, which you are free to install or uninstall.
You don't need to be on stock. You need to flash Jaguar, boot it and then you contact me: you'll get instructions and one additional file to flash. After that, you just relock.
Click to expand...
Click to collapse
Safety net is passed. I have information on screen of app my bootloader is unlocked. Some banking app can work and some is not possible even when safety net is passed and is hided in magisk hide. I know now magisk hide don't work but I checked that long time ago. I have 2 banks what can't work on unlocked bootloader.
krkhaha said:
Can you write about gapps? What exactly is in?
Click to expand...
Click to collapse
If you meant Kernel manager apps, yes, you can use them on locked bootloader, as they don't modify kernel, just send commands.
Gapps. Gapps could be flashed by users like on unlocked bootloader.
The rom has the hush signature that represents the sum of Vendor/Boot and Recovery partitions. So, any change to those partitions, except when you upgrade Jaguar, would result in 'your device is corrupt and can't boot' message.
Have you got some screenshots from additional settings? Okay I will try in the free time. At this moment I work all the time. Sounds good.
Ona bad thing is not possible to manage kernel in app I have a lot settings. And is not possible to use kona heh... You know.... From long time on radioactive mod kernel with my own settings. But with unlocked bootloader will be possible to manage kernel in app.
krkhaha said:
Ona bad thing is not possible to manage kernel in app I have a lot settings. And is not possible to use kona heh... You know.... From long time on radioactive mod kernel with my own settings. But with unlocked bootloader will be possible to manage kernel in app.
Click to expand...
Click to collapse
No. You CAN use kernel managers, as they don't modify kernel. They just issue commands.
But you can't flash another kernel.
How can I install it on Oneplus 8 TMO?, I have to unlock my bootloader install the room and relock it again?
acostmisa said:
How can I install it on Oneplus 8 TMO?, I have to unlock my bootloader install the room and relock it again?
Click to expand...
Click to collapse
Have you ever installed a custom rom on your TMO's Oneplus 8?
optimumpro said:
Have you ever installed a custom rom on your TMO's Oneplus 8?
Click to expand...
Click to collapse
yes, as you said that can be used with locked boot loader so i wanted to know if i have to unlock it, flash and relock.
acostmisa said:
yes, as you said that can be used with locked boot loader so i wanted to know if i have to unlock it, flash and relock.
Click to expand...
Click to collapse
OK. As it says above, it's a donate feature. You need instructions and additional file to flash, then you can relock. Contact me via PM.
Edit: And No, you don't have to be on stock to relock.
TELEGRAM CHANNEL ADDED: HERE
TELEGRAM CHAT GROUP: HERE
I normally build roms for Oneplus devices, but one of Xperia users donated and asked to build for Xperia XA2 Ultra. XA2 Ultra doesn't have a lot of options, so, here it is:
I have been building Android roms since 2012 for various devices including multiple Sonys, Lenovo Zuk, Oneplus 3, Oneplus 5, 6, 8 and 9. You can check my Oneplus 6 or Oneplus 6T or Oneplus 8 threads and browse my profile.
Jaguar rom is focused on hardening of AndroidOS and kernel. As such, the rom has hardened bionic, art, framework and tightened security.
1 Rom control with custom Power options, Statusbar, Buttons, Navbar, Quicksettings, Lockscreen, Notifications, Gestures, Themes etc...
2. Heavily modified Art, Bionic System/Vold and System/Security
3. Telephony response to Type Zero sms ('silently acknowledged') disabled
4. Toggle to disable Captive Portal logging.
5. Speakerphone proximity sensor toggle - could be set to automatically switch to speaker when not at the ear
6. IMEI and phone numbers hidden in About menu
7. Built-in encrypted DNS providers, such as: Cloudflare (US); LibreDns (Germany); AdguardDns (Cyprus); and PowerDns (Netherlands)
8. Wakelock and Alarmblocker
9. Fully working Call recording with the button visible in Dialer
10. Deskclock app modified to work with PowerOn alarm. The app will boot the phone 2 minutes before scheduled time to trigger the alarm on time
11. Default Dark mode
12. All regular customizations plus. You tell me which feature is missing.
The rom has 2 versions Vanilla (no Gapps) and Full. So, pick according to your needs.
Install instructions
Xperia AX2 Ultra is somewhat easier to deal with (because it doesn't have virtual partitions). So, the only requirement is to be on the latest stock firmware in both slots, and unlocked bootloader, of course. If you have been using Lineageos 18-19, you already have it. If not, install stock and then use Lineage's copy-partitions zip to populate another slot.
1. Either boot official TWRP and flash the rom followed by factory reset, or boot my recovery and sideload the rom also followed by factory reset.:
The command to boot recovery (from fastboot) is simple:
fastboot boot 'recovery name' (without quotes).
The first boot might take longer, because your phone will be encrypted.
2. Magisk: only versions 24.3 and higher will pass Safetynet. However, don't use TWRP, or any other recovery, because you won't boot. Rather install Magisk as a regular app, take boot.img I provide (the same as recovery), put it on your internal storage and patch from the app. Then install the new image (Magisk will tell you where it would save it) via fastboot: fastboot flash boot boot.img.
Download rom V20.2-VANILLA: Here
Download rom V20.2-FULL: Here
Download recovery (same as boot.img): Here
All subsequent releases will be in post #3.
XDAevDB Information
JAGUAR R, ROM for Sony Xperia AX2 Ultra
Contributors
optimumpro
Kernel Source Code (for now Lineage kernel): Here
ROM OS Version: 11.x R
ROM Kernel: Linux 4.x
ROM Firmware Required: no lower than Android 11 + unlocked bootloader
Based On: AOSP/Lineage/DirtyUnicorn/Crdroid
Version Information
Status: Stable
Current Stable Version: See post #3
Stable Release Date: 2021-01-26
Created: 2021-01-29
Updated: 2022-10-18
Credit: AOSP, Lineage, DU, Crdroid, GrapheneOS, CalyxOS
Why not Android 12? Because Google's major new releases don't become stable until at least r50+. Why? Ask Google. My view is: their primary focus is on advertising revenue, hence, everything else is on the back burner.
In addition, I personally dislike Android 12 (12L): you get some minor UI changes in exchange for giving up more privacy..
Screenshots: see Here
Magisk 25 and LSposed are loading now.
October 18. New release V025:
1. October security patches
2. Android r60
3. System webview to 106.x
4. Ability to disable screenshots saving: when disabled, screenshots are taken, but not saved
Native video still doesn't work and probably will never work due to the phone's low ram
Dirty flashing is fine on a previous release
Download rom V25 VANILLA: Here
Download rom V25 FULL: Here
September 13. New release V-24: major update
1. September security patches
2. Android r59
3.Ability to change clock size in statusbar and quicksettings
4. Rom is now compatible with Magisk 25 and Lsposed
5. AOD is fully working
6. DIaler: toggle for post-call snackbar
7. System webview to 105.x
Native gallery still cannot play videos and probably won't ever, as Jaguar takes more ram than Lineage: XA's 4GB of RAM is simply not enough. Use VLC player, which works fine.
Download rom V24-VANILLA: Here
Download rom V24-FULL: Here
August 21. New release V-23
1. August security patches
2. Android r58
3. Video playing may or may not be fixed (no longer have the device)
Dirty flashing is fine on a previous release
Download rom V-23 VANILLA: Here
Download rom V-23 FULL: Here
July 8. New release V-22
1. July security patches
2. Android r57
3. Automatic sleep/suspend mode (scheduled by a user) in Settings/Battery
4. 'Internet permission missing' issue with several apps fixed. Now, all apps including Googleplay, as well as third party apps, have no problems connecting to the internet (no F/C)
5. Many under the hood improvements
Dirty flashing on top of a previous release is fine. Otherwise, clean flash.
Download rom V-22 FULL: Here
Download rom V-22 VANILLA: Here
Does miracast work in this rom, and when mirroring could it black/turn off the screen. This is possible with the stock firmware and i hope that its also possible with the jaguar rom.
July 8. New release V-22
1. July security patches
2. Android r57
3. Automatic sleep/suspend mode (scheduled by a user) in Settings/Battery
4. 'Internet permission missing' issue with several apps fixed. Now, all apps including Googleplay, as well as third party apps, have no problems connecting to the internet (no F/C)
5. Many under the hood improvements
Download in post #3.
Newpipe does not work and possibly other videoplayback applications, doesn 't work in the browser . Only YouTube video plays. And could you integrate audio boost Ainur narsil, Viper or Sound Enhancement Sony Xperia 10 and then magisk is not needed
TheStormRanger said:
Newpipe does not work and possibly other videoplayback applications, doesn 't work in the browser . Only YouTube video plays. And could you integrate audio boost Ainur narsil, Viper or Sound Enhancement Sony Xperia 10 and then magisk is not needed
Click to expand...
Click to collapse
That's because you are using MicroG and you have NOT enabled 'signature spoofing' in Settings/Privacy. Most Google apps will NOT work with MicroG, unless signature spoofing is enabled.
optimumpro said:
That's because you are using MicroG and you have NOT enabled 'signature spoofing' in Settings/Privacy. Most Google apps will NOT work with MicroG, unless signature spoofing is enabled.
Click to expand...
Click to collapse
I am using the full version 22. Everything is already installed there. Changing the settings doesn't help. Newpipe and other software always work without Google services and MicroG. It's sad that not all software works. Your firmware is good, including Bluetooth and security tweaks
TheStormRanger said:
I am using the full version 22. Everything is already installed there. Changing the settings doesn't help. Newpipe and other software always work without Google services and MicroG. It's sad that not all software works. Your firmware is good, including Bluetooth and security tweaks
Click to expand...
Click to collapse
The same for me. Video playback doesn't work. I don't have microg installed. Even the video stored on the phone, or the video recorded with the camera doesn't work. Other than that, everything seems to be working great.
Sorry for my English...
My problem is cannot use Video Playing (From Facebook and other app)
If I play video , it show only black screen . How to fix it
[email protected] said:
Sorry for my English...
My problem is cannot use Video Playing (From Facebook and other app)
If I play video , it show only black screen . How to fix it
TheStormRanger said:
I am using the full version 22. Everything is already installed there. Changing the settings doesn't help. Newpipe and other software always work without Google services and MicroG. It's sad that not all software works. Your firmware is good, including Bluetooth and security tweaks
Click to expand...
Click to collapse
branja6 said:
The same for me. Video playback doesn't work. I don't have microg installed. Even the video stored on the phone, or the video recorded with the camera doesn't work. Other than that, everything seems to be working great.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
One of you would have to post a logcat running when you are trying to play videos.
optimumpro said:
One of you would have to post a logcat running when you are trying to play videos.
Click to expand...
Click to collapse
Ok, I installed a clean V22 full and a Newpipe app. And I attach the logcat. Newpipe works fine on the original firmware and Lineage and others
branja6 said:
The same for me. Video playback doesn't work. I don't have microg installed. Even the video stored on the phone, or the video recorded with the camera doesn't work. Other than that, everything seems to be working great.
Click to expand...
Click to collapse
So far the workaround to an extent is using VLC media player, so this may be some type of codec issue... Hopefully it can be resolved soon
August 21. New release V-23
1. August security patches
2. Android r58
3. Video playing may or may not be fixed (no longer have the device)
Download in post #3.
How long is the first load? I feel like it's been loading for a long time now. At least 10 minutes. Installed in twrp the latest version, was coming from stock 8. Didn't read I needed firmware 11+ until just now. Do I just wait for the phone battery to die and try again? I had planned on installing Magisk after boot, but at this point I'm not sure it is even going to boot.
rjdeleon said:
How long is the first load? I feel like it's been loading for a long time now. At least 10 minutes. Installed in twrp the latest version, was coming from stock 8. Didn't read I needed firmware 11+ until just now. Do I just wait for the phone battery to die and try again? I had planned on installing Magisk after boot, but at this point I'm not sure it is even going to boot.
Click to expand...
Click to collapse
You can always shutdown the phone by pressing 'power key' and 'volume up and down' together for 5-10 seconds.
TWRP doesn't flash well and certainly doesn't work when flashing Magisk (you'll get bootloop).
Don't use V23. Use V22. Get recovery from post #1 and flash it in fastboot like this:
fastboot flash boot_a boot.img
then
fastboot flash boot_b boot.img
Disconnect the phone and start it in recovery by pressing 'power button' and 'volume down' at the same time. Once in recovery, wipe system, then side load V22.
optimumpro said:
You can always shutdown the phone by pressing 'power key' and 'volume up and down' together for 5-10 seconds.
TWRP doesn't flash well and certainly doesn't work when flashing Magisk (you'll get bootloop).
Don't use V23. Use V22. Get recovery from post #1 and flash it in fastboot like this:
fastboot flash boot_a boot.img
then
fastboot flash boot_b boot.img
Disconnect the phone and start it in recovery by pressing 'power button' and 'volume down' at the same time. Once in recovery, wipe system, then side load V22.
Click to expand...
Click to collapse
Thank you, in recovery now about to sideload the V22, then I will reboot into the system and then reboot into recovery and sideload the V23 on top. Should I install Magisk before the V23? Or just go straight into V22 to V23? Again, thank you for responding.
rjdeleon said:
Thank you, in recovery now about to sideload the V22, then I will reboot into the system and then reboot into recovery and sideload the V23 on top. Should I install Magisk before the V23? Or just go straight into V22 to V23? Again, thank you for responding.
Click to expand...
Click to collapse
Don't use v23. I will post v24 tomorrow. I described how to apply Magisk in the OP.
ugh, unfortunately cannot sideload to it for some reason:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I am in ADB Sideload though so who knows, maybe I need to switch computers.
rjdeleon said:
ugh, unfortunately cannot sideload to it for some reason:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I am in ADB Sideload though so who knows, maybe I need to switch computers.
Click to expand...
Click to collapse
That means there is no connection between your phone and pc. May be adb drivers etc. Try to open the terminal as administrator.