[One (M8) General] scotty1223:
*this thread is for m8. it will NOT work on m7(or anything older). search your device general forum for a specific thread

if you have recently s-off'ed using an exploit that did not remove your tampered banner from the bootloader screen,then this thread is for you.

*note: if you are on hboot 3.19.0.0000 this thread will change software status: modified banner to: software status: official. to my knowledge,this

banner is not completely removable

(more info)

you do

NOT

need to downgrade your hboot. this simple adb command works without any scary hboot downgrades.

*you must be s off.

*you must have superuser installed

read this:

this will not work if your s on

the usual disclaimers:

i have tested this my my m8_ul t mobile variant,but use this info at your own risk. if it melts your phone into a little pile of aluminum goo,its not my fault.

credits

-beaups for schooling me on echo command protocol

-andybones for testing it on m7_wlv

*WorldIRC and brar.arsh for testing on m8

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 lower)

-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:

this process,in your cmd window,should look something like this:

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 "tampered flag"

enter the following:

adb devices

adb shell

su (if needed to get a # prompt)

echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564

(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 tamered is gone :)

your cmd window should look like this(red= my inputs,blue=additional comments):

c:\miniadb_m8>[COLOR="Red"]adb shell[/COLOR]
shell@htc_m8:/ $ su
su
root@htc_m8:/ # [COLOR="red"]echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564[/COLOR]
ock/mmcblk0p6 bs=1 seek=5314564 <
1+0 records in [COLOR="Blue"][COLOR="red"]adb reboot bootloader[/COLOR]

c:\miniadb_m8>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...

finished. total time: 0.022s

c:\miniadb_m8>

other useful threads:

lock/unlock without htcdev: http://xdaforums.com/showthread.php?t=2708571

change mid without eng hboot: http://xdaforums.com/showthread.php?t=2708581

if this does not work for you

*first reread this thread in its entirety. make sure you have met the prerequisites,and double check your code and make sure you have not forgotten a step,or screwed something up trying to type it (especially if using a terminal emulator),and check that you have not gotten any errors.

if youre still confident you did things correctly,you need to PM me:

1)the results of: fastboot getvar all

2)a link to an uploaded p6.

you get fastboot getvar all by:

-place phone in fastboot

-enter in fastboot getvar all right click,click mark,highlight in white,hit enter or right click to copy

you dump p6 by:

adb shell

su (if needed to get a #)

dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6

transfer the file on internal storage to your pc and upload it

im not trying to be a ****,but its not helpful to post "didnt work" if you screwed something up,or if your not willing to help find a solution. especially if others have found it to work on their same variant.

important:

from now on,i will need a copy of your cmd window as well if we want to get to the bottom of whats happening. some folks seem to be simply writing extra bytes,wich is screwing up the flag location. please make sure this shows an entire session,not just a last part where it looks correct. we cant figure it out if you only show part of what you did.

if you have other questions:

first and foremost:

DO NOT quote this post in its entirety. doing so will result in your questions being ignored

next:

please search the thread for answers before blindly jumping to the end and posting. by now its unlikely that you have experienced a unique issue