I have just unlocked the Bootloader, and now I am trying to install TWRP recovery. I have tried the manual method through the command prompt, and also through Hasoon2000's toolkit. I just receive this error:
sending 'recovery' (7912 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.005s
I've tried reinstalling drivers, but that doesn't seem to solve it. I've also tried different USB ports. Has anyone encountered this error? Does anyone have a solution? Thanks.
Did you reboot your PC after uninstalling the drivers? Are you using a USB3 port? Win8?
bigdaddy619 said:
Did you reboot your PC after uninstalling the drivers? Are you using a USB3 port? Win8?
Click to expand...
Click to collapse
I didn't reboot, I'm gonna do that now; and yes, it's USB3, so probably gonna move to USB2? I'm on Win7.
Fired334 said:
I didn't reboot, I'm gonna do that now; and yes, it's USB3, so probably gonna move to USB2? I'm on Win7.
Click to expand...
Click to collapse
Yeah USB 3 ports are kinda finicky sometimes also have you updated your android-sdk files lately there have been quite a few updates the past couple weeks including drivers.
bigdaddy619 said:
Yeah USB 3 ports are kinda finicky sometimes also have you updated your android-sdk files lately there have been quite a few updates the past couple weeks including drivers.
Click to expand...
Click to collapse
No I haven't. I wasn't keeping up with the HTC One; I just received it. (Moving over from GNex)
Okay, I uninstalled drivers, restarted PC, used a USB2 port, and the TWRP flash was finally successful. :victory: Thanks. I should've known to do those steps.
sending 'recovery' (7912 KB)
OKAY [ 1.099s]
writing 'recovery'...
OKAY [ 0.639s]
finished. total time: 1.740s
Fired334 said:
Okay, I uninstalled drivers, restarted PC, used a USB2 port, and the TWRP flash was finally successful. :victory: Thanks. I should've known to do those steps.
sending 'recovery' (7912 KB)
OKAY [ 1.099s]
writing 'recovery'...
OKAY [ 0.639s]
finished. total time: 1.740s
Click to expand...
Click to collapse
Cool glad you got it enjoy
bigdaddy619 said:
Cool glad you got it enjoy
Click to expand...
Click to collapse
Thanks, looking forward to using my awesome-looking One.
Sloth said:
Did you reboot your PC after uninstalling the drivers? Are you using a USB3 port? Win8?
Click to expand...
Click to collapse
how can i uninstall adb??
getting the same problem
Related
Hey everyone, even though I dont have this device I figured it'd be good to have this thread so I'll start it.
This thread will contain all zips / firmwares for the device as well as changelogs if anyone wants to supply it. The zips will be flashable through bootloader not through recovery (I dont want to deal with the issues of "Well I bricked it because my recovery locked up" or however the hell you manage to break it.)
Download links:
M7_WL_JB_50_SPCS_Sprint_WWE_1.29.651.10-1.29.651.7 Firmware zip
Code:
Changelog for 1.29.651.10
- BlinkFeed improvements
- New Sprint Zone client
- Improved Back and Home key sensitivity
Any more files someone wants to provide feel free to PM me or post them here.
Is this the ota that's flashable for us rooted people
Sent from my HTCONE using Tapatalk 2
It's the firmware to flash through bootloader....
Thanks.
Sent from my Nexus 10 using Tapatalk HD
Is this safe for root or is this just a manuel upload instead of waiting for the OTA?
Should we flash the firmware or is it
Ok to just wait for a rooted Rom to be made with the new firmware and just flash that. I guess my question is are we going to be missing any key components by not taking it directly from HTC like newer radios
Sent from my HTCONE using xda premium
Nice to see you here Noob.
And it's OTAs. Official updates.
D3rped out Beastmode! HTC ONE!
gonowhere said:
Is this safe for root or is this just a manuel upload instead of waiting for the OTA?
Click to expand...
Click to collapse
fastboot oem rebootRUU
fastboot flash zip FIRMWARENAME.zip
fastboot reboot
Just installs new firmware for you. Doesnt actually affect your rom. Will wipe recovery though because there is no s-off.
dandan2980 said:
Should we flash the firmware or is it
Ok to just wait for a rooted Rom to be made with the new firmware and just flash that. I guess my question is are we going to be missing any key components by not taking it directly from HTC like newer radios
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
You flash the firmware because I believe the boot.img and tp.img are new. Haven't checked because I dont have an image dump to compare. But without s-off we cant flash selectively.
thronnos said:
Nice to see you here Noob.
And it's OTAs. Official updates.
D3rped out Beastmode! HTC ONE!
Click to expand...
Click to collapse
Still don't have a phone though. Kinda bums me out but because I got fired I can't afford the upgrade now. :/
And I'm less of a newb than you
So we can flash this through CMD WITHOUT HAVING STOCK RECOVERY. It will just erase twrp and we need to reflash twrp again??? Then flash stock rooted.
Sent from my HTCONE using xda premium
Dev-Host is borked
First of all, thank you for sharing it! I was waiting for CyanogenMod to update their ROM but they haven't yet.
I clicked on the link but it doesn't download the file after clicking on "download"
Any advice?
Thanks!
chamo311 said:
I clicked on the link but it doesn't download the file after clicking on "download"
Any advice?
Thanks!
Click to expand...
Click to collapse
Mine took me to a page not found the first time, but refreshing the page worked. Also, make sure you're clicking the right "download" button, as I had a couple ads with larger download buttons related to the ads.
Now my turn for a question. I tried flashing it and it failed. Anyone have an idea why? Here's what fastboot reported:
Code:
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.048s]
finished. total time: 0.063s
C:\Android>fastboot flash zip M7_WL_JB_50_SPCS_Sprint_WWE_1.29.651.10-1.29.651.7
-Firmware.zip
sending 'zip' (15538 KB)...
OKAY [ 1.809s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.059s
C:\Android>fastboot reboot
rebooting...
finished. total time: 0.044s
No harm done, but I'm still on 1.29.651.7
Thanks! I downloaded it!
Hmmm no idea, I haven't flashed mine yet....I'm away from a computer. I'll let you know.
Thanks again!
kzibart said:
Mine took me to a page not found the first time, but refreshing the page worked. Also, make sure you're clicking the right "download" button, as I had a couple ads with larger download buttons related to the ads.
Now my turn for a question. I tried flashing it and it failed. Anyone have an idea why? Here's what fastboot reported:
Code:
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.048s]
finished. total time: 0.063s
C:\Android>fastboot flash zip M7_WL_JB_50_SPCS_Sprint_WWE_1.29.651.10-1.29.651.7
-Firmware.zip
sending 'zip' (15538 KB)...
OKAY [ 1.809s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.059s
C:\Android>fastboot reboot
rebooting...
finished. total time: 0.044s
No harm done, but I'm still on 1.29.651.7
Click to expand...
Click to collapse
when you get that error just retype the fastboot flash command again immediately after you recieve the error and it should go then.
Aldo101t said:
when you get that error just retype the fastboot flash command again immediately after you recieve the error and it should go then.
Click to expand...
Click to collapse
I tried that (about 8 times) and still the same error each time. I even tried a shorter USB cable (which someone elsewhere suggested as a fix for this error), but no dice. So then I tried restoring the factory recovery and letting it take the update OTA. When the update started, it rebooted into recovery and then the screen went black with the red/orange led on for about 20 seconds, off for 5, repeating like that. I let it sit for a good 30 minutes before giving up. I had to long-press the power for 20 seconds to get it to reboot.
Still no harm done, but I'm still stuck on 1.29.651.7.
kzibart said:
I tried that (about 8 times) and still the same error each time. I even tried a shorter USB cable (which someone elsewhere suggested as a fix for this error), but no dice. So then I tried restoring the factory recovery and letting it take the update OTA. When the update started, it rebooted into recovery and then the screen went black with the red/orange led on for about 20 seconds, off for 5, repeating like that. I let it sit for a good 30 minutes before giving up. I had to long-press the power for 20 seconds to get it to reboot.
Still no harm done, but I'm still stuck on 1.29.651.7.
Click to expand...
Click to collapse
Have you checked the MD5 of the .zip?
kzibart said:
I tried that (about 8 times) and still the same error each time. I even tried a shorter USB cable (which someone elsewhere suggested as a fix for this error), but no dice. So then I tried restoring the factory recovery and letting it take the update OTA. When the update started, it rebooted into recovery and then the screen went black with the red/orange led on for about 20 seconds, off for 5, repeating like that. I let it sit for a good 30 minutes before giving up. I had to long-press the power for 20 seconds to get it to reboot.
Still no harm done, but I'm still stuck on 1.29.651.7.
Click to expand...
Click to collapse
YES, i tried this also and got the same results.
Aldo101t said:
YES, i tried this also and got the same results.
Click to expand...
Click to collapse
Same here......FAILED for me too
aschlect said:
Same here......FAILED for me too
Click to expand...
Click to collapse
Are you guys SuperSu instead of Koush's Superuser?
jaytv said:
Are you guys SuperSu instead of Koush's Superuser?
Click to expand...
Click to collapse
Yes, I am SuperSU
I was trying to unlock my bootloader (which I've done a hundred times on other phones, including my wife's), but when I went to flash Unlock_token.bin, I received this error:
Code:
sending 'unlock_token' (0 KB)...
OKAY [ 0.142s]
writing 'unlock_token'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.145s
Thinking I did something wrong, I went back and resubmitted the identifier token from my phone and downloaded the unlock code that HTC e-mailed me - twice. No luck. I even resorted to threats of violence and yelling at it. Help?
DeathTorrent said:
I was trying to unlock my bootloader (which I've done a hundred times on other phones, including my wife's), but when I went to flash Unlock_token.bin, I received this error:
Code:
sending 'unlock_token' (0 KB)...
OKAY [ 0.142s]
writing 'unlock_token'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.145s
Thinking I did something wrong, I went back and resubmitted the identifier token from my phone and downloaded the unlock code that HTC e-mailed me - twice. No luck. I even resorted to threats of violence and yelling at it. Help?
Click to expand...
Click to collapse
Who is your provider, like who did you buy the phone from? If its Verizon, from what I've been reading, you may be out of luck
dgtiii said:
Who is your provider, like who did you buy the phone from? If its Verizon, from what I've been reading, you may be out of luck
Click to expand...
Click to collapse
It's T-Mobile, and as far as I can tell, I'm the only one having this issue.
DeathTorrent said:
It's T-Mobile, and as far as I can tell, I'm the only one having this issue.
Click to expand...
Click to collapse
Yeah, that's weird. Try fastboot erase cache, reboot, and try the token again. Then do the common sense stuff, try a different cable, different USB port, then a different computer
dgtiii said:
Yeah, that's weird. Try fastboot erase cache, reboot, and try the token again. Then do the common sense stuff, try a different cable, different USB port, then a different computer
Click to expand...
Click to collapse
Still no luck I think this phone just hates me
DeathTorrent said:
Still no luck I think this phone just hates me
Click to expand...
Click to collapse
What command are you using to send the code? Also, try unchecking fastboot in Settings -> Power, turn it off then hold power and volume down to enter bootloader.
Sent from my HTC One using XDA Premium 4 mobile app
redbull123 said:
What command are you using to send the code? Also, try unchecking fastboot in Settings -> Power, turn it off then hold power and volume down to enter bootloader.
Click to expand...
Click to collapse
I'm using
Code:
fastboot flash unlock_token Unlock_code.bin
Fastboot is already off, and I've been using adb to reboot into the bootloader, which is my standard procedure. Even so, rebooting the phone manually instead of using adb still results in the signature verify failure. I've tried it in both Linux and Winblows as well.
DeathTorrent said:
I'm using
Code:
fastboot flash unlock_token Unlock_code.bin
Fastboot is already off, and I've been using adb to reboot into the bootloader, which is my standard procedure. Even so, rebooting the phone manually instead of using adb still results in the signature verify failure. I've tried it in both Linux and Winblows as well.
Click to expand...
Click to collapse
Wrong command...
fastboot flash unlocktoken Unlock_code.bin
EddyOS said:
Wrong command...
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
...I'm an idiot -_-
im getting this error to
im using the right code but i still get the error im using a my touch 4g
So like a moron I installed ViperRom 5.0 with regular old CWM. Now as a result I'm stuck at the bootloader with no access to recovery.
I have no idea what to do now. PLEASE HELP!!!!
S-ON
Hboot 1.55.0000
Can you not boot into recovery from the boot loader or reboot and hold the volume down button?
Sent from my HTC One Max using Tapatalk!
gimmeitorilltell said:
Can you not boot into recovery from the boot loader or reboot and hold the volume down button?
Sent from my HTC One Max using Tapatalk!
Click to expand...
Click to collapse
I only have access to my bootloader......can't get into recovery or boot into the rom.
My terminal window keeps hanging on "waiting for device" so I don't think USB Debugging was enabled.....
The only thing that is looking bright is that my computer is recognizing my phone in Fastboot.
I'm completely clueless on what to do now.....
Please anyone help
Maybe try flashing recovery again?
Sent from my HTC One Max using Tapatalk!
Does it say fastbootusb? If not press the power button to select fastboot.
BD619 said:
Does it say fastbootusb? If not press the power button to select fastboot.
Click to expand...
Click to collapse
I can get to fastboot USB but from there I'm honestly lost...
nickhernandez said:
I can get to fastboot USB but from there I'm honestly lost...
Click to expand...
Click to collapse
I can help you remotely PM if interested
i'm in the same boat, but when I go to flash another recovery in fastboot my phone freezes after it fails to flash.
sending 'recovery' (9786 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.016s
Then my phone freezes and I have to reboot into bootloader.
Never mind solved it.
Morghan said:
i'm in the same boat, but when I go to flash another recovery in fastboot my phone freezes after it fails to flash.
sending 'recovery' (9786 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.016s
Then my phone freezes and I have to reboot into bootloader.
Click to expand...
Click to collapse
I had to run RUU to fix mine
So, I was BROWSING REDDIT, and an app starts downloading in the background. Which somehow caused google play services to crash, along with everything running on my phone. Then bootloop. Completely unprompted. Still at a loss here.
My nexus 6 is unlocked, no custom kernel or xposed installed, just running AOSiP 3.3 android 6.0.1. havent flashed anything other than that, which i flashed more than a month ago.
So, my troubleshooting thus far.
./fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.002s
device still says UNLOCKED STATUS CODE 3
next i tried:
./fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (12004 KB)...
OKAY [ 0.378s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.382s
and lastly, I tried:
./fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8196 KB)...
OKAY [ 0.259s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.264s
So, i'm kinda at a loss here. Recovery is failing to mount to storage, etc. Again, I was BROWSING REDDIT and this happened. I'd like to save my data at all costs. if anyone has any ideas, please, I am desperate. thank you.
Sorry but why open a new thread on the same issue? Did you think you would get a different answer than what you were getting in your original thread?
alryder said:
Sorry but why open a new thread on the same issue? Did you think you would get a different answer than what you were getting in your original thread?
Click to expand...
Click to collapse
to condense, summarize and make clear what i have already tried, and to seek further troubleshooting to my issue. there must be someone with an idea of how to fix this. if not, does it really hurt the forum? i am a person with a problem, seeking advice.
While I agree it's good to summarize the issue and layout what you've tried to resolve it, it could have been done as a post in your original thread to avoid the clutter of having two threads about the same issue. I also think you got the correct answer in the original thread that, however it happened, your bootloader has somehow became locked and in all likelihood the device is beyond repair. Sorry to say so but that's the way I see it.
alryder said:
While I agree it's good to summarize the issue and layout what you've tried to resolve it, it could have been done as a post in your original thread to avoid the clutter of having two threads about the same issue. I also think you got the correct answer in the original thread that, however it happened, your bootloader has somehow became locked and in all likelihood the device is beyond repair. Sorry to say so but that's the way I see it.
Click to expand...
Click to collapse
how is that even possible?
I'm super curious on what downloaded in the background...
Sent from my Nexus 6 using Tapatalk
MrBlob69 said:
I'm super curious on what downloaded in the background...
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
automatic update of some sort. it crashed my phone as soon as it was finished updating. didnt know a background app update could relock my bootloader and brick my phone. not sure why some are suggesting the bootloader is locked when it still displays status code 3 device is unlocked.
Post a screenshot of the bootloader screen
Sent from my Nexus 6 using XDA Free mobile app
The only thing that I can think of is you could try formatting /system and /boot separately and then try again flashing the system and boot images???
Sent from my Nexus 6 using Tapatalk
MrBlob69 said:
The only thing that I can think of is you could try formatting /system and /boot separately and then try again flashing the system and boot images???
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This won't work as if the bootloader is locked, you cannot wipe/flash img files to the phone.
To answer your question OP, we can't tell you how this happened, or what the download was that happened in the background, we simply weren't there and don't know what you have installed to your phone. This line indicates that "Allow OEM Unlocking" is not enabled in Developer Options:
Code:
(bootloader) [B]Check 'Allow OEM Unlock' in Developer Options.[/B]
FAILED (remote failure)
finished. total time: 0.002s
With that not enabled, you cannot issue:
Code:
fastboot oem unlock
You also cannot flash factory images to the device, or wipe the device either. I'm afraid that this device is bricked since it appears your bootloader is locked.
scottshebs said:
So, I was BROWSING REDDIT, and an app starts downloading in the background. Which somehow caused google play services to crash, along with everything running on my phone. Then bootloop. Completely unprompted. Still at a loss here.
My nexus 6 is unlocked, no custom kernel or xposed installed, just running AOSiP 3.3 android 6.0.1. havent flashed anything other than that, which i flashed more than a month ago.
So, my troubleshooting thus far.
./fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.002s
device still says UNLOCKED STATUS CODE 3
next i tried:
./fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (12004 KB)...
OKAY [ 0.378s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.382s
and lastly, I tried:
./fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8196 KB)...
OKAY [ 0.259s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.264s
So, i'm kinda at a loss here. Recovery is failing to mount to storage, etc. Again, I was BROWSING REDDIT and this happened. I'd like to save my data at all costs. if anyone has any ideas, please, I am desperate. thank you.
Click to expand...
Click to collapse
i guess all the time i devoted to you yesterday means absolutely nothing to you, and you learned nothing.. thanks
RMarkwald said:
This won't work as if the bootloader is locked, you cannot wipe/flash img files to the phone.
To answer your question OP, we can't tell you how this happened, or what the download was that happened in the background, we simply weren't there and don't know what you have installed to your phone. This line indicates that "Allow OEM Unlocking" is not enabled in Developer Options:
Code:
(bootloader) [B]Check 'Allow OEM Unlock' in Developer Options.[/B]
FAILED (remote failure)
finished. total time: 0.002s
With that not enabled, you cannot issue:
Code:
fastboot oem unlock
You also cannot flash factory images to the device, or wipe the device either. I'm afraid that this device is bricked since it appears your bootloader is locked.
Click to expand...
Click to collapse
forgive me, but how can the phones bootloader lock itself? this is the fastboot screen still saying code 3 unlocked. sorry if i am stubborn, just refusing to believe my 300 dollar device bricked itsself while i literally did nothing. never seen anything like this.
31ken31 said:
Post a screenshot of the bootloader screen
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
just posted, still status code 3.
Thread closed.
Not sure why the OP started 2 similar threads (like THIS) and ignored the help provided already....
i have MM updated already on my G4. i am trying to get CM13 installed as i am tired of the bloatware and whatnot. anyway i got fastboot connected, and unlocked the bootloader. but when i tried to install TWRP i get an error.
sending 'recovery' (33448 KB)...
OKAY [ 0.750s]
writing 'recovery'...
FAILED (remote: unknown command)
i have tried v3.0.0.0 and v2.8.7.0
i am at a loss. not super comfortable with fastboot, as i have mainly dealt with samsung and most of the time ODIN is all you need. have dont kindle fire HD with fastboot and nexus 5 & 7 but had no errors arise so i dont know how to troubleshoot it.
diptenkrom said:
i have MM updated already on my G4. i am trying to get CM13 installed as i am tired of the bloatware and whatnot. anyway i got fastboot connected, and unlocked the bootloader. but when i tried to install TWRP i get an error.
sending 'recovery' (33448 KB)...
OKAY [ 0.750s]
writing 'recovery'...
FAILED (remote: unknown command)
i have tried v3.0.0.0 and v2.8.7.0
i am at a loss. not super comfortable with fastboot, as i have mainly dealt with samsung and most of the time ODIN is all you need. have dont kindle fire HD with fastboot and nexus 5 & 7 but had no errors arise so i dont know how to troubleshoot it.
Click to expand...
Click to collapse
twrp 2.8.7.1-h811.img i put it on desktop then dragged and dropped into cmd window, didnt take first time but second time it did.have it on sd crd to flash for perm as per auto primes instructiuns.good luck
buckless said:
twrp 2.8.7.1-h811.img i put it on desktop then dragged and dropped into cmd window, didnt take first time but second time it did.have it on sd crd to flash for perm as per auto primes instructiuns.good luck
Click to expand...
Click to collapse
Thanks!
also are you on windows? im on Win 10 x64 if that matters.
can you link me to those instructions because i haven't been able to find any detailed instructions other than whats on CM instruction page?
diptenkrom said:
Thanks!
also are you on windows? im on Win 10 x64 if that matters.
can you link me to those instructions because i haven't been able to find any detailed instructions other than whats on CM instruction page?
Click to expand...
Click to collapse
yes i am on windows 10 also, just look for autoprimes thread in the development section it has all the info and links
buckless said:
yes i am on windows 10 also, just look for autoprimes thread in the development section it has all the info and links
Click to expand...
Click to collapse
thank you man!
I got it to work with those instructions. Thanks again so much.