Search results

Many improvements (audio, recharge and battery life are what I remember reading the telegram group). I deleted that build because OP is releasing a new build with more things fixed and/or improved (fingerprint reader I suppose, try asking him directly for changelog but I think you will not get...

You tried with the new build released a couple hours ago?

New build is out!

Mega.nz mirror, updated until official or until I can keep up: https://mega.nz/#F!XAIxhIAT!_I9nSVRXRC7yLgyn9ia23Q

I don't even know what's ANX camera, lol. Join the Telegram group (link in the first post) to keep yourself updated on LOS for davinci and ask this kind of questions to someone that knows more than me.

https://mega.nz/#F!XAIxhIAT!_I9nSVRXRC7yLgyn9ia23Q

Sorry to ask something that probably I can find by searching, but I'm in a hurry and very worried. Today I just changed the wallpaper on my Mi 9T and the screen started flashing on and off, I cannot connect via ADB or Mi PC suite, only via Mi recovery and only to sideload a zip ROM. I tried...

I found this code in MIUI forums, it enables DC dimming on some devices with PWM dimming. Anybody tried if this works on Mi A3? Digit this in the dialer app: *#*#3225#*#*

I'm not sure, but what happens if you reset your phone and at the start configuration you choose "India" or "China" in the country list?

New version 2.2: https://forum.xda-developers.com/showpost.php?p=80084835&postcount=310

Flash this via TWRP to add root: https://mirrorbits.lineageos.org/su/20190709/addonsu-16.0-arm64-signed.zip Flash this via TWRP to remove root: https://mirrorbits.lineageos.org/su/20190709/addonsu-remove-16.0-arm64-signed.zip

I flashed yesterday the latest version (6.7), I must say it's really good, I love all the extra features added, like the ignored notch and the OnePlus navigation gestures. I'll probably stick with this ROM for a long time. Keep the good work! I also flashed the stock ROM before, as the guide in...

You didn't read the page linked in the text you quoted... You have to enable OEM unlocking to unlock bootloader. After the bootloader is unlocked, you can disable OEM unlocking. If you unlocked the bootloader, it means you are going to modify the original ROM somehow. But if you erroneously...

I updated my previous post to write what happened after the reboot, but probably I forgot to press the send button, damn distractions... However yes, everything was fine for me also, and I got full safetynet validation now (before the CTS profile was not ok). There is also the circle battery icon.

I freshly installed the 20190601 version, with Gapps and Magisk but no TWRP, I boot it via fastboot and PC when I need it. Now I'm installing the new version via OTA, but after downloading it took around 45 minutes for installing it. Now it has finished. Does the OTA needs TWRP installed on the...

I'm sorry that I disappeared and didn't update the guide, but work and real life events come before this. I cannot reply to some help requests I received in the past weeks too, sorry again. And now that I have some little spare time, I prefer experimenting with the custom ROMs than working...

I just installed the 0529 version from scratch, I still haven't finished to setup the phone that a notification advice about this new 0530 version. So, time to test the OTA update... EDIT: everything went smooth following this guide, both in installing from scratch and in OTA seamless updating...

I didn't tried TWRP extensively, but from that little experience, it seems almost useless at the moment. I suggest following the guide in the first post, if you only need root.

Thanks for your feedback. The link to the original guide was already there since the beginning, only it's in the last line of the first post, in the credits. I updated the guide to say that the OTA update part should be working fine again with the latest Magisk. I will remove the old warning...

if you only unlocked bootloader, without any other change, you can do OTA (except Xiaomi did something wrong on its side).

Today I uploaded in the guide the last vanilla boot and patched_boot. I noticed the following: September >>> V9.6.8.0.ODLMIFF (Oreo) October >>> V9.6.9.0.ODLMIFF (Oreo) November (1) >>> V9.6.10.0.ODLMIFF (Oreo) November (2) >>> V9.6.11.0.ODLMIFF (Oreo) December (?) >>> V10.0.1.0.PDLMIFJ (Pie)...

If you have important data on the phone don't update at the moment. If you want to try anyway you must copy it to an external memory or a PC. You should download the vanilla boot 10.0.2.0 (you can find it in the first post), then boot the phone with it via "fastboot boot boot.img" If the phone...

no, because patched_boot is not flashed in the phone memory directly, only used as a temporary boot. The OTA updater must find a clean boot partition in the phone memory to proceed with the update process. But you can boot temporarily with vanilla boot like it was a patched_boot, just to check...

Probably, once boot.img is flashed on the phone, it got changed a bit (something like a signature), and it will not work correctly on other phones (just like the patched_boot.img, that could not be flashed directly, but only used to boot). Somebody already tried to only boot from your vanilla...

This boot.img is probably taken from the OTA zip with size ~70 MB. That OTA don't contains whole partitions, but only the changes from old to new partitions (it's a Delta update). The boot.img should be extracted from the full OTA zip, that contains the whole new partitions. I don't know how to...

Sorry if the question has already been asked, but I didn't find it. Does this script can auto-update hosts file without user intervention, or I have to manually run the script from time to time to stay up-to-date?

Try flashing with fastboot the vanilla boot (non-patched), it should work: fastboot getvar current-slot fastboot flash boot_? boot.img Change the ? with the letter given by the first command. Obviously the version of the vanilla boot.img must be equal to the ROM version installed at the moment...

I flashed with fastboot in Linux, using the script file that is contained in the ROM (flash_all_except_storage.sh). That's the same thing as flashing with MiFlash Tool, because it will do the same, but in Windows with a graphical interface.

Yes, at the moment I think that the anti-tamper check that before was done on the system partition, now with Android 9 is done in the boot partition also, so you're out of the OTA game as soon as you install Magisk or TWRP. I can't wait for a working LineageOS ROM... I tried the "except...

Yesterday I flashed my phone with V10.0.2.0.PDLMIFJ via fastboot, and then I installed Magisk. After a full day of using it, a notification said that the January update is ready, so I followed my own guide and got bootloop'd. I tried a couple methods to restore access to my data, but without...

I got the flu, so I have some spare time and I did minor updates to the guide, and also I upgraded to Pie my phone, with a backup + erase + full fastboot flash

Hi everyone. Long time since my last visit here. I'm very busy in those days, I hope to get some free time in the next days to update the guide if needed. I noticed that Android Pie arrived for our phones but I still haven't upgraded. There is something in the guide that needs to be changed?

Magisk works just like this, changing the /system partition without really touching it. That's because if you want to do OTA updates you need to do everything that involves /system from Magisk.

Maybe it's an app that you're using that causes that. Maybe an app that uses the accessibility services to block the rotation.

Do a full ROM flash using the batch file "flash_all_execpt_storage.bat" to keep all your data, (or the bash script with the same name if you're using a Linux distro), then install Magisk and try again the update procedure. I don't know why it didn't work, I literally did all the OTA updates...

There is a Magisk module for Busybox, just install it, reboot and you should be fine.

About the system.img not flashing, this may be the cause: https://askubuntu.com/questions/777663/simg2img-invalid-sparse-file-format-at-header-magi I'm busy right now, I hope to find a solution later, but probably the system.img file inside the OTA is in RAW format, and it has to be converted...

First post updated with November patched_boot.img, vanilla boot.img and full OTA dump as .img files. I'm sorry for the delay in uploading the new updates, but my job keeps me very busy sometimes... Obviously yes. I'd do this: uninstall AdAway, fastboot flash only the system.img extracted from...

If you enable the "systemless hosts" option in Magisk Manager before, you can use AdAway without problems (it won't modify the hosts file in the system partition).

No, because TWRP in A/B devices (like A2 Lite) is located in the boot image too. So doing the second step of your procedure will cancel the TWRP installed in the first step.

Guide updated with the new 9.6.9.0 October 2018 links: Original boot.img original boot.img 9.6.9.0 (2018 October update) - taken from OTA update Magisk-patched boot.img patched_boot 9.6.9.0 (2018 October update) - patched with Magisk 17.1 IMG files extracted from OTA update 9.6.9.0 (October...

You can't uninstall them, but you can deactivate them. If you remove them from /system you'll tamper the system partition and OTA updates will not work. Or, you can use a Magisk module to remove those apps "systemlessly" (don't remember its name at the moment).

Theoretically it should work, but Xposed through Magisk made my phone behave strange, even after uninstalling it, so I don't know for sure...

Sorry, but I don't know anything about that. It's an encryption problem, and that's why I hate data encryption on the phone: my data is not so important to be protected when some hackers physically stole my phone, it's only a nuisance when things like this happens. I can only suggest to change...

Here it is

Open the Phone app, go to the keypad and type *#*#6484#*#* Then open the first test and scroll to find the information you're looking for.

I don't know if you already did this, but try using a PC with Linux (you can use Ubuntu without installing it on the PC, then install the fastboot package).

That ROM is only a system.img file, no other partitions are involved.

It's a treble ROM, like this: https://forum.xda-developers.com/mi-a2-lite/development/9-0-pixelexperience-p-unofficial-t3840551 But as it doesn't touch the radio partitions (only the system partition), I doubt it will resolve. But many settings are stored on /system, maybe... Give it a try if...

Both guides to install Magisk are valid, but this version is more detailed. Choose what you prefer. If there is only that version on the Miui site, you can flash only that version. But why are you flashing with miflash? You got some problem?