yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Lanchon:
nothing happens if he tries to adb! the adb daemon is a linux process, you need linux to be up for the daemon to run, ie: either android or recovery. no boot to either of them = no adbd.

---------- Post added at 06:09 AM ---------- Previous post was at 06:08 AM ----------

toolkit???!! you can forget about toolkits!

---------- Post added at 06:17 AM ---------- Previous post was at 06:09 AM ----------

you mean you did a full flash of COS and it still doesnt boot? are you sure you did a COMPLETE FLASH and it finished without errors? then your phone must be defective. otherwise, i repeat, you need to flash COS.

there is a thread for debricking by flashing COS. go to that thread and post there, ask for help. dont post here anymore, this thread is for OEM unlocking **if you have a working custom recovery**. you dont, so this thread is not for you. no one here can help you because we dont know how to flash COS or debrick.
[ONE Android Development] waterdaan:
And what about fastboot,

Is that part of the bootloader or kernel?
[ONE Android Development] Lanchon:
fastboot is the lastest stage bootloader. problem is, this phone is OEM locked.

fastboot can't OEM unlock. when you send the unlock command, fastboot boots the recovery with a special command so that recovery (which is linux) wipes then OEM unlocks. only stock recoveries understand the command or know how to do OEM unlock. so if you have custom recovery or non-functional recovery, you can't OEM unlock at all.
[ONE Android Development] Filko84:
I have already install it but I am still at boot logo!

Only fastboot is working.
[ONE Android Development] Lanchon:
your phone may be defective. anyway, we don't know how to debrick here.
[ONE Android Development] kewinhdorff:
[MENTION=2258271]EddyOS[/MENTION] my bootloader is unlocked, but if i for some reason want to relock it, i can do it in fastboot mode. but is it safe? i asked this on the opo forum and they sid that i could run in to some problems by just relocking it :eek: and will i run in to problems if i unlock it again ?
[ONE Android Development] nickhaven:
Not sure what happens but most tutorials for unlocking the bootloader say the relocking causes issues.
[ONE Android Development] kewinhdorff:
yeah thats very sad that it causes problems :(
[ONE Android Development] nickhaven:
Just curious but why would you want to relock. Even its to resell the device, unlocked doesn't effect the price.
[ONE Android Development] kewinhdorff:
i think i was just curious when i was reading return back to 100% stock threads :) and there were links to this thread.

---------- Post added at 01:34 PM ---------- Previous post was at 01:26 PM ----------

just one more question. when i first unlocked my device in the guide it said

code

fastboot oem unlock

code

fastboot reboot

the device rebooted it self after the fastboot oem unlock and i think i did the fastboot reboot during that reboot or after it. that doesn't affect my device does it ? it is just a reboot command. it kind of made me unsure because i am all about following the guides completely. hehe
[ONE Android Development] Filko84:
No I am at state:

(bootloader) Device tampered: true

(bootloader) Device unlocked: true

(bootloader) Charger screen enabled: false

OKAY [ 0.010s]

finished. total time: 0.010s

Still can't go to recovery.

Flashed TWRP, but no luck to boot in recovery.

fastboot boot <custom_recovery.img>

Reboot with fastboot sign but not loading recovery and not in fastboot mode. Do not acceptings commands from fastboot.
[ONE Android Development] Lanchon:
now that you have fastbook unlocked you can flash CM12S or OxygenOS and if it doesnt work, you probably have a defective phone.

you can also flash just modem+firmware (as in the CM1XS distros) and the flash custom recovery. (and if it doesnt work, you might have a defective phone.)
[ONE Android Development] el_jefe:
@ Mnt-XDA: Thank you very much!!! You saved my phone from hitting a wall!
[ONE Android Development] moobieboobie:
1) Did you unlock your device before by any means ? (or by fastboot oem unlock) ?

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

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

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

5) Steps you tried.

1) did not unlock before

2) recovery is stock cyngn recovery. phone is completely stock

3)

(bootloader)	Device tampered: true

(bootloader)	Device unlocked: false

(bootloader)	Charger screen enabled: false

(bootloader)	Display panel:

OKAY [ 0.006s]

finished. total time: 0.006s

4)

fastboot boot twrp-2.8.7.0-bacon.img

downloading 'boot.img'...

OKAY [ 0.330s]

booting...

FAILED (remote:	Device not unlocked cannot boot)

finished. total time: 0.333s

5) i'm trying to fix the phone. it's stock as a box of rocks, with locked bootloader and no root. the owner said she had it down to 30% and turn it off, charged over night. turned it on and now stuck at cyanogen logo. all steps to try and recover os have failed. I think because the bootloader i locked, i cant seem to do anything else. not sure if this script can/or will work with my situation.
[ONE Android Development] Lanchon:
no it cant help you.

steps you can try:

1) if adb debugging is enabled and some computer is trusted, get the key from that computer (or use that computer) to figure things out.

2) factory reset from recovery, see if it boots then.

3) it may be possible to factory reset from fastboot too, dont know.

4) fastboot oem unlock (which will factory reset; if you got this far, the reset probably wont help you to boot)

5) fastboot boot a custom recovery, get in via adb and look around. you can dump partitions and see whats wrong. DEFINITELY dump the least call it "efs" partition to the PC!!! something's wrong so find it. you can also pipe the complete raw 64GB image (including partition table) to the pc for analysis. do use lzo or similar in the pipe!

6) if no recovery boots, there might be corruption on the emmc or you might have defective hardware. your next to last resource may be factory flashing, but then you wont know what happened.

7) alternatively you could try to get the deivce into QCOM mass storage mode (via keys and cold-usb plugging, or, maybe, --DANGER--> by invalidating the bootloader). you are supposed to be able to access the raw emmc from that mode.
[ONE Android Development] smertz:
Hey I am really stupid. Can someone please post east to follow instructions on how to do this?
[ONE Android Development] hyddro:
I ahve a problem. My new OPO came and tried unlocking the bootloader using a toolkit... i think i made a big mistake when i run the fastboot oem device.info command i get

unlocked : false

tampered: true..

so now no matter what i do i cant get my phone to:

1. boot into recovery

2. unlock the bootloader.

Im trying to use this patch to remove the tamper thing as i remember i ran into a similiar situation long ago, but it would let me cause its telling me my device isnt unlocked... help?
[ONE Android Development] Kofi o:
Tamper Bit

Thanks for the MOD [MENTION=5381511]Mnt-XDA[/MENTION]

I'm currently have a rooted, unlocked OPO and I would like to set the tamper bit to false so that I can install a work app on my device.

Does anyone know if the tamper toggle zip is working correctly?

Also, is there a possibility of my device being in an unrecoverable bricked state of iI flash the tamper toggle zip?

Thanks
[ONE Android Development] FRooter:
Regarding the possibility of damage or becoming unrecoverable, it's difficult to rule-out with any form of modification, but at least from my personal experience I was able to fully restore the stock ROM and both the Unlock Bit and Tamper Bit resulting in no damage -- the device was still fully usable without any visible issues to my knowledge.
[ONE Android Development] therohanchawla:
Use bootunlocker from the play store.... It lets you tamper/untamper and lock/unlock on the fly if you have root.....
[ONE Android Development] ghassir:
Deleted!
[ONE Android Development] khurram1991:
Thanks for helping!! 100% Stock now.

I was on kitkat 4.4.4 cyanogen mod and using twrp recovery to flash the script all the process was smooth. And now my mobile state is toggled from true to false state. Thank you everyone who dedicated in making these script.
[ONE Android Development] anshumangoyal:
The Tricks given here are too confusing. Is there any easy way available. I have been able to revert to stock rom, but my boot loader is still locked and temper flag is set as well. I want to come back to full stock with no root as I need to return this phone to service center.
[ONE Android Development] Lanchon:
you don't need to! oneplus officially stated it does not void warranties due to unlocking or tampering. that is the only reason i bought the OPO.

also, many many devices are sold new directly from oneplus in a tampered state. i've personally seen 3 such devices (out of 4 devices i received as new straight from them).

but to solve the technical question...

it's easy:

-fully return to stock and reset

(now you have full stock with unlocked and tampered BL state)

-MAKE ABSOLUTELY SURE YOU HAVE STOCK RECOVERY IN PLACE BEFORE CONTINUING!!! LOCKING THE BL WITH CUSTOM RECOVERY MEANS A LOT OF PAIN, DON'T DO IT!!!

-fastboot boot your-favorite-twrp-image.img

-reset both BL flags with the script(s)

-profit!
[ONE Android Development] anshumangoyal:
Why I want to move to stock to test the Marshmallow release which is going to come for One Plus One soon (as per news). Rest there is no reason to do that. Many People telling the battery backup has been excellent with Marshmallow.
[ONE Android Development] gunvald89:
Hi guys. I have a OP2 and im having a little bit of a problem. My device can only boot into fastboot-mode, no recovery possible, the device is tampered but not unlocked. What can I do? Can I use OnePlusOne-BootUnlocker.zip on a Onplus two?
[ONE Android Development] ruthvik179:
Which twrp version did you guys use?

There seem to be some problems with the latest 2.8.7.0.

Will this work with 2.8.6.0?
[ONE Android Development] ruthvik179:
OK the thing is I have erased my EFS partition by mistake and need to give it to RMA ASAP. For that I need warranty.

So till now I have flashed stock and my bootloader is still unlocked. And I checked my tamper bit

[IMG="This was what showed up"]http://imgur.com/KUJtaCn[/IMG]

So please tell me step by step what to do now

-which zip to flash of the given 3

-how many times should I flash it

-When should I flash it after locking or while the phone is still unlocked

-how to relock the phone
[ONE Android Development] sihag:
No need to flash anything for RMA. OPO don't consider software tampering as a crime or to say they themself ask you to root so that color os could be installed. You can give back device as it is untill you are returning it for software issue itself.
[ONE Android Development] mihai2xk:
Hi guys,

I am on 12.1 stock rom but i have unlocked bootloader and twrp recovery installed.

Please tell me what i have to do for 100% stock

What is the order of steps to follow?

Thanks
[ONE Android Development] Lanchon:
read before posting
[ONE Android Development] mihai2xk:
Sorry. I read what you said in #434 but I don't understand. First I have to return to stock recovery and after I have to flash script? Which script to use? First or second and third? Please answer. Thanks.
[ONE Android Development] Lanchon:
first step is:

"-fully return to stock and reset"

where does it say "stock recovery"? fully return to stock. everything. recovery included. (but do not re-lock the bootloader yet.) sorry, i will not continue to answer because you obviously do not read. so it is of no use to write anything else. (note to casual readers: user PM'd me with questions too.)
[ONE Android Development] heineken78:
used same methode to patch Infocus m810 LOCKED bootloader.

There was no way to use oem unlock or else..

Working perfect with patch! Also at same offsets as OnePlusOne!

Thank you.
[ONE Android Development] vikphogat:
sorry its the off-device thread but i need help. I have yu yunique device and my device stats are

device tampered : true

device unlocked : false

plz help me . how to reset these two. i am unable to unlock bootloader now and cannot process command ( fastboot boot "recovery.img" )
[ONE Android Development] xbit:
The fastboot boot recovery.img doesn't work for me.

I have my OPO bricked, only starts in fastboot mode and I can't do fatboot oem unlock (It restarts and it's locked again).

Device Tampered: true

Device Unlocked: false

C:\adb>fastboot boot recovery.img

downloading 'boot.img'...

OKAY [ 0.290s]

booting...

FAILED (remote: Device not unlocked cannot boot)

finished. total time: 0.302s

C:\adb>fastboot oem unlock

...

OKAY [ 0.019s]

finished. total time: 0.019s

(OPO restarts without change unlock flag)

C:\adb>fastboot oem device-info

...

(bootloader) Device tampered: true

(bootloader) Device unlocked: false

(bootloader) Charger screen enabled: false

(bootloader) Display panel:

(bootloader) console_enabled: 0

(bootloader) exec_console_unconsole: 0

OKAY [ 0.004s]

finished. total time:

I had CM12S nautghly (latest one) and I have tried to upgrade to CM13 today without lucky....

¿Can someone help me?
[ONE Android Development] bahar_b:
Thanks for the script.will save for maybe in-future be usefull.so sorry to say but a bit hard to understand "step by step guide@1st page"
[ONE Android Development] e1forall:
Trying to help

Hello

From what I understood I will try to help you if not solved.

1. Download latest nightly or latest fastboot zip.

2. Extract boot.img from that.

3. Connect the phone in fastboot mode and flash this boot.img using "fastboot flash recovery boot.img".

4. Then "fastboot oem device-info". It's should be locked still and tampered.

5. The. "fastboot oem unlock".Check It should do some things in recovery, let it do it and boot itself and then again go to fastboot mode.

6. Then again check "fastboot oem device-info". Then bootloader should be unlocked now.

7. Now flash recovery of your choice.

Thanks
[ONE Android Development] xbit:
I have solve the problem without bootloader because it doesn't work.

I used COM connection conecting the switched off phone to PC and with OnePlusRestoreTool.
[ONE Android Development] sigex:
1) Did you unlock your device before by any means ? (or by fastboot oem unlock) ?

Yes device was unlocked rooted had TWRP and CM13 running on it

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

IT was TWRP (nothing now)

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

----

C:\Users\DMsb45zero\AppData\Local\Android\sdk\platform-tools>fastboot oem device-info

...

(bootloader) Device tampered: true

(bootloader) Device unlocked: false

(bootloader) Charger screen enabled: false

(bootloader) Display panel:

(bootloader) console_enabled: 0

(bootloader) exec_console_unconsole: 0

OKAY [ 0.008s]

finished. total time: 0.009s

----

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

Tells me that it failed since the device is not unlocked.

5) Steps you tried.

I tried using fastboot to install TWRP again but like I said this just fails as the device is locked

There are 4 possibilities of the the value set of the 2 bits ( unlock bit & tamper bit)

2) Unlock Bit - FALSE , Tamper Bit - TRUE

This is the current status of my device. If I try fastboot oem unlock it reboots into fast mode and is still locked. This is the only thing my phone will do, fastboot. I can detect it on the PC using fastboot devices. It is a oneplus one.

HELP? How on earth do I run the script to toggle the unlock state? I see META-INF what am I suppose to do with that? The guide says something about flashing it using TWRP. But that's not going to work as I don't have a recovery or a system rom.. Also I tried the OPO recovery tool (which is the moded version of the coloros factory reset) But it doesn't just up the com text as the guide suggested. Also the guide says put phone into recovery mode but again I can't...
[ONE Android Development] e1forall:
ohh...okay good that you have solved your problem :good: :D
[ONE Android Development] PrashanthOPO:
Unlock bootloader without data erase
[ONE Android Development] seblog:
I reverted back to stock (YOG7DAS2K1) via fastboot image, all went ok.

Now I want to set to false both tamper flags, but I cannot get to boot to temporary TWRP (of course now I am all stock, so I have Cyanogen bootloader, but still have unlocked bootloader)

I am in fastboot (dimmed cyanogen logo face smiling at me and "fastboot" written on the right of it)

Go to dos and type command (all tools and drivers are correctly set up)

fastboot boot twrp.img

Notification led flashes once (amber color), then the cyanogen logo and text became more lit, but phone get stuck there, and from fastboot commands I don't have fastboot connection to phone anymore...

I tried flashing with TWRP 2.8.6.0, 2.8.6.1, 2.8.7.0

Only way to restart is keeping power button pushed 10 sec.

If I go to recovery it's still the Cyanogen recovery.

No way I can access TWRP, so I cannot flash the untamper zip script.

Do you know what I can try? Are the information at post n.1 still valid on latest CM12.1 builds?

Thanks
[ONE Android Development] agstn.tanmay:
1)i have unlocked my device previously with fastboot oem unlock without any issue.

2)i have installed twrp 2.8.6.0

3) "fastboot oem device-info status of my device is Unlock Bit - TRUE, Tamper Bit - TRUE .

4)haven't tried yet the command fastboot boot <custom_recovery.img>. ,basically what this command do??

5)these are the steps i have already done,accept the no step command which i mentioned., and i havent faced any error with all these steps.

now can u plz tell me what i can gain if my devicce's Tamper Bit is false from the true ??
[ONE Android Development] Evil Eye:
deleted!
[ONE Android Development] agstn.tanmay:
till no help?
[ONE Android Development] drgibbon:
I notice that the first post in the thread has a warning about CM11, so I just want to check if I can use it safely or not with CM12.1.

I have a OnePlus One that I want to set the tampered and unlocked both to false. I have previously unlocked the bootloader (with fastboot oem unlock), and I had installed TWRP and the latest Cyanogenmod 12.1 rom. At present I have restored the device to the stock with cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18.zip from Cyanogen Support, by issuing the following commands;

fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img

My current 'fastboot oem device-info' is

(bootloader)	Device tampered: true
(bootloader)	Device unlocked: true

I haven't tried booting into a temporary recovery and trying to script, because I am not sure if it will brick my device or not!

Can anyone confirm that the script will be ok in this case? :confused: Thanks. :cowboy:
[ONE Android Development] xkanth:
Oneplus x

I have the same issue with oneplus x. Can you please give me a step by step guide to unlock the bootloader again. I cant flash anything except restoring a TWRP backup, super su, blu_spark. When i unlock using fastboot oem unlock. The device restarts and boots into TWRP
[ONE Android Development] saurabh40629:
Were you able to solve it? I have the same issue.
[MENTION=5381511]Mnt-XDA[/MENTION] , I checked the script and its different for all device. Do you know how can we get to know about offset bit for our device? My device is Oneplus x(onyx).
[ONE Android Development] chak05:
i can't unlock my opo

i can't unlock my opo, trying to follow all your instructions step by step but with no solution :(

C:\ADB Drivers_Updated>adb version

Android Debug Bridge version 1.0.31

C:\ADB Drivers_Updated>fastboot oem device-info

...

(bootloader) Device tampered: false

(bootloader) Device unlocked: false

(bootloader) Charger screen enabled: false

(bootloader) Display panel:

(bootloader) console_enabled: 0

(bootloader) exec_console_unconsole: 0

OKAY [ 0.008s]

finished. total time: 0.009s

C:\ADB Drivers_Updated>fastboot boot twrp.img

downloading 'boot.img'...

OKAY [ 0.357s]

booting...

FAILED (remote: Device not unlocked cannot boot)

finished. total time: 0.370s

thanks for your help
[ONE Android Development] anessie:
'locked' using the fastboot twrp, now I cannot unlock it. Same as above..

\opo>fastboot flash recovery recovery.img

target reported max download size of 1073741824 bytes

sending 'recovery' (9964 KB)...

OKAY [ 0.352s]

writing 'recovery'...

FAILED (remote: Device not unlocked cannot flash or erase)

finished. total time: 0.357s

edit: after being stuck I spend a few hours looking for options, only thing that worked was this http://xdaforums.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
[ONE Android Development] Superb Azam:
Flashfire app support??

can this mod be flashed with flashfire application? because i dont wanna unlock the bootloader just to flash this mod through twrp/cwm custom recovery :confused:

noob here , your help is really appreciated , thanks :o
[ONE Android Development] AWretchSavedByGrace:
Soooo, what're the chances of the tamper / unlock bit reset working on a OnePlus 3? If not, is anyone aware of a method for doing this yet?
[ONE Android Development] cregi:
I am right now with my bootloader unlocked and TWRP recovery installed. I want to restore it to original state for RMA, so in principle I should flash this file to reset the tamper bit, and then flash by fastboot the original rom and the original recovery, and lock again the bootloader. For instance following this guide http://xdaforums.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541

is it like that?

Because if I flash the original recovery first , I will not be able later to flash the reset tamper file.

Am i right?
[ONE Android Development] Mjallo:
Okay I have tried and read everything now :(

Okay.

I have a serious problem with my opo, it just keep on having a new problem to solve.

I have tried to boot into recovery (fastboot boot recovery.img (its TWRP renamed)) but it gives me the (Device not unlocked cannot boot) error.

Have run (fastboot oem device-info) and it returns with Device tampered: true, Device unlocked: false, and if I run (fastboot oem unlock) it just reboot the phone and noting changed.

I may be ****ing dumb here but what am I doing wrong? Is it possible to reset the tampered bit in another way or force the phone to be unlocked? Have tried Wugs toolkit and other toolkits with no dice.

Hope one of you can help me
[ONE Android Development] djha53k:
[MENTION=1958419]Mjallo[/MENTION] sounds like me 28hours nightmare ... search for my post on oneplus.net forum. I wrote there a full guide... maybe I put it here too, but I cannot find it rifht now :( sorry
[ONE Android Development] Mjallo:
Have abit of a problem finding your post on oneplus.net so if you stumple on a link at some point it would be lovely :)
[ONE Android Development] djha53k:
Hello,

seems like it was removed from OnePlus forum... it is 2 years back , uff :eek:

Time is running sooooo fast...

Suddenly I dont have it in engl anymore and I dont have time to translate it right now... we just came back from holiday... a lot of staff to clean :(

How to fix device unlocked cannot flash or erase

but Google translation looks OK...

translated

Let me know if you would need something... :fingers-crossed:
[ONE Android Development] Mjallo:
Sadly I have tried all that, but I cant even install (or boot) twrp recovery. Cant even in cyanogen recovery Apply update->choose from emulated it just cant mount anything.