Just got my phone trying to flash the custom recovery to no joy (bootloader unlocked)
Keep getting
C:\Users\graem\Desktop\1p3>fastboot flash recovery recovery.img
< waiting for device >
target reported max download size of 536870912 bytes
sending 'recovery' (17776 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 0.022s
C:\Users\graem\Desktop\1p3>fastboot flash recovery recovery.img
sending 'recovery' (17776 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.013s
C:\Users\graem\Desktop\1p3>
Any thoughts guys
This was using the [email protected]_radaideh-v2.1
How i got it working was installing stock recovery from tool then install custom and all worked fine.
Related
Keep getting:
sending 'system' (955771 KB)
FAILED (remote: (00000006))
finished. total time: 0.004s
When trying to flash system.img
Can flash boot and recovery no problems, any ideas?
I've the same thing, I think it's normal.
How did you get around it?
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
Dear all, I would reset my Mate and did a factory reset from Android Menu. After that the phone was going to the TWRP Recovery. So I didn't read further tutorials and thought a full wipe would not a bad Idea. But sadly I did not found the old Custom Image ZIP file and would install the factory default firmware. UPDATE.APP. After some doings I lost my TWRP Image (I think by swiping) and now I have only the HUAWEI SDCARD&USB UPDATE AGENT VERSION 2.0 running.
When I try now to update of UPDATE.APP from SDCARD, the error is, the Agent can not mount. I was trying two SD Cards. fresh formatted.
Are all sizes compatible? Or do I have to use a small SD card?
Hi all, I found this instruction: http://forum.xda-developers.com/showthread.php?t=2682979
I tried, but failed...
..........\Downloads\Ascend_Mate_firmware\adb>fastboot flash BOOT BOOT.img
< waiting for device >
target reported max download size of 838860800 bytes
sending 'BOOT' (5308 KB)...
OKAY [ 0.228s]
writing 'BOOT'...
FAILED (remote: partition does not exist)
finished. total time: 0.232s
..........\Downloads\Ascend_Mate_firmware\adb>fastboot flash RECOVERY RECOVERY.img
target reported max download size of 838860800 bytes
sending 'RECOVERY' (7942 KB)...
OKAY [ 0.340s]
writing 'RECOVERY'...
FAILED (remote: partition does not exist)
finished. total time: 0.343s
..........\Downloads\Ascend_Mate_firmware\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
My M8 was once upon a time a Rogers M8.
Quite some time ago i converted it to a GPE with 5.1.
It was rooted and is S-Off.
Last night I pushed the MM RUU from GraphixNYC. It worked and I was happy.
Except I like to teak the DPI so I root it.
This morning I installed TWRP2.8.7.0 recovery and allowed TWRP to SuperSu it.
Now when it boots I don't get past the loading screen.
I can put it in Fastboot, connect to it from my Mac, and to push the LP/MM RUUs.
Both fail in the same way (below). What can I do?
------ 5.1 ----
~/Documents/Android/platform_tools/Mac => ./fastboot devices
SH45LWM0nnnnn fastboot
~/Documents/Android/platform_tools/Mac => ./fastboot flash zip RUU51.zip
target reported max download size of 1826414592 bytes
sending 'zip' (649759 KB)...
OKAY [ 23.080s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 23.085s
~/Documents/Android/platform_tools/Mac =>
----- 6.0 ---
~/Documents/Android/platform_tools/Mac => ./fastboot flash zip RUU60.zip
target reported max download size of 1826414592 bytes
sending 'zip' (633780 KB)...
OKAY [ 22.373s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 22.378s
~/Documents/Android/platform_tools/Mac =>
----
I got this working.
I took the v6 RUU, put it on my external SD, renamed it as 0p6bimg and booted into HBOOT.
I guess I did this: http://forum.xda-developers.com/showthread.php?t=2708589
A second time, carefully following the directions I have MM + systemless root.
http://forum.xda-developers.com/htc-one-m8/general/root-root-marshmallow-gpe-supersu-t3242210