New: XDA launches forum for app developers. Discuss coding, tools, marketing, and more.
XDA Developers Android and Mobile Development Forum
Forgot your password?
 
Post Reply+
Tip us?
 
socal87
Old
#1  
Senior Member - OP
Thanks Meter 53
Posts: 309
Join Date: Feb 2011
Location: Tacoma, Washington
Default Stuck with locked bootloader

Long story short, I re-locked the bootloader in order to flash the new ICS prerelease, to prepare for CleanRom 4.0. Everything seems to have gone well; however, I cannot unlock the bootloader again. I have verified that fastboot sees the phone, and obviously have ensured that the phone is in bootloader when I send the command. I have also ensured that my token is good.

When sending the command:
fastboot flash unlocktoken Unlock_code.bin
All I get is:
sending 'unlocktoken' (0 kb)...
Doesn't make any progress, just sits there. Phone is unresponsive and requires a battery pull to turn off or reboot - sending "fastboot reboot" seems to be successful but doesn't actually reboot the phone once it's frozen.

I'm trying to figure out a way to get support from hTC as well.
 
trickster2369
Old
#2  
trickster2369's Avatar
Senior Member
Thanks Meter 440
Posts: 1,707
Join Date: Feb 2011
Location: SD

 
DONATE TO ME
Make sure your unlock token is in the same folder as adb/fastboot. Then change your directory to that folder before sending the command.

Sent from my ADR6425LVW using xda premium
 
con247
Old
#3  
con247's Avatar
Recognized Developer
Thanks Meter 3068
Posts: 3,072
Join Date: Sep 2010
Location: Ann Arbor
Quote:
Originally Posted by trickster2369 View Post
Make sure your unlock token is in the same folder as adb/fastboot. Then change your directory to that folder before sending the command.

Sent from my ADR6425LVW using xda premium
I think he figured it out. His PC needed a reboot.

Current Phone: Galaxy S3 16GB White on VZW
Current ROM: AOKP JB Build 4
Check out my GS3 Splash Screen Changer
 
socal87
Old
#4  
Senior Member - OP
Thanks Meter 53
Posts: 309
Join Date: Feb 2011
Location: Tacoma, Washington
Quote:
Originally Posted by con247 View Post
I think he figured it out. His PC needed a reboot.
Yup...PC troubleshooting 101...when in doubt, reboot everything and try again.