yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] SamdungSpambot:
ok everything happened.. like you said... but.. still says device unlocked is false...

---------- Post added at 07:24 PM ---------- Previous post was at 07:21 PM ----------

List of devices attached

9970b168 device

c:\ADB>adb shell

shell@A0001:/ $ su

su

root@A0001:/ # dd if=/data/media/0/emmc_appsboot.mbn of=/dev/block/platform/msm_

sdcc.1/by-name/aboot

t.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot <

748+1 records in

748+1 records out

383188 bytes transferred in 0.203 secs (1887625 bytes/sec)

root@A0001:/ # exit

exit

shell@A0001:/ $

shell@A0001:/ $ exit

exit

c:\ADB>adb reboot bootloader

c:\ADB>fastboot devices

c:\ADB>fastboot devices

9970b168 fastboot

c:\ADB>fastboot boot TWRP.img

downloading 'boot.img'...

OKAY [ 0.466s]

booting...

OKAY [ 0.021s]

finished. total time: 0.488s

c:\ADB>fastboot oem device-info

...

(bootloader) Device tampered: true

(bootloader) Device unlocked: false

(bootloader) Charger screen enabled: false

OKAY [ 0.008s]

finished. total time: 0.010s

c:\ADB>fastboot oem device-info

...

(bootloader) Device tampered: true

(bootloader) Device unlocked: false

(bootloader) Charger screen enabled: false

OKAY [ 0.005s]

finished. total time: 0.006s
[ONE Android Development] Vonnegut:
That's not possible. Power off your phone, reboot to system, then reboot in fastboot mode and check again with fastboot oem device-info

If the the TWRP booted that means the flashing was succesful. The script works, so you must be unlocked.
[ONE Android Development] SamdungSpambot:
i think the script zip didn't actually run..maybe i should try another recovery?
[ONE Android Development] Vonnegut:
That one works just fine. Boot again the recovery fastboot boot TWRP.img and flash the script again.

This time, before leaving the recovery, go in advanced and take a recovery.log (it will be created on the internal storage).

P.S. Of course, after flashing the script, check again the fastboot oem device-info
[ONE Android Development] SamdungSpambot:
i don't see a log in the internal storage... not in the root or the TWRP folder

unless it's the .twrps file... but doesn't look like it...

and yeah still locked...
[ONE Android Development] Vonnegut:
no log? still locked? That's quite strange. I'm under the impression that the script didn't run 'cause one check failed, that's why i wanted to see the recovery.log. Are you sure you went in the advanced options and clicked on the log option?

You should have a recoverylog.txt file in your internal recovery...

I'm quite puzzled but we can try another way.

The script makes some check to verify if the phone is an OPO...but we know it is. gimme a few sec...
[ONE Android Development] SamdungSpambot:
Yeah it said it was copying log to SD..but nothing is there....

---------- Post added at 08:03 PM ---------- Previous post was at 07:58 PM ----------

Yeah it said it was copying log to SD..but nothing is there....

Is twrp suppose to say simulating actions on the top?
[ONE Android Development] Vonnegut:
Run the script again, then push the button between the Home virtual button and the Back virtual button.

You will se the log...read it and tell me exactly what it says.

---------- Post added at 02:07 AM ---------- Previous post was at 02:05 AM ----------

No!

Unless the Simulate action for theme testing is flagged (under setting)

---------- Post added at 02:15 AM ---------- Previous post was at 02:07 AM ----------

You haven't clearly flashed anything for real...that would explain why you're still locked.

I dunno why TWRP isn't working as expected.

Anyway, the script does lot of stuffs but ultimately there's is only one echo command that does the trick.

We can run it via ADB shell...but first i'd like to see if the script says that the bit matches and your locked....

Anyway, it's too late now for doing anything else. I'll see ya again tomorrow...time to sleep now
[ONE Android Development] SamdungSpambot:
ok... i turned it off... no idea how it was turned on in the first place.. i never did it...

looks like it ran... and i got an error zip signature verification failed:1

Error flashing zip "sdcard/OnePlusONe-OnlyBootloaderToggle.zip

updating partition details

turned off the verification and ran it again... looks like it's working

woohoooo you rock!!!!

c:\ADB>fastboot oem device-info

...

(bootloader) Device tampered: true

(bootloader) Device unlocked: true

(bootloader) Charger screen enabled: false

OKAY [ 0.006s]

finished. total time: 0.007s
[ONE Android Development] Vonnegut:
:good:

Now you have to promise to not use any Toolkit again and to not lock the bootloader again :)

You have your ADB forlder now...learn how to use it and gain control of what you're doing!
[ONE Android Development] SamdungSpambot:
i promise,

now if i wanted a clean wipe (everything including user data) and reflash up to the newest firmware but leaving my bootloader unlocked... would that also update my bootloader back to 33? is there a reason to update to the newest bootloader?
[ONE Android Development] Vonnegut:
I think the only update made to the bootloader was done to trouble ppl like you. Anyway, as long as you won't relock the bootloader you can safely update it.

Download the full official 33R ROM http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip, go in fastboot mode, then flash each and every partition. You will surely find the commands somewhere in this forum...

Of course you have to flash the userdata for your phone (there are 2 of them inside the .zip, one for the 16GB and one for the 64GB).

---------- Post added at 02:43 AM ---------- Previous post was at 02:39 AM ----------

fastboot flash modem NON-HLOS.bin

fastboot flash sbl1 sbl1.mbn

fastboot flash dbi sdi.mbn

fastboot flash rpm rpm.mbn

fastboot flash tz tz.mbn

fastboot flash LOGO logo.bin

fastboot flash system system.img

fastboot flash boot boot.img

fastboot flash recovery <flash_your_favorite_custom_recovery_here_not_the_stock_one>

fastboot flash userdata <name_of_the_userdata_for_your_OPO>

fastboot flash aboot emmc_appsboot.mbn
[ONE Android Development] SamdungSpambot:
thanks again... feel a lot better about this device now that i know what's been done on it..
[ONE Android Development] Kaar3l:
I did:

fastboot oem device-info

And straight out of factory opo was tampered bit 1. All I did was update OTA stock 4.4.2 to 4.4.4.

An now unlocked bootloader with factory reset. :)
[ONE Android Development] zaquaz:
Same here, Brand new OPO, just opened. Fastboot oem device-info shows tampered after update to latest OTA. Nothing was done except set it up and do an update. I'm not sure what to think of this. Is this a bad update from OPO that caused it? We may never know. It has factory everything, rom, boot, serisously untouched besides updates. I'm a bit saddened that OPO seems to be causing more issues instead of embracing.
[ONE Android Development] Vonnegut:
Did you buy it trough an invite?
[ONE Android Development] zaquaz:
Correct, it was purchased through an invite. My first OPO was fastboot oem unlocked, and works fine. This was done after the last OTA. However, the second one has not been touched by fastboot until running the fastboot deviceinfo, and shows tampered. Cannot get a good backup of the second device to try a fastboot oem unlock at this point. It fails everytime.

Need to unlock to flash a kernel and fix the touchscreen issues. That is the only reason the first device was unlocked and rooted. They are beginning to become unbearable. Any swype-type keyboard is unusable at this point, and touch texting requires extra time to make sure it takes every touch.
[ONE Android Development] djha53k:
Device not unlocked cannot boot

1) Did you unlock your device before by any means ? (or by fastboot oem unlock) ? YES

2) What is the recovery already installed in your device ? TWRP-2.8.1.0

3) What is the status of your device ? "fastboot oem device-info"

(bootloader) Device tampered: true

(bootloader) Device unlocked: false

(bootloader) Charger screen enabled: false

4) What error msg you got when tried to run command fastboot boot <custom_recovery.img>.

booting...

FAILED (remote: Device not unlocked cannot boot)

5) Steps you tried.

Installed other ROMs, other boot.img files...nothing works...

The command: fastboot oem unlock reset One to the TWRP, but it does not unlock it

So I am in the state: 2) Unlock Bit - FALSE , Tamper Bit - TRUE

What now???
[ONE Android Development] gianvy:
Dear all,

I am using this amazing phone since two weeks, and now i decided i need a custom recovery to make a full nandroid backup of my device that now runs stock rom at last update (i think). Now i'm really confused, i would like to simpyl install twrp and have root permissions.

My situation is:

tamper= true

unlock= false

I never run a toolkit and never tried unlock trhough fastboot, because i do not understand if i will factory reset phone acting like this.

Also tried temporary boot from recovery with fastboot command but i get error message saying i can't do this because im locked!

Sorry for the stupid question, maybe it's the late hour...

Thanks for your kind help in advance!
[ONE Android Development] gianvy:
Really nobody?

---------- Post added at 11:28 PM ---------- Previous post was at 11:19 PM ----------

Really nobody?
[ONE Android Development] Vonnegut:
Did you read the latest 40 post?
[ONE Android Development] gianvy:
Yes i read from the beginning the thread, i was looking for a way to unlock without wiping everything, since i do not have a nandroid backup of my actual situation, and my first intention in unlocking was to have a full backup of stock ROM latest update (don't know if i madre myself clear, sorry for my bad english...)
[ONE Android Development] SamdungSpambot:
Guys are you reading how Vonnegut helped me? The fix is about downgrading the bootloader back to 25 and then running custom recovery to fix the tamper bits
[ONE Android Development] gianvy:
Ok i will read carefully what to do, thanks!
[ONE Android Development] i860:
I went back to stock and i have this

(bootloader) Device tampered: true

(bootloader) Device unlocked: false

(bootloader) Charger screen enabled: false

OKAY [ 0.005s]

I try to flash the zip tamper from stock recovery but it failed. How do i reset (bootloader) Device tampered: true to false via fastboot?
[ONE Android Development] davideelde:
[MENTION=5381511]Mnt-XDA[/MENTION] hi i have the same issue whit my bootloader i have made a screenshot of my cmd fastboot info.

I hope you can help me out whit it

Regards david

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Android Development] davideelde:
Never mind guys i haved flash the bootloader unlock.zip and the problem solved thanks for making this

Verstuurd vanaf mijn Oneplus met Tapatalk
[ONE Android Development] b0li:
Worked like a charm. Flashed zips to lock bootloader and reset tamper bit, so my OPO is stock again. Great guide, thanks.
[ONE Android Development] steve8x8:
My OPO, right out of the box, still waiting for the OTA to arrive, no unlock, nothing changed yet (only WiFi activated): tamper bit set, unlock bit unset. Firmware is 33R but with kernel dated Sep 1. Apparently the tamper bit has changed its meaning, and resetting it might tell OP someone has, well, tampered it?
[ONE Android Development] tmcpnet:
(bootloader) Device tampered: true

(bootloader) Device unlocked: true

Which script will reset tampered and unlocked state to False?

Thanks

---------- Post added at 08:22 PM ---------- Previous post was at 07:53 PM ----------

How to reset back tamper bit to False?

Thanks

T
[ONE Android Development] steve8x8:
Should be easy to tweak the BootUnlocker script to revert the changes... or use the *Toggle zips (caveat: they are "untested" so you should at least read the code and check it against the BootUnlocker one)
[ONE Android Development] reinert012:
This thing just saved my device, thank you so much!
[ONE Android Development] mandaman2k:
Mine is exactly the same, right out of the box and i got this

C:\Users\Isaac\Documents\OnePlus\cm-11.0-XNPH38R-bacon-signed-fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.016s]
finished. total time: 0.016s

Should i report it?
[ONE Android Development] jejehtc:
delete
[ONE Android Development] Vonnegut:
What for?

A) there's already a script doing that in the OP

B) there's no reason whatsoever to turn back the bits to FALSE. OnePlus warranty does support modding.

C) only an insane man would lock and relock the bootloader whenever he wants to flash anything

D) THAT IS AN HIGHLY DANGEROUS THING TO DO

Since 33R they added some code to the bootloader which screws up everything. After relocking the booloader, some ppl couldn't boot a recovery or access to the installed recovery anymore. Moreover the fastboot oem unlock command doesn't work anymore too.

That means ppl had no way to flash the script to unlock their bootloader anymore.

Just browsing this thread you'll find a lot of them.

I managed to help some of them but i could do that just because they were rooted.

To make it short, if someone thinks to be smart and uses the script and finally find himself with:

- no way to unlock the bootloader with the fastboot command

- no way to boot or access his recovery

- no root

then he might use his OPO as a wedge to balance his kitchen table.

Dear reader, if you did that anyway and found yourself in trouble, don't write me an MP. I won't even answer you.

Lemmings can't be helped.
[ONE Android Development] jejehtc:
Ok delete the post
[ONE Android Development] Vonnegut:
As a matter of fact, the R25 bootloader works just fine..so if anyone feels the irrational urge to relock their OPO they should first flash the R25 bootloader. I'm not saying that's something that someone should do...but, at least, he could still boot a custom recovery, flash the script again and learn why this practice is useless without bricking his phone.
[ONE Android Development] rahditzz:
38r

Will this work if i updated to 38R? I didnt update through OTA, i downloaded 38R rooted from xda and flashed.. Can i still use this mod?
[ONE Android Development] th3xeroeagle:
I'm running the latest cDroid rom I have twrp 2.8 but my bootloader is locked (because I oem lock and oem unlock thinking itll act like a nexus but nope)...will this work?

EDIT: took a leap of faith ...IT WORKED!!! thank you. this saved my device
[ONE Android Development] P1nGu1n_:
I was wondering too if it's still compatible with 38R. This is my last shot. I accidentally relocked my bootloader with a custom recovery still flashed, now I'm not able to unlock it anymore, it fails. Can you still use it with 38R's bootloader? Maybe [MENTION=945041]Polarfuchs[/MENTION] knows it?
[ONE Android Development] Vonnegut:
It works...they didn't change the bootloader after 30O and the bits are still the same.

Flash this http://xdaforums.com/attachment.php?attachmentid=2876403&d=1406718707
[ONE Android Development] Polarfuchs:
Thx for your reply, I don't have a 1+1 any more to check it.
[ONE Android Development] ahac85:
Hi ive put back on 25r to return my phone, using the script it sets everything to false but once ive rebooted phone and go back into bootloader it shows as tampered true
[ONE Android Development] Astrovilos:
Thanks! The zip works just fine in 38r!
[ONE Android Development] mkdroid:
Thanks alot!!!!!

That script worked for me as well. 1+1 64GB back to life..to its original ROM and TWRP as default recovery again. LOL. The reason I needed this type of script or solution is because I flashed 38R rom and flashed userdata.img instead of userdata_64.img so I got limited in storage capacity.

I couldn't OEM unlock with fastboot. I tried so many times and finally gave up on that. And start my research on this issue in xda and other 1+ related forums.

AND finally found it here in XDA where Android techie lives.

Thanks Again!!!!
[ONE Android Development] adam_ridzuan:
4) Unlock Bit - TRUE, Tamper Bit - TRUE

what is tampered? what happen in the above state?

ive gone trough all this thread but didnt found any explanation of it. please link to me if theres already discussed. tq
[ONE Android Development] P1nGu1n_:
Tampered with the bootloader. Once you unlock it, it gets set to true. If you re-lock the bootloader, Unlock-bit gets set to false, but the tamper bit stays false. This bit just remember whether there was tampered with the bootloader, even though it's relocked.

Sent from my phone, please forgive any tpyos.
[ONE Android Development] y2jdmbfan:
Do I run fastboot oem lock first, then boot into recovery from fastboot and flash this zip?
[ONE Android Development] adam_ridzuan:
ok ty..so i think it is use for checking warranty right? bought chinese set, and both are set to true by the shop since the need to flash cm11s over coloros. hope it didn void warranty provided by them.

---------- Post added at 02:00 AM ---------- Previous post was at 01:57 AM ----------

if u mean to unlock, if oem unlock can unlock ur phone, nothing to do with this zip. unless u wanna set back tampered to false. if im not mistaken.
[ONE Android Development] konrad496:
I can't boot custom recovery via fastboot because device is locked: "Device not unlocked cannot boot". I also can't flash it via fastboot or stock recovery: "Device not unlocked cannot flash or erase". Funny enough my device is rooted! I am running latest CM11. How to unlock it? I don't care about the data. This is the case no 2) Unlock Bit - FALSE , Tamper Bit - TRUE
[ONE Android Development] Vonnegut:
Luckily enough you're rooted...otherwise you would be stuck forever.

I still wonder why some ppl put themselves in this kind of situation just to satisfy an irrational impulse...

Anyway, in this thread you'll find a long post exchange (between me and a guy who was facing your troubles) that will tell you what to do http://xdaforums.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912/post55587946
[ONE Android Development] konrad496:
Sir, I can't download the official .zip 25R zip http://dist01.slc.cyngn.com/factory/...d-fastboot.zip. Could you please provide other link? Can't extract emmc_appsboot.mbn. Downloading cm11s25R from http://xdaforums.com/oneplus-one/general/rom-xnph25r-cm11s-zip-t2820008
[ONE Android Development] Vonnegut:
Just download this .zip, then open it and finally extract the file.

https://www.androidfilehost.com/?fid=23578570567714588
[ONE Android Development] konrad496:
I've downloaded the file, extracted emmc_appsboot.mbn and now I am struggling to move it to root directory using file manager. Moving 374.21KB takes forever... I am unable to move the file even though I have root access. Could you please elaborate on how exactly to put extracted emmc_appsboot.mbn file in the root of the internal storage? I'm stuck here. I have su installed but it doesn't seem that I have root access... HELP, please
[ONE Android Development] Vonnegut:
I fear you've not the required knowledge to follow the instructions.

You had to put it in the internal storage...not in the the root of the phone.

Moving a few kb via MTP takes a few seconds.

P.S. The root of your internal storage means that you do NOT have to put it inside any folder...
[ONE Android Development] konrad496:
Don't worry, I've got enough knowledge to know what I need to clarify. Thanks for the input, I really appreciate it, however your criticism was unnecessary.

---------- Post added at 08:50 PM ---------- Previous post was at 08:44 PM ----------

error: device unauthorized. Please check the confirmation dialog on your device ...
[ONE Android Development] Vonnegut:
Really?

i'm an idiot... working now... i didn't click ok on my phone when it asked for usb debuggin access

http://xdaforums.com/showpost.php?p=55591364&postcount=250

Read all the post exchange, i mean ALL to the end
[ONE Android Development] konrad496:
Thank you. The script worked.
[ONE Android Development] hellshinoda:
Apologize for being a noob but I'm confused because there are so many cases. I have unlocked my bootloader by the normal way (fastboot oem unlock) and now I want to return to 100% Stock. I have flashed the latest 38R stock image. I just want to ask that does I need to relock my bootloader to receive OTA in the future. If it is, what is the best way for me to relock my bootloader and fix my tamper flags. Thank you very much for reading my question!
[ONE Android Development] P1nGu1n_:
Having an unlocked bootloader does not stop you from receiving OTA's. Modifying system files does break it, for example, but since you flashed the factory image that isn't the case.
[ONE Android Development] bukithd:
So I am in a state of,

Device unlocked: False

Device tampered: True

Will flashing the bootloader flag zip work in my situation?

Current setup is: CM11 (not s), Cyanogen recovery, locked bootloader, no ability to use fastboot oem unlock unless I can somehow reflash stock recovery. If anyone could clarify, I would be grateful.

EDIT: I can confirm after installing TWRP that just flashing the zip worked. Now I can rest easy. My love/hate relationship with android continues.
[ONE Android Development] timbuctoo:
Awesome

Many thanks for helping so many users out
[ONE Android Development] DPinched:
Thank you SO MUCH!

Received my OPO yesterday with a non functioning Vol UP button and non functioning vibrate motor... to check if it was software related I have reflashed kernels and ROMs to no avail... :(

So it has to go back to RMA

I had no idea these flags existed and because of you, I feel more secure my RMA will go through without unnecessary hassles.

THANK YOU! :good:
[ONE Android Development] -Already Exist-:
Hi, I can't unlock my bootloader with command: fastboot oem unlock (it just reboot my phone). When I type: fastboot oem divece-info,

I got this: Unlock Bit - FALSE , Tamper Bit - TRUE.

When I try to flash something i got an error: Device not unlocked cannot flash or erase.

Do you have any solution?
[ONE Android Development] Vonnegut:
Read the thread...
[ONE Android Development] STEyeAndroid:
I just got my new OnePlus and checked the unlock/tamper bits. It says that Unlock=false and Tamper=true. I didn't unlock my phone yet, I simply went into fastboot. Anyone ever get this? Does this mean OnePlus sent me an refurbished phone?
[ONE Android Development] skyn3t:
Anyone tried with last OTA 44S ?
[ONE Android Development] Mnt-XDA:
It should work....
[ONE Android Development] dafonehacker:
[MENTION=5381511]Mnt-XDA[/MENTION] sorry for the dumb question, but if I understand correctly, if I want to go from an unlocked+tampered device to a locked+non+tampered device, I have to flash the bootunlocker.zip? The OP is a little bit confusing, maybe you could change it a bit? Thanks in advance.

Edit: nevermind. I read trough the thread and saw some people having tampered bits after OTA on never unlocked phones. And since the warranty still covers tampered phones I guess I'll just fastboot OEM lock it and not care about the tamper bit. I just want to lock it for security reasons anyways.
[ONE Android Development] hrishi21007:
How do i reset Tamper & Unlocked to false mode???

I flashed the .zip twice in TWRP which made the Tamper bit to False...

but then when i reflash STOCK ROM with OPO TOOLBOX... it says Tamper False ... Unlocked True!!! :(

After that if i lock the bootloader it says Tamper:true Unlocked: False???!!!

please help!!! [MENTION=5381511]Mnt-XDA[/MENTION]
[ONE Android Development] youngchaos:
Anyone can confirm on 44S ?
[ONE Android Development] skyn3t:
C:\\Downloads\One+1\ADBfastboot>fastboot oem device-info

...

(bootloader) Device tampered: true

(bootloader) Device unlocked: false

(bootloader) Charger screen enabled: false

OKAY [ 0.007s]

finished. total time: 0.008s

C:\Downloads\One+1\ADBfastboot>fastboot boot openrecovery-twrp-2.8.1.0-bacon.img

downloading 'boot.img'...

OKAY [ 0.453s]

booting...

FAILED (remote: Device not unlocked cannot boot)

finished. total time: 0.458s

can load temporary recovery :(
[ONE Android Development] P1nGu1n_:
This workaround was patched in 30O if I remember correctly. You now have to unlock your bootloader.