Yeah, I don't care that much about the tampered tag. Just noticed that it came back.
Sent from my HTC6435LVW using Tapatalk 2
Sent from my HTC6435LVW using Tapatalk 2
[how to]reset your lock status flag
- Thread starter scotty1223
- Start date
-
- Tags
- development
Me? I don't have this device. Other s off devices I've run stock and custom ROMs/kernels. I most always have a custom recovery installed.
With s off,Once gone,I've never had tampered reappear no matter what kernel/recovery I have.
Sent from my ADR6425LVW using Tapatalk 2
thats strange... cause as soon as i unlocked and put a custom recovery on it it would say tampered/unlocked no matter what
what about CID-11111111 on the screen?
If we are talking strictly about getting the bootloader screen back to what it looked like stock, in case someone checks, what about getting the CID blurb gone? When I was stock, there wasn't even a CID on the screen. Now there is CID- 11111111 or CID-22222222. Just asking. Is there a way to change the CID back to what it was?
If we are talking strictly about getting the bootloader screen back to what it looked like stock, in case someone checks, what about getting the CID blurb gone? When I was stock, there wasn't even a CID on the screen. Now there is CID- 11111111 or CID-22222222. Just asking. Is there a way to change the CID back to what it was?
Yes, the oem write_cid command allows you to revert cid to any value you want (as long as you have s-off or super cid). I think the Verizon cid is vzw__001 or something like that, but I'm not sure so make sure to verify that before trying it. Although users have reported that Verizon doesn't really care about s-off and unlock, so you probably will be fine leaving it with super cid.
Changing cid back to VZW__001 is part of the back to stock process. The cid is only displayed when s off. When you turn s back on,it will disappear.
Sent from my HTC PG09410 using Tapatalk 2
Sent from my HTC PG09410 using Tapatalk 2
No space... "Writesecureflag 3"
If you need to get back to 100% stock use this guide: http://androidforums.com/showthread.php?t=691213
Just make sure to use a DNA ruu not a one s ruu
Sent from my HTC One XL using Tapatalk 2
No space... "Writesecureflag 3"
If you need to get back to 100% stock use this guide: http://androidforums.com/showthread.php?t=691213
Just make sure to use a DNA ruu not a one s ruu
Sent from my HTC One XL using Tapatalk 2
Lol I know. I figured it out lastnight. Thanks for both of the threads. Very helpful.
RATTLED FROM MY ONE XL USING ICS TAPATALK 2
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
13first and formost special thanks CastleBravo,without whos testing and help in this thread,this would not have happened so quickly. he asked all the right questions,and gave others all the right answers while i was at work and couldnt respond. also to treadwayj,who dumped mmcblk0p3 from his still locked phone for comparison,providing valuable confirmation.
since the current s-off method is not resetting the "lock status" flag,i thot there would be a need for this.
i happened across this thread inthe gsm evo 3d forum: http://xdaforums.com/showthread.php?t=1970252 and found it to work on the rezound,inc 4g,sensation 4g,cdma evo 3d,MT4GS,Amaze 4g,one s,droid DNA,and prolly several others.
this does NOT mean you can unlock your bootloader without going thru htcdev. all this means,is that if your bootloader is unlocked after s-off,you can get rid of the relocked watermark and get back to 100% locked prior to s-on for legitimate warranty purposes.
ive always been unlocked. for S&Gs,i dumped mmcblk0p3 and found the described "HTCU" at 0x8404. changed it to 0x00000000 and voila! back to locked
afterward,relfashed my origianl mmcblk0p3,wich brought me back to unlocked with no getting or flashing tokens.
this is NOT a patched or hex edited hboot.again,this is ONLY to get back your original ***locked*** status.
*this is for s-off phones only
2 ways to do it:
1)old school
this assumes you to have drivers,adb/fastboot,a hex editor,a fair understanding about what youre doing,and the ability to follow directions on the linked thread
Code:Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Scott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR] c:\mini-adb_vigor>[COLOR="red"]adb devices[/COLOR] * daemon not running. starting it now * * daemon started successfully * List of devices attached HTxxxxxxxxxx device c:\mini-adb_vigor>[COLOR="Red"]adb shell[/COLOR] shell@android:/ $ [COLOR="red"]su[/COLOR] su shell@android:/ # [COLOR="red"]dd if=/dev/block/mmcblk0p3 of=/sdcard2/mmcblk0p3[/COLOR] dd if=/dev/block/mmcblk0p3 of=/sdcard2/mmcblk0p3 64734+0 records in 64734+0 records out 33143808 bytes transferred in 9.519 secs (3481858 bytes/sec) shell@android:/ # [COLOR="red"]exit[/COLOR] exit shell@android:/ $ [COLOR="red"]exit[/COLOR] exit c:\mini-adb_vigor>[COLOR="red"]adb pull /sdcard2/mmcblk0p3[/COLOR] 2292 KB/s (33143808 bytes in 14.116s) [COLOR="Blue"]*modify mmcblk0p3 with a hex editor[/COLOR] c:\mini-adb_vigor>[COLOR="Red"]adb push mmcblk0p3mod /sdcard2/mmcblk0p3mod[/COLOR] 2478 KB/s (33143808 bytes in 13.059s) c:\mini-adb_vigor>[COLOR="red"]adb shell[/COLOR] shell@android:/ $ [COLOR="red"]su[/COLOR] su shell@android:/ # [COLOR="red"]dd if=/sdcard2/mmcblk0p3mod of=/dev/block/mmcblk0p3[/COLOR] dd if=/sdcard2/mmcblk0p3mod of=/dev/block/mmcblk0p3 64734+0 records in 64734+0 records out 33143808 bytes transferred in 18.937 secs (1750214 bytes/sec) shell@android:/ #[COLOR="red"] exit[/COLOR] exit shell@android:/ $ [COLOR="red"]exit[/COLOR] exit c:\mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR] c:\mini-adb_vigor>
2)noob friendly
-download the appropriate zips,place on sd card.
-boot to recoverywipe cache/dalvik
-flash in recovery. i recomend to run query first,to make sure its working. tested on my personal one s,amaze,jetstream,rezound,inc) 4g,sensation,MT4GS,and gsm evo 3d. tested by castlebravo on DNA.
query:query_bootloader.zip
query_bootloader.zip f335f78f9f46469c823da0c671026de5
unlock:unlock_bootloader.zip
unlock_bootloader.zip f335f78f9f46469c823da0c671026de5
lock:lock_bootloader.zip
lock_bootloader.zip f335f78f9f46469c823da0c671026de5
a little bit of explanation. yes,the md5s are all the same. its the same file,just named differently. the script behaves based on the name of the zip. i knew if i only included 1 download and instructed folks to change the name there would be confusion,so this is my attempt to keep it simple. feel free to download one file and just change the name to make the other zips.
it also works to make your phone relocked if for some reason you want it that way(rename relock_bootloader.zip). i didnt include a zip for that because i figued there would be no demand.
before:
after:
sure,i could have easily faked the above photos,but i dint.
again,all credit goes to s trace on the above thread,be sure to click the thanks button on his post. all i did was remove the device check per his instruction. DO NOT flash on other devices without checking for the proper location of the lock flag first.
DISCLAIMER:this is not my work. i have tested it on my own device,but use it at your own risk. if it melts your phone into a lil pile of goo,its not my fault.
enjoy
special thanks
-CastleBravo for testing and suport on the original test thread,as well as the pics you see here
-treadwayj for dumping mmcblk0p3 from his still locked phone.
-brian for unlocking his bootloader,then dumping mmcblock0p3 to make sure it would work for cdma evo3d phones too
-brian and donb for fearless testing of the zip files on evo3d cdma4
Stock, locked hboot with s-off: not all fastboot commands will be available (mostly radio related), but you can still flash roms etc as normal.
Stock, unlocked hboot with s-off: bootloader will allow more fastboot commands, but still not as much as an engineering hboot.
ENG hboot, unlocked or locked, with s-off: all fastboot commands are available, and there's nothing it will prevent you from doing. ENG hboot doesn't care about locked or unlocked status.
With s-off, the locked/unlocked status can be changed any time if you change your mind. The tampered flag will be reset if you flash another hboot.
Sent from my ViperROM HTC Droid DNA3
No. It s making you out of the box,stock locked.
Sent from my ADR6425LVW using Tapatalk 22
I think the **tampered** flag also reflects you having a custom recovery.. if you flashed the stock recovery that *should* go away.. but with stock recovery you can't do anything fun1
