Working on Ubuntu 20.04. I want to root my device to uninstall some apps (.apk) and possibly also install Ubuntu Touch. I want to uninstall almost all Google apps because I don't have a Google account and I don't want to. Without a Google account, you cannot use most Google applications (Gmail, YouTube, Drive...). A few months ago when I bought the device, I unlocked the bootloader, but I didn't have time to root it. Now I want to root it. I followed these TWRP for Xiaomi Mi A3 instructions and cannot flash or boot the TWRP.img. 1. I downloaded: twrp-installer-3.4.0-0-laurel_sprout.zip and twrp-3.4.0-0-laurel_sprout.img renamed it to **twrp.img** and **twrp-installer.zip**. 2. I copied the files to the device in **/sdcard** ---- adb devices adb push ~/Downloads/twrp.img /sdcard adb push ~/Downloads/twrp-installer.zip /sdcard adb reboot-bootloader ---- fastboot devices ---- fastboot flashing unlock ... FAILED (remote: Device already : unlocked!) finished. total time: 0.000s ---- fastboot flashing unlock_critical ... OKAY [ 0.026s] finished. total time: 0.026s ---- fastboot flashing get_unlock_ability ... (bootloader) get_unlock_ability: 1 OKAY [ 0.000s] finished. total time: 0.000s ---- fastboot boot twrp.img downloading 'boot.img'... OKAY [ 1.174s] booting... FAILED (remote: unknown command) finished. total time: 1.175s ---- fastboot flash recovery twrp.img target reported max download size of 804261888 bytes sending 'recovery' (39892 KB)... OKAY [ 1.172s] writing 'recovery'... FAILED (remote: (recovery_a) No such partition) finished. total time: 1.174s ---- Did I do something wrong? How can I root the device? To recover the device follow this instructions: https://c.mi.com/oc/miuidownload/detail?guide=2
--EDIT-- fastboot getvar current-slot current-slot: a finished. total time: 0.002s ---- fastboot --set-active=b Setting current slot to 'b'... OKAY [ 0.039s] finished. total time: 0.039s ---- fastboot flash boot twrp.img target reported max download size of 804261888 bytes sending 'boot_b' (39892 KB)... OKAY [ 1.181s] writing 'boot_b'... OKAY [ 0.207s] finished. total time: 1.388s Press and hold **volume up button** on device and enter the command **fastboot reboot**
Back in Fastboot ---- fastboot --set-active=a Setting current slot to 'a'... OKAY [ 0.039s] finished. total time: 0.039s Press and hold **volume up button** on device and enter the command **fastboot reboot** Do not press any key boots in Android-OS

Overnight, starting from a 100% charge, all apps closed, even from a fresh reboot, screen of course off, my phone (Redmi 6) ends up with a ~90% charge. I know this is abnormal, as my previous phone (Redmi 5A, with worn out battery) ends up with ~99% in the same situation. That's quite annoying to know that *something* needlessly drains my battery! I'm pretty sure it's due to some software bug. Encountering the issue as well on MIUI 10 and 11. I'd like to find out the culprit in order to fix the issue. What can I do?
For the record, my syslog receives the following two errors *a lot* (several per second): BoostFramework() : Exception_1 = java.lang.ClassNotFoundException: com.qualcomm.qti.Performance BoostFramework() Ux Perf : Exception = java.lang.ClassNotFoundException: com.qualcomm.qti.UxPerformance (then, just in case, I went to the Developer options and fully disabled logging, who knows! But it didn't fix the battery issue.)
Also for the record, I have already done a lot of googling about that battery drain issue, and tried the following fix: Go to "Settings > App > Permissions > Autostart" and disable everything (in my case I only had "Camera" enabled). Sadly, it didn't fix the issue.
**Update:** I've had run "Battery usage stats" during the day, and it reported me that the screen was most (like 90~95%, as I recall) using the battery, followed by a few % by the networks (cell, wifi). But here I just looked at "Battery usage stats" and it gave me interesting results: Screen 35%, Cell standby 31%, Wifi 24%… This is something I was also suspecting. It's highly possible the battery drain is caused by network (both cell and wifi) activity, which in turn could be caused by some software bug. Even though I made sure that no apps or widgets are running. What could I do to investigate further this path? Maybe there is some setting (possibly advanced) that could fix the issue?
**Update 2:** As suggested in the comments, I tried "airplane mode" (i.e. cell and wifi networks disabled) and it seems to solve the issue. I think that both, cell and wifi, cause battery drain. However, that adds an annoying handling step, and I cannot receive calls while in airplane mode. I wish I could avoid that extra handling. I usually don't use wifi, so I'll try disabling only wifi and see if it's sufficient. The MediaTek chipset of the Redmi 6 definitely seems to be a bad pick. This chipset forbids almost any custom ROM, and now I discover it's not energy-efficient at all for networks…
**Update 3:** Some feedback after an extensive period of testing. I can keep cell network and mobile data always on, turning the wifi off seems to be sufficient. Overnight, the battery goes down to barely 99%, it reaches 98% at the very worst… sometimes it even stays at 100% :) Coupled with a good mobile plan, I just keep the wifi always off, and no longer think about this issue :)

I just bought a new Xiaomi 14t phone, which came with HyperOs installed and which I want to use with both my personal and work accounts. Both of these are Gmail/Google accounts. I have therefore set up Xiaomi's second space and tried to use my work email as the second space's main account. This isn't working, the account seems to be added but I get a notification with: > Account action required > > my.email@my.company.com Tapping the notification does nothing, but when I go to Settings -> Google -> Manage account, I get: > Something went wrong. > > Some info may be out of date. Please try again later. At some point, I managed to get to a screen that told me: > To access your work account on this device, you'll need to set a lock screen. This is your organization's mobile device policy. Sorry, I can't seem to figure out how to get back to that screen now. In any case, OK, I need a lock screen, but I have one! I have set a lock screen password on both spaces (main and "second space") so why isn't this working? Is there something else I need to do to "set a lock screen"?

I recently bought an Intenso microSDXC UHS-I Premium card, formatted it as internal storage, and the content has been moved without any errors. But after that, the phone started having several issues: - Most photos, videos, music, and recorded audio files are missing. - Some apps—like CamScanner, Foxit PDF Reader, and the camera—don’t work. - WhatsApp media (voices, images, videos) can’t be downloaded or saved. - App updates can’t be installed. - Storage shows a negative value (see attached photo). I’ve tried common fixes online and contacted the manufacturers, but nothing has worked. I also couldn’t find an option to reformat or separate the internal storage from the SD card. What would be the best next step? Should I try reinserting the SD card and choosing "forget" option, enable “Force allow apps on external” in Developer Options, or is there a better solution to recover the files and resolve the storage issues? - Device Name: Redmi Note 9 Pro - MIUI version: MIUI Global 12.0.3 Stable 12.0.3.0(QJZMIXM) - Android version: 10 QKQ1.191215.002

I have two identical Poco Android phones. On both devices, I use the microphone button on the keyboard to enable voice typing in Hebrew — I speak, and the text appears on the screen. On one phone, it works perfectly. On the other, I get the following error message: "Permission to use: Voice typing is not granted." I’ve checked permissions but can’t figure out what’s causing the problem. Any ideas? I have Gboard keyboard.

I have Xiaomi Redmi Note 8T (ginkgo). I was installing a new ROM, wiped the device, and from TWRP, flashed the recommended recovery from the CrDroid device page - SHRP (SkyHawk Recovery Project). After flashing, it said it was going to reboot to recovery, but it didn't, and it seems to be stuck in a loop. - Holding Power and Volume down - Vibrates and just flashes. - Holding Power and Volume down - Orange Fastboot logo flashes on and off. - When the buttons are released, it goes blank, i.e., the phone stays turned off. - If connected by USB to a laptop, it keeps flashing every second. - adb fastboot does not recognize the device: - using adb devices = just says: List of devices attached - adb reboot bootloader = error: no devices / emulators found - fastboot reboot = Any way out of this?

My phone (Xiaomi Redmi Note 10, 2 years usage, the warranty just passed) suddenly shut down at 50% battery at normal usage when I clicked an app to open it and it will not boot up. I want to fix it myself due to privacy reasons, as I don't trust payed services and have experience in opening phones, but only to replace the screens. I tried to turn it on on safe mode - unsuccessfully. I tried to charge it but it didn't even pop the animation of charging. Nonetheless I left it for couple hours to charge and tried again - still not booting up. The USB connector is clean, dust-free and not loose. I tried different chargers. It is not detected by the computer when plugged in (checked in the Device Manager, Windows). I also called the phone from another phone to check if it's the screen's issue - I got "user out of service" message. I tried to troubleshoot the connector and it was a surprise to me: I own a MakerHawk UM34C USB 3.0 tester and tried it on my working phone - readings were reasonable, approx. 13W of charging power. I tried it on bunch of other devices, with correct readings. I also tested a device with physical on/off switch and the device showed voltage of 5V when turned off (charger voltage) and voltage + amperage when turned on (with propper readings). **So when I plugged it in the phone and if the connector were bad then I should have the same reading as in the device with off switch. But what I got was device (tester) restarting constantly without even showing me the data, as if the connection was ok but the phone "intentionally" disconnected it repeatedly.** This means that the phone recognises the charger and disconnects it immediately. What does it imply? Is it the software issue? I tried to open it like on the vid, using same tools but the glue seems to be too strong and it won't open so I can't check the battery itself without damaging the phone: https://www.youtube.com/watch?v=PhC37fp4o7Y **How should I troubleshoot the issue?** These threads provided no help: https://android.stackexchange.com/questions/171472/galaxy-s4-not-booting-up https://android.stackexchange.com/questions/247451/poco-m3-pro-5g-not-booting-up-after-unexpected-shutdown-it-does-not-charge-as-w

Has anyone experienced it before? The speech recognition (Google Now and speech input) is not working in Redmi Note 4G at all. I've tried cleaning cache, re-training, re-authentication, etc. but every time it says- "Didn't catch it. Please try again." Can anyone please tell me what's wrong? Thanks for your help! P.S: I'm having excellent WiFi connection with mic turned on. I've also checked all permission settings.

Before we start, just want to make it clear that I am aware how easy it is to brick this device, and have decided to go ahead rooting and installing a custom ROM anyway. My goal currently is to use twrp to install magisk and root the phone, but I cannot get the thing to boot into twrp. In case it matters, I'm running Miui 12.0.8.0 Global with Android 10 (4/01/21 patch) on a Global phone. My device is a 6GB/64GB variant with plenty of storage available. I've grabbed the required twrp image from the link in the XDA developers guide (https://forum.xda-developers.com/t/guide-begonia-unlock-bootloader-flash-twrp-and-root-proper.3995919/) as well as a vbmeta image for a Redmi Note 8 because I couldn't find one for the pro variant. I wouldn't expect that's an issue because they run the same OS, but because mine has a mediatek SOC I won't rule it out; if someone has the right vbmeta for me, it would be appreciated. My procedure is as follows: - Boot phone into fastboot, open minimal fastboot/adb from the guide. - Make sure twrp.img and vbmeta.img are in the fastboot directory - fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img - fastboot erase recovery - fastboot flash recovery twrp.img - Hold power and volume up to try to boot recovery. At this point, as long as I keep holding power+vol up the phone will make it to the "REDMI" splash screen, show me the unlocked bootloader icon, and power off. A few seconds later, it will try again to the same result. This will loop indefinitely until I stop holding volume up, at which point it happily boots into Miui; I've let it loop 5 times to be sure. If I hold just vol up (no power) once the phone turns on, like the guide says, it will pass the splash screen and simply shut off. I've tried multiple twrp and vbmeta images to the same result. The next thing to try was to boot directly to the image. I erased recovery, flashed vbmeta, and ran 'fastboot boot twrp.img." The phone hung on the fastboot screen for about 90 seconds before shutting off, and frustratingly then rebooting into *Miui* like nothing happened. If I try to boot to recovery after successfully booting Miui, it works, but I get the stock Xiaomi recovery, which will not help me root my phone. I'm running out of ideas on how to get this thing into the custom recovery. Still a little suspicious it's an AVB related issue, or some form of anti-rollback protection kicking in. Anyone here got any better ideas?

The phone is a Xiaomi Redmi 9 running Android 10 and MIUI 12.0.1. After a reboot, my phone refuses to mount my SD card. From what I have searched, this seems to be a common problem with MIUI, but no one seems to have tried to do anything except reformatting, which probably makes the phone just not scan. - I have checked, the SD card is alright. It never had any problems until the reboot and Android weirdness, and still does not have any problems on any other device. - I have tried putting another SD card from the same brand, and it passed the check, however, that card has way fewer files, which I think might be part of the reason. - I ran adb logcat vold, and I have noticed that every time it tries to mount the card, it runs fsck.exfat, After 50 seconds, the check times out. After a while, the check finishes with no errors, but since it times out, it does not mount. This seems like a pretty bad design choice. - adb shell sm list-volumes returns the card as unmountable. There is a slight chance some corruption occurred after the restart, as it was not present earlier. And yes, I am absolutely sure there are no problems with the card. Now the question is, is there any way to change the check timeout? Or just do anything else to fix this instead of having to move files or format the card? Maybe a way to force the mount? I have tried pretty much everything, nothing works except for the command to mount the card

I’m facing a really annoying problem with the Bluetooth on my POCO F4 GT and wanted to share everything I’ve tried so far to see if anyone can help or if they're going through something similar. I’ve always used the BSP D3 controller on my phone without any issues, working perfectly in Android mode (holding the X button while turning it on). I believe that, at the time of the first pairing, my phone was still on an earlier version of the system. Then, I bought a new controller, the JK 02 model, and that’s when the problems started. It shows up in the Bluetooth device list, but it won’t connect at all. I thought it could be some interference from other paired devices, so I removed all of them—including the BSP D3. And that’s when I noticed the worst: now even the BSP D3 won’t connect in Android mode, which is the mode I always used. The only way to connect the BSP D3 now is by using the Xbox 360 mode, but in this mode, I lose the ability to remap the buttons, which was exactly the reason I used Android mode. Since then, I’ve tried absolutely everything: - Resetting the phone’s network settings. - Restarting Bluetooth, toggling airplane mode on/off, restarting the phone multiple times. - Clearing Bluetooth and other related service caches. - I performed a full backup and restored the phone to factory settings, but the problem persists. - I tested other devices—my Bluetooth headphones, for example, connect normally, which shows that Bluetooth is not completely unusable, but there’s clearly some bug with controllers in Android mode. - I tested both controllers on another old phone of mine (a Xiaomi Mi A3) and they both worked perfectly in Android mode without any issues. I also tested the JK 02 controller on my wife’s phone, and it worked right away. So, everything points to the problem being with the current system version on the POCO F4 GT. My phone is currently on Android 14, system version 1.0.10.0.ULJMIXM. Apparently, this update bugged the Bluetooth compatibility with controllers in Android mode. And it’s really frustrating because the only alternative now would be to use the controller in Xbox mode, which breaks the entire button mapping configuration in apps like Shooting Plus V3.

I have a Xiaomi Redmi 7. After I installed Derp Fest ROM with Magisk and rebooted, it rebooted to EDL Mode, precisely Qualcomm HS-USB 900E mode. I was told this was not the right mode and tried all methods of switching to QDLoader 9008. After I eventually did (Windows had some driver issues), Xiaomi Flash software and QFIL software told me there was something wrong with the Sahara protocol. In both these programs, I got some kind of message about the Sahara: > SAHARA_NAK_MEMORY_DEBUG_NOT_SUPPORTED and in Xiaomi Flash, I got this:

w XiaoMiFlash.code.bl.SerialPortDevice.SaharaDownloadProgrammer(Int32 programmertype)
  w XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlashNew()

I successfully opened up the phone, and test points are available if that helps. Also, I tested on different computers with different cables. I also downloaded the ROM for Xiaomi Redmi 7 from 3 different websites, and it was the fastboot ROM in all of those cases. My main goal in this, is to either flash the downloaded ROM in Xiaomi Flash or somehow get back to fastboot mode. I hope I provided enough information so that someone can solve this problem.

I want to set an image I saved from [Imgur](https://imgur.com/gallery/lamborghini-gallardo-spatial-wrap-Qk8Chze) as my wallpaper. But the problem is, I'm not getting the image as I want. It stretches when I try to set it as a wallpaper. |Original|Wallpaper| |-|-| ||| I tried apps from the Play Store and did resizing image, but no progress. How do I set the wallpaper to just **fitting the screen** with **original resolution?**

I know, similar posts about this topic have been discussed but reading through them couldn't solve my problem: I have a 5-year-old Redmi note 8 pro (MIUI 12.5.7, Android 11). The internal storage is 64GB of which 42.4GB are occupied but I just cannot find out by what data. I plugged the phone into my Windows 10 pc with the option "show hidden files" activated in Windows Explorer but I still could not see any files that would take that much space. When I select all folders of my internal data in win explorer manually and sum up their size I only get 118MB. I have deleted 1-2GB with DiskUsage but still 40GB remain. The apps I have installed should not occupy more than 10-15GB. So there are still about 25-30gb of unknown files that are swallowing up my phone's storage. How can I find the files that take all the rest of the storage? Also, my internal disk space should be 64GB but windows says I only have 51.3GB which tells me that windows somewhat cannot see everything on my phone.

I bought a Mi MIX 2 and it is not connecting on mobile data. WiFi everything else works perfect. But in the APN settings menu it reads that "APN Settings are not available..." I am using Verizon BTW. MIUI 8.5.7.0 How would I fix this?

I have an Xiaomi Mi Note 10 Pro phone, and there are some issue with NFC. I can use it to pay at shops, or to interact with banking terminals. However, when I try to scan a card, nothing happens, and my phone don't see it, though, it had no problems with that before (maybe a year ago), and also another Xiaomi phone can read those cards with no effort. Yesterday I was repairing my screen, and also looked at NFC antenna and pins, that are used for connecting it to the motherboard, but nothing wrong there too. Maybe I'm missing some option in phone settings, that control that feature, and which I turned off with no purpose. *P.S. No software modifications are applied to my phone, bootloader is locked and have never been touched.*

How can I write (š) on Xiaomi keyboard?

I am trying to root my Xiaomi MI A2 phone with **Android 10**. I followed the steps to install **TWRP** which was successfully done. After that, I tried installing **Magisk** to get root access. After following the installation guide and performing patching images, I am now stuck in a fastboot/TWRP loop where I can switch between fastboot and recovery using the volume up and power button only. My PC cannot detect the device in either mode, although it had no issue detecting it before. I also alternated between A and B partitions. How do I get out of this loop so I can do a fresh installation of ROM?

I had a Huawei Mate 9 before, and there was an icon at the bottom-center of the screen, so that when I tap it, it shows all apps on the phone. (It is running the latest Android it can, which I think is Android 9 and EMUI 9.1) However, I just got a Xiaomi Redmi 9 , and there seems to be no such icon (it is running Android 10 and MIMU 11). I can only slide the desktop left and right. Is the standard Android interface actually to show all apps by default on the desktop (and is slide-able, like on an iPhone), and so there is no need to have that bottom-center icon, and we actually can see all apps on the phone just by sliding the desktop left and right?

In Xiaomi Mi 10i, the manufacturer had made the OS in such a way, from whichever app I add a Google account to, it just launches the same "account adding screen" (maybe from Play Services) and no option but to agree to Play Services to use this sign-in in all Google apps. In earlier models, we had the option to sync selective items like only Gmail and not Contacts of an account being added to a phone, but now if I add 2nd account, by default it syncs all data (Gmail, contacts, etc. while adding itself). And there is no option to remove the synced contacts of one account. Please help in this regard.