yashsingh1/xdaforums huggingface dataset:
[ONE General] EddyOS:
There was no purpose to the reboot, just that Nexus devices and all updates with the OPO until now had the reboot in their scripts. They're not necessarily required, it was just good practise.

If they're not needed then by all means remove them from the script and use them, or flash every entry one at a time without the reboot but, as always, I'm not responsible for anything that happens to your device
[ONE General] chrismalla:
So why can't you remove those "reboot"-lines and re-upload the files? Where in the OP does is say that you are not responsible for anything? Is it really that hard to show just a little bit of respect and understanding to the people who come and visit this thread by adding an explanatory warning?
[ONE General] EddyOS:
Unless anything comes from CM/OPO, everything on here is the responsibility of the end user and risk is implied (look at ROM threads - they all say do it at your own risk. I didn't put this as I really didn't think it was required - we're all smart cookies here aren't we? ;) ). If I have the time I'll edit the latest files but I'm not going to change every image.
[ONE General] Spannaa:
I'd leave the official cyngn cm-12.0-YNG1TAS17L-bacon-signed-factory_reset.zip well alone for now.

It should just work but for some reason, it doesn't...
[ONE General] nirmalkurienmathews:
Useful post. This helped me to restore my friends phone. Please update this guide whenever needed.
[ONE General] mirosaw2:
finally managed to fix the IMEI problem ..

by following this guide .. http://xdaforums.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 ..

now i have a totally functional phone .. :)

thx for helping guys.
[ONE General] Spannaa:
Yep, that one's fine - it's the one that was released OTA
[ONE General] vijendrahs:
Hi, You can include the below mentioned URL and instructions in OP. (You can modify to make it work in Linux as well with shell)

There is an official scripts to revert back to CM11S without any issues.

After downloading the zip, extract it and follow the README!!!!!!!.pdf and proceed (only for windows).

https://s3.amazonaws.com/oneplussupport/ONEPLUS ONE-FIX-Windows.zip

Note: Make sure you backup all your phone data to computer before doing this, since this will wipe everything including storage.
[ONE General] vicky2131:
Brother, ive been using your method since start to clean flash my oneplus. But this last release bricked my phone and i had to unbrick it.

Please do look forward on whats the issue.

thank you.

PS: i was on cm11s with franco kernel before flashing this factory image.

edit: just saw that official page is updated today with fastboot file ---> https://cyngn.com/support

can make a bat file from it mate?
[ONE General] EddyOS:
Downloaded, let me have a look ;)
[ONE General] hughfollett:
That was a known problem tho. I even wrote a post some pages back. Reading would have saved you some time?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE General] vicky2131:
Ha ha, yes!! my mistake

thanks mate ;)
[ONE General] hughfollett:
No problem☺

Inviato dal mio A0001 utilizzando Tapatalk
[ONE General] stryker09:
Quick question - because I don't see userdata_64G in the https://cyngn.com/support zip file. I dont think its still okay to flash this in TWRP?
[ONE General] Spannaa:
You don't flash fastboot zips via TWRP.

Sent via Bacon...
[ONE General] aditya2603d:
Batch file

Can you just upload the batch file flash-all.bat because I already downloaded the fastboot zip from cyngn website.
[ONE General] waterdaan:
Select ' new ' in ESFile Explorer

Name your new file flash-all.bat

Open this file as text

Type the desired fastboot commands and save

Use it to flash, if it works,

Upload it to this thread and make someone happy :)
[ONE General] chaimc:
Would this help to revert from multirom?
[ONE General] mjprashanth:
Works like a charm

Thank you so much!! Unfortunately, I typed a wrong password multiple times and it led to my device getting wiped out completely. The TWRP recovery screen as well was blinking continuously and I thought the system was dead in the water. I used the same method as you have mentioned and go to CM11S - 44S. Then I again went to Vanir Exodus. with the usual method..
[ONE General] Framzo:
Hello. Iv'e tried to follow this guide. My OPO used to be in 38R with fraco kernel and TWRP I completely unable to update (error with OTA), i have hence decided to do this to finally be able to get my OPO on CM12.

I installed ADB, checked that my bootloader was unlocked and everything was ok on that point.

I then proceeded to use the script, at one point in the script it stopped and was on a <waiting for device> I tought it was just slow this time but after 30 minute i decided to interrupt the script to restrat it all over again.

Since then Misery ! My OPO don't even boot in fastboot, it doesn't even rumble when I press power, i'm currently quite panicked and have no idea what to do and i don't even have a backup phone (yeah that is not really clever of me) so I'm posting here to seek advice on what i should do to be able to boot it at least in fastboot to flash it again using this. i'm afraid that iv'e completely lost my opo...
[ONE General] Spannaa:
It probably happened because of the "fastboot reboot-bootloader" lines in the flash-all.bat & flash-all.sh files

You should be able to use the OnePlusRecovery Tool to get your OPO up and running again.
[ONE General] Framzo:
Thanks alot Mate It worked like a charm. I'm now in 44S I'm gonna try to OTA up to Android 5.

Also if i must use this script, what should I change to avoid this kind of issue ?
[ONE General] Spannaa:
Glad you're sorted Mate :good:

I'd advise NOT using a script to fastboot flash files - do it manually.

There's a great guide by [MENTION=4153349]Heisenberg[/MENTION] here that covers everything you need to know ;)
[ONE General] vicky2131:
[MENTION=2258271]EddyOS[/MENTION]

hello mate!! any eta for the latest cos 12 file(current cos12 file gets into hard brick) ? or has it been modified and reuploaded?
[ONE General] Spannaa:
It hasn't but, instead of asking for an ETA, why not just read the guide I linked to in the post above yours and do it manually.

Sent via Bacon...
[ONE General] vicky2131:
yes saw that,but its not been updated for latest cos12 fastboot pack. I guess one or two files from that has been changed in lastest zip(COS12 - YNG1TAS17L)
[ONE General] Spannaa:
The steps and the file names in the guide are exactly the same for YNG1TAS17L - just download it from here and follow the guide exactly.
[ONE General] stormjenkins:
3. Flash the factory image

Once you've unlocked the bootloader, and rebooted the phone, turn the phone off and back on into fastboot mode and reconnect it to the PC. You can now run the flash-all.bat (Windows) or flash-all.sh (Linux) file. These automate the flashing process. Once complete, the phone will reboot.

*** Some users have had issues using the script in Linux so in these cases extract the ZIP file and flash each IMG individually ***

***YOU WILL BRICK YOUR PHONE IF YOU USE THE "FLASH-ALL.BAT" FOR COS12, YOU MUST MANUALLY FLASH EACH FILE***

EddyOS, Please be the Recognized Contributor that you are and update the OP accordingly, highlighted in red above, or something similar.

Thanks
[ONE General] Signor Rossi:
Aww Brilliant.... I just did that, now what ? RMA ?
[ONE General] stormjenkins:
Not yet. The way I solved this issue was to plug in my OP to a wall charger for about an hour, then try reconnecting it to my PC. Then it recognized my phone again. Before that, I had no screen, vibration, nothing, but the plug in helped. I the followed guide the guide below and was successful in getting my phone back. I hope this helps you too.

http://xdaforums.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
[ONE General] hughfollett:
If you read the last pages, I have already explained when this is safe to use. Are you on CM12.1/CM12.1 based roms with up to date firmware? You can flash this with the .bat file. Are you on CM11(S)/KitKat rom? You need to flash everything manually without rebooting.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE General] Spannaa:
You should be able to use the OnePlusRecovery Tool to get your OPO up and running again.

Sent via Bacon...
[ONE General] Signor Rossi:
Thanks I'll try this now. Sounds Promissing as my Phone is curretnly in the state as you described. It does not reacat to any button action. Charging now and will test in one hour. Thanks

I was on no OS as I wiped DATA/SYSTEM Partition. Before that I was on CM12s
[ONE General] hughfollett:
That wasn't necessary, as factory images wipe everything, even system. Seems strange tho, maybe something else went wrong

Inviato dal mio A0001 utilizzando Tapatalk
[ONE General] Signor Rossi:
I'm on color OS now... so it's back. Nice Guide ! Thanks.

My Phone did not vibrate at all, so it was hard to understand it, but it worked so I'm happy again :)
[ONE General] LiquidSolstice:
So, through two friends in the past two days who have used this guide, I have learned something EXTREMELY important. Do NOT reboot immediately after each step (fastboot reboot-bootloader). Do it at the end. Twice now, after flashing the rpm and rebooting, they brick their phones.

If you brick your phone (black screen, doesn't seem to turn on, no lights, no vibrate), do NOT PANIC. You do NOT need to send it back to OPO. All you need is a Windows PC and a couple minutes of time. It is extremeley easy and straight forward to unbrick it and go back to a state where you can repeat the process in this thread. http://xdaforums.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

OP, you really, really should consider removing all the "fastboot reboot-bootloader" steps. Until all images are flashed, you really shouldn't reboot the bootloader at all.
[ONE General] AspenSTi:
I tried to use this method two different times yesterday to go back to full stock and hard bricked both times. Thanks to your link i was able to recover both times and now am wondering really how to go back to full stock CM (not colorOS). Today ill try with an older factory image not the cm12 version.
[ONE General] waterdaan:
Thanks for this thread [MENTION=2258271]EddyOS[/MENTION] but

However

This is not idiot proof and requires too much concentrated reading

Please

Copy and paste this or something similar
[ONE General] chitrannamt:
I messed it up!!

I need help- I messed it up- I flashed my OPO without unlocking bootloader. Now its sitting at boot screen and nothing is happening!! I could boot the device only in fast boot mode and nothing happens if I flash it!! Looks like boot loader is locked and device is not showing up in adb devices! Please suggest:confused:

---------- Post added at 05:07 PM ---------- Previous post was at 04:41 PM ----------

I am in trouble- I really don't want to lose this phone. It's been 3 months since I bought this phone and got it updated to Lolipop which was a pain. I decided to downgrade it and flashed my OPO without unlocking bootloader(forgot to unlock it). Now its sitting at boot screen and nothing is happening!! I could boot the device only in fast boot mode and nothing happens if I flash it again!! No recovery options and device is not showing up in adb device list! Please suggest how to fix it. Do I take it to service center? Does it help? I really really want this phone back online...:(
[ONE General] androizers:
See bro, adb is only possible when ur device is working alright. Since it's not switching on, it won't show ur device in adb devices.

Now the thing is u want to get it back on to stock, so u must have to unlock the bootloader in order to downgrade the device or even if u want to upgrade in future. So first unlock the bootloader of device, flash the required files and then boot it. There is no need to worry bout the device no booting since device is fully locked and nothing can make changes to system. So don't panic and keep the process steady.

Report back if its successful or not. Will try to help more.

If u're not enough confident, take it to service centre. But they sucks in my opinion.
[ONE General] gianton:
+1 I just did the same but luckily I unbricked my device using @ netbuzz guide. No I clean flashed with fastboot commands all at once and booting the CM12S.
[ONE General] westenlive:
after this step

fastboot flash rpm rpm.mbn

fastboot reboot-bootloader

my opo is dead....

HELP ME PLEASE
[ONE General] gianton:
Follow the guide I posted the link just one post above yours. Next time you flash the stock images, skip the "fastboot reboot bootloader" command in between.
[ONE General] westenlive:
ok.

All is done.

Now my windows in in test mode, i want change this mode.

thank you very much
[ONE General] danielsinnema:
Do what in the end? "Fastboot reboot-bootloader" or "Fastboot reboot" ?

Is that step really necessary?

I'm sorry for being dumb in this matter, I just want to make sure I do it right. (I'm pretty scared after having read all those brick stories.)
[ONE General] gianton:
Just "fastboot reboot" is needed after you finished flashing all files.

BTW, I've edited the "flash.bat" file from the CM12S factory image and removed all "fastboot reboot-bootloader" commands and flashed fine automatically.
[ONE General] Spannaa:
Don't fastboot reboot-bootloader between each step and, when you've flashed all of the files, fastboot reboot.

Sent via Bacon...
[ONE General] danielsinnema:
OK thanks a lot.

Did you remove "ping -n 5 127.0.0.1 >nul" as well from the .bat file?
[ONE General] gianton:
No I left them untouched.
[ONE General] LiquidSolstice:
Do not use "fastboot reboot-bootloader" at the end of each step. That's what's bricking people. Only use fastboot reboot at the very, very end of flashing all the partitions.
[ONE General] LiquidSolstice:
The OP seems to be totally unresponsive, so if you're reading this, again:

DO NOT RUN 'FASTBOOT REBOOT-BOOTLOADER' AFTER EVERY SINGLE STEP. YOU WILL BRICK RIGHT AFTER FLASHING RPM IF YOU DO.

Flash all images in one go (ignore the reboot-bootloader steps) and ONLY when you have finished flashing them all, use fastboot reboot, and you will boot back into the stock ROM and you will be JUST FINE.

I have reported the OP's post in hopes of getting it edited so no one else bricks their phone.
[ONE General] orangekid:
@EddyOS

I edited the OP - removing every line that says the reboot bootloader before every flash.

I actually did this about 2 weeks ago, and I did everything in the OP except the reboot bootloader part, because it seemed pointless, and now I am glad I skipped it. Can you please look at this and fix your OP accordingly? There seems to be a real issue and so that .bat files needs to be looked at too I am sure, thanks.
[ONE General] danielsinnema:
So after having asked some questions about how I could safely flash stock rom to OnePlus One, I went for it.

Unluckily, it didn't go as smooth as I had hoped for. There was 1 command which failed. It failed to erase userdata... I'm not exactly sure what it does.. Anyway, I continued to enter the next commands in line and those worked fine. Then I rebooted using "fastboot reboot". Then I thought I got a bootloop. The device booted like 3 times.. (Maybe this is normal after having flashed a ROM.. idk..). Luckily, After that stressful moment, the device booted up. I think it worked because I came from Stock 5.0.2 and I flashed stock 5.0.2.. It works on the old userdata I think.... idk I don't get it fully. But I think I would have had bigger problems if I came from CM 12.1 or whatsoever, wouldn't I? Anyway, my question is. Would a command failure like this indicate future problems? Will I have a bricked phone if the command fails to erase/flash userdata when coming from a ROM other than Stock ROM? And what does this "Userdata" command do? What exactly is meant by "userdata". Is it like all the files downloaded/extracted ever to the phone? I'm sorry for being a noob on this. I regularly flash my Nexus 7 2013 without any problems (without any failures), but on my OPO I've had several problems already.

This is the failure I had..
[ONE General] LiquidSolstice:
Userdata is just the data partition of the phone. You actually don't need to necessarily flash it to be able to boot up, it's just another way of formatting the partition. Were you encrypted before? Did you have a password lock on your device? That might do it. Also, there is no "5.0.2: userdata. Userdata imgs aren't dependent on the Android version.

Don't worry too much about it. Of all the partition images, userdata and cache are the least important ones to flash. If you really want clean internal storage, just wipe it from TWRP or format from within Android.
[ONE General] danielsinnema:
OK thanks a lot for all the answers.

Now I'm facing a new problem. I can't install TWRP after having flashed stock 5.0.2... I have disabled "cm recovery update" in developer settings already and I flashed TWRP recovery multiple times.. However, when I enter recovery, it will show me the old cyanogen os... Now I'm thinking about flashing kitkat to be able to install TWRP. And then I'll install lollipop via "TWRPable" OTAs. Is anyone else having problems installing TWRP after having flashed stock 5.0.2? And for me, the .bat files have always worked for me on kitkat. The difference is that I now have installed stock 5.0.2 once via fastboot. Is it still safe to flash kitkat using these .bat files from Kitkat images?

EDIT:

Solved.

I flashed custom recovery via fastboot, then I rebooted the device using fastboot.

I didn't let the device boot, I held the power button for 9 seconds, so it would turn off. Then I entered TWRP via power button + volume down. On kitkat, i wouldn't have to hold the power button for 9 seconds. I could just let it boot and enter TWRP recovery via the "software" way.
[ONE General] Felix_928:
hey guys,

just tried to get my opo back to stock. The script suddendly stopped at flash rpm and failed reboot my phone. No nothing is working with, it doesn't even start in fastboot. Did I brick it? What should I do?
[ONE General] gianton:
Read this and the previous page and you'll find the answer.
[ONE General] itechy:
hightail links work but the downloads aren't :/
[ONE General] LiquidSolstice:
Sorry, I didn't see this before. The correct method of flashing recovery is the way you did it. We have Nexus-like devices that can be bootloader unlocked. If you can fastboot flash unsigned images, you can always flash TWRP. Glad you got there in the end!
[ONE General] Thunderbolt:
Can I back to cm11s without Fastboot? Just flash zip by twrp? I have lost my faith in this path after a few hours.. I have a problem with black screen While phone calls. Im trying to flash radios etc.. And issue still exist.
[ONE General] lodevs:
Dear,

I hope you guys can help me. I got a big problem. My opo had a stock CM11 running...just out of the box.

So i unlocked the bootloader, flashed TWRP recovery and afterwards flashed CM 12.1 nightly release but forgot to flash my gapps.

Because of that i tried to restore it back to CM11 (like it's out of the box)

But the problem for now is that my phone isn't recognized anymore by my computer. Not even when i'm put him in fastboot mode and try to use by cmd the fastboot tool with command "fastboot devices" it's not recognized annymore :( so i can't restore him to stock...

what do i need to do
[ONE General] erad1:
Search for Bacon Root Tool kit and let it install the drivers and see if it recognize your device while in fastboot. Good luck.
[ONE General] mabmed:
Hi. I try flash manualy; and all is ok untill the command fastboot flash system system.img, it stuck at writing system more than 20 minutes!! Any solution please!!
[ONE General] maksud_ans:
upload please YNG1TAS17L 64GB flash-all.bat file
[ONE General] Nexus5-32GB:
It doesnt work:
[ONE General] orangekid:
Don't use the batch file, do it manually
[ONE General] counterfeit187:
I really wish you would have changed the instructions in the OP, to COMPLETELY REMOVE ANYTHING SAYING TO FLASH-ALL. So, is this brick unfixable?

---------- Post added at 04:58 PM ---------- Previous post was at 04:55 PM ----------

This is no longer true on latest 12.1 nightlies. BRICKED with flash-all.bat
[ONE General] LiquidSolstice:
Don't panic. You're going to be just fine. Take a deep breath, and follow this guide: http://xdaforums.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

Keep your phone plugged in while you prepare for this. You'll want it to have some charge for the unbricking process.
[ONE General] counterfeit187:
I read through the last few pages of this thread and got it back up and running. Took a few hours to get the drivers right but after that the recovery tool did the trick.
[ONE General] elijahonli:
Can the mods please ban this guy or remove this thread? There is no where in his original first post that he stated dont use the flash-all zip... now my device is bricked and unable to even be detected by my computer :crying::mad:
[ONE General] LiquidSolstice:
Your phone is fine. Even though you think it's off, and it doesn't vibrate, and no LEDs light up, it's just waiting for the right type of program.

Use this guide: http://xdaforums.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
[ONE General] mrruin:
My OPO does not show up at all upoon connection to my PC. No Unknown device, no Qualcom device, simply nothing. I do not even get to the part with installing drivers...
[ONE General] LiquidSolstice:
Charge your phone for a few hours and then try the guide again. It will work.
[ONE General] gauravsaini964:
I am on CM12.1 Build by Sultanxda. I want to revert to COS12 build so I can update to latest system they have released today.Please tell me what steps to follow. Do I have to flash all image manually ? If so , is there any more command other than stated in OP ? And is this mirror file valid/correct "https://www.androidfilehost.com/?fid=96042739161892230" ?

Thanks
[ONE General] Siphter:
If you use notpad++ or similar to remove the reboot commands between each flash in the flash-all.bat file you can still use the flash-all
[ONE General] yairyd:
i do the guide instrucations and its say

witaing for devices for a long time after the installioton

so i unplug the opo and now he didnt turn on:crying::crying:

what can i do?
[ONE General] alexktz:
Bricked my phone by running flash-all.sh from OSX. The OP MUST be modified, this is ridiculous.
[ONE General] imbonfi:
OMG, u have saved my life(OPO) *___*
[ONE General] antmunny:
so after we delete "fastboot reboot-bootloader" commands, no space between the previous command and "ping"?
[ONE General] Spannaa:
Just:

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

then if you have the 64GB model

fastboot flash userdata userdata_64G.img

or if you have the 16GB model

fastboot flash userdata userdata.img

then

fastboot reboot
[ONE General] harisled:
Same here.
[ONE General] cdkg:
Can we get an alternate/mirror download for YNG1TAS17L?
[ONE General] Spannaa:
Try here ?

Sent via Bacon...
[ONE General] aditya2603d:
Can't flash userdata_64G.img

I downloaded the fastboot image from cyngn official website but when executing all the code the commmand fastboot flash userdata userdata_64G.img it returns error cannot load userdata_64G.img. Please help
[ONE General] Spannaa:
That'll be because the official fastboot zip from Cyanogen doesn't contain userdata_64G.img

Try the one from the mirror I linked to in the post above yours.
[ONE General] aditya2603d:
What if I run command fastboot flash userdata userdata.img which is provided in the official fastboot zip file from cyngn website
[ONE General] Spannaa:
I wouldn't - it could mess up your data partition.

Either use userdata_64G.img or leave it out completely and do a factory reset once you've booted your device.
[ONE General] andybfmv96:
yeah i have no idea how to use a .sh script, anyone wanna give me a crash course?