yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] CuraeL:
-----

Just gonna leave this here even tho I know that the new OTA screws the boot sequence. For the sake of science. And I hate deleting posts and leaving emptiness. <3

-----

I'm on the newest OTA and my phone keeps on telling me that it cannot load the recovery cause my loader is locked. And I'm simply trying to "fastboot boot recovery image.IMG" and also tried "fastboot boot image.IMG" for good measure. I dunno what's up. It just won't temp boot the recovery. Siiiiiigh maaaaan. I set up everything cause I counted on this. :P Seems like I shouldof done my research cause now I really, really don't wanna do an oem unluck, lul. Oh well.

I also have true tampered while having false unlocked. So I dunno man.

For the sake of troubleshootin'

Fastboot works

Get device info no worries

No bootloops or anything

Unrooted

Never been unlocked, mint device that I set up when I was not at my computer, otherwise this wouldn't be an issue.

All in all the device works as it should on stock and nothing's happened from this. I simply can't temp boot the recovery to continue.

Greetings!
[ONE Android Development] abejoker:
Not even Flashify worked for me.
[ONE Android Development] drgelin:
I don't know why cyanogen did it. It is supposed this smartphone is for rooting and custom roms.
[ONE Android Development] 00negative:
I also have device tampered = true, but device unlocked = false. Everything seems to be working fine and I can use recovery, lock/unlock the bootloader etc just cant get the tamper bit overwritten. Tried on 4.4.2 stock image (fresh from Cyanogenmod's site) and that didn't work, ended up applying the 4.4.4 update in the CM stock recovery and trying again and still couldn't get it even with bootloader locked and booting TWRP from the laptop running Ubuntu.
[ONE Android Development] barondebxl:
Ok guys seems this thread is where i can get help for my issue. I got this OnePlus from someone else who had it unlocked before but relocked the bootloader. "fastboot oem unlock" does not work for me at all. Im on the latest update 30o and i want to unlock this bootloader. i have no custom recovery, just the regular CM recovery. Can anyone explain me or giveme the steps on how to do this? a little noobish here. Would be much appreciated thanks!

Edit: All good, big thanks to op and [MENTION=1036857]r8zer[/MENTION]!!
[ONE Android Development] dhruvaz:
Wait what??? which script? i used fastboot oem unlock it worked... but it restarted automatically after it succeeded so I didnt have to use fastboot reboot. its rooted now.
[ONE Android Development] MICa.fighter:
The script in the First Post. Fastboot oem unlock is not a script it is one command. A script is usually a series of commands, in a specific order, in some kind of executable format, like a recovery flashable zip.

Fastboot oem unlock will work fine. But don't forget it will wipe your phone.

Tapatalk'd from my 1+1
[ONE Android Development] dhruvaz:
ah okay.... yea I know it did wipe my phone.. wasnt installed much so it was no biggie.
[ONE Android Development] Dibbyo123:
How to Lock the Bootlaoder ? and remove the Flag ?????????
[ONE Android Development] MICa.fighter:
As far as I understand, the script in the first post is a "toggle" basically. If you are locked, it will unlock, and vica versa: if you are unlocked it will lock. It also removes the flag. Though I am not sure because im on phone and I cant look at the code of the script atm.

Tapatalk'd from my 1+1
[ONE Android Development] webpatrick:
Well cause it was an exploit, this should only be working with an unlocked bootloader. And yes you can root and install custom ROMs, but then you should unlock. It's not that hard.
[ONE Android Development] drgelin:
Yes i know but then i lose all my data
[ONE Android Development] Heisenberg:
So back it up first.

Transmitted via Bacon
[ONE Android Development] drgelin:
Yeah but how?. Titanium backup needs root. Any other utility?
[ONE Android Development] Heisenberg:
You can use an app called Helium to backup without root.

Transmitted via Bacon
[ONE Android Development] MICa.fighter:
OP recently got updated: ,,My Friend [MENTION=945041]Polarfuchs[/MENTION] has confirmed that our unlocker zips are working fine, after new CM11S 30O OTA update."

The unlocker zip's purpose is to unlock/lock without loosing data. So what are you talking about? Did i miss something?
[ONE Android Development] drgelin:
Yes. I wrote a couple of post before. That mod isn't working for me. I'm in stock recovery and the sentence fastboot boot recovery.img doesn't work. It appears a error message: your bootloader is locked. Unlock it first.
[ONE Android Development] 7ewis:
So it is still possible to reset the tamper flag in the latest OTA? And it is definitely working?
[ONE Android Development] 00negative:
No the zips purpose is to remove the tamper/reset toggles from being tripped which showed that the bootloader had been unlocked previously

Edit: shouldn't say remove, should of said reset

---------- Post added at 08:01 AM ---------- Previous post was at 07:57 AM ----------

Didn't work for me, didn't do any damage either but still shows that it has been unlocked previously
[ONE Android Development] Mnt-XDA:
OP Updated , with the following note....

========================================================

Note:

Many users having trouble to UNLOCK their device for the FIRST TIME by using this script.

Let me clarify few things for this mod.

The main purpose of this script is not UNLOCK Bootloader without wiping data.

It's main purpose is to reset tamper bit, which can not be done by any other way.

UNLOCK Bootloader without wiping data -- is another outcome of this MOD.

If you have not unlocked your device before (atleast for 1 time) by using command "fastboot oem unlock", then the script might not work for you.

In case your device is locked and you want to install this script from custom recovery like TWRP/CWM,

it will be possible only if, you can boot temporarily using command -- fastboot boot <custom_recovery.img>.

If this command failed, you will not be able to run the unlocker script and hence device will not be unlocked without wiping data

In which condition the device can be booted to custom recovery by using command -- fastboot boot <custom_recovery.img>, is still not very clear.

before running the command , check your device status "fastboot oem device-info"

and report your error with the following points

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 -- fastboot boot <custom_recovery.img>.

5) Steps you tried.

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

1) Unlock Bit - FALSE , Tamper Bit - FALSE

2) Unlock Bit - FALSE , Tamper Bit - TRUE

3) Unlock Bit - TRUE, Tamper Bit - FALSE

4) Unlock Bit - TRUE, Tamper Bit - TRUE

After getting proper error report from you , we can give confirmation about, in which of the above state,

fastboot boot <custom_recovery.img> will work and hence installing the unlocker script/mod/zip can help you to

UNLOCK your Bootloader without wiping DATA.

Kindly report your issues as I mentioned above...

Thanks

:fingers-crossed:
[ONE Android Development] :
Does temporary recovery still work in the OTA, or would I have to unlock the bootloader now?

EDIT: They've blocked it now in the OTA, :(
[ONE Android Development] LookedPath:
The answer is in the post previous to yours...

Written with Tapatalk on my OnePlus One
[ONE Android Development] ondoy1943:
i did the

command and the result is that my one is in condition 3) as in the above, and i have root. should i toggle the tamper bit to true? or just leave as is? is condition 4) the best to be for my one? thanks...
[ONE Android Development] Polarfuchs:
Condition 3 could be seen as the best for now. Because it says that your device is unlocked although you didn't tamper with it (tampered = false). Which actually is contradictory.

If you want to send your device back for RMA the best state would be condition 1. Because that is the original state.
[ONE Android Development] LiquidSolstice:
OnePlus doesn't give a damn if you unlocked the bootloader or not. They are developer-friendly, unlike companies like HTC, LG, and Samsung.

This is really impressive and all that OP figured out how to do this, but I don't think it's fair to new people to fear-monger them into believing this tamper-bit has anything to do with their warranty.

It simply doesn't. When I hear a story about OnePlus rejecting an RMA because they checked and not only found that the bootloader was unlocked but that they also dove into the bootloader and found that the tamper flag was tripped, maybe then I'll be convinced that this is, in any way, useful. Until then, no.

When you RMA your device, it's because there is something wrong with the hardware. Unlocking your bootloader has no bearing on that whatsoever. They'll take it locked or unlocked because there are only really two ways you can screw up your device; overclocking the crap out of it and playing with voltages to the point where you damage the CPU, and blowing out your speakers because you fiddled too much with the volume.

If you don't damage your phone in those above two ways, you could EASILY get away with shipping them a device that's running Madhi with root and TWRP and they simply would not care.
[ONE Android Development] Polarfuchs:
You are correct. Oneplus doesn't care about the state of the tamper and unlock bit. Furthermore they don't care about your RMA request at all. People are waiting for days yet some even weeks right now, with no response.
[ONE Android Development] dryspuri:
Yes you are right just sell the device don't provide any customer device at all I am waiting for there reply for 2 weeks now. Dont think I can RMA my device at all.
[ONE Android Development] donalgodon:
Can anyone please tell me what is the problem (if any) with having the Tamper Bit not in the default/factory state? :confused:
[ONE Android Development] 00negative:
Read the post above you ... That is what they are debating. It shouldn't be an issue unless you have a rare warranty issue and you are trying to cover your tracks or you are selling it and the customer doesn't want one that had been fiddled with which is going to be rare for this type of phone. Like buying a second hand Nexus and expecting it to have never been unlocked and rooted, it ain't happening.
[ONE Android Development] MICa.fighter:
All true.
[ONE Android Development] LiquidSolstice:
Thanks for the link, I knew they said it somewhere on the site. Just wasn't sure where.

They do say they'll check to see if rooting caused the problem, but again, if you blew out your speakers or cooked your CPU because you didn't know what you were doing and you were trying to push your device to the limits, would it really be fair for you to claim it's OP's fault and that they should repair/replace it?

From a moral and ethical standpoint, I would say no, it's not fair.
[ONE Android Development] nielsscholte:
I have a question for you sir:

I want to completely unroot my OPO. I have the factory image downloaded but how can i reset the Tamper Bit etc?

Thanks in advance!
[ONE Android Development] :
big chance after an ota update it will reset to tampered. It seems to do that
[ONE Android Development] pr3tender:
I received my OPO a few days ago, and the phones loopboots on the android logo.

I can boot into fastboot mode.

I tried to unlock the bootloader via the standard fastboot comand with no success.

I tried to boot to a temporary custom recovery with no success.

fastboot oem device-info says that the bootloader is locked and the phone is tempered.

I tries all this with windows 8 and windows 7.

Please, sew more details in my thread: http://xdaforums.com/oneplus-one/help/loopboot-android-logo-t2850498

I don't know what to do next...does anyone have any ideia?

Thanks!
[ONE Android Development] GeniusJack:
Hi, I've got a problem with a OPO of a friend..

Bits are: Unlock Bit - FALSE , Tamper Bit - TRUE

When I try to flash something from cmd it says that with a locked bootloader I can't do that..

If I put the command: "fastboot oem unlock" it reboot into the cwm recovery (but the recovery installed is the Stock)

What can I do?
[ONE Android Development] :
read the thread

http://xdaforums.com/showthread.php?p=54721639

this might help if fastboot temporary recovery doest work :)

also disable update recovery in development settings
[ONE Android Development] Antiope:
Thanks for the unlock

A very big thanks for this thread, you save my one. I've bought a one with an chinese recovery and with an rom without OTA,I' ve tried to install the last cyanogen and the phone doesn't start again.

I was stuck with fastboot because it was impossible to install something and with your zip you unlock my one and I've followed your instructions and installed the last cyanogen and now 46700 at antutu!!!!

Thanks again.

Great job.
[ONE Android Development] jamesst20:
Does it still works with latest XNPH33R ?
[ONE Android Development] Vonnegut:
33R hasn't changed the bootloader, so it must still works.
[ONE Android Development] jejehtc:
Hello there,

I'm on the new 33R version not rooter and what method should I do to have tampered with the False and False unlock in because I can not put the two in False I have to be one or the another False.

I am in stock recovery and flash the script I go through the manipulation of fastboot boot recovery.img

See my screenshot attached.
[ONE Android Development] wonger007:
If my flags are

unlock = true

tampered = true

am I ok? I can get into TWRP, but whenever I try to install root on 33R, it wont give me root.

Update: I fixed it by installing it within the Android supersu app using "normal" rather than TWRP
[ONE Android Development] Barleyman:
Doesn't work.

Not a previously unlocked phone here with latest OTA.

D:\Incoming\Google Drive\Oneplus one>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

and

D:\Incoming\Google Drive\Oneplus one>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.390s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.392s

So I'd say it's safe to assume this simple custom recovery temporary boot exploit has been closed and won't work anymore. I just wanted to root without factory reset but it seems it's not going to happen.. I think another exploit is needed, which probably needs (ha-ha) toolkit or at the very least a batch file as that sort of thing usually requires a fair number of abusing in-phone recovery-style options etc.

Btw it would've saved me a fair amount of cursing if the op mentioned fastboot commands only work on bootloader.. Been there, done that, but by the time I get a new phone I've forgotten about that sort of thing already.
[ONE Android Development] Vonnegut:
That's not an exploit. They just decided to forbid booting a temporary recovery. You will also find out that it was a really bad idea to relock the booloader, 'cause now you won't be able to unlock it anymore using the fastboot oem unlock command.

I already helped a guy to get out of that situation anyway..

In case you'll need help, i'm here.,..but you'll have first to swear by your God to not relock the booloader again for the rest of your life :)
[ONE Android Development] Barleyman:
I never touched the bootloader so far. I'm actually setting up helium here for the official factory reset method of unlocking.
[ONE Android Development] ram11:
Hi, what is the official factory reset method of unlocking? Could you please explan or give me a link?

I am planning to unlock the bootloader to install custom rom. Seeing conflicting messages after the new update
[ONE Android Development] LiquidSolstice:
The official method (which, going forward, you should always do on any Nexus-based device or open bootloader devices like the OPO) is rebooting into fastboot mode, and from a computer, issuing the command "fastboot oem unlock". This wipes the entire device completely (including storage) but you only ever have to do this once during the lifetime of the device.
[ONE Android Development] cyanoviper:
really? One one uses fastboot oem lock, you can never fastboot oem unlock again? That wasnt the case with nexus phones was it?
[ONE Android Development] Vonnegut:
Happened to some guy who posted in this very thread...and some of them were quite pleased to know that they could unlock it again thanks to the script. Anyway that was possibile before 30O came out: with the new bootloader the fastboot boot recovery.img command doesn't work anymore (if the aboot is locked).

Let me tell you a story about ppl freaking out to unlock their bootloader...

There was a guy who did unlock his bootloader running the script after booting a custom recovery (he was still on 25R). Then he flashed the TWRP. After that he relocked the bootloader. After some time and a pair of OTA he realized he couldn't

boot

any recovery from fastboot anymore and it couldn't enter the installed recovery as well. Moreover, he didn't root his device...and finally fastboot oem unlock wasn't working anymore.

What is funny is that the tamper bit was set to TRUE so he was paranoid about being out of warranty for no reason.

Is there a way to save such a situation? Think about it...
[ONE Android Development] SamdungSpambot:
Some help here please...

I bought a used opo and just wanted it returned back to stock it was rooted.

After I master reset it...it just goes into twrp and freezes

Phone still works though.. I used a toolkit to look around and see that its tampered true and unloc is false. Its on the latest os. Is there a way I can unlock the bootloader and put it back to 100% stock otherwise?

When I run the unlock bootloader script from fastboot it does the 5 sec thing and reboots into twrp and doesn't do anything after.

I also can't boot a "temp" recovery anymore either
[ONE Android Development] andrej01:
Hi, what if you want to reset the 1+1 to complete factory settings? I rooted my phone and it's acting, well not as it should. So I wanted to set it to complete factory default, to see if anything will change. But just wiping it doesn't reset the flags (the phone is still rooted even after flashing it). So my question is, how to actually set the bits back to false? Thank you for your answer :)
[ONE Android Development] Vonnegut:
Did you read the post just before yours?
[ONE Android Development] SamdungSpambot:
I did..so is there a way to save it?
[ONE Android Development] Vonnegut:
Are you rooted?
[ONE Android Development] SamdungSpambot:
Yes Sir I believe I still am
[ONE Android Development] Vonnegut:
In this case, we can do something to fix that :good:

You're the 4th guy going trough this...

I'll tell you what we are going to do in order to fix the bootloader:

A) we need the script to unlock the bootloader http://xdaforums.com/attachment.php?attachmentid=2876403&d=1406718707 Download it and save it for now.

B) we need a working custom recovery. Since i'm sure that it works fine i suggest the TWRP 2.7.1.1 http://techerrata.com/file/twrp2/bacon/openrecovery-twrp-2.7.1.1-bacon.img Download it, rename the file to TWRP.img and save it for now

C) Since you used a toolkit, you already have installed the right ADB drivers. Anyway, since i'm not there with you, in order to make my task easier, download this file http://www.mediafire.com/download/s4yibc9qedo1geo/ADB.zip, unzip the folder and move it to your root C:\ (you're running windows aren't you?). I need to have both ADB.exe and fastboot.exe in C:\ADB, ok?

D) make sure you unblocked the developer options in your setting. Then enable USB debugging.

E) put the TWRP.img in the C:\ADB folder. Put the the flashable script in the OPO internal storage.

F) make sure everything is ok. Just do the following stuffs:

F1) plug the OPO to your PC

F2) open the prompt in windows (if you don't what that is just click START--> RUN and type cmd (then press return).

F3) you will see a windows with a prompt like this C:\user\your_name_or_nick

F4) type cd c:\adb (then press return) and your prompt will change to c:\ADB

F5) type adb devices (then press return). After a few seconds you will see the the daemon starting and listing your device (that is an alphanumerical string)

G) if everything is set and working come back to me
[ONE Android Development] SamdungSpambot:
got a device... says its unauthorized.... zip file loaded i'm ready
[ONE Android Development] Vonnegut:
Unauthorized? you should see something like this...

http://www.mediafire.com/view/v44u90m36n4bch7/prompt.JPG

Have you really done everything stated in my previous post?
[ONE Android Development] SamdungSpambot:
yeah that's what i have but next to the number..instead of device it says unauthrized

i'm an idiot... working now... i didn't click ok on my phone when it asked for usb debuggin access
[ONE Android Development] Vonnegut:
:good:.

Now, since you can't boot into your custom recovery anymore, we need to replace the aboot partition with the one coming with 25R.

So you're last task is to download the official .zip 25R zip http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH25R-bacon-signed-fastboot.zip

Then you have to extract the emmc_appsboot.mbn file and put it in the root of the internal storage of your OPO (where the script should already be).

We are going to flash it over the 33R aboot...

Doing so, we'll able to boot the TWRP.img and flash the script.

When you're ready to start, plug in your phone to the PC.

Open the prompt windows and write cd c:\adb and adb devices, if everything is ok, we should proceed.

Write adb shell (return) on the prompt and you will see the prompt changing to shell@android:/ $

Then write su (return) and check your phone 'cause SuperSU (or whater superuser you've installed) should ask you if you want to grant ADB. Grant it of course. The prompt will change to root@android:/ #

Now, copy and paste this command in the prompt windows and press return

dd if=/data/media/0/emmc_appsboot.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot

We have flashed the 25R bootloader now :good:

Now write exit and press return 2 times and your prompt will change back to C:\ADB.

Write adb reboot bootloader and your OPO will reboot in fastboot mode.

Now write fastboot devices (return) just to check if everything is ok as usual.

Then write fastboot boot TWRP.img (return) and your OPO will boot into recovery.

From there, press install and select the script .zip...then flash it, go back and find the option to reboot to bootloader.

Write fastboot oem device-info in the prompt and you should see both the tamper and the bootloader set to TRUE now :good:

Now you can unplug your phone and do whatever you want. If you want to flash back the 33R bootloader, i'll tell you how.

Good luck!