I should start off by saying that XDA does not have a subforum for the EVO Design, and because i'm new here, I didn't know where else to go. If there's a more appropriate place to post about the Evo Design, please point me to it.
Now on the my problem at hand. I get stuck around Step 11 in the guide on how to unlock your bootloader on the HTCdev site. Whenever I type in the command in the prompt, fastboot flash unlocktoken Unlock_code.bin, It just sits there looking like this:
c:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
I had followed all previous steps right prefectly, but for whatever reason it just decides to stop working at that point.
I have searched around a bit, but not to many other people had that problem, so I couldn't get any good answers. Thanks in advance if you can figure it out.
I'm using windows Vista if that helps.
64_hit_combo said:
I should start off by saying that XDA does not have a subforum for the EVO Design, and because i'm new here, I didn't know where else to go. If there's a more appropriate place to post about the Evo Design, please point me to it.
Now on the my problem at hand. I get stuck around Step 11 in the guide on how to unlock your bootloader on the HTCdev site. Whenever I type in the command in the prompt, fastboot flash unlocktoken Unlock_code.bin, It just sits there looking like this:
c:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
I had followed all previous steps right prefectly, but for whatever reason it just decides to stop working at that point.
I have searched around a bit, but not to many other people had that problem, so I couldn't get any good answers. Thanks in advance if you can figure it out.
I'm using windows Vista if that helps.
Click to expand...
Click to collapse
Did you reboot the phone into the bootloader? Power off the phone. You may have to pop out the battery and put it back in. Hold down the volume - button and press power. In the menu, navigate to the entry that says FASTBOOT. Plug in your USB cable, and the heading should now say FASTBOOT USB. Now try sending the unlocktoken to the phone.
~co~
closeone said:
Did you reboot the phone into the bootloader? Power off the phone. You may have to pop out the battery and put it back in. Hold down the volume - button and press power. In the menu, navigate to the entry that says FASTBOOT. Plug in your USB cable, and the heading should now say FASTBOOT USB. Now try sending the unlocktoken to the phone.
~co~
Click to expand...
Click to collapse
Yeah, fastboot, that's exactly what i chose.
64_hit_combo said:
Yeah, fastboot, that's exactly what i chose.
Click to expand...
Click to collapse
redo the whole procedure and when you get the token youll see the numbers and letters are different... try flashing the new one to the partition PM me soon if you have any questions or problems....
I've tried redoing it, and tried it on a different computer, but it's still not working.
At the beginning did you typ fastboot get identifiertoken
Sent from my HTC EVO 3D X515m using xda premium
jslim38 said:
At the beginning did you typ fastboot get identifiertoken
Sent from my HTC EVO 3D X515m using xda premium
Click to expand...
Click to collapse
Yes, i did. And pasted the token into space provided to get the unlock token.
64_hit_combo said:
I should start off by saying that XDA does not have a subforum for the EVO Design, and because i'm new here, I didn't know where else to go. If there's a more appropriate place to post about the Evo Design, please point me to it.
Now on the my problem at hand. I get stuck around Step 11 in the guide on how to unlock your bootloader on the HTCdev site. Whenever I type in the command in the prompt, fastboot flash unlocktoken Unlock_code.bin, It just sits there looking like this:
c:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
I had followed all previous steps right prefectly, but for whatever reason it just decides to stop working at that point.
I have searched around a bit, but not to many other people had that problem, so I couldn't get any good answers. Thanks in advance if you can figure it out.
I'm using windows Vista if that helps.
Click to expand...
Click to collapse
Don't know if you have solved your problem or not but I was having the same issue and my problem was I wasn't using the usb cable that came with my phone. Hope this helps someone.
Is it recognized in fastboot.
Can you type fastboot reboot-bootloader and does it work?
If not, my guess is your phone drivers aren't installed for adb to communicate.
Sent from my HTC EVO 3D X515m using Tapatalk 2
re
hi, i have the same probleme
Do you have HTC sync installed on your computer? If so uninstall it. Sync will interfere with fastboot writing. I'm not sure if this helps but also check mark the USB debugging box in your settings before you boot your phone into fastboot.
nano3000 said:
hi, i have the same probleme
Click to expand...
Click to collapse
This is a known problem with the HTC unlock process and is resolved by flashing a current RUU.exe for your phone, then flashing the unlock token again.
ramjet73
Hello.
I just got a Desire S my friend gave me to unlock and root, and I'm having the same problem. I did everything step-by-step in the HTCdev guide, and it's also stuck at "sending 'unlocktoken' (0 KB)...". Fastboot does recognize my device and ADB pushing/pulling works.
S-ON HBoot-2.02.0002
Stock Desire S EU ICS RUU.
USB debugging is enabled, but I don't think those settings would affect fastboot/bootloader.
Same problem here. Been trying to unlock my friend's EVO Design 4G from Sprint and I get stuck at the exact same spot. Maybe it has something to do with the HBoot that got installed with the latest update. Mine is showing HBoot 1.30.0000. This is just a guess though.
problem solved
you must add one more file to the android folder then type in the command again. The file is: AdbWinUsbApi.dll. Htc dev does not say to add this but you must.
koolmanhayes said:
you must add one more file to the android folder then type in the command again. The file is: AdbWinUsbApi.dll. Htc dev does not say to add this but you must.
Click to expand...
Click to collapse
I looked that up and found that is only required if you are using the generic Microsoft WinUSB driver with ADB. The HTC USB drivers installed separately or as part of the HTC Sync application use a driver called androidusb.sys. As long as the HTC drivers are installed and operational that file shouldn't be necessary for the htcdev unlock, which is probably why they didn't include it in the requirements for step 5 of the unlock procedure.
Here's a more detailed explanation:
/** \brief Function prototype for InstantiateWinUsbInterface routine exported
from AdbWinUsbApi.dll
In order to provide backward compatibility with the systems that still run
legacy (custom) USB drivers, and have not installed WINUSB.DLL we need to
split functionality of our ADB API on Windows between two DLLs: AdbWinApi,
and AdbWinUsbApi. AdbWinApi is fully capable of working on top of the legacy
driver, but has no traces to WinUsb. AdbWinUsbApi is capable of working on
top of WinUsb API. We are forced to do this split, because we can have
dependency on WINUSB.DLL in the DLL that implements legacy API. The problem
is that customers may have a legacy driver that they don't want to upgrade
to WinUsb, so they may not have WINUSB.DLL installed on their machines, but
they still must be able to use ADB. So, the idea behind the split is as
such. When AdbWinApi.dll is loaded into a process, it will check WINUSB.DLL
installation (by checking existance of C:\Windows\System32\winusb.dll). If
WINUSB.DLL is installed, AdbWinApi will also load AdbWinUsbApi.dll (by
calling LoadLibrary), and will extract address of InstantiateWinUsbInterface
routine exported from AdbWinUsbApi.dll. Then this routine will be used to
instantiate AdbInterfaceObject instance on condition that it is confirmed
that USB driver underneath us is in deed WinUsb.
*/
Click to expand...
Click to collapse
ramjet73
I tried adding that extra file and it didn't work. I'm still stuck at the same screen as the original post. Ramjet73 you mentioned flashing a current RUU.exe, but is that possible with a locked bootloader? Did you have this exact problem previously? If so, where can I get a current RUU for the Sprint Design 4g?
Qoolcat said:
I tried adding that extra file and it didn't work. I'm still stuck at the same screen as the original post. Ramjet73 you mentioned flashing a current RUU.exe, but is that possible with a locked bootloader? Did you have this exact problem previously? If so, where can I get a current RUU for the Sprint Design 4g?
Click to expand...
Click to collapse
Flashing an RUU.exe from Windows requires a locked bootloader.
The Evo Design 4G (kingdom) RUU's are here.
I couldn't seem to find an ICS RUU for the Sprint version if it is different than the Boost version. Maybe someone else can help with that. If you can't find a Sprint ICS RUU you could flash the GB version, HTC unlock, then do the OTA upgrade to ICS.
I haven't experienced this problem myself when I unlocked two phones with the Sprint GB 2.17.651.5 build installed, but I had just flashed the RUU.exe before doing that. Several people have reported problems with the unlock if they updated via the OTA instead of the RUU.
ramjet73
64_hit_combo said:
I should start off by saying that XDA does not have a subforum for the EVO Design, and because i'm new here, I didn't know where else to go. If there's a more appropriate place to post about the Evo Design, please point me to it.
Now on the my problem at hand. I get stuck around Step 11 in the guide on how to unlock your bootloader on the HTCdev site. Whenever I type in the command in the prompt, fastboot flash unlocktoken Unlock_code.bin, It just sits there looking like this:
c:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
I had followed all previous steps right prefectly, but for whatever reason it just decides to stop working at that point.
I have searched around a bit, but not to many other people had that problem, so I couldn't get any good answers. Thanks in advance if you can figure it out.
I'm using windows Vista if that helps.
Click to expand...
Click to collapse
I ran into this problem when unlocking my EVO 4G LTE. It was caused by using an old version of the fastboot.exe
If you download the new one from the HTC website in step 5 or the unlock process, it will give you a different identifier token and the process should work smoothly from there.
I hope that helps.
Related
Hey Guys,
I have been waiting for this day, and now that its here, I'm stuck. I did everything the HTCDev instructions said, got my Unlock.bin but when I go to flash it, it hangs at:
C:\>fastboot flash unlocktoken C:\Unlock_code.bin
sending 'unlocktoken' (0 KB)...
I have searched everywhere for a solution and have tried everything, I now have a phone thats empty and has the latest RUU. I have tried every port on my laptop and my desktop, nothing works. Can anyone help me with this? Should I contact VZW and try and get a replacement? I'm pulling my hair out trying to get this to work.
Thanks
Wouldn't the command be?
Code:
fastboot flash unlock_code.bin
You need to type the filename exactly as it appears or it will not work.
nope, I followed the directions on the HTC site, and they are the same as all the posted guides. It has to be my token, is it possible I have a bad token or phone? Should I contact HTC to see if they will replace it?
You have to put the unlock_code.bin in the same folder as the ADB and fastboot executables.
Then you can leave out the path in the command. You don't need to use the full path, just
Code:
fastboot flash unlocktoken Unlock_code.bin
EDIT: Clearly you didn't follow the instructions by the way, otherwise you would have created an Android folder on your C:\ drive and would have known to put all the files in that directory. No worries, just do as I said and you should be good
It is in the same folder as it, I have tried it in the platfor-tools folder, in its own folder at C:\android and i have tried it on the root of c:\. I just tried it on a 3rd computer i have and same deal. It has to be my token.
icy1899 said:
It is in the same folder as it, I have tried it in the platfor-tools folder, in its own folder at C:\android and i have tried it on the root of c:\. I just tried it on a 3rd computer i have and same deal. It has to be my token.
Click to expand...
Click to collapse
Interesting. USB Debug enabled? Charge only mode?
icy1899 said:
It is in the same folder as it, I have tried it in the platfor-tools folder, in its own folder at C:\android and i have tried it on the root of c:\. I just tried it on a 3rd computer i have and same deal. It has to be my token.
Click to expand...
Click to collapse
I don't know but to be honest I just cannot see how it could be the token.
BTW...the .bin file needs to be in the same folder/location as the fastboot.exe file which would be under the "Tools" folder not the "Platform-tools".
I was in fastboot mode in the "recovery" screen. I will boot up and try running it then.
EDIT: Still no dice. This is killing me.....
I hate to tell you, but it's on your end. Other people would be posting with the same issue if it were HTC Dev's issue.
Anyway, all I can say is follow the instructions EXACTLY and start from step one.
icy1899 said:
Hey Guys,
I have been waiting for this day, and now that its here, I'm stuck. I did everything the HTCDev instructions said, got my Unlock.bin but when I go to flash it, it hangs at:
C:\>fastboot flash unlocktoken C:\Unlock_code.bin
sending 'unlocktoken' (0 KB)...
I have searched everywhere for a solution and have tried everything, I now have a phone thats empty and has the latest RUU. I have tried every port on my laptop and my desktop, nothing works. Can anyone help me with this? Should I contact VZW and try and get a replacement? I'm pulling my hair out trying to get this to work.
Thanks
Click to expand...
Click to collapse
This is how/why bootloaders get locked...
Your best bet is to post step by step what you've done so we can figure out what you're not doing right.
Sent from my newly unlocked Rezound.. Thank you HTC.
I have followed every step of every walkthru on this forum and others, as well as the HTCDev instructions. I have done it on all 3 computers (all Win7 Pro legit) trying every usb port with every method. I have also tried different USB cables. I have had my girlfriend watching my every keystroke to accuracy (she also has a rezound, but is waiting on a replacement device ,screen cracked). I have tried putting the files in:
C:\
C:\Android
C:\Program Files\Android\androidsdk\platform-tools\
D:\
S:\ a network drive (didnt expect this to work)
F:\ a flash drive
I just got off the phone with HTC support and they think it is strange as well, they escalated my issue so I should get a call from someone who actually knows what fastboot is.
I am going to try a LiveUSB copy of Ubuntu 11.10. I will let you know of any progress.
Why would vzw replace a phone you screwed up trying to root it.
Sent from my Galaxy Tab 10.1
jbh00jh said:
Why would vzw replace a phone you screwed up trying to root it.
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
I didn't screw it up trying to root. The phone works fine, the issue is that the HTC provided system will not work for my phone. Vzw should replace it only if HTC escalation team cant get to the bottom of it. They should replace it because there is a manufacturing error on the device.
Sent from my Kindle Fire using Tapatalk
The instruction page at htc/dev unlock says if you use the unlock you void your warranty if your software is altered from stock.
From what i understand, its not unlocked yet, thats y they can still help
jbh00jh said:
The instruction page at htc/dev unlock says if you use the unlock you void your warranty if your software is altered from stock.
Click to expand...
Click to collapse
Sent from my ADR6425LVW using XDA App
dragonrazorz said:
From what i understand, its not unlocked yet, thats y they can still help
Click to expand...
Click to collapse
Exactly.
jbh00jh said:
The instruction page at htc/dev unlock says if you use the unlock you void your warranty if your software is altered from stock.
Click to expand...
Click to collapse
The HTCDev website says "I acknowledge that use of the unlock bootloader may void all or parts of my warranty device and my device may not function as intended by HTC."
You can see this here http://www.htcdev.com/process/legal
Also I just tried the entire process again using a Linux machine and a different HTCDev account sending to a non gmail address, same thing. It has to be a device issue.
Sent from my Kindle Fire using Tapatalk
Well I hope someone can fix his phone, I'm sure he needs it.
Sent from my Galaxy Tab 10.1
Are you sure that you're correctly in fastboot when trying to run the unlock bin? You need to pull the battery, power on with Vol Down + Power, it should bring you to the hboot. There will be a menu with options (fastboot, recovery, reboot, a couple others) that you can scroll through. Highlight fastboot (I believe it's the top one and highlighted by default) and press power. This should change the menu options shown at the bottom. If I remember correctly, the picture during the HTC dev walkthrough is a picture taken while in fastboot. You need to run the unlock fastboot command while on that menu screen.
Phone: Evo 3D
Android Version: 2.3.4
Software number: 2..08.651.3
Hboot: 1.50
S-On
Done:
1) HTC boot unlock (http://htcdev.com/bootloader)
2) http://forum.xda-developers.com/showthread.php?t=1239821
-was able to push flies over to phone, but command line "fastboot flash recovery recovery.img" resulted in errors
3) tried to downgrade Hboot using RUU and got an error telling me that my current version was most up to date
Common Threads:
1) http://forum.xda-developers.com/showthread.php?t=1388740
-I downloaded Superuser, titanium back up, and a random program that claimed to verify rooting -- all said I was NOT rooted
2) http://forum.xda-developers.com/showthread.php?t=1307982
-My true goal is to install wifi teathering and titanium backup, I don't care much for custom roms
Forum Confusion:
Unlocking the boot loader does not seem to be the same as rooting, but when I've search through the forums people offer one as a solution to the other.
I'd really appreciate any feedback
thanks guys,
-Nave
navenine said:
Phone: Evo 3D
Android Version: 2.3.4
Software number: 2..08.651.3
Hboot: 1.50
S-On
Done:
1) HTC boot unlock (http://htcdev.com/bootloader)
2) http://forum.xda-developers.com/showthread.php?t=1239821
-was able to push flies over to phone, but command line "fastboot flash recovery recovery.img" resulted in errors
3) tried to downgrade Hboot using RUU and got an error telling me that my current version was most up to date
Common Threads:
1) http://forum.xda-developers.com/showthread.php?t=1388740
-I downloaded Superuser, titanium back up, and a random program that claimed to verify rooting -- all said I was NOT rooted
2) http://forum.xda-developers.com/showthread.php?t=1307982
-My true goal is to install wifi teathering and titanium backup, I don't care much for custom roms
Forum Confusion:
Unlocking the boot loader does not seem to be the same as rooting, but when I've search through the forums people offer one as a solution to the other.
I'd really appreciate any feedback
thanks guys,
-Nave
Click to expand...
Click to collapse
Try this, starting over. You shouldnt run into any hiccups.
tailsthecat3 said:
Try this, starting over. You shouldnt run into any hiccups.
Click to expand...
Click to collapse
I received Error [155] Unknown Error
Display From Phone:
***Unlocked***
Shooter XC ship S-ON RL
HBoot-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
RUU
Security fail!
Update Fail!
when it rebooted after recovery I still had all of my user data
navenine said:
I received Error [155] Unknown Error
Display From Phone:
***Unlocked***
Shooter XC ship S-ON RL
HBoot-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
RUU
Security fail!
Update Fail!
when it rebooted after recovery I still had all of my user data
Click to expand...
Click to collapse
Ive been through this. Relock(lock) it, run the RUU, then proceed with the instructions I linked.
I was never able to run the RUU while the device was 'unlocked'.
tailsthecat3 said:
Ive been through this. Relock(lock) it, run the RUU, then proceed with the instructions I linked.
I was never able to run the RUU while the device was 'unlocked'.
Click to expand...
Click to collapse
I've been trying to lock it back through the CMD, I wrote a little batch file (and I've manually typed it):
cd c:\android
fastboot oem lock
but after it runs a line shows up as follows:
< waiting for device >
I have USB debugging mode on, and I've tried it with the sd card both mounted and unmounted, I have all the drivers, and adb commands are effective...
do you know what I'm missing?
Thanks again for the help,
-Evan
hey im trying to use the ruu to get back to stock , just re locked the phone , and im STILL getting errors with ruu, its saying Update Failed : Hboot version is older , im on hboot 1.5000 .........Im losing my mind trying to get this thing back to stock and out of htc screen logo bootlooping.........any ideas?
navenine said:
I've been trying to lock it back through the CMD, I wrote a little batch file (and I've manually typed it):
cd c:\android
fastboot oem lock
but after it runs a line shows up as follows:
< waiting for device >
I have USB debugging mode on, and I've tried it with the sd card both mounted and unmounted, I have all the drivers, and adb commands are effective...
do you know what I'm missing?
Thanks again for the help,
-Evan
Click to expand...
Click to collapse
That tells me that youre not in fastboot on your device. I can dupe the same message with my phone disconnected from the pc, then I plug it in in fastboot, and all is good.
Please reinstall the drivers needed but it sounds like youre good. On occasion, I wont be able to flash some things or a file cant load. A reboot of the pc fixes those rare cases for me. Also, refreshing the folders where the files are located.
I also had issues using fastboot, flashing things to the evo because I had my nexus connected for a tether.
If I could do it for you, I would. Hopefully I can help.
tailsthecat3 said:
That tells me that youre not in fastboot on your device. I can dupe the same message with my phone disconnected from the pc, then I plug it in in fastboot, and all is good.
Please reinstall the drivers needed but it sounds like youre good. On occasion, I wont be able to flash some things or a file cant load. A reboot of the pc fixes those rare cases for me. Also, refreshing the folders where the files are located.
I also had issues using fastboot, flashing things to the evo because I had my nexus connected for a tether.
If I could do it for you, I would. Hopefully I can help.
Click to expand...
Click to collapse
this just got even worse, I uninstalled the drivers, and now I can't reinstall them. I can't find them. My computer wont recognize my phone at all. I've tried to goto the device manager and find them online automatically, and I've tried the google USB drivers from the extra folder from the SDK Manager...
if you can point me toward the USB drivers that'd be great, but regardless, what your saying is I need to connect my phone while its in the bootloader? not once its booted? or are you saying I need to boot my phone through the bootloader selecting "fastboot" first?
thanks again
-Nave
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
tailsthecat3 said:
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
Great, I have all the drivers, my phone is relocked, and I'm running the RUU prog now, I'll post in a few minutes to say what happens
thanks for all the help so far, I really do appreciate it!
-Nave
navenine said:
Great, I have all the drivers, my phone is relocked, and I'm running the RUU prog now, I'll post in a few minutes to say what happens
thanks for all the help so far, I really do appreciate it!
-Nave
Click to expand...
Click to collapse
Good. Ive done the process on two different 3D's, a few times. If you follow the instructions, its almost as easy to root as my nexus s was.
tailsthecat3 said:
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
I pushed everything over, got it into the fastboot USB and then typed the "fastboot flash recovery recovery.img" command line
my script was:
sending 'recovery' <5068 KB>...
Okay [ 1.207s]
writing 'recovery'...
<bootloader> signature checking...
FAILED <remote:signature verify fail>
finished. total time: 1.855s
any ideas?
tailsthecat3 said:
Good. Ive done the process on two different 3D's, a few times. If you follow the instructions, its almost as easy to root as my nexus s was.
Click to expand...
Click to collapse
Great! thank you soooo much I finally have everything working the way I want it!
haha it seems so much easier now that I know what I was supposed to do
navenine said:
Great! thank you soooo much I finally have everything working the way I want it!
haha it seems so much easier now that I know what I was supposed to do
Click to expand...
Click to collapse
Where were you going wrong? And what'd you do to correct it? So everyone knows, in case they encounter the same issues.
Sent from my Google Nexus S 4G via XDA Premium
Good Idea:
Problem 1)
The RUU wouldn't run
I had this problem because I had already unlocked the the bootloader
I had to re-lock it in order to fix it
Problem 2)
Then The Recovery.img would push through because I forgot to re-unlock the phone
what I did that made it easier:
I wrote a little batch file to run the scripts - a batch file is a command prompt command list set. you open a notepad, type in the the command lists and save it with a .bat file extension...
so I would install all the files and then make a batch file with the following:
cd C:\android
adb push recovery.img /sdcard/
adb push su-2.3.6.3.zip /sdcard/
adb reboot bootloader
pause
fastboot flash recovery recovery.img
change the C:\andriod to whatever your directory set was
and when the batch program runs
anyway good luck to anyone who ends up here, and thanks again tailsthecat3 for the great help
navenine said:
Good Idea:
Problem 1)
The RUU wouldn't run
I had this problem because I had already unlocked the the bootloader
I had to re-lock it in order to fix it
Problem 2)
Then The Recovery.img would push through because I forgot to re-unlock the phone
what I did that made it easier:
I wrote a little batch file to run the scripts - a batch file is a command prompt command list set. you open a notepad, type in the the command lists and save it with a .bat file extension...
so I would install all the files and then make a batch file with the following:
cd C:\android
adb push recovery.img /sdcard/
adb push su-2.3.6.3.zip /sdcard/
adb reboot bootloader
pause
fastboot flash recovery recovery.img
change the C:\andriod to whatever your directory set was
and when the batch program runs
anyway good luck to anyone who ends up here, and thanks again tailsthecat3 for the great help
Click to expand...
Click to collapse
I appreciate that, thank you.
[Solved!] Thanks.
So on step 12 of the website it says to type the below:
C:\>fastboot flash unlocktoken C:\Unlock_code.bin
I do so and I get the correct output that the site displays.
Which is:
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' <0 KB>...
OKAY [0.151s]
writing 'unlocktoken' ...
<bootloader> unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.158s
Step 13 reads:
"On your phone you will now see the disclaimer. Please read this carefully as this action may void your warranty"
However, I see no disclaimer appear on my phone. It stays on the fastloader hboot screen.
What's going on? Do I have to be not in the recovery fastloader screen and do that command when the normal os is showing? Or what?
Thanks if you can help.
Locate and flash the latest stock Ruu (or current one installed) from football or Mr.esp's thread to clear the issue. You should id your current Rom/radio version in android settings (about phone ) first... Ie. 2.08.651.3 vs 2.17.651.5 and phone codename is "shooter" not shooteru .
http://forum.xda-developers.com/showthread.php?p=19089387
Then retry the unlock & it should work. Check development sticky thread.for link & instructions. If you look at jtniggles hboot unlock/flash thread it will mention this issue.
If your hboot 1.50 you may have issues with specific recoveries not loading. I'd recommend you grab Cwm touch 5.0.8.1 and a more current Su 3.0 file to flash. I have some examples of flashing these & other stuff after unlocking in my recovery issues thread (see signature). Htcevohacks.com has a good how to video also.
Sent from my "Up all night, sleep all day" Evo3D via Tapatalk.
i tried this method myself but when i run the ruu it just sits at sending.... and never gets past it. please help!
Saw you posted a separate RUU question, so hopefully you'll get a response there, but just to try and help a bit...
There is an RUU .exe Instructions Doc in the Sticky Thread that may help you.
Edit: its 1/2 way down my useful thread links post (in my signature).
- you should indicate in your questions what your phone setup is so people can better help you: Hboot version, Firmware/Radio version, HTC Unlocked/Locked/not rooted, S-ON vs S-Off, Custom Recovery you use, filenames/thread links you're using, etc if they apply to your situation.
did you enable "usb Debugging" under settings, applications?
Did you DL the RUU.exe or RUU PG86IMG.zip ?
What he said you need to run latest RUU I have walked a bunch of folks through that .... Worked everytime for them...
og92 said:
i tried this method myself but when i run the ruu it just sits at sending.... and never gets past it. please help!
Click to expand...
Click to collapse
Relock and then run RUU.
Sent in L*W*H
intrlude said:
Relock and then run RUU.
Sent in L*W*H
Click to expand...
Click to collapse
He sounds like he is tryin to root the first time and gets to the part were the phone splash screen is suppose to say do you wish to unlock bootloader....
Which he needs to just run the RUU and should be good to go..
Thanks a bunch guys! Flashing the latest RUU and redoing the process worked. However...how do you know the bootloader was unlocked afterall? I want to double check.
Edit: Sorry, just figured it out..just needed to do the reboot again and says unlocked on the top. Yay!
FYI, I added some RUU info to the other post:
Running stock RUU Reference info: http://forum.xda-developers.com/showpost.php?p=22190515&postcount=5
GamerC said:
So on step 12 of the website it says to type the below:
C:\>fastboot flash unlocktoken C:\Unlock_code.bin
I do so and I get the correct output that the site displays.
Which is:
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' <0 KB>...
OKAY [0.151s]
writing 'unlocktoken' ...
<bootloader> unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.158s
Step 13 reads:
"On your phone you will now see the disclaimer. Please read this carefully as this action may void your warranty"
However, I see no disclaimer appear on my phone. It stays on the fastloader hboot screen.
What's going on? Do I have to be not in the recovery fastloader screen and do that command when the normal os is showing? Or what?
Thanks if you can help.
Click to expand...
Click to collapse
The first suspect thing to me here is that file says that its 0 kb, try to download again that file but maybe disable the AV to avoid getting it corrupted or stripped.
Sent from my PG86100 using Tapatalk
So, I'm having some major issues here. I'm on HBoot 1.5, with software 2.17.xxx.xxx(the newest update) and when I'm using the unlock token "flash unlock token" I get this.
Code:
C:\root>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (remote: loading custom splash failed)
finished. total time: 0.001s
The RUU doesn't work for my phone, either. (It's already on the newest software, and the RUU says the USB disconnects before it finishes)
The live CD tool asks me "hold volume down and plug in the phone" and I tried everything for that part, opening fastboot, going into fastboot usb, everything for that and it doesn't detect my phone.
I've also reset the phone to factory, which is where it is now, and before I tried all this.
Is there something I'm doing wrong? If so, what is it?
Are you tryin to downgrade to s off or you going htc dev method ?
Sent from my PG86100 using xda premium
He needs to stick with one thread or the other. I asked the same.thing:
mpgrimm2 said:
Overall I'm confused about a few things.
What is your detailed hw & sw versions:
- hboot:
- locked/unlocked:
- s-on/s-off:
- Fw: 2.17.651.5 etc?
- Radio:
What do u actually want... HTC Unlock or hboot downgrade with s-off?
U said u tried everything, but didn't link any threads or files that u used, so we can't be sure what u actually did.
(havent seen u post in any of the xda threads u should be following. I coulda missed it. U did say ur post count was low).
U didn't indicate if u read the hboot 1.50 guide in my signature.
Click to expand...
Click to collapse
Sent from my PG86100 using Tapatalk
Install the drivers..
I'm not quite sure what you are asking for, but if your computer isn't detecting your phone, then you need to install the ADB and Fastboot drivers. Do you have android SDK installed? or just simply Google "how to install ADB and Fastboot drivers"
I know this might seem similar to other post but i haven't found anything that has my exact problem.
I unlocked my boot loader HBOOT 1.5 S=ON and the phone seemed to be working fine until the new update for Android was released.
My phone will download the update but when i hit ok to install the phone restarts and sits at a white triangle with a yellow ! and a blue android guy.
I followed this video to unlock my phone:
"htcevohacks.com/htc-evo-3d-hacks/how-to-root-htc-evo-3d-gsm/"
can u enter in bootloader??
power down phone then press n hold the volume up and power button for a couple of seconds
Dadovvv said:
can u enter in bootloader??
power down phone then press n hold the volume up and power button for a couple of seconds
Click to expand...
Click to collapse
Yes i can enter into my bootloader and i have to custom recovery installed that was shown in the video i posted the link to.
Whats your hboot version now? 1.53?
Dadovvv said:
Whats your hboot version now? 1.53?
Click to expand...
Click to collapse
1.50.0000
LOL
---------- Post added at 10:07 AM ---------- Previous post was at 10:02 AM ----------
u have gsm or cdma?
Dadovvv said:
LOL
Click to expand...
Click to collapse
"lol" what?
jb14813 said:
"lol" what?
Click to expand...
Click to collapse
I honestly am not sure its US Sprint. and i dont have a sim card at least that i can get to.
You shouldn't take an update of you are unlocked. Have you tried to install a custom Rom since you have your custom recovery?
Read, Search, Read again, ... Then Ask with Tapatalk 2
coal686 said:
You shouldn't take an update of you are unlocked. Have you tried to install a custom Rom since you have your custom recovery?
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
I havent found good instructions on how to update to a new rom and i still have s-on.. Is there any roms of icecream that work 100% and good instructions that you can point me too.
jb14813 said:
I havent found good instructions on how to update to a new rom and i still have s-on.. Is there any roms of icecream that work 100% and good instructions that you can point me too.
Click to expand...
Click to collapse
Download the android sdk, and flash a custom recovery (I can walk you through it) then run a few fastboot commands and then flash a new rom. I recommend either homebrew, common sense, or any other ics rom with hboot 1.50 compatibility, just search the development forums
Again, I can walk you through this step by step if you want. I've had my time with s-on forever.
Sent from my EVO 3DMA with a little "Common Sense"
or you could just downgrade your hboot, get S-OFF and do as you please?
CDMA downgrade:
http://forum.xda-developers.com/showthread.php?t=1563342
beneath-a-burning-turtle said:
Download the android sdk, and flash a custom recovery (I can walk you through it) then run a few fastboot commands and then flash a new rom. I recommend either homebrew, common sense, or any other ics rom with hboot 1.50 compatibility, just search the development forums
Again, I can walk you through this step by step if you want. I've had my time with s-on forever.
Sent from my EVO 3DMA with a little "Common Sense"
Click to expand...
Click to collapse
That would be very helpful and id rather stick to the safest way of getting the new version of Android as this is my only phone and i dont have the money to replace it if i turn it into an expensive paper weight. Also i have a custom recovery installed the one from the video i first mentioned in this post. I will look into the roms but are there any that you can suggests specificly for my device
You could try running the stock ruu.exe to go back to stock you would have to relock your phone to do so personally I just done the wire trick to gain s off its simple to do plus takes less time that the downgrade method running stock ruu never worked for me but has for other people so I would recommend doing the wire trick and gaining s off wish you luck
Sent from my PG86100 using xda app-developers app
jb14813 said:
That would be very helpful and id rather stick to the safest way of getting the new version of Android as this is my only phone and i dont have the money to replace it if i turn it into an expensive paper weight. Also i have a custom recovery installed the one from the video i first mentioned in this post. I will look into the roms but are there any that you can suggests specificly for my device
Click to expand...
Click to collapse
Alright, so this is what you need to do:
1. Download the android SDK from htcdev.com. It contains fastboot and adb which are essential. Without them you won't be able to reboot into recovery right.
2. I don't remember if you said you were unlocked or not, so if not, unlock through the HTCDev method (htcdev.com -> unlock bootloader)
4. Now make sure you're in the bootloader, and then click on fastboot, because this is where the fastboot commands will be run. Keep it plugged into the computer as well.
3. Take your custom recovery and place it in the same folder as adb and fastboot.
4. Open the command prompt on your computer and type in "cd c:\[directory with fastboot and adb]" (minus the quotes)
5. Once you're in that directory, type "fastboot flash recovery recovery.img" (minus the quotes) ***if your recovery isn't named recovery.img, change it to that, makes it easier***
6.Once it finishes that, type in "fastboot boot recovery.img" (minus the quotes)
7. Now you're successfully in recovery!
8. Because I'm completely biased beyond belief lmfao, I would recommend my rom (link is in the signature), or powduh09's rom, homebrew. Both roms are excellent, powduh did a fantastic job with his. Both of these will work with no issues with your firmware, I promise
9. Once you've downloaded one, place on your sdcard and flash!
10. Reboot and enjoy ice cream sandwich
Sent from my EVO 3DMA with a little "Common Sense"
I installed your rom but its just sitting at HTC screen has been for like 20 mins
jb14813 said:
I installed your rom but its just sitting at HTC screen has been for like 20 mins
Click to expand...
Click to collapse
Then you might have to extract the boot.img to the fastboot directory, cd c:/(fastboot directory) from cmd and type in "fastboot flash boot boot.img" while in the BOOTLOADER, not recovery
Sent from my EVO 3DMA with a little "Common Sense"
beneath-a-burning-turtle said:
Then you might have to extract the boot.img to the fastboot directory, cd c:/(fastboot directory) from cmd and type in "fastboot flash boot boot.img" while in the BOOTLOADER, not recovery
Sent from my EVO 3DMA with a little "Common Sense"
Click to expand...
Click to collapse
what boot.img i used the install .zip from sdcard in recovery and it ran through your installer and everything went ok
I extracted the boot.img from the zip like im thinking you said lol
it booted past the htc now i have like a wave of triangles lol im not sure if this is the new boot screen i think you had listed or if my phone is has entered the twilight zone.
It booted past that screen and i had seen the home menu for a few seconds then it just reboots...
C:\rootevo3dnew>fastboot flash boot boot.img
sending 'boot' (3756 KB)...
OKAY [ 0.990s]
writing 'boot'...
OKAY [ 1.192s]
finished. total time: 2.182s
jb14813 said:
I extracted the boot.img from the zip like im thinking you said lol
it booted past the htc now i have like a wave of triangles lol im not sure if this is the new boot screen i think you had listed or if my phone is has entered the twilight zone.
It booted past that screen and i had seen the home menu for a few seconds then it just reboots...
C:\rootevo3dnew>fastboot flash boot boot.img
sending 'boot' (3756 KB)...
OKAY [ 0.990s]
writing 'boot'...
OKAY [ 1.192s]
finished. total time: 2.182s
Click to expand...
Click to collapse
Lmfao twilight zone, lol no that's the boot animation I listed. What recovery are you using? I use twrp, and that gives me no issues, if you're using ext4, make sure you turn smartflash on.
Before flashing again, manually wipe EVERYTHING minus the sdcard, that means wipe system and data as well. Just to make sure it starts on a clean slate. If you still can't get it pm me and ill help you one on one
And wait.. wait install.zip? I don't have an install.zip listed...?
Sent from my EVO 3DMA with a little "Common Sense"