[UNLOCK] AT&T Bootloader Unlock Through HTC-Dev

Search This thread

jesusdavid

Senior Member
Jun 9, 2010
78
7
I'm on 1.85 however I'm rooted can I use this method to unlock? (I got rooted on 1.82 and than got the updated)
 

mbh87

Senior Member
Jun 16, 2010
6,499
1,027
Idaho
I've heard from some people that their phones were unable to be powered on after going through with this. Would that be caused by user error or is it just a potential risk in general for are devices?
 

tobia996

Senior Member
Sep 27, 2009
59
1
unbrand my phone

objective: install the eu stock ruu on my phone (htc one s) instead of the brandized one that i run now.
do those procedures are right?
1-unlock my device on htc dev
2-install recovery
3-obtain root
4-change cid with this procedure
5-re-unlock my phone at htc dev??
6-install my favourite ruu??

Or can i :
1-change cid with this procedure
2-install a ruu for my new cid?
 

Fberry

Member
Mar 29, 2008
21
2
Once you completed this procedure and have an unlocked bootloader. Should you replace the modded mmcblk0p4 with the original. I have an unlocked rooted phone, but I am unable to flash custom roms. The kernel gets flashed, but when I try to flash the rom through custom recovery I get error messages and the rom does not install properly. I have tried 3 different custom roms and get the same issues with all of them. I get error messages during the install and they seem to indicate I do not have the right phone. The error message follows:
Checking Model ID
assert failed: getpropt("ro.build.product") =="endeavoru" ll getprop"ro.product.board"0 ** "endeavoru"

Any advice would be appreciated.
 

Fberry

Member
Mar 29, 2008
21
2
Once you completed this procedure and have an unlocked bootloader. Should you replace the modded mmcblk0p4 with the original. I have an unlocked rooted phone, but I am unable to flash custom roms. The kernel gets flashed, but when I try to flash the rom through custom recovery I get error messages and the rom does not install properly. I have tried 3 different custom roms and get the same issues with all of them. I get error messages during the install and they seem to indicate I do not have the right phone. The error message follows:
Checking Model ID
assert failed: getpropt("ro.build.product") =="endeavoru" ll getprop"ro.product.board"0 ** "endeavoru"

Added 06/23
Figured it out. Thanks.
 

gunnyman

Senior Member
Apr 12, 2010
7,998
2,668
Greenville SC
Once you completed this procedure and have an unlocked bootloader. Should you replace the modded mmcblk0p4 with the original. I have an unlocked rooted phone, but I am unable to flash custom roms. The kernel gets flashed, but when I try to flash the rom through custom recovery I get error messages and the rom does not install properly. I have tried 3 different custom roms and get the same issues with all of them. I get error messages during the install and they seem to indicate I do not have the right phone. The error message follows:
Checking Model ID
assert failed: getpropt("ro.build.product") =="endeavoru" ll getprop"ro.product.board"0 ** "endeavoru"

Added 06/23
Figured it out. Thanks.


did you figure out that your phone is an EVITA and not and Endeavor?

Don't flash stuff from international HOX forum on a US HTC One X (L)
 

garrettjjjj

Member
Mar 25, 2012
23
0
Newark, DE
Is there a certain trick I need to do to access the boatloader on startup? When I unlocked my Kindle Fire bootloader I had a screen during startup that let me enter bootloader. After the first time it showed the bootloader screen on my One X, I haven't seen anything on any other restart. Could it have cleared back to normal? (Noob question, sorry)

EDIT: NVM. Got it. I'm just dumb.
 
Last edited:

dynezxice

Senior Member
Mar 8, 2011
138
13
I have rooted my phone running on pre-loaded firmware 1.85. Does this unlock bootloader method work for rooted phones on firmware 1.85? Thanks.
 

Thongvilay

Senior Member
Jan 25, 2008
177
0
I have a similar post on a different thread before realizing I should have posted here.


OK, I have ROOT....went to unlock bootloader, got my token, went to enter it at HTCdev....I keep getting the error message "Invalid bootloader token length" & "The submitted Token appears to be the wrong length and won't work."

I have copied the highlighted areas that I need and no matter what, I get the same error, no spaces, no margains. Here is my token if someone wants to try and see if it works.

<<<< Identifier Token Start >>>>
AEFB4D81A0EC8401BB57189772000BE1
086F6C696D81B3D184AAB201DBEA05D3
DCF25ACDFCA9532A7E87BD6F8D50FA96
DA5110C3BE2AD45A7F624A7AC1923A08
31B5256F091686B7A936943E5918D2CF
317E95A4AEE02E8A971BB11743E0A69F
0410B1ABE36505073D2FC23BE4BC3511
79A9311825C16698297A33344449BDEA
F54D3237E5E29E53E1BFABB879CAE508
385B30E69CE1D1B52C46C45C770EF0AE
23A8B283197180D10D06F61D7A95922F
98F09E048FE25FB9ACE8BDE83473D72E
E71B1CAEC5F9A3608A97346FF16C56EF
9D9B12419327A13B119E8DED5ECEB617
0532EDCBB8A3B650B9962B6A552BDA3C
9C5FB42A49C373B5CF4922D0A999AEEC
<<<<< Identifier Token End >>>>>
 

Top Liked Posts

  • There are no posts matching your filters.
  • 349
    You do this at your own risk!!! This could turn your new phone into a very expensive paperweight!!! If you don't know how to do it or are uncomfortable DON'T DO IT!!!

    You need ADB and an understanding of how to use it and have a rooted device (although I didn't test this). You will also need a hex editor like HxD.

    BACK UP YOUR DATA BEFORE DOING THIS!!!! WHEN HTCDEV UNLOCKS YOUR DEVICE YOU MUST START FROM SCRATCH!!!

    1. Fire up your command prompt and go to the directory that you have ADB installed to. Type "adb shell" and hit enter.

    2. Type "su" and hit enter. You now have root privileges.

    3. Next type "dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4" and hit enter. This will dump the partition to your sdcard.

    4. Next type "exit", hit enter, type "exit", and hit enter again. This should take you back to a command prompt for your computer.

    5. type "adb pull /sdcard/mmcblk0p4" and hit enter. NOTE THE SIZE OF THE FILE BEFORE THE NEXT STEP!

    6. Open the file (mmcblk0p4) with your hex editor.

    7. Look for offset 00000210 (if your on RUU version 1.82 the offset may be 00000214) and you should see CWS__001 with your IMEI number attached to it.

    8. Change CWS__001 to 11111111 and save the file as mmcblk0p4MOD. This will give you SuperCID as well. :D MAKE SURE AT THIS POINT THAT THE FILE IS THE EXACT SIZE IT WAS BEFORE YOU HEX EDITED IT!

    9. Now go back to your command prompt and type "adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD" and hit enter.

    10. Type "adb shell" and hit enter then type "su" and hit enter again. This will put you back into the android shell and give you root privileges.

    11. Type "dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4" and hit enter. To test if it worked restart the phone into fastboot (type "adb reboot bootloader" and hit enter) and once the bootloader screen comes up type "fastboot oem readcid" and hit enter. It should read "11111111".

    12. Next type "fastboot oem get_identifier_token" and hit enter. Leave that up on your screen and go to HTCdev.com. Follow the instructions from there. Choose "All other supported models" from the dropdown menu.

    For those having trouble with the hex editor portion of this I have posted a picture from Squeak22 showing exactly what it should look like. Thanks Squeak22!

    Enjoy all!

    Guy
    26
    Worked for me with CID 11111111.

    Thanks, my friend, now I can stop that f'ing thread...

    IMG_0502.jpg
    9
    Ya, a complete write up with step-by-step pictures would be nice... since this is sort of dangerous with a potential to get a brick.

    probably need to make a script that can do all dd and hexing, that would make it much safer.
    8
    All those involved in the argument should stop now. I'll be visiting this page in the next few hours. If I see another response, infractions will be handed out.

    Follow the steps carefully, use caution, don't blame others, and don't ***** each other out. If you have a problem, private message me.

    you-were-saying_o_187166.gif
    5
    Now all we need is SK to finish CWM Recovery! :)

    Thanks, Will try when I get home

    Now I can actually test the f-ing thing, should be a gimme...I am so relieved this is done. Now its working recovery and s-off time...;). Again, thanks grankin...