Root [HOW TO](gaining root)unlock,downgrade,and achieve s-off with htcDev

[DIncNewbie]

First, some backstory: After unlocking, S-OFF, and loading AOKP, I had to backtrack and restore my stock Gingerbread ROM. Now having some instability (lockups, losing settings, downloaded apps mysteriously disappearing, etc.) and VZW has gotten into the act trying to help repair (not my choice, but it's my employer's phone...)

Anyway, at this point I may have to have the local VZW tech dig into the phone. How do I go back to S-ON and locked to make the phone look as stock as possible?

 

[sdrawkcab25]

First, some backstory: After unlocking, S-OFF, and loading AOKP, I had to backtrack and restore my stock Gingerbread ROM. Now having some instability (lockups, losing settings, downloaded apps mysteriously disappearing, etc.) and VZW has gotten into the act trying to help repair (not my choice, but it's my employer's phone...)

Anyway, at this point I may have to have the local VZW tech dig into the phone. How do I go back to S-ON and locked to make the phone look as stock as possible?

You'd follow the guide here to unroot:
http://androidforums.com/incredible-all-things-root/181255-how-return-stock-gingerbread.html

 

[scotty85]

Muwahahaha - sitting here in Afghanistan after a bad day, I've been staring at my Dinc's clock since I got here 9 months ago. Phone doesn't work (well, wireless does, but no phone radio). I said "self, lets play with this thing...how 'bout a root? Found this thread (from the old outdated thread) and voila. Good thing I read every post before I tried (i.e. hit the stick button instead of power) - worked 1st time. Don't know what I'ma gonna do with it now - but w/e, it was fun. OK, now onto hexxeh.net to eff around with Lime, can't sleep for $#!+ anyway. Thx Scotty!

awsome! glad it worked out for you

sdrawkcab25, no, I didn't. And that made all the difference...just wiped and things seem much more stable. My blood pressure is now something less than stratospheric!

I think I didn't do it originally because I was afraid that I would have wiped out my Nandroid backup files on the SD. As it turned out I had a second SD card that I used for the earlier processes and it had a copy of the backups. Definitely want to keep that original stock unrooted GB one around for any future problems...

Thanks again!

glad your prollem was easily sorted. ive always thot that nandroids were supposed to wipe for you,but as you see that may not be the case. i have personally alwasys wiped data/cache/dalvik cache prior to restoring a nandroid.

if you did not wipe prior to installing AOKP,may want to give it another shot sometime after a proper wipe as well

 

[scotty85]

Anyway, at this point I may have to have the local VZW tech dig into the phone. How do I go back to S-ON and locked to make the phone look as stock as possible?

forgot to answer this... just restoring your stock backup is usually good enuff. if you do need to get to a stock recovery/radios/etc. you can always run an RUU. your s-off will remain,so you can easily re-roto after simply by reinstalling custom recovery,flashing superuser.

i perosnally would not turn s back on. its only fnuction is to make sure the bootloader does not install things that htc does not want us to install. it will not have any affect whatsoever on the booted phones operation,nor the ability to recieve OTAs,etc.

being s-off adds alot of extra options for recovery of a soft bricked device.

being s-on,however,has absolutely no advantages whatsoever

 

[DIncNewbie]

scotty85, sounds good to me. My only concern is VZW coughing up a hairball if they see that something may have been done. Because doesn't it show (in HBOOT) if the phone is unlocked and/or S-OFF?

 

[DIncNewbie]

You'd follow the guide here to unroot:
http://androidforums.com/incredible-all-things-root/181255-how-return-stock-gingerbread.html

sdrawcab25 (or anyone), ran into a snag trying to get back to Gingerbread. Did S-ON first, then tried option #1 (ZIP file on freshly formatted SD card). HBOOT showed a progress bar that it was loading PB31IMG.ZIP but then it just went back to the main screen with no prompt to load. Retried twice, no joy. Then went to option #2 (RUU), and it got partway through the process and kicked back Error 155 (unknown) and said that it could not update. Any ideas?? Thanks, as always!

 

[scotty85]

scotty85, sounds good to me. My only concern is VZW coughing up a hairball if they see that something may have been done. Because doesn't it show (in HBOOT) if the phone is unlocked and/or S-OFF?

does your phone still have factory warranty? most dincs are well past that point,but if it does,you can turn s-on if needed. legitimate warranty claims with physical hardware are likely to be honored,even if your hboot does show s-off or unlocked. the reality is we as rooters are in the minority when you look at the phone using public,and vzw has stated that they do not check for rotoed devices when they recieve them back from warranty.

according to a statement from vzw they check:
1)overall condiditon of the shipping packaging
2)overall physical condiditon of the device(scratches,chips,etc)
3)that the device does(or doesnt) power on.

not to mention that some legitimate test phones did ship s-off to pre-release testers. being s-off does not neccessarily indicate to vzw or htc that you have messed with the device.

if youre just relying on 3rd party insurance,then it definately does not matter. asurion and other 3rd party carriers do not care if youve rooted your phone,lost it,or smashed it with a hammer as long as youve paid the premiums and deductible

sdrawcab25 (or anyone), ran into a snag trying to get back to Gingerbread. Did S-ON first, then tried option #1 (ZIP file on freshly formatted SD card). HBOOT showed a progress bar that it was loading PB31IMG.ZIP but then it just went back to the main screen with no prompt to load. Retried twice, no joy. Then went to option #2 (RUU), and it got partway through the process and kicked back Error 155 (unknown) and said that it could not update. Any ideas?? Thanks, as always!

again,id consider staying s-off until you need to make a warranty claim,this can always be returned to complete stock later. theres no benefit to doing it now.

hboot flashing requires:
1)sd formatted FAT32
2)properly named file(phone must see PB31IMG.zip)

so if youre using a signed by htc file,and do not have it hidden inside folders,then one of those 2 things is prolly wrong. a common mistake with windows is to typs in the .zip,resulting in a file name of "PB31IMG.zip.zip" since windows adds,and hides the file extension.

also note that you can put the PB31IMG into your miniadb_inc folder and use fastboot to flash it just like you did the downgrade.

when you get error 155 from the RUU utility in the booted OS,most of the time it will work to place the phone in fastboot mode,then start the utility.

 

[DIncNewbie]

scotty, great info, thanks again. The phone's out of warranty, so its root and/or S-state is probably moot, as you pointed out. However, one of the VZW business techs said that if my DInc did in fact completely lose its mind, she could probably swing some sort of courtesy replacement (which was music to my ears, because if my company IT people have to replace a phone they're now handing out iPhones <ugh>). Just wanted to make sure I wasn't doing anything that would ***** the deal if they saw that I'd been toying with it...

As far as the stock ROM problem, I checked the SD formatting, file name, MD5, etc. Also tried the RUU on fastbooted phone, no go. (Did not try flashing from fastboot on the PC, though.) Then for the heck of it I went back to S-OFF and tried the ZIP from the SD card, and damned if it didn't work just fine and dandy! So, I'm still S-OFF but no longer concerned about that. Just waiting to see if things become stable again. (Have a sneaking suspicion that something else is wonky in the hardware, but hoping it's not so that I don't get wedged into an iPhone...)

Thanks again!

 

[scotty85]

well i definately do not blame you for not wanting to get wedged into an iphone! i would do everything to prevent that from happening as well

as for PB31IMG,when your s-on it does a number of security checks,most of wich will fail with errors,rather than siliently returning to the hboot screen.

is it givin you an error of some sort? is it finding and checking the file?

it could be the main version of the upgrade is older than the main version in your phone. it could be corrupt,and not passing the signiture check. if you happen to have hboot 1.02 or 1.07 it oculd be failing an hboot check.

at any rate,thats one of the beauties of being s-off you cAn flash whatever firmware you want,whenever you want! :smokingsomb:

i would definately run the phone completely stock for a couple days after running the ruu. if you still have prollems,try a factory reset from hboot. hopefully that will clear some tihngs out and make it a lil happier.

if everything is fine after a few days,then you can easily reroot.

if you want to stay pretty much stock,except for root access,it is possible to boot recovery into phone memory without actually installing it. you can then flash superuser from the booted recovery,keeping the stock recovery on the phone in case OTAs sneek up on you,and/or you need to call vzw customer service. if you want i can go over that with you at some point

 

[StarScream2109]

thanks scotty! followed all your instructions im now rooted with s-off great work man!

 

[pkh106]

Hi Scotty85-
Thanks for taking the time to create this great information! This is exactly where i'm stuck and i'm hoping you can help me out.

Incredible 2 from Verizon.
Currently, i'm:
*** UNLOCKED ***
VIVO_W XB SHIP S-ON RL
HBOOT-0.98.0000
RADIO-1.09.01.1111
eMMC-boot
Jul 18 2011, 12:39:36

I'm HTC DEV Unlocked, but i installed CM7 and didn't back up the original ROM.
I'm at your step 4 and is the bootloader supposed to be locked at this point? (i.e. fastboot oem lock?). If so, will locking it with CM7 cause a problem? If it does cause a problem, is there a way to go back to the original RUU with CWM to load it? I'm so stuck, i have it unlocked (scared to lock it) and only have CM7 running.

thanks in advance!

 

[sdrawkcab25]

Hi Scotty85-
Thanks for taking the time to create this great information! This is exactly where i'm stuck and i'm hoping you can help me out.

Incredible 2 from Verizon.
Currently, i'm:
*** UNLOCKED ***
VIVO_W XB SHIP S-ON RL
HBOOT-0.98.0000
RADIO-1.09.01.1111
eMMC-boot
Jul 18 2011, 12:39:36

I'm HTC DEV Unlocked, but i installed CM7 and didn't back up the original ROM.
I'm at your step 4 and is the bootloader supposed to be locked at this point? (i.e. fastboot oem lock?). If so, will locking it with CM7 cause a problem? If it does cause a problem, is there a way to go back to the original RUU with CWM to load it? I'm so stuck, i have it unlocked (scared to lock it) and only have CM7 running.

thanks in advance!

This thread for the original incredible, not the incredible 2.... But why are you trying to relock the phone?

 

[scotty85]

Hi Scotty85-
Thanks for taking the time to create this great information! This is exactly where i'm stuck and i'm hoping you can help me out.

Incredible 2 from Verizon.
Currently, i'm:
*** UNLOCKED ***
VIVO_W XB SHIP S-ON RL
HBOOT-0.98.0000
RADIO-1.09.01.1111
eMMC-boot
Jul 18 2011, 12:39:36

I'm HTC DEV Unlocked, but i installed CM7 and didn't back up the original ROM.
I'm at your step 4 and is the bootloader supposed to be locked at this point? (i.e. fastboot oem lock?). If so, will locking it with CM7 cause a problem? If it does cause a problem, is there a way to go back to the original RUU with CWM to load it? I'm so stuck, i have it unlocked (scared to lock it) and only have CM7 running.

thanks in advance!

if you are on an inc 2 you want this guide.

relocking with cm7 will likely cause a security warning that will lock you into bootloader until you run an ruu or re-unlock with your original unlock_code.bin. it should not be a big deal as yuor just going to run the ruu right after(so make sure youve backed up cm7 if you want to go back to it)

if you have further questions feel free to post in that thread,so folks here are not confused

 

[3sgte]

ok guys i finally have decided tonight to give this a shot. sorry for the very basic questions that will follow but i am very new to all this and for that matter any real c-prompt stuff.... i have just started to try and unlock the bootloader and im a little confused about how to get the unlock key.
i have gone to htcdev and got the email sent to me and now im on step 11 and having an issue. it says to save the unlock file to the same folder as
C:\Android --in my case it is--- miniadb_inc folder.
i save it to this folder which is on its own in my C drive but when i type in my c-prompt--- fastboot flash unlocktoken Unlock_code.bin ----
it says "cannot load unlock_code.bin"
not sure what im doing wrong but im sure its pretty simple but im to new to this to figure it out..lol
thanks for the help

 

[DIncNewbie]

well i definately do not blame you for not wanting to get wedged into an iphone! i would do everything to prevent that from happening as well

as for PB31IMG,when your s-on it does a number of security checks,most of wich will fail with errors,rather than siliently returning to the hboot screen.

is it givin you an error of some sort? is it finding and checking the file?

it could be the main version of the upgrade is older than the main version in your phone. it could be corrupt,and not passing the signiture check. if you happen to have hboot 1.02 or 1.07 it oculd be failing an hboot check.

at any rate,thats one of the beauties of being s-off you cAn flash whatever firmware you want,whenever you want! :smokingsomb:

i would definately run the phone completely stock for a couple days after running the ruu. if you still have prollems,try a factory reset from hboot. hopefully that will clear some tihngs out and make it a lil happier.

if everything is fine after a few days,then you can easily reroot.

if you want to stay pretty much stock,except for root access,it is possible to boot recovery into phone memory without actually installing it. you can then flash superuser from the booted recovery,keeping the stock recovery on the phone in case OTAs sneek up on you,and/or you need to call vzw customer service. if you want i can go over that with you at some point

scotty, that's the crazy thing...it's finding and loading the file (you see the vertical progress bar in the upper right) but not sure what sort of checking it's doing because the instant that the progress bar goes complete it immediately returns to the menu, with no message or error or anything. I made sure that the image file's MD5 checked out OK, complete formatting of the SD, etc. I do have HBOOT 1.07 so maybe that's part of it.

Anyway, things seem to be stable now, so going to give it a few days and cross my fingers. Actually, there is one little oddity at this point: if I go into HBOOT there is no top menu line that says LOCKED or UNLOCKED. It starts with the line that has the phone model and S-OFF. Why is that, do you think? And when I installed the stock ROM would that have locked the bootloader?

If everything stays settled down I may just give AOKP another go. Just to verify, if I'm still rooted and S-OFF, all I have to do is put the AOKP image on the SD, boot to recovery and install? And if I do that, and decide to go back to stock, do the same thing with that image?

Thanks again for all your assistance and hard work on this. These forums are a tremendous resource.

 

[scotty85]

ok guys i finally have decided tonight to give this a shot. sorry for the very basic questions that will follow but i am very new to all this and for that matter any real c-prompt stuff.... i have just started to try and unlock the bootloader and im a little confused about how to get the unlock key.
i have gone to htcdev and got the email sent to me and now im on step 11 and having an issue. it says to save the unlock file to the same folder as
C:\Android --in my case it is--- miniadb_inc folder.
i save it to this folder which is on its own in my C drive but when i type in my c-prompt--- fastboot flash unlocktoken Unlock_code.bin ----
it says "cannot load unlock_code.bin"
not sure what im doing wrong but im sure its pretty simple but im to new to this to figure it out..lol
thanks for the help

the directions assume that when you enter the command to unlock(fastboot flash unlocktoken Unlock_code.bin) that you still have your cmd window open,and the phone in fastboot.

off the top of my head,the only things i can think of are that the unlock_code.bin is not in your miniadb_inc directory,it has become corrupt during file trasfer or download,or possibly the phone is not in fsatboot. make sure that you are in fastboot,and not in hboot,or the booted OS.

you should also make sure that htc sync,pdanet,easy tether,or any other program capable of comunicating with the phone is disabled or uninstalled. you can try different usb ports or cables.

if its not one of those things,a copy/paste of your entire cmd window may provide some clues

scotty, that's the crazy thing...it's finding and loading the file (you see the vertical progress bar in the upper right) but not sure what sort of checking it's doing because the instant that the progress bar goes complete it immediately returns to the menu, with no message or error or anything. I made sure that the image file's MD5 checked out OK, complete formatting of the SD, etc. I do have HBOOT 1.07 so maybe that's part of it.

Anyway, things seem to be stable now, so going to give it a few days and cross my fingers. Actually, there is one little oddity at this point: if I go into HBOOT there is no top menu line that says LOCKED or UNLOCKED. It starts with the line that has the phone model and S-OFF. Why is that, do you think? And when I installed the stock ROM would that have locked the bootloader?

If everything stays settled down I may just give AOKP another go. Just to verify, if I'm still rooted and S-OFF, all I have to do is put the AOKP image on the SD, boot to recovery and install? And if I do that, and decide to go back to stock, do the same thing with that image?

Thanks again for all your assistance and hard work on this. These forums are a tremendous resource.

yup,if you had 1.07 when trying to update s-on,it realized that even tho the main version was lower,that hboot was higher,and did not give you the option to update. when you are s-on,you cannot install a lower bootloader(.92 or 1.02) i place of 1.07.

when you went back to s-off,the security checks went out the window so the file flashed fine.

you do not have the locked or unlocked banner any longer,becasue when you run the upgrade ruu,it actually downgraded your hboot back to .92 wich does not support htcdev unlock functions.

on your aokp question,yup,easy as that. just boot to recovery and install. make sure you wipe data/factory reset,cache,and dalvik cache so you dont have prollems.

to get back to stock,you can flash a stock rom,or you can restore a nandroid of the stock rom.

feel free to bounce around and check out different roms. just remember to always do the "wull wipe" described above,and make sure you make nandroids(and keep a list of what they are )

 

[3sgte]

thanks for the help on this scotty85. i have been trying this for a few hours now but i have run into a new problem and cant move forward. not sure if anyone else has had this problem but i cant log back into the htcdev website???
i was on it yesterday without problem but today when i try to login it says thanks for logging in and then redirects me and then says im not logged in?
i have tried logging in on my girlfriends macbook and all works good, i can log in.
when trying from my compaq with vista 64bit i cant get in.
i have cleared all cache and cookies with no fix.
getting pretty frustrated as this is really only the beginning steps of rooting this phone and i cant even get this done!! is this what i have to look forward to??LOL i hope not...

 

[scotty85]

not sure on htcdevs website... for what its worth,once you have your unlock_code.bin,you really dont need it.

 

[DIncNewbie]

yup,if you had 1.07 when trying to update s-on,it realized that even tho the main version was lower,that hboot was higher,and did not give you the option to update. when you are s-on,you cannot install a lower bootloader(.92 or 1.02) i place of 1.07.

when you went back to s-off,the security checks went out the window so the file flashed fine.

you do not have the locked or unlocked banner any longer,becasue when you run the upgrade ruu,it actually downgraded your hboot back to .92 wich does not support htcdev unlock functions.

on your aokp question,yup,easy as that. just boot to recovery and install. make sure you wipe data/factory reset,cache,and dalvik cache so you dont have prollems.

to get back to stock,you can flash a stock rom,or you can restore a nandroid of the stock rom.

feel free to bounce around and check out different roms. just remember to always do the "wull wipe" described above,and make sure you make nandroids(and keep a list of what they are )

scotty, bingo. That explains it. Frighteningly, this is all starting to make sense now!

This then begs the question: is there a simple way to get back to HBOOT 1.07 (which I'm assuming is better to have than the older one) and unlocked, and hopefully doesn't involve having to flash a whole ROM? Checked back on HTCdev and they have an updater to 1.02; is that good enough, do you think? (I'm hoping too that I don't have to go through the whole earlier downgrade-to-Froyo routine, which if I remember correctly was just to get UnrEVOked forever to go S-OFF?) Or can I just wait until I install a new ROM (AOKP or whatever) and hopefully that ROM will update HBOOT?

 

[3sgte]

thanks Scotty85, i guess i dont neeed to go to htcdev then. my original problem still exists. when i try to get the unlock code from the c prompt i get and error message. i made sure that the unluck file from the email i got from htc is in the miniadb_inc folder in my c-drive. here is what is see..



c:\miniadb_inc>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT04PHJ03730 device


c:\miniadb_inc>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *

c:\miniadb_inc>fastboot devices
HT04PHJ03730 fastboot

c:\miniadb_inc>fastboot oem get_identifier_token
... INFO
INFO< Please cut following message >
INFO<<<< Identifier Token Start >>>>
INFO86E49AE734000122DDAF7E20FB7BCADA
INFO454C112703958D8D67A6980360A3A14D
INFO2A4C66B0B9F611DB7640FF4D95BF65FE
INFO5D7D55E593A4BDA4E52CC307C8BD72BA
INFO64BB70D2D89B4F2960CC9B0B441ECE2D
INFO6D9EA398D8FD93EA7B3BC0C34A3E1E14
INFO90F116049882BFA8B87E1D7D3AD4ED80
INFO063E1B6BDD6977D7B0A5F4D4F847DCB3
INFOA251CFF705CAEC80B97FA0D77E641B75
INFODA41664EF6D879A69E5269DF065BF906
INFO3FB54B88945DE10829AB917D9126D3C6
INFO1C65B96D9C1B3E68C98F44CDD17A3E73
INFO0901834DDA4F704E60332E80A2F90B26
INFO10B5A66A19AACC7CFB8073BEE55F30CF
INFOAE97E4AB9836DD77920241983C2EEC51
INFO375F2A2776BFC277FFC3FF4FFCB9EF21
INFO<<<<< Identifier Token End >>>>>
OKAY [ 0.063s]
finished. total time: 0.064s

c:\miniadb_inc>fastboot flash unlocktoken Unlock_code.bin
error: cannot load 'Unlock_code.bin'

 

[scotty85]

scotty, bingo. That explains it. Frighteningly, this is all starting to make sense now!

This then begs the question: is there a simple way to get back to HBOOT 1.07 (which I'm assuming is better to have than the older one) and unlocked, and hopefully doesn't involve having to flash a whole ROM? Checked back on HTCdev and they have an updater to 1.02; is that good enough, do you think? (I'm hoping too that I don't have to go through the whole earlier downgrade-to-Froyo routine, which if I remember correctly was just to get UnrEVOked forever to go S-OFF?) Or can I just wait until I install a new ROM (AOKP or whatever) and hopefully that ROM will update HBOOT?

after you ran the GB ruu,if you still have the stock recovery,you can just let the phone OTA to the most current firmware.

if youve allready flashed your custom recovery,then you can simply download and install it as a PB31IMG in hboot:

PB31IMG-4.08.605.15-hboot-1.07.zip
md5: PB31IMG-4.08.605.15-hboot-1.07.zip db019de010ae8ef6a2c250fd8b378ba1

it may still be in ints previous state when you re-flash it(i.e.,if it was unlocked,it will still be). if you find it to be locked or relocked you can use your original unlock-code.bin to re-unlock it.

here is the newet radio,if you want that as well:
PB31IMG-4.08.605.15-radio.zip

md5: PB31IMG-4.08.605.15-radio.zip cb8b3ac72c0ae13e1f088b302135bd58

 

[scotty85]

thanks Scotty85, i guess i dont neeed to go to htcdev then. my original problem still exists. when i try to get the unlock code from the c prompt i get and error message. i made sure that the unluck file from the email i got from htc is in the miniadb_inc folder in my c-drive. here is what is see..



c:\miniadb_inc>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT04PHJ03730 device


c:\miniadb_inc>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *

c:\miniadb_inc>fastboot devices
HT04PHJ03730 fastboot

c:\miniadb_inc>fastboot oem get_identifier_token
... INFO
INFO< Please cut following message >
INFO<<<< Identifier Token Start >>>>
INFO86E49AE734000122DDAF7E20FB7BCADA
INFO454C112703958D8D67A6980360A3A14D
INFO2A4C66B0B9F611DB7640FF4D95BF65FE
INFO5D7D55E593A4BDA4E52CC307C8BD72BA
INFO64BB70D2D89B4F2960CC9B0B441ECE2D
INFO6D9EA398D8FD93EA7B3BC0C34A3E1E14
INFO90F116049882BFA8B87E1D7D3AD4ED80
INFO063E1B6BDD6977D7B0A5F4D4F847DCB3
INFOA251CFF705CAEC80B97FA0D77E641B75
INFODA41664EF6D879A69E5269DF065BF906
INFO3FB54B88945DE10829AB917D9126D3C6
INFO1C65B96D9C1B3E68C98F44CDD17A3E73
INFO0901834DDA4F704E60332E80A2F90B26
INFO10B5A66A19AACC7CFB8073BEE55F30CF
INFOAE97E4AB9836DD77920241983C2EEC51
INFO375F2A2776BFC277FFC3FF4FFCB9EF21
INFO<<<<< Identifier Token End >>>>>
OKAY [ 0.063s]
finished. total time: 0.064s

c:\miniadb_inc>fastboot flash unlocktoken Unlock_code.bin
error: cannot load 'Unlock_code.bin'

hmmm,there is nothing immediately wrong with that... looks like it should have flashed fine.

when you saved it to miniadb_inc,did you change the name at all? if you did,its possible the name or file extention is changed somehow(for example,Unlock_code.bin.bin if you typed in the file ext)

the only other things i can think of,are if you were missing a character when you submitted the identifier token,or if you have something running on the PC thats interfering with it.

this is the unlock_code.bin that you got from the identifier token from this phone that youre unlocking,correct?

can you get a screen shot of the contents of miniadb_inc? you might also right clock on unlock_code.bin,click properties,and see what that says... make sure its still a .bin file

 

[3sgte]

hmmm,there is nothing immediately wrong with that... looks like it should have flashed fine.

when you saved it to miniadb_inc,did you change the name at all? if you did,its possible the name or file extention is changed somehow(for example,Unlock_code.bin.bin if you typed in the file ext)

the only other things i can think of,are if you were missing a character when you submitted the identifier token,or if you have something running on the PC thats interfering with it.

this is the unlock_code.bin that you got from the identifier token from this phone that youre unlocking,correct?

can you get a screen shot of the contents of miniadb_inc? you might also right clock on unlock_code.bin,click properties,and see what that says... make sure its still a .bin file

yes this is the unlock code for this phone. also i dont believe i have anything else running that would interfere with it. i do have htc sync but it is not active when i plug the phone in. i did not change the name of the bin file at all. i have attached some photos of the file.

 

[3sgte]

Scotty, well i took 2 pics of the computer screen with my phone and it wont let me attach either one due to its size. is there a way to make them smaller or maybe not use my phone but actually do a screen shot? again im not very computer literate so forgive me for the dumb questions.
thanks

 

[scotty85]

Scotty, well i took 2 pics of the computer screen with my phone and it wont let me attach either one due to its size. is there a way to make them smaller or maybe not use my phone but actually do a screen shot? again im not very computer literate so forgive me for the dumb questions.
thanks

with windows,you can use the Alt/Print Screen to take a screenshot of your active window,or just Print Screen to take the whole screen. this will copy a screen shot to your clipboard,then you can open photo shop or similar program, then open a new project(file/new) then edit/paste and it will open your screen shot. you can then save it,and hopefully upload.

alternately,you could adjust the camera on your phone to the smallest resolution,you could host the pics on photobucket,or upload them to somewhere like drop box.

you might just start the process over on a different pc or laptop that has never had any phone stuff installed on it.