yashsingh1/xdaforums huggingface dataset:
[ONE General] POCKATA:
Hollo,

I want to perform step 8 from the guider so that I can restore from a factory image. However I have a few questions before I proceed with the instructions:

1. Will I be able to flash the 12S factory image if I am currently on OxygenOS?

2. Do I need to use the factory image from the link in the instructions ( http://builds.cyngn.com/cyanogen-os.../cm-12.0-YNG1TAS0YL-bacon-signed-fastboot.zip )?I am asking this because I saw 3 variants of the factory image: untouched version ; version with added Userdata_64G.img ; and a Debuggable version with unsecure boot.img. I apologize for my ignorance, but what are the difference between the 3 versions and does it matter which I install?

3. Do I need to wait for the tutorial to be updated, or would the current instructions work in my case?

My configuration is a follows:

1. USB drivers are installed on my PC

2. ADB and fastboot prompts are working

3. Latest version of TWRP is installed (however i would not need it in my case)

4.. The phone is not rooted (if that matters at all)

5. The phone is currently running OxigenOS (if that matters at all)
[ONE General] Amro90:
It seems that this Cyanogen OS 12 stock fastboot image does not include userdata_64G.img and flashing the userdata.img only gives you the 16GB partition.
[ONE General] Spannaa:
This one does ;)

Since the userdata.img in the OS12 fastboot zip is EXACTLY the same as the one in the 05Q fastboot zip, I just added the userdata_64G.img too.
[ONE General] Amro90:
Yup, ended up doing the same thing. :good:

Current instructions work just fine, but if you have a 64GB device you need to use an image that has the userdata_64G.img included. The one posted above this post should work perdectly fine. Piece of advice: do NOT reboot the device in between flashing the images or you might end up hard bricking your device and then you'd have to unbrick it with ColorOS. OxygenOS has a different bootloader AFAIK.
[ONE General] illanxr:
Be careful with latest CM12S fastboot images: I am unable to flash TWRP recovery after flashing the factory image. Had to return back to 11S to flash it. Tried everything, but nothing worked
[ONE General] Spannaa:
Strange - I had no problem.

Which OS12 fastboot zip did you use?

Did you flash the zip or fastboot flash it's contents individually?

Sent via Bacon...
[ONE General] Heisenberg:
Instead of rebooting the phone normally, you need to use the power + volume down button combination to boot into TWRP directly after flashing it. After doing this once you can boot into TWRP the normal way, using the advanced reboot menu.

Transmitted via Bacon
[ONE General] illanxr:
That's strange. I flashed all the contents from the attached zip (I have a .bat file to do that). After that, I typed adb reboot recovery, and I only got CyanogenMod Recovery, not TWRP. Have no problems flashing TWRP, though (2.8.6.0).

Will try again when official images are available at https://cyngn.com/support. Meanwhile, I am very happy using CM12.1 :)
[ONE General] Heisenberg:
As I said, try the button combination.

Transmitted via Bacon
[ONE General] Spannaa:
If you flashed all of the fastboot zip's contents then TWRP would have been overwritten by CM recovery(.img)

Sent via Bacon...
[ONE General] Reptilez_DK:
NVM - Reading/understanding is hard. ;)

Is the option to "update cyanogen recovery" disabled ? :)

Just my first thought.
[ONE General] illanxr:
Okay guys. Thank you for your support. This was a really weird thing, and it just... disappeared. This were my steps:

I've got a 64 GB mode. When I want to go back to stock, I just connect my OPO to the PC and turn on ADB debugging. Then, inside a folder in which I've got unzipped the factory flashable image, the TWRP recovery image (renamed as twrp2860.img) , adb.exe (with its .dll's) and fastboot.exe, I have a .bat file (edited with Notepad++) in which I have typed:

@echo off
adb reboot bootloader
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64G.img
fastboot reboot
exit

That always work. But then, I have another .bat file (in case I want to have TWRP recovery):

@echo off
adb reboot bootloader
fastboot flash recovery twrp2860.img
fastboot reboot
exit

That ALWAYS had worked for me... until yesterday. I mean: everything seemed okay, but when I tried to reboot into recovery, I got the Cyanogen recovery, instead of TWRP. I had unticked the 'Updated Cyanogen Recovery' option. I tried it several times, but it didn't work. Just normal Cyanogen recovery.

Today, I redownloaded the factory image and... it worked :eek:. It seems everything was a bad download.

Anyway: if anyone wants to use this little code, all credits go to [MENTION=4153349]timmaaa[/MENTION] . I just created a .bat file (open Notedpad++ or simply Notedpad, paste the code and save it as .bat).
[ONE General] jbejaranogarcia:
thanks man, it was driving me crazy!!! done, working twrp finally!!! :eek::D;)
[ONE General] MrAman007:
I want to know how to use fastboot because I want to flash stock logo.bin so plz give me the full procedure steps to do it :):)
[ONE General] Heisenberg:
Have you actually read the guide? It's all there in plain sight.

Transmitted via Bacon
[ONE General] MrAman007:
Oopps.. Sorry I forget to watch 1st page:p:p:p
[ONE General] 3's&7's:
Thanks for the note on this. Just returned to the OnePlus and this was super helpful! :good:
[ONE General] jeeeorb:
8. How To Flash....

Hello,

I was trying to follow along, but I totally missed this step:

fastboot flash aboot emmc_appsboot.mbn

When rebooted, it vibrated, but the screen does not come on. Not sure.... what to do at this point. Any suggestions?

:(
[ONE General] :
Please don't ask same question in multiple threads....it is just confusing for everyone, especially yourself.

You asked this here, http://xdaforums.com/showpost.php?p=60490825&postcount=2501

Thanks,

Darth

Forum Moderator
[ONE General] Spannaa:
Hey [MENTION=4153349]timmaaa[/MENTION], just spotted you're now a mod.

Congratulations - I'm sure that with your cool, calm temperament, you'll be awesome :good:
[ONE General] Heisenberg:
Yes sir, I've only just been inducted into the moderator ranks but I'm looking forward to my new position. Thanks for your kind words.

Transmitted via Bacon
[ONE General] nicolahaye:
Just wanna say thx for your guide, everything worked flawlessly :) and congrats on becoming a mod ;)
[ONE General] Heisenberg:
Thanks mate, appreciate it. Hope you're enjoying your new toy.

Transmitted via Bacon
[ONE General] 1337SereniTyx3:
Just visited Cyngn and saw that the factory image is now officially available. But it doesn't say fastboot in the name.

How is one supposed to flash it?
[ONE General] Heisenberg:
If you want the fastboot images go here:

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

XDA Moderator

Transmitted via Bacon
[ONE General] Spannaa:
cm-12.0-YNG1TAS17L-bacon-signed-factory_reset.zip on the Cyanogen support page is a recovery flashable zip that includes the stock recovery and wipes userdata.
[ONE General] allesmeglische:
Can i Flash the Zip with TWRP, or must i have the Stock Recovery?

Getippt mit nem OnePlus
[ONE General] Heisenberg:
TWRP is fine.

XDA Moderator

Transmitted via Bacon
[ONE General] karluag:
cm-12.0-YNG1TAS17L-bacon-signed-factory_reset.zip

How is one supposed to flash it?

with TWRP Recovery?
[ONE General] coldzage:
Hello,

Newbie here, though I know the basics of how to use adb/fastboot/bootloader/recovery/flash....

...still I also thought this factory image would be like a clean slate while installing the OS.

I tried both with cyanogen recovery to wipe everything, apply update (pointing to the cos 12 zip file), and, after installing TWRP, using this one to go to wipe everything, go to install and point to the zip, but, the end result does not change, it simply installs cyanogen stock recovery, no OS is installed. At least... it keeps booting into cyanogen recovery afterwards, be it be slecting reboot into system or simply turning on the phone.

So, is it no supposed to install os?

What, how to do it?

Regards
[ONE General] Heisenberg:
The answer to your question is within the post you quoted.

XDA Moderator

Transmitted via Bacon
[ONE General] phochiom:
Exactly the same thing with me. I was booting back to stock CM recovery whatever I tried. I could not install the above mentioned zip. In the end reverted to my nandroid backup after powering down from CM recovery and then powering on to my modified TWRP by holding power and volume button combination.
[ONE General] margosa:
I forgot to put *.zip files in the sd and I unlocked the bootloader. Now I are not able to copy files. Anyone show me how to put those ROM files in my phone? Thank you.
[ONE General] ramongallud:
I have one question, when you say dowload the full Android SDK, you mean where it says "Download Android Studio" at the top of the page or where it says "SDK Tools Only", at the bottom?

Thanks!
[ONE General] Spannaa:
SDK tools only unless you intend to use Android Studio for development.
[ONE General] ramongallud:
And what do you recommend me, the .zip file or the .exe installer? I tried the .zip but i can't figure out how to install it

Thanks a lot for the quick reply!
[ONE General] Spannaa:
Use the (recommended) installer_r24.2-windows.exe
[ONE General] ramongallud:
So I install that AND the universal adb/fastboot drivers

And thats all I need to have installed to unlok, root, etc, am I right?

Thanks a lot! Im a total noob on android :silly:
[ONE General] Heisenberg:
Yes that's right. The SDK gives you adb & fastboot, and the drivers allow it to communicate with your phone via the usb cable.

XDA Moderator

Transmitted via Bacon
[ONE General] jerbhabes:
just bought the phone in china and the it has Color OS installed. I follow the tutorial how to unlocked the bootloader and flash TWRP successfully ( did not root ). My question is do I need to flash firmware for the phone first before I proceed flashing the CM12 or just follow the the tutorial here 8. How To Flash The YNG1TAS17L (CM12S) Fastboot Images.. Thank you for this tutorial it really helps for a beginner like me...
[ONE General] Heisenberg:
You can go ahead and just flash the stock images, they contain all the firmware components.

XDA Moderator

Transmitted via Bacon
[ONE General] jerbhabes:
oh thanks for your reply. I will get back once I have done..:):):)
[ONE General] HEZAiKU:
"fastboot flash oppostanvbk static_nvbk.bin" this is not working with my device because after done reflashing latest cm12s using this method, i got connection error or can't get connection to a server when i want to sign in Google and Cynogen. So i reflashing again without this command code and it's working. When i see the "oppo" name on this command code is it really necessary to flash it?
[ONE General] ramongallud:
I followed all the intructions but, when I went to do the Nandroid Backup With TWRP Recovery, it doesent boot into the TWRP, it boot into the Cyanogen recovery

Any ideas? :rolleyes:

Edit: Fixed it: I booted into fastboot again, flashed again the TWRP Recovery and rebooted into recovery mode directly from fastboot mode (long pres volume down + power while in the fastboot screen)

It booted into TWRP and everything went fine.

TWRP even gave me the option to download SuperSU directly from the recovery.

Thanks a lot for the guide and all the help!
[ONE General] jerbhabes:
cm12s successfully done using no.8 instruction but there are problems about my connections. Wifi and mobile network have exclamation mark beside the signal icons. Any ideas what are these? btw. I'm living in China. Are there possible ways to fix these? Please guide me.. Thank You.
[ONE General] Heisenberg:
Go into About Phone and tell me if you can see your IMEI and your baseband version.
[ONE General] jerbhabes:
I see the IMEI number. baseband version : DI.3.0c6-00230-m8974aaaaaanazm-1.
[ONE General] Heisenberg:
Ok that's good. Did you flash all of the files from the zip?
[ONE General] jerbhabes:
yes I flash all the files. I tried to wipe again in CM recovery and all are ok but when i restarted the phone ( reboot or power on / off ) the problem exist again.
[ONE General] Heisenberg:
Try flashing this:

https://www.androidfilehost.com/?fid=23991606952597817

Or this:

https://www.androidfilehost.com/?fid=23991606952602297
[ONE General] jerbhabes:
How do I flash these via TWRP? ( i didn't flash the TWRP after flashing the CM12s ) so right way is flash TWRP and flash this? about the bootloader, do you think i still need to unlocked it before flashing TWRP? Thank you very much for helping me.
[ONE General] Heisenberg:
Your bootloader is still unlocked unless you deliberately locked it again. So just flash TWRP and then flash the firmware file via the install menu in TWRP.
[ONE General] WislaHD:
Guys I need help badly, I hope I can get a timely response.

I just got my OPO a few days ago and I wanted to upgrade the CM12s Nightlys and to unlock bootloader, install custom recovery and root the phone, and I was following the instructions here[1]. I got to the process of installing the custom recovery by flashing as per the instructions and received an error trying to flash it, rebooted the phone, then turned the phone off to attempt to install the custom recovery again.

Except this time, the phone will not turn on. Neither Fast Reboot and Hard Reboot will work. Did I just hard-brick the phone? What can I do now?

[1] - xda forum won't allow me to post links. Delete the space after oneplus:

forums.oneplus .net/threads/guide-oneplus-one-how-to-unlock-bootloader-install-custom-recovery-and-root.64487
[ONE General] Heisenberg:
Exactly what recovery did you flash? What's the full filename? And what specific error did you get?
[ONE General] WislaHD:
It just said that the 'Flash Failed' on command prompt, I didn't think to take screenshots at the time unfortunately as this was before I realized my phone was bricked.

I used the TWRP recovery mentioned in the guide, renamed to recovery.inc.md5. I believe the reason it failed was because of this reason below:

http://forums.oneplus.net/threads/g...ecovery-and-root.64487/page-116#post-11176890

After rebooting, I turned my phone off as I intended to repeat the flashing except this time with the above instructions. That's when I realize the phone as bricked.

I found this guide on the forums for unbricking the OnePlus One, should I follow them for now?

http://xdaforums.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
[ONE General] Heisenberg:
Can you show me where it says to rename the file to recovery.inc.md5? I can't believe any reputable guide would say that, it's ridiculous. Anyway, yes you should go to the unbrick thread by netbuzz and attempt that, it's probably your only hope.
[ONE General] WislaHD:
It says so here, scrolling down to Step 2.

forums.oneplus .net/threads/guide-oneplus-one-how-to-unlock-bootloader-install-custom-recovery-and-root.64487/#post-3016164

"Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img* Remember that this file should be placed in the platform-tools folder inside of the android-sdk-windows folder on your desktop."

Seemed ridiculous to me too but this is my first time attempting to unlock/root/flash a phone so what do I know?

Hopefully netbuzz's instructions work. I'll report back when they are completed.
[ONE General] Heisenberg:
Ok, but those instructions say to rename it to recovery.img, which makes sense. You said you renamed it to recovery.inc.md5 though.

XDA Moderator

Transmitted via Bacon
[ONE General] WislaHD:
To be clear, the .md5 was the file extension. Sorry for any confusion.

edit: Now I just remembered what it is I have done that might have accidentally hard-bricked my OPO. When the flash failed the first time, I then flashed it again except writing "recovery.imc.md5" in the Command Prompt. That might have been what bricked my phone.
[ONE General] Heisenberg:
Yeah, but either way that isn't at all what the instructions said. It's a .img file, not a .md5 file. And yes, that's definitely what bricked your phone.
[ONE General] WislaHD:
Well I am happy to report that my phone is unbricked by following the instructions in netbuzz's thread, and I successfully flashed and rooted my phone using the instructions in the OP.

Thank you Heisenberg for your rapid support response, it's been a tough few hours but now my phone is running the latest nightly and everything is super smooth. :)
[ONE General] Heisenberg:
That's very good news, glad to see you revived your phone.
[ONE General] juzzylink:
Hi... (sory bad english)

I want to root my one for installing x-mod, wich step should i do? Should i back up my data?

View attachment 3336083
[ONE General] Spannaa:
Backup everything you can because step one will wipe your data.

To obtain root, follow steps 1, 2, 3 & 4

Step 3 is optional but follow it anyway as you'll then have a backup of your rom.
[ONE General] Laucien:
****, sorry, wrong Q&A thread.
[ONE General] flod10:
hello,

please I need a answer

from one month ago, my phone is overheat, more the 70°C, I don't now way

I change some soft cm11, cm12,and another software and overheat is the same for all.

I have this phone from 8 month, and never have this problem.

now I am on stock cm11 and overheat is the same

this is happening when I am on data mobile, or when I put the phone in charge and I look on same video, I don't play game on this device

maybe somebody tell what to do for remove that heat from the phone

thanks
[ONE General] Mecca EL:
Go into settings, and display, then change the screen density from 480(default), to 400. This should help with the overheating, and give your battery a boost too.
[ONE General] Heisenberg:
Sorry, but no. The DPI setting has no bearing on the amount of heat that's produced, nor does it have an effect on battery life. What makes you think that?
[ONE General] Mecca EL:
Observation. I'd been running the same ROM for two weeks, and couldn't figure out why my OPO would suddenly overheat. Figured it could be something gone rogue, but nothing showed up in the logcat. I'm on CM12.1.1. Battery monitor showed nothing, no wakelocks, nada.

A week later, after deleting apps, and monitoring, I figure I'd change the dpi. I'm a graphic arts, so I know how resource intensive some settings can be. I went to 400dpi, and haven't experienced anymore overheating. I went from seeing 49-50c, back to maybe 30c. Still installing all 158 apps, and everything is fine. I'm not running any of the cleansing apps, except MobileGo, for connectivity purposes.
[ONE General] Heisenberg:
Fair enough, but the change in DPI isn't what stopped the overheating. It just doesn't work like that. The actual DPI of the device isn't changing, that's impossible, it's just changing the reported DPI of the device. Whatever was causing your phone to overheat was something else, and because your phone stopped heating up so much you saw better battery life because heat reduces battery life.
[ONE General] sm753:
After flashing TWRP recovery

Thank you for this wonderfully detailed guide.

However, it might be worth noting in the original post when flashing TWRP. If I reboot using the fastboot commands, CM recovery appears to overwrite TWRP. I couldn't figure out what the problem was, a few pages back - someone mentioned they got it to work by holding down the power button (in the fastboot "menu") until the phone shuts down, and then booting directly into recovery (vol down + power). That just worked for me as well.
[ONE General] flod10:
Mr. Heisenberg,

Please suggest me everything to escape from this heat.

Until one month ago, never happens to this phone.

When access mobile data, when I make a video, when play a game, but never same complicated game, I have that heat.

I change all soft 11s,12s,12.1 for all I have heat over 70°C, when I use the phone in that conditions.

I wait an answer please.

Thanks
[ONE General] Heisenberg:
It's impossible for me to determine what's causing the heat, so it's impossible for me to determine how to fix it. The only thing I can suggest is flashing the stock images and start clean.
[ONE General] tetakpatak:
It may be a hardware issue. If clean flash with fastboot doesn't help, I would send the device to OPO service.

tetakpatalked from Nexus 7 flo
[ONE General] flod10:
thanks for both for your answer

I made a clean install with cm11 so and I think the phone doesn't heat like before, is heat normal

I looking few day's and I will see what happened

thanks again
[ONE General] weshall:
Problem while rooting plzz help

I was rooting my one+ which is on cm 12 5.0.1 ...when I was trying to flash custom recovery using fastboot flash recovery recovery_name.IMG command the command ended properly but when I tried to boot in recovery mode it was still stock recovery not custom ( twrp)....I tried this 3-4 times then also same problem occurs.This made my one+ very slow ...plzzz help me and one more thing there is no root access {} option in developer option..what is the problem plzzz help me
[ONE General] Heisenberg:
The answer to your problem is in the underlined text at the bottom of section 2, didn't you read it??
[ONE General] naturallyfrozen:
I'm on 4.4.4. Cyanogen OS 11. I tried the regular process which required 'fastboot reboot.' Rebooted, did the advanced option, rebooted to recovery and didn't get twrp. I read the notes on bottom of section 2. I flashed, unplugged, then tried to access recovery. Everytime I do it, it boot loops once, then reboots normally. It never opened the recovery. I've read that I'm not the only one having this issue.

---------- Post added at 05:13 PM ---------- Previous post was at 05:04 PM ----------

Which recovery did you flash? I've tried that step, but the result is it boot loops once, then boots the OS regularly; never reach recovery.
[ONE General] sm753:
At first I flashed the latest TWRP recovery for the OPO. When it wouldn't stick, I thought maybe it was a compatibility issue? Don't ask why I thought this, I'm hardly an expert. I then flashed the exact version of the recovery the OP had in the post, I had the same issue with it not sticking until I rebooted directly from Fastboot to Recovery. Again, booting from Fastboot into OS appears to overwrite TWRP for some reason. Hope that helps.

I'm also on a 5.1.1 ROM so your issue might be different.
[ONE General] Heisenberg:
Did you remember to uncheck the "update CM recovery" option in Developer Options?
[ONE General] naturallyfrozen:
I tried both, checked and unchecked. Didn't make a difference. I've only tried to flash the latest TWRP. Later on today, I'll try to flash an older version of TWRP. I'll try all approaches (reboot via fastboot & reboot to recovery via hardware buttons). We'll see how that goes.
[ONE General] Heisenberg:
I just noticed that you seemed to contradict yourself, earlier you said you're on CM12 but later you said you're on KitKat, which is it?
[ONE General] naturallyfrozen:
Cyanogen OS version 11. Android version: 4.4.4. Exactly how I got the phone. I never claimed to be on CM12.
[ONE General] Heisenberg:
Yeah I was mistaking you for someone else, apologies. What is the output from the command prompt when you flash the recovery?
[ONE General] twowheeler:
curious: where did the famous reboot bootloader thing came from when flashing the factory image? I've seen toolkits do it as well. Never do it myself as nexus devices don't need it either
[ONE General] Spannaa:
Not sure as I've never used it on either Nexus or OPO.

IMO, it isn't necessary and can be dangerous on the OPO.

Sent via Bacon...