Related
Is there a way to enable Moto's one button nav for the Android One variant Moto X4 without root access? Upgraded to Android Pie, Moto actions doesn't have an option for one button nav. Fingerprint nav was one of my favorite features.
Yes, but not as easy as it once was with Android 7.1.
You would have to flash the Retail version without erasing data (you can do this without unlocking bootloader). You will then have the ability to enable One Button Nav in the Motorola app.
At this point I would recommend just sticking with the Retail version as I have found nothing that I missed from Android One (other than the boot animation, maybe). You still get OTA updates just fine - in fact more timely than Android One.
This is what I have done with my second X4 (Android One/Fi). I switched to Retail without unlocking bootloader, and have been getting OTAs just fine.
But to get back to the Android One version, you would do the same process as above but with the Android One firmware, and your One Button Nav preference will stay (but lose the setting to turn it off).
Firmware:
https://mirrors.lolinet.com/firmware/moto/payton/official/RETAIL/
https://mirrors.lolinet.com/firmware/moto/payton/official/FI/
Flashing guide with some useful information:
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
I have attached my batch file (just remove the .txt extension).
jhedfors said:
Yes, but not as easy as it once was with Android 7.1.
You would have to flash the Retail version without erasing data (you can do this without unlocking bootloader). You will then have the ability to enable One Button Nav in the Motorola app.
At this point I would recommend just sticking with the Retail version as I have found nothing that I missed from Android One (other than the boot animation, maybe). You still get OTA updates just fine - in fact more timely than Android One.
This is what I have done with my second X4 (Android One/Fi). I switched to Retail without unlocking bootloader, and have been getting OTAs just fine.
But to get back to the Android One version, you would do the same process as above but with the Android One firmware, and your One Button Nav preference will stay (but lose the setting to turn it off).
Firmware:
https://mirrors.lolinet.com/firmware/moto/payton/official/RETAIL/
https://mirrors.lolinet.com/firmware/moto/payton/official/FI/
Flashing guide with some useful information:
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
I have attached my batch file (just remove the .txt extension).
Click to expand...
Click to collapse
Thank you
Hey guys
I'm coming from a OnePlus One, Lineage OS 16.0. Rooted with latest Magisk.
Over the years I've encountered several apps that wont work on a modified system - now I want to start new with the Mi9T Pro and set it up in the right way.
To start with: Will a bootloader unlock alone be detected by anything? I'm not sure what ROM to use in the end, but this is always the first step.
And since Magisk can't hide everything (e.g. health insurance apps are really strict and clever), is it possible to have two systems parallel (like dual-boot)? One "unmodified" system for all the security-concerned apps.
Or are there any other solutions for this?
Thanks!
NcX 2.5 A71 ROMPretty straight forward, I took OneUI 2.5 firmware, debloated it and added a few features which can be found here: Link to MODs
My plan is to make this the best version of OneUI 2.5 with more features and fixed things (my mission is to fix Secure Folder in the near future) Fixed
Anyway, let's get started.
Code:
Your warranty is now void.
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about flashing this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. HARD!
Features!
TWRP Included
Full OneUI 2.5 features
Debloated
Added camera features
Dolby Atmos without earphones
Optimized
Edge Lighting fully enabled
Secure Folder fixed
Smart View fixed
Samsung Health fixed
Samsung OCR service
Bugs!
Secure Folder broken (will try to fix later) Fixed on 2.5.1
Samsung Pass broken (because of knox 0x1, duh) Removed from ROM, it will never work.
Bug with AOD brightness when you use fingerprint unlock method. This bug happens when you have AOD to always show. If AOD is showing, then you turn the screen on to only show lockscreen clock and then turn the screen off for AOD to show, the brightness of AOD will reduce to the most minimal and it will be hard to see, regardless of what brightness you set up. There are 2 ways to getting rid of this bug:
Disable unlocking phone with fingerprint
Unlocking your phone and then locking it again. This will only fix it until you trigger the bug again
Fixed, clock animation removed.
You tell me
Changelog!
25/Oct/2020 (NcX 2.5.2):
Added 60 fps recording on selfie cam
Added wide selfies. (a biiiiit buggy, but serviceable)
Added 24 fps recording modes on pro video mode
Fixed Samsung Health
Added Samsung OCR Service for better text extraction
12/Oct/2020 (NcX 2.5.1):
Secure Folder fixed
Smart View fixed
AOD bug fixed
Removed Samsung Pass
Removed Samsung Daily
Removed "Tips" app
Removed Bixby
Added camera features
08/Oct/2020: Release
Links!
(V2.5.2)Google Drive
(V2.5.1)Google Drive
(V2.5)Google Drive
PrequisitesMANDATORY ALWAYS: SD Card. It IS possible to have it on internal storage but ONLY if you are not encrypted. If you are encrypted, then you will need to FORMAT DATA and that will delete everything in your internal storage and you won't be able to add it back to internal storage with TWRP because MTP is broken.For installing 2.5.1/2.5.2:
Installing and following NcX 2.5 installation steps, as well as its prequesites
TWRP Installed (included in NcX 2.5)
Download multidisabler.zip (link: From Telegram Group (also attached on this thread) and add to SD Card or internal storage
Download Magisk zip installer to your SD Card or internal storage
For installing 2.5:
Update to bootloader U3 (either install OneUI 2.1 or OneUI 2.5 fully with Odin), otherwise you will have problems with camera
Fully unlock bootloader. I don't mean just turning OEM unlock on in developer settings , I mean FULLY unlock. If you didn't know, Samsung changed up how you unlock the bootloader on newer devices like this one. @topjohnwu gets a little more specific here: Explanation but I'm going to quote the important stuff to FULLY unlock bootloader:
Unlocking BL on modern Samsung devices have some caveats, so I figure this would be helpful.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: reboot and press the download mode key combo for your device.
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
Go through the initial setup. Skip through all the steps since data will be wiped again later.
Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode.
Click to expand...
Click to collapse
Download Magisk zip installer to your SD Card or internal storage
Download multidisabler.zip (link: From Telegram Group and also attached in this thread) and add to SD Card or internal storage
Instructions!For installing 2.5.1/2.5.2:
Reboot to TWRP
Flash NcX 2.5.1.img or NcX 2.5.2 as "super" image in TWRP
Reboot to Recovery
Format data if you are coming from Stock ROM. If you are coming from NcX 2.5 then you don't need to wipe or format, you can just skip this step.
Flash multidisabler (this is required always)
Flash Magisk zip (optional)
Reboot and wait patiently
For installing 2.5:
Reboot to download mode and add AP_NcX 2.5 A71 in AP on Odin
Uncheck the Auto reboot option in Odin
Flash
When it is finished, force a manual reboot (keep pressing VOL - and Power buttons together)
Immediately when phone reboots, boot to recovery mode (VOL + and Power button)
If your phone was unencrypted before, just do a normal wipe. If your phone was not unencrypted before, do a full data format (Go to WIPE option in TWRP, select FORMAT DATA button at the bottom and they type yes on the keyboard. This will completely wipe your internal storage so be sure to backup and photos, music, etc... you have in internal media.)
Flash multidisabler to ensure you do not get encrypted
Flash magisk (I don't know if this is mandatory, I would fully recommend it though)
Reboot and wait patiently
Credits! @ananjaser1211 for all your help and always willing to lend a helping hand
@SuperR. For his Super R's Kitchen which you can find here: https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
@topjohnwu for Magisk
@sac23 for his tutorial on how to fix Secure Folder which you can find here: https://forum.xda-developers.com/showpost.php?p=82978861&postcount=1522
@Belco02 for the extra camera modes and features
@ianmacd in Telegram group TWRP/Root Samsung Android Devices for compiling TWRP for us
@ Samsung for the firmware
@ Team TWRP for their amazing recovery
@ To users like you!
If you feel I missed you, please give me a PM so I can add you
XDA:DevDB Information
NcX 2.5 for A71, ROM for the Samsung Galaxy A71
Contributors
ShaDisNX255, Ian Macdonald
Source Code: https://github.com/ianmacd/twrp_a71
Source Code: https://github.com/ianmacd/a71
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: OneUI 2.5
Version Information
Status: Stable
Current Stable Version: 2.5
Stable Release Date: 2020-10-08
Created 2020-10-08
Last Updated 2020-10-08
Join our Telegram group
Code:
Check out the latest projects on our Telegram group, where we share our advancement on new things and try to help as best as we can.
For anything already released, please ask here in XDA
Link: Telegram Group
Join our Discord group
Code:
Check out the latest projects on our Discord, where we share our advancement on new things and try to help as best as we can.
For anything already released, please ask here in XDA
Link: Discord
Android group in spanish
Link: Grupo Android
FAQ
[Q] My phone is stuck in bootloop/infinite boot, what should I do?
[A] It is normal for first instalation to take aprox 10-20 minutes on first boot, let it sit for a little bit
[Q] Even after 20 minutes, my phone is still in a bootloop/infinite boot, what can I do?
[A] It is possible that your previoius Android setup is conflicting with this new setup. Please, do the following:
1. FORMAT DATA (not WIPE, FORMAT!)
2. Try the instalation of NcX again
[Q] I've found a bug, what should I do
[A] Please read the "Bugs" section of the thread to see if your bug has been reported, if it hasn't, please let me know exactly what the problem is so I can take a look
[Q] I flashed magisk on TWRP but no apps are asking for SU Permission
[A] Make sure you have the Magisk Manager app installed
[Q] I don't see Magisk Manager in my apps
[A] You need to download the manager from the official source: https://github.com/topjohnwu/Magisk
[Q] Something bothers me and I want it fixed/changed
[A] Please, kindly make a request and if it's within my grasp, I'll try to fix it. Just, don't be rude and demand something. Either that or return to stock, your choice
How to report a bug/Ask for a change
Over the small amount of time I've been doing my edits and shared them with the community, I've noticed something that seems to irritate me. I can't speak for all the developers on this forum, but I do edits/ROMs/PORTs/etc... to what I like. I don't work for anybody else but me. I share my work because it may have something of value to other people and/or some people may share the same taste as me on regards to what they want on a ROM.
That being said, that doesn't mean I will completely ignore what the community has to say.
First and foremost, it must be said, I am merely a beginner. I do not claim to be a professional developer that knows how to add everything, I am nowhere close and I learn as I go.
There are ways to ask for something and/or report a bug when it comes to ROMs, and this post is my attempt to try to explain how to (and how not to) report a bug in order to help me out as much as possible to try to fix something
You can also ask for something to be added, but there are also ways to ask for something
So, here we go
Keep in mind:
I do not add stuff that can easily be downloaded from the Playstore
I, myself, don't do kernel edits
I COULD remove stuff if NOBODY uses it
---REPORTING BUGS---
How NOT to report a bug:
"SystemUI (or any app)is crashing, please help!"
"Instagram doesn't allow me to edit my post, what could be wrong?"
"My bank account app is not letting me do such thing"
These posts are sort of pointless as they only state something but I have no context on what could be causing it. Also, I can't really control (for the most part) third-party apps, so if you're going to ask about them this way, don't even bother
A slightly better way to report a bug:
"I clean installed the ROM and was working fine, after I installed Facebook and logged in, I immediately uploaded a photo and SystemUI started to crash. Can you look in to it?"
"I tried to install Black Neon theme (a link to it would work as well) and it was working fine until I tried to activate AOD (or anything else for some reason) and SystemUI (or any other app) is crashing, could you look in to it?"
"My bank account app doesn't let me take a screenshot of my accounts. I get a toast notification saying "Can't take screenshot due to security policy"
As you can see, this provides a bit more context and explanation on your current situation. This gives me a little more detail on trying to replicate the problem and hopefully could fix it by replicating it. Well, except for point #3 which is out of my hands for the most part (I think). If you include what kernel you're using would make everything better! Also any significant change that would require root (like xposed and or anything that modifies /system also needs to be informed for better results)
The BEST way to report a bug:
LOGCAT!!!!!!!!!!!!!!!!!!
Please learn the ins and outs of a logcat, this really helps a lot on finding what the problem is. Also, please give a brief explanation as the above examples when providing a log cat
---ASKING FOR STUFF TO BE ADDED---
How NOT to ask for stuff:
On your next update, add iris scanner
You should add (app) on your next update
Hey, please add (app or feature) on your next update
No, I do not work for you. Even if you say please like the third example, that doesn't mean you're being polite. It still sounds like an order lol so you should probably rephrase your request.
How to ask for stuff to be added to my work:
Would you be so kind to add (feature) to your ROM, if possible?
Would it be possible to add this app to your ROM?
Please, can you add (feature) to your ROM, if it isn't much to ask?
See how politeness makes everything better? You're not demanding it, you're just politely asking to see if maybe it is within my grasp to add something. And if all request would be like this, I can assure you I'd try my best to add said feature
I hope this is useful to you or I at least hope that some people read it.
If not, I can just tell you to return to stock ROM, probably better than any ROM I put out anyway
Enjoy guys, keep on the lookout for updates. I plan on adding more MODs and fixes
Attach the singletake .xml also here
sankhauaa said:
Attach the singletake .xml also here
Click to expand...
Click to collapse
I'll hold it off.
Plan on adding a future update with this and more stuff included
Good mod! Downloading...
well done mate, nice to see
New update hopefully tomorrow.
What's new?
-Fix Secure Folder, now working
-Fix Smart View mirroring, now working
-Adding CSC features, in progress
When i try to do the process of unlocking again It say after long press volume up. Lock Bootloader? Guess thats not what i want? My device is rooted stock with twrp installed..... Do you have an idea.?
I want to install your rom.
hans3103 said:
When i try to do the process of unlocking again It say after long press volume up. Lock Bootloader? Guess thats not what i want? My device is rooted stock with twrp installed..... Do you have an idea.?
I want to install your rom.
Click to expand...
Click to collapse
If you've already rooted, that means you have fully unlocked bootloader and it means that you can now freely install my ROM.
I installed it, it look very good. Its a big timesaver also. I used to root this device in a time comsuming way. This rom is very easy.... Very nice work!
hans3103 said:
I installed it, it look very good. Its a big timesaver also. I used to root this device in a time comsuming way. This rom is very easy.... Very nice work!
Click to expand...
Click to collapse
Thanks, next version will be easier to flash, just with super.img flash on TWRP.
ShaDisNX255 said:
Thanks, next version will be easier to flash, just with super.img flash on TWRP.
Click to expand...
Click to collapse
I will try it for sure, can I do an update or do I have to make a clean install?
hans3103 said:
I will try it for sure, can I do an update or do I have to make a clean install?
Click to expand...
Click to collapse
It can be installed with current version so no need to wipe data
ShaDisNX255 said:
It can be installed with current version so no need to wipe data
Click to expand...
Click to collapse
Very nice....many thanks!
nice business friend
Even if resizing in vendor, it will be nice because it will be very possible to make mod and custom kernel
No idea
my galaxy a71 its still in bootloop. bootloader fully unlocked with oem activated. data formated, installed decrypted data, and magisk zip installed, pls help..
zorexblade said:
my galaxy a71 its still in bootloop. bootloader fully unlocked with oem activated. data formated, installed decrypted data, and magisk zip installed, pls help..
Click to expand...
Click to collapse
Are you getting to boot animation?
Were there any red messages in TWRP when you were installing?
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. A direct link to kernel sources can be found here. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
https://wiki.lineageos.org/devices/sake/install
Download:
https://download.lineageos.org/sake
Reporting Bugs:
DO NOT report bugs if you're running a custom kernel or you installed Xposed.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless.)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Thank you for that!!
Pre install of stock android 12 needed?
thanks pro
NisseGurra said:
Pre install of stock android 12 needed?
Click to expand...
Click to collapse
Yes, I'll update description to clarify that. If you try and boot into the LOS 19 recovery with Android 11 firmware it will crashdump.
GMS = Google ? Service?
I'm trying this right now. Hopefully I make it functional before I have to head to bed.
eVen123 said:
GMS = Google ? Service?
I'm trying this right now. Hopefully I make it functional before I have to head to bed.
Click to expand...
Click to collapse
Google Mobile Services, basically google apps and services
Also @ZVNexus, the google drive folder for the build without GMS seems to be empty, has it been removed?
Update:
I had a clean flash of:
WW-ZS590KS-31.0803.0403.54-DEV-2109-M3.13.24.46-SM8350_0000110-1.1.25-user_20210831-release_for_google
I was able too boot to TWRP. It wouldn't allow me to flash your zip. I rebooted to bootloader and flashed vendor_boot. After that, I was unable to get to TWRP recovery. I flashed boot and got to some sort of LOS-like recovery (purple color).
Flashing the image now.
UPDATE: Success. However, I was in a bootloop. Got back to recovery, it suggested to wipe data. It looks like LOS is now performing it's first boot.
UPDATE 2: First boot successful! Got into language and network selection. Seems to be stuck on "Getting your phone ready" step. Scratch that, we got past that! Big success!
UPDATE 3: Got past that bit, it was in "Getting your phone ready" process a long time. Booted now!
AWESOME, thank you for your work!
For anyone else reading, the TLDR:
Installed the above zip (downloaded from official ASUS site). https://www.asus.com/Mobile/Phones/ZenFone/Zenfone-8/HelpDesk_Manual/
Downloaded all the files provided by the author
Flashed boot and vendor_boot
Went to recovery, flashed the ROM zip with "apply update" and "sideload"
Bootloped a couple more times
Recovery suggested I clean data. I did.
...
Works
UPDATE 4: Note - it seems that fingerprint still makes full screen go max brightness + it doesn't work with screen off.
Adaoh said:
Google Mobile Services, basically google apps and services
Also @ZVNexus, the google drive folder for the build without GMS seems to be empty, has it been removed?
Click to expand...
Click to collapse
Nothing was ever uploaded to it. I haven't made a build without GMS yet.
eVen123 said:
Update:
I had a clean flash of:
WW-ZS590KS-31.0803.0403.54-DEV-2109-M3.13.24.46-SM8350_0000110-1.1.25-user_20210831-release_for_google
I was able too boot to TWRP. It wouldn't allow me to flash your zip. I rebooted to bootloader and flashed vendor_boot. After that, I was unable to get to TWRP recovery. I flashed boot and got to some sort of LOS-like recovery (purple color).
Flashing the image now.
UPDATE: Success. However, I was in a bootloop. Got back to recovery, it suggested to wipe data. It looks like LOS is now performing it's first boot.
UPDATE 2: First boot successful! Got into language and network selection. Seems to be stuck on "Getting your phone ready" step. Scratch that, we got past that! Big success!
UPDATE 3: Got past that bit, it was in "Getting your phone ready" process a long time. Booted now!
AWESOME, thank you for your work!
For anyone else reading, the TLDR:
Installed the above zip (downloaded from official ASUS site). https://www.asus.com/Mobile/Phones/ZenFone/Zenfone-8/HelpDesk_Manual/
Downloaded all the files provided by the author
Flashed boot and vendor_boot
Went to recovery, flashed the ROM zip with "apply update" and "sideload"
Bootloped a couple more times
Recovery suggested I clean data. I did.
...
Works
UPDATE 4: Note - it seems that fingerprint still makes full screen go max brightness + it doesn't work with screen off.
Click to expand...
Click to collapse
Updated OP to specify the exact version you need to be on [31.1004.0404.81 (or .71)]. Basically just a public release, not a beta.
What I was able to test now, it's pretty good. Very usable already!
Bugs I notice:
The GMS seems to be a bit slower than expected.
Fingerprint doesn't work with screen off.
Fingerprint request location is not marked.
Fingerprint maxes brightness of whole display.
Task switcher sometimes doesn't work.
Bottom navigation sometimes disappears.
It keeps warning me about SELinux not enforcing issue. Not sure if that's intended/known.
More bugs I noticed after a day of use:
Google account data doesn't want to sync. Perhaps android 11 -> 12 mismatch?
Touch reader stopped working (required forced reboot).
Can't log in certain applications (don't know if it's a ROM issue).
eVen123 said:
What I was able to test now, it's pretty good. Very usable already!
Bugs I notice:
The GMS seems to be a bit slower than expected.
Fingerprint doesn't work with screen off.
Fingerprint request location is not marked.
Fingerprint maxes brightness of whole display.
Task switcher sometimes doesn't work.
Bottom navigation sometimes disappears.
It keeps warning me about SELinux not enforcing issue. Not sure if that's intended/known.
More bugs I noticed after a day of use:
Google account data doesn't want to sync. Perhaps android 11 -> 12 mismatch?
Touch reader stopped working (required forced reboot).
Can't log in certain applications (don't know if it's a ROM issue).
Click to expand...
Click to collapse
SELinux isn't enforcing because it's one of the first builds right after a bringup.
Put up a new build with some things resolved, notably SELinux is now Enforcing.
I also switched from stock's prebuilt NXP NFC stack to the open source stack. Anyone who is able to make payments with Google Pay or something like that, let me know if it works.
Added a vendor_dlkm partition to hold vendor kernel modules so you can flash a different vendor regardless of the kernel situation as the modules are no longer held there.
Enabled automatic brightness by default.
Fixed night light by correct PIxelworks device detection.
Switched from QTI BT to AOSP BT until it gets merged.
Put out a new build.
Upped kernel target level from 5 to 6. The new minimum requirement of level 6 is a minimum kernel version of 5.4.86. To comply with this I updated kernel to LA.UM.9.14.r1-16300-LAHAINA.0.
Also dropped Snapdragon Camera overlays in /vendor as it won't be supported this cycle. Just Camera2 unless I can somehow figure out getting ASUS Camera working.
Automatic brightness is now enabled by default.
Synced with latest lineage-19.0 sources which last I checked now include some theming stuff(?).
Alright, just thought I'd ask here.
I unlocked my BL and disabled some apps. Was running on stock rom!
Just tried to upgrade to Android 12 to be able to flash this rom but it is now stuck on a ramdump screen. Note: it is stuck on this screen with the Official Asus image! I had LOS18 on this device before but was running it for a few months with the stock rom (because of the camera in LOS).
It gets stuck in a loop. When I power down the phone (all 3 buttons for ~10s) it just gets me back to the ramdump.
Even using ASUS recovery RAW image and the instructions from this thread does not work: https://forum.xda-developers.com/t/full-recover-to-stock-if-things-went-really-bad.4337467/ .
After going to fastboot I am NOT able to flash the official ASUS Android 12 image, it just stops on 1/2 and does not give any details.
I am able to flash LOS recovery, LOS18 (latest) and AFTER that I am able to flash back to stock Android 11 (NOT 12, that gives me a ramdump again).
This cost me about half a day to figure out.
Anyone know what is going on and what I can do to get my phone to some kind of normal state when installing roms???
EDIT:
Just got completely stuck on ramdump.
Only thing that helped was: erase vendor_boot, boot_a/b partitions and do fastboot snapshot-update cancel . After that I was able to recover using the link above. Actually got scared there for a sec...
Uploaded a build without GMS for people who don't like using GMS.
Tap to wake functional?, installed "no gms", runs nicely
ZVNexus said:
Put out a new build.
Upped kernel target level from 5 to 6. The new minimum requirement of level 6 is a minimum kernel version of 5.4.86. To comply with this I updated kernel to LA.UM.9.14.r1-16300-LAHAINA.0.
Also dropped Snapdragon Camera overlays in /vendor as it won't be supported this cycle. Just Camera2 unless I can somehow figure out getting ASUS Camera working.
Automatic brightness is now enabled by default.
Synced with latest lineage-19.0 sources which last I checked now include some theming stuff(?).
Click to expand...
Click to collapse
Working great so far. I am having one issue where once I unlock the phone (and the screen gets really bright to read the fingerprint), it stays bright. If I tap the brightness slider, it doesn't move but it adjusts the brightness to what it should be according the slider.
This is the case with and without Adaptive Brightness enabled.
NisseGurra said:
Tap to wake functional?, installed "no gms", runs nicely
Click to expand...
Click to collapse
NisseGurra said:
Tap to wake functional?, installed "no gms", runs nicely
Click to expand...
Click to collapse
No, Tap to Wake does not work.
Mecallie said:
Alright, just thought I'd ask here.
I unlocked my BL and disabled some apps. Was running on stock rom!
Just tried to upgrade to Android 12 to be able to flash this rom but it is now stuck on a ramdump screen. Note: it is stuck on this screen with the Official Asus image! I had LOS18 on this device before but was running it for a few months with the stock rom (because of the camera in LOS).
It gets stuck in a loop. When I power down the phone (all 3 buttons for ~10s) it just gets me back to the ramdump.
Even using ASUS recovery RAW image and the instructions from this thread does not work: https://forum.xda-developers.com/t/full-recover-to-stock-if-things-went-really-bad.4337467/ .
After going to fastboot I am NOT able to flash the official ASUS Android 12 image, it just stops on 1/2 and does not give any details.
I am able to flash LOS recovery, LOS18 (latest) and AFTER that I am able to flash back to stock Android 11 (NOT 12, that gives me a ramdump again).
This cost me about half a day to figure out.
Anyone know what is going on and what I can do to get my phone to some kind of normal state when installing roms???
EDIT:
Just got completely stuck on ramdump.
Only thing that helped was: erase vendor_boot, boot_a/b partitions and do fastboot snapshot-update cancel . After that I was able to recover using the link above. Actually got scared there for a sec...
Click to expand...
Click to collapse
Same happenning here, booting to Android12 ramdumps me... I was able to update before but now it does not work... Also the flash script gives me an error that it did not give me before.
Code:
Project ZS590KS matching success!
Start erase misc
Erasing 'misc' FAILED (remote: 'Erase of misc is not allowed in snapshotted state')
fastboot: error: Command failed
misc flash failed!
Press any key to exit the script.
. I guess I will be staying on Android 11 then...
EDIT: Ran fastboot snapshot-update cancel like you did, and now the raw image file script works to reset the phone. Very weird. Also thank you so much, without your post, I would have never figured a way to make the script work again I am so glad you posted this
EDIT 2: After running the script (And everything working and passing) and getting everything back to normal, I was able to install Android 12 like I normally would without ramdumps
I've got an XZ1c (G8441), stock Oreo (47.1.A.12.270), I think it's the HK build (R13B). Not rooted, bootloader not unlocked. Fingerprint reader works, VoLTE & WiFi calling settings are not present. Now I'm getting texts from T-Mobile (US) saying I need to get VoLTE working or lose service.
I'd like to enable VoLTE and ideally WiFi calling, without breaking anything (fingerprint reader), without losing my data (one sms thread goes back 5 years), and with as little re-configuring of apps as is realistic.
Spent all day digging through forums, reading guides, etc. Holy sh*t - pages and pages of info, some of it conflicting and most of it 3-4 years old. So I could use a sanity check on the process before I pull the trigger. Questions:
Backup - I ran the stock Google One backup (seems to have worked), Xperia Backup (the phone app - seems to have worked), Xperia Companion backup (says messages failed, and a few other files), and SMS Backup Print & Restore (app) on that one super long sms thread. Have my photos backed up separately. Is there some other, more reliable & comprehensive backup/restore method for an unrooted phone?
Oreo Solution - can I just flash the OEM .sin file from a US build (I found G8441_Customized US_1310-4371_47.1.A.12.270_R8B online) onto my existing Oreo, using newflasher? Most sources seem to indicate that's where the VoLTE functionality is located.
Pie Solution - am I better off updating to Pie? Lots of complaints about Pie on these forums, but they're also years old - did Pie ever stabilize and get good?
Full Flash - if I do end up needing to flash a full new firmware, which files should be deleted before flashing? I'm tempted to go with 1, 2, 3, and maybe 6 or 7.
this source says just delete the Userdata .sin to keep data, and swap in OEM sim for VoLTE
this source says to also delete all the *.ta files
the post below it says delete the persist .sin (attest key)
but this source says keep cust-reset.ta
this source says keep the *.ta file from /boot, and delete the rest
this source lists several other *.sin files to delete: appslog, diag, ssd, and Qnovo
this source says newflasher now has a single prompt for keeping user data, making much of the above obsolete
UPDATE: I tried option #2, and just flashed the OEM .sin file from a US build. Both VoLTE and WiFi calling/messaging seem to be working.
Still interested in info about #1, #3 & #4, in case I decide to upgrade to Pie at some point, though.
meeotch1 said:
am I better off updating to Pie?
Click to expand...
Click to collapse
If you're considering an upgrade, why not Android 12
Thanks for the reply. I've been fine with the stock firmware - in fact, I wouldn't be updating at all, if it weren't for the forced VoLTE thing. So I'm not really looking to unlock the bootloader, or experiment too much.