[Tutorial][Rescue]Sprint HTC One users that flash GSM roms on their CDMA devices.

Did this Guide help you save your phone?

  • Yes

    Votes: 53 84.1%
  • No

    Votes: 10 15.9%

  • Total voters
    63

bwright4

Member
Apr 10, 2010
27
6
0
If you use the folder attached in post 1
open the folder and press shift and right click in an empty area and choose open cmd here :D
Everytime I try to start the process in the cmd window i get this:

C:\Users\Brandon\Desktop\Htc fix>fastboot oem lock
'fastboot' is not recognized as an internal or external command,
operable program or batch file.

and also my phone is being recognized as cd drive (F:) but it's named android phone.
 
Last edited:

Sloth

Recognized Contributor / Retired Forum Moderator
Apr 23, 2012
10,699
11,295
0
Xda-Dev,NV
Everytime I try to start the process in the cmd window i get this:

C:\Users\Brandon\Desktop\Htc fix>fastboot oem lock
'fastboot' is not recognized as an internal or external command,
operable program or batch file.

and also my phone is being recognized as cd drive (F:) but it's named android phone.
Sounds like you are not running the command from the proper folder.
Are you using the folder attached in post 1? If so did you unzip it?
 

varunrs

Senior Member
Dec 4, 2009
420
5
0
I ran into the same "offline" problem last night with someone else I have been searching for a solution.
I found this but have yet to try it. https://groups.google.com/forum/#!topic/android-developers/bYHeMm0qf2g
If you try please report back if it works :D
I read and thought the solution seems logical, I can't get into the adb shell because adb is not working. I am not new to this but I haven't used adb and command prompt extensively.

Edit - Problem solved. Needed to update adb to latest 1.0.31. The RSA verification is now required and the adb that came with hasoon's toolkit and the one you posted in OP are both 1.0.26 which will not work with 4.3. That's it for me. Now I need to see if I can root this thing.
 
Last edited:

varunrs

Senior Member
Dec 4, 2009
420
5
0
So I followed all the instructions again and I was able to achieve S-off. Can I now downgrade back to 1.29 RUU and root that.
 

Sloth

Recognized Contributor / Retired Forum Moderator
Apr 23, 2012
10,699
11,295
0
Xda-Dev,NV
I read and thought the solution seems logical, I can't get into the adb shell because adb is not working. I am not new to this but I haven't used adb and command prompt extensively.

Edit - Problem solved. Needed to update adb to latest 1.0.31. The RSA verification is now required and the adb that came with hasoon's toolkit and the one you posted in OP are both 1.0.26 which will not work with 4.3. That's it for me. Now I need to see if I can root this thing.
I just updated my Android-Sdk to the latest and put together a new folder attached at the bottom of post 1
So hopefully everything will be good now :D
 
Last edited:

ficeball

Senior Member
Jul 3, 2012
259
42
0
Cimahi
Hi again, thanks for the guide i can get it work nao :D

btw is it posible to remove "for testing purpose ... balblabla" message on startup?
i notice that its appear after i reflash a new ROM
 

Sloth

Recognized Contributor / Retired Forum Moderator
Apr 23, 2012
10,699
11,295
0
Xda-Dev,NV
  • Like
Reactions: ficeball

Nicelysedated

Senior Member
Dec 1, 2011
187
124
0
Yorktown
I have managed to bork my phone. Yay me!

Trying to flash the firmware I get into RUU mode fine and flash the the firmware file the first time, I get:

failed 90 hboot pre-update! please flush image again immediately

I push up and try again and it just hangs. It sits on:

Sending 'zip' (39722)kb...

forever. Any ideas?
 

Sloth

Recognized Contributor / Retired Forum Moderator
Apr 23, 2012
10,699
11,295
0
Xda-Dev,NV
I have managed to bork my phone. Yay me!

Trying to flash the firmware I get into RUU mode fine and flash the the firmware file the first time, I get:

failed 90 hboot pre-update! please flush image again immediately

I push up and try again and it just hangs. It sits on:

Sending 'zip' (39722)kb...

forever. Any ideas?
Yeah I ran into that also we had to change to a different PC
 

santi8903

New member
Nov 1, 2013
3
1
0
Thanks dude, you have helped me a lot cause I was stuck in a boot loop every 2 minutes and didn't know what to do until I saw this thread. Thanks a lot.
 
  • Like
Reactions: Sloth

coyote81

Member
Feb 13, 2010
38
2
0
Dixon
Ok, I am having same problems as the poster above, bootloop every two minutes. what I don't get is step 4? Is this something I type into the cmd promt? Also if I type anything under that, I get the waiting for device and nothing happens.
 

Boomchaos

Senior Member
Apr 2, 2011
171
136
0
My computer isn't recognizing my phone when it's in Fastboot mode. It should normally be going to Fastboot USB but it doesn't. I'm on a mac so driver issues shouldn't be the problem. Any ideas?

Also of note: Whenever the phone is powered down and is plugged into my computer, it boots up into fastboot mode without me turning it on.
 
Last edited:

Sloth

Recognized Contributor / Retired Forum Moderator
Apr 23, 2012
10,699
11,295
0
Xda-Dev,NV
My computer isn't recognizing my phone when it's in Fastboot mode. It should normally be going to Fastboot USB but it doesn't. I'm on a mac so driver issues shouldn't be the problem. Any ideas?

Also of note: Whenever the phone is powered down and is plugged into my computer, it boots up into fastboot mode without me turning it on.
Are you tapping power to select fastboot?