I was stuck in a boot loop after flashing AOSP ROM. So I decided to power off and use SPFlashTool to flash the stock ROM. But both SP and Tecno flash tools give the following error: > ERROR : STATUS_BROM_CMD_STARTCMD_FAIL (-1073348607) , MSP ERROR CODE : 0x00. The phone doesn't respond to any button presses. However, whenever I connected it to my PC, the charging indicator glows and even Windows can detect it, and the device is listed in ports. Can anyone please help?

I have a Asus Zenfone 2 and a few days ago it ran out of battery and turned off. Then after I charged it up and restarted it, it wouldn't turn on. It gets to the logo and the loading circle and just gets stuck there forever. I can get into recovery, but can't do anything in recovery, because everything gives this error: > E:failed to mount /cache (invalid argument) Trying to wipe cache, factory reset the phone, mount /system, flash a ROM from SD card, ADB sideload, everything gives the error multiple times. Factory reset formats /data fine, but when it gets to /cache, gives the error and aborts. Same thing with fastboot. I tried to flash TWRP (I have stock recovery) and I tried to erase and format cache through fastboot, but both give this error: > FAILED (remote: 'Can not mount the necessary partition') > >fastboot: error: Command failed Is there anything I can do to format the phone or somehow rebuild the partitions without being able to flash anything via recovery or fastboot? I don't know if tools like AFT or xfstk can do anything for me. Edit: I don't think the EMMC chip is dead, because the recovery partition is still fine, I can still boot into recovery and when I did a factory reset, it formatted /data without any errors, only had an error when it started formatting /cache. When I was looking for a solution to this problem, I read somewhere that sometimes when the device gets interrupted, like when it shuts down suddenly, to prevent data loss android would change permissions on the /cache partition to read only or something like that. This would certainly explain what happened to my phone. Just need to think of a way to access ADB shell on it to try to change permissions. Shell doesn't work in ADB sideload mode, that's the only ADB thing the stock recovery has. Is that a similar thing in fastboot by any chance?

I have a Galaxy Mini GT-5570 phone. Last night I installed "ROM Manager" and tried to partition my SD card. It requires rebooting my phone, and I confirmed that, so it shut down my phone. Then it can't boot anymore -- all I get is just a black screen! Unfortunately, I read that ROM Manager can cause a hard brick for Galaxy Mini lately... I tried all possible solutions found on the Internet, but nothing works. So I decided to try the USB JIG method as it can force my phone to boot to download mode. The point is that I can't find a 300k resistor, then can I try 330k or is it dangerous? Is there another method to revive my phone back ??

I have an issue with my LG K10 (K430, MT6753). I was experimenting with it to learn the adb function. I accidentally erased the whole boot partition using rm, and then my phone is not booting anymore. It is showing the LG boot logo, but not starting up, keeps rebooting. I tried to: 1. Repair it through LG Bridge, to flash the stock ROM through LG UP and LG Flash Tool. But the phone is not staying in Flash mode or Download mode, and can't boot into Fastboot. The only thing that apparently works is the Factory Reset mode, but it only shows the interface. It only reboots the phone and nothing else. 2. Flash the boot image through SP Flash Tool, but have no luck. The phone is detected by Windows, but only for 3 seconds, then it disconnects. No matter what I do, when I connect the phone to my PC, it quickly disconnects, even with Driver Enforcement deactivated. I tried LG drivers and some other drivers for Mediatek, but still have no luck. Is there any other way to recover the boot partition's data or to unbrick my phone?

For the purpose of flashing custom ROM I flashed Lenovo Tab M10 FHD Plus (X606F) with Android 9 ROM. I used SP Flash Tool. Now the tablet won't power on. Pressing buttons does nothing. Can't invoke fastboot nor recovery mode. Red LED indicating charging is the only thing the tablet is giving me now. I've tried to restore the device using official Lenovo's Rescue Tool. Process of restoring gets stuck on 40% and won't go on. Hard reset (pressing and holding volume buttons + power button for few secs) isn't doing anything. What else I can try ? I've followed the steps outlined and I got to the point where Windows doesn't recognize the tablet:

I am trying to fix my Huawei P30 (Android 10) which gets stuck in recovery mode. I tried to fix it by using eRecovery but I get the error "Get Package info failed". Around the internet, I was told to flash a new ROM to solve this problem, but there is no tutorial for flashing stock ROMs for Huawei P30 on the internet. My Huawei P30 does not have an SD Card slot meaning I can't use the method of adding update.app to /dload folder on an SD card. I also cannot use ADB fastboot because the Huawei on Android 10 does not have the image files required (boot.img, recovery.img, etc.) Instead, it has a myriad of images like Super.img, Ramdisk.img, erocovery.img, etc. I don't know which ones to select because I am unable to find a tutorial on the internet that tells me which files to select. I also cannot use the SP Flash Tool because Android 10 stock ROMs do not have scatter file XML or txt (it has update.app) I am unable to use SigmaKey as well because of the "SmartCard resource manager not running" error (I'm on Windows 10) I have exhausted many options with no luck, please help me.

I've tried to root my HTC Desire 516 dual sim by following this guide: http://forum.xda-developers.com/android/help/bootloader-fastboot-recovery-htc-desire-t2845467/page8 But obviously, I did something wrong. Now, when I turn on my phone and unlock the screen, suddenly there is a message saying "Unfortunately, HTC Sense has stopped", and I didn't make a backup and now don't know what to do. Can someone help me to fix it? I cannot do anything on the homescreen or even to get in the app menu, only in settings menu. Also, when I try to wipe cache or go for the factory reset it returns a string saying "E: failed to mount/sdcard (no such file or directory)" I tried to find a stock ROM for this phone but seems that there's none on the internet.

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 have a problem with my Samsung Galaxy Tab S SM-T700 (WiFi) that I couldn't solve even after a lot of googling. - Main Problem: It won't boot after I did some software updates (stuck on the Samsung logo) - Complications: Retail mode (MDM does not allow factory reset) The data on the device is not important, it would be no problem to lose it if I could somehow do a factory reset. I tried re-flashing with the stock ROM, but it still won't boot and still is in retail mode (actually, it "half-booted" once immediately after the flash, the OS started just to tell me it's not working and "has been quit"). Any ideas? Is it actually possible that there is no way to revive it?

I was experimenting (more specifically, trying to flash ROMs) with my Samsung Galaxy J1 Ace (rooted). It was all going well until I tried flashing the TWRP recovery mode. I followed all the steps mentioned on various XDA forums, but a red exclamation mark appears at the top left of the screen when I try to turn it on along with the Samsung logo, and the phone just hangs. When I go to the Download mode, it shows "MDM Download Block: 0". I tried flashing, using ODIN, other versions of the TWRP for my phone model, but the same error persists. Is my phone soft-bricked? How do I fix it? I am trying to restore the original stock Samsung firmware now.

I have a ZTE nubia Red Magic 7 on Android 13. I accidentally had to erase all checked in QFIL when trying to bring it back from soft bricked. That's irrelevant now though as erase all did just that. - 0 partitions. - 0 GPT headers. I have backups from before in QFIL. However, this is not working either as they are all snippets for QFIL to use. I have a full partition list from before d and a few readings from the partition manager as well, user and system I believe, maybe different, can't read it to tell. no help on XDA or the manufacturer or Qualcomm or online communities. How can I bring this phone back from death?

I've got tablet Asus MeMo Pad 7 (ME173X). I don't know what happened with him (is it broken physically or by software). Tablet don't respond on buttons, or charger. I connected it to computer dmesg shows (device also disconnect after one second and connect again): usb 2-1.3: new full-speed USB device number 3 using ehci-pci usb 2-1.3: New USB device found, idVendor=0e8d, idProduct=0003 usb 2-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 cdc_acm 2-1.3:1.0: ttyACM0: USB ACM device Sometimes but very rarely dmesg shows also (including above): usbcore: registered new interface driver cdc_acm cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters usbcore: registered new interface driver usbserial usbcore: registered new interface driver usbserial_generic usbserial: USB Serial support registered for generic usbcore: registered new interface driver option usbserial: USB Serial support registered for GSM modem (1-port) I found stoc firmware, to flash preloader but every time I got error Storage type mismatch! scatter storage type is hw_storage_emmc target storage type is hw_storage_none I was looking some more info. I read some info about meta mode. I tried connect device holding vol up or vol down (both) but device is always recognize as above and flashing also return the same error. Is there any chance to unbrick this tablet?

I need to know how to un-**softbrick** the Samsung Galaxy Core Prime. I don't know how it got bricked, I was just asked to fix it. It looks like a bootloop issue. The Product name is **SM-G360V**. I have already attempted flashing TWRP on it with Odin3, but it fails saying SECURE CHECK FAIL : recovery and the next line is Custom Binary(recovery) Blocked By R/L. I have no idea how to flash a custom ROM (of which I can't find) without a custom recovery.

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 deleted my only launcher and now I cannot open settings to set to debug mode in order to use ADB or similar to install a new launcher. I can't open the Play store, can't open anything except those that use voice commands: e-mail, text, phone, maps, navigation, and note to self. Oh, and it only boots in safe mode. It's an LG Optimus T. How do I put a launcher back on this phone?

My Samsung Note 9 bricked itself after I installed an apk theme. Upon trying to reinstall the software, I'm met with an error saying that /data failed to mount. I have tried clearing the cache and factory resetting in the recovery mode, along with repartitioning and erasing the nand in Odin, but no luck. The phone is 100% stock and I can't unlock the bootloader as it's a US model. Is the phone just done for at this point? I haven't found any info that points to me being able to do anything but get a new motherboard.

When I tried to reboot my phone a few days ago, it booted into CSC fastboot mode and it couldn't boot into the OS. I tried Vol down + power off combo to boot into recovery but that doesn't work and after showing the Android Phone screen, it just powers off again. The CSC fastboot screen is the same as on this image of another phone (same model) having the same issue: I unlocked the bootloader using fastboot and now it shows FASTBOOT instead of CSC FASTBOOT.

getvar all

shows 'unlocked: yes', so the bootloader is definitely unlocked. Then I flashed the stock rom for my phone and even after successfully flashing all required img files, I still cannot boot successfully. I tried this procedure multiple times but nothing works. I also can't boot into recovery after flashing stock recovery.img or even compatible twrp versions. Flashing works successfully but it shows FAILED when trying to boot. After leaving the phone alone for a day, I connected it to the pc using the usb cable this morning and the battery charging animation showed up and it showed the Bootloader unlocked warning with 'press power off to pause boot' I got excited or something and pressed the power off button. It then booted into the fastboot mode again as usual. But now it briefly shows the battery animation when I connect it to the charger when it's switched off, and it boots into fastboot mode again. I tried re-locking the bootloader and trying it again, same with locking it and nothing works. Neither does trying to flash or boot recovery/twrp, or flashing the stock rom again. The volume buttons are working fine and there was no problem with them before as well. I also opened the device and tried pressing the buttons manually and got the same result.

getvar all

output:

I installed LineageOS on my Samsung M20. After installing it removed the TWRP. However, I needed TWRP to install MAGISK so I flashed the TWRP image again but this time the phone is stuck on the TWRP splash screen. It can only reboot (Power + Volume down), it isn't detected by ODIN nor can I enter download mode, therefore only the Samsung boot logo and the TWRP splash screen.

**Question** What is a "Firehose file" (or its counterpart, the mere "Firehose", if that's more applicable)? **Rationale and Research** I ask because, in threads like the undermentioned: 1. [forum.fairphone.com/t/trapped-in-fastboot-mode-with-locked-bootloader-and-corrupted-custom-rom](https://forum.fairphone.com/t/trapped-in-fastboot-mode-with-locked-bootloader-and-corrupted-custom-rom/80985/18?u=rokejulianlockhart) and 1. [xdaforums.com/t/does-twrp-function-with-non-aosp-oses.4692346](https://xdaforums.com/t/does-twrp-function-with-non-aosp-oses.4692346/post-89709606) ...I have been informed that it's necessary for the Emergency Download Mode (EDL) to work, which itself is necessary to recover a soft-or-hard-bricked AOSP device. However, what it actually is isn't well elaborated on. You can see an example of this at [github.com/bkerler/edl/discussions/577](https://github.com/bkerler/edl/discussions/577#discussion-7174797) , where the tool is entirely about "Firehose", yet doesn't appear to explain much about how to acquire the data necessary to operate it. Understanding this would be useful to me because I've an Amazon Fire tablet which is currently bricked, due to a failed superuser elevation after a Recovery partition wipe (in preparation for TWRP installation) leaving me with an entirely inoperable device. I don't want this to accidentally occur to a device which I care about more, without me having a way to restore it to a usable state. **(Lack of) Duplicates** [Searching for "What is Firehose?" in android.stackexchange.com](https://android.stackexchange.com/search?q=what+is+firehose) returns two mostly irrelevant results: 1. https://android.stackexchange.com/questions/253944/flash-avb-custom-key-using-edl?r=SearchResults&s=1%7C15.2844 1. https://android.stackexchange.com/questions/225868/need-help-unbricking-my-google-pixel-sailfish/225920?r=SearchResults&s=2%7C12.0902#225920