- #Fastboot flash recovery invalid argument how to
- #Fastboot flash recovery invalid argument android
- #Fastboot flash recovery invalid argument Pc
Shell doesn't work in ADB sideload mode, that's the only ADB thing the stock recovery has. Just need to think of a way to access ADB shell on it to try to change permissions.
![fastboot flash recovery invalid argument fastboot flash recovery invalid argument](https://i.ytimg.com/vi/Rs4zcryNt5Y/hqdefault.jpg)
This would certainly explain what happened to my phone.
#Fastboot flash recovery invalid argument android
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. I don't know if tools like AFT or xfstk can do anything for me.Įdit: 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. 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? True, and I can switch this to PTP, but once I go back to Helium, it bounces back to MTP So I felt I should root the phone to circumvent this, and I tried to follow this Howto. I tried to flash TWRP (I have stock recovery) and I tried to erase and format cache through fastboot, but both give this error:įAILED (remote: 'Can not mount the necessary partition') Hi, my original intention was just to move as much as possible from my old phone to my new FP2 with Android 6, but Helium Backup always complains that USB debugging is not in PTP mode. Factory reset formats /data fine, but when it gets to /cache, gives the error and aborts. Trying to wipe cache, factory reset the phone, mount /system, flash a ROM from SD card, ADB sideload, everything gives the error multiple times. I can get into recovery, but can't do anything in recovery, because everything gives this error:Į:failed to mount /cache (invalid argument) fastboot oem unlock which gives me FAILED (remote: oem unlock is not allowed) fastboot boot twrp-3.3.1-0k4y0z-20200202-02-fp3.img which gives me FAILED (remote: unlock device to use this command) fastboot flash boot boot. But when I reboot it into recovery, the stock CM recovery menu appears. It gets to the logo and the loading circle and just gets stuck there forever. Device is already unlocked, i typed those things to flash TWRP (2.8.5.1-bacon) 'fastboot devices'. Issue the following commands one by one: adb reboot bootloader fastboot erase modemst1 fastboot erase modemst2.
#Fastboot flash recovery invalid argument Pc
Connect your device to the PC and open a command window on the PC. Enable Developer options & USB debugging on your Android device.
#Fastboot flash recovery invalid argument how to
In CMD, type following commands and hit enter after each line: fastboot flash recovery motoetwrp2.7.0.0v1.2. How to Fix EFS from Bootloader Mode using Fastboot commands.
![fastboot flash recovery invalid argument fastboot flash recovery invalid argument](https://i2.wp.com/ministryofsolutions.com/wp-content/uploads/Huawei-P9-Lite-Root-Nougat/Huawei-P9-Lite-Nougat-Root_10.jpg)
Press the volume up or power button (depending on your phone) to select it. Unplug your phone and use the volume down key to scroll to the Recovery option in your bootloader.
![fastboot flash recovery invalid argument fastboot flash recovery invalid argument](https://i.ytimg.com/vi/boyU1MnI7HU/maxresdefault.jpg)
Click on the option ‘Open command window here’. If all goes well, you should see a success message in your Command Prompt window. Then after I charged it up and restarted it, it wouldn't turn on. Now right-click on the ‘ADB and Fastboot’ folder while holding down the ‘Shift’ key in Windows. I have a Asus Zenfone 2 and a few days ago it ran out of battery and turned off.