Hi, i recently bought a replacement EVO 3D and i am having trouble unlocking it. I was able to unlock my first 3D which had the exact same software versions with no problem.
I have HBOOT 1.58 and the latest Sprint OTA ICS update.
When i go through the CMD part and enter the following:
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
nothing happens.
CMD shows the following:
C:\sdk-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.151s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.160s
Click to expand...
Click to collapse
but I don't receive an option to accept on my phone it just stays in the bootloader menu. Has anyone had this issue? Thanks
I know this doesn't help but I did have the problem with one EVO 3d I had with hboot 1.5 so I returned it and luckily got another with 1.4...spent 8 hours trying to unlock that one and never did get answers
Sent from my PG86100 using Tapatalk 2
Well first is the code.bin in it folder were it shud be?
EVO 3DIZZLE
S-OFF
HBOOT 1.58
Jmurphy8367 said:
Well first is the code.bin in it folder were it shud be?
EVO 3DIZZLE
S-OFF
HBOOT 1.58
Click to expand...
Click to collapse
Yes, it is sitting in the main folder with the other files. I followed the same steps i used before which worked on my old EVO 3D, but are not working on this one. Thanks.
All drivers and HTC sync good to go?
EVO 3DIZZLE
S-Off
hboot 1.58
Jmurphy8367 said:
All drivers and HTC sync good to go?
EVO 3DIZZLE
S-Off
hboot 1.58
Click to expand...
Click to collapse
Yes, I also tried uninstalling and reinstalling the drivers..and I tried a second computer. I have no idea what could be wrong, Is there an official RUU out yet from sprint for the new OTA ICS that I should install on it?
Here's my s-off folder put it on it hardisk its got fast boot adb and recovery put the code.bin in there and try it
EVO 3DIZZLE
S-Off
hboot 1.58
---------- Post added at 08:16 PM ---------- Previous post was at 08:08 PM ----------
http://db.tt/T6eecDpL
EVO 3DIZZLE
S-Off
hboot 1.58
The same thing happened. Command Prompt returns the following:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.159s
But nothing happens on my phone screen. Still stuck at the screen that says Fastboot USB in red. The window asking me if i want to unlock bootloader does not come up.
Robot818 said:
Hi, i recently bought a replacement EVO 3D and i am having trouble unlocking it. I was able to unlock my first 3D which had the exact same software versions with no problem.
I have HBOOT 1.58 and the latest Sprint OTA ICS update.
When i go through the CMD part and enter the following:
nothing happens.
CMD shows the following:
but I don't receive an option to accept on my phone it just stays in the bootloader menu. Has anyone had this issue? Thanks
Click to expand...
Click to collapse
Did you get a new token file for your replacement phone?
I would submit the file you capture from your phone and get a new token again just in case something went wrong the first time.
I "re unlocked" my phone after 1.58 using the same binary file I had from when I previously unlocked it.
sonza said:
Did you get a new token file for your replacement phone?
I would submit the file you capture from your phone and get a new token again just in case something went wrong the first time.
I "re unlocked" my phone after 1.58 using the same binary file I had from when I previously unlocked it.
Click to expand...
Click to collapse
Thanks for your reply, I just tried getting a new token again and still haven't been able to get the unlock bootloader option to pop. I've actually requested a new token three times now and and still nothing.
Just to let anyone else know that might have this same problem, i was able to fix this by running the RUU found here: http://forum.xda-developers.com/showthread.php?t=1827712
My phone is finally unlocked!
Robot818 said:
Thanks for your reply, I just tried getting a new token again and still haven't been able to get the unlock bootloader option to pop. I've actually requested a new token three times now and and still nothing.
Click to expand...
Click to collapse
Ok, the fact that is says sending with 0KB would seem to me that it is not actually reading the darn .bin file.
Now this might seem stupid, but we are shooting totally in the dark here.
First, I have my folder that has adb and all the other files in the root of the hard drive. It is called rootevo, just to keep the folder name short. While it usually should not matter, I knew we would be running adb from a command box, and that can sometimes cause issues with folder and file names longer than 8 characters.
If the phone is booted, plug it in and you should be able to type "adb reboot bootloader" and the phone should reboot to the bootloader screen. If this works, I would try and do the unlock process again. Make sure you are typing in the name exactly as it is named in the folder.
The other option would be to boot straight to bootloader after a battery pull. Again, not sure why it would matter, but you have a strange one here, so the fix could end up being equally strange.
Good luck! :laugh:
i guy's can you help us
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.172s
what is the solution of this error.???
Related
i can't flash the unlock token i get from htc using the official method and i've tried to redo the procedures for like a hundred times now, everything is set properly on my phone like fastboot is unchecked and debug mode is toggled on but everytime i just get the same error...i'm getting desperate
C:\adb>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.145s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.150s
can somebody shed some light?
tomanlam said:
i can't flash the unlock token i get from htc using the official method and i've tried to redo the procedures for like a hundred times now, everything is set properly on my phone like fastboot is unchecked and debug mode is toggled on but everytime i just get the same error...i'm getting desperate
C:\adb>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.145s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.150s
can somebody shed some light?
Click to expand...
Click to collapse
try this
http://htcevohacks.com/htc-evo-3d-hacks/how-to-root-evo-3d-2-08-651-2-and-later-htc-unlock-method/
Did you name the file adb? Try changing the file name of the folder you have fastroot in.
Calidrifter said:
Did you name the file adb? Try changing the file name of the folder you have fastroot in.
Click to expand...
Click to collapse
mnomaanw said:
try this
http://htcevohacks.com/htc-evo-3d-hacks/how-to-root-evo-3d-2-08-651-2-and-later-htc-unlock-method/
Click to expand...
Click to collapse
thx guys but the problem is i got adb and everything setup right, just that the token cant be correctly verified by my evo 3d...
Use fastboot. It'll work
Sent from my PG86100 using xda premium
Download the fastboot drivers. Put the phone on fastboot usb. Put the unlock.bin in the right folder. Usually c:/android. Enter the command prompt on your computer and change it to the right directory then type
C:/android> fastboot flash unlocktoken Unlock_code.bin
That should do the trick
Sent from my blazing fast 3d using xda premium
I know how you feel. I re-locked mine and now it wont even send the unlock_code.bin to unlocktoken...
Hopefully someone will be able to assist you better.
http://forum.xda-developers.com/showthread.php?t=1343114 try this...
N4LG4S said:
http://forum.xda-developers.com/showthread.php?t=1343114 try this...
Click to expand...
Click to collapse
thx, i tried it ytd but yet still no luck...it doesn't S-OFF at the last step and there're many "daemon not starting" (error?)
[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
Hey guys,
I've been following HTC's unlock method on my 3d. I have the Unlock_code.bin, but whenever I flash it, no splash screen comes up.
Does anybody know how to solve this?
semisight said:
Hey guys,
I've been following HTC's unlock method on my 3d. I have the Unlock_code.bin, but whenever I flash it, no splash screen comes up.
Does anybody know how to solve this?
Click to expand...
Click to collapse
What does it do when you flash the unlock code
You need to use the latest ruu exe and then redo the unlock code. Will fix ya .
Are u cdma or gsm ?
Sent from my PG86100 using xda premium
It gives me:
sending 'unlocktoken' (0 KB)... OKAY
writing 'unlocktoken'... INFOunlock token check successfully
OKAY
Click to expand...
Click to collapse
And there's no reaction from the phone. If I try it a second time it says:
sending 'unlocktoken' (0 KB)... FAILED (remote: loading custom splash failed)
Click to expand...
Click to collapse
My phone is HBOOT 1.50 with the 2.08 stock rom.
I'm CDMA, but I'm on a mac. Is there an RUU for mac?
EDIT: Downloading the update now, I'll try what you said.
Now I'm on 2.17. Same exact stuff is happening. Any other ideas?
semisight said:
Now I'm on 2.17. Same exact stuff is happening. Any other ideas?
Click to expand...
Click to collapse
The RUU exe is what everyone uses to get it to work.. You run that from hboot ... I don't know if the exe will run on mac since I run windows 7. I would see if mac users use it? I don't wanna say run something and it cause you more issues man since your using a mac ... The only fix I know is that RUU works every time...
Alright, I guess I can try my roommate's computer. Where can I find the RUU?
semisight said:
Alright, I guess I can try my roommate's computer. Where can I find the RUU?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1334473
Here you go man..
i'm having the same problem "(remote: loading custom splash failed)". tried updating the RUU, but i get error 155 which means the current RUU doesn't match the one its trying to install. My current RUU is 2.89 and the RUU it tries to install is 2.17. Also using CDMA EVO 3D on windows 7. Has any one had any luck with this? is there a work-around?
Hi
my problem
i have Evo 3D Hboot 1.49.0018 middle east
my Evo was unlock but i gave it HTC for repairing it stooped work suddenly
they changed Motherbord
any way
now im tryin again um trying to unloack it as before by HTCDEV method
when i reach step 12 it give me failed Msg
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.141s
i read a lot but i could not solve my problem or find an answer on the same old thread
thanks alot
You used the same token as before? If you have then there you got the reason why it is not working.
You have an new motherboard so you should have an new unlock token to.
Sometimes the unlock process won't work. Just install the RUU if you are having issues, and then try to unlock it and you will be successful.
Here is the link for the RUU: http://www.multiupload.com/09NOXKCUN0
EDIT: Mult-upload is down. I fogot. lol. The name of the RUU is 2.08.651.2 Install that and then try unlocking again.
yes I know the new Mb mean I have a new pocket
I start unlocking from 1 step
Seven times from a different pcs
Same fail msg appear
DexterMorganNL said:
You used the same token as before? If you have then there you got the reason why it is not working.
You have an new motherboard so you should have an new unlock token to.
Click to expand...
Click to collapse
How I can get the last middle east RUU ?
Thanks
mh7 said:
yes I know the new Mb mean I have a new pocket
I start unlocking from 1 step
Seven times from a different pcs
Same fail msg appear
Click to expand...
Click to collapse
You are having issues because the motherboard changed by htc was preloaded with 2.17.651.5 and some of the phones preloaded with this SW number have issues.
i found a link for RUU_Shooter_U_HTC_ARA_1.24.415.6
same that i I'm using
i will flash and see if it solve the problem
i falshed RUU
and started unlocke steps from step 1
same msg :
"sending 'unlocktoken' (0 KB)...
OKAY [ 0.140s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.150s"
i tried
RUU_Shooter_U_HTC_ARA_1.24.415.6
it give me same Hboot 1.49.0018
and
RUU_Shooter_U_HTC_ARA_1.24.415.2
with Hboot.1.49.0012
for sure im starting unlock from step 1
same Msg appearing
I'm guessing you mistakenly included an extra space at the end of the unlock token when you copied/pasted. It's a common error
Sent from my PG86100 using Tapatalk
greeg32 said:
I'm guessing you mistakenly included an extra space at the end of the unlock token when you copied/pasted. It's a common error
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
i checked that many time there is no space between
and HTC accept the code successfully !!
the problem that i did unlock before to my Evo before changing M.B
thanks to all who try to help
Is there any way to root my EVO without unlock
And sure not temporary
mh7 said:
Is there any way to root my EVO without unlock
And sure not temporary
Click to expand...
Click to collapse
there is a program ,developed by the people here at XDA ,called GingerBreak that does work for some phones and versions of gingerbread...read up on it before trying and use at your own risk
any new solution ?!!
you should have any problems with this. i did it too, and had no problems. is your device s-on or s-off?
stefanschroen said:
you should have any problems with this. i did it too, and had no problems. is your device s-on or s-off?
Click to expand...
Click to collapse
Sry for jumpin' in.. but did what?
stefanschroen said:
you should have any problems with this. i did it too, and had no problems. is your device s-on or s-off?
Click to expand...
Click to collapse
If I have s-off I won't open this topic: D
unlock failed
did you use the original unlock token that you downloaded the from the first time you unlocked it or did you download another unlock token
sure i start a new steps cause i have a new M.B
i think no way to use HTC unlock
and to change CID should start with unlock bootloder
i think only way to sell it and purchase a new one
current state: unrooted, s-on, relocked
I successfully unlocked my phone, installed TWRP and attempted to flash a new ROM. Some how I messed up by wiping out system file without backup, and I failed to flash a new ROM either.
So I flashed my phone with RUU latest version (hboot 1.19, radio 1.12.) Now on the bootloader screen it says RELOCKED on top.
When I tried to unlock (normal HTC Dev method) the terminal gave "unlock token checked successfully OKAY", and the unlock confirmation screen showed up normally.
But after rebooting, it turns out my phone is still "RELOCKED." Is there any reason why it doesn't work? And how to reunlock it successfully?
Did you submit the unlock token to htc website so that you can be given the unlock_code.bin file to flash?
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
Never mind I misread the post, try the relock command and unlocking again
Make sure the command is right
Fastboot flash unlocktoken Unlock_code.bin
om4 said:
Did you submit the unlock token to htc website so that you can be given the unlock_code.bin file to flash?
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
Never mind I misread the post, try the relock command and unlocking again
Make sure the command is right
Fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
Here is what happened in my terminal:
C:\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.011s]
finished. total time: 0.014s
C:\android-sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.147s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.011s]
finished. total time: 0.164s
After that the green unlock confirmation screen showed up on the phone, I chose unlock, pressed power button, waited for it to reboot, then reboot again to see the bootloader. Still no avail (relocked).
Have you tried flashing twrp anyway?
Use the 2.2.2.0 release, the new 2.3 has some issues that need to be worked out. It may just flash over, and never know
om4 said:
Have you tried flashing twrp anyway?
Use the 2.2.2.0 release, the new 2.3 has some issues that need to be worked out. It may just flash over, and never know
Click to expand...
Click to collapse
Here's what I got:
C:\android-sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7356 KB)...
OKAY [ 1.170s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.810s
(I used the img file in 2.2.2.0 twrp zip file. The name is recovery.img)
Does the failure message have something to do with being relocked?
Have you tried the PJ75IMG.zip for twrp. If you are s-off you should be able to install that and not worry about being unlocked.
Sent from my icrap 2 using Tapatalk HD
That shouldn't happen unless phone is still locked or software doesn't match
cruise350 said:
Have you tried the PJ75IMG.zip for twrp. If you are s-off you should be able to install that and not worry about being unlocked.
Click to expand...
Click to collapse
Opps sorry, I'm currently S-On.
om4 said:
That shouldn't happen unless phone is still locked or software doesn't match
Click to expand...
Click to collapse
When I tried to lock the phone again, it says my phone is already locked. But the problem is normal unlock method doesn't work with some reason.
I'm stumped, maybe ruu again?
om4 said:
I'm stumped, maybe ruu again?
Click to expand...
Click to collapse
Done ruu again, but still can't get unlocked.
Maybe it's worth mentioning that after select 'Yes' on the unlock bootloader screen (the green page), the phone didn't reboot. It just turned itself off with red LED charging.
chtat12 said:
Done ruu again, but still can't get unlocked.
Maybe it's worth mentioning that after select 'Yes' on the unlock bootloader screen (the green page), the phone didn't reboot. It just turned itself off with red LED charging.
Click to expand...
Click to collapse
Is there another way around (manual method) for unlocking? To me it looked like some thing after the green confirmation page just didn't work right.
I can't think of any reason it wouldn't work again, maybe someone else will see this and have a fix. Sorry
chtat12 said:
Is there another way around (manual method) for unlocking? To me it looked like some thing after the green confirmation page just didn't work right.
Click to expand...
Click to collapse
You could try downgrading to hboot 1.12 to get s-off...then it won't matter if you're unlocked or not. The process is still pretty new and not for the faint of heart (yet), but seems to be verified working. Check the downgrade sticky thread in the original dev forum for more details.
Sent from my EVO LTE
I would have mentioned it if closeone had a release ready but it's still a bit off. Better to wait then to have someone following directions to purposely brick their phones
premo15 said:
You could try downgrading to hboot 1.12 to get s-off...then it won't matter if you're unlocked or not. The process is still pretty new and not for the faint of heart (yet), but seems to be verified working. Check the downgrade sticky thread in the original dev forum for more details.
Sent from my EVO LTE
Click to expand...
Click to collapse
I believe downgrading method requires an unlocked phone, since it needs twrp for adb commands?
Yes it does, I didn't even remember that lol. I just didn't mention it because right now the overall process is rough
I think the unlock process modified the boot section, and looks like mine is a bit messed up. If so, would 'fastboot flash boot <bootfile>' work? (I don't know where to find it yet, just an another thought.)
chtat12 said:
I believe downgrading method requires an unlocked phone, since it needs twrp for adb commands?
Click to expand...
Click to collapse
Good point...
Sent from my EVO LTE
any resolution to this? i find myself in the same situation