yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Lanchon:
does f2fs work 100% stable for /data?
[ONE Original Android Development] Heisenberg:
Are any of you guys having issues while creating or restoring backups on 2.8.1.0? The damn thing completely freezes up mid way through a backup/restore for me half the time. It's not so much a problem during a backup, more of an annoyance, but having to force reboot the phone halfway through a restore is obviously pretty dangerous.
[ONE Original Android Development] gianton:
Never had such an issue with either the official or unofficial 2.8.1.0. You might have better luck with the unofficial one, give it a try.
[ONE Original Android Development] Vonnegut:
Never had a single problem so far. Maybe you should just download the image again and then flash it again...but only after having checked the MD5 hash.

http://www.nirsoft.net/utils/hash_my_files.html

It's quite easy to check if a downloaded zip file is corrupted...if it doesn't open, it's corrupted (same thing for an installer = .exe)

Whenever i download non-zip file, i always check the MD5 because even just one corrupted bit makes a lot of difference.
[ONE Original Android Development] HaTrED_:
None mate! I'm using a Tasker profile to do that without any issues...
[ONE Original Android Development] Heisenberg:
I always check the md5 of any file I'm going to flash, without fail. This one was fine, otherwise I wouldn't have flashed it. Oh well, I've rolled back to 2.7.1.1 and no issues.

Transmitted via Bacon
[ONE Original Android Development] störte:
Did not had any problems observed. At the moment i am back to ext4 because i like to test some more Lollipop Roms
[ONE Original Android Development] inffy:
I need help.

MY companys exchange wants that the phone is encrypted to get mail, calendar etc synced.

Can I somehow use TWRP with encrypted phone and flash other roms?
[ONE Original Android Development] NYZack:
Yes. The latest TWRP version supports encryption, as do Cyanogenmod 11 nightlies. Whether other ROMs support it might be variable, but my guess is that most do.
[ONE Original Android Development] ptr_hamilton:
But with latest version you mean 2.8.2.0, which isn't available von OPO, right?
[ONE Original Android Development] NYZack:
No, I mean 2.8.1.0.
[ONE Original Android Development] inffy:
OH so the rom has to support encrypted devices too?

So I guess the cm12 builds might not support it then
[ONE Original Android Development] NYZack:
People have been reporting difficulties installing CM12 builds on previously encrypted devices. But I have to believe this will be fixed.
[ONE Original Android Development] inffy:
I guess as there is not even official nightlies that statement is propably true. Will have to wait then for the first official stable version
[ONE Original Android Development] sd65:
Hi Guys,

Just an info when using the app on Lollipop :

I tried to update my version of TWRP par the app. It downloads, check sum and flash the image while in Android "succesfully" (I got this message).

Not so good, because when I rebooted : stuck on logo, no recovery or boot. Fortunately, the fastboot mode worked and I could flash recovery by the boog old way !

The app is not compatible with CM12 ?
[ONE Original Android Development] xanthrax:
First that app isn't recommended to flash, isn't stable

Second, disable from dev options "update cm recovery"

Third, I've posted a flashable zip one page back

Sent from my Darkside of 1+1
[ONE Original Android Development] störte:
If i want to change the filesystem on my phone. i have to choose the partition and the repair /change but if i select internal sd then the selection is canceled upon clicking repair/change.

How do i change my internal to f2fs ?
[ONE Original Android Development] Rycon33:
Your "internal storage" is your /data partition.
[ONE Original Android Development] Vonnegut:
The internal storage is just a folder of the USERDATA (namely the /data/media/0 folder)...it is NOT a partition.

Read this for more info http://teamw.in/DataMedia
[ONE Original Android Development] RobbieL811:
[MENTION=912474]Dees_Troy[/MENTION] I am having some trouble w/ TWRP on SlimLP builds. I am trying to test my new builds, and the only way that I can manage to get the room to flag is if I do a clean flash. It will not dirty flash at all. Is this a known problem? It doesn't seem to be affecting other devices as far as I know. I also have the problem w/ CM builds.

Sent from my 1+1
[ONE Original Android Development] AbhishekS:
Sorry for being a noob but what is bacon?

Is it a codename for the OnePlus One?
[ONE Original Android Development] vicky2131:
yes bro!! its the code name of oneplus one
[ONE Original Android Development] Zorachus:
I am lost on how to update my Recovery ?

I installed TWRP when I first got my OnePlus One, which was version 2.7.x.x at the time, now I want to flash the latest TWRP 2.8.1.0, so I installed the Play Store app, and when I go to " Install TWRP " option, it says Please tap here and choose device, I tap it, and the app crashes every time.
[ONE Original Android Development] wcn:
Download the flashable zip from here by [MENTION=3946657]xanthrax[/MENTION] and flash it in TWRP.
[ONE Original Android Development] Heisenberg:
Just use fastboot to flash it, the app is terrible.

fastboot flash recovery <filename>.img

Transmitted via Bacon
[ONE Original Android Development] Zorachus:
Thank you :cool:
[ONE Original Android Development] Hanny:
Recently, new backups on TWRP, which is stored in /data/media/0/TWRP/Backups, are not showing in /storage/emulated/0/TWRP/Backups and non-root file explorers.

They are only accessible by navigating to /data/media/0 with root explorer.

I am unable to move backups into my PC through MTP since the Backup folder appears to be empty.

Still, TWRP recognises these backups in recovery, but I sense some problem going on.

I totally understand how /data/media works as outlined here, but the current situation is,

only TWRP backups are not showing in /storage/emulated/0 but lies in /data/media/0,

while all my other files, e.g. pictures, downloads, are showing fine in both /data/media/0 and /storage/emulated/0.

Can anybody shed some light on this, or is this supposed to be fixed in a future TWRP update, possibly 2.8.2.0 for bacon?

Edit: Weird, after a few reboots, all my new backups are totally showing up in non-root file managers, i.e. /storage/emulated/0.

Things happened between these reboots were: flashing a new CM12 nightly, rebooted twice, attempted to do a TWRP backup, TWRP froze (1st time in my life), forced power reset, boot into TWRP, delete broken backup, backup again, reboot system, and viola my backups appear in non-root file managers.

I am not sure about whether it is because of the multiple reboots, or the forceful TWRP power reset, that allowed /storage/emulated/0 to correctly reflect what's new in /data/media.

After all, the problem is currently solved for me.
[ONE Original Android Development] Lanchon:
there is a very heavy security issue with world readable backups: any silly game you install could open the backup and get to your browser saved passwords and auth tokens for all you accounts and send it all out into outer space. most tokens never expire, such as the ones for you google accounts.

my intuition tells me that for this reason TWRP writes the backups files under a different user and permission set (probably root) so that the fuse daemon (sdcard.c) can't see them and thus they are not mirroed to the emulated sdcard. this would be by design.

but its not a very good design. CM's recovery places them outside /data/media/0 which is better IMO. some root apps or zip files you flash can carelessly "fix permissions" in /data/media/0 killing this brittle security fix.
[ONE Original Android Development] thebrainkafka:
Deleted
[ONE Original Android Development] ghul21:
Nobody see that title change and we have 2. 8. 3. 0. :)

Sent from my A0001
[ONE Original Android Development] dafonehacker:
2.8.3.0 doesn't work for me, it just reboots after the 'teamwin' screen
[ONE Original Android Development] LeroViten:
Yeah. I was wondering whether anyone here uses Flashify app to push updates to recovery..? Or you prefer fastboot way? ?
[ONE Original Android Development] Artificial_Intelligence:
I'm using Flashify and never had any problems with it :)
[ONE Original Android Development] finistere:
Have you tried

restorecon -FR /data/media/0

on adb shell as root?

Worked for me...

Cheers
[ONE Original Android Development] ghul21:
It works like it should ;) I'm using flashify with no problem
[ONE Original Android Development] Chochiwpg:
Here as well. Downloaded the .img from the TeamWin website and used Flashify to flash. Booted into recovery without issue and it's working as expected. :good:
[ONE Original Android Development] dafonehacker:
Yeah, tried flashify and now it works. Very strange, was probably a bad download or flash.

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] gianton:
Flashable zip for v2.8.3.0, tested and working fine.

https://mega.co.nz/#!kMhEVTaK!gx_t1wd1QwbdnhKTlZI1SrOLD5mX_4mpoVAgyCBobPw
[ONE Original Android Development] CBpbxEcmecmBeH:
Flashify works :)
[ONE Original Android Development] tobitege:
VERY handy, thank you!
[ONE Original Android Development] Lar5:
TWRP 2.8.3.0 is not problem free for me :(

When using v. 2.8.3.0 i can't connect to my PC via ADB.

The phone is just an "Unknown device". (See picture)

Any recommendation on what to do?

If i go back to v. 2.8.1.0 the ADB connection is back.
[ONE Original Android Development] tobitege:
You need to remove the drivers for that device, reboot and let it reinstall those drivers. Also make sure your phone has USB debugging and MTP actually enabled.
[ONE Original Android Development] PresidentMcCain:
USB support for 2.8.3.0 is indeed broken. Getting picked up as "Unknown device" here as well.
[ONE Original Android Development] Lar5:
I know that procedure when Android is started but my problem is when TWRP 2.8.3.0 is started.

Then i loose the connection. No USB debugging or MTP here.

Try rebooting to TWRP 2.8.3.0, connect a USB cable to the PC and see if you can get an ADB connection from a command prompt.

I can't :eek:
[ONE Original Android Development] Emilius:
Maybe we need fresh platform-tools with latest adb and fastboot?
[ONE Original Android Development] eagleeyetom:
Unlikely. I'm using the newest platform tools on Arch and I can't execute any adb commands but adb sideload. Something must be wrong with a recovery.
[ONE Original Android Development] efrai3:
We need new adb binaries as it mentioned in the note of the last changelog :

''Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.''
[ONE Original Android Development] PresidentMcCain:
Not the issue:

C:\>adb version
Android Debug Bridge version 1.0.32

2.8.3.0's USB support is just broken.
[ONE Original Android Development] Emilius:
Interesting, I have very same problem with 2.8.2.0 with Nexus 4. I am back because of it to twrp 2.8.2.1.
[ONE Original Android Development] :
Have just pushed SuperSu via adb. Everything works fine with v2.8.3.0.
[ONE Original Android Development] PresidentMcCain:
#edit: Looks like you have to enable MTP explicitly before ADB starts working. That's really strange. Previous versions didn't require MTP to be enabled first to use ADB.
[ONE Original Android Development] :
via fastboot

Before i installed newest revovery, i updated some tools via sdk manager. Maybe you should check, if you have installed latest updates. Don't know, if this solves your problem.

#edit Saw your edit Mr.notelectedpresident. Good news.
[ONE Original Android Development] PresidentMcCain:
Solved the issue: had to enable MTP in TWRP and then ADB started working immediately.
[ONE Original Android Development] Hanny:
Thanks! Another member in CM12 thread also suggested me this, after a bit of further searching this should fix that little lollipop sdcard bug, when it happens.

I didn't use it though as said in my post after a few reboots the backups automatically showed up themselves, but I have noted it down for future uses.

Hopefully this change in 2.8.3.0 is also related and fixes the issue that I have experienced :)
[ONE Original Android Development] Lar5:
Perfect! It seems to fix the USB connection. Also after restarting TWRP.

Strange behavior. My Nexus S, 7 and 4 with TWRP 2.8.3.0 (1) doesn't need to enable MTP.
[ONE Original Android Development] soralz:
Dunno, but I seems to have some problems with TWRP 2.8.3.0. Now I am reverting back to 2.8.1.0. Like flashing halfway the phone will auto-reboot and I reboot to recovery it will just hang/stuck at blank screen.
[ONE Original Android Development] bombadier:
Same here I am back to 2.8.1.0 first problem was enabling MTP caused a reboot, will wait and see what happens as doubt there is a killer feature that I need
[ONE Original Android Development] thebrainkafka:
A non mega mirror please. THX.
[ONE Original Android Development] gianton:
Here you go

https://docs.google.com/file/d/0B8mXr0tbx63LMXhKYXBwZ2ZnRDQ/edit?usp=docslist_api
[ONE Original Android Development] ek69:
You know you can use an app flashify to install the recovery img file directly too? Doesn't need to be a flashable zip

Sent From Lollipopified Bacon Goodness!
[ONE Original Android Development] Bronyr:
You've got the best gapps, sir! Thank you.
[ONE Original Android Development] mateorod:
Man, stock rom was so buggy I had to come by XDA.

I know [MENTION=2332422]temasek[/MENTION] from old XDA, a trusted name. Thanks for the work, contributors.
[ONE Original Android Development] PresidentMcCain:
I looked more into this. The issue is actually independent of MTP being enabled or disabled: it breaks every time you reboot your phone into recovery from OS while USB cable is still plugged into your PC regardless if MTP is enabled or not.
[ONE Original Android Development] tanveerkhan9:
Cant Update TWRP 2.8.0.0 to 2.8.3 Oneplus one

Cant Update TWRP 2.8.0.0 to 2.8.3 Oneplus one

Only Version is working is 2.8.0.0 but all other version i can't flash by any method , i try by Fastboot flash recovery ...... img , also i try by recovery .zip file , also i try by TWRP Recovery Manager to update but its not working :confused:

only version i can flash is TWRP 2.8.0.0 , i don't understand if i can flash 2.8.0.0 then why i can't other like 2.8.1 or 2.8.3 ? :confused:
[ONE Original Android Development] Heisenberg:
Are you checking the md5 after downloading the file?

Transmitted via Bacon
[ONE Original Android Development] tobitege:
Just in case this is still an issue for you: unmounting data before enabling MTP solved random reboots for me.
[ONE Original Android Development] geowolf1000:
Does latest v support backup/restore modem partition?
[ONE Original Android Development] tobitege:
The one by [MENTION=3814731]katinatez[/MENTION] does (EFS): http://xdaforums.com/oneplus-one/development/unofficial-twrp-2-8-3-0-t2981495
[ONE Original Android Development] dead-I:
I was hoping I could get some help with a problem i ran into this morning. I flashed one of the 5.0 roms, but it lacked some features that i wanted so i decided to restore my kitkat backup. All seemed to be going well but at some point the process froze and i have not been able to get the phone to unlock or reboot back to recovery or bootloader.

The screen is responsive and wakes when i touch it, but the unlock slider doesn't respond and pressing the button combinations has no effect either. I hooked it up to computer and it gives an audible prompt that something is connected but searching for fastboot or adb devices in the sdk brings up nothing. Any help would be appreciated.

This is the screen that its stuck on

[IMG="TWRP screen"][/IMG]
[ONE Original Android Development] DanteGR:
Keep pressing the power button until the phone turns off. I have seen it take up to 1 minute of continuous pressing until it switches off.

Then boot to recovery by power+vol. down.

Oh and update the recovery to 2.8.3.0!
[ONE Original Android Development] dead-I:
Tried holding down the power button, also the pwr + vol up/down and none worked. Is there any way to at least get to the bootloader?

Update: after 5 min of holding down the power button i finally rebooted gonna update my recovery and reinstall the rom, thanks for the help.
[ONE Original Android Development] Paradox:
Help !!! Cant boot into recovery

I am not sure what went wrong. Everything was working fine. I was using temasek's cm12 and twrp 2.8.3.0. with AK Kernel. But when I wanted to install latest AK build, I noticed that I couldn't enter into recovery mode. Phone restarts if I try to boot into recovery, even I cant reset my phone. Please help !! :crying::crying:
[ONE Original Android Development] bombadier:
Can you not get into fastboot ? if you can try reflashing the recovery image
[ONE Original Android Development] giaur:
I can't restore my CM12 (Lollipop backup). Actually, restore was succeded but always after restore full backup (all partitions) wifi does not work on system restored from my backup. I need to reflash rom (without wiping /data) to make it working again.

I'm on TWRP 2.7.1, now updating to 2.8.3 and we'll se if it helps.
[ONE Original Android Development] tobitege:
[MENTION=5411589]giaur[/MENTION]: is your backup with or without EFS/modem? Just wondering if there's a difference.
[ONE Original Android Development] giaur:
I just selected all partitions to backup: /system, /data, /cache and /boot. Then restore the same all partitions. I have no idea if twrp is able to backup efs and modem, it seems not. But I flashed L modem after restore so it should be ok.
[ONE Original Android Development] tobitege:
Yeah, there's an unofficial TWRP bacon version available which allows to backup EFS/modems/persistent. So in your case the modem shouldn't be an issue within TWRP then.

However, depending on the CM-12 build's date, it may have had different binaries in it's build that now do not work nice with your current modem.
[ONE Original Android Development] cam30era:
[MENTION=4877142]tobitege[/MENTION] and [MENTION=5411589]giaur[/MENTION]

See item 10) How to backup and restore your EFS partition here > http://xdaforums.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
[ONE Original Android Development] tiny4579:
I think whether you use compression takes into account the time to backup. I'm at several minutes and I chose compression. Maybe I should skip that since 64 GB is a lot of space.
[ONE Original Android Development] dmarden:
Yeah, I never use compression... surely a factor.
[ONE Original Android Development] dansou901:
I can second that. If I do a backup, it's mostly done within two minutes (without compression)
[ONE Original Android Development] bud77:
Same here, around 80 seconds for a 2Gb backup without compression
[ONE Original Android Development] zephiK:
Is it just me or when rebooting to recovery, it takes a long time to boot to recovery compared to other devices?
[ONE Original Android Development] simo.scorpion:
Same for me

Inviato dal mio OnePlus One
[ONE Original Android Development] dmarden:
Yeah, takes a bit.
[ONE Original Android Development] ThommmF:
That is a big issue for me as well!
[ONE Original Android Development] zephiK:
I wonder if theres any way to speed it up.
[ONE Original Android Development] rodawg71:
TWRP updated

Sent from my One
[ONE Original Android Development] zephiK:
http://techerrata.com/file/twrp2/bacon/openrecovery-twrp-2.7.1.1-bacon.img

Edit: Seems like the phone boots faster into recovery, still not as fast as previous devices but a improvement (I think)
[ONE Original Android Development] simo.scorpion:
[MENTION=912474]Dees_Troy[/MENTION] can you upload also the zip file ? just for seplicity and velocity to install for the people who have already one custom recovery
[ONE Original Android Development] zephiK:
Download flashify from the play store and you can flash the img file directly from the app. Don't even need to reboot to flash the updated recovery. Root required.
[ONE Original Android Development] simo.scorpion:
flashify work fine with opo ?
[ONE Original Android Development] zephiK:
Yeah I flashed it using Flashify, no problems. I'm on my PC now, https://play.google.com/store/apps/details?id=com.cgollner.flashify is the link.
[ONE Original Android Development] playya:
After going here and reading I checked out this page for those of you that dont want to use img. Its another alternative to flashify. Check it out if you like its straight from TWRP
[ONE Original Android Development] Mikey:
2.7.1.1-Bacon Recovery Flashable zip

http://xdaforums.com/oneplus-one/development/recovery-unofficial-twrp-2-7-1-0-t2815247
[ONE Original Android Development] dansou901:
Just an FYI... The backup/restore of modem partition is seriuosly broken. When I used it to just restore modemst1, my modem stopped working. I fixed it with flashing modem via fastboot, flashing it via dd did not help.
[ONE Original Android Development] PhaseBurn:
TWRP on the Bacon isn't able to mount /data or perform any functions that require it when Android's system encryption is used.

Error is as follows:

I did some digging around, and discovered that a few days ago, the location of the crypto folder has changed on the device. You can see more details here.

Basically it looks like a workaround for a factory/build issue. Either way, the encryption folder is no longer in the footer of userdata, but in its own reserved partition, located at /dev/block/platform/msm_sdcc.1/by-name/reserve4

I'd be willing to try any TWRP test builds with that change in them, as it doesn't seem that too many people encrypt their devices.
[ONE Original Android Development] DuckMcQUack:
So basically backing up efs partition using the recovery is just useless??

Is it a problem of the last version or is it shared with 2.7.1.0 too?

Thanks for the infos.
[ONE Original Android Development] giaur:
Ok but it's not what we are talking about. TWRP does not support it, I know how to backup my efs and modem.

I tested latest TWRP by performing steps:

- make backup all partitions

- wipe all partitions

- restore with TWRP.

Then after reboot system wifi seems to be ok. But I'm not coming from KitKat this time.

P.S. I can see new option - now I can backup to OTG. But how to restore from OTG? I can't choose my backup location?
[ONE Original Android Development] cam30era:
[MENTION=5411589]giaur[/MENTION]

OK. I understood that you were talking about TWRP not supporting it. Just thought I'd offer that. Thanks for the feedback.
[ONE Original Android Development] tobitege:
It's on internal storage, "ubs-otg" folder or similar.
[ONE Original Android Development] giaur:
It's not clear for me. How to restore from otg? Should I mount my otg and I will see backup located on otg on backups list? I can't browse directories to locate my backup (I can't see option for that).
[ONE Original Android Development] tobitege:
Oh, misunderstood you. I think choose storage and USB-OTG should automatically show up in addition to internal storage. In File Manager you can access it via the ubs-otg folder in internal storage. I'll re-check it myself now, will get back to you in a few...

So, I'm actually not using the official version, but [MENTION=3814731]katinatez[/MENTION]'s version. And with that UBS-OTG should automatically show up in storage selection dialog.
[ONE Original Android Development] giaur:
I did not actually tried, I'm just asking how does it work