Hi,
what i did so far was:
unlocked the bootloader
download the twrp recovery img (...ruu.lalleman.net/HTC_M8S%28QL_UL%29/Recovery/twrp-recovery-2.8.7.0-m8s-qlul/)
set phone on Fastboot USB
over the cmd bar (windows 10) i used fastboot and got this result:
C:\Android>fastboot flash recovery twrp-2.8.7.0-m8s-qlul.img
target reported max download size of 16510976 bytes
Invalid sparse file format at header magi
sending sparse 'recovery' 1/2 (15368 KB)...
OKAY [ 1.899s]
writing 'recovery' 1/2...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.907s
I have no idea what i did wrong or how i can solve the problem. I just wanted run the twrp, use the Superuser. zip to have the rootet htc one m8s.
Thajin said:
Hi,
what i did so far was:
unlocked the bootloader
download the twrp recovery img (...ruu.lalleman.net/HTC_M8S%28QL_UL%29/Recovery/twrp-recovery-2.8.7.0-m8s-qlul/)
set phone on Fastboot USB
over the cmd bar (windows 10) i used fastboot and got this result:
C:\Android>fastboot flash recovery twrp-2.8.7.0-m8s-qlul.img
target reported max download size of 16510976 bytes
Invalid sparse file format at header magi
sending sparse 'recovery' 1/2 (15368 KB)...
OKAY [ 1.899s]
writing 'recovery' 1/2...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.907s
I have no idea what i did wrong or how i can solve the problem. I just wanted run the twrp, use the Superuser. zip to have the rootet htc one m8s.
Click to expand...
Click to collapse
Use HTC_fastboot and not the generic fastboot..
nopynel said:
Use HTC_fastboot and not the generic fastboot..
Click to expand...
Click to collapse
I have the same problem and just ask now because i am really confused about the hole stuff here.. Have we now to tipp in cmd
C:\Android>HTC_fastboot flash recovery twrp-2.8.7.0-m8s-qlul.img ??
Edit: Ok, i find HTC_Fastboot there > ruu.lalleman.net/HTC_M8S%28QL_UL%29/Tools/Fastboot/ and it solve this problem.
But i think its still not everything fine.. if i change to hboot on bootlader i get this infomations
fs5.directupload.net/images/160727/z9lr634u.jpg
whether unlock bootloader?
Related
Hello i have a problem with this htc sensation of mine.. phone is Hang up in HTC logo only. i try to factory reset but its same. try to Recovery but theres no recovery only an image of unit with red triangle.. i try to download CWM here http://www.clockworkmod.com/rommanager via CMD command but its always failed. like below
i make a folder in my drive "d" name android and i put inside the recovery.img
C:\Users\Almutakhases\Desktop>d:
D:\>cd\android
D:\android>fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
D:\android>
Click to expand...
Click to collapse
can someone give me a working CWM for this unit.? help me to solve this please.
Model HTC Sensation PG58130
Problem: Hang on Logo Only
Action Taken:
1. try to factory Reset = Same problem
2. Try to Recovery Mode = No Recovery Mode. displays a mobile with a triangle and red exclamation mark.
3. Try to send CWM via Fastboot or CMD command = Failed. logs below
4. try to JTAG via Riff box = same Problem
C:\Users\Almutakhases\Desktop>d:
D:\>cd\android
D:\android>fastboot flash recovery recovery.img
sending 'recovery' (5400 KB)... OKAY [ 1.476s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.175s
D:\android>
########################################################################
C:\Users\Almutakhases\Desktop>d:
D:\>cd\android
D:\android>fastboot flash recovery recovery.img
sending 'recovery' (4618 KB)... OKAY [ 1.142s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.740s
D:\android>fastboot erase cache
erasing 'cache'... OKAY [ 1.559s]
finished. total time: 1.559s
D:\android>
Click to expand...
Click to collapse
Any Advice to Solve this
Sounds like you are s on and locked. You'll need to either unlock the boot loader,or run a full,signed ruu
Also,If you have a sensation,you have put your problem in the wrong forum. This is one x
thanks scooty i found RUU for this model and its all ok now.... :good:
Hey there,
as the title of the threat already indicates, my HTC One X got bricked.
As this usually happens when trying to flash some custom roms or recoverys, in my case it is the result of an official HTC update for android.
I can boot into Fastboot, and via cmd "fastboot devices" does show me the connected phone.
Now my approach for solving this matter was to flash the clockwork mod and then boot into recovery.
From there i wanted to pull data from the phone via adb commands.
The only problem is that my phone is locked. I cannot unlock it at the moment without wiping all data (which obviously would miss the whole data recovery point).
When i try tp flash the CWM in fastboot i get:
sending 'recovery' (8100 KB)...
FAILED (unknown status code)
finished. total time: 0.933s
I also tried to directly boot a recovery via fastboot boot recovery.img.
This resulted in
downloading 'boot.img'...
FAILED (unknown status code)
finished. total time: 0.933s
Well now I am seriously frustrated and dont know how to get my data.
Any help is very much appreciated.
Cheers
Josef
Update:
fastboot flash recovery recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (8100 KB)...
OKAY [ 1.066s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.066s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.068s
fastboot boot recovery recovery.img
cannot load 'recovery': Permission denied
any help?
joe1000 said:
Update:
fastboot flash recovery recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (8100 KB)...
OKAY [ 1.066s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.066s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.068s
fastboot boot recovery recovery.img
cannot load 'recovery': Permission denied
any help?
Click to expand...
Click to collapse
You must to unlock the device qith locked you can't do anything but if you unlock it is possible to wipe all data on the SD card
well but thats exactly the problem...
I downloaded the stock recovery for 5.0.1 from here http://forum.xda-developers.com/showpost.php?p=51836232&postcount=1
When I go into fastboot and try to flash I get an error:
$ fastboot flash recovery Tmo-M8-4.20.531.4-recovery.img
target reported max download size of 1826152448 bytes
sending 'recovery' (16046 KB)...
OKAY [ 1.753s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
This is with bootloader unlocked, if I try with bootloader locked I get:
$ fastboot flash recovery Tmo-M8-4.20.531.4-recovery.img
target reported max download size of 1826152448 bytes
sending 'recovery' (16046 KB)...
OKAY [ 1.757s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.763s
I notice theres a 1mb difference between twrp-2.8.7.0-m8.img (17.4mb) and Tmo-M8-4.20.531.4-recovery.img (16.4mb)
How am I supposed to get the stock recovery back without erasing anything else?
Device is S-OFF
Wow, turned out to be a bad download :| Redownloaded and it flashed fine
CHECK MD5 SUMS BEFORE FLASHING
Some screwed up stuff could have happened, thankfully even S-OFF does have some precautions.
MOD EDIT
Hi, Yeah I tried to flash the unlock image,
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.031s]
writing 'unlock'...
FAILED (remote: unlock failed)
finished. total time: 0.053s
Now I am in latest version Nougat
I fixed it ....
Solution ..just try one more time get new unlock_bootloader.IMG then flash it ...Enjoy
viknesh war said:
Hi, Yeah I tried to flash the unlock image,
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.031s]
writing 'unlock'...
FAILED (remote: unlock failed)
finished. total time: 0.053s
Now I am in latest version Nougat
Click to expand...
Click to collapse
Yup i was also facing the same problem a new bootloader image will fix it just request for a new bootloader image from zuk.
viknesh war said:
I fixed it ....
Solution ..just try one more time get new unlock_bootloader.IMG then flash it ...Enjoy
Click to expand...
Click to collapse
Thanks a lot bro.. I downloaded a new unlock_bootloader. Img file, and it worked just fine.
Actually I entered wrong serial number in zuk website while downloading the img file maybe because of that it didn't work at first
Hello people i hope someone can help me with a bit of a problem i have flashing twrp. I have done this many times in the past but i am having problems on this phone whn i try to flash recovery i am getting error below.
target reported max download size of 536870912 bytes
sending 'recovery' (11206 KB)...
OKAY [ 0.246s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.135s]
finished. total time: 0.387s
but iff i use command fastboot boot recovery.img it will boot into twrp no without problems.
sam00561 said:
Hello people i hope someone can help me with a bit of a problem i have flashing twrp. I have done this many times in the past but i am having problems on this phone whn i try to flash recovery i am getting error below.
target reported max download size of 536870912 bytes
sending 'recovery' (11206 KB)...
OKAY [ 0.246s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.135s]
finished. total time: 0.387s
but iff i use command fastboot boot recovery.img it will boot into twrp no without problems.
Click to expand...
Click to collapse
Ignore that error ... Don't boot in to system after flashing recovery instead boot to recovery first and then boot to system from twrp recovery
:good:
Hope this helps
jatinkhatri said:
Ignore that error ... Don't boot in to system after flashing recovery instead boot to recovery first and then boot to system from twrp recovery
:good:
Hope this helps
Click to expand...
Click to collapse
Cheers figured it out in the end