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?
Related
One day my battery was empty and then i charged it. it failed many times to startup. i got error about SDcard crashed or something like that. then i shut down it. then it didnt start. no fastboot. no CWM. nothing. but it is going APX mode. and i tried to use nvflash to restore. but error. here is the error.
.................................................. ............
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x
42000 (0x37042000) flags: 0
Press any key to continue . . .
It stops like this. Can anyone help me please. my DS is not starting up, no boot, no CWM i cant use anything other than nvflash. please help me? is there any other method to restore using APX mode.
Hi, i cant get into CWM (recovery) after installing rom so I tried NvFlash but it fails...
failed executing command 14 NvError 0x120000
command failure: partition download fail
any solutions? or i can just dump my optimus to trash
SOLVED!
http://forum.xda-developers.com/showthread.php?t=1715272
flashed it to stock, easy and fast, tnx to Homero
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 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?
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)