Maybe, not sure
[RECOVERY][oneplus3] Unofficial TWRP 3.0.3-0 touch recovery for OnePlus 3
- Thread starter dianlujitao
- Start date
Thanks for your answer.
Ok, I just saw I was using official and not yours .. So sorry for annoying.
OP in official states ext4 is still better than F2FS and F2FS is only for benchmarks, what's your opinion about it ?
different answers in different aspects, I say IDK
Hi, I am on last official CM13.1 (20161106) and modified TWRP (3.0.2-1.28).
I would like to test offical OxygenOS v4 (Marsh) and Unoffical LAOS14.1 (from you).
Is it possible with your modified TWRP (3.0.3-0) to switch within CM13/CM14/OxygenOS without any problems?
Like there was screenlock pattern + decryption problems after resoring Nandroid backup etc... @dianlujitao
I would like to test offical OxygenOS v4 (Marsh) and Unoffical LAOS14.1 (from you).
Is it possible with your modified TWRP (3.0.3-0) to switch within CM13/CM14/OxygenOS without any problems?
Like there was screenlock pattern + decryption problems after resoring Nandroid backup etc... @dianlujitao
Last edited:
You can't downgrade the database
@dianlujito you mean lockscreen.db? If yes, removing before flashing should result with no problems with flashing between those?
Can anyone please give me music.Zip file for op3 ... I lost my music app while making music as a system app by titanium backup ... Please
if i change twrp, when reboot, the new twrp remain in the initial screen and then reboots
unable to restore backups..
i m unable to restore backups made by this recovery..and if i flash the rom and then restore data my pattern lock is not opening..i m very frustrated please help
i m unable to restore backups made by this recovery..and if i flash the rom and then restore data my pattern lock is not opening..i m very frustrated please help
It seems AFH is unable to find any mirrors. Would anyone happen to have a mega, dropbox, drive, etc link?
I downloaded your TWRP, then used it to flash lineage-14.1-20170125-nightly-oneplus3-signed.zip, but it stucked after showing two lines of "detected filesystem ext4 for /dev/block/bootdevice/by-name/system", then I rebooted to recovery again and change the /system to F2FS, unfortunately, this time it showed "detected filesystem ext4 for /dev/block/bootdevice/by-name/system" after the line "detected filesystem F2FS for /dev/block/bootdevice/by-name/"
So weird...
So weird...
Hello,
I need your help.
My TWRP ask me in boot recovery a password for mount decrypt data :/
I can't use recovery
I need your help.
My TWRP ask me in boot recovery a password for mount decrypt data :/
I can't use recovery
Happened to me with this version... Dump it. Get official 3.0.4 unreleased (from the thread) or Blu spark v15.Hello,
I need your help.
My TWRP ask me in boot recovery a password for mount decrypt data :/
I can't use recovery
@dianlujitao Something weird happened for me while testing some unrelated issues I was having with recent builds of open gapps.
I'm usually not prompted to set encryption during setup, but when installing official lineage from 01-31 along with 02-02 gapps and the recent EX kernel update(2.0), I was. On entering TWRP, however, it failed to decrypt data!
I tried to test this without EX kernel installed, but I was unable to get it to prompt me to encrypt at setup again.
I know you can't support a custom kernel, but EX Kernel was just rebased on the latest Lineage kernel yesterday, and I remember you saying something about a new kernel in the lineage thread.
I was just wondering if you might know what the issue is, I thought perhaps the new lineage kernel is incompatible with the custom kernel you put in this TWRP.
Thanks for all your work on TWRP and Lineage, it's all very confusing right now and I appreciate you keeping our devices working! = )
I'm usually not prompted to set encryption during setup, but when installing official lineage from 01-31 along with 02-02 gapps and the recent EX kernel update(2.0), I was. On entering TWRP, however, it failed to decrypt data!
I tried to test this without EX kernel installed, but I was unable to get it to prompt me to encrypt at setup again.
I know you can't support a custom kernel, but EX Kernel was just rebased on the latest Lineage kernel yesterday, and I remember you saying something about a new kernel in the lineage thread.
I was just wondering if you might know what the issue is, I thought perhaps the new lineage kernel is incompatible with the custom kernel you put in this TWRP.
Thanks for all your work on TWRP and Lineage, it's all very confusing right now and I appreciate you keeping our devices working! = )
I haaate to post issues on xda but I'm desperate. I was just enjoying how my phone has been running for the past 3 months and I decided to make a twrp backup. Looked like all went well. I went to boot afterwards and it took forever, and gave me system force close issue. I tried restoring my backup and it looks like it's a permanant issue on that backup. I can restore to a backup from months ago but I get tons of crashes and google apps just don't work at all. I updated from twrp 3.0.2.0 to 3.0.3.0 and now I can see it tells me "E:Unable to find file system (first period)." and I've been searching through forums for hours, no luck. I really didn't wanna lose my perfect setup. I was running blissrom 6.3 (marshmallow based) and hadn't had any previous issues. I'm willing to do anything to get back my phone just how it was yesterday. If anyone has absolutely any experience it would be so greatly appreciated. Thank you!!!!
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone