yashsingh1/xdaforums huggingface dataset:
[ONE General] Anghirrim:
Yep, I have to say that everything you did seems right. I don't understand why it fails...

Concerning the rom, as you just installed TWRP, I guess you are still under the official COS 12.1.

Last option, try another terminal emulator on your phone...

And last question, before you begin with your first trial, did you typed in "su" in your terminal?

I'll let more advanced users help you, it's now beyond my limited knowledge.

In case of, just try googling quickly your issue (dd disapearing or adb rights refused), maybe you'll find an answer.
[ONE General] drsiddique5700:
yeah I m still on cmos 12.1 and I tried all what u said different terminal apps and of course typed su in it
[ONE General] Anghirrim:
So I just have to say goid luck then... Sorry
[ONE General] Art Vanderlay:
To answer this question, the letters in the terminal app aren't being deleted. The screen scrolls across in a clunky way so the letters move off screen. Just keep typing and finish the command and it'll work.
[ONE General] arktay:
Thanks for the detailed guide. I need to do a full wipe. What about unlock and relock the bootloader?
[ONE General] Spannaa:
Don't relock your bootloader after unlocking it, you won't be able to unlock it again without using an unbricking tool.

If you really want a full wipe, unlock your bootloader, fastboot flash TWRP and the use TWRP to wipe what you want wiped.

Tapatalked via OnePlus 2
[ONE General] arktay:
If i want to do a wipe without unlock bootloader can I do it with the stock recovery?
[ONE General] Spannaa:
I don't know - I always unlock and install a custom recovery as soon as I get a new device to save issues later.

Boot to stock recovery and see what options are available maybe...

Tapatalked via OnePlus 2
[ONE General] askpcguy:
No, you need a custom recovery in order to wipe/format partitions. Just make sure you can flash your recovery and custom ROM after the wipe.
[ONE General] cliffflip:
Hi, I have few question regarding this method :

1. I'm on CM12.1.1-YOG7DAS2K1 (Lollipop 5.1.1), Is this method works on current OS version?

2. After doing those method, will it revert back to Kitkat (factory version) or stays on current version (Lollipop)?

3. After doing those method, will I get more OTAs from Cyanogenmod?
[ONE General] Art Vanderlay:
Yes

The firmware in the OP is lollipop. You can flash whichever version you want.

Yes
[ONE General] erik.aragorn:
I have COS 13, but methode for flash TWRP not working :-/ what now? After flash TWRP, and reboot do recovery it's still cyanogen :(
[ONE General] Anghirrim:
Try holding the volume down button right after you type "fastboot reboot". COS might erase TWRP automatically if you're booting system right after you flash TWRP.
[ONE General] s4meq:
Recovery problems.

I'm having difficulty on my oneplus one, COS 12.1-YOG7DAS2K1. Every time I try to flash TWRP, it reverts back to COS recovery.

This is what I get in Fedora Linux 23.

[user@localhost ~]$ sudo fastboot flash recovery twrp-2.8.1.0-bacon.img
[sudo] password for user:
target reported max download size of 1073741824 bytes
sending 'recovery' (12588 KB)...
OKAY [ 0.397s]
writing 'recovery'...
OKAY [ 0.105s]
finished. total time: 0.503s
[user@localhost ~]$ sudo fastboot format cache
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.038s]
sending 'cache' (10432 KB)...
OKAY [ 0.331s]
writing 'cache'...
OKAY [ 0.125s]
finished. total time: 0.494s

I should also note that when doing what is stated in the OP, the phone is stuck on the Oneplus logo. However when holding down the power button it boots up normally- and I lose TWRP recovery.

fastboot erase recovery
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot

This might work, but I have not tested this.
[ONE General] CBpbxEcmecmBeH:
what happens when you boot directly to recovery from fastboot (after flashing TWRP)? Power down the phone in fastboot mode and enter recovery directly with power+volumeDown
[ONE General] s4meq:
I'm trying that, and when I do as you described it vibrates and shuts off again at the 1^+ logo. Hmm... seems something is wrong. When powered on with power button it boots up as normal.
[ONE General] 26.2man:
Timmaaa

You have realy been helpful and I need one more bit of advice and direction. Since I did the sideload of the ota and have some issues with the lockscreen wallpaper, I want to start over fresh. I have the cm-11.0xnph25r-bacon signed flashable zip on my phone. Will the easiest way to start over be to just flash that zip?
[ONE General] RISHI RAJ:
yup
[ONE General] hamzer11:
This guide is incredibly helpful so thank you for putting it together and maintaining it. I have a question though. You state in section 6:

I know I modified the stock email apk so I think I'm in this category. Therefore if I use the modified OTA file for the initial upgrade, can I then use the regular incremental update file as is or is there a modified version of that also? Or do I have to add the modified script to that zip file?

Also, generally, will I retain TWRP recovery after this? I am reading various things about it.

Thanks
[ONE General] Heisenberg:
You'd need to modify the updater script for the incremental update too. As long as you don't have 'update cm recovery' ticked in Developer Options TWRP won't go anywhere.

Transmitted via Bacon
[ONE General] Heisenberg:
That's definitely the best way to start fresh. But, I'm not sure it's going to help you, multiple people have reported the same wallpaper problem as you so I think it's a bug in the build.

I'm lost then, I'm not sure what's wrong. Did you check the md5 of the download? You didn't wipe system first did you?

Transmitted via Bacon
[ONE General] knightsh:
Sorry guys, but I'm having problems. First time using adb. Previously had Samsung phones and used odin, etc. I successfully sideloaded the latest update to 30O. Decided to go ahead and unlock bootloader which seems to have worked. While trying to flash twrp recovery I get an error stating it couldn't load it. Any idea why it's not working? I have the android sdk on desktop for ease of use. I downloaded the twrp recovery file(which shows up as a disk image) and placed within the platform-tools file and renamed file to recovery.img.
[ONE General] Heisenberg:
So the recovery image is in the same folder/location as fastboot.exe? Did you check the md5?

Transmitted via Bacon
[ONE General] knightsh:
timmaaa- it's located inside the platform-tools folder. If i open the android-sdk folder,then open the platform-tools folder,inside is adb, sqlite3,api, systrace,fastboot, the recovery download and some other stuff. Is that the correct location?
[ONE General] Heisenberg:
Yeah that's fine, what's the full filename of the recovery? And did you check the md5?

Transmitted via Bacon
[ONE General] Ziglez:
When i try to go into fastbook, i get a black screen, it seems to try to do something as my device manager refreshes when i go into bootloader, but nothing comes up.
[ONE General] Heisenberg:
What method are you using to get into fastboot? And please provide some more information about your device.

Transmitted via Bacon
[ONE General] bobcat333123:
I finally received OTA update prompt on my phone today.

I have few more questions:

1. Can I simply install SuperSU from Playstore or do I need to flash it via TWRP?

2. If yes, how do I do that?

3. I saw on cyanogen website a battery drainage got fixed 2h ago. Will this be included in the next update and will I be able to install it instantly or will I have to wait for my line like for the first OTA update?

Thank you for your time,

Alan
[ONE General] Heisenberg:
1. You have to flash it with TWRP recovery.

2. Please read the thread you're posting in.

3. There's information on the post you're talking about that states there will be an OTA pushed out specifically to address the battery drain issue, so yes it'll be included in the next update because it's the reason for the next update. As for how the update is being rolled out, I'd hazard a guess that it'll be asap but I can't say for sure because I'm not a member or employee of CM.

Transmitted via Bacon
[ONE General] timmyhasissues:
erasing cache causes bootloop

Just throwing this out there, I had a problem when I was following the guide installing TWRP. After I rebooted it became stuck in a bootloop (got past the 1+ logo to the boot animation, animation never froze but boot never progressed from there). I was able to power off and could enter both fastboot and TWRP. In TWRP I was getting an error of "unable to mount cache". Turns out the "erase cache" wiped it clear and the cache couldn't be read. Better to use "fastboot format cache", which erases then initializes the cache partition.

Other than that great guide so far [MENTION=4153349]timmaaa[/MENTION]!
[ONE General] zephiK:
A bit off topic but awkward [MENTION=5991695]timmyhasissues[/MENTION] just made a forum account and op's name is [MENTION=4153349]timmaaa[/MENTION] :eek:
[ONE General] timmyhasissues:
Well I had some issues. I got bettah.
[ONE General] Heisenberg:
Glad to hear it.

Transmitted via Bacon
[ONE General] enigmagnetic:
OTA update XNPH30o - downloaded before unlock bootloader

I just got the OPO. I installed the XNPH30o OTA today right after powering on. I almost regret it now because I don't see anyone mentioning you can use this guide to unlock the bootloader and install custom recovery while on XNPH30o. I haven't tried it yet. Has anyone tried "fastboot oem unlock" with XNPH30o and is it working?

Does anyone know if any of the toolkits are working on XNPH30o?
[ONE General] CBpbxEcmecmBeH:
why not 2.8.6.0 or 3.0.2.0?
[ONE General] s4meq:
Tried 2.8.60 still the same as I described. 3.0.10... hmm I'll have to try. I'll consider it.

---------- Post added at 09:31 PM ---------- Previous post was at 09:09 PM ----------

I did it! TWRP 3.0.10. Typed

sudo fastboot reboot

but held down power and vol down before pressing enter.

SuperSU here I come!
[ONE General] ichigo696:
After flashing twrp, press power+vulome down, then when you see oneplus logo release power and keep pressing volume down until you see twrp logo.
[ONE General] itman00:
Hi,

I have the Oxygen rom installed in my OPO, but I want to go back to CM. Can I use 8 point of this guide without problems?

I apreciate any help on this subjet.

Thank you.
[ONE General] ichigo696:
Sure you can.
[ONE General] itman00:
Thanks, it was worked perfectly.
[ONE General] roastednerd:
Stuck on boot screen

Hi, today I installed the cm13 update, but it completely ruined my Oneplus One. I wanted to downgrade back to CM12.1 so I followed the instructions in this guide to flash an update, but when I try to execute these commands I get the error: Cannot load ....img

fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64G.img

and when I try to reboot I get stuck on the Oneplus logo. What can I do?
[ONE General] kas_27_es:
Hi boy, I'm planning upgrade... What has happened?

Enviado desde mi A0001 mediante Tapatalk
[ONE General] roastednerd:
The battery drained really fast and charging took a very long time, the battery got really hot and it was very slow.
[ONE General] kas_27_es:
Wow[emoji15]

Has got these problems anyone else?

Thanks

Enviado desde mi A0001 mediante Tapatalk
[ONE General] roastednerd:
I fixed it, I didn't download the fastboot thingy.
[ONE General] Dipping_Sticks:
i am unable to get past 2. How To Install A Custom Recovery On Your Device

I cant load the fastboot flash recovery openrecovery-twrp img.

I've tried 2.8.1.0 and twrp-3.0.2-0 get error msg saying its corrupted when i try to mount it. Cmd window says "error: cannot load"

(CM13 destroyed my opo as well, major battery drain, settings crashes, no sim detected, major lag takes about a minute for settings to open properly)

HELP
[ONE General] atulclassic:
try downloading twrp again from this link and then flash accordingly

https://dl.twrp.me/bacon/twrp-3.0.2-0-bacon.img.html
[ONE General] Aazeb:
Did you perform a full wipe before flashing the CM12 stock images? I've downgraded twice from Lollipop to Kitkat.
[ONE General] kryshnakishore:
How to solve this without root
[ONE General] djha53k:
[MENTION=7442015]Dipping_Sticks[/MENTION] : use TWRP 2.8.6.0 !!! It is still the BEST version. I'm on it since in was created and I NEVER had any issue with installing.

[MENTION=6892058]kryshnakishore[/MENTION] : switch off the root option in developer menu (or unisntall SuperSU if you have it)
[ONE General] kryshnakishore:
Both did not help... I dnt use supersu at all, I have cm inbuilt su
[ONE General] Caststarman:
On step 9, tried this but the system.img did not work. Here is what command prompt says:
[ONE General] Spannaa:
Which fastboot zip did the system.img come from?
[ONE General] Caststarman:
cm-13.0-ZNH0EAS2JK-bacon-signed-fastboot.zip It was this one.
[ONE General] Spannaa:
I don't have a OnePlus One so I can't test it...

Did you check the MD5 of the zip to make sure your download was OK?

Did you try rebooting into fastboot mode again and fastboot flash system system.img again?

You could download the signed flashable zip and flash that via recovery.
[ONE General] Caststarman:
I actually fixed the problem by trying again with the most recent 12.1 update. I am able to download the incrementals OTA so I'll be able to update to 13.0 later. Thanks for all the help though!
[ONE General] FloppyTacoes:
Should I be worried about my EFS data before I unlock bootloader / flash TWRP and SuperSU? Or am I good to do those things? (not currently rooted)
[ONE General] Spannaa:
I don't think there's a way to backup your EFS unless you have TWRP or root.

Once you've unlocked your bootloader and fastboot flashed TWRP, you should back it up.

Hopefully, you'll never actually need the backup.
[ONE General] FloppyTacoes:
Fot step 11. I do the commands but the file doesn't show up no matter what I use. What gives?
[ONE General] wael.kh:
Rooting official CyanogenOS 13?

how to root ? official COS13?

I have bootloader unlocked already, but i have stock recovery, cuz when i tried rooting with TWRP 2.7.1.x , it ended up with boot loop and i restored to stock, and now with stock recovery...

should i flash the latest TWRP then root?? with which files??

Thanks in advance.
[ONE General] ichigo696:
I believe you have to use latest TWRP, btw what superSu version are you installing?
[ONE General] azimisahak:
before proceed to all these step stated, do i need to enable usb debugging? The problem is i cant enable usb debug since i'm stuck at audiofx has stopped
[ONE General] Heisenberg:
The sections that use adb only require usb debugging to be turned on, the sections that use fastboot do not.

PS. Please don't quote the whole first post on XDA, they're huge and clog up the page. Can you please edit your post to remove that quote? Thanks.
[ONE General] jaisonguru:
HI I did exactly as per the

8. How To Flash The Cyanogen OS Fastboot Images;

Except the last stage as I wanted my data.

The phone is going in a loop, where it boots, after the logo, comes to main screen and withing 5 seconds reboots.

The problem started as I was draining too much battery due to play store, and i tried to go and change the settings in privacy. T overcome that i did the re installation but it is still failing ..

Do i need to flash userdata also..?
[ONE General] Spannaa:
You didn't say what rom you were on before and which fastboot zip you used but, I suspect you have incompatible data.

You can probably sort this out by booting into recovery and doing a factory reset (wiping data & caches but not your internal storage).

You will lose your apps & messages unless you have them backed up though.
[ONE General] Kundan Wadkar:
Sir i followed all steps for unlocking bootloader via fastboot all drivers were correctly instaleed shown as fastboot and adb device....but after the command fastboot oem unlock it went to state where it says erasing.. it has been a lot of time 15 mins passed what should i do???

please help?

have i lost my oneplus1 please help...please
[ONE General] jaisonguru:
Finally had to do last step of flashing userdata-64G, as expected lost all data.

Could have taken a backup from TWRP.

Any way .. a new beginning.

I installed 13.0 ZNH0EAS2JK, now the phone is having a system update...

Then Root and back to the game!!
[ONE General] jaisonguru:
After the update, the best battery performance so far ever...

Phone is not heating up any more.

What else you need.... Highly satisfied...
[ONE General] davidred7697:
Hi.

I have a HUGE problem and need help.

I was on Cyanogen OS 12.1 and decided to install the latest Cyanogen OS 13.1. I downloaded the flashable zip. Booted into TWRP recovery and installed zip file. I had always allowed my phone to reinstall Super SU in the past with great succes, but it seems I shouldn't have done that? Now my phone is stuck on the bootup animation that says "Cyanogen MOD ready". I also cannot boot into the recovery or safe mode using hardware keys. Please help! I don't want to lose my phone or my data!

Thanks for any advice.

EDIT: I was able to boot into recovery using the command "fastboot boot recovery.img". I cleared dalvik cache and flashed COS 13.1 zip. Currently waiting for phone to boot. Hope it doesn't get stuck on the bootup screen again.

EDIT2: It looks like my phone has booted successfully and is now optimizing apps for COS update! If I don't follow up, it means everything worked out great again!

EDIT 3: My phone finished "optimizing" apps. I thought it would take me to my launcher as all other times I've updated. To my surprise, the phone seemed to reboot and was stuck on the "splash screen" (Cyanogen MOD ready) for a few minutes. After that, I got the "Android is starting" "Optimizing app xx of xxx" message, which is incredibly weird and I think my phone might be in a bootloop. PLEASE HELP!

EDIT 4: One day after this happened, I remembered that I had done a nandroid backup last February. I flashed it using "restore" in TWRP, but my phone has been stuck on the "cyanogen" boot screen for 10 minutes. What now?
[ONE General] Anghirrim:
Did you clean flash and wiped data?

Coming from lollipop to marshmallow, you must do it.
[ONE General] davidred7697:
Thanks for replying. I ended up wiping everything and doing a factory reset. I then updated to COS 13.1 successfully.

The problem I have now is that I can't access TWRP manually using hardware buttons even though I installed it using the command "fastboot flash recovery recovery.img". Even after using the command, trying to reboot straight into TWRP doesn't work. It just shows a blank screen (no access to stock recovery either).

The only way I can access TWRP is by using the command "flashboot boot recovery.img".

Also, when I try to install super SU binaries for root using "adb push UPDATE-SuperSU-v2.65-20151226141550.zip storage/sdcard/", I get "error: device not found".

EDIT: I flashed Super SU and Xposed framework from TWRP and now my device seems to be in a bootloop. It's stuck on the "Cyanogen MOD ready" boot screen. :(

EDIT: I was able to get my phone back by factory resetting and restoring a nandroid backup from february. Could you please tell me the correct procedure for installing COS 13.1 AND having root access with the super su zip AND installing xposed framework zip? I've attempted this three times now and I always end up in a boot loop!
[ONE General] Anghirrim:
For me I juste fastboot flashed the whole factory image (exception from the userdata.img).

Then at least supersu 2.65 (systemless).

For Xposed, don't know. But I would suggest you to go step by step to identify what makes your phone bootloop.

Boot after each step.

If your nandroid backup ils a Lollipop, factory reset your phone in TWRP before flashing it via fastboot.
[ONE General] atulclassic:
What i do..

1. Flash full fastboot factory image..reboot..setup

2. copy supersu 2.74 beta & xposed v85 sdk23 to device

3. reboot to bootloader..flash twrp recovery using fastboot flash recovery recovery.img

4. power off..quickly reboot to custom recovery using vol down + power

5. flash supersu 2.74 & xposed v85 in a row..wipe cache..reboot

6. it takes 5-10 minutes to complete booting upto homescreen.

EDIT : This will wipe al your data..so make sure to take a backup first and keep it safe in pendrive or computer
[ONE General] davidred7697:
I essentially followed the same procedure except I installed a flashable zip from TWRP as opposed to the fastboot factory images, so not sure what might have gone wrong.

I'm going to try to install root and xposed again today and if I get stuck in a bootloop, I'm considering using the fastboot factory images without flashing userdata.img to save my personal files.

---------- Post added at 02:18 PM ---------- Previous post was at 02:16 PM ----------

Got it. It seems that either the super SU zip or the Xposed framework zip are causing the bootloop. I'll take your advice and do it step by step.
[ONE General] bigdogdon:
COS 13.1 Locked Bootloader

So, I was rooted and running COS 13.0. Recently, I flashed the latest COS 13.1 stock ROM using TWRP... I thought I had de-selected "Update Cyanogen Recovery", but apparently not because it has locked the bootloader and installed the Cyanogen recovery.

Now I am unable to unlock the bootloader... the tamper bit is set to true. When I use

fastboot eom unlock

It simply re-boots to the Cyanogen recovery.

Is there something different about COS 13.1 that doesn't allow the bootloader to be unlocked with the usual method?
[ONE General] bigdogdon:
Solved it by using the Qualcomm tool.
[ONE General] chocoloveMcDonnell:
Help!

How long does it take to unlock the bootloader? I did "fastboot oem unlock" and it is already taking 30 min. There wasn't an error message or something.
[ONE General] Spannaa:
It should be almost instant.

Was there nothing displayed after you issued the fastboot oem unlock command?

What happens if you try fastboot oem device-info and fastboot devices?
[ONE General] chocoloveMcDonnell:
in cmd it said:

okay [ 0.031s]

finished. total time: 0.031s

It's just the phone thats still in the android update screen.

fastboot oem device-info returns < waiting for any device >
[ONE General] Spannaa:
If your phone is in fastboot mode & is connected to your PC and the commands are issued from a cmd window opened from the same folder that contains fastboot.exe:

fastboot devices should give you your device's serial number.

fastboot oem device-info should tell you if your device is unlocked.
[ONE General] chocoloveMcDonnell:
Yea, I know. But it doesn't!

Maybe I didnt' make it clear but, after executing fastboot oem unlock my phone is stuck in a screen like that you get when you update your firmware. (Can't post an expample bc xda won't let me). It is not in fastboot mode.

Before that fastboot devices and fastboot oem device-info returned what they should.

I didn't try to unplug the phone or turn it off, because I do not really know what to do.
[ONE General] Spannaa:
Try fastboot reboot and then, after your phone has rebooted, boot back into fastboot mode and try fastboot oem device-info again.
[ONE General] chocoloveMcDonnell:
The phone is not in fastboot mode! So this doesnt work, its just says < waiting for ay device > Should I just unplug it and turn it off and manually boot into fastboot mode?

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

So a little update: Everything worked fine, my phone is now wiped and booted into android, bootloader is unlocked. It was just that the whole process of unlocking the bootloader took 2,5 hours. I just panicked after half an hour of nothing happening. Thank you anyway ^^