testers needed- reset your lock status flag

CastleBravo · Feb 22, 2013

Successfully tested the query, unlock, and lock zip files (didn't bother with the relocked one, its kinda pointless anyway). All worked with the newest CWM touch recovery without any errors. I also dumped mmcblk0p3 after testing, and the 01 remained untouched by the zip.

Here are the requested pics:

unlocked, before flashing zip

locked, after flashing zip

unlocked, after reverting from locked with zip

scotty1223 · Feb 22, 2013

CastleBravo said:
Successfully tested the query, unlock, and lock zip files (didn't bother with the relocked one, its kinda pointless anyway). All worked with the newest CWM touch recovery without any errors. I also dumped mmcblk0p3 after testing, and the 01 remained untouched by the zip.

Here are the requested pics:

unlocked, before flashing zip

locked, after flashing zip

unlocked, after reverting from locked with zip

awsome! thnks for all your support and testing

Serinety · Feb 28, 2013

I think the work on this is great. Thanks for the time spent on this.

But... Has anyone had a problem getting replacement devices? I have easily had close to 100 or more replacement devices over the last 10 years as a vzw customer. I'm the guy you all hate, when I scratch my screen I call up customer service and male up some lame excuse about how something isn't working right and they send me a replacement. Point is, I send all my phones back, rooted, unlocked, and running roms. I've never been, ever, had an issue. So while I can appreciate the work being done, I question the necessity.

Can any one tell me why I would ever need to do this? Is the warranty issues I don't know about where being unlocked would cause a problem?

To be clear, I am not in anyway discrediting these guys, what they do is incredible, and I sincerely appreciate it. I just don't know I would use it, so I'd like someone to hook me up with info

Sent from my HTC6435LVW using Tapatalk 2

CastleBravo · Feb 28, 2013

Serinety said:
I think the work on this is great. Thanks for the time spent on this.

But... Has anyone had a problem getting replacement devices? I have easily had close to 100 or more replacement devices over the last 10 years as a vzw customer. I'm the guy you all hate, when I scratch my screen I call up customer service and male up some lame excuse about how something isn't working right and they send me a replacement. Point is, I send all my phones back, rooted, unlocked, and running roms. I've never been, ever, had an issue. So while I can appreciate the work being done, I question the necessity.

Can any one tell me why I would ever need to do this? Is the warranty issues I don't know about where being unlocked would cause a problem?

Sent from my HTC6435LVW using Tapatalk 2

I just switched to vzw from t-mo in December and I haven't had to send back a device yet so I don't have any personal experience of how picky they are, but back on t-mobile they were crazy about this type of thing. Sometimes people got away with it, sometimes they didn't, but there were a significant number of people that got caught. To get a replacement you first had to take it to a store where they checked the bootloader and a few other things (they cared enough to train every employee to check the bootloader of every type of phone... fairly significant effort went into this) and they checked it again at the repair center. Even if it was a hardware problem completely unrelated to rooting, they'd say flat out no at the store if it was unlocked. If they found it at the repair center they'd sometimes want people to pay for the repairs or to replace the whole device. Back on the htc sensation forums, people would occasionally hard brick phones to stop them from finding out if for some reason they couldn't get it back to stock s-on.

So I'm still kinda paranoid about it from t-mobile... And the actual method is in another thread and is completed and noob-proof, so theres no harm in doing it anyway if you need it.

Serinety · Mar 1, 2013

CastleBravo said:
I just switched to vzw from t-mo in December and I haven't had to send back a device yet so I don't have any personal experience of how picky they are, but back on t-mobile they were crazy about this type of thing. Sometimes people got away with it, sometimes they didn't, but there were a significant number of people that got caught. To get a replacement you first had to take it to a store where they checked the bootloader and a few other things (they cared enough to train every employee to check the bootloader of every type of phone... fairly significant effort went into this) and they checked it again at the repair center. Even if it was a hardware problem completely unrelated to rooting, they'd say flat out no at the store if it was unlocked. If they found it at the repair center they'd sometimes want people to pay for the repairs or to replace the whole device. Back on the htc sensation forums, people would occasionally hard brick phones to stop them from finding out if for some reason they couldn't get it back to stock s-on.

So I'm still kinda paranoid about it from t-mobile... And the actual method is in another thread and is completed and noob-proof, so theres no harm in doing it anyway if you need it.

I could definitely understand the paranoia coming from t-mobile lol. Well on vzw, it's a 5 min process over the phone "hi, my phone doesn't <insert random unfixable, hardware problem here > I've done a master reset and bought a new charger but it's still doing it." "okay sir, a new one is on its way, anything else?"

I have never in 10 years gone into a store for any service. I only deal with 611

Sent from my HTC6435LVW using Tapatalk 2

CastleBravo · Mar 1, 2013

Serinety said:
I could definitely understand the paranoia coming from t-mobile lol. Well on vzw, it's a 5 min process over the phone "hi, my phone doesn't <insert random unfixable, hardware problem here > I've done a master reset and bought a new charger but it's still doing it." "okay sir, a new one is on its way, anything else?"

I have never in 10 years gone into a store for any service. I only deal with 611

Sent from my HTC6435LVW using Tapatalk 2

Every day I start liking Verizon even more lol.

scotty1223 · Mar 1, 2013

Serinety said:
I'm the guy you all hate, when I scratch my screen I call up customer service and male up some lame excuse about how something isn't working right and they send me a replacement.

You're right with that statment. The fact that folks will use it for fraudulent claims makes me not even want to share info like this.

I'm of the opinion if you break your stuff you should man up to it,and pay for it. Your fraudulent warranty claims are making device and service prices higher for the rest of us. Thanks

How you've conned vzw out out a hundred devices is not something I would brag about.

Sent from my ADR6425LVW using Tapatalk 2

Serinety · Mar 1, 2013

scotty1223 said:
You're right with that statment. The fact that folks will use it for fraudulent claims makes me not even want to share info like this.

I'm of the opinion if you break your stuff you should man up to it,and pay for it. Your fraudulent warranty claims are making device and service prices higher for the rest of us. Thanks

How you've conned vzw out out a hundred devices is not something I would brag about.

Sent from my ADR6425LVW using Tapatalk 2

Well you're right, and my point was not to brag, it was to under stand the need to do this.

As far as me, personally being responsible for your extra costs, that's a stretch. I worked as a store manager for a major retail chain for many years, and I can assure, at least at my stores, frodulent returns were the least of my concerns. We had a budget specifically for RTMs, (return to manufacturer) that was there regardless of the legitimacy of the return. I suspect vzw has the same budget and credits in place.

Anyway, i dont want to venture anymore off topic than this, thanks for your work none the less

Sent from my HTC6435LVW using Tapatalk 2

Bigandrewgold · Mar 1, 2013

Serinety said:
Well you're right, and my point was not to brag, it was to under stand the need to do this.

As far as me, personally being responsible for your extra costs, that's a stretch. I worked as a store manager for a major retail chain for many years, and I can assure, at least at my stores, frodulent returns were the least of my concerns. We had a budget specifically for RTMs, (return to manufacturer) that was there regardless of the legitimacy of the return. I suspect vzw has the same budget and credits in place.

Anyway, i dont want to venture anymore off topic than this, thanks for your work none the less

Sent from my HTC6435LVW using Tapatalk 2

And none of that makes it any less illegal or morally wrong to file tens of thousands of dollars worth of false claims.

Sent from my HTC6435LVW using xda app-developers app

beaups · Mar 1, 2013

Nice work scotty, but are we over complicating things?

if we want to lock:

adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33780

if we want to unlock

adb shell
su
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33780

Don't screw up these commands btw (copy paste them).

scotty1223 · Mar 1, 2013

beaups said:
Nice work scotty, but are we over complicating things?

if we want to lock:

adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33780

if we want to unlock

adb shell
su
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33780

Don't screw up these commands btw (copy paste them).

thanks for the reply beaups! thats defaintely easier than the dump/reflash mmcblk0p3 method,and prolly faster than flashing the zip files. the zip files may have less of a margin for error,check out this thread if you havent seen it: http://xdaforums.com/showthread.php?t=2160677

is there a flag for the "tampered" banner as well? if so do you guys know where it is? inside hboot itself? the next thing we could work on is being able to reset that flag,so folks dont need to flash new bootloaders or run ruus to get rid of it.

thanks again for the addidional info

beaups · Mar 1, 2013

scotty1223 said:
thanks for the reply beaups! thats defaintely easier than the dump/reflash mmcblk0p3 method,and prolly faster than flashing the zip files. the zip files may have less of a margin for error,check out this thread if you havent seen it: http://xdaforums.com/showthread.php?t=2160677

is there a flag for the "tampered" banner as well? if so do you guys know where it is? inside hboot itself? the next thing we could work on is being able to reset that flag,so folks dont need to flash new bootloaders or run ruus to get rid of it.

thanks again for the addidional info

tampered I "believe" lives inside misc. I see /sbin/tpd wanting to set some flags, but haven't really spent the time to track it down.

It could be in p3, but p3 is wp after the early bootloaders so I find it unlikely.

What's the story on 0x83F8 in p3?

Or, it could just be hboot's response to seeing unsigned kernel and/or recovery.

scotty1223 · Mar 1, 2013

beaups said:
tampered I "believe" lives inside misc. I see /sbin/tpd wanting to set some flags, but haven't really spent the time to track it down.

It could be in p3, but p3 is wp after the early bootloaders so I find it unlikely.

What's the story on 0x83F8 in p3?

Or, it could just be hboot's response to seeing unsigned kernel and/or recovery.

not sure on 0x83F8. ive not looked at the whole partition,i dont have one of these so ive only see 0x8400 that several folks have reported.

can someone upload or email me their entire p3?

t1gartist · Mar 8, 2013

scotty1223 said:
not sure on 0x83F8. ive not looked at the whole partition,i dont have one of these so ive only see 0x8400 that several folks have reported.

can someone upload or email me their entire p3?

Won't

fastboot oem write secureflag 3 lock the device s-on and fastboot write secureflag 1 unlock the device

beaups · Mar 8, 2013

t1gartist said:
Won't

fastboot oem write secureflag 3 lock the device s-on and fastboot write secureflag 1 unlock the device

3 will s-on and if you have any mods to hboot will instantly brick. 0 is s-off and you cannot execute that command, you would need to exploit again.

Sent from my HTC6435LVW using Tapatalk 2

t1gartist · Mar 8, 2013

oh i thought you could if you have eng hboot and didnt think about needing exploit again

scotty1223 · Mar 8, 2013

t1gartist said:
oh i thought you could if you have eng hboot and didnt think about needing exploit again

1)turning s on with eng hboot will prolly brick the device,assuming it to be signed with the debug signiture,and not a release signiture.

2)even if it didnt,write suefcureflag 0 requires a special file to be present on the extenal sd on older phones,and may require an external sd mounted OTG via the microusb in this case. ive not known the writesecureflag 0 to ever work,even with an eng h boot on older phones

beaups · Mar 24, 2013

scotty1223 said:
thanks for the reply beaups! thats defaintely easier than the dump/reflash mmcblk0p3 method,and prolly faster than flashing the zip files. the zip files may have less of a margin for error,check out this thread if you havent seen it: http://xdaforums.com/showthread.php?t=2160677

is there a flag for the "tampered" banner as well? if so do you guys know where it is? inside hboot itself? the next thing we could work on is being able to reset that flag,so folks dont need to flash new bootloaders or run ruus to get rid of it.

thanks again for the addidional info

btw I had the wrong offset, should be 33796, and, yes, it does work.

zounduser · Mar 25, 2013

scotty, i need to change my cid. and s-on. any help would b great bro. im already on locked bootloader, and ruu ran. thanks

---------- Post added at 10:13 PM ---------- Previous post was at 10:10 PM ----------

fastboot oem write secureflag3 is s-on command? i should know this, but fortunately i havent had to s-on a device!!! lmao! my biggest worry is changing the cid back to vzw_001 or whatever its supposed to say.

Bigandrewgold · Mar 25, 2013

zounduser said:
scotty, i need to change my cid. and s-on. any help would b great bro. im already on locked bootloader, and ruu ran. thanks

---------- Post added at 10:13 PM ---------- Previous post was at 10:10 PM ----------

fastboot oem write secureflag3 is s-on command? i should know this, but fortunately i havent had to s-on a device!!! lmao! my biggest worry is changing the cid back to vzw_001 or whatever its supposed to say.

fastboot oem writesecureflag 3

And you don't really need to worry about your cid. No ones gonna plug it into a computer to check the cid.

Sent from my HTC6435LVW using xda app-developers app

testers needed- reset your lock status flag

Senior Member

Inactive Recognized Contributor

Account currently disabled

Senior Member

Account currently disabled

Senior Member

Inactive Recognized Contributor

Account currently disabled

Senior Member

Senior Recognized Developer

Inactive Recognized Contributor

Senior Recognized Developer

Inactive Recognized Contributor

Senior Member

Senior Recognized Developer

Senior Member

Inactive Recognized Contributor

Senior Recognized Developer

Senior Member

Senior Member

Similar threads

Top Liked Posts