yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] djha53k:
Maaaan what have U done to your One?

U broke it even more then I did [emoji33]

But One is awesome device! U should be able to fix it by fast boot, just overwrite it from scratch, fast boot saved my a** everytime I "fixed" my One [emoji41]

Boot to fast boot (vol up+ power) connect to PC and overwrite everything... that should work everytime ;)
[ONE Android Development] Mjallo:
Nope "device not unlocked" error when trying to flash anything.

I bought it like this and the only thing the old couple that had it was that they let it update but it ran out of battery (because they did not press confirm, and just let it drain the battery).

Here is the readout by the ColorOS installer http://imgur.com/w1zOQFU

This happens when I try to Sideload a update (have tried to do it with the unlocker) http://imgur.com/6L74N6J
[ONE Android Development] djha53k:
Man WT* is that?! Please follow my guide. Do not use any GUI app, just use simple Google fastboot and adb. Links to zip is in my guide.

Just use "fastboot" and "adb" commands directly from "cmd" window, do not use anything else.

I cannot help you more remotly, just try follow my guide precisely. It works I spent 28 hours to prove it [emoji56]

Or I can sell you my One as I had to sell it [emoji22]

Edit: what is output of "fastboot oem device-info" ???
[ONE Android Development] Mjallo:
Have used CMD to do all that but just had that picture that showed some useful info.

When I do "fastboot oem device-info" It gives me tampered: true, Unlocked: false.

Have tried most of the guides and have tried a bunch of tools other people had success with but none is working.

The root is all my problems is that it is not unlocked and therefore I cant install a new backup or boot in to on (using Fastboot boot "filename".img) because every thing says it is not unlocked to flash.

I dont understand why this opo is so square because my other opo works great and can be flashed to all my hearts content
[ONE Android Development] djha53k:
OK, so the

fastboot oem device-info"

gives

then you need to have One in the "Fastboot", then run

fastboot oem unlock

which should change both to TRUE.

If not, then you will need this file info how to is here .

This should help you to have this:

then you should be able to:

fastboot flash recovery recovery.img

:good:

Of course you need to have the "recovery.img" in the same folder as you have the "fastboot" binary file. Also you can name is as you want ;)
[ONE Android Development] CBpbxEcmecmBeH:
and this?

http://android.stackexchange.com/questions/133576/how-to-re-unlock-bootloader-for-oneplus-one
[ONE Android Development] Mjallo:
Oem unlock do not work. It just reboot the phone and changes nothing.

Have tried to use the boot-unlocker but that gives me cant mount or flash error (depends on if I try to sideload it or feed it though cmd).

I may be retarded but the OnePlusOne-BootUnlocker.zip is installed with cyanogen "apply update" right? (thats when you sideload it with adb), because that just gives a error screen like this http://imgur.com/6L74N6J

I have tried to push the file onto the memory with cmd and tried to run it but that just make the same error like the sideload one.

I sorry for asking so much for help but I have run out of ideas to try fixing it, I just feel like it should be possible to do because the Cyanogen Recovery menu works and it "boots" (just not past logo)

---------- Post added at 02:27 AM ---------- Previous post was at 02:24 AM ----------

Cant do that because

Unlock the bootloader (fastboot oem unlock) Does nothing and just reboots the phone.

Boot TWRP (fastboot boot twrp-2.8.6.0-bacon.img) cant boot that because the phone is not unlocked so it cant flash it to memory

So It is a endless cycle with not being able to flash so I can unlock it so I can flash :(
[ONE Android Development] djha53k:
I dont belive that, One is possible to fix till it is not physically broken ;)

Can U share video with fastboot commands (unlock and flash recovery)?

If you are near Prague ... come to visit me ;)
[ONE Android Development] Mjallo:
Thanks for the offer.

I'm working on making a video with the commands running but I have alot going on right now (sorry for the late reply)
[ONE Android Development] Mjallo:
Okay have tried to make a movie, here is the link https://www.youtube.com/watch?v=IPl9L8yXNSs

I have taken a picture of the phones screen when I try to sideload. http://imgur.com/a/rBjTM

Hope they are okay, have not made videos this way before.

PS. I forgot to film me trying booting recovery but the result is the same as the boot.img
[ONE Android Development] djha53k:
Hmm man, then I'm sorry, but I have no idea :(

In 2:38 after "unlock" the One should be "Unlocked = True".

Its very strange, that it is " False" again.

Does One reboot after U hit "fastboot unlock" or nothing happened on device?
[ONE Android Development] Mjallo:
It reboots the device when "fastboot oem unlock" have been run. Thats why is have read this thread and tried to flip the bits so it was possible to make it false again. My research have showed that it may be a borked update from one Cyanogen edition to another that have caused the flip
[ONE Android Development] djha53k:
It is very wiered, should not be like this :(

I'm truly sorry, but seems I could not help you. I thought I have seen all fastboot errors already, but seems you have found another level of this...

It just popuped in my mind...

U might give try to install CM11 recovery image to overwrite all partitions and try this again. I just remember that it helped me once as well. Just get the original CM11 fastboot recovery image and overwrite whole mobile by that...
[ONE Android Development] Mjallo:
Will try using CM12 recovery image https://download.cyanogenmod.org/?device=bacon

Will use CM11 Image if you know where to get that.

---------- Post added at 11:26 PM ---------- Previous post was at 11:21 PM ----------

Yeah same results with the CM12 image.

I'm starting to think I maybe just should sell it because the screen and case is fine and someone maybe need that, but I would love to fix it
[ONE Android Development] djha53k:
Hmm, maybe that would be the fastest solution. I can sell you mine, as I have to buy new mobile, suddenly :'(

I'm sorry, I cannot help more remotely :'(
[ONE Android Development] santhosragav:
device unlocked false

1) Did you unlock your device before by any means ? (or by fastboot oem unlock) ? ya unlocked oem but it says u r not rooted ur device

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

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

4) What error msg you got when tried to run command fastboot boot <custom_recovery.img>. FAILED (remote: Device not unlocked cannot flash or erase)

5) Steps you tried. tried al the steps but no use
[ONE Android Development] piriri007:
hello,

also the same problem:

1) Did you unlock your device before by any means ? (or by fastboot oem unlock) ? UNLOCKED with fastboot oem unlocked. Phone rooted.

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

3) What is the status of your device ?

- i can only access to fastboot screen in phone and i can do fastboot commands in pc;

- command 'fastboot oem unlock' doesn't work (error: FAILED (remote: oem unlock is disabled) )

- command 'fastboot flash recovery <flash.zip>' doesn't work (error: FAILED (remote: Device not unlocked cannot flash or erase))

- all adb commands say: "error: device not found"

- i can't access twrp recovery for use adb sideload (with VOL DOWN+POWER the phone freezes with 1+ icon in screen)

- i can't access Android (on booting phone freezes with 1+ icon in screen)

C:\adb>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.000s]

finished. total time: 0.000s

4) What error msg you got when tried to run command fastboot boot <custom_recovery.img>. FAILED (remote: Device not unlocked cannot flash or erase)

5) Steps you tried. tried al the steps but no use

Can anyone please help?

thanks
[ONE Android Development] Lanchon:
this thread can't help you so don't post here anymore.

this thread is for people that want to change the lock status of their phone having root access to it.

you dont have root access; you dont have any access at all.

you have 2 options:

1) recover as if hard-bricked using the colorOS magic files. google and read carefully.

i wont answer any questions regarding 1) that you miss-post on this thread.

2) otherwise you could do this:

-it is simpler but hasn't been done by anyone to the best of my knowledge; but should work.

-you need to have a tinkerer's mindset and prepare to go through uncharted territory.

-you need linux and experience using linux tools.

-you should post on this thread ONLY IF YOU CHOOSE OPTION 2): if you choose option 2) what you do is relevant to this thread.

-you wont loose your data if you do this.

-i can't help you.

-this is what you should do:

a) get your opo to power on in QHSUSB_BULK mode. google; i think it requires the phone being off, then holding down some button (not the power button), and then plugging it to a computer.

b) once in QHSUSB_BULK mode you should be able to access the device partitions from the PC. immediately back up images of all the partitions you think are valuable (using 'dd' or the 'Disks' GUI tool in linux mint for instance). most important is the partition where IMEI is stored (google). also important might be userdata, where all your files are.

c) now read this thread carefully. you will see that the flashable script just toggles 1 bit in one partition to lock and unlock the device.

d) to unlock the device, you just need to toggle this bit from the PC. you can use code similar to the one used in the flashable script because in QHSUSB_BULK mode the partitions will be visible to the PC's kernel. you can pull an image of the relevant partition to the PC and test your code against the image before running it against the real device. you can make the image file appear as a real device partition using a loop device or the disk image mounter GUI in linux mint (right click on the *.img file, then go see the device in 'Disks' (and you can unmount it from there)).

e) now reboot to fastboot and your device should be unlocked. flash a recovery, reboot recovery, and start setting up your phone again.
[ONE Android Development] krishna442:
Worked for me on COS13.1.2. Thanks a lot.
[ONE Android Development] polinatirohit:
My oneplus one struck on boot logo. oneplus one automatically it struck in bot logo and tried to recover with oneplus restore tool and msm8974 download tool but it is showing only oneplus logo.I even tried it with fastboot mode in fastboot mode I had typed fastboot oem unlock and in that it is showing device unlock false and device tampered true. What should I do now?
[ONE Android Development] abcdandroid:
Hello All,

I really need some guidance here.

1. Completely Stock One Plus One, and Encrypted too

2. After a SIM card change it just went in a reboot and it is stuck at Cyanogen Mod Logo

3. Fastboot and recovery is accessible

4. In recovery I tried Wiping Cache and it tells ; E: Failed to mount Cache (invalid argument)

5. adb devices does not show anything

6. fastboot oem device-info shows this

Tampered True

Unlocked False

//Ask

Is there any way to reset this Tamper bit back to 1 as I am on completely stock unrooted ROM where I cannot mount any drive via Wipe Cache. Goal is to keep user data intact. I am willing to reverse fastboot if that helps me to achieve this but need some guidance from experts here.

Thank you so much for reading!
[ONE Android Development] SBCR7:
Help please

Please help me I'm stuck and I am very new to this forum and rooting mobiles .

My fastboot oem device-info shows that

DEVICE TAMPERED : False

Device unlocked : True

Device is verified : False

Charger screen enabled : Faslse .

What shall i do . Please help

I have a One plus 2
[ONE Android Development] d-r0ck:
Sorry noob questions here...

Do I have to have CWM or TWRP to install this script?

Or do I just c/p the code with the cmd window open?
[ONE Android Development] MonkeyRugger:
This is such an old post but I had the issue of Hardbricking my phone trying to upgrade my OnePlus One and now I am trying to lock and rest the flags for the bootlocker.

Am I to run the flags in the cmd while my phone is in Fastboot Mode? I am just stuck on this last part. This is what I am getting in CMD

C:\Users\MonkeyRugger> fastboot oem device-info ... (bootloader) Device tampered: true (bootloader) Device unlocked: true (bootloader) Charger screen enabled: false (bootloader) Display panel: OKAY [ 0.014s] finished. total time: 0.015s C:\Users\MonkeyRugger>Parition - aboot (bootloader) 'Parition' is not recognized as an internal or external command, operable program or batch file.

I have downloaded the zip and I placed it on the phone's storage itself too. I am all confused. Any help would be greatly appreciated.
[ONE Android Development] 2643625:
OPO softbricked fastboot mode but no recovery.

Hi everyone,

Hopefully someone can help...

OnePlus One softbricked bootloops to Android OnePlus One logo with Fastboot mode working but NO recovery therefore I can't use adb. Windows drivers on my laptop are OK because I used to get access to my OPO so many times using adb, mtp, Fastboot and access to internal storage.

OPO 64Gig Global Version

Multirom/TWRP 3.1.1-0 2017-07-11 p1

ROMs:

As a Primary ROM:

Lollipop bacon-userdebug_5.1.1_LMY48Y_a84dbba7eb_tes NETHUNTER

As secondary ROMs:

Marshmallow cm13.0-ZNH5Y-170703-SULTANXDA

Nougat lineage-14.1-20171126_233224-UNOFFICIAL-Sultan-bacon

How I got there? I tried to update the third ROM and my OPO could only reboot into TWRP with no access to system (ROMs). That was the first and last time I used OTA instead of simply dirty flashing as usual...

Then I tried to return my OPO to stock using this fix because I have Nandroids for each ROMs and a good backup of my sdcard (internal storage).

https://xdaforums.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390

I runned the 3 *.bat files in the proper sequence and I got errors (see Oneplus_One_Patch_result.txt)

Since then my OPO can only reboot in Fastboot mode with no access to adb commands (see Fastboot_Commands_OPO_Troubleshooting.txt)

From what I read I realize now that I had a much better situation when booting into TWRP only...

C:\Users\HM>fastboot oem device-info

...

(bootloader) Device tampered: true

(bootloader) Device unlocked: false

(bootloader) Charger screen enabled: false

OKAY [ 0.029s]

finished. total time: 0.031s

I need to change the tampered and unlocked bits but how can I do that using fastboot?

One post (https://xdaforums.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912) is suggesting this Code but I can't figure out how to do that...

"Once you unlock, both bits will come TRUE. This mod will write the 2 bits in aboot partition and can reset

both bits (TOGGLE Bcsically) without factory reset as opposed to fastboot command fastboot oem unlock

So for One Plus One...

Code:

Partition - aboot (bootloader)

Unlock Bit Position - 0x000FFE10 Hex - (1048080) Decimal

Tamper Bit Position - 0x000FFE14 Hex - (1048084) Decimal

By [MENTION=945041]Polarfuchs[/MENTION]"

Let me know if you need more info.

Thank you for reading and I really hope someone will read and help.
[ONE Android Development] Malaach2:
Bootloader Unlocked!!

Thank you for this work!! :):):):):):):):)
[ONE Android Development] rshoreview:
Please help - bricked my OPO bacon

Please help!!

I have messed up my oneplus one bacon

I was using lineageos 16 and all was fine. For some dumb reason 'Screen mirroring', I decided to go back to lineageos 15.1. Somewhere in the instructions I read, a clean wipe is recommended to go back to previous release.

I wiped all my partitions from twrp

As a result, my system partition is lost.

I tried to flash the stock recovery and stock ROM

Recovery flash was successful and so I am on CWM, but the ROM failed as the system partition could not be mounted/unmounted

Now, my phone's state is

ADB does not work.

Fastboot works, but am unable to unlock my bootloader, not sure how it got locked.

>fastboot oem unlock

OKAY [ 0.009s]

Finished. Total time: 0.019s

It simple reboots to the recovery without unlocking

>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.021s]

Finished. Total time: 0.028s

I was hoping this thread would help me. But not sure how to apply this fix

I am unable to flash or boot as I get the following error

FAILED (remote: ' Device not unlocked cannot boot')

fastboot: error: Command failed
[ONE Android Development] eiwarmer:
You need to go to this thread:

https://xdaforums.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851/page34
[ONE Android Development] opo2014:
Unable to reset unlock and tamper bit for opo

Hi,

I have upgraded opo to lineage os 17.1. post that had run command fastboot OEM lock. Since then I am unable to unlock bootloader as well.

Had tried all 3 scripts as given in thread but no luck.

Device tamper status says true and unlock status status says false when I run fastboot oem device-info

Pls help
[ONE Android Development] Heisenberg:
The part where it says to install the SU.apk, you just download Superuser from the Play Store. Open it and follow the prompts.

Sent via Bacon
[ONE Android Development] r8zer:
Or go to chainfire's website and download the su.zip from there and install when u are in custom recovery

http://download.chainfire.eu/396/SuperSU
[ONE Android Development] rahulrai:
my screen giving problems with touch sending for rma. anyway thx for helping guys.
[ONE Android Development] Mnt-XDA:
OP Updated..

To avoid confusions and make things easier , I created 2 NEW Flash-able scripts

1) OnePlusOne-OnlyBootloaderToggle.zip

2) OnePlusOne-OnlyTamperBitToggle.zip

Whoever facing issue with the main unlocker script ... please try above scripts and please confirm me that it works or not...

:) Enjoy!!!
[ONE Android Development] Maxim92:
What does "tampered" and "Charger screen enabled" even mean?

[MENTION=5381511]Mnt-XDA[/MENTION]

So now is like this:

...

(bootloader) Device tampered: false

(bootloader) Device unlocked: true

(bootloader) Charger screen enabled: false

Should Device tampered and Charger screen enabled result true? And what if they are false: what does it even mean and how to correct?

Thank you
[ONE Android Development] Mnt-XDA:
1) I don't know what is the purpose of --- Charger screen enabled: false / true

As its name indicates , it is something related to screen that show charge animation probably when phone is off.

2) Device unlocked: true / false --- indicates that you can perform fastboot flash operaion on any partition to install ROM

You need to unlock bootloader to do this.

fastboot oem unlock / lock

3) If you unlock bootloader ( say for the first time for your device)

the Tamper Bit set to TRUE -- indicating that user performed oem unlock atleast for once..

This bit might be used for checking warranty.

Hope this can clear your queries...
[ONE Android Development] Maxim92:
1. Could it be that you cannot access Bootloader from offline charge animation screen? Because when I try to do so, Bootloader won't show up and the device will reboot normally (at least, on my OnePlus One)

By the way, doesn't seem that this is something important and that either is true or false doesn't really matter.

2. I unlocked bootloader with your mod. From what I understood if I did using Fastboot command: fastboot oem unlock, I would have lost all the user data, correct?

3. Then why on my OPO the Temper Bit is still false? Wasn't it supposed to change to True?
[ONE Android Development] Mnt-XDA:
1. Could it be that you cannot access Bootloader from offline charge animation screen? Because when I try to do so, Bootloader won't show up and the device will reboot normally (at least, on my OnePlus One)

By the way, doesn't seem that this is something important and that either is true or false doesn't really matter.

Right , Not that important

2. I unlocked bootloader with your mod. From what I understood if I did using Fastboot command: fastboot oem unlock, I would have lost all the user data, correct?

YES Correct

3. Then why on my OPO the Temper Bit is still false? Wasn't it supposed to change to True?

I don't know the operations that you or your seller performed before with bootloader.. ( Chinese version or International ?)

Try to lock bootloader by fastboot command first, then try to unlock by fastboot command

Then see the oem-deviceinfo

After that Tamper bit should show true...

Let me know...
[ONE Android Development] analyst28:
I can not get this to work no matter what I try. I am currently running stock everything, when I try to boot into twrp through fastboot I get the message "Device not unlocked cannot boot" what am I missing?
[ONE Android Development] r8zer:
Did u fastboot with this

Fastboot boot recovery recovery.IMG(this should be name of your recovery.IMG)
[ONE Android Development] analyst28:
I type

"fastboot boot twrp.img"

I get

"downloading 'boot.img'..

"okay

"booting..."

"failed device not unlocked cannot boot"

I have renamed my recovery to twrp.img
[ONE Android Development] r8zer:
Then u need to do this

Fastboot boot recovery twrp.img
[ONE Android Development] analyst28:
When I type exactly that I get

"cannot load 'recovery' : no such file or directory"

Thank you for the advice so far..

---------- Post added at 03:57 PM ---------- Previous post was at 03:53 PM ----------

Just to be clear, I am currently running stock recovery, no root, with a locked bootloader.
[ONE Android Development] Polarfuchs:
Is your twrp.IMG located in the same directory as your adb and fastboot exe?
[ONE Android Development] r8zer:
Right when u type fastboot devices does it see your device.

Do you have the USB drivers installed.

Do you also have adb working.

If so is the twrp.IMG in the same directory as the fastboot comand
[ONE Android Development] r8zer:
Is the twrp file in that same folder aswell
[ONE Android Development] analyst28:
I have been through this process before but I have always just used the OEM unlock command and then flashed TWRP. Am I correct in thinking that this is a method of unlocking the bootloader without having to erase the device?
[ONE Android Development] r8zer:
Yes u would be correct. Makes life so much easier.
[ONE Android Development] analyst28:
This is really making me crazy, it seems to be sending the file it just wont boot into it...
[ONE Android Development] r8zer:
Also I didn't think platform tools is used anymore

Also what platform are you running. Windows. Linux. Mac.

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

Does it say loading OK.

Can u Post a video of what you are doing.

Do you have the correct recovery image.

Have you done fastboot devices to see if your device is seen. Also have you put the phone in fastboot mode.

Silly I know??
[ONE Android Development] analyst28:
I am running windows 7. Would you believe fastboot oem unlock just worked fine?? I am starting from scratch now.. Thanks for your help.
[ONE Android Development] r8zer:
No problem. Shame I could not help. But hope all further ventures into the world of rooting and all. Good luck.
[ONE Android Development] Mnt-XDA:
If you do this once ...

fastboot oem unlock

then

fastboot boot twrp.img

... will work

After that you can reset the unlock and tamper bits

===

If you like to root device without data wipe for the first time

You can try this technique..

https://forums.oneplus.net/threads/root-without-wipe.62709/#post-2895271

https://forums.oneplus.net/threads/root-without-wipe.62709/page-2#post-2903595

Try and let me know...

:good: