- Jun 22, 2021
I have been using 1Password for years I am used to it and it suits me
Just tested 1password and it works. Show user or password next to field to select.I have been using 1Password for years I am used to it and it suits me
Autofill also works great on MIUI ROM.
However, in this ROM it doesn't show up next to the forms Field from which I would select the login credentials and log in.
I would be glad if someone who uses 1Password on this ROM could advise.
Use TWRP!Hello, I have a poco x3 nfc global version, I had the bootloader unlocked, and I had rom xiaomi eu 12.0.7 android 10, download this version "surya_global_images_V188.8.131.52.RJGMIXM_20210602.0000.00_11.0_global" install through my flash and It gave me the error: "xbl error" computer when restarting no longer turns on anything, it does not recognize fastboot only recognizes when connecting to the pc: "Qualcomm Hs usb qloader 9008 (com 10)". Any solution? Thank you.
I dont know how to help you.Hello.
Thank you very much for your willingness to help.
It's really weird, but I've had it set up exactly the same as you all along...
I've posted some pictures below.
I would like to send you also a photo directly with the application that there really is no box 1 Password I have.
But unfortunately I can't take a picture directly in the app.
I really have no idea where the problem could be :-( The Autofill feature is so addictive
And may I ask how best to proceed ?
Hello, the equipment is totally dead, it does not turn on, fastboot does not enter, recovery does not enter, from what I have read, you need to test the motherboard and flash with my flash and an authorized account of me in EDL mode.
By livin, I assume it's the one from Mandiri. I once had the same issue with Dana (another banking app working flawlessly), turn out it come from my setup:
1. Yes, I did it via recovery many times, change the recovery from inside the recovery
1. Check any workaround here to know your position, if you're sure that EDL is the only option
There is no best way for me, it depends on your needs (ex: using OTG drive to proceed for me is better). But reviewing your steps, all is okay, you may proceed with it.And may I ask how best to proceed ?
https://androidfilehost.com/?fid=14943124697586349510My procedure was as follows:
Flash Global ROM using MiFlash
It was specifically this ROM:
Subsequent installation of Recovery via Fastboot Toolkit
I used this TWRP: https://androidfilehost.com/?fid=14943124697586349510
Then I did a complete Factory reset including data format:
Wipe / Format Data / Swipe to Wipe / yes
I then rebooted back into TWRP and copied Arrow-v11.0-surya-OFFICIAL-20210617-GAPPS to a clean internal storage
Finally, I performed a standard install:
Install / Then select Arrow-v11.0-surya-OFFICIAL-20210617-GAPPS / Install Image / Swipe to confirm enrolment / And when the installation is complete, click on Reboot the system
Is this correct or am I doing it completely wrong ?
Thanks so much. Can you please confirm that you changed recovery from recovery on poco x3? Also any guide about what needs to be done before flashing recovery img and how? Like if caches etc needs to be cleared?
I got the same message today, even though I'm using 20210601 build.
Alright, I think I got it working. I had Magisk Hide for Google apps and banking already activated. I hadn't hidden the manager yet though.
To everyone, please STOP this misconception about having the need to flash magisk in order to pass safety net. Do read the OP I've clearly mentioned there's no need of a magisk or modules for safety net. Device is certified and passes safety net out of the box without need of any modifications.Mission Impossible in all custom ROMs !
1. Safetynet check the bootloader status and will automatically fail if magisk is not installed (Magisk Hide ON must be applied for this) !
2. Furthermore, now you have to install the safetynet-fix module to make your banking apps working !
3. Finally, you must hide Magisk Manager.apk with a random name too (Magisk Settings)
I'm aware of the notification led issue, its interlinked to an sepolicy denial from vendor which is quite tricky to address it while we're using the prebuilt/stock vendor. For now you can assume it as a trade off for enforcing builds. I'm working on a fix, once we start a full transition towards an OSS vendor these issues will be more convenient to be addressed.