yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] playya:
I would leave 2.8 alone completely until the bugs are worked out and use 2.7. Or at least do not try and restore with 2.8
[ONE Original Android Development] nikku_hot123:
Please give the script to restore too.
[ONE Original Android Development] Vonnegut:
I don't think so, ppl flash everything even when not needed.

Anyway all of those partition are quite straightforward to flash in fastboot mode. Each name correspond to the name of the partition it belongs to. Let's say you want to flash the reserve4.bak for a very good reason (for example you've flashed the ColorOS beta and you've found out that it changes that block...which indeed does!)

fastboot flash reserve2 reserve2.bak

And so on...
[ONE Original Android Development] Ok_Kaleidoscope5109:
Is there a need to backup every other partition or is the EFS script that backs up Persist, Modemst1, and Modemst2 sufficient?
[ONE Original Android Development] tr1gg3r.man:
I've done several restores from backups with 2.8.0.1 and haven't run into any issues thus far...

Sent from my bacon!
[ONE Original Android Development] PaoloMix09:
I second this.

Sent from TOCINO on VanirAOSP
[ONE Original Android Development] Vonnegut:
Judging by the most occurred problem so far, one could only backup the persist.

My point is Why shouldn't have a full backup even if i won't ever need it?

I don't have to pay for it. it takes less than one minute. (Almost) whatever will happen to my OPO, i'll be able to solve that.

Let's say i flash a ROM thinking that it would change only the usual boot and system partition. Let's say that later i find out that ROM changed many other partition too. In this case i'd be able to revert whatever change has been made.

That's what exactly happen to ppl flashing the ColorOS.. The average user doesn't know that ROM flashes much more than the boot and the system...
[ONE Original Android Development] playya:
Thats good to hear. There is a problem somewhere though and the most consistent factor was 2.8.0.1. Hopefully we can all figure out exactly whats triggering the destruction of some users efs partition
[ONE Original Android Development] PaoloMix09:
Idk but this is kinda scary. I hope I don't get any problems; so far done 3 restores without problems on 2.8.0.1

Sent from TOCINO on VanirAOSP
[ONE Original Android Development] playya:
Official or unofficial
[ONE Original Android Development] PaoloMix09:
How do I know if it's official or unofficial lol. I clicked on the mirror links from first page and downloaded the 2.8.0.1 one.

Sent from TOCINO on VanirAOSP
[ONE Original Android Development] playya:
Lol the thread header would generally tell you but if you got it from here then question answered
[ONE Original Android Development] DanteGR:
Hello all.

New to the OPO (just have it for a week or so) and I unlocked and rooted it. Took a backup of the stock rom.

Flashed 2 ROMs without problems so far but when I tried to flash a third one (exactly the same way as I did with the other two, by wiping system, data, cache and dalvik) it fails and says that it can't mount data and storage.

Also, i cannot restore my nandroid cause it doesn't show up on the "restore" menu. The thing is that it shows up on the TWRP file manager fine though.

So basically now I'm without an OS and stuck. Running TWRP 2.8.0.1.

I did some searching on Google and XDA but couldn't come up with something.

Anyone's help would be greatly appreciated.

Thanks in advance :)
[ONE Original Android Development] D.vink:
http://xdaforums.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061

Maybe this will help.
[ONE Original Android Development] DanteGR:
Thanks but I just found the solution and it was nothing this complicated.

Just had to do a factory reset lol :D

Thanks anyways my friend :)
[ONE Original Android Development] Brockg:
Hey guys I flashed TWRP both through the toolkit and in fastboot...however when i boot into recover it still takes me to the cyanogen stock recovery interface...any ideas of what's going on? My device has both unlocked bootloader(verified with fastboot device info) and is rooted.

I also installed TWRP through the TWRP manager app to no avail.

When flashing recovery through toolkit during the unlock/recovery/root process it brought me into the TWRP but that was the only time.

Thoughts?
[ONE Original Android Development] PaoloMix09:
You should just try to flash it through fastboot, that's how I always did it and no problems.

As of now I decided to use a different recovery since I've heard many people having issues when restoring while using TWRP recovery, things like losing IMEI and other nasty things.

Also, I'd recommend trying to learn to do things manually. Toolkits can led to issues sometimes. You'll be much better off by knowing how to do everything manually.

Sent from TOCINO on VanirAOSP
[ONE Original Android Development] Brockg:
Hey Paolo sorry if my original question wasn't clear...i flashed the recovery both methods(toolkit and then through fastboot)
[ONE Original Android Development] PaoloMix09:
Whooops, did not read correctly. Anyway, you sure you typed the right command? When flashing through fastboot did you rename the file to "recovery.img" to make life easier? Idk... If it still doesn't work you could try flashing a different recovery and see if that works.
[ONE Original Android Development] Brockg:
Yup, did all that. Thanks for the help and time. I'll try a different recovery; any one you recommend?
[ONE Original Android Development] PaoloMix09:
I'm using Philz at the moment, everything working just fine. I do miss TWRP, I just don't wanna risk having problems when restoring backups.
[ONE Original Android Development] elrey311:
I'm using Philz for the same reason, just to be on the safe side.
[ONE Original Android Development] dr.m0x:
Philz and twrp 2.7.0.1 have both proven reliable for me. 2.8.0.1 has killed my phone twice and I wouldn't touch it again.

Mmm bacon
[ONE Original Android Development] elrey311:
Twrp 2.7.0.1 left me without a imei# and in a mess. I will only use Philz and the bad thing is I like twrp, but don't want to go thru that again.
[ONE Original Android Development] dr.m0x:
Oh that sucks, I might stick with philz for now then. Unfortunately philz is done with the project and it's no longer being updated so might stop working at some point. Probably around when we get Android L I suspect.

Mmm bacon
[ONE Original Android Development] Natakranta:
Did you go to developer options and untick: restore recovery after update, or something like this, I don't recall the exact name? If it is ticked, during booting CM11S will flash stock CM recovery over your freshly flashed custom recovery.

Untick it. Boot to bootloader. Fastboot flash recovery of your choice. Reboot to system. Reboot to recovery. Your custom recovery should still be there.

I had zero problems with TWRP 2.7.1.1. Now I use TWRP 2.8.0.1. I did few backups and restores, a lot of flashing clean and dirty. No problems so far. I need to mention I don't jump from one ROM to another. Especially colouros can make a trouble. I stick with Slim and update on weekly bases or more frequently if some testing is needed to be done for developers.

For both TWRP I used a theme xda thread end link to download. For OnePlus you need 1080p resolution theme. I personally use materialised dark theme. Materialised themes are for TWRP 2.8.0.1 only. Older themes are for TWRP 2.7.x.x.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Original Android Development] dmarden:
I mess around a lot, so I've backed up and restored a heap of times via the official releast of 2.8.0.1. No issues here, knock on wood.
[ONE Original Android Development] playya:
I really wonder what it is and why it is triggered for some and not others. I have backed up everything I need too just in case but I too may be jumping ship back to CWM
[ONE Original Android Development] dmarden:
Yeah, I am not sure... I don't do anything with encryption, but I gather that most people don't either. I also only restore backups made on version X via that same version. *shrug*
[ONE Original Android Development] Notor1ouS-:
so, is twrp that buggy atm that it bricks phones?
[ONE Original Android Development] dmarden:
Not entirely sure what you mean... the short answer for literally

bricking

phones, no. Have some people had trouble? Yes. Have some people had no trouble? Yes.
[ONE Original Android Development] Brockg:
Man I went into dev options and I'm not seeing that option... I even flashed the philz recovery yet when I boot into recovery I still get the stock recovery :mad:
[ONE Original Android Development] istampal:
twrp 2.8.0.1

I use TWRP 2.8.0.1 and had few issues. As i am often cahnging ROM-s i lost EFS (modem).

It is possible to back up EFS with TWRP 2.7.0.1. then it will show up in TWRP 2.8.0.1 . Now after

flashing new ROM-s i can always reflash EFS using 2.8.0.1 version if WIFI or modem connection

does not function. Also had few times to reflash TWRP 2.8.0.1 via fastboot because of freezing screen

or touch completly wrong you press one command it starts other.
[ONE Original Android Development] playya:
the unofficial one backs up efs

---------- Post added at 10:34 AM ---------- Previous post was at 10:32 AM ----------

you went into developer options and did not see Update CM recovery option?
[ONE Original Android Development] appro77:
I'm using 2.7.0.1. Is there no support for USG OTG?
[ONE Original Android Development] elrey311:
Take a look at this thread: http://xdaforums.com/oneplus-one/development/recovery-unofficial-twrp-2-7-1-0-t2815247
[ONE Original Android Development] danyvw:
Untick Update CM Recovery in Developer

Sent from my Oneplus One
[ONE Original Android Development] shawn0223:
can't make a backup

Any reason I'm getting a million errors when trying to backup on 2.8.0.1

The xda app won't lemme upload a pic so I put the screenshot in my drop box

https://www.dropbox.com/s/2nq1mbh7c0zclpb/Screenshot_2014-10-10-11-44-53.png?dl=0
[ONE Original Android Development] MrMarkEdward:
What are you trying to backup to otg or phone?
[ONE Original Android Development] shawn0223:
Just a standard nandroid before flipping to another Rom
[ONE Original Android Development] MrMarkEdward:
If you are using the official try using the unofficial twrp
[ONE Original Android Development] shawn0223:
Still no go. Giving the errors. Even tried 2.7.1.0

https://www.dropbox.com/s/nuy4kz6at1s5trd/Screenshot_2014-10-10-13-33-14.png?dl=0
[ONE Original Android Development] MrMarkEdward:
Have you tried backingup without the data? From picture I see the error is on the data.

If that is case when you install new rom do an advanced wipe and include data in the wipe.
[ONE Original Android Development] shawn0223:
It completes but still shows the errors

https://www.dropbox.com/s/4lhwpgyd2yfeax1/Screenshot_2014-10-10-14-01-20.png?dl=0
[ONE Original Android Development] MrMarkEdward:
Ok go back into twrp choose wipe then look for file system choose it choose data the press repair/change file system

then try another backup with data
[ONE Original Android Development] shawn0223:
It wants me to choose either repair or cjange file system. Repair right?

Edit: repair completes but gives the same errors. Backup failed again
[ONE Original Android Development] MrMarkEdward:
Do you have a backup that didnt give you issues or is this first backup period?
[ONE Original Android Development] shawn0223:
Last backup I made was 9/27. No issues, although I think that was through the online nandroid.
[ONE Original Android Development] MrMarkEdward:
If you do have a good backup I would just go ahead and install new rom you want and wipe everything except the internal sd

after you rebbot and set it up after first reboot make sure to backup twrp folder to computer or whatever you wanna keep to desktop/laptop and then wipe internal sd rebbot then copy what u saved to phone. Then try to backup.
[ONE Original Android Development] shawn0223:
man that would take for f*cking ever lol. I got like half of the storage full of stuff lol. this is so stupid lol. i just wanna make a damn backup lol. i guess ill try cwm or philz before i fully wipe the b*tch lol. unless anyone else has any other ideas?

---------- Post added at 03:03 PM ---------- Previous post was at 03:00 PM ----------

[MENTION=4764401]daorderdillon[/MENTION] you helped me with a twrp issue in the past. any chance you've seen this issue im having now? linked the post below

http://xdaforums.com/showpost.php?p=55944259&postcount=368
[ONE Original Android Development] manorton:
Just tried SuperSU and it does NOT work yet.

Installed from Play store.

EDIT: Just found this link and will try the update SuperSU

http://www.ibtimes.co.uk/how-root-oneplus-one-install-twrp-recovery-1450708
[ONE Original Android Development] Mnt-XDA:
:good::good::good:
[ONE Original Android Development] Cogra147:
Don't encrypt this phone with TWRP installed. Can't remove encryption or unlock bootloader. If anyone has any ideas they would be much appreciated.
[ONE Original Android Development] Gwanatu:
So this morning I received an incremental update from CM and now it appears that TWRP won't flash or boot on the phone. Rebooting to bootloader only brings me to the stock CM bootloader, not TWRP, no matter what I try. I had it working just fine before the update. Any ideas?
[ONE Original Android Development] Gwanatu:
As a followup to the previous post I flashed back to the previous R update using these commands:

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

The only thing I did NOT flash was user data since that overrides any data on that partition. I lost nothing and am now running in TWRP and have root.
[ONE Original Android Development] JinRoh3:
C:\adb>fastboot oem unlock
...
OKAY [ 0.002s]
finished. total time: 0.002s

C:\adb>fastboot flash recovery openrecovery-twrp-2.7.1.0-bacon.img
target reported max download size of 536870912 bytes
sending 'recovery' (15294 KB)...
OKAY [ 0.499s]
writing 'recovery'...
OKAY [ 0.208s]
finished. total time: 0.707s

C:\adb>fastboot reboot
rebooting...

finished. total time: 0.004s

C:\adb>adb reboot recovery

I can't seem to be able to install TWRP on my device... As you can see it appears to have been installed properly, however when I boot into recovery (from any method) it still shows CYANOGEN SIMPLE RECOVERY...

I'm going crazy and I've tried redoing it miltiple times. Any hints?
[ONE Original Android Development] chrmhoffmann:
I had same problem. I tried 2.7.0.0 and that worked. No clue what goes wrong with the 2.7.1.0 version.

Chris
[ONE Original Android Development] ToRvaLDs:
Disable CM Recovery Protection - On your phone go to Settings > Developer options. Then disable the 'Update recovery with system updates' option.
[ONE Original Android Development] jcubed:
Thank you for your very helpful post. I was having the same issue since I've never seen that option before. I feel like that should be mentioned in the OP.
[ONE Original Android Development] elios93:
I've tried to mount a USB drive bit seems that the otg doesn't work. It should appear in mount settings right? Anyone has the same problem?
[ONE Original Android Development] Expliciate:
Is there a reason why half the time when I attempt to enter recovery none of the partitions mount and shows all directories being blank under install, while the other half, it works perfectly normally?
[ONE Original Android Development] chrmhoffmann:
Encrypted data partitions are not mounting as reported over irc.

Chris
[ONE Original Android Development] cybertlc:
I noticed TWRP does charge the OnePlus, but verrrrrrryyyyyyyyyyyyy slowly. Any reason behind this?
[ONE Original Android Development] ilpolpi65:
Don't give fastboot reboot after that u flashed twrp but boot in recovery immediately:

http://wiki.cyanogenmod.org/w/Install_CM_for_bacon

Point 7
[ONE Original Android Development] Klarooo:
Jep, same problem here...

When this happens and I reboot the phone some apps like WhatsApp or Chrome have problems to load the data.. Don't know why..
[ONE Original Android Development] MontAlbert:
Same problem here too. Wasn't sure if it was the ROM I was using or not. It didn't happen with the cm nightlies but when I switched to mahdi it started happening. After that it happened on a previously tested cm nightly.

When loaded into twrp the data partition is basically considered to be not there. It says it is 0mb and won't mount it. .

Is it possible that TWRP doesn't recognise the correct userdata.img and somehow this screws it up?

https://github.com/CyanogenMod/android_device_oneplus_bacon/blob/cm-11.0/BoardConfig.mk#L39

" unless roms support the "BOARD_USERDATAEXTRAIMAGE_PARTITION_SIZE" tuneable

it uses the*BOARD_USERDATAIMAGE_PARTITION_SIZ "
[ONE Original Android Development] jrior001:
Guys I've issued pull requests on commits to TWRP that fix usb OTG mounting in recovery and hopefully fix up mounting encrypted /data(may require a FULL data wipe before this will work properly again).
[ONE Original Android Development] dansou901:
Same problem here too...
[ONE Original Android Development] inffy:
Why is this so damn slow to backup? Taking ages to do a nandroid backup
[ONE Original Android Development] dmarden:
Not sure how slow you mean, but I am using the version of TWRP here: http://xdaforums.com/showpost.php?p=54157796&postcount=10

and my 2.5GB backup took 89 seconds.
[ONE Original Android Development] MrMarkEdward:
Try without wiping internal.
[ONE Original Android Development] sheikhramnuj:
I'm using this latest twrp 2.8.0.1 and having no issues or problems at all, from backup to restore or flashing another roms. Everything works fine :)
[ONE Original Android Development] shawn0223:
still no go. wiped everything but internal and it was giving me the error on that too. even tried flashing another rom and it would fail on that too.

just restored back to my old backup. it says restore completed but still gave those errors. i think its booting. taking its sweet a$$ time though
[ONE Original Android Development] MrMarkEdward:
Well my guess would be to go back to completely pure stock via adb then re install recovery of your choice. But as I said before backup everything to your desktop/laptop anything you wanna keep. Sorry I couldn't be more helpful.
[ONE Original Android Development] shawn0223:
Thats what im doing. I cant find the command to flash the whole fastboot zip image i dpwnloaded. Do u know the fastboot command?

I looked in the guide to return to stock but it just says extract and flash. I dont wanna put a wrong command and mess up more lol
[ONE Original Android Development] MrMarkEdward:
I would follow the guide. And I sure don't.

---------- Post added at 04:54 PM ---------- Previous post was at 04:51 PM ----------

8. How To Flash The XNPH33R Fastboot Images Scroll down till you find it.
[ONE Original Android Development] MrMarkEdward:
[MENTION=4244537]shawn0223[/MENTION] did u get it fixed what did u end up doing.
[ONE Original Android Development] elrey311:
Here you go:

fastboot flash boot boot.img

fastboot flash userdata userdata.img

fastboot flash system system.img

fastboot flash recovery recovery.img

fastboot flash cache cache.img

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
[ONE Original Android Development] drbest:
THE recovery for my Oneplus One

Nice, until now no problems with this recovery. :good:

Thanks for your work and and good luck for the future.

Greetings
[ONE Original Android Development] noobtoob:
Restore w/ ART enabled nandroid

Well, I was searching this thread for ART restoring issues but couldn't find anything related to what happened to me. I just got my OPO last week, but have discovered that restoring a nandroid that has ART enabled does cause issues, mainly never fully wiping the cache. Just wanted to post that I tried several methods and the only way I was able to restore was to wipe everything and then restore the partial nandroid by first unchecking the "restore cache" checkbox. Only then was I able to get a proper re-installation. Hope this helps anyone else that may have the same restore issues as I was having.

Edit: forgot to mention version 2.8.0.1
[ONE Original Android Development] -ION-:
Bricked my damn phone with this recovery when I flashed ParanoidAndroid. Had to use the following command in the twrp terminal:

make_ext4fs /dev/block/mmcblk0p15

Source: http://xdaforums.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061

I'm heading back to PhilZ.
[ONE Original Android Development] störte:
Wow that sucks. I never had problems with TWRP . In Philz i had the Time problem which i hate.
[ONE Original Android Development] PaoloMix09:
Same here. And yes, stupid time... was annoying.
[ONE Original Android Development] gps3dx:
You'll need to reboot windows 8.1 into a special mode that allows installation of unsigned drivers. Do that, and then you'll be able to install the ADB drivers correctly.

Plus, Look that my post HERE because on win 8.1 MS changed the way the OS manage drivers - so some small registry work may be needed ( for win 8 ( prior to the 1 update ) that is not the case ):angel:

---------- Post added at 01:17 PM ---------- Previous post was at 01:10 PM ----------

Hi,

I hope you ppl can help me on this:

Using v2.8.0.1 or v2.8.0.0 ( cuz I want F2FS support ) When I enable MTP, I see it on my windows explorer as expected ( using win 8.1 x64 )

A problem arises when I try to copy files from my PC to OPO:

When I copy a compressed file(like zip), the OPO extract them automaticlly

Sometimes I get a "Cannot copy" message when I copy some files.

I cannot create folders on the OPO using Win explorer

That problem happens when /data is formatted as 4ext.

when it formatted as F2FS - Win does NOT sees MTP at all !

What should I do ?

Who cause this weird behavior? :eek:

Is it twrp, drivers or win ? :confused:
[ONE Original Android Development] MrMarkEdward:
It wasnt TWRPS fault:

Here's An Easy Fix For A OnePlus One Sudden Death Bug That Results In Neverending Boot Loops
[ONE Original Android Development] PaoloMix09:
If we never had any of those problems is it recommended to still do that? And how do I run it? So I go to TWRP and where do I enter the command at? I'm kinda lost on that one :eek:
[ONE Original Android Development] MrMarkEdward:
You can flash aromafm enable TWRP to use Aromafm. Then when in TWRP select file manager swipe to start aromafm then menu then select Open Console.
[ONE Original Android Development] elrey311:
How do you open up a terminal in twrp? I see the option in the recovery but don't know how to get the terminal to appear.
[ONE Original Android Development] Notor1ouS-:
so should i apply that fix, even if i dont have that bug yet?
[ONE Original Android Development] Vonnegut:
Just flash this .zip in recovery and you'll be fine http://www.mediafire.com/download/77d5w7yyydkxp7e/Persist.zip

---------- Post added at 07:19 PM ---------- Previous post was at 07:13 PM ----------

1) ????

2) Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.

Source: http://teamw.in/project/twrp2

3) MTP can be buggy

---------- Post added at 07:22 PM ---------- Previous post was at 07:19 PM ----------

That can happen with Philz too.

Anyway, each and every Team is updating their ROM with this --> http://xdaforums.com/showpost.php?p=56086489&postcount=787

So it won't happen again anymore...