yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] paiktaras:
Why not have corrected it?

They have justified it ?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I've raised an issue for it with the TWRP team. It's up to them, not the maintainer, to fix.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
[MENTION=5091734]dianlujitao[/MENTION] and everybody else.

I reported the problem of having two different download links for TWRP for the OnePlus 3 and 3T, especially given that the same version name showed up but had different images.

As a result, the TWRP team have removed the old oneplus3t pages.

The only device page for both phones is now https://twrp.me/oneplus/oneplusthree.html and the only download page is https://dl.twrp.me/oneplus3/

This should avoid the confusion as to which version of TWRP is the latest official one (3.2.1-0).
[OnePlus 3 & 3T Cross Device Development] thomasnsr:
Thank you very much Sir for the kind action and fast reminder here. You save my day:highfive:
[OnePlus 3 & 3T Cross Device Development] wilriker:
I have a NON-T device, so I wouldn't even consider using the (old) version for T.

I also verified my downloaded versions md5sum (twice) and reflashed recovery. Everything to no avail.

Not sure if this has something to do with it: a couple of weeks back (and after flashing the latest TWRP through TWRP - I usually use this way since it became available) I switched my device locking from pattern to PIN. Even though I selected to also use the PIN to protect device at boot it never actually changed that part and I had to still use the very same pattern as before. Since I did not want to ways of unlocking the device I switched back to pattern (again selecting to use this method to protect at boot).

I have not used recovery since, so this might be connected.

EDIT: I have not yet tried blu_spark and will do so now.

EDIT2: blu_spark TWRP works fine. Now why does official TWRP which is even newer not? Is there anything I can do to help fix this issue?
[OnePlus 3 & 3T Cross Device Development] vurtomatic:
Is there a way to avoid or fix the issue where 3.2.1-0 asks for a PIN when previous versions didn't?

I just clean flashed my phone to an Oreo ROM (AICP) using 3.1.1-2 and I've read 3.2.1-0 is better suited if flashing Oreo ROMS.

So I'm wondering if I should try 3.2.1-0 again and if there was a fix for the PIN issue.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Glad you sorted it out.

Maybe [MENTION=5091734]dianlujitao[/MENTION] and [MENTION=3873953]eng.stk[/MENTION] could work together to make sure the official TWRP version has all the fixes that are in the Blu Spark version.

---------- Post added at 07:24 AM ---------- Previous post was at 07:21 AM ----------

Try using Blu Spark 8.61.
[OnePlus 3 & 3T Cross Device Development] vurtomatic:
Thank you, that's the impression I'm getting from the last few posts after my question!

[EDIT: Back to report blu spark 8.6.1 works fine.]
[OnePlus 3 & 3T Cross Device Development] tathagatab:
FWIW, I was happy with official twrp 3.2.1-0 version 1. When v2 came out on February 01, 2018, I upgraded and faced the password/pattern issue. My OP3 doesn't even have a boot lock, so I couldn't enter anything, and twrp refused to read the data partition. I downgraded to v1, and have been happy ever since.
[OnePlus 3 & 3T Cross Device Development] wilriker:
Funny (more or less) is that after installing Oreo I had to switch back to official TWRP as the blu_spark version would then have issues with mounting /data after successful decryption.
[OnePlus 3 & 3T Cross Device Development] :
This should be noted on the first page though... I see a repeated question..

This official TWRP has bugs with custom N build and whatever f2fs problem that cause pin/data decrypt. If you still want to use this official follow this gentlemen finding

https://xdaforums.com/showpost.php?p=75500069&postcount=49

Either way if you don't want any headache, use the outdated TWRP in blu_spark thread, though it has compatibilty issues with some O custom roms.

And i encourage anybody here with experience and some free time to build his own unofficial of TWRP outside this thread. You'll be the savior for OP3 community since engstk has already full in his hand and dianjulitao can't prety much do anything because of the "official" manner.
[OnePlus 3 & 3T Cross Device Development] vurtomatic:
Does this mean if we're on O, the official TWRP should work?

I ran into the PIN problem while on N and I've flashed to O since.

I wasn't aware blu_spark's TWRP has compatibility issues with some O custom roms.
[OnePlus 3 & 3T Cross Device Development] Uumas:
Official works fine on Oreo
[OnePlus 3 & 3T Cross Device Development] tathagatab:
Only the older version of 3.2.1-0, in my experience. The one that was replaced on February 01. The newer version can't decrypt the data partition on Oreo.
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
I never had a single problem with the latest TWRP build from this thread, I however flashed to OOS 5 with the blu_spark TWRP available at this time and then updated to this version of TWRP - I could imagine that the key here is to first upgrade firmware to OOS 5 before you update the recovery...

I flash lots of different stuff and I'm quite sure I would have seen issue by now, flashing this while being already on OOS Oreo works flawlessly..

I also don't understand why people go back to outdated versions of TWRP, I mean backup internal storage and if decryption problems occur format /data, after this all should be fine - it wouldn't be a solution for me to head back to some old TWRP, especially when damaged was done already... That's just my opinion of course :)
[OnePlus 3 & 3T Cross Device Development] counterfeit187:
The only problem is that it can't format from ext4 to f2fs
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
True that :) but fortunately [MENTION=2911853]BillGoss[/MENTION] did report it via the right channels and a fix should be on the way...
[OnePlus 3 & 3T Cross Device Development] bian_ki:
Is it no longer necessary to install "dm-verity and forced encryption disabler zip" (no-verify-opt-encrypt.zip) after TWRP installation as I found in another online guide (cannot post URLs yet)?

I flashed TWRP as decribed there but I wonder if this zip was unnecessary since it's a HOWTO from 2016.

This part scared me:
[OnePlus 3 & 3T Cross Device Development] Uumas:
It's required if you don't root your phone or install a custom rom
[OnePlus 3 & 3T Cross Device Development] suolrihm:
If you want to keep OOS but have TWRP you need to flash the dm-verity fix, Custom Kernel or Magisk otherwise dm-verity is triggered
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Your better off looking at the procedures in the following thread which is current for Oreo.

https://xdaforums.com/oneplus-3t/ho...y-force-encryption-op3t-t3688748/post74155053
[OnePlus 3 & 3T Cross Device Development] anyone23:
Am I the only one having problems with decrypting Data in TWRP? I have secured LineageOS 15.1 with a passphrase and everything has worked fine the last few weeks however now I can't upgrade from last weeks build to this weeks build as TWRP complains that the password is incorrect.

Does anyone else have this issue? I tried it with the latest official TWRP and also blue_spark.
[OnePlus 3 & 3T Cross Device Development] theCroh:
Did you by any chance install OB32 or OB33? They both caused decrypting to fail on my device. I'm on RR, though.
[OnePlus 3 & 3T Cross Device Development] anyone23:
Thx, that did the trick! :)

I was able to sideload OB31 FW with adb and TWRP can decrypt data again.

So what could be the reason for this? In the LOS 15.1 thread a lot of people are using OB32 or OB33 without issues. Could it be that by dirty flashing from LOS 14.1 to 15.1 it kept an old and now incompatible encryption?
[OnePlus 3 & 3T Cross Device Development] theCroh:
Or maybe there is some change in LOS that's missing from the latest RR that fixes this.
[OnePlus 3 & 3T Cross Device Development] theduke7:
[MENTION=5091734]dianlujitao[/MENTION] flashing OOS beta 32 and 33 goes will but reboot after flashing (immediately after) causes a freeze with the phone vibrating all the time, i had to shut the phone down with the power button long press, then it went ok....

just letting you know for future updates, let me know if you need any logs.
[OnePlus 3 & 3T Cross Device Development] :
Just ranting, it's been a month since billgoss made a "proper" report aaaaand nothing

Another dead thread like before? Possibly
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
I've been using this TWRP since OB22... And, I noticed one thing... Whenever I flashed any OB, the phone would freeze as soon as I flashed Magisk zip/rebooted my device after flashing it. Flashing Xposed always went fine.

When I flashed OB24 on my 3T, due to some reasons, I left my phone un attended for sometime in TWRP itself. I had just flashed OB24 zip & nothing else.

So when I came back to it after 10-15 mins, I flashed Magisk zip & rebooted & didn't face any freezing/white LED light issue.

Now when I moved to OB25 day 3 days back, I again faced that freeze problem after flashing Magisk zip. Had to do a force reboot.

And, I'm encrypted if that helps to figure out the issue :/
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
That doesn't really help, logs do help, that's why devs are so keen on it to get them....

Even if you upload a simple recovery log it might help much more than just describing the problem...

After you experienced issues in TWRP you can go to TWRP'S mainscreen -> advanced -> logs (checking last kernel log is recommended) and swipe to save them, boot up or pull the logs from /data and upload them to G-drive (or similar) and share the link, that's the most helpful you can do...
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
Surely will when I experience it. Forgot to take them last time that's why couldn't post any :)

Sent from my Moto G3 Turbo Edition
[OnePlus 3 & 3T Cross Device Development] GalaticStryder:
I've just submitted a "fix" for F2FS /data conversion, the problem was the footer length fstab argument that we set to reserve partition blocks for writing the encryption metadata, the current code seems to be quite old and at the time mkfs.f2fs probably had that -r option to reserve blocks but for some reason, it's not available anymore, EXT4 has the -l flag to reserve them natively.

The workaround is to get the whole number of blocks and subtract the length out of them, that should do it for the time being. The whole crypto code is quite obscure to me at least but the patch I sent to gerrit did get the conversion and encryption going with my device.

If some developer wants to try out compiling TWRP with the patch and verify it, please do and report back. Posting here because there should be more developers around here to discuss the issues with encryption and many users wanting to get it "fixed".
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I hope that this will get some traction from the TWRP team and fix issue #210 (https://github.com/omnirom/android_bootable_recovery/issues/210). Glad to see that you included [MENTION=912474]Dees_Troy[/MENTION] and [MENTION=2638973]bigbiff[/MENTION] as reviewers.
[OnePlus 3 & 3T Cross Device Development] Ollebro:
I'm using blu spark​ twrp today since I couldn't get the official one to work with Oreo last I tried. How is the official today, works fine with latest LOS 15.1?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I have absolutely no problems with the official version https://dl.twrp.me/oneplus3
[OnePlus 3 & 3T Cross Device Development] theduke7:
[MENTION=5091734]dianlujitao[/MENTION] I took a log of the freeze and continues vibration issue when flashing new OOS (I don't know if such issue exist for custom ROMs)

Attached, with also kernel log
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
It's only present when flashing full OOS, at least that's my experience...
[OnePlus 3 & 3T Cross Device Development] theduke7:
yes, only on full OOS... i tried the suggestion by another member above to leave it for a few mins after flashing, but same result.
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
I have two 3Ts, both with LOS 15.1 and encrypted DATA with f2fs.

My phone is working well with the "new" TWRP 3.2.1-0, no problems so far, TWRP can decrypt DATA.

My wifes phone worked well with the "new" 3.2.1-0 too, but suddenly TWRP is asking for a password (no password set, using default) and can't decrypt DATA anymore.

My "solution" is to use the "old" 3.2.1-0 which is working and decrypting DATA. But I wonder why, because the "new" 3.2.1-0 was working well before.

Does anybody know what's the problem or how it can be solved ? The recovery.log is attached, thanks.

[...]
I:Done processing fstab files
I:Setting up '/data' as data/media emulated storage.
I:Can't probe device /dev/block/sda15
I:Unable to mount '/data'
I:Actual block device: '/dev/block/sda15', current file system: 'ext4'
I:Can't probe device /dev/block/sda15
I:Unable to mount '/data'
I:Actual block device: '/dev/block/sda15', current file system: 'ext4'
get_crypt_ftr_info crypto key location: 'footer'
I:Backup folder set to '/data/media/TWRP/BACKUPS/12345678'
I:Settings storage is '/data/media'
I:Device is encrypted with the default password, attempting to decrypt.
crypt_ftr->fs_size = 237437880
Using scrypt with keymaster for cryptfs KDF
Invalid hex string
Failed to convert passwd from hex, using passwd instead
keymaster module name is Keymaster QTI HAL
keymaster version is 256
Found keymaster1 module, using keymaster1 API.
Signing safely-padded object
Error starting keymaster signature transaction: -10000
Signing failed
kdf failed
failure decrypting master key
Failed to decrypt master key
crypt_ftr->fs_size = 237437880
Using scrypt with keymaster for cryptfs KDF
keymaster module name is Keymaster QTI HAL
keymaster version is 256
Found keymaster1 module, using keymaster1 API.
Signing safely-padded object
Error sending data to keymaster signature transaction: -21
Signing failed
kdf failed
failure decrypting master key
Failed to decrypt master key
Failed to decrypt data.
Unable to decrypt with default password.
Updating partition details...
[...]
[OnePlus 3 & 3T Cross Device Development] thes3usa:
This may be a dumb question, but have you tried "default_password"?
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
I guess many users do not think about it, so good question, thank you. :cool:

I tried it a while ago after I had a look at the AOSP Full-Disk Encryption page:

https://source.android.com/security/encryption/full-disk

Edit: tried it again, no success ...
[OnePlus 3 & 3T Cross Device Development] :
Even ext4 data partition have an issue with decryption? Or did i misread the log...
[OnePlus 3 & 3T Cross Device Development] BillGoss:
You could try the Blu Spark TWRP from here https://xdaforums.com/oneplus-3/oneplus-3--3t-cross-device-development/kernel-t3404970/post67463496

Also, you could set a password to be required at boot.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Very interesting!

On my phone, which is f2fs, encrypted, password protected, the official TWRP (which works perfectly fine for me) says the data file system is ext4 before decrypting:

I:Can't probe device /dev/block/sda15
I:Unable to mount '/data'
I:Actual block device: '/dev/block/sda15', current file system: 'ext4'
I:Can't probe device /dev/block/sda15
...
/data | /dev/block/sda15 | Size: 0MB
Flags: Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Is_Encrypted Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage
Symlink_Path: /data/media
Symlink_Mount_Point: /sdcard
Primary_Block_Device: /dev/block/sda15
Length: -16384
Display_Name: data
Storage_Name: Internal Storage
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /data/media
Current_File_System: emmc
Fstab_File_System: ext4
Backup_Method: dd
MTP_Storage_ID: 65537

But the decrypted partition is correctly identified as f2fs:

/data | /dev/block/dm-0 | Size: 115934MB Used: 3971MB Free: 69905MB Backup Size: 3971MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Is_Encrypted Is_Decrypted Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage
Symlink_Path: /data/media/0
Symlink_Mount_Point: /sdcard
Primary_Block_Device: /dev/block/sda15
Decrypted_Block_Device: /dev/block/dm-0
Length: -16384
Display_Name: data
Storage_Name: Internal Storage
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /data/media/0
Current_File_System: f2fs
Fstab_File_System: ext4
Backup_Method: files
MTP_Storage_ID: 65537

I have no idea what to do with this information, but maybe [MENTION=5091734]dianlujitao[/MENTION] can make sense of this.
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
Same here on my working phone, before decrypting: ext4

I:Unable to mount '/data'
I:Actual block device: '/dev/block/sda15', current file system: 'ext4'

and after decrypting: f2fs

/data | /dev/block/dm-0 | Size: ...
...
Current_File_System: f2fs
Fstab_File_System: ext4

I hope so. It wouldn't be a problem for me to backup, reformat, reencrypt and restore, but solving the problem would be nicer :D
[Samsung Galaxy S7 Questions and Answers] Hexafox:
Hey guys,

has anyone tried putting a S7 edge Mainboard into a 'normal' S7?

A friend of mine has a totally shattered S7 edge that works apart from the display.

I might get a S7 with some problems but working screens cheap, so would this swap be possible?

On ifixit I saw that the mainboards are very similar, but the screen connector looked different, but they were different versions. (G930V and G935A, 'S7 edge Teardown')

Mine would be SM-G930F and SM-G935F

Thanks :fingers-crossed:
[Samsung Galaxy S7 Questions and Answers] RossTeagan:
Why don't you sell the S7 and with the money you get buy a screen for the edge one?
[Xiaomi Redmi Note 3 Questions & Answers] vickeye:
Is there a way to enable Airtel volte ,?
[Xiaomi Redmi Note 3 Questions & Answers] vickeye:
Any idea
[Xiaomi Redmi Note 3 Questions & Answers] Abhijith Sasikumar:
As of now redmi note 3 does not support airtel volte. But maybe it can fixed with a software upgrade
[ZTE Axon 7 Mini Questions & Answers] monicaparry:
I can't figure out how to remove the date and time from my google photos, has anyone had this issue and has been able to resolve it? Any help would be great.

Thanks!
[ZTE Axon 7 Mini Questions & Answers] Deleted member 7646815:
What exactly do you mean? Correct me if I'm wrong, but I don't think "removing" the time and date has ever been a feature in Google Photos.
[Galaxy S 4 Q&A, Help & Troubleshooting] darkness:
Hello can i use ROM i9505/for i9506
[Galaxy S 4 Q&A, Help & Troubleshooting] krasCGQ:
The answer: No. i9505 and i9506 have different chipset.
[Moto Z Play Questions & Answers] GiantPlaidSquirrel:
I just flashed magisk to the stock rom using twrp, but certain apps i use that use SU (Automate) don't work, and no modules will install.
[Moto Z Play Questions & Answers] St.Noigel:
you need to flash this kernel if you are using 7.1.1 with Dec patch ot this if you are 7.1.1 with using Nov patch
[Moto Z Play Questions & Answers] Artim_96:
Just get the F2FS loopback bug workaround module and flash it through TWRP. It will move Magisk to /cache. No custom kernel needed
[HTC Vox] sirride:
Hi

I have a S710 Vox (Original HTC, not Orange or something)

Since the firmwareupdate, i have troubles with wifi.

Before, i could access it at my hole appartment with "auto" power.

Now, I have to change the WiFi settings to "fullpower" to get a connection to internet.

It doesnt depend how far I am away from my AP. (testet with 1m distance on FritzBoxFonWlan, LaFonera and Zyxel 660Series)

When i am close to the APs, i have full signal strengh...

When i change the wifisettings to fullpower, it emties my battery within 2 hours....

What could be the reason that i can't connect with the "Auto"-Powersettings?
[HTC Vox] sirride:
Bringing up...

I've reflashed with the original ROM. First thing I tried is WLAN. Still same issues.

Is there anyone having any Idea why my WLAN is just running with "MAx-Power"-Setting`?

Tried serveral AccessPoints
[HTC Vox] sirride:
solved

Installed WM6.1

Now it works :)
[HTC Vox] kabeza:
WM 6.1 from Dr. Gonzo ? the one available here ?
[HTC Vox] sirride:
Jep.

Did u also have that issue?
[Xiaomi Mi A1 Guides, News, & Discussion] C.k. Bhatia:
Hey Dear Friends ,

Now As You Know Xiaomi Released Kernal Source Code For MI A1 .

As I know Many Peoples are interested to Install MIUI 9 On MI A1 .

I AM Trying To Port ROM Now . If Anyone Is Pro Here In ROM Port Than Please Help me to do it because I am not experienced .

( ROM Developers Simply Pm me to Join Group )

Why people's are interested to Install MIUI 9 Instead Of Stock Android ?

Many People's Deal with Stock Android For Dual Flagship Camera . Also They can't afford MI 5X With Custom Charges.

Ported ROM Will Available Soon , Stay Tuned .

( interested People Can Take Part In Testing !

Testing Will be Safe As possible as we can .....

Thanks a lot Every XDA Members .
[Xiaomi Mi A1 Guides, News, & Discussion] Rajeev:
U need help for porting or testers for testing?
[Xiaomi Mi A1 Guides, News, & Discussion] ashokmor007:
Ill join you for testing and you can contact [MENTION=5286475]Dhairya[/MENTION] for porting and other stuff he is amzaing in MIUI.
[Xiaomi Mi A1 Guides, News, & Discussion] hk16:
Waiting for It.....Buggy Oreo....A big ****t by Mi ?
[Xiaomi Mi A1 Guides, News, & Discussion] C.k. Bhatia:
Both is welcomed , Testers specially needed , but rom porting helper can help me to port rom more better & faster . Thanks
[Xiaomi Mi A1 Guides, News, & Discussion] nikkpap:
My dream is to get a full functional miui and convert the stupid phone to a smart phone. Re partition the a/b joke and have ota updates from 5x .... This has to be the project.
[Xiaomi Mi A1 Guides, News, & Discussion] sksadh:
Surely i will hep...

I will be tester ,,
[Xiaomi Mi A1 Guides, News, & Discussion] Hellrazoraj:
You release the port..will be there to test it buddy!!
[Xiaomi Mi A1 Guides, News, & Discussion] nicolasmart:
I can help you with porting the ROM. I'm not sure I'll install it on my device immediately but I definitely can help with porting. DM me for information where you can contact me.
[Xiaomi Mi A1 Guides, News, & Discussion] xSairous:
I definitely can help with testing and i will send you daily report for bugs if needed.

waiting your port :)
[Xiaomi Mi A1 Guides, News, & Discussion] amar2cool99:
[MENTION=4960686]OldDroid[/MENTION] working on that
[Xiaomi Mi A1 Guides, News, & Discussion] Sefa142:
I am waiting this <3 Thanks.
[Xiaomi Mi A1 Guides, News, & Discussion] Dewang p3100:
am down for testing
[Xiaomi Mi A1 Guides, News, & Discussion] Dhairya:
ah thankyour bro for the reference really means alot if you need anything contact me on telegram [MENTION=5286475]Dhairya[/MENTION]231
[Xiaomi Mi A1 Guides, News, & Discussion] ashokmor007:
U deserve more than this man...
[Xiaomi Mi A1 Guides, News, & Discussion] navi_58861170:
Try miui

I want to test miui rom
[Xiaomi Mi A1 Guides, News, & Discussion] sooti:
Dream on... you can't really repartition the A/B partitions and will never be able to get updates from the 5X since your rom will not be official... regarding the stupid phone comment.. huh? how is miui smart exactly? because of the junk preloaded apps and spyware xiaomi loads unto miui?
[Xiaomi Mi A1 Guides, News, & Discussion] Faetoms:
I really want to check MIUI 9
[Xiaomi Mi A1 Guides, News, & Discussion] nitroax:
LOL, Who? The guy who won a P9 Lite by donations and made ONE alpha-build full of bugs and disappeard from telegram? Sounds promissing....
[Xiaomi Mi A1 Guides, News, & Discussion] IamSubhodeep:
I'm waiting for MIUI. Big fan. Will appreciate a stable MIUI room.
[Xiaomi Mi A1 Guides, News, & Discussion] C.k. Bhatia:
Thanks For Your Great Helpful Reply . I would like to contact You On Google Plus ( Testbean Labs Community )