{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/12.1/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (from download page, recovery button)
NikGapps core (Download from here - note that you may also need setup wizard addon if you rely on Google restore)
Magisk root (after first boot)
First time installation:
Backup your data to PC, OTG flash drive
Boot to fastboot and flash recovery
Code:
fastboot flash recovery recovery.img
Now boot to recovery by holding VOL UP + POWER
Navigate to Factory reset and format data, wipe cache and wipe system
Now reboot to recovery
Navigate to Apply update and choose from adb (if you have crDroid.zip on external sdcard, you may choose this option and navigate to where the zip is)
Now sideload crDroid zip
Code:
adb sideload crDroid.zip
If you are running with gapps, choose again to apply from adb and sideload gapps.zip
Reboot to system
Update installation:
Via recovery
Boot to recovery
Navigate to Apply update and choose from adb (if you have crDroid.zip on external sdcard, you may choose this option and navigate to where the zip is)
Now sideload crDroid zip
Code:
adb sideload crDroid.zip
Via OTA:
Go to Settings -> System -> Updater and download latest build
Choose install and let it finish
Reboot
Do note that crDroid 8 is encrypted by default, so if you want to run decrypted, you'll need to sideload dfe.zip
Sources:
ROM: https://github.com/crdroidandroid
Kernel source: https://github.com/crdroidandroid/android_kernel_xiaomi_sdm845
Download:
ROM https://crdroid.net/beryllium
Known isues:
- none critical
Visit official website @ crDroid.net
crDroid Poco Telegram
crDroid Community Telegram
If you like my work, consider a donation > My Paypal
The installation worked liked charm. Thank you so much!!
Thanks for your work Gabriel! Wonderful, I'm glad the ROM is finally encrypted by default
Bug: Bluetooth is trying to turn on and off, repeatedly.
Overall, it feels like a LOS developer build with unlocked features.
HI GWOLFU TNX IN ADVANCE
im not be able to root
flash latest magisk apk or zip no difrens beetwin apk and zip
Sia_scazy said:
HI GWOLFU TNX IN ADVANCE
im not be able to root
flash latest magisk apk or zip no difrens beetwin apk and zip
Click to expand...
Click to collapse
Needs magisk canary
That has support for A12
a9k1t said:
Bug: Bluetooth is trying to turn on and off, repeatedly.
Overall, it feels like a LOS developer build with unlocked features.
Click to expand...
Click to collapse
Aware from telegram chat
Will try to fix with next update
Thanks
Best rom.
Thanks gwolfu! I'd love to upgrade this week, but I've got a few questions first:
Is a dirty flash upgrade from crDroid 7 supported?
I had issues with nikgapps before, with the signal app not receiving any messages unless I open the app (nikgapps specific issue). I'd like to try bitgapps instead. your rom should also work well with that gapps pack, right?
I use encrypted f2fs data partition right now. is that also supported by this crdroid 8 build? or do I have to update the fstab again?
Does it pass safetynet (with/without magisk)?
Oehr said:
Thanks gwolfu! I'd love to upgrade this week, but I've got a few questions first:
Is a dirty flash upgrade from crDroid 7 supported?
I had issues with nikgapps before, with the signal app not receiving any messages unless I open the app (nikgapps specific issue). I'd like to try bitgapps instead. your rom should also work well with that gapps pack, right?
I use encrypted f2fs data partition right now. is that also supported by this crdroid 8 build? or do I have to update the fstab again?
Does it pass safetynet (with/without magisk)?
Click to expand...
Click to collapse
1. Not possible to dirty flash
2. Should work with other gapps (I just shared what I used, however not tested by me)
3. F2FS data is not added yet due to some bug I've noticed
4. Passed SN out of the box even without magisk
Build 20200124 is up
Changelog
- Fixed bluetooth issues
There is an issue with the recovery: it does not automount the micrsod card. manually mounting using adb shell works, but as I am not sure where to mount it, I have no means of applying the update from the microsd card.
P.S. I am using a 1TB microSD card with a single exfat partition
gwolfu said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/12.0/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (here)
NikGapps core (Download from here)
Magisk root (after first boot)
First time installation:
Backup your data to PC, OTG flash drive
Boot to fastboot and flash recovery
Code:
fastboot flash recovery recovery.img
Now boot to recovery by holding VOL UP + POWER
Navigate to Factory reset and format data, wipe cache and wipe system
Now reboot to recovery
Navigate to Apply update and choose from adb (if you have crDroid.zip on external sdcard, you may choose this option and navigate to where the zip is)
Now sideload crDroid zip
Code:
adb sideload crDroid.zip
If you are running with gapps, choose again to apply from adb and sideload gapps.zip
Reboot to system
Update installation:
Boot to recovery
Navigate to Apply update and choose from adb (if you have crDroid.zip on external sdcard, you may choose this option and navigate to where the zip is)
Now sideload crDroid zip
Code:
adb sideload crDroid.zip
Do note that crDroid 8 is encrypted by default, so if you want to run decrypted, you'll need to sideload dfe.zip
Sources:
ROM: https://github.com/crdroidandroid
Kernel source: https://github.com/crdroidandroid/android_kernel_xiaomi_sdm845
Download:
ROM https://crdroid.net/beryllium
Known isues:
- none critical
Visit official website @ crDroid.net
crDroid Poco Telegram
crDroid Community Telegram
If you like my work, consider a donation > My Paypal
Click to expand...
Click to collapse
Bug bluetooth.....not working
wladoom said:
Bug bluetooth.....not working
Click to expand...
Click to collapse
Works fine for me with Build 20200124:
gwolfu said:
Build 20200124 is up
Changelog
- Fixed bluetooth issues
Click to expand...
Click to collapse
gwolfu said:
1. Not possible to dirty flash
2. Should work with other gapps (I just shared what I used, however not tested by me)
3. F2FS data is not added yet due to some bug I've noticed
4. Passed SN out of the box even without magisk
Click to expand...
Click to collapse
as for bitgapps: doesn't work. It fails mounting the vendor partition. tried nikgapps now and receiving message in signal seems to work for now. only time will tell!
as for f2fs, the mounting parameters for encryption differ. I didn't check out the fstab yet, but for crdroid 7, I had to remove the ext4 mount for /data and leave only f2fs with the following permissions in there:
Code:
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,background_gc=off,fsync_mode=nobarrier latemount,wait,fileencryption=ice,quota
And even then it was wonky: it only worked when the data partition was COMPLETELY empty, so that encryption was enabled on first boot. encrypting afterwards failed. Maybe that helps you in troubleshooting f2fs support for data.
P.S. Unless it goes mainline again, I'll stick with the current ext4 variant, as I had to patch fstab every time I updated the rom back with crdroid 7...
Hey, huge thanks for crDroid, currently on 7.13, will flash 8 this weekend. I've noticed that when hiding nav bar, the back gesture doesn't work anymore and haven't find out how to fix this (7.13 version though). Did I miss something ?
Oehr said:
Works fine for me with Build 20200124:
as for bitgapps: doesn't work. It fails mounting the vendor partition. tried nikgapps now and receiving message in signal seems to work for now. only time will tell!
as for f2fs, the mounting parameters for encryption differ. I didn't check out the fstab yet, but for crdroid 7, I had to remove the ext4 mount for /data and leave only f2fs with the following permissions in there:
Code:
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,background_gc=off,fsync_mode=nobarrier latemount,wait,fileencryption=ice,quota
And even then it was wonky: it only worked when the data partition was COMPLETELY empty, so that encryption was enabled on first boot. encrypting afterwards failed. Maybe that helps you in troubleshooting f2fs support for data.
P.S. Unless it goes mainline again, I'll stick with the current ext4 variant, as I had to patch fstab every time I updated the rom back with crdroid 7...
Click to expand...
Click to collapse
you can't encrypt afterwards
you either do it at first boot (does that automatically in crDroid 8), or you flash DFE and no encryption from there on
also no real benefits in F2FS imo
gwolfu said:
you can't encrypt afterwards
you either do it at first boot (does that automatically in crDroid 8), or you flash DFE and no encryption from there on
also no real benefits in F2FS imo
Click to expand...
Click to collapse
f2fs has been specifically developed for flash memory. it comes with fs-based wear leveling which is great for flash memory without a proper flash controller (microsd cards, emmc, etc.). Some more recent android phones (e.g. pixel 6, poco x3) use f2fs as its default fs for the data (and cache) partition.
Makigo123 said:
Hey, huge thanks for crDroid, currently on 7.13, will flash 8 this weekend. I've noticed that when hiding nav bar, the back gesture doesn't work anymore and haven't find out how to fix this (7.13 version though). Did I miss something ?
Click to expand...
Click to collapse
do not disable nav bar. switch to gesture bar and set its size to compact and/or disable navigation hint instead. i stumbled into the same "issue" in crdroid 8, until i figured out that I was doing it wrong. It is confusing, as all these options are split between basically three different screens.
Oehr said:
do not disable nav bar. switch to gesture bar and set its size to compact and/or disable navigation hint instead. i stumbled into the same "issue" in crdroid 8, until i figured out that I was doing it wrong. It is confusing, as all these options are split between basically three different screens.
Click to expand...
Click to collapse
Thanks, you made my day brighter
Unfortunately, I have the issue with receiving message in the Signal app again: After a while, especially while not charging, signal stops receiving messages on the phone unless I specifically open the signal app again...
I checked the usual culprits, such as battery optimization and such, but everything checks out... I had the issue before with crdroid back when I also tried nikgapps... There was no issue when I later switched to opengapps, but that is not possible for now.
Any clue as to how to fix this? I really don't want to check my signal app all the time
Oehr said:
Unfortunately, I have the issue with receiving message in the Signal app again: After a while, especially while not charging, signal stops receiving messages on the phone unless I specifically open the signal app again...
I checked the usual culprits, such as battery optimization and such, but everything checks out... I had the issue before with crdroid back when I also tried nikgapps... There was no issue when I later switched to opengapps, but that is not possible for now.
Any clue as to how to fix this? I really don't want to check my signal app all the time
Click to expand...
Click to collapse
issue is with nikgapps
should be fixed in latest build released today
if dirty flashing new gapps on top, do also clear app data of Google Play Services app and reboot after dirty flash done and booted
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for Honor View 10 [berkeley]
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 9.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
NFC
Lights
Sound / vibration
Facelock
Known issues
Nothing
DON'T FLASH GAPPS, ALREADY INCLUDED
Download from my mirror
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Telegram channel
Stay tuned
XDA:DevDB Information
PixelExperience Pie, ROM for the Honor View 10
Contributors
Codebucket, jhenrique09, GtrCraft
Source Code: https://github.com/PixelExperience
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader, EMUI 9
Based On: AOSP
Version Information
Status: Stable
Created 2018-11-14
Last Updated 2019-07-13
DON'T FLASH IF YOU ARE ALREADY ON EMUI 9, IT WON'T BOOT!!
IMPORTANT!
Before you start flashing, make sure you are using a version of TWRP with encryption disabled, otherwise you might end up using eRecovery to rescue your device from a bootloop!
You can also use official TWRP, but it will only work until you have not flashed the ROM!
Unofficial TWRP: https://storage.codebucket.de/public/twrp-3.2.2-0-berkeley.img
(That's not mine actually, I found that on Telegram and uploaded it to my mirror)
Flashing instructions from stock EMUI
Make sure you have TWRP installed and working!!
Reboot phone into recovery mode
Go to "Wipe" and select "Format data", then confirm with yes (some devices might require to disable encryption, see post #54)
Then go to "Advanced" and select /system, /data, /cache and Dalvik-cache for wipe
Copy ROM zip over to your phone (use whatever works for you, I personally use adb push)
Go to "Install" and select the ROM zip (and Magisk if you want), swipe to flash
Done! You can now reboot to system.
Update instructions
Simply go to TWRP and wipe /system, /cache and Dalvik-cache, then flash the update ROM zip and all additional stuff you need.
I also recommend having a backup of boot ramdisk to install Magisk again on a stock boot ramdisk.
Where is the source code of the device tree?
I combined all commits needed to run this ROM into one organization, you can inspect the source code here:
https://github.com/berkeley-pie
Device tree used for this ROM: https://github.com/divadsn/android_device_huawei_berkeley
My submitted patches: https://gerrit.pixelexperience.org/#/q/topic:huawei-derps+(status:open+OR+status:merged)
Special thanks go to @flex1911, @sirhc and @LuK1337 for your hard work, without your commits I wouldn't be able to get this ROM booting for the Honor View 10!
Where are the experimental builds gone?
They are still available on my mirror: https://mirror.codebucket.de/pixelexperience/berkeley/experimental/
But please be aware that those aren't official and you will loose OTA support!
Screenshots
Tried downloading about 6 times with different browsers. Fails at about 80m or so.
thecdn said:
Tried downloading about 6 times with different browsers. Fails at about 80m or so.
Click to expand...
Click to collapse
Try downloading using a download manager, Cloudflare sometimes looses connections.
Hi, is there a guide to follow for installing this rom? I read aosp and i thought to flash system.img through fastboot with stock recovery but i found many files and system is a .br file. Do i need twrp?
Thanks
How do you get this to boot? I have L09 and have wiped all partitions via twrp and stock recovery yet still bootlooping. I have even tried adb sideload and nothing.
passion8059 said:
How do you get this to boot? I have L09 and have wiped all partitions via twrp and stock recovery yet still bootlooping. I have even tried adb sideload and nothing.
Click to expand...
Click to collapse
You need to format data and remove encryption. The procedure is as follow: Download stock firmware using eRecovery, flash TWRP, format data in wipe, reboot TWRP and flash ROM.
Will include some instructions to the #2 post soon.
Codebucket said:
Flashing instructions
Reboot phone into recovery mode
Go to "Wipe" and select "Format data", then confirm with yes
Then go to "Advanced" and select /system and /data for wipe
Return back to home and go to "Settings" to enable "Remove instead formatting"
Go back to "Wipe" => "Advanced" and select /cache and Dalvik-cache to wipe
Reboot to recovery and connect to your PC via USB
Select "Advanced" and "Adb Sideload" to start flashing
On your PC open a terminal and type "adb sideload update.zip", hit enter
Now repeat that procedure if you want to flash Magisk
Done! You can now reboot to system.
Click to expand...
Click to collapse
So dalvik/art cache are to be removed and data and system are formatted?
'update.zip' is the generic name for your rom?
Do the rom and magisk have to be sideloaded? They can't be flashed via twrp?
thecdn said:
So dalvik/art cache are to be removed and data and system are formatted?
'update.zip' is the generic name for your rom?
Do the rom and magisk have to be sideloaded? They can't be flashed via twrp?
Click to expand...
Click to collapse
Update.zip is the placeholder, you have to type the path yourself to the downloaded file. Also sideload is a feature in TWRP.
Codebucket said:
IMPORTANT!
Before you start flashing, make sure you are using a version of TWRP with encryption disabled, otherwise you might end up using eRecovery to rescue your device from a bootloop!
Unofficial TWRP: https://storage.codebucket.de/public/twrp-3.2.2-0-berkeley.img
(That's not mine actually, I found that on Telegram and uploaded it to my mirror)
Flashing instructions
Reboot phone into recovery mode
Go to "Wipe" and select "Format data", then confirm with yes
Then go to "Advanced" and select /system and /data for wipe
Return back to home and go to "Settings" to enable "Remove instead formatting"
Go back to "Wipe" => "Advanced" and select /cache and Dalvik-cache to wipe
Reboot to recovery and connect to your PC via USB
Select "Advanced" and "Adb Sideload" to start flashing
On your PC open a terminal and type "adb sideload update.zip", hit enter
Now repeat that procedure if you want to flash Magisk
Done! You can now reboot to system.
Click to expand...
Click to collapse
but it keeps rebooting brother
Install Question
Very much curious, why couldn't we simply flash the rom through TWRP? Why through ADB Sideload? Just curious, since I've only ever used sideload for official ROMs, but never for custom ones Will try this out soon though! Love Pixel Experience ROMs! Thank you for the hard work!
Is volte working in this Rom?
Gesendet von meinem BKL-L09 mit Tapatalk
mgs250 said:
Very much curious, why couldn't we simply flash the rom through TWRP? Why through ADB Sideload? Just curious, since I've only ever used sideload for official ROMs, but never for custom ones Will try this out soon though! Love Pixel Experience ROMs! Thank you for the hard work!
Click to expand...
Click to collapse
You flash the ROM using ADB Sideload because the TWRP I have used has not working MTP, therefore I have no other way to copy the ROM over. But if you have a version of TWRP which works with Pie and has working MTP then go ahead
Tk19882401 said:
Is volte working in this Rom?
Gesendet von meinem BKL-L09 mit Tapatalk
Click to expand...
Click to collapse
No, there is no fix for that yet.
Ashinnazer said:
but it keeps rebooting brother
Click to expand...
Click to collapse
Have you formatted data and removed encryption?
Update available!
This is hopefully the last unofficial build, as I have pushed the patches made by flex1911 to PixelExperience Gerrit, so we can apply for official device status.
Oh and this build has fixed a derp I made when I cherry-picked a patch, sorry
Download: https://mirror.codebucket.de/pixele...nce_berkeley-9.0-20181116-0926-UNOFFICIAL.zip
Changelog: https://mirror.codebucket.de/pixele...ey-9.0-20181116-0926-UNOFFICIAL-Changelog.txt
(I also tweaked around with some NGINX settings to improve download stability )
Does this ROM work on BKL09 with EMUI Oreo 8.0?
sbtourist said:
Does this ROM work on BKL09 with EMUI Oreo 8.0?
Click to expand...
Click to collapse
Should work, but I can't guarantee, I use a BKL-L04.
Does wifi hotspot work?
Nice work! Working great on BKL-L04 flashed on top of GPU Turbo update.
Next update, should disable nav bar when registering fingerprint. Part of my thumb keeps hitting the home button.
Edit- after registering FP in security settings, device went black and became unresponsive.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* 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 doing this to your device
* 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.
*/
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch-driven user interface, with no more volume rocker or power buttons to mash. The GUI is also fully XML-driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open-source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Pease note! TWRP cannot currently decrypt any A12 ROM on any device. This is a known issue as AOSP changed the way encryption keys are stored. If a new workaround isn't found? TWRP may never decrypt again... We recommend removing lockscreen security, rebooting to TWRP, make your changes and then reboot to system and setup your lockscreen security again.
This is for OFFICIAL and BETA builds of TWRP for the Motorola Moto X4 (payton)
Stable Downloads:
https://twrp.me/motorola/motorolamotox4.html
Test Downloads:
https://osdn.net/projects/twrp-for-payton/releases/
Sources:
Official: https://github.com/TeamWin/android_device_motorola_payton
Tests: https://github.com/ThEMarD/android_device_motorola_payton-twrp
Platform Tools (adb/fastboot):
https://developer.android.com/studio/releases/platform-tools.html#download
Installation:
Make sure your bootloader is unlocked
Download the recovery image (and optionally the TWRP installer zip) from above
Reboot into bootloader
Run this command (Change the .img to whatever the name of file is you downloaded):
Code:
fastboot boot twrp-3.4.0-1-payton.img
Optionally at this point, if you want TWRP to be your default recovery? You can install TWRP via the TWRP installer zip. Please note that ROM upgrades overwrite boot which in turn overwrites recovery so this process would need to be repated.
Upgrade instructions
Download desired TWRP installer zip version
Reboot to recovery
Select Install
Tap on install and select the TWRP installer zip you downloaded from step one
Reboot to recovery and confirm that the updated version of TWRP is installed
Nandroid backup/restore
Have an available microSD Card or USB OTG drive
Backup boot, dtbo, system image, vendor image and data (optionally any other partitions you want a backup of) to your external storage device of choice
Once you wish to restore? Reboot to TWRP and format data (Wipe > "format data" button > type yes > keyboard checkbox)
Reboot to TWRP
Restore boot, dtbo, system image and vendor image
Reboot to system
Once it boots to system without issues? Do not set any lockscreen security and reboot to TWRP
Restore data
Reboot to system
After it finishes boot? Your data and ROM will be restore but sometimes the UI might be incorrect, so reboot to system again
For the TEST builds of TWRP? Please let me know if this works. If so? I will submit it to Gerrit for official updates.
Credits:
bigbiff for helping me get setup on on gerrit.twrp.me for official status and updating official TWRP
kaneawk, erfanoabdi for working on TWRP for payton
All the users who tested my builds of TWRP
ok I could literally be here all day typing so essentially anyone who has worked on the Motorola sdm660-common kernel for LineageOS and TWRP
i have seen you are trying to fix encryption in recovery.fstab - please note the file is overwritten from twrp.fstab during runtime, so either remove twrp.fstab or do the changes in there
for working encryption the flags should be written completely, afaik there is no autocomplete in twrp (like in android)
fileencryption=ice:aes-256-cts
---
furthermore i recommend /system_root instead of /system to keep things in line with other devices (although most flashable zips meanwhile can detect SAR)
to avoid `mount /system` (perhaps silently) fail instead of symlink i recommend bind mount (not standard so far, at least haven't seen that in official builds)
Code:
/system_root ext4 /dev/block/bootdevice/by-name/system flags=display="System Root";backup=1;wipeingui;slotselect
/system auto /system_root/system flags=fsflags="bind";backup=0;usermrf;ignoreblkid
---
another change what seems official now and (in request of user @lowerhater) you may include /data/media/0 aka Internal Storage for backup purposes (decision is up to you, external storage is required for backup location)
Code:
/storage auto /sdcard flags=fsflags="bind";display="Internal Storage";backup=1;usermrf;ignoreblkid
Hey thanks!
Any clue if restoring a nandroid backup works on the newest builds?
Heyyo @aIecxs , thanks for the suggestions! For the fstab change before erfan was saying that's optional as mentioning ice was the only important part, but I can definitely put the full description in for payton. FBE decryption on payton is fixed already as I used the same commits that I did to fix it on nash since sdm660 and msm8998 are the exact same CAF tags.
For the /system_root thing? Afaik that was for devices with A-only SAR that use the pie SAR implementation as it doesn't look like beyond1lte is an A/B device like Motorola sdm660 devices are. berkeley would be another example of A-only SAR device using pie's SAR implementation, but sadly though it seems they haven't had TWRP updates since 2019... Tbh I don't really know any other devices like that offhand...
As for that last suggestion? Yes we can implement that too.
ThE_MarD said:
fastboot boot twrp-3.4.0-1-payton.img
Click to expand...
Click to collapse
when i am giving this command
fastboot boot twrp-3.2.1-1-payton.img
downloading 'boot.img'...
its keeps stucks on this.
Heyyo @DARK EMP3ROR , unfortunately it seems Motorola devices are super picky... For me? It wouldn't work on my Windows 10 PC or Ubuntu Mate 20.04 either... My wife's old Windows 7 notebook it worked fine though, so you might need to setup a USB Live Boot for Windows 7 or something to get it going
you can try to figure out with fastboot options like kernel offset etc..
fastboot boot TWRP.img Not working
edit: or boot from bootable slot
aIecxs said:
found another possible reason why fastboot boot won't work when it should.
Exelios said:
Even worse than that "fastboot boot" works only if current slot is not marked as not bootable, so any try to launch TWRP fails once your in this mode.
Click to expand...
Click to collapse
Worth a try checking which slot is flagged bootable and set as active (the one with yes)
Code:
fastboot getvar current-slot
fastboot getvar slot-bootable
fastboot getvar slot-successful
fastboot --set-active=other
Click to expand...
Click to collapse
Heyyo, I have TWRP 3.6.1_11 test10 build up. It's rebased on TWRP-11 branch with source-built bootctrl HAL and libgptutils.
Please note! This will decrypt Android 11 ROMs, but can't decrypt Android 12.x ROMs unless you remove your lockscreen security first within the ROM before rebooting to TWRP. Currently TWRP does not have a method to decrypt A 12.x ROMs so this isn't a bug specific to payton.
Release twrp-for-payton twrp-3.6.1_11-test10-payton - twrp-for-payton - OSDN
Release twrp-for-payton twrp-3.6.1_11-test10-payton - twrp-for-payton #osdn
osdn.net
Your test 3.6.1_11 test 10 build with lineageOS 19.1 does boot when I use 'fastboot boot <file>', but it cannot unencrypt the drive like 3.5.0_9 was doing on lineageOS 18.1. this is the same behavior I see with the default 3.6.0_9.img file from twrp.me for Payton. All the 3.5.x versions of twrp get stuck booting and I never get far enough to enter a pin. I can't compare against the lineage recovery from the 19.1 test build, as whenever I try a fastboot of that img file, it just boots lineageOS rather than recovery, which seems weird given it works for twrp.
ThE_MarD said:
Heyyo, I have TWRP 3.6.1_11 test10 build up. It's rebased on TWRP-11 branch with source-built bootctrl HAL and libgptutils.
Release twrp-for-payton twrp-3.6.1_11-test10-payton - twrp-for-payton - OSDN
Release twrp-for-payton twrp-3.6.1_11-test10-payton - twrp-for-payton #osdn
osdn.net
Click to expand...
Click to collapse
The previous version prevented me from booting into the rom I installed. Will this work?
Heyyo @jtnc , the twrp.img file is only meant for temporary use (fastboot boot) and then install the twrp-installer.zip to install TWRP to both slots. Please check the installation instructions. Installing the twrp.img will overwrite your kernel which will break the installed ROM.
It didn't decrypt LOS 18.1 for you? That's odd, other users confirmed it did.
@Dukenukemx I confirmed on my payton it works. As I mentioned, the problem before with TWRP builds was the prebuilt bootctrl HAL and libgptutils.
Here is the latest pre-official TWRP test builds from their build server.
TWRP image:
https://build.twrp.me/twrp-3.6.1_11-0-payton.img
TWRP installer zip:
https://build.twrp.me/twrp-installer-3.6.1_11-0-payton.zip
Please test these. If they are confirmed as working? I will ask for a new official TWRP build for payton.
I understand the .img file is only for temporary use (fastboot) and that was all I was using it for. I could fastboot with the twrp 6.1 test10 image fine, but it would not decrypt. As such I did not bother installing it and stayed on 3.5.0_9. I did eventually realize my sdcard was not encrypted (d'uh!) and was able to flash the lineage recovery w/o a problem. I can't see the bulitin storage with lineage, so I'm assuming it's not decrypting either (nor did it prompt).
Using fastboot boot (so .img files for all), I saw:
twrp < 3.6 -- hangs on the twrp boot screen
twrp 3.6 -- fails to decrypt, but boots fine otherwise
lineeageOS recovery (any) -- boots to OS not to recovery when running 'fastboot boot lineage....recovery.img
I will try the official build you just posted later today when I can get back to my old laptop.
I just tried out the 3.6.1_11-0-payton.zip version of twrp on the official build server you pointed me at. It had the same results as with your test build, namely it does not decrypt internal storage for me. Probably worth someone else validating - assuming others are encrypted.
Since all the 3.5 series hang for me, I tried rolling back to an older version that used to work with encryption, namely a 3.3.3_1 version by Syberhexen, but it too failed decryption. I haven't looked at how encryption works, but it makes me wonder if something changed in 19.1 related to it.
18.1 encrypted worked fine with 3.5.0_9. I can't recall if I was running 3.5.0_9 or the 3.3.3_1 syperhexen version with 17.1/HavocOS.
Depending on how time goes this weekend, I might try rolling back to 18.1 and see if your build will decrypt that or not.
@jtnc, just to check, are you using FBE and not FDE for encryption methods? I just formatted the data on my payton and wiped dalvik and flashed LOS 18.1 and tested both via fastboot boot twrp-3.6.1_11-0-payton.img and adb sideload twrp-installer-3.6.1_11-0-payton.zip and both booted fine and I could PIN decrypt my LOS 18.1 ROM
It does take a minute or three to boot into TWRP, so I do recommend giving it a bit of time for decryption to work.
As I mentioned above though, TWRP cannot currently decrypt A12.x ROMs, so users MUST remove lockscreen security in the ROM before rebooting to TWRP.
Will there some time be a chance to decrypt A12 ROMs with lockscreen security by TWRP?
Thanks for an answer.
Heyyo @woodpe, from my understanding? Android 12.1 changes the way security key storage works, so the path that TWRP usually uses for decryption does not exist... so unless a new solution is found? Potentially TWRP might never decrypt lock screen security ever again...
Please test the pre-official TWRP build from their built server.
TWRP image:
https://build.twrp.me/twrp-3.6.1_11-0-payton.img
TWRP installer zip:
https://build.twrp.me/twrp-installer-3.6.1_11-0-payton.zip
If they are confirmed as working? I will ask for a new official TWRP build for payton.
I'm using lineageos19.1 in combination with the pre-offical TWRP.
All works fine, but no decryption.
@woodpe for A12 ROMs? You must remove lockscreen security, reboot to TWRP, make changes, reboot to system and then setup your lockscreen security again
ThE_MarD said:
Heyyo @woodpe, from my understanding? Android 12.1 changes the way security key storage works, so the path that TWRP usually uses for decryption does not exist... so unless a new solution is found? Potentially TWRP might never decrypt lock screen security ever again...
Click to expand...
Click to collapse
I think this is the problem I've been seeing then. I think I was hoping your test build fixed that problem! All my decryption issues with TWRP have occurred after moving to LineageOS 19.1. I did not have a chance to roll back to 18.1 and revalidate the 3.6.1 build you posted over the weekend, but given the above comment and your experiment on 18.1 I'd expect it to work fine for me.
Removing the lock screen pin and rebooting to recovery worked fine with 19.1 and TWRP 3.6.1_11, I have not tried it on TWRP 3.5.0_9. It's a bit annoying that you have to redo fingerprints every time you remove the lock screen security (at least for PIN, I assume that's true for any).
But given that TWRP 3.6.1 is not expected to work well PIN and 19.1, I'd say go ahead and make 3.6.1_11 official. The only thing I haven't tried is a complete ROM install but I was able to flash recover and other zips from it fine.
Question, would it be worth adding a note to maybe the second post of the lineageOS 19.1 thread indicating TWRP + 19.1 + lockscreen PIN does not currently work?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices,
* 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.
*/
What's working :
Everything that worked in last OFFICIAL build.
There are NO MODIFICATIONS at all. If something didn't work in the last official LineageOS release, it wont work in this build.
Instructions :
Download build and copy it to Internal Memory
Reboot to TWRP recovery
Create TWRP Backup (Recommended)
Flash the latest build (Clean Flash if coming from any other build)
Flash Magisk/LineageSU zip (Optional)
Flash GApps/MicroG (Optional)
Reboot
Downloads :
deb
Build: lineage-14.1-20230514-UNOFFICIAL-deb.zip
MD5: 534dff964ca9c44a8ab00e6a6d3883f9
flo
Build: lineage-14.1-20230514-UNOFFICIAL-flo.zip
MD5: 66a094b14a1f1531af1d195bf787a03b
TWRP
deb: twrp-3.4.0-0-deb.img
flo: twrp-3.4.0-0-flo.img
followmsi builds: TWRP-followmsi
Root Method:
Magisk: here
LineageOS su: here
Addon (GApps/MicroG):
GApps: BiTGApps (arm 7.1.2)
MicroG (Built via FriendlyNeighborhoodShane repo): MinMicroG.zip
Source Code: https://github.com/LineageOS
Proprietary Files: TheMuppets
Kernel Source: Here
ROM OS Version: 7.1.2 Nougat
ROM Kernel: Linux 3.4.0
Security Patch: May 2023
Created 2021-01-12
Last Updated 2023-05-14
Older Builds
Downloads:
AFH Google Nexus 7 (2013) Root Folder (Builds older than July 2022)
SourceForge - deb
SourceForge - flo
Thank you.
Hi,
Somehow I'm not being to properly install and boot this build.
I repartitioned, then restored the stock partitions via the same script; installed the above TWRP.
I can only see the LOS logo for a very long time.
Any idea what it could be?
Thank you,
aurocha said:
Somehow I'm not being to properly install and boot this build.
I repartitioned, then restored the stock partitions via the same script; installed the above TWRP.
I can only see the LOS logo for a very long time.
Click to expand...
Click to collapse
I am not sure what you mean. This ROM runs on reparttioned device only. Boot into recovery, select wipe, select system partition and tap on 'resize or repair' button (you don't need to repair or resize, it's just to check partition size). There will be a report on partition size. This size should be above 1.1 Gb or the ROM won't boot. Exit this page without doing any modifications. If the partition size is 800 Mb or so you have to repartition the device.
aurocha said:
Hi,
Somehow I'm not being to properly install and boot this build.
I repartitioned, then restored the stock partitions via the same script; installed the above TWRP.
I can only see the LOS logo for a very long time.
Any idea what it could be?
Thank you,
Click to expand...
Click to collapse
You do not need to repartition. It works correctly on stock partition scheme (system with 832M size). Also, make sure that in TWRP, all your partitions are in ext4 format.
Try doing this:
- Goto Wipe -> Advanced wipe -> select all partitions and then swipe. Once done go back to main menu
- Goto Wipe -> Format Data -> type "yes" and then press enter. Once done go back to main menu
- Goto Reboot and then select Recovery
- After reboot, tick the "allow system modification" and then swipe to enter TWRP.
- Connect to Laptop/PC and copy lineageos.zip
- Flash only lineageos.zip (for testing)
- Reboot
If you get the welcome screen, then there should be an issue with any other zips that you are flashing along with the ROM.
Os_A said:
I am not sure what you mean. This ROM runs on reparttioned device only. Boot into recovery, select wipe, select system partition and tap on 'resize or repair' button (you don't need to repair or resize, it's just to check partition size). There will be a report on partition size. This size should be above 1.1 Gb or the ROM won't boot. Exit this page without doing any modifications. If the partition size is 800 Mb or so you have to repartition the device.
Click to expand...
Click to collapse
cm-14.1 works with stock partition scheme. You need repartition only for Android 9 ROMs and above (If I am not wrong as I don't know about oreo)
I have successfully installed on my Nexus 7 (2013) LTE (deb) with stock partition scheme.
M4Master96 said:
You do not need to repartition. It works correctly on stock partition scheme (system with 832M size). Also, make sure that in TWRP, all your partitions are in ext4 format.
Try doing this:
- Goto Wipe -> Advanced wipe -> select all partitions and then swipe. Once done go back to main menu
- Goto Wipe -> Format Data -> type "yes" and then press enter. Once done go back to main menu
- Goto Reboot and then select Recovery
- After reboot, tick the "allow system modification" and then swipe to enter TWRP.
- Connect to Laptop/PC and copy lineageos.zip
- Flash only lineageos.zip (for testing)
- Reboot
If you get the welcome screen, then there should be an issue with any other zips that you are flashing along with the ROM.
cm-14.1 works with stock partition scheme. You need repartition only for Android 9 ROMs and above (If I am not wrong as I don't know about oreo)
I have successfully installed on my Nexus 7 (2013) LTE (deb) with stock partition scheme.
Click to expand...
Click to collapse
Hi,
Just wanted to report that, after restoring my tablet with official image from Google and wiping it and flashing lineageos-14.1, it all went ok.
I then proceeded to flash BitGapps core and Magisk and it's running like a charm.
I don't know why it wasn't running, but I decided to revert back to the original partition scheme, restore stock images, and start all over again.
This version is stable, fluid and fast, and probably it's the best version for our device, since Android Q seems to be a bit more heavy on resources (tried the official flox build).
Thank you for keeping our device alive!
Regards,
aurocha said:
This version is stable, fluid and fast, and probably it's the best version for our device, since Android Q seems to be a bit more heavy on resources (tried the official flox build).
Click to expand...
Click to collapse
I felt the same which is why I went back to Nougat.
I use microg as only use it for watching movies/tv shows and for reading. AuroraOSS works like a charm for installing apps.
By the way, If you want things like DT2W (double tap to wake), overclocking CPU/GPU, etc... you can also flash ElementalX-N7-6.17 kernel
M4Master96 said:
I felt the same which is why I went back to Nougat.
I use microg as only use it for watching movies/tv shows and for reading. AuroraOSS works like a charm for installing apps.
By the way, If you want things like DT2W (double tap to wake), overclocking CPU/GPU, etc... you can also flash ElementalX-N7-6.17 kernel
Click to expand...
Click to collapse
Yep, that's the kernel I'm running. Mainly because of DT2W. Loads of options when flashing because of the Aroma installer and easily manageable with exkm, which I bought some years ago.
M4Master96 said:
By the way, If you want things like DT2W (double tap to wake), overclocking CPU/GPU, etc... you can also flash ElementalX-N7-6.17 kernel
Click to expand...
Click to collapse
When you flash this kernel, is there a way to re-apply/restore existing settings? I have had to go through the Aroma installer and manually enter the same settings after every update, but I can see an elementalxbackup file in my Internal Storage, which would be much easier to use if possible!
plusminus_ said:
When you flash this kernel, is there a way to re-apply/restore existing settings? I have had to go through the Aroma installer and manually enter the same settings after every update, but I can see an elementalxbackup file in my Internal Storage, which would be much easier to use if possible!
Click to expand...
Click to collapse
I think you need to use EX Kernel Manager app from Play Store which is basically app developed by the same person who built ElementalX kernel for managing the kernel. But you will need to Root your device for the app to work (if I am not wrong)
this looks great - thank you - does it work with any of the Custom Kernels?
February 2021 Security Patches
deb
Build: lineage-14.1-20210208-UNOFFICIAL-deb.zip
MD5: 7ed9473d325d20b863d1516d902602d7
flo
Build: lineage-14.1-20210208-UNOFFICIAL-flo.zip
MD5: 9a6617aa7111b4c91daf310e7bf09183
Added links in first post
M4Master96 said:
I think you need to use EX Kernel Manager app from Play Store which is basically app developed by the same person who built ElementalX kernel for managing the kernel. But you will need to Root your device for the app to work (if I am not wrong)
Click to expand...
Click to collapse
Ah I suspected this, hmm
thanks
Thanks all you guys, was looking for a decent rom for this tablet, can't live without doubletap2wake and newer roms are just too heavy for this gadget, was looking for a decent rom for it, and I have finally find it
March 2021 Security Patches
deb
Build: lineage-14.1-20210309-UNOFFICIAL-deb.zip
MD5: 6d23b5115b073a6d9a85981cb6abac11
flo
Build: lineage-14.1-20210309-UNOFFICIAL-flo.zip
MD5: 39f1a8945af9870369ffdd1deefb5e4c
Updated links in first post
First also a big THX from me for supporting our good old nexus7. You mentioned in #8 that you use microg only. How can i achive that? Is there a ready made microg.zip i can just flash with twrp after rom?
sundog1 said:
First also a big THX from me for supporting our good old nexus7. You mentioned in #8 that you use microg only. How can i achive that? Is there a ready made microg.zip i can just flash with twrp after rom?
Click to expand...
Click to collapse
I create flashable microg zip via https://github.com/WeAreFairphone/flashable-zip_microG and then flash it along with ROM, magisk and kernel. Afterwards, I use SmaliPatcher Module to patch and enable SignatureSpoofing so that MicroG works.
I had also raised Merge Request in lineageos4microg so that We can build ROM with microg without syncing repository but my MR is still open and so, Not able to build that.
April 2021 Security Patches
deb
Build: lineage-14.1-20210409-UNOFFICIAL-deb.zip
MD5: 627ce7454888bc71aec2fea10e6023ce
flo
Build: lineage-14.1-20210409-UNOFFICIAL-flo.zip
MD5: 54ac5466ae8df749a6650ee1c7b28e82
Updated links in first post
aurocha said:
Hi,
Just wanted to report that, after restoring my tablet with official image from Google and wiping it and flashing lineageos-14.1, it all went ok.
I then proceeded to flash BitGapps core and Magisk and it's running like a charm.
I don't know why it wasn't running, but I decided to revert back to the original partition scheme, restore stock images, and start all over again.
This version is stable, fluid and fast, and probably it's the best version for our device, since Android Q seems to be a bit more heavy on resources (tried the official flox build).
Thank you for keeping our device alive!
Regards,
Click to expand...
Click to collapse
Hi,
May i know which 'official image' you restored and which version of twrp was used?
I flashed LOS 18.1 before and it work but seems lag. Then I tried to flash this ROM but faced the same problem, endless looping is the screen of upwards arc w/ circle (LOS logo?) running from right to left again and again.
Thank you!
Update: Well, i just follow the link provided by @JT1510365 in https://forum.xda-developers.com/t/...oted-unmodified-6-0-mra58v-flashable.3694735/ and download the stock rom, restore to 6.0, it boot normal. Then flash twrp & this rom and it work now.
Thank you for your share of the reinstallation of 'official image'.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Disclaimer
*
* Your warranty is now void.
*
* We're 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 us for messing up your device, we will laugh at you.
*/
Introduction
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
TWRP version: 3.6.0_11
For device: gta4lwifi
Device tree: https://github.com/pazos/android_device_samsung_gta4lwifi
Maintainer/Authors build: paziusss
Known limitations
FBE encrypted storage (Internal Data) not able to be decrypted in TWRP.
Changelog
2021-12-08:
Added: exfat support
Added: mass storage support
Fixed: USB composition rules
Supressed audit messages in logcat
Misc changes (see device tree for details)
2021-12-05: Initial release
Motivation and credits.
AFAICT there're two TWRP builds on xda for the SM-T500, made by ragarcia87 and agreenbhm
The main motivation for Yet Another TWRP build was getting fastboot working, so we can follow official instructions to flash GSI builds on our devices.
Credits to u/agreenbhm for the device tree: https://github.com/agreenbhm/android_device_samsung_gta4lwifi
Credits to u/ragarcia87 for the thread, which I used as a template for this one
Installation Instructions
Spoiler
From computer:
Download Odin Flashable Tar from bellow
Put tablet into Odin Download Mode
Flash Blank vbmeta via Userdata
Flash Odin Flashable Tar via AP
From TWRP:
Download recovery.img from below
Copy recovery.img to device
Install > Install Image > recovery.img to Recovery
Reboot > Recovery
Flashing system/vendor/product/odm partitions
Spoiler
Logical partitions are read only from TWRP. If you want to flash them you'll need to reboot in fastbootd.
Boot in TWRP
Go to reboot and select fastboot.
Wait until you see a TWRP dialog saying "entered in fastboot"
Once you flashed all desired partitions reboot to recovery
In recovery wipe -> format data.
Notes on GSI flashing:
/product partition is unused in GSI builds. You can flash an empty image to gain 1GB for other logical partitions.
/system partition will be resized to the size of the GSI image you're flashing.
Thanks for migrating this to Android 11! One issue I'm seeing is that I can't mount the Micro SD card.
Also, the link for your device tree seems to be broken. Could you please update?
Hi Magendanz. Thanks for your feedback.
I have no issues mounting the MicroSD card. Do you have some logs?
Updated DT link!
About the device tree: I'm having trouble pushing the changes to github because my slow connection. Will see if I got them pushed somehow. If not I will revert blobs to agreenbhm version.
Magendanz said:
Thanks for migrating this to Android 11! One issue I'm seeing is that I can't mount the Micro SD card.
Also, the link for your device tree seems to be broken. Could you please update?
Click to expand...
Click to collapse
paziusss said:
I have no issues mounting the MicroSD card. Do you have some logs?
Click to expand...
Click to collapse
Here's the log...
Hi!
Indeed, I didn't test with exfat. Should be fixed soon. Also adb sideload don't work in the version attached.
I will make the changes ASAP and give a better commit history in device tree
Hi. Device tree updated with support for exfat and ADB sideload fixed.
Will upload the binaries in a few hours!
Thanks for bringing a nicer TWRP for GSI loading to our devices. I flashed this with no issues, but I am really struggling to get my device to boot any GSI. I am sure it is something that I am doing wrong on my end, since I have not messed with Samsung devices or any GSI installations before. Is there a change to have a more in-depth guide written up on installing a GSI on our device, or is there one already available that has similar instructions? I am planning on starting from scratch once I get home, and would like to have all of my ducks in a row before attempting again.
stompysan said:
Thanks for bringing a nicer TWRP for GSI loading to our devices. I flashed this with no issues, but I am really struggling to get my device to boot any GSI. I am sure it is something that I am doing wrong on my end, since I have not messed with Samsung devices or any GSI installations before. Is there a change to have a more in-depth guide written up on installing a GSI on our device, or is there one already available that has similar instructions? I am planning on starting from scratch once I get home, and would like to have all of my ducks in a row before attempting again.
Click to expand...
Click to collapse
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Hi. I've updated recovery binaries and added a changelog.
Please report the issues you find.
paziusss said:
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Click to expand...
Click to collapse
Will it work with Pixel Experience?
EdwardTCM said:
Will it work with Pixel Experience?
Click to expand...
Click to collapse
I didn't try. Install instructions are the same for all GSI roms. You can get a big list of GSIs in https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Some roms are bigger than stock, so you'll need to delete/wipe your product partition first. OP has instructions about it. I personally prefeer to flash an empty product.img instead of deleting the logical partition, to avoid TWRP warnings trying (and failing) to mount the partition.
paziusss said:
I didn't try. Install instructions are the same for all GSI roms. You can get a big list of GSIs in https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Some roms are bigger than stock, so you'll need to delete/wipe your product partition first. OP has instructions about it. I personally prefeer to flash an empty product.img instead of deleting the logical partition, to avoid TWRP warnings trying (and failing) to mount the partition.
Click to expand...
Click to collapse
Alright Thanks
paziusss said:
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Click to expand...
Click to collapse
I flashed phhusson's GSI rom but my galaxy tab a7 keeps boot looping
paziusss said:
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Click to expand...
Click to collapse
I'm trying to flash the ROM I downloaded but I keep getting Sparse errors and when it finishes I get this FAILED (remote: Operation not permitted)
Edit: Maybe this is happening because of the ROM being A only
EdwardTCM said:
I flashed phhusson's GSI rom but my galaxy tab a7 keeps boot looping
Click to expand...
Click to collapse
You need one of the ARM64 AB variants. No matter if it is vanilla, floss or gapps.
thank you for twrp and fastboot but i noticed that most gsi images are bugy no brightness or randemly rebooting
paziusss said:
You need one of the ARM64 AB variants. No matter if it is vanilla, floss or gapps.
Click to expand...
Click to collapse
OOOH I thought it was A Only
EdwardTCM said:
I'm trying to flash the ROM I downloaded but I keep getting Sparse errors and when it finishes I get this FAILED (remote: Operation not permitted)
Click to expand...
Click to collapse
paziusss said:
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Click to expand...
Click to collapse
To anyone who wants to try the Pixel Experience rom
USE A/B NOT A ONLY
EdwardTCM said:
To anyone who wants to try the Pixel Experience rom
USE A/B NOT A ONLY
Click to expand...
Click to collapse
Btw the wifi doesn't work
One Issue when downgrading to TWRP 3.5 is that it will boot loop
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
GPL compliance:
Device tree source code: LineageOS/android_device_xiaomi_beryllium
Kernel source code: LineageOS/android_kernel_xiaomi_sdm845
Working:
Camera (and flashlight)
WiFi
Bluetooth
Telephony (Calls and Data)
IMS (RCS, VoLTE and WiFi Calling)
Audio (Record and Playback)
Video Playback
Sensors
GPS
Encryption (FBE)
WiFi Display
Broken:
Nothing (?)
Compatibility:
Compatible with all Xiaomi Poco F1 variants.Builds are based off the Xiaomi's Android 10 firmware with proprietary blobs from MIUI v12.0.3.0 global stable package.
Device wiki:
Official wiki link
Downloads:
Official download links
Installation:
Follow instructions found in the respective wiki page
Is this a System-Ext-Rom?
Chris_Kaos79 said:
Is this a System-Ext-Rom?
Click to expand...
Click to collapse
Yes
Read the upgrade instructions, had to sadly ignore them because i no longer have a cable/port/adb combo that allows adb to sideload successfully (i just get errors when he starts to transmit).
EDIT [i am lying, adb works but fastboot does not]
So i remained on the Reignz TWRP, and from a recent LOS 19.1:
- flash LOS 20
- flash MindTheGapps 13
- flash Magisk
- flash NGK kernel
- Wipe dalvik/cache
- reboot system
-> Bootloop. Well theoretically this must work, so maybe try less at once? I did see that Magisk re-flashed itself automatically in TWRP, so attempt 2:
- flash LOS 20
[Magisk automatically reflashes itself]
- flash MindTheGapps 13
- reboot system
Works now.. but i am always eager to ruin myself so i will try to reflash NGK now.
EDIT: Yup NGK+TWRP causes bootloop. I will reflash LOS20 again ... and try LOS recovery with NGK maybe.
EDIT2: LOS recovery with NGK bootloops also. Stock kernel it is.
EDIT3: Working good with stock kernel. Magisk works, camera works, banking and auth apps work. Thank you
Another oddity: The updater app immediatly came up and recommended i upgrade to the LOS20 i just flashed. Uh huh?
I updated to LOS 20 via dirty flash from LOS 19.1 (following the official procedure: https://wiki.lineageos.org/devices/beryllium/upgrade)
It worked flawlessly!
AtomicStryker said:
Read the upgrade instructions, had to sadly ignore them because i no longer have a cable/port/adb combo that allows adb to sideload successfully (i just get errors when he starts to transmit).
EDIT [i am lying, adb works but fastboot does not]
So i remained on the Reignz TWRP, and from a recent LOS 19.1:
- flash LOS 20
- flash MindTheGapps 13
- flash Magisk
- flash NGK kernel
- Wipe dalvik/cache
- reboot system
-> Bootloop. Well theoretically this must work, so maybe try less at once? I did see that Magisk re-flashed itself automatically in TWRP, so attempt 2:
- flash LOS 20
[Magisk automatically reflashes itself]
- flash MindTheGapps 13
- reboot system
Works now.. but i am always eager to ruin myself so i will try to reflash NGK now.
EDIT: Yup NGK+TWRP causes bootloop. I will reflash LOS20 again ... and try LOS recovery with NGK maybe.
EDIT2: LOS recovery with NGK bootloops also. Stock kernel it is.
EDIT3: Working good with stock kernel. Magisk works, camera works, banking and auth apps work. Thank you
Another oddity: The updater app immediatly came up and recommended i upgrade to the LOS20 i just flashed. Uh huh?
Click to expand...
Click to collapse
NGK has some problems for now, wait for update or use orange fox...
AtomicStryker said:
Read the upgrade instructions, had to sadly ignore them because i no longer have a cable/port/adb combo that allows adb to sideload successfully (i just get errors when he starts to transmit).
EDIT [i am lying, adb works but fastboot does not]
So i remained on the Reignz TWRP, and from a recent LOS 19.1:
- flash LOS 20
- flash MindTheGapps 13
- flash Magisk
- flash NGK kernel
- Wipe dalvik/cache
- reboot system
-> Bootloop. Well theoretically this must work, so maybe try less at once? I did see that Magisk re-flashed itself automatically in TWRP, so attempt 2:
- flash LOS 20
[Magisk automatically reflashes itself]
- flash MindTheGapps 13
- reboot system
Works now.. but i am always eager to ruin myself so i will try to reflash NGK now.
EDIT: Yup NGK+TWRP causes bootloop. I will reflash LOS20 again ... and try LOS recovery with NGK maybe.
EDIT2: LOS recovery with NGK bootloops also. Stock kernel it is.
EDIT3: Working good with stock kernel. Magisk works, camera works, banking and auth apps work. Thank you
Another oddity: The updater app immediatly came up and recommended i upgrade to the LOS20 i just flashed. Uh huh?
Click to expand...
Click to collapse
I know this is off-topic, but I guess you used Reignz V3.6.2 that he tested for A13 support?
Interesting that apparently A13 again uses other encryption than A12? I though now with A13 FBE would be the new standard but there is something new again?
So official 3.7.0 TWRP will not work with A13 I guess.
Looking forward to jump to A13 this weekend based on all the positive feedback so far - thank you bgcngm for your hard work!
hello there,
I've just dirty flashed LOS20, and I'm having problems connecting anything via bluetooth, any idea how to fix this without clean installing?
Another question, I'm using MindTheGapps 13 as recommended here, but I was looking for something the minimum google services, do you think I can use NikGapps?
Thanks
alright, I couldn't fix it, I had it reinstalled clean. Everything is working nicely and the new camera is a very welcome improvement.
I'm still facing issues with bluetooth though. I'm able to use it and connect normally, but when listening to audio, it seems that the connection is weak, and I can often hear cuts in the connection, or noise. Anyone having the same?
AtomicStryker said:
EDIT: Yup NGK+TWRP causes bootloop. I will reflash LOS20 again ... and try LOS recovery with NGK maybe.
EDIT2: LOS recovery with NGK bootloops also. Stock kernel it is.
Click to expand...
Click to collapse
This problem is a known issue since the day before yesterday. Several people are experiencing this with the upgrade from 19.1 to 20. For now, running the stock kernel should be fine.
Installation GuidesOfficial way of installation can be found at OP.
Installation Guides:
Clean Install via TWRP:
Backup your data to PC or SDCard if you have.
Downland:
Spoiler: These files
- TWRP by REIGNZ v2 [twrp-beryllium-v3.7.0-A12-V2.img] - [Current Bugs/Issues & Workarounds]
- Latest build of Official LineageOS ROM and optional LineageOS Recovery from the same link, if you want to flash that later.
- Optional A13 GApps of your choice.
Boot, flash and reboot to TWRP. [Check Install Custom Recovery Guide]
Select Wipe > Advanced Wipe -> Select Dalvik / ART Cache, System, System_EXT, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe.
Reboot to recovery once again (needed due to a current issue with TWRP by REGINZ) and then Format data > type yes.
Transfer the files you previously downloaded into Internal Storage, while you are connected and into TWRP from PC to your Device. If you have SDcard or USB OTG you can also use that.
[TWRP by REIGNZ have an issue, if PC doesn't recognize the device, press in twrp menu, Advanced > File Manager > and find and select sdcard folder aka Internal Storage > go back and now your pc should be able to recognize the device]
Flash ROM > GApps. NOTE: ROM IS FORCE ENCRYPTED
[Optional] Flash LineageOS recovery by pressing "Install Image > Navigate and Select the LineageOS Recovery > Flash it to recovery partition.
Reboot and Enjoy!
[Optional] In case you want to change Kernel to NGK or SC [SE version - aka System_Ext], flash it after the first boot of the ROM.
[Optional] In you case you want Root, flash Magisk after the first boot of the ROM.
SafetyNet & Certified Play Store:
Official LineageOS doesn't pass SafetyNet or have certified Play Store by default. [Read here why]
Root your device with Magisk and Follow this Guide (or this) to pass SafetyNet and have certified Play Store. [YouTube Video Guide]
OTA Upgrade/Update:
Warning
Only use OTA if you are encrypted. Simply go to updater and press install, everything will be automatic.
Dirty Installation via TWRP:
{Manually Upgrade/Update the ROM}
Download:
Spoiler: These files
- TWRP by REIGNZ [twrp-beryllium-v3.7.0-A12.img] - [Current Bugs/Issues & Workarounds]
- Latest build of Official LineageOS ROM and optional LineageOS Recovery from the same link, if you want to flash that later.
- Optional A13 GApps of your choice.
Wipe System, System_Ext, Dalvik ART/ Cache, Cache, Vendor.
Flash ROM > GApps > [Optional]Magisk.
Reboot and Enjoy!
Notes:
If you want to flash DFE use TWRP by REIGNZ based on A9. (not A12) [Not recommended be decrypted]
If you encounter Fastboot issues read the guide/fix in my thread.
You can translate the ROM in Crowdin.
Check my threads:
Spoiler: My threads
- POCO F1 Ultimate Collection & Guides
- Android Ultimate Collection & Guides
- ReVanced & ReVanced Extended - Guides & Useful Links
- Windows Ultimate Collection & Guides
pmcmm said:
I'm still facing issues with bluetooth though. I'm able to use it and connect normally, but when listening to audio, it seems that the connection is weak, and I can often hear cuts in the connection, or noise. Anyone having the same?
Click to expand...
Click to collapse
I had to unpair my existing bluetooth devices and re-pair them, (presumably because the upgrade changed the phones bluetooth ID) but it seems to work perfectly for me.
- I am on this ROM since 01.01, no major issues so far.
- Just FYI, DFE zip (Disable Force Encryption) from Retrial collection doesn't seem to work on this ROM. For the sake of testing, I tried both A13 DFE and the older zip (which worked on LOS19.1) with clean installations. When I check in the settings, the phone was encrypted every time, no matter what I do.
- On the other hand, I can report that unofficial TWRP A12 by Reignz (twrp-beryllium-v3.7.0-A12.img) can decrypt storage on LOS20.
- One small glitch I found: If I lit up the screen (press power button) while charging, the phone stays on the lockscreen with the display on, never turning off by itself. Of course if I press power button or double tap I can turn it off. Also if I just disconnect power cable, display turns off in few seconds like it should. But if I just press power once and leave it, it will stay on the lockscreen forever.
- Bluetooth is fully working for me. I am using 2 different BT headsets for few hours every day. Not a single issue so far.
marsa47 said:
- Just FYI, DFE zip (Disable Force Encryption) from Retrial collection doesn't seem to work on this ROM. For the sake of testing, I tried both A13 DFE and the older zip (which worked on LOS19.1) with clean installations. When I check in the settings, the phone was encrypted every time, no matter what I do.
- On the other hand, I can report that unofficial TWRP A12 by Reignz (twrp-beryllium-v3.7.0-A12.img) can decrypt storage on LOS20.
Click to expand...
Click to collapse
The DFE not seem to working with the TWRP by REIGNZ based on A12. Instead you should try to flash DFE via TWRP by REIGNZ but based on A9.
The purpose of A12 based twrp is to decrypt A12+ encrypted ROMs. If you don't need encryption (which I recommend everyone to use encryption), then use TWRP by REIGNZ A9 and flash DFE.
any way to get F2FS working ? With flashed fstab i get recovery reboot and without i get a bootloop
Is it important to fastboot the required xiaomi firmware first? Coming from 19.1.
MagnesG said:
Is it important to fastboot the required xiaomi firmware first? Coming from 19.1.
Click to expand...
Click to collapse
I assume u already have it. No need.
noah001 said:
any way to get F2FS working ? With flashed fstab i get recovery reboot and without i get a bootloop
Click to expand...
Click to collapse
Flash a kernel with with f2fs support,
Do "long loading while taking picture from whatsapp-bug" still occurred????
123r4ka456 said:
Do "long loading while taking picture from whatsapp-bug" still occurred????
Click to expand...
Click to collapse
I get the following behavior:
1st try: click on photo button: nothing happens (but no hang)
2nd try: click on photo button: photo is immediately taken and can be sent, no hang
So: not really running without issues, but no hang
Maybe this is helpful