Is there a tutorial like this for Honor 5X?
https://www.reddit.com/r/LineageOS/comments/am6dn9/encrypt_phone_on_oneplus_3_not_working/
ephemunch said:
Is there a tutorial like this for Honor 5X?
https://www.reddit.com/r/LineageOS/comments/am6dn9/encrypt_phone_on_oneplus_3_not_working/
Click to expand...
Click to collapse
Just clean flash it.
Edit: Last time I encrypted my lineageos, I couldn't flash anyting through twrp as it wouldn't ask me for decryption password. So make sure your current TWRP supports decryption or else you'll run in to the same problem as I did.
Then I can't take the risk if it wasn't possible to flash via TWRP (twrp-3.4.0-0-kiwi).
So you couldn't even flash LineageOS updates.
Goddamit. 2020 (almost 2021) and still not possible to encrypt smartphone easily with LineageOS+TWRP.
ephemunch said:
Then I can't take the risk if it wasn't possible to flash via TWRP (twrp-3.4.0-0-kiwi).
So you couldn't even flash LineageOS updates.
Goddamit. 2020 (almost 2021) and still not possible to encrypt smartphone easily with LineageOS+TWRP.
Click to expand...
Click to collapse
Those decryption commits never went far with developers. Also, you should not encrypt this device, it will lag like hell probably.
ephemunch said:
Goddamit. 2020 (almost 2021) and still not possible to encrypt smartphone easily with LineageOS+TWRP.
Click to expand...
Click to collapse
To be fair, it's just this one device. I don't have any other device that doesn't support encryption. I have 5 other devices currently running LOS all with encryption that work perfectly. The only one that hasn't ever worked correctly has been the Honor 5X.
Related
TWRP for the OnePlus 5T with File Based Encryption support. Everything is working as expected! Unlock your device with fastboot oem unlock and then fastboot flash the recovery. The stock rom WILL reset your recovery on boot!
Not working / issues
Restoring data partition from backups will lead to boot issues if FBE-encrypted. It's not a TWRP issue but rather a side effect on how FBE works.
Download
SOURCE
Device Tree
Kernel
Patch for FBE
Manifest For Omni-7.1
Credits:
Code:
rhcp011235 - General help, testing, whatnot
xdevs23 - pointing us at the patch for FBE
XDA:DevDB Information
TWRP, Tool/Utility for the OnePlus 5T
Contributors
simonsickle, Dees_Troy, bigbiff
Source Code: https://github.com/SimonSickle/android_device_oneplus_dumpling
Version Information
Status: Stable
Current Stable Version: 3.2.0
Stable Release Date: 2017-12-01
Created 2017-12-07
Last Updated 2017-12-07
any plans for 3.2.0 ?
Currently there are some issues with it booting. Once 8.1 is merged, I’d say 3.2 will be out from me. Otherwise, I’m waiting on the test build from #twrp to get it official. Once that comes in, it will likely be expedited.
Official twrp has taken a surprisingly long time considering that sources have been out for a while
Waiting for official one. There must be a issue which takes time to fix. Never saw TWRP team need a so long time period between device release to TWRP release.
Finally an official TWRP comes out. That was the only thing I was waiting for. I just now need to find the time to root the phone...
Tefzors said:
Finally an official TWRP comes out. That was the only thing I was waiting for. I just now need to find the time to root the phone...
Click to expand...
Click to collapse
this ia not official
Just to understand this correctly... We will have issues restoring data partitions if FBE is enabled? Since FBE was introduced to Android in 7.0, this means we would have to be decrypted for any restore operations to work? Is that only for this version? I swear I saw others restoring data without issues in TWRP as long as they removed their Fingerprint.
Thanks for your work, regardless.
xocomaox said:
Just to understand this correctly... We will have issues restoring data partitions if FBE is enabled? Since FBE was introduced to Android in 7.0, this means we would have to be decrypted for any restore operations to work? Is that only for this version? I swear I saw others restoring data without issues in TWRP as long as they removed their Fingerprint.
Thanks for your work, regardless.
Click to expand...
Click to collapse
It worked for me if PIN was used exclusively. There still are some ways for the restore to go wrong, so I left the warning.
3.1.1.0 doesn't recognize my OTG and fix for this ?
****problem solved... 3.2.0. 0 *****
Updated to 3.2.0. Enjoy!
Also, this is now official: https://twrp.me/oneplus/oneplus5t.html
I liked the theme for the previous version unofficial version.
anyway to replicate that theme with the updated TWRP?
simonsickle said:
Updated to 3.2.0. Enjoy!
Also, this is now official: https://twrp.me/oneplus/oneplus5t.html
Click to expand...
Click to collapse
Thank you
Dont use it for now!
5T users are advised to stay on TWRP by ibe or bluspark as official twrp has issues with data restore, I have tested restore on ibe and bluspark and both work fine for now. Looking at the past track of OnePlus devices official for dumpling would also not be maintained and further updated so it's best to stay on unofficial for now which would be frequently maintained and updated.
Thanks to @FuNkWizard for his tests and heads up.
TWRP connecting pc.The device's name shows as "OnePlus 5"
skyeking69 said:
3.1.1.0 doesn't recognize my OTG and fix for this ?
****problem solved... 3.2.0. 0 *****
Click to expand...
Click to collapse
Try the OTG on TWRP, but same adaptor working on OxygenOS, don't want to work on TWRP... strange.
Did you boot on TWRP with OTG connected?
I solved it by upgrading to version 3.2.0..OTG work fine on that..... Love the custom theme as well.....
Sent from my ONEPLUS A5010 using XDA Free mobile app
This is quick, Thank you.
For some reason USB otg is not recognized when I'm on official 3.2.0 TWRP. Bluspark doesn't have this problem. Any advices?
Schrotty35 said:
Dont use it for now!
5T users are advised to stay on TWRP by ibe or bluspark as official twrp has issues with data restore, I have tested restore on ibe and bluspark and both work fine for now. Looking at the past track of OnePlus devices official for dumpling would also not be maintained and further updated so it's best to stay on unofficial for now which would be frequently maintained and updated.
Thanks to @FuNkWizard for his tests and heads up.
Click to expand...
Click to collapse
Tested /data restore using Bluspark: works just fine.
Tested /data restore using Official 3.2.x: works just fine.
But, ymmv, so if BS version is safer/better: use that one
:good:
I like the form factor and specs on the MediaPad M5 with WiFi and 64GB as a replacement for the Nexus 7 (2013). However, I want root, TWRP and a factory image before I buy it.
Does the XDA community think that we will ever see these or am I waiting in vain?
At least this tablet ships with Android 8.0 and treble project out of the box. It even is a real treble enabled device with an A/B-partition setup. Thus it might be possible that there'll be TWRP sooner or later. In theory there already exist a GSI - Generic System Image - that should boot on the MediaPad M5 by phhusson.
It's discussed already in this thread: https://forum.xda-developers.com/mediapad-m5/help/generic-lineageos-root-t3769331/page5
Sent from my HTC U11 using XDA Labs
@5m4r7ph0n36uru no, the device has no A/B partition setup, but it's treble. Unfortunately there is no stock image available yet so if you overwrite the recovery / system with GSI there is probably no way back ...
AndDiSa said:
@5m4r7ph0n36uru no, the device has no A/B partition setup, but it's treble. Unfortunately there is no stock image available yet so if you overwrite the recovery / system with GSI there is probably no way back ...
Click to expand...
Click to collapse
The second part I new already. But thanks for the heads-up, as the A-only thing is new to me. Damn it Huawei could have done better on that one.
Sent from my HTC U11 using XDA Labs
Alright, so recently I got the zip file for the MIUI 11, Android 10 update. I installed it, all is well, except I miss the face unlock feature. Considering it's a device with the IR face unlock and not the normal optical one. Is there a way I can go back to MIUI 11, Android 9 safely without bricking my device?
Uh, the face unlock option is still there though..?
The Pocophone F1 stock android 10 very definitely does include ir face unlock
Try changing your region, OP
Check it's selected in your security settings too
I'm assuming here that it was the official update zip - not a custom one
lollipopmadman said:
Alright, so recently I got the zip file for the MIUI 11, Android 10 update. I installed it, all is well, except I miss the face unlock feature. Considering it's a device with the IR face unlock and not the normal optical one. Is there a way I can go back to MIUI 11, Android 9 safely without bricking my device?
Click to expand...
Click to collapse
This device doesnt have anti-rollback-protection iirc.
BenjiScale said:
This device doesnt have anti-rollback-protection iirc.
Click to expand...
Click to collapse
Alright, my bad, since I read somewhere that the update might require a location change and hence I did it and made it other than India.
Switched it back to India and I'm all good. Thank you so very much. Saved me from rooting a new phone.
Cheers!
lollipopmadman said:
Alright, my bad, since I read somewhere that the update might require a location change and hence I did it and made it other than India.
Switched it back to India and I'm all good. Thank you so very much. Saved me from rooting a new phone.
Cheers!
Click to expand...
Click to collapse
Now delete thread
I just bought recently MI A3 2 days ago and upon unboxing , I instantly updated it to android 10. Then I suddenly noticed on my official receipt that it is a MI A3 EU... But here is my current rom and it came from OTA. MI meaning it is global. The store is an official MI Store here in the Philippines. In the box it has EU label also next to MI A3 label. Am i global or EU? Planning to unlock and flash stock pie and relock
You are definitely in Global ROM, as the Android 10 EU ROM haven't rolled out yet. Also, there are no practical differences between one rom or another, more than EU policies and stuff like that.
wilburyh said:
You are definitely in Global ROM, as the Android 10 EU ROM haven't rolled out yet. Also, there are no practical differences between one rom or another, more than EU policies and stuff like that.
Click to expand...
Click to collapse
Well actually just concern with warranty
Do not downgrade Android version after you successfully installed Android 10. There are user reports and also Xiaomi confirms that it makes permanent changes to some partitions and your phone won't work correctly after the downgrade.
_mysiak_ said:
Do not downgrade Android version after you successfully installed Android 10. There are user reports and also Xiaomi confirms that it makes permanent changes to some partitions and your phone won't work correctly after the downgrade.
Click to expand...
Click to collapse
Thank you for the warning i almost did it. But what are the suppose issues others are reporting? Even in fastboot issues will arise?
amnher said:
Thank you for the warning i almost did it. But what are the suppose issues others are reporting? Even in fastboot issues will arise?
Click to expand...
Click to collapse
Ok. When i had chat with Xiaomi chat support. Technician told me that it is safe to downgrade android version. There will be no issues provided i perform factory reset.
amnher said:
Thank you for the warning i almost did it. But what are the suppose issues others are reporting? Even in fastboot issues will arise?
Click to expand...
Click to collapse
Official warning: https://c.mi.com/thread-2918723-1-0.html
I can't find the report on mi forum, but I recall that it was non functional WiFi and maybe some other things. Most probably related to persist partition.
There is no other option how to rollback than to use Fastboot, so yes, even if you use Fastboot you're risking non functional phone.
I don't know about stock 9 rom, but after I flashed the offical Android 10 rom, I went back to miui (which is Android 9) and my phone is working perfectly fine.
_mysiak_ said:
Official warning: https://c.mi.com/thread-2918723-1-0.html
I can't find the report on mi forum, but I recall that it was non functional WiFi and maybe some other things. Most probably related to persist partition.
There is no other option how to rollback than to use Fastboot, so yes, even if you use Fastboot you're risking non functional phone.
Click to expand...
Click to collapse
That is so unfortunate I dont wanna risk my 2 day old phone
Termi92 said:
I don't know about stock 9 rom, but after I flashed the offical Android 10 rom, I went back to miui (which is Android 9) and my phone is working perfectly fine.
Click to expand...
Click to collapse
Well MIUI is different from Android One
My wife owns a Mi A3 EEA V11.0.10.0.QFQEUXM, is there a chance she will have A11 one day ?
Ehm, yes? Plus plenty ROMs here.
I don't want to install a custom ROM, onlmy the stock one, it seems that QFQEUXM are not update since 2020 and blocked in A10
Sadly, we can never trust an OEM any more (could we ever?)...
gmaurinphoto said:
My wife owns a Mi A3 EEA V11.0.10.0.QFQEUXM, is there a chance she will have A11 one day ?
Click to expand...
Click to collapse
if your phone doesn't receive OTAs just load the last one through recovery. mine stopped getting OTAs since summer of 2020 and I have to apply updates with recovery ever since.
labeed said:
if your phone doesn't receive OTAs just load the last one through recovery. mine stopped getting OTAs since summer of 2020 and I have to apply updates with recovery ever since.
Click to expand...
Click to collapse
The problem is, there is no new recovery for QFQEUXM EEA
gmaurinphoto said:
The problem is, there is no new recovery for QFQEUXM EEA
Click to expand...
Click to collapse
q means 10 r is 11, mine is RFQEUXM now. just grab android 11 full rom recovery and load that
labeed said:
q means 10 r is 11, mine is RFQEUXM now. just grab android 11 full rom recovery and load that
Click to expand...
Click to collapse
Could i put a RFQEUXM on a QFQ .... ?
gmaurinphoto said:
Could i put a RFQEUXM on a QFQ .... ?
Click to expand...
Click to collapse
i applied V12.0.3.0.RFQEUXM on V11.0.10.0.QFQEUXM but it's been well over a year now since that