WiFi issues - HTC One S

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.

Related

[Discussion] Rogers Post-911 Rooting

I wanted to bring this in here, as I found a way to enable fastboot to flash recovery!
Quick device info update:
HBOOT-1.33.0010
Radio-3.22.26.17
Ok, first put the phone into fastboot mode. Then execute the command:
fastboot oem rebootRUU
Wait for it to reboot in RUU mode. Then, when I execute fastboot flash recovery recovery-RA-dream-v1.6.2R.img, I get the following:
sending 'recovery' (4568 KB)... OKAY [ 1.721s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 3.036s
So, is there a signed recovery we can launch?
As an update, booting recovery:
downloading 'boot.img'... OKAY [ 1.647s]
booting...
hangs here

HTC Ville hboot 2.15 unable to unlock bootloader

C:\Program Files\Android>fastboot flash unlock_token Unlock_code.bin
sending 'unlock_token' (0 KB)...
OKAY [ 0.141s]
writing 'unlock_token'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.156s
Anyone can help me with this? The problem arose after flashing twrp I ran RUU several times but it didn't help

Fastboot error

writing 'system' 1/4...
**FAILED (remote: flash write failure)**
finished. total time: 9.167s
Any solution...I have unlocked bootloader.

Require some help and some advice if possible.

Hi There,
I hope someone can advise and possibly provide help resolving this problem.
The Moto G4 XT1622 is not able to boot to OS, It only boots into bootloader, cannot go into recovery and cannot go into Factory Mode etc.
The error i get on the phone is....
"Start Up Failed"
Failed to verify hab image boot
Failed to verify boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
I have tried to clear fb_mode and tried to unlock the bootloader without success.
I have tried various stock roms to get this fixed. The phone has never been unlocked and not been rooted.
C:\adb>fastboot oem fb_mode_set
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.094s
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.172s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.319s
C:\adb>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1848 KB)...
OKAY [ 0.094s]
writing 'logo'...
OKAY [ 0.078s]
finished. total time: 0.172s
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.687s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.891s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.664s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.883s
C:\adb>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257278 KB)...
OKAY [ 9.982s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.097s
C:\adb>fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (258607 KB)...
OKAY [ 10.125s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.157s
C:\adb>fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (258384 KB)...
OKAY [ 10.076s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.107s
C:\adb>fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (252313 KB)...
OKAY [ 9.973s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.004s
C:\adb>fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (254404 KB)...
OKAY [ 10.017s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.064s
C:\adb>fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (258060 KB)...
OKAY [ 10.114s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.161s
C:\adb>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (76857 KB)...
OKAY [ 3.038s]
writing 'modem'...
OKAY [ 2.036s]
finished. total time: 5.075s
C:\adb>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\adb>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\adb>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (1864 KB)...
OKAY [ 0.100s]
writing 'fsg'...
OKAY [ 0.109s]
finished. total time: 0.210s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.031s
C:\adb>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.078s]
finished. total time: 0.078s
C:\adb>fastboot erase customize
erasing 'customize'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\adb>fastboot erase clogo
erasing 'clogo'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\adb>fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.016s
Click to expand...
Click to collapse
Phatzy said:
Hi There,
I hope someone can advise and possibly provide help resolving this problem.
The Moto G4 XT1622 is not able to boot to OS, It only boots into bootloader, cannot go into recovery and cannot go into Factory Mode etc.
The error i get on the phone is....
"Start Up Failed"
Failed to verify hab image boot
Failed to verify boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
I have tried to clear fb_mode and tried to unlock the bootloader without success.
I have tried various stock roms to get this fixed. The phone has never been unlocked and not been rooted.
Click to expand...
Click to collapse
It looks to me like you're trying to flash a firmware that is a downgrade from what was already on the device. It's probably blocking you because it won't allow a downgrade. Flash the version that the device already had on it or flash a newer version.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
I throught that would be the case but i have tried the 4 roms available for this device and even the 7.0 OTA rom but nothing if able to flash. I cannot even unlock the bootloader.
Thanks
Phatzy said:
I throught that would be the case but i have tried the 4 roms available for this device and even the 7.0 OTA rom but nothing if able to flash. I cannot even unlock the bootloader.
Thanks
Click to expand...
Click to collapse
You may have to faatboot flash the individual .img(boot, system, cache, recovery, etc..) files by themselves.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Yeah I tried that too. I just get the same errors as this.....
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.094s
Click to expand...
Click to collapse
Phatzy said:
Yeah I tried that too. I just get the same errors as this.....
Click to expand...
Click to collapse
Do you have USB debugging enabled?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hi,
I dont think so as I cannot check due to the phone not able to get pass bootloader. I tried to use the fb_mode command but still goes back to bootloader saying filed to start.
Thanks..
Droidriven said:
Do you have USB debugging enabled?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse

now my device(mi a2 lite) is stuck in a boot loop and the device is locked after android 10 update

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.

Categories

Resources