When trying to flash a couple of recovery ROMs, I got messages of "Variable not supported" and "FAILED (remote failure)". Googling told me that all Motorola phones require a specific build of fastboot in order to flash ROMs. However, I can't find one. Does anyone know where I can find the most recent build?
Related
When I try flashing anything at all it says FAILED (remote: not supported in locked device). I unlocked it via "fastboot oem unlock" but I noticed it keeps getting back to the locked state when the phone reboots to bootloader.
In this thread people say to flash cache.img and see what happens. So I entered the command "fastboot flash cache cache.img" and I got FAILURE (remote: flash write failure).
I just want to mention that I've tried several guides and haven't had any luck. Also I'd like to say I haven't installed any custom ROMs nor rooted my phone before this happened.
Heres's an androidExchange topic if anyone wants to read it. http://android.stackexchange.com/qu...re-while-trying-to-fix-a-bootloop/98809#98809
Is there anything else I can do to confirm that my phone is dead, meaning it's some kind of a hardware problem?
Sorry, but your emmc is fried. Not being able to lock/unlock is a sure sign. You'll have to rma the device.
Sent from my Nexus 9 using XDA Free mobile app
Let me explain my story.
Rooted phone, installed dual recovery, decided to have some xposed modules, installed a ton, went into a boot animation, went into recovery and decided to clear system and now I can only access fastboot mode. I tried to fastboot flash boot Z3_DooMLoRD_AdvStkKernel_v01_FW-93.img, but i get FAILED (remote: Command not allowed) at the end so it doesn't work.
I don't think my bootloader is unlocked. So I guess I bricked my phone unless someone has a way to fix it. I literally rooted my phone two days ago.
Flashtool says the same thing.
Model number: D6603.
EDIT: Currently testing if I can flash an FTF.
EDIT: Praise the lord, flashing a new FTF works amazing.
/Thread.
Hello,
I was facing a lot of issues with my YUPHORIA. So, I tried to flash it using the official instructions on official forum using Fastboot.
The flashing got stuck when it was trying to flash the "system" partition. I disconnected the cable and tried the flashing process again.
Now, I am able to flash everything else except "system"
It is giving an error -
"FAILED (remote: flash write failure)"
ADB is not detecting my phone.
QFIL is also showing "No Ports Found"
However, Fastboot is working fine.
I donot have TWRP on my phone as of now.
Please help !
I am having exact same problem. Were you able to find solution for it?
Same issue here
Did you get the final solution?
I cant not flash system.img to my softbricked Yu Yuphoria 5110 even with the latest version of adb and fastboot and even with the -S option! Nothing works! Can't flash only system.img, other images are getting flashed. Pl help!
Hi,
I managed to install openkirin/omnirom a year ago on my honor6x but i want to sell the phone so i want to go back to the debranded india version (bln-l22)
i still have all the old tools and firmware, but somehow im getting an error when i try to reflash twrp with this guide https://forum.xda-developers.com/honor-6x/how-to/update-bln-l22c675-emui-5-x-x-to-emui-8-t3819317
However im stuck in adb on the 2nd step when i type "fastboot flash recovery twrp-3.1.1-0-berlin.img"
im getting "Writing 'recovery' FAILED (remote: 'partition length get error') fastboot: error: Command failed"
i cant really interpret this error. any pointers that i could try? or is there maybe even a tutorial on how to rollback from custom roms?
Thanks and Cheers
So, at first, I thought it was my computer because I was running the leaked Windows 11, but now its doing it with windows 10 as well. I was trying to install GrapheneOS (bootloader unlocked, done this countless times, tried different cables) but for some reason whenever it gets to
Code:
Writing sparse 'system_b' 4/10 FAILED (remote: 'Operation not permitted')
I get this with google's Flash-All for flashing to stock, I get this on GrapheneOS, I get it with GSI images. Seems like its always step 4 on the ROM. Not sure what's going on here. Stuck at bootloader currently. Recovery states android 11.
I'm about to attempt to flash with Chrome via google's online flash tool
Update: Flashed GrapheneOS "successfully" with chrome through their online flasher... but then start up error is "error setup km". Fresh install of win10
Update2: Fixed. Flashed the OTA image from google via stock recovery with adb sideload