So I downloaded this Archive.zip from http://forum.xda-developers.com/showthread.php?t=2064868
and I boot my device to fastboot...
now on my pc when i type:
fastboot flash recovery adsp.img
I get:
sending 'recovery' (6345 KB)...
OKAY [ 0.950s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 0.998s
--------------------------------------------------------
or if i try:
>fastboot flash adsp adsp.img
sending 'adsp' (6345 KB)...
OKAY [ 0.949s]
writing 'adsp'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.485s
What am I doing wrong? I have HBOOT-1.13 and viperones rom on my HTC One S
Im pretty sure you cant flash it through fastboot.
You need hboot 1.09 or lower and flash through recovery.
hey guys
i have p920 with problem hang on the logo
but can not flash and error after 35 %
please help me thanks
can not go to recovery custom
phone is unlocke bootloader and write recovery philz_touch but after write can not go to recovery and still here bootloader!!!!?
C:\Documents and Settings\Administrator\Desktop\ADB & FASTBOOT>fastboot flash re
covery philz_touch_6.18.7-zaradug.img
sending 'recovery' (8056 KB)...
OKAY [ 1.750s]
writing 'recovery'...
OKAY [ 0.828s]
finished. total time: 2.578s
ive been following numerous tutorials and with everyone of them i receive the same error message what could i be doing wrong?
i turned oem on on fastboot but that as far as i could go i cant go beyond flashing the recovery.
sending 'recovery' (4876 KB)...
OKAY [ 1.131s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.458s
XDA Visitor said:
ive been following numerous tutorials and with everyone of them i receive the same error message what could i be doing wrong?
i turned oem on on fastboot but that as far as i could go i cant go beyond flashing the recovery.
sending 'recovery' (4876 KB)...
OKAY [ 1.131s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.458s
Click to expand...
Click to collapse
Hi
Thank you for using XDA Assist
You can create an account and post this here
http://forum.xda-developers.com/lg-v10/help
Thank you..
using cmd
when trying to unlock oem; giving:
FAILED (remote: OEM unlock is not allowed)
finished. total time: 0.011s
-----------------------------------------------------------------
when trying to flash boot or recovery; giving:
boot:
sending 'boot' (29069 KB)...
OKAY [ 0.765s]
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.787s
recovery:
sending 'recovery' (42204 KB)...
OKAY [ 1.103s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.121s
-----------------------------------------------------------------
when trying to change the partition giving:
C:\Users\Rfastboot --set-active=b
fastboot: unknown option -- set-active=b
-----------------------------------------------------------------
please help!!!
FkReMy said:
using cmd
when trying to unlock oem; giving:
FAILED (remote: OEM unlock is not allowed)
finished. total time: 0.011s
-----------------------------------------------------------------
when trying to flash boot or recovery; giving:
boot:
sending 'boot' (29069 KB)...
OKAY [ 0.765s]
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.787s
recovery:
sending 'recovery' (42204 KB)...
OKAY [ 1.103s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.121s
-----------------------------------------------------------------
when trying to change the partition giving:
C:\Users\Rfastboot --set-active=b
fastboot: unknown option -- set-active=b
-----------------------------------------------------------------
please help!!!
Click to expand...
Click to collapse
From what I found on the internet, I guess you didn't turn on the setting `oem allow unlock' in developer settings.
But isn't there `rescue party' (a subsystem of androids recovery which shows two options: 1) Try again 2) Factory data reset)?
If it is, just press that Try again button, wait until it boots into rescue party again and then press the Try again button again. Do that 5-7 times in a row (depending on the phone). Your phone should detect that your current slot is unbootable and should boot into the unupdated slot.
You could also try to find the stock image (or whatever image you have currently installed) and flash it within recovery (there should be a button labeled like `update...' or `sideload...' or something). That should also work.
If nothing helps, you could also factory data reset and hope that it works now...
If that also doesn't work, you could research abit about edl (emergency donwload mode) and how to use it to reflash your device.
Basically, I tried installing Pixel Experience and in the end, ended up completely wiping everything.
Things I can do:
Flash TWRP
Get into Fastboot
Get into EDL/Crashdump
Things that don't work:
I tried flashing a stock ROM through FastBoot, and didn't work, got the following:
Spoiler
C:\Users\bstei\Downloads\adb>fastboot flash aop aop.img
Sending 'aop' (200 KB) OKAY [ 0.013s]
Writing 'aop' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash bluetooth bluetooth.img
Sending 'bluetooth' (652 KB) OKAY [ 0.026s]
Writing 'bluetooth' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash boot boot.img
Sending 'boot_a' (98304 KB) OKAY [ 2.854s]
Writing 'boot_a' OKAY [ 0.241s]
Finished. Total time: 3.819s
C:\Users\bstei\Downloads\adb>fastboot flash dsp dsp.img
Sending 'dsp' (65536 KB) OKAY [ 1.946s]
Writing 'dsp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash dtbo dtbo.img
Sending 'dtbo' (8192 KB) OKAY [ 0.250s]
Writing 'dtbo' OKAY [ 0.029s]
Finished. Total time: 0.291s
C:\Users\bstei\Downloads\adb>fastboot flash LOGO LOGO.img
Sending 'LOGO' (7780 KB) OKAY [ 0.244s]
Writing 'LOGO' FAILED (remote: '(LOGO_a) No such partition')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash modem modem.img
Sending 'modem_a' (240188 KB) OKAY [ 7.226s]
Writing 'modem_a' OKAY [ 0.846s]
Finished. Total time: 8.094s
C:\Users\bstei\Downloads\adb>fastboot flash oem_stanvbk oem_stanvbk.img
fastboot: error: cannot load 'oem_stanvbk.img': No such file or directory
C:\Users\bstei\Downloads\adb>fastboot flash qupfw qupfw.img
Sending 'qupfw' (56 KB) OKAY [ 0.009s]
Writing 'qupfw' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash storsec storsec.img
Sending 'storsec' (20 KB) OKAY [ 0.004s]
Writing 'storsec' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash multiimgoem multiimgoem.img
Sending 'multiimgoem' (16 KB) OKAY [ 0.005s]
Writing 'multiimgoem' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash uefisecapp uefisecapp.img
Sending 'uefisecapp' (124 KB) OKAY [ 0.005s]
Writing 'uefisecapp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash recovery recovery.img
Sending 'recovery' (102400 KB) OKAY [ 3.073s]
Writing 'recovery' OKAY [ 0.294s]
Finished. Total time: 3.380s
C:\Users\bstei\Downloads\adb>fastboot --disable-verity flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.002s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.020s
C:\Users\bstei\Downloads\adb>fastboot --disable-verity flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.030s
C:\Users\bstei\Downloads\adb>fastboot flash opproduct opproduct.img
fastboot: error: cannot load 'opproduct.img': No such file or directory
C:\Users\bstei\Downloads\adb>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.002s]
Tried using the MSM unbrick tool but every single time I tried to use it, I get the Sahara Communications failed. I tried on two different computers with two different USB cords, one Intel based and one AMD based.
Guys, please help me, you're my last hope.
HorseyMD said:
Basically, I tried installing Pixel Experience and in the end, ended up completely wiping everything.
Things I can do:
Flash TWRP
Get into Fastboot
Get into EDL/Crashdump
Things that don't work:
I tried flashing a stock ROM through FastBoot, and didn't work, got the following:
Spoiler
C:\Users\bstei\Downloads\adb>fastboot flash aop aop.img
Sending 'aop' (200 KB) OKAY [ 0.013s]
Writing 'aop' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash bluetooth bluetooth.img
Sending 'bluetooth' (652 KB) OKAY [ 0.026s]
Writing 'bluetooth' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash boot boot.img
Sending 'boot_a' (98304 KB) OKAY [ 2.854s]
Writing 'boot_a' OKAY [ 0.241s]
Finished. Total time: 3.819s
C:\Users\bstei\Downloads\adb>fastboot flash dsp dsp.img
Sending 'dsp' (65536 KB) OKAY [ 1.946s]
Writing 'dsp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash dtbo dtbo.img
Sending 'dtbo' (8192 KB) OKAY [ 0.250s]
Writing 'dtbo' OKAY [ 0.029s]
Finished. Total time: 0.291s
C:\Users\bstei\Downloads\adb>fastboot flash LOGO LOGO.img
Sending 'LOGO' (7780 KB) OKAY [ 0.244s]
Writing 'LOGO' FAILED (remote: '(LOGO_a) No such partition')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash modem modem.img
Sending 'modem_a' (240188 KB) OKAY [ 7.226s]
Writing 'modem_a' OKAY [ 0.846s]
Finished. Total time: 8.094s
C:\Users\bstei\Downloads\adb>fastboot flash oem_stanvbk oem_stanvbk.img
fastboot: error: cannot load 'oem_stanvbk.img': No such file or directory
C:\Users\bstei\Downloads\adb>fastboot flash qupfw qupfw.img
Sending 'qupfw' (56 KB) OKAY [ 0.009s]
Writing 'qupfw' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash storsec storsec.img
Sending 'storsec' (20 KB) OKAY [ 0.004s]
Writing 'storsec' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash multiimgoem multiimgoem.img
Sending 'multiimgoem' (16 KB) OKAY [ 0.005s]
Writing 'multiimgoem' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash uefisecapp uefisecapp.img
Sending 'uefisecapp' (124 KB) OKAY [ 0.005s]
Writing 'uefisecapp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
C:\Users\bstei\Downloads\adb>fastboot flash recovery recovery.img
Sending 'recovery' (102400 KB) OKAY [ 3.073s]
Writing 'recovery' OKAY [ 0.294s]
Finished. Total time: 3.380s
C:\Users\bstei\Downloads\adb>fastboot --disable-verity flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.002s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.020s
C:\Users\bstei\Downloads\adb>fastboot --disable-verity flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.030s
C:\Users\bstei\Downloads\adb>fastboot flash opproduct opproduct.img
fastboot: error: cannot load 'opproduct.img': No such file or directory
C:\Users\bstei\Downloads\adb>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.002s]
Tried using the MSM unbrick tool but every single time I tried to use it, I get the Sahara Communications failed. I tried on two different computers with two different USB cords, one Intel based and one AMD based.
Guys, please help me, you're my last hope.
Click to expand...
Click to collapse
I seem to remember getting the "'Flashing is not allowed for Critical Partitions" error when using bootloader mode instead of using fastbootd mode.
BillGoss said:
I seem to remember getting the "'Flashing is not allowed for Critical Partitions" error when using bootloader mode instead of using fastbootd mode.
Click to expand...
Click to collapse
If I remember correctly, I tried both, but I'll go try again
BillGoss said:
I seem to remember getting the "'Flashing is not allowed for Critical Partitions" error when using bootloader mode instead of using fastbootd mode.
Click to expand...
Click to collapse
Seems like I've gotten further this time, as it seems to be attempting to boot into Pixel Experience. How exactly do I get into FastbootD as opposed to normal fastboot?
EDIT: IT WORKS! YOU'RE A LIFESAVER
BillGoss said:
I seem to remember getting the "'Flashing is not allowed for Critical Partitions" error when using bootloader mode instead of using fastbootd mode.
Click to expand...
Click to collapse
Thank you so much for the help, the successful flashing of at least a few images seems to have made the MSM tool work, right now it's booting up, hoping it will be successful...we'll see here in a second, I guess...
IT WORKED!!!!!