I would like to know is there any way to **backup Samsung A20s device through download mode/bootloader mode?** My device went into bootloop tried so many things only left to reinstall firmware but its lost user data so i need to backup before doing that any way? How it happens- - Charging over night besides my bed, - My hand touch the adapter and some cracks in the socket heard - The charger still working and charging other stuffs. - In the morning my device turned off randomly. - When I wakeup the device shows you >Device unable to bootup normally with suggesting three options >1. Try again - tried so many times still fails >2. Wipe app data (which is I think safe but needs a backup before doing that, thats what I'm looking for right now) >3. Poweroff - even after powered off its on again (automatically without my actions) and kept doing the bootloop Well why I mentioned the charging case is because that's the only thing i know before this happening (I'm in sleeping too not remember what happens after that),and I doubt if its any in case trouble in the mobile board so that's why I mentioned. Likely I don' think it was that but a doubt. And **I am able to enter recovery mode and bootloader mode (entering via recovery and show download mode (idk is that download or bootloader mode or these 2 things are same, I tried a backup using download mode in realme devices but not with Samsung)** And when I tried to enter recovery it shows a android image and with error text labeled under the image. It shows for a split second and boots into recovery mode. Also happens with powerup mid bootloop (when I saw this I thought some firmware bug. Because of this, that I thought the charging case is not the issue, not sure till now. Is there any way i can fix this? have any method to backup?

It happened when Google Play was automatically updating apps. I guess, something went wrong and the phone suddenly restarted and was not able to turn on again. It always gets stuck on "Starting apps" screen and then restarts again (bootloop). I figured out, that if I can delete the app causing bootloop it should be just fine. However, I don't know how I could do it.

My phone is nexus 4 running Android Marshmallow. Also, I have a custom recovery (cwm 6.0.4.7). So, I tried to connect through adb to the phone in recovery mode and delete the app, however, I can't use any adb command, because "device unauthorized". I assume, as soon as I can get access through adb, I can delete the app.

After surfing many forums for the past several hours I couldn't able to find any solution which preserves data the phone has. Any ideas how I can delete/fix the app without loosing any data? (nexus 4 doesn't have SD card slot). Thanks. P.S. wipe cache partition didn't help.

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?

My phone started rebooting all by itself all the time after I did 2 things with it. Installed Snapdragon BatteryGuru and put it on learning mode (for an estimated 3 days I guess) so that I could start saving battery by the app learning my behavior, and cleaned RAM with CleanMaster. These were the only changes I've done, I don't remember which was first but soon my phone started rebooting whether I was handling it or not at random intervals. I've also noticed the phone was hot all the time, the Note 3 runs into some hot period with some frequency but not with that frequency. I've uninstalled both apps and it didn't work, wiped cache and it didn't work. The phone was still rebooting even on safe mode. After I wiped Dalvik with the help of TWRP, I thought the problem went away but when I hit the power button to turn the screen off, the phone rebooted and it will now always reboot when the screen turns off, even if it's just from the phone being inactive. It doesn't boot-loops, it just reboots, then after a random time, can be seconds, can be half an hour, it will reboot again. Note 3 SM-N9003 VJUBMI6.

So I was going to root this (previsouly healthy) BQ A4.5. Unlocked the bootloader and flashed [TWRP from here](https://twrp.me/bq/bqaquarisa45.html) :

$ fastboot oem unlock
(bootloader) Start unlock flow

OKAY [ 32.954s]
Finished. Total time: 32.960s
$ fastboot flash recovery downloads/twrp-3.3.1-0-dendeone.img
target reported max download size of 134217728 bytes
Sending 'recovery' (11342 KB)...
OKAY [  0.378s]
Writing 'recovery'...
OKAY [  0.335s]
Finished. Total time: 0.727s
$ fastboot reboot bootloader
rebooting into bootloader
OKAY [  0.003s]
Finished. Total time: 0.058s
$ fastboot reboot
Rebooting...

Finished. Total time: 0.058s

The first reboot to bootloader didn't do anything. Now it's on a bootloop which states:

Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds

Pressing _Volume Up + PowerOn_ used to work for recovery (that's how I got into fastboot mode). Now, pressing _Volume Up/Down/Up+Down + PowerOn_ doesn't do anything, fastboot stands indefinitely `, and adb always responds with error: no devices/emulators found` regardless of when it's run. If I press _Volume Up+Down_ it turns off. Plugging in USB it turns on. Nothing else seems to respond. dmesg states:

[32774.364937] usb 2-7: new high-speed USB device number 59 using xhci_hcd
[32774.514434] cdc_acm 2-7:1.0: Zero length descriptor references
[32774.514450] cdc_acm: probe of 2-7:1.0 failed with error -22
[32774.554519] cdc_acm 2-7:1.1: ttyACM0: USB ACM device
[32777.142205] usb 2-7: USB disconnect, device number 59

The disconnect happens before the bq logo appears. Trash bin time?

I uninstalled the DocumentsUI only to know it wasn't "just" a file manager. My /system/priv-app/DocumentsUI is empty. Putting any 3rd-party DocumentsUI.apk in it results in a bootloop. I have a custom ROM (AOSP Extended). Flashing the /system again would fix the problem, I think. Just want to make sure if this will make the condition worse, or am I going alright?

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?

A friend gave me an Alcatel phone to fix it, the phone updated automatically and when it starts up, this happens: > dm-verity corruption > > Your device is corrupt. > It can't be trusted and may not work properly. > Press power button to continue. > Or, device will power of in 5s 5 seconds after the message is displayed, it restarts and displays the same message. I tried putting it into fastboot to do what they tell me to do with this error, but the phone reboots by disconnecting from the PC. Even to put it in fastboot, I have to use the volume up arrow and the power button, I choose the fastboot option, and when I choose fastboot, the phone does not show a terminal like they do in the tutorial, it seems as if it was turned off. I connect it to the PC and the same thing happens, it restarts every 5 seconds and adb does not recognize it. I do not know what to do.

I have a boot-looped Samsung Galaxy S II GT-i9100, running the Android 2.3 Gingerbread it came with, unrooted and unmodified (although Optus-branded). The phone's battery depleted while the phone was running; now, any attempt to boot the phone results in the boot sequence looping indefinitely. I wish to recover data from this device (before attempting to solve the boot-loop problem later via factory reset or other method). I read the [boot-loop tag information](https://android.stackexchange.com/tags/boot-loop/info) but the instructions have not been helpful for me: I have tried to boot into Safe Mode, but my attempts also trigger the indefinite boot-loop; I wiped the cache via stock recovery but that had no effect; and, the last recommendation was a factory reset which I won't follow until I have recovered the data. I believe USB Debugging is already enabled. I have an 8GB external SD card and I have Linux Mint 13 as my desktop operating system. [This answer](https://android.stackexchange.com/a/59044/81471) indicated that it should be possible to root the phone and recover data via the [Android Debug Bridge (ADB)](http://en.wikipedia.org/wiki/Android_software_development#ADB) for a different Samsung Galaxy S version, but I need instructions for the Samsung Galaxy S II GT-i9100 if this avenue is worth pursuing. This seems related to [this question](https://android.stackexchange.com/questions/71776/samsung-galaxy-2-stuck-at-start-up-can-i-recovery-the-phone-or-at-least-the-dat) but could be a different [variant](http://en.wikipedia.org/wiki/Samsung_Galaxy_S_II#Variants) and issue. It's not the same as [this question](https://android.stackexchange.com/questions/39316/how-to-regain-control-over-a-samsung-galaxy-s-ii-with-a-boot-loop) because I need to recover data.

My son has a Motorola Moto G73 5G (XT2237-2), always used it normally without trying to root it. So the bootloader has not been unlocked. It is stuck in a boot loop. I can boot into fastboot mode (by pressing power and volume down) and then into recovery, but I am not allowed to change anything. While the phone was still working properly we should of course have enabled Developer Options, Allow USB Debugging and Allow OEM Unlocking, but it is too late for those. Is there another way to get to the data before doing a reset? - If side-loading the firmware in recovery mode is possible, I guess that would wipe the data, but mounting in recovery mode (to save any content) does not seem to work. - I tried accessing the phone with fastboot and adb (from the linux prompt) and the phone recorded receiving the commands fastboot oem unlock and fastboot flashing unlock, but then that was not allowed because we had not allowed unlocking from the Developer Options menu.

For a few days, I've been struggling with a Tytera model TYT IP-98 PoC (Push to Talk over Cellular) radio that has the boot loop problem typical of the Android system. Basically the PoC turns on, but in a few seconds, it restarts randomly always with the initial logo. I searched online to see if there could be a solution perhaps, by doing a factory reset with a key combination, but in vain.

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?

My Tecno F1 Pro is stuck on the boot animation. I'm trying to hard reset my Tecno F1 Pro, but in Android Recovery, I'm getting this error. Supported API: 3 E:failed to mount /cache: Invalid argument E:Failed to mount /cache/recovery/last_locale E:failed to mount /cache: Invalid argument How to fix it?

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?

Here's my situation: I have a Sprint Samsung Nexus S 4g. It is rooted, unlocked, and loaded with CyanogenMod 10.1. I am attaching it to a Windows 8 machine via USB cable. Recently, the phone went into a boot loop, and thus I can only do anything with it in recovery mode. I'm trying to transfer the stock ROM to the phone for loading. I follow these steps 1. I boot into Recovery mode 2. I go to Mounts and Storage 3. I mount the USB card 4. In Windows, I open up the phone in explorer, and copy the update.zip file to the root of what is now the G: Drive on my phone. 5. I try to load the ZIP file for processing. Recovery says "Can't open file /sdcard/update.zip" 6. I reboot into recovery again to 'refresh' things. At this point, the file that I loaded is gone! It's not on the SD Card anymore. I can't find it via Recovery mode, and if I remount the USB disk, it's not visible in Windows either. Weird, huh? One other thing to note: I've wiped and reformatted everything I can via Recovery (Cache, system, data, Dalvik, everything) and yet when the phone occasionally manages to boot all the way to the OS, I can still see my wall paper. How can I get the files I copy over to actually stay on the phone? Any ideas on what is going on? I just want to wipe this phone and start over, but I can't seem to make that happen. Thanks. More: Okay, I formatted and wiped everything that I could. And now the phone only boots to fastboot mode. I mount the USB card, move a ZIP over, and double check it in Windows. I can open the file on the phone. But when I unmount the USB card (I have no choice), the ZIP is there, but the phone won't read it. It says "Can't open (bad)". This is trying with CM9.1 and I'm 100% sure it is the right version for my phone (crespo4G)

I put in the battery on my HTC Desire Z, set it on to charge, press the power button, and boom, a loud little boot-up song with the logo on the screen "htc quietly brilliant" not so very quiet. 5 seconds later, it goes dark, and BOOM, right in my face with that same noise and logo. It has been in a loop like that since. Yes, I'm aware that the HTC Desire Z was released years ago, but I'm still willing to try. I have tried force shutdown and everything that I could find, but first of all, it won't even turn off and it's giving me a migraine headache from that loud noise. I'm out of options, and I'm not risking an electric shock from taking out the battery.

A Redmi Note 8 got hit and only now we noticed that it's broken. It just reboots into "Redmi-Recovery 3.0" every time I press Reboot > Reboot to System. If possible, we would like to save data on the phone, since there might be our old photos. On some other related post, I saw that "Recovery buttons are Vol. Up + Power, and Vol. Up was stuck". But I think it is not broken on ours, since I can press it to go up. Is it possible to fix it without deleting or saving photos to my PC before wiping?

Let me start off by saying that I have a Verizon Galaxy Nexus. I flashed cyanogenmod 10.1 last night and was having some issues so I decided to go back to 9. Unfortunately clockworkmod wasn't able to use my recovery data due to the new profile feature in Android 4.2.2. So instead, I flashed CyanogenMod 9 once again. Not when I boot it, it just stays on the blue loading screen. I can't even get to recovery mode because when I boot in Odin I get the message "Downloading... do not turn off target" Is there anything I can do to fix this?

I have a Xiaomi Redmi Note 9 (128GB/4GB RAM). I have unlocked my bootloader. Then I tried to install TWRP. I got into the fastboot mode, then executed:

fastboot devices
fastboot flash recovery [file].img
fastboot flash vbmeta [file2].img
fastboot flash misc [file3].bin
reboot

or something like it. And when I push the volume(-) and power buttons while rebooting, it just reboots into the Xiaomi logo, again. I can not even turn it off. Now, it is stuck on a bootloop showing the Xiaomi logo. I am unable to boot into the bootloader. When I connected it to the PC and tried to boot into the bootloader -with no success-, the PC made the sound of something being connected but it quickly made the sound of something being disconnected. What should I do? Note: I am a complete newbie in this. I went to different repair shops and they told me it needs software or worse a new ROM.

Firstly, I have found a similar question here (), but no answer there seemed to solve the behavior. I am experiencing the same sort of problem that seems to be affecting multiple Motorola One Hyper in my country and abroad. The phone boots, stays on for about 10 seconds, then automatically restarts, prompting a factory reset, which I do not want do do, given that there are many personal files still inside the phone. During this brief period of time, I can see my files there, which is why I'm asking this question. I don't really care about the phone anymore, it had its day already and I am willing to break it down entirely if needed, the only thing I want to do is to have one clean boot or method to access my files and transfer them to another storage. Any tips on what I could try, or where I could start to make things work? Thank you very much in advance.