yashsingh1/xdaforums huggingface dataset:
[ONE General] Mr hOaX:
[MENTION=4153349]Heisenberg[/MENTION]

I would like you to add this information in OP

CMOS12 fasboot images doesn't have any different file for userdata.img(16GB) or userdata_64G.img. Even if you are on 64GB variant, you need to flash userdata.img

After first boot, immediately go into Settings->Storage and verify that it shows 54.XX GB for 64GB variant. If it doesn't show, boot into stock recovery with volume down + power button and factory reset and also wipe cache partition and reboot the system.

Now it'll display proper storage

P.S : If you are 16GB variant user, need not follow above steps
[ONE General] Spannaa:
The latest stock fastboot image linked to in section #8 of the first post actually does contain userdata_64G.img - I added it myself ;)

It's not really necessary to fastboot flash userdata though as the img doesn't contain anything

Simply wiping the data partition will give you exactly the same result.
[ONE General] Heisenberg:
[MENTION=2948558]Spannaa[/MENTION] beat me to it, but that's exactly what I was going to say. I'll leave the OP as is for the moment, flashing the userdata image isn't usually necessary anyway.
[ONE General] spicediablo:
I have tried flashing twrp recovery using fastboot but after rebooting, it is still ok cyanogen recovery. I have disable the update cyanogen recovery in developer option. Pls help
[ONE General] Spannaa:
Try reading post #1 especially the underlined part at the end of section 2...

Sent via Bacon...
[ONE General] crandy2:
I just updated to the latest 12s build YNG1TASI3, and I am having the same difficulty flashing TWRP. I did the underlined parts you referenced several times, but the vol down + power refuses to go into recovery after a power off. When I boot to recovery from the advanced power menu, it is still the stock recovery. Is it possible they did something in this latest build to circumvent that work around?
[ONE General] Heisenberg:
You're most likely just not doing the button combo right. Hold power to turn the phone off after flashing the recovery. Then hold volume down, then hold power (so you're holding them together), when you see the OnePlus boot logo let go of power but keep holding volume down until you reach recovery.
[ONE General] spicediablo:
I would like to know what these codes do, coming from nexus 4, I understand the meaning to flashing system, boot etc messages but these codes below, I'm not familiar :

fastboot flash modem NON-HLOS.bin[/CODE]

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

Much appreciated. Thanks.
[ONE General] marcusblue:
Hi, I had encounter all sensor are not working except sound (mic), had try to restore to stock rom, from CM11, CM11S, CM12 and the latest build also not function, all sensor not working. Try other rom like blisspop, exodus, miui, coloros, all are out of luck, still can make that sensor work. Is there a way to check the function of all sensor using software method? maybe this is hardware issue. Another question is why the "sys" folder still exist even i had already format and wipe the system and ready to flash a new rom, maybe there's some corrupted file in the "sys" folder that cause this issue, hope someone with the knowledge here can help me.
[ONE General] Heisenberg:
Have you flashed the stock images with fastboot?
[ONE General] crandy2:
Thanks for the help. You were correct. I was also trying TWRP 2.8.6.0, when 2.8.6.1 is the one I should have used.
[ONE General] marcusblue:
I had flash all the file using fastboot method, that included the stock image. still cant get the sensor to work. Do you know about the "sys" folder? maybe some files corrupted in this folder. I am not familiar with the file system, but when i browse all the file in the phone after flash a new rom, the "system" folder only change but content in "sys" folder stay the same.
[ONE General] daringsmart:
i unlocked my bootloader successfully now i need to flash recovery wch one u recommend twrp official or unofficial one??
[ONE General] Heisenberg:
Can't really recommend one but I use the official one.
[ONE General] daringsmart:
the one u recommended in 1st post ???? and its the latest one (( openrecovery-twrp-2.8.5.1-bacon.img )) pls confirm
[ONE General] Heisenberg:
They've changed their download site, the link in the OP is fixed now.
[ONE General] daringsmart:
OK thank u buddy
[ONE General] alkaloids:
I've followed your guide to unlock the bootloader and root and everything went well. But then I tried to backup my EFS partition as described in step 10 but it didn't work out. I followed the exact steps and typed in those commands and got the exact same output as shown in the screenshot, however, there are no files to be found on my internal storage. It seems as they're just not created. Any idea what's the problem?

EDIT: Ok, so if I browse the storage on my phone, I can see the two files, but I just don't see them on my PC (W7). I thought it might have been a setting on my pc but I tried several things and can't seem to make them show up.

EDIT2: Hmm, I found them, though I don't understand what the initial problem was. I created a new folder on my phone and moved the two files there (on my phone), when I opened that new folder on my pc, I could see both files.
[ONE General] Heisenberg:
Yeah that's a pretty common but annoying problem, for some reason you can't see files in the root of the internal storage when it's mounted to a PC.
[ONE General] daringsmart:
[MENTION=4153349]Heisenberg[/MENTION] thank u so much for this guide. I have successfully unlocked my bootloader and also installed twrp. Now its time to install ROM and kernel. 8x thanks pressed. :D:cool:
[ONE General] Heisenberg:
No worries, I'm glad that it helped you.
[ONE General] dada vali:
hello.

i cant flash zip file from twrp recovery

( install failed

finding update package . . .

opening update package . . .

verifying update package . . .

E: failed to verify whole- file signature

E: signature verification failed

installation abort.)

:(:(:(:(:(
[ONE General] Spannaa:
Every zip file or one in particular?

If you need help, giving as much detail as possible about your issue will probably result in a quicker answer...
[ONE General] JimJ2Mz:
[MENTION=4153349]Heisenberg[/MENTION]

Hi there. I'll be quick. Is flashing the CyanogenOS Fastboot image you provided similar to updating to the latest CyanogenOS version via OTA? Does it include the new modem, firmware, touchscreen fixes, etc.? I'd much rather flash to the latest version instead of take multiple OTAs. Thanks!
[ONE General] Spannaa:
I'm not [MENTION=4153349]Heisenberg[/MENTION] but flashing the latest recovery flashable zip or fastboot flashing the contents of the latest fastboot zip will give you the same result as flashing multiple OTAs.

If you're coming from CM11S then you need to wipe data as well as caches before updating so back up anything important first.

Sent via Bacon...
[ONE General] JimJ2Mz:
Sounds awesome. Thanks! Well, to you and Heisenberg. I'm new to the OPO and I am thoroughly excited now that I have a device with countless ROMs and kernels.

---------- Post added at 02:58 PM ---------- Previous post was at 02:32 PM ----------

[MENTION=2948558]Spannaa[/MENTION]

Apologies if I'm bothering you, but I have yet another question.

Once I fastboot flash to the latest build of COS12, do I need to do anything special before making the jump to another custom ROM, like Exodus? Anything I need to flash or modify, or am I already set?

Thanks again!
[ONE General] Heisenberg:
There's nothing extra that you need to do, you can just flash the custom ROM of your choice.
[ONE General] JimJ2Mz:
Okay. Thank you for the help.
[ONE General] AJ.Rockwell:
An AWESOME resource, thanks SO much!

In any case, if someone would run to corrupt cache when flashing recovery in Step #2 "fastboot format cache" step like me - the phone gets stuck on the boot animation and even upon applying something that requires cache manipulation (custom ROM or Kernel / cache wipe) the Recovery will tell you that it can't open /cache.

The solution is simple - just flash the cache from the official image via fastboot (fastboot flash cache cache.img) and you are back in business :)

Cheers!
[ONE General] rehan716:
Great post. Thanks a lot
[ONE General] arkedk:
If anybody wants to have a batch script for flashing the latest cm-12.0-YNG1TAS2I3-bacon-signed-fastboot that doesn't wipe your userdata and keeps your TWRP recovery, I've made one for myself.

I couldn't get the OTA to flash in TWRP some error on incorrect build number, so just downloaded the full zip unpacked it and put my script in the same folder.

And just for good measure, remember you have to have your adb and fastboot drivers installed for this to work!

I came from build cm-12.0-YNG1TAS17L.

But in case anyone else can use it, here it is. It relies on you having downloaded the:

OS	File	MD5
Cyanogen OS 12.0 (5.0)	cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip	1d8b0ec9207776646e84b16fd7f43259

https://cyngn.com/support

Then just save this as a .bat file in Windows. If you have installed the Android SDK at the standard location it should just work, if not then just correct the PATH=%PATH%; to your ADB and Fastboot files.

PATH=%PATH%;"%localappdata%\Android\android-sdk\platform-tools\"
adb reboot-bootloader
adb kill-server
ping -n 5 127.0.0.1 >nul
fastboot flash aboot emmc_appsboot.mbn
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash tz tz.mbn
::keeping TWRP recovery. Remove comment out if you want stock recovery.
::fastboot flash recovery recovery.img
::fastboot reboot-bootloader
::ping -n 5 127.0.0.1 >nul
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot reboot
[ONE General] clemens_s:
No OS installed

Hello!

You already answered to my question from yesterday, but it still didn't seem to solve my problem.

The only difference in TWRP i realised between my phone and your instructions was the following: When you said choose the custom rom zip for installation --> swipe to install...it says swipe to confirm flash on my phone. And after i did dalvik/cache wipe, i pressed reboot and the phone still said no OS installed. Are you sure you want to reboot?

Please let me know if you have any idea what I am doing wrong all the time.

Regards,

clemens_s
[ONE General] Spannaa:
[MENTION=2949982]arkedk[/MENTION] - Can I suggest that you remove the fastboot reboot-bootloader lines after every step as they're unnecessary and can brick devices ;)

Reference: the last few pages of this thread.
[ONE General] arkedk:
Script corrected, thanks for pointing that out.
[ONE General] Raahul_Singh:
Thanks!

Worked perfectly for me!

Thank you so very much !:D
[ONE General] redesign93:
hey guys

so i have never really rooted or done anything with my phone

i used to only apply OTA updates

so right now my phone is on Cyanogen OS 12.0-YNG1TAS2I3 / Android version 5.0.2

So i am thinking of flashing a custom rom on my OPO

On the first page it says

so can some one please explain that, do i have to flash the custom recovery twice ? or after the bootloader thing i directly do that step?
[ONE General] Heisenberg:
Flash your recovery once, and then use those instructions to boot directly into recovery instead of booting into the OS (booting into the OS will patch the recovery with the stock one).
[ONE General] redesign93:
thanks dude

i got it

so first unlock bootloader then put the custom rom into my phone

then install custom recovery twrp

then power off

then use hardware keys to go to recovery mode

and flash the custom rom

right ?
[ONE General] AbedFa:
uh this probably isn't the place to say this but, what good would rooting your device do. I mean, of all the things I've seen it appears that rooting is more negative than it is positive
[ONE General] Heisenberg:
That's right.

You're looking in the wrong places then, there are countless reasons to root a device. Look online, plenty of articles available.
[ONE General] AbedFa:
Hi, this is my current system info

(sorry xda just wouldn't allow me to post link. Copy paste this please)

i18.servimg.com/u/f18/11/07/64/32/screen10.png

and I was wondering whether I can just go ahead with the rooting process without having to manually reset everything first hand? the OS or Android version shouldn't matter?
[ONE General] Heisenberg:
I just answered you in the other thread you posted in, please don't create duplicate posts, it's against the rules. Anyway, yes you can go ahead because your Android version and build number don't matter. Pay attention to the underlined text in the section about flashing TWRP recovery to your device.
[ONE General] AbedFa:
My apologizes. I was planning to follow Chromium's guide because it looked much simpler and easier to follow since I'm a complete beginner. Your guide, on the other hand, has a lot of steps that I have no idea of.

I mean, compared to Chromium's, that's a lot more. I was thinking that there could be some steps that are unnecessary in your guide which I can skip, but I know that's unlikely.
[ONE General] Heisenberg:
The processes in my thread are the same as in Chromium's, mine just contains more guides than his does. The numbered sections in my guide aren't steps, so you don't need to follow them all. Each numbered section is a guide on how to do a specific thing. If your phone is stock then you'll need to follow the sections for unlocking your bootloader, installing TWRP recovery, making a nandroid backup, and installing a custom ROM. You should really make an EFS backup too, that's super important.
[ONE General] AbedFa:
This is what I feared the most.. I couldn't even get past unlocking my Bootloader.

I installed the full Android Studio/SDK and universal adb/fastboot driver. Although I got this when it was almost finished installing:

gyazo.com/703ebe0cca893b8393e8e69161e27dd3

This is the step I'm struggling with:

I don't know what you meant by fastboot folder, or where to find that.

And this probably won't be the only thing I get stuck with, so can I ask you to recommend me any video guide similar to this instead? Perhaps, if you've made one?
[ONE General] Heisenberg:
You're installing the wrong thing, you don't need the Android Studio. You want to go to the link that's in the start of my guide, scroll to the bottom of the page and find the "Other Download Options" section. Right there you'll find download links for the SDK Tools, get appropriate one for your OS.
[ONE General] AbedFa:
Thanks. I got it right this time, and I'm making progress.

It seems that I ran into a problem (not sure if it's anything major) so I want to make sure before proceeding:

prntscr.com/7zkfwb

Sorry for troubling you with every little thing.

EDIT: Also, I have Cyanogen OS 12.0-YNG1TAS2I3 do I need to pay attention to this?
[ONE General] Spannaa:
Watch your spelling - it's fastboot flash recovery not fastboot flash recover ?

EDIT: Yes you do need to pay attention to that.

Sent from Marrakech via Bacon...
[ONE General] AbedFa:
Oh my God. Silly me

Thanks mate

---------- Post added at 12:36 PM ---------- Previous post was at 11:54 AM ----------

Okay, I've rooted my stock ROM, made a Nandroid Backup With TWRP Recovery. Installed cm-12.1-20150731-NIGHTLY. But I'm gonna need to download Google Play now since it's not included in this ROM

I tried downloading several APK files to install Google Play. It was installed and all but when attempted to run it just flashes in and out immediately. I can't run it.

What should I do?
[ONE General] Heisenberg:
Only install a custom ROM if you want to, you'll find plenty in the development sections here in the OnePlus One forum, the links are in the threads for the ROMs, just download the ROM zip (and a gapps package) to your phone and then you can use TWRP to install it.
[ONE General] drsamratroy:
[MENTION=4153349]Heisenberg[/MENTION] this is my current status.... bought my phone a month back, unlocked bootloader, rooted it, installed a custom recovery but dint get any guide on how to upgrade to 5.1.1 from 4.4.4 Android version? ....also as i am coming from a HTC One which din't have much custom ROMS based on nightlies, can u also advise me on a stable ROM with weekly or monthly updates? View attachment 3425541
[ONE General] Heisenberg:
To upgrade to Cyanogen OS Lollipop just grab the latest flashable zip from here:

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

You can just flash that with your recovery. But if you're going to flash a custom ROM there's no point in doing that. I run Exodus ROM, there's a link to the thread in my signature.
[ONE General] drsamratroy:
But in the blisspop rom instructions, they talk of flashing a firmware of 05/15 build before flashing any new ROM...do i need to flash it??
[ONE General] Heisenberg:
You can flash that 0515 firmware or flash the latest CM nightly to make sure you're on the right firmware first. Keep in mind that recent versions of TWRP recovery don't flash firmware properly so you'd need to downgrade to the 2.8.6.0 build.
[ONE General] Nakulkhanna:
hey guys i unlocked my bootloader successfully but am stuck at installing the TWRP recovery. i have the latest recovery downloaded in the sam folder where fastboot.exe is located, now when i give the command to install it gives Error: cannot load "openrecovery twrp-2.8.7.0-bacon.img"

and yes is did change the name of recovery to the one i have in command line.

Plus also tell me where do i have to check the md5? i dont know what is that...

PLZ HELP
[ONE General] Heisenberg:
Please show a screenshot of the command prompt when you try to flash it.
[ONE General] elargento:
Thanks heinsenberg, I finally managed to install twrp with your steps.

Enviado desde mi A0001 mediante Tapatalk
[ONE General] kewinhdorff:
hey everyone in this thread.

i have got the oneplus one. have been running cm11s xnph44s for a very long time. and it has been great but i want to use cm12 now. i feel like i want to update.

so, i downloaded the fastboot zip on cyngn.com/support for oneplus one the (cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip) but inside the zip there is only the userdata.img file and not a userdata_64G.img file. i have the black one so 64G... why is there no userdata_64G.img in the zip file from the official source ? or maybe it doesn't matter ? any help much appreciated :)

Edit: i would update it through fastboot mode rather than through the recovery. fastboot mode seems better and i am pretty used to it. so just help me figure out that i should do about the userdata. and also what in what order i should flash them or should i jsut flash them in the same orders as if i would flash the cm11s?
[ONE General] Spannaa:
Read section #8 in the first post ?

Sent via Bacon...
[ONE General] Reptilez_DK:
It doesn't really tell, how to deal with the userdata being the wrong size. :)

What I did, (I also have a 64 GB device) was flash the userdata file included in the zip, and then wipe/format/erase internal storage. Don't know if it was actually necessary, but better safe than sorry.
[ONE General] Spannaa:
Flashing userdata.img on a 64GB device can leave you with a small data partition.

Unless your data partition is messed up completely though, you don't need to flash userdata/userdata_64G at all.

Just wiping both data and internal storage or doing a factory reset is enough.

Sent via Bacon...
[ONE General] Jirv0id:
Awesome guides, but for whatever reason my 1+1 won't write system via fastboot. Everything else flashes fine. [IMG="Log"]http://s27.postimg.org/6g9372n0j/LOG.png[/IMG]

*Edit it has been like that for over 15 minutes*
[ONE General] Kofi o:
Order of flashing

Thanks for the excellent guide.!

In section 8 of this guide, is it important to Flash the image files in the order stated?
[ONE General] Heisenberg:
Not really, but why wouldn't you?
[ONE General] elargento:
I forgot to flash the rpm in step 8 and hardbicked the phone. Luckily I managed to fix it but I got really scared for a moment.

Enviado desde mi A0001 mediante Tapatalk
[ONE General] Heisenberg:
It wasn't a hard brick then. That would be a soft brick.
[ONE General] elargento:
Nope, definitely a hard brick. Couldn't boot into fastboot or recovery, no image on screen nothing.

Enviado desde mi A0001 mediante Tapatalk
[ONE General] Heisenberg:
How did you revive the device?
[ONE General] elargento:
I followed a guide posted on this forum. I had to install new drivers for the phone and flash color os with a toolbox provided in the same guide.

Enviado desde mi A0001 mediante Tapatalk
[ONE General] Heisenberg:
I know the one you mean, that still isn't technically a hard brick though. Either way it's good you were able to get it working again.
[ONE General] elargento:
I guess you're right. But the more common soft bricks are way easier to fix. Because you can enter recovery or bootloader.

Enviado desde mi A0001 mediante Tapatalk
[ONE General] Heisenberg:
That's true, but even most situations where people refer to their problem as a soft brick isn't right either. A true soft brick can't be recovered from. For example, a situation where the phone won't boot into the OS, has no access to recovery, has access to the bootloader, but it's locked and is unable to be unlocked in order to flash fastboot images. Most "soft bricks" that people report here usually just require another flash to fix, so it isn't really a brick at all.
[ONE General] yoyo_58:
Heisenberg

Thanks much for the guide, especially part 8.

Do you have a writeup that explains what the files that are pushed in part 8 are or what they do?
[ONE General] Heisenberg:
No I don't, some are pretty self-explanatory, others are not. They're essentially firmware components as well as the recovery, the system, the bootloader.
[ONE General] Kofi o:
Thanks.

Just in case - it's not entirely impossible to accidently mix the lines up.
[ONE General] Heisenberg:
Yeah true, as long as they're all flashed it'll be fine.
[ONE General] 903tex:
Well I installed twrp 2.8.7.0. Heard about it being not good. So I tried to downgrade to 2.8.6.0. It will flash but trying to boot into it phone just reboots back to rom. But I can flash 2.8.7.0 and it will boot into it just fine. Do I need to downgrade even further, or should I use another custom recovery all together
[ONE General] Heisenberg:
I've seen others with this problem talk about it in the q&a thread, have a look there and you should find your answer.