Database Develop

Reset Simlock Count on Hw6515

Does it possible to reset the simlock counter try?
I've a problem with it : Simlock say i've tried 20 times to enter simlock code!
And now i can't valide new code : Ok button stay grey
This happened after i used vBar to kill Simlock task ! Number of try has reach 20 and now it seem to be lock for many days.
If someone can help me... Please cause now i've my simlock code but i can't valide if !
Ipaq Hw6515 French Bouygue telecom
Last ROM 1.23 French
vBar (great freeware but dangerous for simlock!) :
http://www.pocketpcfreewares.com/fr/index.php?soft=562

Go into bootloader using mtty.exe, you need to access AT command interpreter, in some htc devices this is done by command 'rtask 7' on others is 'rtask b' (I don't know on the beetles). Should be something like this:
Code:
USB> rtask b <--- go into AT command interface
ate1 <--- type this to enable local echo
atv1 <--- type this to enable verbose output
[email protected]=0,1,code <--- replace "code" with your MSL
[email protected]=0,2,code
[email protected]=0,4,code
[email protected]=0,8,code
[email protected]=0,16,code
[email protected]=0,32,code
[email protected]?40
If the last command returns simlock=00 means it's unlocked, other vaule means is still locked.
No need to reset the counter

[email protected] Doesn't work
Hi,
Thank for your reply but it doesn't work :
[email protected] doesn't seem to be implemented :
USB>h rtask
Usage:
rtask [Type [Value]]
Type(hex) 0: Reset radio and [value](hex) is ignore.
Type(hex) 1: Turn on radio, lease use type 3 and 4 instead.
Type(hex) 2: Turn off radio and [value](hex) is ignore.
Type(hex) 3: Run radio image and [value](hex) is ignore.
Type(hex) 4: Run radio bootloader and [value](hex) is ignore.
Type(hex) 7: Radio AT Command Debug.
Type(hex) 8: GSM trace route.
Type(hex) 9: Run radio external bootloader and [value](hex) is ignore.
Type(hex) A: Radio image flash by external bootloader and [value](hex) is ignore.
Type(hex) C: Select debug path.
Type(hex) D: Radio AT Command with GSM trace route.
Type(hex) 10: Set radio external boot UART mode(fast(1)/normal(0)).
USB>rtask 7
Radio AT command debug.
Wait 177 ms
ATCmd Version 0.1
CAIF Init Done
ate1
0
atv1
aatv1
OK
[email protected]?40
[email protected]?40
ERROR
[email protected]?40
[email protected]?40
ERROR
[email protected]?40
[email protected]?40
ERROR
ati
aati
Ericsson Mobile Platform
OK
And when i trie [email protected]=0, facility(0 to 32), unlocking code => ERROR
I've tried with the first ROM 1.05 and the last 1.23, with the 1.23 the help for rtask disappear!
Does Someone know another methode or command to accomplish my unlocking action? Please I gonna be crazy, I've left my ipaq running simlock 7 days and Validation button stay grey!! I've reset to test [email protected] without success

ouch, then hw6515 bootloader is different from what I've seen previously....

hw6515a locked
i have the same problems for months. my hw6515a 22 times. and i cannot have the button ok enabled. i cannot reset it. im still fresh on the boat. i downloaded the mtty.exe but i dont know how to use it. how to get my fone in the bootloader. Pof. you genius. plz show me how to unlock this fone. or reset the simlock count back. many thanks. Andrew. [email protected]

pof said:
Go into bootloader using mtty.exe, you need to access AT command interpreter, in some htc devices this is done by command 'rtask 7' on others is 'rtask b' (I don't know on the beetles). Should be something like this:
Code:
USB> rtask b <--- go into AT command interface
ate1 <--- type this to enable local echo
atv1 <--- type this to enable verbose output
[email protected]=0,1,code <--- replace "code" with your MSL
[email protected]=0,2,code
[email protected]=0,4,code
[email protected]=0,8,code
[email protected]=0,16,code
[email protected]=0,32,code
[email protected]?40
If the last command returns simlock=00 means it's unlocked, other vaule means is still locked.
No need to reset the counter
Click to expand...
Click to collapse
The bootloader are totally different, maybe the one that your are testing is on ipaq 6365...CMIIWW thanks

do HARD-RESET, that what i did to my H6515 USA version

Need a little help I am new with Ipaq 6515 but have unlocked other PDA and Pocket pcs, one thing how to put 6515 in bootmode and also how to hard reset it please can any one help.
thanks
bcnboy

need too to reset simlock counter.. this also can unlock beetles devices??

Hi all. I have the hw6515 spanish, sim locked, and french, without sim lock. Iz it possible to make both english and unlock it???

How to reset unlock codes counter on HP 6515a?
How can I manage connection with mtty.exe and device. Because there is not any COM ports emulated by AS.

Pof - a little help with X01HT
Hi - this worked on the HTC Hermes (I have X01HT)
Before i started - [email protected]?40 - returned - 01
I then ran [email protected]=0,1,code (code= the code I bought off a member here)
Then [email protected]?40 - returned - 00 (unlocked)
Thanks heaps

lemming77 said:
Hi - this worked on the HTC Hermes (I have X01HT)
Before i started - [email protected]?40 - returned - 01
I then ran [email protected]=0,1,code (code= the code I bought off a member here)
Then [email protected]?40 - returned - 00 (unlocked)
Thanks heaps
Click to expand...
Click to collapse
I think i need help with this. In mtty i get command error!!! all the time. Maybe I need to get the password? bootloader_pwn3d.pdf doesnt help.
I have my code, I just need to know how to input it. I have HardSPL installed maybe I will try flashing another rom to input the code?

How to apply to elf
dear sir
HOW TO APPLY TO ELF & what is Msl that will be inserted instead of code

Cant reset hermes
Khianto said:
The bootloader are totally different, maybe the one that your are testing is on ipaq 6365...CMIIWW thanks
Click to expand...
Click to collapse
DOES ANYONE KNOW HOW TO RESET COUNTS ON HERMES I TRIED LIKE THIS WITHOUT ANY RESULT
task 32
Level = 0
Cmd>28
Command error !!!
Cmd>task 32
Level = 0
Cmd>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 13
Storage start block: 464
Storage Total block: 472
Total Bad Block in CE: 0
NeedToEraseBlockStart: 477
Storage format success
Cmd>task b
Cmd>task 7
Cmd>task b
Cmd>rtask b
Command error !!!
Cmd>rtask 7
Command error !!!
Cmd>task 7
Cmd>ate 1
Command error !!!
Cmd>ave 1
Command error !!!
Cmd>rask ave 1
Command error !!!
Cmd>task ave1
Cmd>task ate 1
Cmd>USB hrtask
Command error !!!
Cmd>hrtask
Command error !!!
Cmd>h rtask
Command error !!!
Cmd>task h rtask
Cmd>USB> rtask b
Command error !!!
Cmd>rtask b
Command error !!!
Cmd>rtask 7
Command error !!!
Cmd>'rtask b'
Command error !!!
Cmd>rtask 7'
Command error !!!
Cmd>[email protected]=0,1,code <--- replace "code" with your MSL
[email protected]=0,2,code
[email protected]=0,4,code
[email protected]=0,8,code
[email protected]=0,16,code
[email protected]=0,32,code
[email protected]?40
Cmd>
Cmd>[email protected]=0,1,00000000
Command error !!!
Cmd>simlock=00
Command error !!!
NO USB JUST CMD BUT I READ IT WAS THE SAME THING.
THANK YOU ANYONE WHO KNOWS OR HOW TO DOWNGRADE SPL 1.4 OLIPRO TO 1.04 I HAVE SIM LOCKED 18 TIMES THX. AND I HAVE THE CODE.
AND ANYONBE KNOWS HOW MANY TIME I HAVE TO WAIT FOR OK BOTTON? OR IT CANT BE DONE

Adb error...

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Tfj4>adb shell
adb server is out of date. killing...
CreateProcess failure, error 2
* failed to start daemon *
error:
C:\Users\Tfj4>
Click to expand...
Click to collapse
Any thoughts???Does that with every command

Have you recently upgraded your Android Development Tools (ADT)???
Not sure what causes it but I seen a fix in this thread
http://forum.xda-developers.com/showthread.php?p=4822780

I have the same problem, updating the SDK didn't help. I've been digging through the internet long and wide and haven't found a solution.

Install ADB on Windows & ubuntu 12.04 or 12.10

If you need to flash ROM even using fastboot for Smartphone or Tablet in which they use Android OS! Then Ubuntu OS is needed!
This is a guide I made for ubuntu users and included a guide for windows users to setup Android SDK which contains ADB.
Android Debug Bridge (ADB) provides a terminal interface on your PC to interact with your device's file system. This can be useful for many things like installing & uninstalling apps, logcat, backup & restore, and hacking your device just to name a few.
ubuntu 12.04 & 12.10 Guide
1. Go here and download android-sdk (not the adt-bundle)....
https://hotfile.com/dl/241406263/5e6a306/android-sdk_r22.0.5-linux.tgz.html
2. Place the downloaded file in your home folder and then extract it and you should get a folder named android-sdk-linux (do not rename it).
3. If you’re on a 64bit machine run these commands in terminal to make sdk compatible with 64bit (if you’re on 32bit machine then skip this step)....
sudo apt-get update
sudo apt-get install ia32-libs-multiarch
4. Run this command in terminal to install jdk if you don’t have it already....
sudo apt-get install openjdk-6-jdk
5. Navigate to the home folder where you extracted android-sdk-linux and open the folder then open the folder named tools
6. Inside the tools folder there will be a file named android... double click it and select run then android sdk manager will open.
7. In the center pane deselect everything... Now only select the following....
Android SDK Tools
Android SDK Platform-tools
Android Support Library
8. Once selections have been made click on install packages and wait till finished.
9. Upon completion of step 8 in terminal run this command....
sudo gedit ~/.bashrc
When the file opens, go to the very bottom and copy/paste the following 3 lines (make sure they’re each on separate lines)....
# Android tools
export PATH=${PATH}:~/android-sdk-linux/tools
export PATH=${PATH}:~/android-sdk-linux/platform-tools
10. Now reboot your computer.
11. Set your phone to usb debugging then plug it to your pc after pc is done booting
12. Open a terminal on your pc and enter....
adb devices
If all went well, you should see your phone’s serial number and you’ll be ready to go.
~~~~~Important~~~~~
You can use steps 5 & 6 to open Android SDK Manager & update your ADB/SDK installation. Only select your installed packages then update.

Also if you only need the fastboot/adbtools:
sudo add-apt-repository -y ppa: phablet-team/tools
Note: delete the space after"-y ppa:" -xda creates smileys like ppa
sudo apt-get update
sudo apt-get install -y phablet-tools
Sent from my Nexus 4 using xda app-developers app

Thank...
gazhead said:
Also if you only need the fastboot/adbtools:
sudo add-apt-repository -y ppa: phablet-team/tools
Note: delete the space after"-y ppa:" -xda creates smileys like ppa
sudo apt-get update
sudo apt-get install -y phablet-tools
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks man! It's also good way!

Followed this guide (thank you for posting) but couldn't connect. Scratched around and found I needed to create a new file in /etc/udev/rules.d with:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="<4-char_verndorID>", ATTR{idProduct}=="4-char_productID", MODE="0666", OWNER="username"
Followed by:
Code:
sudo restart udev
Then plugged device in and it worked!

qtoon said:
Followed this guide (thank you for posting) but couldn't connect. Scratched around and found I needed to create a new file in /etc/udev/rules.d with:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="<4-char_verndorID>", ATTR{idProduct}=="4-char_productID", MODE="0666", OWNER="username"
Followed by:
Code:
sudo restart udev
Then plugged device in and it worked!
Click to expand...
Click to collapse
What did you name the new file you created? Or did you add this string to another existing file from the rules.d directory? I'm not sure what I've done wrong, but I get
Code:
[email protected]:~$ adb devices
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'dab' from package 'bsdgames' (universe)
Command 'zdb' from package 'zfs-fuse' (universe)
Command 'kdb' from package 'elektra-bin' (universe)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'jdb' from package 'openjdk-7-jdk' (universe)
Command 'ab' from package 'apache2-utils' (main)
Command 'ad' from package 'netatalk' (universe)
adb: command not found
[email protected]:~$
This is after following each step, adding the three lines to the end of .bashrc and rebooting.

atmu5fear said:
What did you name the new file you created? Or did you add this string to another existing file from the rules.d directory? I'm not sure what I've done wrong, but I get
Code:
[email protected]:~$ adb devices
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'dab' from package 'bsdgames' (universe)
Command 'zdb' from package 'zfs-fuse' (universe)
Command 'kdb' from package 'elektra-bin' (universe)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'jdb' from package 'openjdk-7-jdk' (universe)
Command 'ab' from package 'apache2-utils' (main)
Command 'ad' from package 'netatalk' (universe)
adb: command not found
[email protected]:~$
This is after following each step, adding the three lines to the end of .bashrc and rebooting.
Click to expand...
Click to collapse
@atmu5fear, inferring that you're new to Linux (a common background for all), some notes:
Unlike wlth Win-d'oh-s, there is a worldwide development community that's always working toward improvement of every aspect of the system, including echoed messages and documentation. You may have to shake off the tendency to ignore Windudz messages, which are frequently unhelpful. Linux command echoes are much more on-target. Also, look for files such as README in rules.d and read it!
Now before creating a new config file (which may not be necessary on your system), see the top feedback line: "No command 'adb' found." First, see that the adb binary is present and that it has exec permission. (Since it's a small file and functions alone, I prefer to copy it to the folder I'm working from.)
If it then runs but won't connect, read on...
Directory (or "folder") names with a trailing '.d' are special: They configure, control, or provide executables for daemons (programs which run continuously, providing a service).
Within service-config.d folders, if the service steps through the files sequentially (as in this case), then it does so based on each filename. (True except for the special case of rc.d, iIRC, in which order is set by the special program rcorder).
So in this case, for example, since the existing files are named 70-whatever, your newly-created file could be 80-atmu5fears-phone to load after the others.
Should connect.

qtoon said:
@atmu5fear, inferring that you're new to Linux (a common background for all), some notes:
Unlike wlth Win-d'oh-s, there is a worldwide development community that's always working toward improvement of every aspect of the system, including echoed messages and documentation. You may have to shake off the tendency to ignore Windudz messages, which are frequently unhelpful. Linux command echoes are much more on-target. Also, look for files such as README in rules.d and read it!
Now before creating a new config file (which may not be necessary on your system), see the top feedback line: "No command 'adb' found." First, see that the adb binary is present and that it has exec permission. (Since it's a small file and functions alone, I prefer to copy it to the folder I'm working from.)
If it then runs but won't connect, read on...
Directory (or "folder") names with a trailing '.d' are special: They configure, control, or provide executables for daemons (programs which run continuously, providing a service).
Within service-config.d folders, if the service steps through the files sequentially (as in this case), then it does so based on each filename. (True except for the special case of rc.d, iIRC, in which order is set by the special program rcorder).
So in this case, for example, since the existing files are named 70-whatever, your newly-created file could be 80-atmu5fears-phone to load after the others.
Should connect.
Click to expand...
Click to collapse
Thanks @qtoon for the reply. I'm not really new to Ubuntu, albeit, it's been a while. First started using it just prior to the realease of Hardy Heron 8.04 LTS. That being said I am certainly no expert, but am somewhat familiar and comfortable with the command line. I did read the README file before posting, but since I'm not all that familiar with configuration files and the like, I figured maybe I should ask.
As per your suggestion i moved the ADB binary to my home folder, not necessarily my working folder, but to test to see if the adb command would be recognized in terminal.
Code:
mv ~/ADB/android-sdk-linux/platform-tools/adb ~/
Still got same result so I moved it back, then went on to make a new file and add the suggested string
Code:
sudo > /etc/udev/rules.d/80-atmu5fear-adb
sudo gedit /etc/udev/rules.d/80-atmu5fear-adb
After saving and restarting udev I still get the same "adb command not found" error.
I then changed the string to read OWNER"atmu5fear" instead of "username", still nothing
Any more suggestions?
Thanks
atmu5fear

Sorted it out
instead of:
adb devices
i needed to input:
./adb devices
It's listed, and in order to use the adb shell:
./adb shell
once in the shell all adb commands work

I get this error...
[email protected]:~$ sudo > /etc/udev/rules.d/80-sjy-phone
bash: /etc/udev/rules.d/80-sjy-phone: Permission denied
ok....... didn't need to add a file, changed phone usb mode to media device and all is ok.
thanks

atmu5fear said:
Sorted it out
instead of:
adb devices
i needed to input:
./adb devices
It's listed, and in order to use the adb shell:
./adb shell
once in the shell all adb commands work
Click to expand...
Click to collapse
Didn't think to mention that, apologies.
Quick 'why' on the ./ here.
Glad you got it running.

Just tried on 14.4 and worked like a charm.
Note: No need to reboot the computer, just reload the bash config with
Code:
source ~/.bashrc

Thanks
A good step by step guide
i will try it and see if it works
Thanks again

Hello, can someone help me ? - I m having problems connecting my device with adb (I ve connected several other devices before with no problems).
I ve got an Allwinner A20 tv box, it worked fine for a few months then one day, after being on (but idle) for a few hours, I noticed the screen was blank but the light on the front was blue (indicating it was on, red is standby). It would not respond to the remote control or to anything, so I unplugged it and since then it will not boot and the screen is blank, the red light will light up but that is it. I ve eliminated the remote controller not working, but I cant boot the device.
So I ve tried connecting via ADB (with Ubuntu) but I cant get the device to show up after typing "adb devices".
Using this guide:
http://androidonlinux.wordpress.com/2013/05/12/setting-up-adb-on-linux/
I can get the vendor id and device id and I ve added it and the manufacturer to udev/modeswitch devices, but when I type "sudo usb_modeswitch -v 0x1f3a -p 0xefe8 -S -R -W"
I get the following error:
~/Android/sdk/platform-tools$ sudo usb_modeswitch -v 0x1f3a -p 0xefe8 -S -R -W
Take all parameters from the command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 2.1.1 (C) Josua Dietze 2014
* Based on libusb1/libusbx
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x1f3a
DefaultProduct= 0xefe8
SierraMode=1
NeedResponse=0
Look for default devices ...
found USB ID 048d:1336
found USB ID 1d6b:0002
found USB ID 19a8:2036
found USB ID 1f3a:efe8
vendor ID matched
product ID matched
found USB ID 1d6b:0001
found USB ID 062a:0102
found USB ID 1d6b:0001
Found devices in default mode (1)
Access device 004 on bus 003
Current configuration number is 1
Use interface number 0
USB description data (for identification)
-------------------------
Manufacturer: not provided
Product: not provided
Serial No.: not provided
-------------------------
Send Sierra control message
Error: Sierra control message failed (error -7). Abort
I ve searched Google for the error code but I cannot find anything.
The device was rooted and USB debugging was on.
Any help would really be appreciated.
Thanks

[Q] Cannot get root on Xperia Z1

I've been trying this for most of the day, having read everything here about doing it, and even watching the video.
Unfortunately, I let the phone update to 14.1.G.2.257, but I found the instructions on how to flash back to the previous 1.534. The flashing worked perfectly.
I am trying to use Root_with_Restore_by_Bin4ry_v32 having read how to and watched the tutorial. USB debugging is enabled, as is Unknown Sources, and the 'adb devices' command in the stuff folder of the aforementioned program lists the phone.
However, it does not seem to work. I get the following output:
Code:
C:\xpe>runme
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (20.11.2013) v32 =
======================================================================
Device type:
0) Xperia Z1 14.1.G.1.534 Root by cubeundcube
1) New Standard-Root (thx Ariel Berkman)
2) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
3) Old
4) Old-Special (for example: Sony Tablet S, Medion Lifetab)
G) Google Glass Mode (thx Saurik for the ab file)
x) Unroot
Make a choice: 0
Please connect your device with enabled USB-Debugging ...
Copy needed files ...
error: protocol fault (no status)
2881 KB/s (2242263 bytes in 0.760s)
error: protocol fault (no status)
error: protocol fault (no status)
133 KB/s (1230 bytes in 0.009s)
error: protocol fault (no status)
Unable to chmod /data/local/tmp/busybox: No such file or directory
Running Exploit
error: protocol fault (no status)
rm failed for /data/local/tmp/getroot, No such file or directory
error: protocol fault (no status)
error: protocol fault (no status)
Rebooting now, after reboot all should be done!
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
The phone reboots, but there is no SuperUser app. I have re-run the program many times, reflashed the stock firmware again to make sure, and banged my head against my desktop several times to no avail.
Please help...
Rick.

Have you enabled usb debugging
have you allowed unkoown sources
Have you installed drivers
please send a screen shot of your about phone in the settings

gregbradley said:
Have you enabled usb debugging
have you allowed unkoown sources
Have you installed drivers
please send a screen shot of your about phone in the settings
Click to expand...
Click to collapse
Yes thanks, USB debugging and unknown sources are enabled. Is this the screenshot you need to see?
**Edit**
I got it to work!
I just pulled out my laptop which had a clean install of Windows 7 as of a few days ago, installed the above stuff (plus ADB drivers from pdanet) on that, and it worked.
Why it didn't work on my main PC I have no idea, but it is probably an issue with some driver somewhere messing things up. I did try reinstalling all of them, but to no avail.
Anyway, got it now. Thanks!

[how to]lock/unlock your bootloader without htcdev(s-off required)

READ THIIS!
*this thread is for desire 510. it will NOT work on m7,or any older device. please check the general forum for your particular device for a similar thread.
this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or unlocked back to stock.
advantages
-no hassle with htcdev,tokens,or unlock codes
-no submitting your phones personal info to htc
-the ability to get back to 100% stock without any visual traces or records of having been s off or unlocking your bootloader.
*you must be s off.
*you must have superuser installed
read this:
this will not work if your s on. its not a way to magically unlock
the usual disclaimers:
use this info at your own risk. if it melts your phone into a little pile of plastic goo,its not my fault.
credits
-beaups for schooling me on echo comand protocol
-strace for originally discovering the location of the lock status flag(check out this thread for more info)
*i have tested this on my gsm cricket desire 510 variant(a11_ul). let me know if you try it on a different variant,or if youd like to dump partitions and have me take a look
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and older)
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "lock status flag"
to LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now locked
_____________________________________________________________________________________________
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now unlocked
other useful threads:
remove your tampered banner: http://forum.xda-developers.com/desire-510/general/how-to-remove-tampered-banner-t3179866

mine too