I had Revolut on my Redmi Note 8 Pro phone for a while. First when rooted, I used Magisk Hide to get around its security. 2-3 years ago my system started bootlopping and I just went with clean vendor ROM (MIUI) instead. Revolut worked fine on the device until this week. I noticed that it first showed some error that the device can't run the app because of potential security risks, such as rooting, unlocked bootloader, etc. After that it switched to brilliant UX of just showing infinite black screen over and over again. - My phone is **not rooted**. - It still has **unlocked bootloader**. - The ROM is **MIUI Global 12.5.15**. So the only potential culprit is unlocked bootloader, but it has been for years now. I don't want to lock it, nor do anything that causes any sort of data loss. E.g. I know I could go back to root + Magisk Hide, but I don't have time for it now. Revolut support was beyond useless and the only useful thing they told me to do was using some SafetyNet check app, which failed the test, with no details as to why. Other than that, they recommended basic troubleshooting I've already tried, like reinstalling, cache clearing, data clearing, restarting the device, etc. And to lose my data with factory reset, Magisk Hide or anything similar. Other banking apps I have, like mBank and Curve, still work problemlessly BTW. Why did Revolut suddenly decide to cut me off from my money? Is it related to some SafetyNet update? I doubt as it said it's deprecated in the SafetyNet test app? Is there any way to get around it **without losing data of other apps**?

My Redmi 8 phone is in bootloop. It got stuck with its Remi logo and does not start. I am trying to unlock the bootloader but I didn't find a way other than mi unlock which I don't know how to use it without knowing my mi account credentials.

My Alcatel Android decided not to boot. It starts and says "Alcatel" then just flashes "enjoy now" about 60 times until Android Recovery. TCL/5003D_EEA/Curie 8.1.0/0PM2.171019.012/5003D_ALGB_V2.3 If I click "try again" I get Android Error and it then starts the reboot process again. I can access Android Recovery by removing and reinserting the battery, holding down Power Button, both Volume Up and Volume Down all together, once it says "Alcatel" releasing all of them, it then enters Android Recovery. I have tried "reboot now, I have tried Wipe Cache partition". What is my next move please? Are the recovery logs useful for anyone to help me?

I was trying to unlock the bootloader of an old Redmi Note 4x, Downloaded fastboot and adb. I first enabled developer option and turned on USB debugging. I tried finding OEM unlock option which was not present on the phone. After few hours of searching about it online, I finally concluded it is not available for the phone. So I went on and fired up my terminal \[in administrator mode\];

$ adb devices
> List of devices attached
> 8H4DZP69S44DQOEM        device

then I rebooted my device in bootloader (fastboot)

$ adb reboot bootloader

My Phone restarted in bootloader, then I went back to my terminal and checked if the fastboot was working or not;

$ fastboot devices
> 8H4DZP69S44DQOEM        fastboot

After confirming that the fastboot is running, I tried unlocking OEM;

$ fastboot oem unlock
> (bootloader) Start unlock flow

> FAILED (remote: '
> Unlock failed - Err:0xffffffff
> ')
> fastboot: error: Command failed

which.. well... failed and I don't know why. I tried searching this very error code online but failed to find anything close to it. My other attempts like unlocking flashing failed in similar fashion;

$ fastboot flashing unlock
> (bootloader) Start unlock flow

> FAILED (remote: '
> Unlock failed - Err:0xffffffff
> ')
> fastboot: error: Command failed

$ fastboot flashing unlock_critical
> (bootloader) Start unlock flow

> FAILED (remote: '
> Unlock failed - Err:0xffffffff
> ')
> fastboot: error: Command failed

Nothing seems to be working, Please help!

I want to unlock the bootloader of my Moto X4 running Android 9 and get the unlock code. My computer is a Linux Mint Ideapad 3 (so should have USB-3 ports (referring to this post )). My device gets displayed when I type fastboot devices However, none of the 3 USB ports give me a response when I type fastboot oem get_unlock_data nor does the command finish. The bootloader logs say on the phone cmd: oem get_unlock_data. "**Allow bootloader get unlocked**" is enabled in developer options, and so is USB debugging. I need the unlock data to request on the Motorola page the unlock key.

My stock HP Slate no longer boots. It stops at the HP logo / Powered by Android splash screen. I've tried all of the solutions typically available to this device like resetting with the power turned off button combination. I've tried all the options (start, Recovery Mode and Restart BootLoader) but they all freeze on the same splash screen. I now have a really nice brick. Any suggestions / recommendations on what I can do to restore or recover this device?

I can't seem to find this information anywhere. I'm not quite sure if "Bootloader unlock" is ignoring secure boot or if it's ignoring Android Verified Boot. For the sake of convenience, let us discuss using Qualcomm SoCs. In Qualcomm design, PBL, XBL, and some others would need to be verified by a certificate chain, where the root cert is verified by a fused hash value. Source: https://www.qualcomm.com/content/dam/qcomm-martech/dm-assets/documents/secure-boot-and-image-authentication-version_final.pdf Because the image is about secure boot in general and not necessarily in the perspective of Android, if we want to discuss with Android, the "OS Bootloader" would be the Android bootloader (ABL). From the Android bootloader, the Android verifies the boot partitions with dm-verity. Which of these does the bootloader unlock ignore? 1. Verification of XBL, QTEE, ABL, etc that are verified with the fused root hash 2. Verification of boot images that the are verified by the Android bootloader I would assume the use of fastboot only affects the ABL and thus the answer would be #2, but I can't find an answer to confirm this. Are there any documents or books that explain this in detail?

I was using my Nokia 5.4 phone, but suddenly it restarted itself and cannot get past the "Nokia" screen (normally it would fade out and get into the Android system). I have tried restarting my phone many times and the problem persist. I am able to get into the Fastboot Mode and Recovery Mode, but there is no option to factory reset at all. In the recovery mode, there are only 3 options: 1. Reboot system now 2. Enter fastboot 3. Power off And there is no option to factory reset in fastboot as well. In fastboot, there are 4 options: 1. Reboot system now 2. Enter recovery 3. Reboot to bootloader 4. Power off And in bootloader, still no factory reset. There are 4 options: 1. Start 2. Restart bootloader 3. Recovery mode 4. Power off I have already bought a new phone, but I would like to see if there is anyway to save this phone. All my important data is already in the cloud, so data loss is not a problem, and I may try some riskier method. Is there anyway I can make this phone work again?

I'm trying to solve a problem that is affecting a **Moto G 2014 XT1069** device. What has happened is that the device did shutdown, then when trying to power it up again, it stayed stuck on the Motorola logo for some time. Another person trying to help, said that it was needed to format the cellphone and rebooted into recovery mode. The point is that when trying to factory reset an error appeared. This person then said that the device was bricked and needed to do something to correct it. Then using fastboot through a computer, I don't know what she did but the situation got somehow worse. The first thing is that she unlocked the bootloader. But after all the procedure what happens is that when the device powered up, it just got stuck in a screen with a message **WARNING BOOTLOADER UNLOCKED** and it *doesn't progress any further*. On that same screen it is possible, by pressing **PWR** + **VOL DWN** to access the bootloader, but even if we select "Normal Powerup" or "Recovery", the device just gets back to the screen **WARNING BOOTLOADER UNLOCKED** and nothing more happens. Furthermore, it seems that the battery became somehow "mad". After a *quite long* time interval charging, the device got to 29% of battery and after just a few minutes trying to correct all this mess, the battery got to 6%. I don't know what they did and how all of this happened. How can I fix this mess? How can I make the cellphone boot and make everything right again? If possible I want to avoid flashing the factory image for the reason that I don't have access to the image from the official source and I feel quite uneasy to get from one untrusted source, since it might compromise confidential data. What can I do to solve this? I believe there has to be a way to correct all of this.

Is it possible to root a Huawei Mate 20 Lite without losing any data? Any help would be greatly appreciated!

I tried to flash the most recent android pie update to my pixel 2 only for it to fail writing partitions even though I followed a recent guide to my best ability. Now, the phone is stuck in the bootloader with no way to boot into android or any way to access the recovery options (throws an error and takes me back to the bootloader info page) Neither fastboot nor ADB can recognize the phone, I think this is because the USB debugging must have turned off somehow even though I turned it on, as before I WAS able to access it through fastboot. But now I can not, plugging it into the Windows machine, windows doesn't see any change in Device Manager when the phone is plugged in and out. I reached out to a google supports rep and they told me since there is no way to access the recovery options, the phone needs to go through warranty, but is this really the only way? Is there some driver I am missing?

I somehow bricked my OnePlus One phone badly. It only loads directly to the recovery. Pressing vol up + power button or rebooting it with adb reboot bootloader doesn't get me to the bootloader. I think I erased the bootloader partition or deleted my bootloader. Here comes the tricky part. I can't even sideload any file or access my internal SD card because then I get either following error messages: - E: footer is wrong - E: signature verification failed - Error opening '/data/media' (no such file or directory) Right now I can either flash the OnePlusRestoreTool(64GB) recovery or the ColorOS recovery tool (both can't access the internal storage - button is not clickable). I thought I just have to mount my SD card new, but I can't enter a shell command, and most badly, I can't enter the bootloader. How to fix it?

Phone: Huawei honor 3c I downloaded Emotion UI 3.0 for "probably" the wrong set form here offical site .But it was installed properly. Then there was an update of same emotion UI, which on installation put the phone in bootloop on restart. This is what phone does - On pressing power button, it vibrates without going into recovery mode or showing logo - just a black screen - The phone vibrates after every 15-20 seconds, which is probably an indication that it is restarting again and agian - Pressing Power button/volume up/down keeps does not make any difference - Partition is not shown in my computer (when connected to laptop) - Using ADB: Command adb devices or adb wait-for-device do not list any device - Windows device manager shows "MediaTek PreLoader USB VCOM(Android)(COM5)" under Ports (COM & LPT) which indicates that phone is detected but before anything happens it reboots I've gone through several threads on this topic and nothing helped. Please help.

I'm having a problem when trying to boot into a twrp. When I try to use the fastboot boot twrp.img it returns with the error >(bootloader) command is not implemented!\ \ Sending 'boot.img' (33144 KB) OKAY [ 1.047s]\ Booting (bootloader) command is not implemented!\ OKAY [ 0.007s]\ Finished. Total time: 1.093s I'm using Ubuntu MATE 24.10, and it is my first root and I'm trying to do it on a Moto g8 Play. (sorry if my english is bad)

I am trying to unlock the bootloader on my **Realme RMX3710 (Android 14)**. I am facing issues switching the phone **from Fastbootd to the standard Fastboot (Bootloader)** mode. - Operating system: Linux (Ubuntu 24.04) - ADB/Fastboot versions: Android Debug Bridge version 1.0.41 Version 35.0.2-12147458, fastboot version 35.0.2-12147458 - OEM Unlocking is enabled in Developer Options on the phone. USB Debugging is enabled and functioning correctly. Below are the steps I’ve taken and the results I encountered. Thank you in advance for any help! 1. Checking the device in ADB - Command: adb devices - Result: List of devices attached KRG6AELZT4SSAMBE device 2. Attempting to enter Bootloader mode via ADB - Command: adb reboot bootloader - Result: The phone restarts and boots back to normal mode. 3. Attempting to enter Fastbootd via ADB - Command: adb reboot fastboot - Result: The phone switches to Fastbootd. - Command: fastboot devices - Result: KRG6AELZT4SSAMBE fastbootd 4. Trying to switch from Fastbootd to Bootloader using Fastboot - Command:fastboot reboot bootloader - Result: The phone restarts and boots back to normal mode. 5. Attempting manual entry into Bootloader mode - Steps:I turn off the phone.I hold the power button and volume down button simultaneously. - Result:The phone enters Recovery mode instead of Bootloader. The Recovery menu lacks an option like Enter Fastboot Mode. 6. Attempting to unlock the bootloader in Fastbootd - Command:fastboot flashing unlock Result:FAILED (remote: 'Unrecognized command flashing unlock') fastboot: error: Command failed - Command:fastboot oem unlock Result:FAILED (remote: 'Unable to open fastboot HAL') fastboot: error: Command failed

I have a Redmi Note 3 (INDIAN VARIANT Kenzo/Snapdragon variant running on Marshmellow 6.0.1 with MIUI Global 10.2) on which I performed an bootloader unlocking procedure via the tool XiaoMiTool V2 from [xda](https://forum.xda-developers.com/android/software-hacking/tool-miunlocktool-unlock-bootloader-t3782444) since the official method kept denying me for some reason I also want to let you know that during the procedure i left the *oem unlocking option disabled* and ran the tool So after the device's bootloader was unlocked (ss attached) I noticed that the OEM unlocking option was still active (meaning I can flip the button and it will just ask for the pass and warn me and enable the option: again ss attached) **So my question is is my device properly unlocked? OR Did I mess up with procedure ?** I know i could dial

*#*#7378423#*#*

*(which doesn't work in miui devices)* or using *fastboot method* [mentioned here](https://android.stackexchange.com/questions/73567/how-to-check-if-your-bootloader-is-unlocked)- *but the problem is that my device's usb port is damaged in a way that charging works but MTP or any other option doesn't (Yeah I tried multiple usb cables, brought a brand new from official store and multiple devices)* or is there any app to do that ? **EDIT :** Okay now I tried by adjusting the chord into the port and running

getvar unlocked

(ss attached) Now what does this mean ? Is it still locked ? I would really thankful if someone can help

I'm trying to unlock the bootloader of a MediaTek-based phone using mtkclient. Does it work with a virtual machine (Linux guest on Windows host)? Connecting to the host using USB cable, and enabling USB passthrough by selecting the device, didn't work for me. It seems that the device is recognized but a "handshake failed" error appears.

So, to summarise the questions: 1. How do I get the bootloader to work if I want to install Linux ARM distro on Android phones (in this case, OnePlus 5T) 2. Is it possible to copy drivers in /vendor in any possible way to my Linux install and get it to work? Details: I've installed Ubuntu Touch on my OnePlus 5T phone. After some experience with it, I found that it's not fun so I want to switch to other distros that allow me to install whatever GUI I want, 99% open-source (no Snap), be able to get into tty, and compile a custom kernel. Basically, most functionalities that could be found on x86 Linux distros. (It would be best if it's Gentoo) However, there are 2 big problems that I couldn't get over with: bootloaders and modules. From installing Gentoo Linux by hand, I'm pretty familiar with installing bootloaders with Grub on EFI. But there's no such thing as BIOS or EFI on phones (just fastboot), and as for the drivers, on Ubuntu Touch (which is supposed to be more "Linux" than "Android") don't have kernel modules .ko file but says all the drivers are in /vendor. Since I cannot boot from USB in phones but am able to install alternative OS from flashing .img files, I have come up with a way to install Linux on phones (ignoring driver and bootloader issues): 1. Plug a USB drive on the phone and mount it to a directory 2. In the directory, download and extract Gentoo/Arch/etc. stage tarball 3. chroot into the Linux environment and try all I can to install Linux on it 4. Unplug the USB drive, mount it on my Linux PC, and dd into a .img file 5. Flash the .img file in whatever way Is it possible, if so, how/why not? I know that Android is based on the Linux kernel, but it's still much different from Linux distros that I've seen. I have much less Android knowledge than Linux, so feel free to correct my misunderstandings.

I am trying to unlock the bootloader of my Tecno Spark 10c to install custom ROM on it.

C:\Users\Monami and Agnibha\OneDrive\Documents\tecno_root\platform-tools>fastboot flashing unlock
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed

C:\Users\Monami and Agnibha\OneDrive\Documents\tecno_root\platform-tools>fastboot oem unlock
FAILED (remote: 'Unlock bootloader fail.')
fastboot: error: Command failed

C:\Users\Monami and Agnibha\OneDrive\Documents\tecno_root\platform-tools>fastboot oem unlock-go
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed

C:\Users\Monami and Agnibha\OneDrive\Documents\tecno_root\platform-tools>fastboot flashing unlock_critical
FAILED (remote: 'Not implement.')
fastboot: error: Command failed

C:\Users\Monami and Agnibha\OneDrive\Documents\tecno_root\platform-tools>

I have tried everything, and every command, stack forum, and other website doesn't help. Please help if any experts are there.

I'm using Debian GNU/Linux trixie (well, the Devuan equivalent to be exact), and am working on a Samsung SM-P900 Galaxy Note 12.2 Pro tablet. As part of possibly flashing it, I need to make sure the bootloader is unlocked. I have adb and fastboot installed. What I see is:

# adb devices
List of devices attached
5200b47af69a4247	device

# fastboot devices

so, visible with adb, not with fastboot. I found this question: https://android.stackexchange.com/questions/221634/fastboot-connection-problem which said I can't see the device at the same time with both adb and fastboot, and that I should reboot it like so:

adb reboot bootloader

but when I do that - it reboots as usual, and I still see it only with adb. I also tried the following: 1. Booted into recovery mode (using Power + Center-bottom button + Volume Up) 2. Chose "reboot to bootloader" ... that also resulted in a regular boot (showing my homescreen and apps), and device was still invisible with fastboot. What can I do to get my tablet to be fastboot-visible (so I can flash it)?