I tried to install ubports to my nexus 5 and I got the error
Error: fastboot:flash: Error: Flashing failed: {"error":{"code":1},"stderr":"ery'FAILED (remote: 'flash write failure')\rfastboot: error: Command failed"}
I tried to fix it with nexus root toolkit and tried normal adb help?
Related
I am trying to restore my S7 using the nvflash method as posted by illdill and I am getting the following error after the boot loader is downloaded successfully:
failed executing command 31 NvError 0x120002
command failure: writedeviceraw failed (bad data)
Any ideas?
Thanks
I believe this is the read only error that people have been talking about before. I was wondering if I formatted all the partitions if this would help to re-write the .img files. Anyone out there with a clue about NVFlash?
Trying to get this guys code example to run. I can send the app to my phone and see my chromecast. When I connect, I get the following error message:
StartSessionTask failed with error: failed to start application request failed
chromecast: route seesion start failed: errorCategory=1; errorCode=2
Error: failed to start application: request failed [errorCategory=1, errorCode=2]
LINK i.imgur.com/YnoyMEC.png
I'm following this guys REALLY awesome tutorial. Code is well documented and readable for any one else looking to get started.
chromecastlab.com/2013/11/06/hello-chromecast
Greetings
I'm trying to flashe recovery TWRP and it gives me an error
"FAILED (remote: image verification error)"
What should I do?
The botlauder is open
I installed TWRP and am trying to transfer the xiaomi.eu MIUI10 rom to the device to flash it, but I keep getting errors.
Trying to drag and drop through explorer always results in the same error:
(Cannot copy rom.zip. The device has either stopped responding or has been disconnected.)
Trying to sideload gives the error:
(Total xfer: 0.00x)
Trying to push gives the error:
(adb: error: failed to copy 'rom.zip' to '/sdcard/rom.zip': remote couldn't create file: Required key not available
rom.zip: 0 files pushed. 49.2 MB/s (262112 bytes in 0.005s)
Edit:
I realize I wasn't in sideload when trying to push. Now it gives a different error:
(adb: error: connect failed: closed)
I didn't realize that Pixels didn't work with Magisk's A/B update method, so I tried it, and afterwards I received the 'Your device is corrupt' on startup and the phone wouldn't boot.
I ended up flashing the December factory image (sans -w flag), and the phone now boots, but I still am receiving the 'Your device is corrupt' message on startup.
I did flash the patched init_boot, but the message existed before then.
Would anyone know of any steps I can take to get rid of this message? Preferably without data loss?
Thanks in advanced for any help.
Hmm. Try sideloading the OTA, see if that fixes it. Somehow, dm-verity got stuck in EIO mode. More details here
Edit: Did a little more research. In a ADB terminal (either recovery or system) you can use adb reboot "dm-verity enforcing"
Thanks for the reply.
Trying to sideload the OTA with adb sideload image.zip gives me the following error on my phone:
ERROR: recovery: footer is wrong
ERROR: recovery: Signature verification failed
ERROR: recovery: error: 21
I have verified the .zip hash matches the hash on the factory images site.
_____
If I try to run adb reboot "dm-verity enforcing" it gives me a "too many arguments" error in my terminal.
I did find this command, which seems the newer way of doing this:
fastboot flash vbmeta –disable-verity –disable-verification vbmeta.img
... but running that with the vbmeta.img from the OTA zip gives me this weird error:
fastboot: error: cannot load 'ûdisable-verity': No such file or directory (û character included)