Related
I have a Samsung Galaxy Tab 10.1 WiFi (SM-T520, picassowifi, n2awifi).
I want to have LineageOS 14.1 (nightly build of 2017-05-18). In comparison to the stock ROM (Android 4.2.2), LineageOS offers me a more current version of Android including "more current" security patches.
Furthermore I already use LineageOS on my smartphone so I am familiar with the LineageOS ROM.
So much for my motivation. Here comes the issue with it...
I went over to wiki.lineageos.org/devices/n2awifi/install to review the installation instructions for LineageOS on my tablet variant (there mentioned as "n2awifi"). I see references to Heimdall which I never was able to properly "install" (more precisely the drivers) so I use my own perfectly working way I describe now:
I went over to download.lineageos.org for receiving the latest (as of 2017-05-25) nightly (only nightlies are available at this time) of LineageOS 14.1 for my tablet variant (there mentioned as "n2awifi"). The version I took was "lineage-14.1-20170518-nightly-n2awifi-signed.zip".
I went over to https://eu.dl.twrp.me/picassowifi/ for receiving the latest (as of 2017-05-25) build of the TWRP recovery image for my tablet variant (there mentioned as "picassowifi"). The version I took was "twrp-3.0.2-0-picassowifi.img.tar".
Edit: 3.1.1 was already out but I discovery random crashes and reboots with it. So I went back to the known stable 3.0.2.
I went over to www.sammobile.com/firmwares/ for receiving the latest (as of 2017-05-25) build of the Odin tools to flash TWRP recovery onto my tablet variant (there mentioned as "SM-T520"). The version I took was "Odin v3.11.1".
I went over to developer.samsung.com to receive the latest (as of 2017-05-25) build of the SAMSUNG Android USB Driver for Windows. The version I took was "Feb 10, 2015".
I went over to opengapps.org for receiving the latest (as of 2017-05-25) build of the OpenGApps package. The version I took was "open_gapps-arm-7.1-nano-20170525.zip".
I downloaded the latest Android Platform Tools directly from Google and extract it into my home directory (Windows). I extend the PATH variable with the directory I just extracted to be able to use just "adb" in any to access the adb application which is now within that extracted directory.
I started my tablet into the Download environment (ODIN mode).
I flashed the TWRP recovery image (tar ball) with Odin.
I restarted my tablet into the Recovery environment (now TWRP).
I wiped out everything on the tablet. using TWRP wipe option. Like system, data, both caches, internal storage.
I startet TWRP's ADB Sideload mode.
I sideloaded the LineageOS ZIP package onto the tablet.
I performed a factory reset. Notice: I did not install any other software (like OpenGApps) onto the tablet.
I performed a restart and complete the LineageOS installation procedure. As of now everything works fine expect that no Google application where installed (like Google Play store for getting apps).
I restartet my tablet into the Recovery environment (TWRP) again and like before wiped out everything.
I startet TWRP's ADB Sideload mode.
I sideloaded the LineageOS ZIP package onto the tablet.
I sideloaded the OpenGApps ZIP package onto the tablet.
I performed a factory reset. Notice: Now GApps are already installed onto my tablet.
I performed a restart and try complete the LineageOS installation procedure. Unfortunately the installation wizard crashes on the second step.
LineageOS welcome screen: <Next>
Language selection: "English (United States)": <Next>
Welcome to your SM-T520 screen: "Set up as new"
Error message: "Setup Wizard has stopped"
Of course there was an option to "Open app again" but this just results into getting to the language selection page again (step 2).
Since I cannot reach the developer tools to enable ADB I cannot access the logs, right?
I this behavior known? How can I supply helpful log files in this situation?
burnersk said:
I this behavior known?
Click to expand...
Click to collapse
Yes.
Setup needs some networking.
Just pull down the status bar and enable wifi.
It becomes possible after error message (step 4 in your post) if I remember correctly.
bbsc said:
Just pull down the status bar and enable wifi.
It becomes possible after error message (step 4 in your post) if I remember correctly.
Click to expand...
Click to collapse
Thank you.
But it only becomes available within the time frame of the black screen after hitting "Open app again". When the language screen is up again the status bar is unavailable again. But if you pulled it down at black screen you will have it.
burnersk said:
When the language screen is up again the status bar is unavailable again.
Click to expand...
Click to collapse
Ok, but you only need it once - just for to enable wifi which is disabled by default for some reason.
[ZE620KL/Android 9][TREBLE] COMPLETE GUIDE: Unlocking, Rooting & Flash GSI + Fixes
Unlocking bootloader to Flashing GSI (Asus Zenfone 5 [ZE620KL] / Android 9.0)
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! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About :
The last guide could leads to soft brick, as the instructions were not clear nor the files not supported for Android 9.0.
Here is a complete guide with TWRP 3.3.0 for Android 9.0, clear instructions and multiple fixes for GSI.
It has been tested on stock version v16.0615.1903.92.
Requirements :
- A stock version V16.0610.XXXX.XX or higher
- A phone on Android 9.0 (not 8.0!)
- A fully working USB cable
- Latest ADB / Fastboot drivers
- Bootloader unlocker (download latest from Asus website or from here)
- TWRP 3.3.0 image
- Android9EncryptionDisablerZE620KL.zip
- Magisk v19.3
Instructions :
Unlocking Bootloader
1. Backup all your important data.
2. Install the bootloader unlocker APK, and follow the steps. You will loss your warranty here, and it will factory reset your data
3. If there is any issue here, go into your stock recovery (volume down + power button) and factory reset.
Installing TWRP
4. Shutdown your device & boot in fastboot mode using volume up + power button.
5. Check that the connection between your device and your computer by typing this in your command line :
Code:
fastboot devices
6. Flash TWRP recovery using :
Code:
fastboot flash recovery <twrp_name>.img
7. Now reboot in recovery mode using :
Code:
fastboot oem reboot-recovery
8. In TWRP, select Wipe > Format Data > enter "yes" and confirm
9. Return to the main menu, select Reboot > Recovery
10. Do 8. & 9. and again
11. Using TWRP or ADB, install Android9EncryptionDisablerZE620KL.zip (on TWRP, go into Install > find Android9EncryptionDisablerZE620KL.zip > Install zip)
If everything has gone successfully, you now have a custom recovery.
As for some GSIs, a patched boot partition may cause bootloop, you should try installing Magisk after installing the GSI. If you want to keep your stock ROM, go directly to "Magisk Installation" section.Installing a GSI
This step may vary depending on the different GSIs distribution. I assume you install Havoc OS v2.7 GSI which actually works on this device.
1. Backup all your important data using TWRP backup.
2. Select the arm64-aonly GSI image you want, and move it on your external SD.
3. Wipe Data, Dalvik, and Cache.
4. Go back in the main menu of TWRP, and reboot to recovery.
5. Remove Magisk if it was previously installed, by using its uninstaller script.
6. Flash the GSI to system partition.
7. Boot and perform a factory reset.
Installing Magisk
1. Add the Magisk zip archive to your external storage.
2. Boot into TWRP recovery, and install the zip.
3. Enjoy!
Bug fixes:
Insufficient storage in the system partition to flash GApps : Download your OpenGApps archive on your external SD, and use MagicGApps 2018.9.23 to install GApps.
Auto-Brightness doesn't work: Download framework-res__auto_generated_rro.apk from here.
Using a root explorer or command-line, push the APK to /vendor/overlay.
Then run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/framework-res__auto_generated_rro.apk
My camera doesn't work well (green tint on face camera) and/or the app doesn't boot: If Asus Camera doesn't launch on your GSI, you should probably edit your /system/build.prob file.
You need to edit ro.product.model, ro.product.brand, ro.product.name, ro.product.device, ro.product.manufacturer & ro.build.product properties to be:
Code:
ro.product.model=ASUS_X00QD
ro.product.brand=asus
ro.product.name=WW_Phone
ro.product.device=ASUS_X00QD
ro.product.manufacturer=asus
ro.build.product=ZE620KL
You can instead use Google Camera mod (port from Arnova8G2 & modded by 5Z community, thanks to them!), which works well (edit: there is a bug on HavocOS, we can't access settings).Bonus:
- You can reinstall DTS Headphone:X here.
- For booting your kernel in Permissive mode, check here
Sources:
TWRP 3.3.0 : On GitHub
If you need help or if you want to help on ZE620KL development go here:
https://t.me/Zenfone5Dev
(We will continue to update & help here though.)
Many thanks to all of the Zenfone 5 community (particularly Emincan, Pandolfi and Lmajkej),
Phhusson & Erfan for their works on GSI, and Shakalaca for its work on TWRP 3.3.0!
On HavocOS v2.8 GSI (13-08-2019):
It works:
- Almost anything
- Adaptive Brightness (after manual fix)
- Notch overlay
- DTS Headphone X (after manual installation)
- NFC
- Face unlock
- Stock camera (after manual fix)
- Magisk
- SDcard access
It doesn't works:
- VoLTE / VoWifi
- Google Camera settings
- External speaker amplifier (NXP amp)
- APT-X / APT-X HD bluetooth
- Low microphone in normal use
- No microphone in calls (only headphone microphone works)
GCam settings
But my google camera keep crashing when I want to go into camera settings
Hi thanks for this tutorial, this is my first time rooting my phone. I'm encountering a problem with my sd card after installing havoc os, everytime i try to move, save or any write functionality i do to my sd card, it always says the android version isn't compatible. I could still see my files from my sd, but everytime it asks permission it always say this
bentley0928 said:
But my google camera keep crashing when I want to go into camera settings
Click to expand...
Click to collapse
Same issue here. I will update the thread when I will find a more working GCam port (perhaps, this GCam port works well on ZenUI)
Jolo110 said:
Hi thanks for this tutorial, this is my first time rooting my phone. I'm encountering a problem with my sd card after installing havoc os, everytime i try to move, save or any write functionality i do to my sd card, it always says the android version isn't compatible. I could still see my files from my sd, but every time it asks permission it always say this
Click to expand...
Click to collapse
It's a known issue, the GSI maintainer @vince31fr is working on it. I don't have it, but I can advice you to use Solid File Manager, which works like a charm on my device.
"- No microphone in calls (only headphone microphone works)"
Funny... I'm on stock latest firmware and I have this issue, so I thought I try something new, and this has that issue. It can't be a coincidence. Something is ****ed up with this device.
Wonder if this will work for the Zenfone 5 Lite (or 5Q)? I wanna root my 5Q so bad haha
Thanks for the great instructions! Steps 1 through 11 worked perfectly for me, then I installed LineageOS (lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img) and it works properly. Then when I go back to TWRP and install Magisk v20.1 it reboots into an endless Lineage bootup logo animation (not boot loop). I can get an adb shell, but now also the external SD card has become invisible. Any suggestions?
UPDATE: I switched over to the patched Magisk version from PHH (https://forum.xda-developers.com/zenfone-5/general/ze620kl-add-support-to-evey-android-9-t3966918) and everything works perfectly now!
Hi!! I thanks for these instructions you gave. I know this post is a bit older. But is the only one I think could help me.
I got an ZE620KL and I'm trying to root this device. I have some experience in unlocking bootloader and rooting devices. But this one... Is giving me a lot of work. Researching in a lot of forums and websites I tried a lot of things with no success. In theory, is just install the official apk provided by ASUS and run the application. But the app doesn't work for a long time as I researched (error accusing network problem). I tried unlock via fastboot commands but I always got stucked by "remote: permission denied" even with latest drivers and ADB Fastboot installed. And yes... I let my device with no one security feature enabled and didn't worked. I tried everything even after wiped data / cache and factory reset and no progress.
In my researches, I realized something about 'oem unlock'. It appears to be the key to solve this. And I guess the tool to work with this is the damn unlock tool from ASUS which don't work! Also, I've heard about workaround with Magisk by flashing a custom recovery to achieve the root. Magisk no longer supports zip files to flash. Only '.img' and '.tar' files. I'd like to find some light here... I don't know what to do. I appreciate any help!
Hello do I need to flash Android9EncryptionDisablerZE620KL.zip if Im gonna flash a non-GSI custom ROM? Or its only for GSI Treble ROM?
[email protected] said:
Hi!! I thanks for these instructions you gave. I know this post is a bit older. But is the only one I think could help me.
I got an ZE620KL and I'm trying to root this device. I have some experience in unlocking bootloader and rooting devices. But this one... Is giving me a lot of work. Researching in a lot of forums and websites I tried a lot of things with no success. In theory, is just install the official apk provided by ASUS and run the application. But the app doesn't work for a long time as I researched (error accusing network problem). I tried unlock via fastboot commands but I always got stucked by "remote: permission denied" even with latest drivers and ADB Fastboot installed. And yes... I let my device with no one security feature enabled and didn't worked. I tried everything even after wiped data / cache and factory reset and no progress.
In my researches, I realized something about 'oem unlock'. It appears to be the key to solve this. And I guess the tool to work with this is the damn unlock tool from ASUS which don't work! Also, I've heard about workaround with Magisk by flashing a custom recovery to achieve the root. Magisk no longer supports zip files to flash. Only '.img' and '.tar' files. I'd like to find some light here... I don't know what to do. I appreciate any help!
Click to expand...
Click to collapse
Im not sure if you still have your phone or you have successfully unlocked bl. but I found an updated version of their tool which works.
*tried unlocking from android 10 not working, it says device model not supported*
Zenfone 5 Unlock BL
cf100clunk said:
Thanks for the great instructions! Steps 1 through 11 worked perfectly for me, then I installed LineageOS (lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img) and it works properly. Then when I go back to TWRP and install Magisk v20.1 it reboots into an endless Lineage bootup logo animation (not boot loop). I can get an adb shell, but now also the external SD card has become invisible. Any suggestions?
UPDATE: I switched over to the patched Magisk version from PHH (https://forum.xda-developers.com/zenfone-5/general/ze620kl-add-support-to-evey-android-9-t3966918) and everything works perfectly now!
Click to expand...
Click to collapse
Do you still have the patched Magisk zip file, the original link in the post seems not working
Hi
I have installed Lineage Os 16 custom rom for Poco F1.
But the problem is i can't root the device.
I have downloaded the magisk 20.1 zip and the Disable-Force-Encryption-Treble.zip from:
https://magisk.me/root-xiaomi-poco-f1-using-magisk/
I enter the TWRP , i flashed first the disable force encryption zip, i rebooted to twrp , i flashed the magisk and i rebooted the device,
Magisk manager installed properly but when i tap Safety Net Check Success i get the ctsProfile:false.
Rootchecker also gives me the message that root is not properly installed.
Any ideas but if possible without having to format data .
I also tried (after another members suggestion) to flash magisk 19.4, canary magisk but with no results.
thank you in advance
First of all: keep it simple. Set screen lock to swipe. That avoids encryption too. Go twrp and wipe system and re-flash ROM (and GApps if needed) that restores boot image.
Second: try rooting with lineageOS native addonsu from download/extras. Enable it in developer options.
Hello, I would need help to root my device, if someone could bring me advice I'm taking, I own remote control software if it tempts someone to help me I'm up for it
Have you unlocked the bootloader and install TWRP first?
The bootloader is unlocked, TWRP is not installed, I had to read the forums to try to install TWRP but my phone is stuck on fastboot impossible to do anything
You can root very easily:
1. start the phone in fastboot mode
2. from a PC type command "fastboot boot twrp.img"
3. once in TWRP, install magisk.zip file (don't forget to follow new instructions for Magisk v22)
4. once Magisk has been installed, reboot to system
5. congrats, your phone is rooted now (without TWRP permanently installed)
hello
after updating to android 11, euxm version, I have problems rooting with magisk 22, I change the apk extension to zip, I install it from twrp, but on reboot it crashes and returns to twrp.
also i no longer see the internal memory folders in android - data
carabot said:
hello
after updating to android 11, euxm version, I have problems rooting with magisk 22, I change the apk extension to zip, I install it from twrp, but on reboot it crashes and returns to twrp.
also i no longer see the internal memory folders in android - data
Click to expand...
Click to collapse
You might have incompatible module installed (for example SafetyNet fix) - disable all modules temporarily, install Magisk and see if the phone starts.
I disabled all the modules before installing the recovery rom, however there is the uninstall of magisk 22.0 and safetynet fix?
carabot said:
I disabled all the modules before installing the recovery rom, however there is the uninstall of magisk 22.0 and safetynet fix?
Click to expand...
Click to collapse
Can you start the phone without Magisk installed?
yes
I solved by disabling modules from orange fox recovery,
how can i do to see the contents of the android folder, that is scoped storage?
carabot said:
yes
I solved by disabling modules from orange fox recovery,
how can i do to see the contents of the android folder, that is scoped storage?
Click to expand...
Click to collapse
You are contradicting yourself a little, you said that you disabled all modules before recovery ROM installation, now that you disabled them from Orange recovery. It might help to describe steps which you did and current status of your phone.
I had disabled them from magisk, but in the twrp they were active, and when I realized it I disabled them from twrp and I solved them.
p. s.
safetynet fix is compatible with android 11 and magisk 22?
i wouldn't ruin it again
carabot said:
I had disabled them from magisk, but in the twrp they were active, and when I realized it I disabled them from twrp and I solved them.
p. s.
safetynet fix is compatible with android 11 and magisk 22?
i wouldn't ruin it again
Click to expand...
Click to collapse
Yeah just hide magisk from all google apps and it will work fine, mine passes
Jooan92 said:
Hello, I would need help to root my device, if someone could bring me advice I'm taking, I own remote control software if it tempts someone to help me I'm up for it
Click to expand...
Click to collapse
Unlock bootloader
Flash a recovery (fastboot flash recovery nameofrecovery.img)
Reboot into recovery (fastboot reboot and hold power and volume up)
Load magisk zip on an EXTERNAL SD find it and flash
Boom
for scoped storage is there a solution?
carabot said:
I had disabled them from magisk, but in the twrp they were active, and when I realized it I disabled them from twrp and I solved them.
p. s.
safetynet fix is compatible with android 11 and magisk 22?
i wouldn't ruin it again
Click to expand...
Click to collapse
You need to reinstall safetynet fix after Android upgrade, installation script uses different files for different Android versions.
What issue exactly do you have with storage?
after the update open file manager and if I click on android - date I no longer see the folders
i tried to install safetynetfix from twrp but it gives me error
carabot said:
i tried to install safetynetfix from twrp but it gives me error
Click to expand...
Click to collapse
Install from magisk under the modules section, then install from storage
gave me mistake because i had wrong files
Just for notification. If safety net is important with you. Install latest stable xiaomi.eu rom v12.0.11.0. Safety net is passed and implement in rom. I 've installed it...Developers continue playing cat and mouse with Google
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