Related
As has been mentioned in the thread, I have my one plus 3 encrypted ( Oxygen OS 4.1.6 ) encrypted, Can I flash lineage OS or RR without unencrypt my phone?
Sure. I've tried many ROMs and always kept encryption.
Sent from my OnePlus 3 using Tapatalk
Yes, as long as you remember the encryption key.
Yeah, absolutely.
To keep OOS encryption DO NOT wipe data via fastboot format/erase command, but ONLY via recovery (like in 99.9% of scenarios).
Unlike @Ozone74 said, there's no encryption key to remember, since Android encryption is based on the used pattern/PIN/password.
I highly suggest, both for security and compatibility reasons, to enable authentication request at bootup.
Otherwise:
1) Recovery could be accessible for everyone;
2) Recovery could be still protected, but unable to unlock.
Simone98RC said:
Yeah, absolutely.
To keep OOS encryption DO NOT wipe data via fastboot format/erase command, but ONLY via recovery (like in 99.9% of scenarios).
Unlike @Ozone74 said, there's no encryption key to remember, since Android encryption is based on the used pattern/PIN/password.
I highly suggest, both for security and compatibility reasons, to enable authentication request at bootup.
Otherwise:
1) Recovery could be accessible for everyone;
2) Recovery could be still protected, but unable to unlock.
Click to expand...
Click to collapse
Well, AFAIK you can change your device PIN/Pattern as many times as you like but the encryption key cannot be change after the initial setup. So he might have changed his PIN/Pattern after encrypting the device but the encryption key will stay the same as the original PIN/Pattern.
Ozone74 said:
Well, AFAIK you can change your device PIN/Pattern as many times as you like but the encryption key cannot be change after the initial setup. So he might have changed his PIN/Pattern after encrypting the device but the encryption key will stay the same as the original PIN/Pattern.
Click to expand...
Click to collapse
You're absolutely wrong!
The encryption is based on latest PIN/pattern/password.
Have you never tried to change authentication method on encrypted phone?
Simone98RC said:
You're absolutely wrong!
The encryption is based on latest PIN/pattern/password.
Have you never tried to change authentication method on encrypted phone?
Click to expand...
Click to collapse
I gave it a test run, since you sounded so confident but it only proved what I already knew.
You cannot decrypt the device with your new PIN and can only be done if the original pin.
My device was originally encrypted with the PIN 1234 and it was the same to unlock my phone too. I changed my device PIN to 0000 and rebooted into TWRP where I was met with the the decryption page. I entered my new PIN 0000 and it failed to decrypt. I then entered my original pin of 1234 and it decrypted.
I think you need to check it out for yourself too.
Simone98RC said:
You're absolutely wrong!
The encryption is based on latest PIN/pattern/password.
Have you never tried to change authentication method on encrypted phone?
Click to expand...
Click to collapse
More than 3 months and still no reply. I think you stand corrected.
Disclaimer :
YOU are choosing to make these modifications
and YOU are the only one responsible for any damages done to your device
==== Notes/Prerequisets/Links ====
* you should have already unlocked your bootloader (if not then start the process as soon as possible because it's going to take a while).
* backup your stuff, make sure you have sufficient charge just in case anything went wrong.
* download the unoffical TWRP port from Here (get the latest version)
* get the latest magisk from Here
* install device usb drivers
* set up fastboot properly Method A, Method B (using chocolaty)
- - - - - - - - - - - -
instructions :
1- shutdown your device completely.
2- enter fastboot mode by pressing and holding the Vol Down + Power Button button until you see xiaomi's mi bunny with a blue "fastboot" text underneath it.
3- connect your device to your pc via usb cable.
4- on your pc check if you have fastboot configured properly and your device recognized by typing:
Code:
fastboot devices
if it's detected then you're good to proceed to the next step.
5- flash the twrp recovery image by using the usual fastboot commands.
Code:
fastboot flash recovery recovery.img
in our case it should look something like:
Code:
fastboot flash recovery recovery-TWRP-3.3.0-0517-XIAOMI8LITE-CN-wzsx150.img
6- unplug usb cable and hold the Vol up + Power Button (don't let go of the buttons untill the devices vibrates) and let it boot to the twrp recovery you just installed.
7- if you rebooted successfully, you should be at TWRP splash screen, if greeted with a slider slide it and continue.
8- in the main menu of TWRP, go to "Install" choose the magisk zip file you downloaded and flash it, when done reboot the device.
9- congratulations friend, you're now rooted and have TWRP as your recovery Happy Flashing :highfive:
- - - - - - - - - - - -
Optional : install Orange Fox Recovery from Here (Supports Encryption and MIUI OTA updates).
- - - - - - - - - - - -
2020-02-25 Last upated and working on MIUI Global Stable 11.0.8 Pie
just in case
Is it possible to just accesss the TWRP to edit build.prop enabling camera2 Api?
If I remember is something about:
fastboot boot twrp.img
and then:
setprop persist.camera.HAL3.enabled 1
Without the need of root the device.
Thanks for the guide!
antonioli84 said:
Is it possible to just accesss the TWRP to edit build.prop enabling camera2 Api?
If I remember is something about:
fastboot boot twrp.img
and then:
setprop persist.camera.HAL3.enabled 1
Without the need of root the device.
Thanks for the guide!
Click to expand...
Click to collapse
Sorry for the late reply
No problem
+
I'm not really sure if you could do it with TWRP's built in file manager without root
You could try
I've seen people do it with adb but haven't had the chance to try it yet
take a look here : https://www.google.iq/amp/s/amp.red...gswg/camera2_api_without_root/#ampf=undefined
And here (this has some very useful info)
https://www.google.iq/amp/s/forum.x...o/guide-enable-camera2-api-root-t3690366/amp/
malek_anas_97 said:
Sorry for the late reply
No problem
+
I'm not really sure if you could do it with TWRP's built in file manager without root
You could try
I've seen people do it with adb but haven't had the chance to try it yet
take a look here : https://www.google.iq/amp/s/amp.red...gswg/camera2_api_without_root/#ampf=undefined
And here (this has some very useful info)
https://www.google.iq/amp/s/forum.x...o/guide-enable-camera2-api-root-t3690366/amp/
Click to expand...
Click to collapse
Thank you for the reply. I've done it in Mi A1 but I don't know if it's the same procedure because of the MIUI. One of the links says that we have to change something in kernel to do it.
It would be good expert people try it to see what method works. It's sad that the Mi 8 Lite doesn't have a proper forum until now.
antonioli84 said:
Thank you for the reply. I've done it in Mi A1 but I don't know if it's the same procedure because of the MIUI. One of the links says that we have to change something in kernel to do it.
It would be good expert people try it to see what method works. It's sad that the Mi 8 Lite doesn't have a proper forum until now.
Click to expand...
Click to collapse
i enabled it in stock miui by adding "persist.camera.HAL3.enabled=1" to my build prop and then rebooting
malek_anas_97 said:
i enabled it in stock miui by adding "persist.camera.HAL3.enabled=1" to my build prop and then rebooting
Click to expand...
Click to collapse
Thanks for the reply.
What method did you use to change build.prop?
Can't find a similar guide for the Mi 8, is it the same process as for the lite ?
antonioli84 said:
Thanks for the reply.
What method did you use to change build.prop?
Click to expand...
Click to collapse
i'm rooted with magisk
with a file manager, i use this one https://play.google.com/store/apps/details?id=nextapp.fx&hl=en
+
this addon https://play.google.com/store/apps/details?id=nextapp.fx.rr
the file is in /system/build.prop
webvan said:
Can't find a similar guide for the Mi 8, is it the same process as for the lite ?
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=YI2CtIIPVaI
malek_anas_97 said:
i'm rooted with magisk
with a file manager, i use this one https://play.google.com/store/apps/details?id=nextapp.fx&hl=en
+
this addon https://play.google.com/store/apps/details?id=nextapp.fx.rr
the file is in /system/build.prop
Click to expand...
Click to collapse
Thank you man. I would like to know if anyone can do the trick without root. I've bought a Mi 8 Lite for my wife and it would be nice to her receive the updates from Xiaomi and use the GCam the same way she receives in Mi A1.
malek_anas_97 said:
7- if you rebooted successfully, you should be at TWRP splash screen
you will be greeted with a slider slide it and continue
Click to expand...
Click to collapse
Hi Malek,
When you first boot to TWRP, were you asked for the decryption password? If yes, did you just format data to skip this? I was asked for the password and my screen PIN did not work. Just wondering if there is no other choice that to format data.
Official Xiaomi Mi 8 Lite (Platina) telegram group 24/7 support and latest ROM news posted here first!
Rules :
1 - English only.
2 - Be polite.
3 - Don't spam.
Gp Link : https://t.me/joinchat/DXcdlA0r5XYI-ooJlO8IlQ
Please Join
chan200606 said:
Hi Malek,
When you first boot to TWRP, were you asked for the decryption password? If yes, did you just format data to skip this? I was asked for the password and my screen PIN did not work. Just wondering if there is no other choice that to format data.
Click to expand...
Click to collapse
to this point i don't really understand how encryption works on this device
it's on by default i guess
so what i finally did the other day to be kinda sure of what's happening
i flashed stock rom in Mi Flash with the clean all option checked
i set up the phone for the first time without setting any fingerprint or security or anything
after that i flashed twrp
from twrp i flashed dm verity and encryption disable
get it from here https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
(make aure to read the first post)
then formatted data
after that the booted up and i set it up normally
and then booted to twrp again to flash latest magisk
now when i check if my device is encrypted using this adb command "adb shell getprop ro.crypto.state"
i get "unencrypted"
so i guess it works? i don't know lol
malek_anas_97 said:
i flashed stock rom in Mi Flash with the clean all option checked
i set up the phone for the first time without setting any fingerprint or security or anything
after that i flashed twrp
from twrp i flashed dm verity and encryption disable
Click to expand...
Click to collapse
It looks like your phone was not encrypted (or was encrypted with MIUI's default password) when you flashed TWRP, as you had clean flashed stock then set up without setting security. That you could start TWRP to flash "dm versity and encryption disable", without being asked to input a password first, shows that TWRP was able to handle the default encryption (or no encryption) of the clean MIUI install.
In my case I already have a screen PIN set up on my phone before trying to install TWRP, and this version of TWRP can't handle it. Another difference is that I have not actually flashed TWRP onto the phone but have merely booted to TWRP via fastboot. I wouldn't have thought that this would affect TWRP's ability to decrypt the DATA partition though.
In hindsight I should have just done the minimum setup after the phone was wiped by the bootloader unlocking process before installing TWRP. I guess that unless there is another version of TWRP out that can handle the screen PIN encryption, my only option is to wipe clean the phone so that I can repeat what you did. However, now that I have reinstalled everything on the phone, I am a bit reluctant to do this just to get root. I think I will wait until there is an AOSP ROM available and do the wipe/format at the time of switching. Hopefully I don't have to wait too long!
chan200606 said:
In my case I already have a screen PIN set up on my phone before trying to install TWRP, and this version of TWRP can't handle it. Another difference is that I have not actually flashed TWRP onto the phone but have merely booted to TWRP via fastboot. I wouldn't have thought that this would affect TWRP's ability to decrypt the DATA partition though.
Click to expand...
Click to collapse
An update: I've now got over this encryption thing. It is indeed the screen PIN that was causing me problems. While I had tried removing the PIN and all fingerprints last time, I had powered down the phone immediately after removing the PIN and booted into fastboot mode. Today I thought I better try it one more time: after removing the PIN, reboot the phone to system first before powering it down and restarting in fastboot mode. This cycles the phone system at least once without the PIN so hopefully any traces of the PIN would really be wiped. And indeed it works - the booted TWRP (i.e. not flashed to phone) has no problems reading my phone and I could install Magisk.
So I now have stock recovery + Magisk on my Mi8 Lite, which is the minimum I wished to do to it. Maybe at a later date I would flash TWRP onto the phone as well.
i cant unlock my mi 8 lite, say user portrait scores too low or black, i activate all need, oem, usb, sync device. no work, any help?
Everything is ok for global rom.
For the language twrp asked directly at first launch for it and you don't need anymore magisk, you can install it directly from twrp. ( advance/install root ) it'll install the version 17.1 and you can update it from the app on the phone.
No problem for reboot into twrp ( volume up + power) even with fingerprint.
kax001 said:
i cant unlock my mi 8 lite, say user portrait scores too low or black, i activate all need, oem, usb, sync device. no work, any help?
Click to expand...
Click to collapse
i really have no idea why this is happening to you
i searched online and it seems like you're not the only one having this
vonclutch said:
Everything is ok for global rom.
For the language twrp asked directly at first launch for it and you don't need anymore magisk, you can install it directly from twrp. ( advance/install root ) it'll install the version 17.1 and you can update it from the app on the phone.
No problem for reboot into twrp ( volume up + power) even with fingerprint.
Click to expand...
Click to collapse
yeah i know there's no problem in turning the phone off then rebooting manually with the buttons
but i was talking about using "fastboot reboot recovery" command to reboot to recovery from fastboot directly
anyways glad everything worked for you friend : )
Hi, new to the forums.
I downloaded MIUI 10 recovery rom (based on Android 9) and flashed it with TWRP. It booted to MIUI as normal, but I changed my mind and wanted to flash MIUI 11 recovery rom (still based on Android 9) instead. I normally set a pattern lock before rebooting into recovery but this time i forgot. This time it rebooted into MiRecovery3.0, then I wiped data from that menu thinking it would bring me to TWRP...now Im stuck with MiRecovery and cant even load MIUI 10 rom. All id like to do is to get TWRP back and flash my MIUI 11 then flash Magisk like I always do.
I tried
HTML:
.\fastboot.exe flash recovery twrp.img
but I keep getting FAILED (write to device failed(unknown error))
Then I realized I normally set the Pattern lock AND turn on USB debugging...but this time I wiped data before either of these things could be done...bad move ugh
Unlocked bootloader before all this happened but some threads say I might have relocked it?
I tried everything, please someone help!
My device is Global Rom.
Adrian
voidturbulence said:
Unlocked bootloader before all this happened but some threads say I might have relocked it
Click to expand...
Click to collapse
Check with:
>> fastboot oem device-info
"fastboot" is equivalent to "./fastboot.exe"
I did that earlier and it said error too many threads or something similar and immediately kicked my device out of fastboot. I can double check when I wake up if needed?
And surprise, I left it on the charger and it booted back into MIUI all by itself . I checked developer settings and it says bootloader already unlocked with the greyed out slider. However, I still get the same unknown error when flashing twrp..
I did .\fastboot.exe devices and it detects the device but it just kicks me out of fastboot with that unknown error when I try flashing hope I can get twrp back
Edit : this time as soon as I saw MIUI I turned on USB debugging and set a Pattern lock! But still got the error after
voidturbulence said:
I did that earlier and it said error too many threads or something similar and immediately kicked my device out of fastboot. I can double check when I wake up if needed?
And surprise, I left it on the charger and it booted back into MIUI all by itself . I checked developer settings and it says bootloader already unlocked with the greyed out slider. However, I still get the same unknown error when flashing twrp..
I did .\fastboot.exe devices and it detects the device but it just kicks me out of fastboot with that unknown error when I try flashing hope I can get twrp back
Edit : this time as soon as I saw MIUI I turned on USB debugging and set a Pattern lock! But still got the error after
Click to expand...
Click to collapse
I don't know why you need a Pattern lock - I absolutely never use it and flash from Fastboot or use TWRP with no problem (fingerprint, pin or nothing)
Ofc, USB debugging must be enabled
just tried the oem unlock command in fastboot, I got unknown error again, then kicked me out of fastboot.
i set the pattern lock cause i remember one time i didnt set one, so when I went to TWRP to flash a rom, folders were encrypted and i couldnt find the rom file. and i didnt have an otg adapter at the time. when i set the pattern i could enter the pattern in TWRP and view my decrypted folders and find the rom easily. now that i think of it does encryption actually stop me from pushing the rom with adb and somehow flashing it?
still new to all of this
edit: my only saving grace is the USB 2.0 hub arriving at my house today, and this thread... fingers crossed
voidturbulence said:
just tried the oem unlock command in fastboot, I got unknown error again, then kicked me out of fastboot.
i set the pattern lock cause i remember one time i didnt set one, so when I went to TWRP to flash a rom, folders were encrypted and i couldnt find the rom file. and i didnt have an otg adapter at the time. when i set the pattern i could enter the pattern in TWRP and view my decrypted folders and find the rom easily. now that i think of it does encryption actually stop me from pushing the rom with adb and somehow flashing it?
still new to all of this
edit: my only saving grace is the USB 2.0 hub arriving at my house today, and this thread... fingers crossed
Click to expand...
Click to collapse
For unlocking Bootloader you need to use their miflash_unlock PC program, not fastboot oem unlock command
So you mean pin/password, not the (graphical) pattern
If you disable pin/password, TWRP will not ask you but it should still know 'default' one to properly read/write to Storage
zgfg said:
For unlocking Bootloader you need to use their miflash_unlock PC program, not fastboot oem unlock command
So you mean pin/password, not the (graphical) pattern
If you disable pin/password, TWRP will not ask you but it should still know 'default' one to properly read/write to Storage
Click to expand...
Click to collapse
sorry i meant i typed oem device-info and I still got the unknown error and got kicked out
edit: also do you mind clarifying default, cause all i saw was the random numbers and letters as folder names and i know that once I entered my pattern in TWRP the issue was gone...did you mean storage/emulated/0?
voidturbulence said:
sorry i meant i typed oem device-info and I still got the unknown error and got kicked out
edit: also do you mind clarifying default, cause all i saw was the random numbers and letters as folder names and i know that once I entered my pattern in TWRP the issue was gone...did you mean storage/emulated/0?
Click to expand...
Click to collapse
USB 2.0 hub worked !! Android 9 based MIUI 11 rooted with Magisk on 84hz refresh rate...mindblowing.
Thanks for the help
voidturbulence said:
USB 2.0 hub worked !! Android 9 based MIUI 11 rooted with Magisk on 84hz refresh rate...mindblowing
Click to expand...
Click to collapse
Glad that you fixed.
Do you really see a difference with 84hz - and you downgraded because of not working with MIUI 11/12, Android 10?
voidturbulence said:
edit: also do you mind clarifying default, cause all i saw was the random numbers and letters as folder names and i know that once I entered my pattern in TWRP the issue was gone
Click to expand...
Click to collapse
Screen unlock Pattern is graphical one (see a screenshot), aren't you talking about pin/password
Data partition is File Based Encrypted (FBE) with ICE:
https://www.qualcomm.com/media/documents/files/file-based-encryption.pdf
You can see that if you open /vendor/data.qcom (textual file but root required)
Even if you don't set screen unlock protection, ICE still uses a key unique for your device and TWRP can also decrypt Storage on boot with 'default' password - see a photo from TWRP
zgfg said:
Glad that you fixed.
Do you really see a difference with 84hz - and you downgraded because of not working with MIUI 11/12, Android 10?
Screen unlock Pattern is graphical one (see a screenshot), aren't you talking about pin/password
Data partition is File Based Encrypted (FBE) with ICE:
https://www.qualcomm.com/media/documents/files/file-based-encryption.pdf
You can see that if you open /vendor/data.qcom (textual file but root required)
Even if you don't set screen unlock protection, ICE still uses a key unique for your device and TWRP can also decrypt Storage on boot with 'default' password - see a photo from TWRP
Click to expand...
Click to collapse
Yes, when i used the graphical screen unlock it then showed me all the proper folder names, but before that it was all encrypted. if what youre saying is true then i might have not even entered phone setup far enough to skip screen unlock protection? i might have just immediately restarted to recovery while skipping usb debugging entirely...long nights i am sleepy lol
and 84hz is amazing, the phone feels so much more premium. I would do Android 10 based MIUI 11 but after seeing posts about getting bootloops with 84hz or other glitches I was scared off. once i go 84hz couldnt go back. also want the latest softwares with 84hz, but Android 9 based MIUI 11 seems to be farthest i can go. 84hz MIUI 12 Android 10 is the dream of course
AOSP for OnePlus 5/5T - Android 12
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it!
*/
Most of the information from here can be applied for this ROM.
Introduction
This projects aims to create an upgradable AOSP build system for the Oneplus 5 (Cheeseburger).
No repository from AOSP is changed: no commit over AOSP is at the moment present on the sources for this ROM.
All the changes are provided in separate repositories (HALs, kernel): this allows to upgrade Android with minimal effort, potentially also for future major versions.
Most of the added repositories is provided by LineageOS or CAF, so thanks to them for those repos.
Screenshots are attached.
This ROM is based on the work on Android 11 from here: https://forum.xda-developers.com/t/...-19-september-2021-locked-bootloader.4183691/
As usual, only builds with enforcing SELinux, no root access and 'user Android build flavor' will be posted here.
Known issues
- None that I'm aware of.
Changelog
See second post.
Download
Releases can be found on AndroidFileHost.
OnePlus 5 (Cheeseburger): https://androidfilehost.com/?w=files&flid=328726
OnePlus 5T (Dumpling): https://androidfilehost.com/?w=files&flid=328820
Installation
Backup everything.
The provided zip can be installed using the TWRP recovery: clear data while doing that.
The ROM expects the firmware from OOS 10.0.1: different firmwares are not tested.
The provided recovery allows only flashing signed images: use TWRP if you need to flash GApps or different packages.
Sources
Kernel on github: https://github.com/robertoglandroid/kernel_oneplus_msm8998
ROM sources: https://github.com/roberto-sartori-gl/local_manifests/tree/a12/gl
Telegram discussion group here!
XDA:DevDB Information
AOSP for OnePlus 5/5T, ROM for the OnePlus 5/5T
Contributors
robertogl
Thank you to @T1mb3 and @Maitreya29!
ROM OS Version: Android 12
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2021-10-05
Last Updated 2022-07-07
Changelog
[07/07/2022] aosp12_cheeseburger/dumpling-ota-user-20220707.zip
July2022 Security patches (synced with AOSP android-12.1.0_r10)
[08/06/2022] aosp12_cheeseburger/dumpling-ota-user-20220608.zip
June 2022 Security patches (synced with AOSP android-12.1.0_r8)
[21/05/2022] aosp12_cheeseburger/dumpling-ota-user-20220521.zip
Support f2fs formatted /cache partition
Synced with Lineage 19.1 sources
Minor fixes
Code cleanup
[15/05/2022] aosp12_cheeseburger/dumpling-ota-user-20220515.zip
Add option to apply OTA updates from SettingsExtra
4 files can be installed:
the ROM OTA - put the zip in /sdcard/update.zip
magisk - put the zip in /sdcard/magisk.zip
gapps - put the zip in /sdcard/gapps.zip
decryption zip - put the zip in /sdcard/decrypt.zip
The device will reboot automatically in recovery and apply the updates. Only TWRP can install magisk, gapps or the decryption zip.
Fix crash of the Settings app while configuring fingerprint or PIN lock (during the first setup, or from the Settings page)
Add possibility to enable location indicator in the Development Options
Location indicator is disabled for the Phone Services
[03/05/2022] aosp12_cheeseburger/dumpling-ota-user-20220503.zip
May 2022 Security patches (synced with AOSP android-12.1.0_r5)
Fix issue with Led Manager (SettingsExtra)
[04/04/2022] aosp12_cheeseburger/dumpling-ota-user-20220404.zip
April 2022 Security patches (synced with AOSP android-12.1.0_r4)
Fix slow unlock when fingerprint is used
[13/03/2022] aosp12_dumpling-ota-user-20220313.zip
Fix Settings app crash when opening fingerprint settings
[08/03/2022] aosp12_cheeseburger/dumpling-ota-user-20220308.zip
Android 12L
March 2022 Security patches (synced with AOSP android-12.1.0_r1)
Fix time and date not persisted after a reboot/factory reset
Fix vibration level setting on SettingsExtra
[01/03/2022] aosp12_cheeseburger/dumpling-ota-user-20220301.zip
Sync with Lineage 19 source
Fix issue with sim2 (data works also on sim2 now)
Fix Pocket Mode
Fix 'issue' that was causing some apps to detect root without Magisk
[08/02/2022] aosp12_cheeseburger/dumpling-ota-user-20220208.zip
February 2022 Security patches (synced with AOSP android-12.0.0_r29)
Fix Jio issues with VoLTE calls
[04/01/2022] aosp12_cheeseburger/dumpling-ota-user-20220104.zip
January 2022 Security patches (synced with AOSP android-12.0.0_r26)
Fix alarms not working with default Clock app
[07/12/2021] aosp12_cheeseburger/dumpling-ota-user-20211207-beta.zip
December Security patches (synced with AOSP android-12.0.0_r16)
[02/11/2021] aosp12_cheeseburger/dumpling-ota-user-20211102-beta.zip
November Security patches (synced with AOSP android-12.0.0_r13)
Add separate wifi and cellular data quick settings tiles (as Android 11)
Unified Android 12 tile is still present
[25/10/2021] aosp12_cheeseburger/dumpling-ota-user-20211025-beta.zip
Add f2fs support on /data partition
[20/10/2021] aosp12_cheeseburger/dumpling-ota-user-20211020-experimental.zip
Add support for OnePlus 5T (Dumpling)
Fix data on SIM1 (SIM2 is not working for data in this release)
Enable switch for default mobile data between SIM1 and SIM2 directly in the Android Settings (removed tile: less code to mantain)
Grant permissions to Play Store (and some Google apps) automatically - allow to setup the device and restore a backup at first boot
Fix TWRP not booting after flashing Android 12
Now recovery is not updated/overwritten anymore (no need for the persist_twrp mod or anything - installed recovery is persisted)
Vibration and alarm icons are back in the status bar
[09/10/2021] aosp12_cheeseburger-ota-user-20211009.zip
Fix encryption - Now File Based Encryption is enabled by default
Fix SIM1 sometimes not being recognized at boot
Fix an issue that caused Android to being stuck at boot sometimes (e.g. after flashing it the first time)
Add 'SIM Data Switch' tile to allow switching the default SIM used for mobile data
[06/10/2021] aosp12_cheeseburger-ota-user-20211006-alpha.zip
First release: October 2021 Security Patch (synced with AOSP android-12.0.0_2)
Only known issue is encryption not working
Booting with locked bootloader
This ROM can be booted with locked bootloader.
Not supported at the moment.
For more info, refer to the A11 thread (the information are the same):
[ROM][11.0][OnePlus 5] AOSP for OnePlus 5 [06 OCTOBER 2021][Locked bootloader]
New build in the first post: aosp_cheeseburger-ota-user-20201205.zip Changelog: Add option to enable Call Recording - available in the Settings Extra app Add battery level on the bluetooth icon on status bar (when a bluetooth device reports a...
forum.xda-developers.com
Reserved3
Gapps android 12 here
Added to the OnePlus 5 Index Thread here.
Sources are now available here: https://github.com/roberto-sartori-gl/local_manifests/tree/a12/gl
New release: aosp12_cheeseburger-ota-user-20211009.zip
Changelog:
Fix encryption - Now File Based Encryption is enabled by default
Fix SIM1 sometimes not being recognized at boot
Fix an issue that caused Android to being stuck at boot sometimes (e.g. after flashing it the first time)
Add 'SIM Data Switch' tile to allow switching the default SIM used for mobile data
So, this release fixes encryption: I only plan to support builds with encryption enabled, so if you flashed the first A12 release (without encryption), you'll need to format /data or disable encryption somehow (I don't provide support for this, sorry, but there should be some flashable zips).
This is the last time that formatting /data will be require, I promise!
This also means that if you have my A11 ROM (linked in the first post) you can actually update to A12 without losing any data (app included). But this is still a beta release, so at your risk!
Roms works fine for the most part. I'm not sure if i'm even supposed to test different browsers but chrome and kiwi browser end up crashing when downloading heavy files (> 100Mb)
work on device decrypted and twrp?
hello, there's some problem with the rom and the phone. i accidentaly rebooted in recovery and it stays stuck on logo screen and wont go over, also force rebooting it will always go into twrp and wont boot anyway. tried also to update to lastest recovery verison, but result it'S also the same. any solution or fix for this? p.s.: at the first flash, the rom booted fine.
kitamurt said:
hello, there's some problem with the rom and the phone. i accidentaly rebooted in recovery and it stays stuck on logo screen and wont go over, also force rebooting it will always go into twrp and wont boot anyway. tried also to update to lastest recovery verison, but result it'S also the same. any solution or fix for this? p.s.: at the first flash, the rom booted fine.
Click to expand...
Click to collapse
What logo? Android animation, oneplus logo, or Android recovery logo?
morfances said:
work on device decrypted and twrp?
Click to expand...
Click to collapse
The ROM only supports encrypted /data, but there should be some zip on XDA to manage decryption (I never tested that though).
robertogl said:
What logo? Android animation, oneplus logo, or Android recovery logo?
The ROM only supports encrypted /data, but there should be some zip on XDA to manage decryption (I never tested that though).
Click to expand...
Click to collapse
it stays stuck on twrp logo, but i can go to fastboot mode also and reboot, but the system wont boot anyway. it will only boot automatically into twrp, but i cant make anything since it stays stuck on twrp logo. i followed the steps above, bootlaoder already unlocked, formatted data, then flashed rom and gapps, eventually rebooted.
kitamurt said:
it stays stuck on twrp logo, but i can go to fastboot mode also and reboot, but the system wont boot anyway. it will only boot automatically into twrp, but i cant make anything since it stays stuck on twrp logo. i followed the steps above, bootlaoder already unlocked, formatted data, then flashed rom and gapps, eventually rebooted.
Click to expand...
Click to collapse
What TWRP are you using? TWRP should boot as it should not depend on the OS.
robertogl said:
What TWRP are you using? TWRP should boot as it should not depend on the OS.
Click to expand...
Click to collapse
i'm using the official twrp downloaded from the website, version 3.5.2. what doesn't add up is the reason why the recovery boots and stays stuck on the logo. so it's really weird. i also tried to boot the twrp from adb, giving the command "fastboot boot twrp.img", but the result it's the same.
kitamurt said:
i'm using the official twrp downloaded from the website, version 3.5.2. what doesn't add up is the reason why the recovery boots and stays stuck on the logo. so it's really weird. i also tried to boot the twrp from adb, giving the command "fastboot boot twrp.img", but the result it's the same.
Click to expand...
Click to collapse
Try booting this: https://androidfilehost.com/?fid=10763459528675599801
robertogl said:
Try booting this: https://androidfilehost.com/?fid=10763459528675599801
Click to expand...
Click to collapse
that worked, thx. but seems that the "signed twrp" can't recognize encrypted data, indeed when asking for pattern/pin, even entering it correctly, will say that isn't recognized and therefore data is not recognized. so normal twrp can't be used for flash this kind of rom and gapps?
kitamurt said:
that worked, thx. but seems that the "signed twrp" can't recognize encrypted data, indeed when asking for pattern/pin, even entering it correctly, will say that isn't recognized and therefore data is not recognized. so normal twrp can't be used for flash this kind of rom and gapps?
Click to expand...
Click to collapse
For sure current TWRP cannot decrypt data as they need to be updated to support A12.
But at least you can flash/format things now.
I'm not sure why your TWRP didn't work, the signature should not be important (I shared that because it was already uploaded).
well, thanks for the advice! that said, the bugs i've encountered so far are:
-wifi very buggy, it disconnects after a while and the signal it's very poor, after it's disconnected it can't reconnect to any network. this is solved by rebooting the device
-random crash of systemui, especially when pressing the settings button
-twrp 3.5.2 not booting after flash the rom, only the signed_twrp will work (but not decrypt data) and allow to flash other things
kitamurt said:
well, thanks for the advice! that said, the bugs i've encountered so far are:
-wifi very buggy, it disconnects after a while and the signal it's very poor, after it's disconnected it can't reconnect to any network. this is solved by rebooting the device
-random crash of systemui, especially when pressing the settings button
-twrp 3.5.2 not booting after flash the rom, only the signed_twrp will work (but not decrypt data) and allow to flash other things
Click to expand...
Click to collapse
- The networking is a bit broken apparently, I already had different report of this. We are working on fixing this.
- This happens when you open the settings button from the Quick Settings view, right? It is broken also on A11, it should work only if you have a PIN/fingerprint configured (for some reason).
- TWRP will need to be updated to support A12 encrypted, yes
Of course, thanks for reporting these issues! Always appreciated, as I cannot test everything by myself
I'm stuck with trying to get ArrowOS to work on my Pixel 2 XL Taimen.
Bootloader is unlocked, I have flashed TWRP 3.6.0_9-0-taimen onto the Pixel.
At some point I was able to move Arrow v12 and GAPPS zip files to the pixel by dragging the files to the phone in Windows. I was able to see the zip files in windows on the phone, but could not see them in TWRP, all the folders had lots of mixed up numbers. Eventually I found the files with File Manager in TWRP, but couldn't do anything with them. I think I have since wiped everything and can't find them now.
on my pc in SDK/platform tools, I can CMD adb devices and see the phone, but if I run fastboot devices, nothing. I have the Google USB driver activated and can see it as an Android Device in Device Manager on windows.
All I can do on the phone is boot to bootloader and get into recovery which takes me to TWRP. If I try to ADB Sideload the ArrowOS zip file to the phone (using sideload in TWRP at the same time) the system just hangs.
Did I just brick my phone? any suggestions on what i can do?
Restore your unit using the full stock ROM package - NOT OTA - from Google. That will get the unit working. To install any ROM you need to do the following.
1. Remove fingerprints and pin numbers from the device. This should disable encryption.
2. In the command prompt boot into TWRP. Do not install unless you want a bootloop.
3. Install Arrow.
As an alternative to 1 above, a USB flash drive with the USB adapter Google includes in the box will also work.
To expand on what @Strephon Alkhalikoi said:
1) TWRP seems unable to handle the encryption used by Android 12, so you probably can't download the new rom to the phone - however sideload should work
2) You should have the baseband and bootloader from the last stock rom installed
3) fastboot devices should work when the phone is in bootloader mode, whereas adb devices works in recovery
4) you may have to format data in TWRP, to clear any incompatible encryption - note that this will delete all the files on your phone
I did the alternative option with a usb drive...worked perfect...thank you so much for helping me!!!
One question...this is my first time installing a custom ROM. I really wanted to try out Android 12 and it is working really well. But my question is, from a security perspective, how secure am I in this mode? not like physical security if someone stole my phone and tried to get in, but secure from online hacking? Will security updates come to me OTA? or will I have to load them from ArrowOS site? I've been on the unsuported updates of Android 11 for a year, so I'm guessing more secure than that?
also, do the Android 12 widgets not come in this ROM, or the GApps ROM? is there a way to get them installed?
bguzz said:
One question...this is my first time installing a custom ROM. I really wanted to try out Android 12 and it is working really well. But my question is, from a security perspective, how secure am I in this mode? not like physical security if someone stole my phone and tried to get in, but secure from online hacking? Will security updates come to me OTA? or will I have to load them from ArrowOS site? I've been on the unsuported updates of Android 11 for a year, so I'm guessing more secure than that?
Click to expand...
Click to collapse
bguzz said:
also, do the Android 12 widgets not come in this ROM, or the GApps ROM? is there a way to get them installed?
Click to expand...
Click to collapse
I believe the ArrowOS developers are working on adding OTA functionality. In the meantime you can flash an update using the USB stick, or you can use adb sideload commands. If you are worried about people accessing your data, a pin and fingerprint lock does wonders.
Which widgets? If you mean the widgets found on the Pixel 6 series, those are exclusive to the Pixel devices: custom ROMs won't have them unless the developer pulls copies from a Pixel 6 / 6 Pro and adds them.
Makes sense. Thank you again.
One thing to make sure if you care about security, is that SElinux is set to enforce. This is an essential security feature that is pretty tedious for the dev to get working, so sometimes it is left as permissive.
Unfortunately, I don't know which roms have enforcing SElinux. If it doesn't say so in the rom's thread, you'll have to install and check.
bguzz said:
If I try to ADB Sideload the ArrowOS zip file to the phone (using sideload in TWRP at the same time) the system just hangs.
Click to expand...
Click to collapse
Try connecting the Pixel 2 XL through a USB hub. I had the same problem in recovery mode and the USB hub solved it.