yashsingh1/xdaforums huggingface dataset:
[ONE Q&A, Help & Troubleshooting] playya:
The guide I provided does not require you to have a unlocked bootloader. This is to restore phone to 100% stock and is done in fastboot with fastboot commands. Are you sure you read it right

Straight from Cyanogen themselves right here

Instructions:

First time flashing CyanogenMod 11S on your device, or coming from another ROM (e.g. ColorOS)?

Download the file cm-11.0-XNPH25R-bacon-signed-fastboot.zip to your PC from the links below
Reboot your device into Fastboot mode by holding PWR+VOL-UP
Connect your device via USB to your PC
Unpack the downloaded zip
Open a command prompt (Windows) or terminal (Linux/Mac) and perform the following fastboot 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 update cm-11.0-XNPH25R-bacon-signed-fastboot.zip
[ONE Q&A, Help & Troubleshooting] gunvald89:
Thanks your suggestion. I tried that and is just says that I have the same driver installed. Also tried to uninstall every driver that has anything to do with google android and phones and then reinstall. I also tied to install from my Android SDK folder but I got the same message.

Oh nice. I will try that after i get the drivers up and running!
[ONE Q&A, Help & Troubleshooting] gunvald89:
I have come so far that I can see that something may be wrong with my driver. When I run “adb devices” I get noting on my list but when I run “fastboot oem device-info” I actually get info. I have tried googles driver, naked driver, Samsung driver. Before every driver I uninstall everything using USBDeview. Then I disconnect the computer from the internet otherwise it will auto install. Plug in the phone when it is in fastboot, and select the driver I want to install. Tested on a win7x64 and one win8.1x64 computer.
[ONE Q&A, Help & Troubleshooting] DuckMcQUack:
I used that drivers on my pc with Windows 7 64bit and they worked flawlessly...are you sure that you're selecting the correct adb driver when prompted?

Inviato dal mio One utilizzando Tapatalk
[ONE Q&A, Help & Troubleshooting] playya:
where are you running "adb devices" in fastboot or in adb after your phone has booted up. When you check for your devices in fastboot the command is "fastboot devices"

My friend honestly slow down and please please please please starting reading everywhere before you start messing with your phone anymore. You seem to be a little anxious on getting your phone back up and running but you may cause further damage if you do not know what you are doing and why you are doing it...
[ONE Q&A, Help & Troubleshooting] gunvald89:
Hehe spot on. Anxious? Totally. Want my phone to work? Desperately. I began to be so confused when everybody was talking about “adb devices”. Now I understand that it will not respond when I’m in fastboot.

With “fastboot devices” I got my phone in the list. Does that mean that the drivers are okey?

If you have the time and patience, please ad me on skype. My nick is gunvald89
[ONE Q&A, Help & Troubleshooting] playya:
skype I do not have sorry and patience comes and goes but more than happy to help you out though. Its your thread say what you want... LOL

Yes if your phone shows up on the list then you are good to go... Simply start the copy and paste procedure of sending the files to your phone

Edit: Download proper factory image according to this thread here
[ONE Q&A, Help & Troubleshooting] gunvald89:
I understand, but it was worth a shot. :)

Regarding the Guide “Return your OPO to 100% Stock” it doesn’t work for me because my bootloader is not unlocked. (See stage 3). But at least I got the factory image.

The guide named “CyanogenMod 11S” looks very promising but again it seems to be rely on an onlocked bootloader.

My log:

C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash modem NON-HLOS.bin

< waiting for device >

target reported max download size of 536870912 bytes

sending 'modem' (56241 KB)...

OKAY [ 1.766s]

writing 'modem'...

FAILED (remote:

Device not unlocked cannot flash or erase

)
[ONE Q&A, Help & Troubleshooting] zephiK:
http://xdaforums.com/showthread.php?t=2386956 I prefer these drivers. They work great on the OPO.

I'll help out :)
[ONE Q&A, Help & Troubleshooting] playya:
is this the only file it fails on? Or was this the first file you tried
[ONE Q&A, Help & Troubleshooting] zephiK:
Sounds like his bootloader is locked. OP's bootloader needs to be unlocked.
[ONE Q&A, Help & Troubleshooting] playya:
yeah I see he is trying to get some love over in CM main thread as well. Question - I never had this issue so curious does the bootloader need to be unlocked to flash all of those files?

Just googling trying to see if there is anyway to help him
[ONE Q&A, Help & Troubleshooting] gunvald89:
I tried everyone. Same error

That is correct! And I can’t unlock it with the regular command. Therefore I tried flash factory rom because maybe it didn’t need a unlocked bootloader. Unfortunately it need a unlocked bootloader and I don’t know what to do.
[ONE Q&A, Help & Troubleshooting] playya:
Yeah man I am googling to see what to do to help you.... Quite sure someone else has dealt with this
[ONE Q&A, Help & Troubleshooting] zephiK:
http://xdaforums.com/showthread.php?t=2731638&page=22

read pages 21-23. OP needs to use the tamper thing.

OP probably had his bootloader unlocked and then relocked it again causing it not to be able to unlock unless you use the tamper bit mod.

http://xdaforums.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
[ONE Q&A, Help & Troubleshooting] playya:
I think thats the route to take right there [MENTION=5118853]gunvald89[/MENTION] . fastboot into recovery and flash the zip file and see what happens from there. I like the success stories that I have read. This is why I read all these threads to see what not to do and how to fix it if it does happen.
[ONE Q&A, Help & Troubleshooting] dansou901:
Yeah. He can also just use the provided solution to unlock the phone by that tamper mod. IMHO it's quicker that way...
[ONE Q&A, Help & Troubleshooting] gunvald89:
Cant use adb-commands. Only fastboot.

Tried that with twrp.

C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot boot openrecovery-twrp-2.7.1.1-bacon.img

downloading 'boot.img'...

OKAY [ 0.390s]

booting...

OKAY [ 0.021s]

finished. total time: 0.415s

And then the phone rebots
[ONE Q&A, Help & Troubleshooting] zephiK:
You can only use fastboot commands in fastboot mode.

You can only use adb commands in recovery mode.

What are you trying to do OP? Please explain to us in the most minimal sentence possible on what you're trying to accomplish so we can help you achieve that.

Right now I'm confused on what you want to do as you're trying to do 3-5 things at once.
[ONE Q&A, Help & Troubleshooting] playya:
when the phone reboots you can use adb to transfer over the zip file to your phone at that point
[ONE Q&A, Help & Troubleshooting] zephiK:
op needs to

1. unlock his bootloader using tamper bit

2. fastboot flash recovery openrecovery-twrp-2.7.1.1-bacon.img

3. boot into recovery

4. adb sideload ur rom zip.
[ONE Q&A, Help & Troubleshooting] playya:
I think he is trying to get his fastboot to unlock since he was in a bootloop when he tried fastboot oem unlock. I would assume after running the exploit he would like to have his phone boot up and if not he can at least unlock his bootloader and flash the stock images
[ONE Q&A, Help & Troubleshooting] gunvald89:
How do i do that? After the phone reboots it reboots in to a never ending loop. I never get to recovery or android OS.

Correct.
[ONE Q&A, Help & Troubleshooting] playya:
did you do this - just change name of recovery to below. I know its not a big deal just saying

Boot with TWRP and Flash

If “fastboot devices” worked without error, type this:

fastboot boot recovery.img

After the recovery.img transfers, your phone reboots into TWRP.
[ONE Q&A, Help & Troubleshooting] gunvald89:
I tried to changed the name openrecovery-twrp-2.7.1.1-bacon.img to recovery.img and run the command "fastboot boot recovery.img". Correct?

After a couple of seconds the phone restarts in to the loop. It reboots every 10sec. No TWRP, only the oneplus logo.

C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot boot recovery.img

downloading 'boot.img'...

OKAY [ 0.390s]

booting...

OKAY [ 0.021s]

finished. total time: 0.415s
[ONE Q&A, Help & Troubleshooting] playya:
Ok as I have seen you asking in threads - how do you implement the tamper flag withing fastboot since thats all you have right now. I for some reason dont understand how to accomplish that. Its probably because I am at work trying to help you out and get my stuff done.... LOL
[ONE Q&A, Help & Troubleshooting] zephiK:
Can you just do the tamper bit and stop trying to boot into TWRP with a locked bootloader? It'll make your life that much easier. I said this before in another thread and I'll say it again

http://xdaforums.com/showpost.php?p=54675779&postcount=33 use that... it will solve your problem.
[ONE Q&A, Help & Troubleshooting] gunvald89:
Haha well all your help is much appreciated! Maybe a couple of hours sleep will do it. At least for me….

That would be wonderful. But I don’t know how that is supposed to be done. The commands I have seen with the tamper bit are adb-based and I’m stuck with fastboot. Even when I try use “fastboot boot recovery.img” to boot into recovery it doesn’t work
[ONE Q&A, Help & Troubleshooting] zephiK:
What happens when you fastboot boot recovery.img? Did you check the MD5 hash of the recovery file?
[ONE Q&A, Help & Troubleshooting] playya:
thats what he was trying to do and said he kept getting a boot loop afterwards
[ONE Q&A, Help & Troubleshooting] gunvald89:
The MD5 hasg was correct.

When i use fastboot boot recovery.img it just reboots. See this video:

http://youtu.be/SDQZq3xGn2o
[ONE Q&A, Help & Troubleshooting] zephiK:
Maybe he has a bad download of the recovery? Try CWR or TWRP 2.7.1.0 instead.

Video is private.

Here I'll add you on Skype. I'm bored anyways so I'll help you on Skype.
[ONE Q&A, Help & Troubleshooting] gunvald89:
I have tried the TWRP 2.7.1.0, same prioblem. Now the video is fixed
[ONE Q&A, Help & Troubleshooting] playya:
i am going to say something stupid here but when you send the command to your phone disconnect the usb cord. Just humor me - so that when it reboots its not plugged in
[ONE Q&A, Help & Troubleshooting] gunvald89:
It just reboots in to a boot loop
[ONE Q&A, Help & Troubleshooting] gunvald89:
Now I and zephiK talked over skype and tried a lot of different things. Nothings help.

We have tried different computers, usb-ports, usb-cables, drivers, tried to boot to TWRP and CWM, tried to boot stock kernel and checked all the MD5 sums of everything we downloaded.

The core of the problem is that I can’t start my phone. It is stuck in a boot loop. The bootloader is tampered but not unlocked. I can’t unlock it with commands (see video) and I can only boot into fastboot. I can’t boot into recovery. I can’t even temporary boot into recovery with “fastboot boot revocery.img” command. The phone just restarts and boot loop.

The phone does however responds to” fastboot oem device-info” and get listed as a connected phone. That’s about it.

We also tied to update the factory image cm-11.0-XNPH25R-bacon-signed-fastboot.zip without success.

Now, after this, has anyone an idea?
[ONE Q&A, Help & Troubleshooting] majesticpark:
Hi

did you manage to fix your phone? i'm stuck in the same position as you were. OPO only boots into fastboot mode. i cannot boot into recovery. fastboot boot recovery.img doesn't work - I get an 'Device not unlocked cannot boot' error.
[ONE Q&A, Help & Troubleshooting] Heisenberg:
What happens when you try to unlock your bootloader? On the more recent firmwares you can't boot a recovery unless your bootloader is unlocked.

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] penjejakbadai:
I solve this problem thru 'adb shell' command from my linux OS but if u still have adb conection.

This is what i do.

Press power+vol down --- phone bootloop at TWRP recovery or OnePlus Logo. Connect ur phone.

Check ur phone adb connection " sudo adb devices "

Than i copy recovery.img from 25R via adb push " sudo adb push recovery.img / "

Than ssh ur phone thru adb " sudo adb shell "

u must got this promp " # " = root shel of ur oneplus

run this command from this root shell #

#cd / *plz check ur recovery.img its should copied at this / (root) from adb push recovery.img

#dd if=recovery.img of=/dev/block/mmcblk0p17 bs=512

#reboot

Than enter fastboot mode check whether ur bootloader is lock or unlocked " fastboot oem device-info "

I got lucky is show unlock and i just proceed with flashing custom recovery with " fastboot flash recovery recovery.img "

Sorry for bad english . English is not my first language :)
[ONE Q&A, Help & Troubleshooting] gunvald89:
No I haven’t solved it yet. I’m trying together with OnePlus personnel to fix it but to be honest it looks dark.

The phone just restart without any change

Unfortunately I can’t run any adb command because I can’t boot it to recovery
[ONE Q&A, Help & Troubleshooting] majesticpark:
hi gunvald89

I managed to fix my phone. this is what worked for me finally. i had to use an XP machine.

http://xdaforums.com/showpost.php?p=55024864&postcount=136
[ONE Q&A, Help & Troubleshooting] gunvald89:
I have been looking in to that but it is hard to find a XP machine these days. Hopefully I can start that project tonight.
[ONE Q&A, Help & Troubleshooting] zephiK:
I'm surprised that you still haven't resolved it. Make a virtual machine with Windows xp on it and give it a try.
[ONE Q&A, Help & Troubleshooting] gunvald89:
I borrowed an old XP computer to try this out but I don’t get it to work.

I have installed the drivers from the provided iso file. No errors what I can understand. It froze like one sec on 95 %. Maybe that’s an indicator that something is wrong?

No Android phone has ever been connected to this computer so there shouldn’t be any old drivers to uninstall.

Here is where I run in to trouble. When I run msm8973 Download Tools Version 1.7 (Msm8974DownloadTool.exe) and all the lines looks the same. When I press Enum nothing happends.

In the device manager I can see that the phone is connected as “Android Phone” -- > “Android Bootloader Interface.” I have also tried with the ordinal USB-cable and a Samsung orginal cable. I also tested all the USB slots that computer have without success.
[ONE Q&A, Help & Troubleshooting] majesticpark:
Try this:

Put your phone in fastboot mode. Don't connect the phone to your computer yet. When in the fastboot mode, hold down power and volume up buttons simultaneously. The screen should go blank. Now connect the phone to your computer with an USB cable. In the command line window, type "fastboot devices" without the quotes. If you see a serial# then you are good to go. Run the Msm8974DownloadTool and enum now. You should see one line that's different.
[ONE Q&A, Help & Troubleshooting] gunvald89:
Thanks that helped!

Too bad it didn’t work.

The old XP computer ask for QHUSB_BULK driver. I installed Qualcomm HS USB QD loader 9008. Later on i also installed Qualcomm HS-USB Diagnostics 9006 when asked.

The line turned green and everything looked good. No error reported. Everything’s looks nice. The phone however behaves exactly the same. It boot loop. I only get to the red One Plus logo and then it restart. I can’t boot into adb but I can boot in to fastboot as before. The bootloader is still tampered but not unlocked. When I run fastboot oem unlock the phone just restart as before and starts the endless bootloop. I have tried this msm8974 tools twice and flashed my phone but with no luck.

When I try to press the big button at the top right corner it seems that I get same kind of error rapport. I get this:

974_msimage.mbn: OK

dynamic_nvbk.bin: OK

emmc_appsboot.mbn: OK

gpt_backup0.bin: OK

gpt_backup0_64G.bin: OK

gpt_main0.bin: OK

gpt_main0_64G.bin: OK

userdata.img: FAILED

userdata_64G.img: FAILED

rawprogram0.xml: OK

rawprogram0_64G.xml: OK

NON-HLOS.bin: OK

MPRG8974.mbn: OK

rpm.mbn: OK

sbl1.mbn: OK

sdi.mbn: OK

static_nvbk.bin: OK

tz.mbn: OK

boot.img: FAILED

cache.img: OK

persist.img: FAILED

recovery.img: FAILED

system.img: FAILED
[ONE Q&A, Help & Troubleshooting] majesticpark:
Are you installing the drivers from the ISO file mentioned in the instructions? At this stage all I can suggest is that you try flashing the color os rom 2-3 times. It might work.
[ONE Q&A, Help & Troubleshooting] Phoenix2000:
Hi gunvald89,

have you sorted out?

I'm in same situation as you are it seems.
[ONE Q&A, Help & Troubleshooting] Heisenberg:
Provide detailed and specific information about your situation.

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] Phoenix2000:
Hi,

my situation is the following.:

- Received phone on Monday 20 October.

- Box opened same day in evening.

- Phone started, configured Google account, installed apps.

- Then OTA was offered, accepted R38 upgrade. Done apparently successfully.

- Few minutes after R38 was updated, the phone froze suddenly

- Restart has been done by pressing Power button until it shuts down

- Pressing Power button to awake phone: stuck at Onplus logo. Does not bootloop! Just stuck.

- Tried to unlock using "fastboot oem unlock". This keeps on failing. Says unlock was ok, but device is still locked.

- "Fastboot oem device-info" show that the device was tampered (flag: true) but is still locked (flag: false)

- Tried the Qualcomm MSM tool to flash ColorOS, and got the same result as gunvald89.
[ONE Q&A, Help & Troubleshooting] sohohopeter:
Have the same problem. I cant fix the phone with the tool. The tool shows the phone but after starting the MSM tool the process breaked up at the first file. I have tried so many things. Today i will install XP on my computer to try it.

Regards
[ONE Q&A, Help & Troubleshooting] Phoenix2000:
Hi sohohopeter,

let us know if you could fix it.

I've tried with an XP in a virtualbox, and that did not work. Apparently the MSM tool was not even seeing my phone even i made sure to connect the USB device to the Virtualbox.
[ONE Q&A, Help & Troubleshooting] sohohopeter:
Hey,

yeah VirtualBox is not working for me too. The MSM Tool do not see any COM USB Ports. So i will try to fix the problem on a pc with XP. If this do not work i try it with Ubuntu. :D Never worked with that. If you could fix it please let me know. We have all the same problem.

regards
[ONE Q&A, Help & Troubleshooting] sohohopeter:
So i tried to install Windows XP and to make it work on it but still the same problem like on WIN 8. The Tool is breaking up on the first file and disconnect the phone.

But after my work yesterday i tried it at first on WIN 8 and the tool starts to copy the file. I do everything like everytime and the tool starts to flash the first files but on system.img it break up with a red line. The worest thing is that i dont understand what there is written. But i think when you let you phone for 24 hours you have a chance to flash it. Or maybe it was because i tried to connect the phone on a apple computer. I will try it today twice and i will tell you :)! Still hoping to get my OPO back.
[ONE Q&A, Help & Troubleshooting] Phoenix2000:
Thanks for the feedback sohohopeter.

I hope you can get your OPO back to life, and me too with your instructions. :)

I keep the fingers crossed.
[ONE Q&A, Help & Troubleshooting] hbkmog:
I have similar issue and I could run Msm tool but even after everything is flashed and shows green, the phone is still dead.

I can see the phone in fastboot and the boot loader is locked. Can't enter other modes.
[ONE Q&A, Help & Troubleshooting] Phoenix2000:
hi hbkmog,

how did your problem happen? are you also having your phone stuck on the Oneplus logo (with no bootloop)?

Tampered = true and unlocked = false when running "fastboot oem device-info"?
[ONE Q&A, Help & Troubleshooting] cyldman:
Hey guys, so I was trying to open up this apk on the phone and it started booting up again. My mistake because when it was booting up I long pressed the power button to turn it off while it was "booting" and now my phone is not booting up. I dont know why. I press the power on button and after a while it gives me a vibrate signal but nothing.

I cannot boot into TWRP too, and I have my phone rooted.

I have 30% battery. So i'm pretty sure its not that issue. Also I tried charging it up but no signal.

When charging to a PC. and pressing volume up + power It can't find QHSUSB_BULK controller. I also have a Nandroid backup.

I trying using this guide: https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/

However...After flashing ColorOS my phone still doesn't turn on. I'm out of ideas.
[ONE Q&A, Help & Troubleshooting] Heisenberg:
Read this thread:

http://xdaforums.com/showthread.php?t=2835696

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] cyldman:
K bro So I'll explain I've read all that.

I managed to find my device via Qualcomm driver.

I had to boot my windows 7 with f8 to accept all digital signatures else it wouldn't accept the drive.

Then I used the program Msm8974DownloadTool.exe to flash ColorOS. It shows me the phone, and I get no Red errors. The installation finishes. and bang, nothing.

I Click on the square in Msm8974DownloadTool to check for errors and I always have the same errors like boot. FAILED and image FAILED even though it installed it. So I really dont know what to do . Any help?
[ONE Q&A, Help & Troubleshooting] kevinf28:
I have posted some useful information here:

http://xdaforums.com/showpost.php?p=57177845&postcount=249

Further, your issue is due to Win8... fix here: http://xdaforums.com/showpost.php?p=57202390&postcount=257

Same boat. Please message me if you figure that out.

Im hoping to grab a copy of aboot partition from another OPO and flash it. The rawprogram0_64G.xml lists the file as 1024KB, but the emmc_apsboot.mbn is around 300K, and the unlocked bit is stored in 1023K as a 1... so the device is never unlocked by MSM tool.. I shall fix that!
[ONE Q&A, Help & Troubleshooting] gcampo703:
Hello, has anyone gotten anywhere with this? :)
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] happyhourtx:
i searched for the answer to this and couldnt find it, hopefully someone can help me out here.

on my home screen, there is no GMAIL widget. i actually cant find gmail any where on my tablet.

i have to goto the actual gmail.com so im missing out on emails unless i constantly check it.

anyone else having this issue?

thanks in advnace.

im using the tmobile samsung galaxy note 10.1 (2014 edition)
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] Bosbouer:
In the app drawer, tap the Google icon(not google+), it has among others, the Gmail app's shortcut.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] happyhourtx:
thanks BOSBOUER!!

i was going crazy!!