[how to] remove your "tampered" banner - HTC One Max

if you have recently s-off'ed using a java card,or some other exploit that did not remove your tampered banner from the bootloader screen,then this thread is for you.
prerequsites:
*you must be s off.
*you must have superuser installed(see this thread if you need help installing superuser)
read this:
this will not work if your s on
the usual disclaimers:
i have tested this my my m7_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.
it has been successfully tested on t6ul with MID 0P3P51000. i feel it is safe for other t6ul users,all MIDs,however,you are welcome to dump and we can verify the flag locations if you have concern.
if you have a different variant than t6ul,please pm me for more info prior to trying this.
credits
-beaups for giving me the echo comand,so yall didnt need to dump,edit with a hex editor,and copy back
-andybones for testing it on m7_wlv
*pradeepvizz for getting the ball rolling for t6 users-dumping partitions,testing commands and providing screenshots. make sure to give him a big thanks
*Murrda and Jiggity Janx for providing the dumps that located the flag for vzw variants.
*Murrda for testing on t6whl
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
-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 "tampered" flag
verizon users:
enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265989
(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
everyone else:
enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
(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
how to lock/unlock without htcdev

---

Thanks mate works perfectly fine on mine LOL!!!

---

scotty1223 said:
if you have recently s-off'ed using a java card,or some other exploit that did not remove your tampered banner from the bootloader screen,then this thread is for you.
prerequsites:
*you must be s off.
*you must have superuser installed(see this thread if you need help installing superuser)
read this:
this will not work if your s on
the usual disclaimers:
i have tested this my my m7_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.
it has been successfully tested on t6ul with MID 0P3P51000. i feel it is safe for other t6ul users,all MIDs,however,you are welcome to dump and we can verify the flag locations if you have concern.
if you have a different variant than t6ul,please pm me for more info prior to trying this.
credits
-beaups for giving me the echo comand,so yall didnt need to dump,edit with a hex editor,and copy back
-andybones for testing it on m7_wlv
*pradeepvizz for getting the ball rolling for t6 users-dumping partitions,testing commands and providing screenshots. make sure to give him a big thanks
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
-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:
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 "tampered flag"
enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
(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
how to lock/unlock without htcdev
Click to expand...
Click to collapse
Will this work for HTC butterfly s
Sent from my HTC Butterfly s using xda premium

---

daorderdillon said:
Will this work for HTC butterfly s
Sent from my HTC Butterfly s using xda premium
Click to expand...
Click to collapse
is your device s off?

---

scotty1223 said:
is your device s off?
Click to expand...
Click to collapse
It worked
Sent from my HTC Butterfly s using xda premium

---

daorderdillon said:
It worked
Sent from my HTC Butterfly s using xda premium
Click to expand...
Click to collapse
if you ran the command above without knowing what lived in the location its writing to,that was an extremely stupid move. you could have easily overwrote somethign important and been left with anything from simply not working,to bootloops,to a hard bricked device.
you are lucky it appears to have been the same,and your impatience did not leave you with an expensive paperweight. hopefully you will not rush into things like this in the future,as i was perfectly willing to make sure it was safe before yuo did it.

---

scotty1223 said:
if you ran the command above without knowing what lived in the location its writing to,that was an extremely stupid move. you could have easily overwrote somethign important and been left with anything from simply not working,to bootloops,to a hard bricked device.
you are lucky it appears to have been the same,and your impatience did not leave you with an expensive paperweight. hopefully you will not rush into things like this in the future,as i was perfectly willing to make sure it was safe before yuo did it.
Click to expand...
Click to collapse
Its a device wihth the same specs and almost same hardware what's the big difference
Sent from my HTC Butterfly s using xda premium

---

daorderdillon said:
Its a device wihth the same specs and almost same hardware what's the big difference
Sent from my HTC Butterfly s using xda premium
Click to expand...
Click to collapse
those things dont gaurantee that things are in the same spots. im glad it worked out for you,but you were lucky. remember s off is letting you do whatever you want,including brick your device if youre not careful

---

scotty1223 said:
those things dont gaurantee that things are in the same spots. im glad it worked out for you,but you were lucky. remember s off is letting you do whatever you want,including brick your device if youre not careful
Click to expand...
Click to collapse
Well we need stuff on the HTC butterfly S forum and we aint getting any so if I cud find a way to get some stuff I will or do u wanna do it
Sent from my HTC Butterfly s using xda premium

---

Worked on Sprint HTC One Max Thanks a ton!

---

Now is the time for everyone who has not donated to the great devs we have to break out their paypal! This initial great group of devs are helping us all out by creating a foundation for rom/kernel/whatever devs to provide us their magic from now on. Without these guys laying the framework none of that would be possible. Remember that we are very lucky that this mostly obscure device is getting the fabulous development support it is at this time. So show your support and DONATE!!

---

Scotty1223 this did not work for me on my Verizon HTC One Max.... ;-( boohoo lol
Any suggestions on what I can do to get rid of the tampered flag? My Verizon HTC One Max may have been the first Vzw with s-off and unlock but I could be wrong.. I let Beaups take over my Macbook and Max for a few hours and he went to town with the rumrunner tool to get it all set up and working right... I don't care if the "Tampered" is there but if I can get rid of it I will...
Let me know if there is anything that you need me to do for you to get it to work on the Vzw variant! Thanks my dude!!
---------- Post added at 11:35 AM ---------- Previous post was at 11:31 AM ----------
Oh so here was the output from terminal after running your command.......
Pauls-MacBook-Pro:~ paul$ adb shell
[email protected]:/ $ su
[email protected]:/ # echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
1+0 records in
1+0 records out
1 bytes transferred in 0.007 secs (142 bytes/sec)
[email protected]:/ # exit
[email protected]:/ $ exit
Pauls-MacBook-Pro:~ paul$ adb reboot bootloader
Could this be which I just noticed right now that it is "t6wl" and not "t6ul" ?? The phone booted up no problems, so far.... lol..... Fingers crossed! Everything seems to be working i.e: calls, data, etc etc

---

Murrda said:
Scotty1223 this did not work for me on my Verizon HTC One Max....
Could this be which I just noticed right now that it is "t6wl" and not "t6ul" ?? The phone booted up no problems, so far.... lol..... Fingers crossed! Everything seems to be working i.e: calls, data, etc etc
Click to expand...
Click to collapse
I linked him to some partitions I pulled at his request yesterday. t6wl must be the Verizon version cause that's what mine says as well. I think he would like to work with you because I don't appear to have the tampered flag.
"In case you need them:
adb shell
su (if you need to to get a #)
dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6
dd if=/dev/block/mmcblk0p7 of=/sdcard/mmcblk0p7
exit
youll find the files on your (internal) sd card
Just upload them somewhere and send (him) the links"

---

So you were able to move your "Tampered" flag on the Vzw? Yeah ill get them and upload in a few moments
Jiggity Janx said:
I linked him to some partitions I pulled at his request yesterday. t6wl must be the Verizon version cause that's what mine says as well. I think he would like to work with you because I don't appear to have the tampered flag.
"In case you need them:
adb shell
su (if you need to to get a #)
dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6
dd if=/dev/block/mmcblk0p7 of=/sdcard/mmcblk0p7
exit
youll find the files on your (internal) sd card
Just upload them somewhere and send (him) the links"
Click to expand...
Click to collapse

---

Murrda said:
So you were able to move your "Tampered" flag on the Vzw? Yeah ill get them and upload in a few moments
Click to expand...
Click to collapse
There doesn't appear to be a visible tampered flag for me. That's why he was looking for someone that had one visible to provide those partitions.

---

Thanks,I would like to see them. Pm me some links wen you get them uploaded.
Sent from my HTC first using Tapatalk

---

Murrda said:
Yeah ill get them and upload in a few moments
Click to expand...
Click to collapse
any luck?

---

Yo I sent you the links in a PM, let me know what's good! Thanks!!
scotty1223 said:
any luck?
Click to expand...
Click to collapse

---

scotty1223 said:
any luck?
Click to expand...
Click to collapse
If it helps any I think I do have the 'tampered ' banner while booting into recovery. Surprisingly enough I only barely caught. Haven't tried removing the lock and tamper yst.

---

Murrda said:
Yo I sent you the links in a PM, let me know what's good! Thanks!!
Click to expand...
Click to collapse
check your pms,let me know what happens
Jiggity Janx said:
If it helps any I think I do have the 'tampered ' banner while booting into recovery. Surprisingly enough I only barely caught. Haven't tried removing the lock and tamper yst.
Click to expand...
Click to collapse
if your refering to the red "this build is for development purposes blah blah " text,that comes from running a custom recovery and/or kernel. i believe it is hboots reaction to finding an inappropriate signiture for one of those partitions. with other devices folks are hex editing the text to spaces, or using the regaw bootloader modifier tool to elimiate it(someone(not me) would have to make you a plug in for that tool to work).