{
"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"
}
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.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
Flashing TWRP:
- Bootloader needs to be unlocked
- You need latest adb and fastboot
- Boot into bootloader
- Check the current active slot, change the slot to the other slot (if current active slot is = a then use b. If b, then use a)
- Switch slot by using fastboot set_active <a or b>
- Use fastboot reboot bootloader to check if right slot is selected.
- Flash the boot image by using fastboot flash boot boot.img
- Select recovery from bootloader
Note : Do not flash recovery to the slot where Stock Rom exists its not yet completely verified if you will be able to boot to stock when recovery is flashed.
Hence is why it is recommended in above steps to change slots so that stock remains unaltered.
What is working:
- Decryption of Data
- ADB
- Screen brightness settings
- Vibration on touch
- Correct screenshot color
- Active slot switching from TWRP
- MTP
DOWNLOAD:
TWRP Recovery Image for Zenfone 5z(ZS620KL) by jackeagle
Fastboot Flashing Code
Code:
[CENTER]fastboot flash boot boot.img[/CENTER]
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
If you like my work, donations are always welcome (but not mandatory).
XDA:DevDB Information
TWRP Recovery, Tool/Utility for the Asus Zenfone 5Z
Contributors
jackeagle, Rohan purohit
Source Code: https://github.com/LineageOS/android_kernel_asus_sdm845/
Version Information
Status: Stable
Current Stable Version: 3.4.0
Stable Release Date: 2019-04-26
Created 2018-10-01
Last Updated 2020-07-14
Steps to Install and Information
TWRP Recovery Downloads
TWRP 3.4.0 Q Image by jackeagle
TWRP 3.4.0 Installer by jackeagle
How To Install TWRP Recovery On Asus Zenfone 5z (ZS620KL)
Prerequisites: Unlocked bootloader (Refer to Asus Documentation on Unlocking Bootloader for further information)
Step 1:
Download TWRP Recovery onto your PC. Make sure you check the md5 to verify its integrity (where possible).
Step 2:
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Power off your phone then boot into the bootloader (power + volume up).
Step 3:
Check Active Slot in fastboot. This is very important and if its showing "a" you have to switch to slot "b" and vice versa.
To switch active slot using following command
Code:
fastboot --set-active= <a/b>
then reboot to bootloader again to check if active slot is changed or not using following command
Code:
fastboot reboot bootloader
Step 4:
Flash TWRP Recovery using following command
Code:
fastboot flash boot boot.img
Step 5:
Press Volume keys and select Reboot to Recovery and Press and Hold Power button to reboot to recovery.
You will be successfully rebooted to TWRP Recovery!
Enjoy!
Warning: DO NOT SWITCH SLOTS USING TWRP SETTINGS FOR NOW! USE FASTBOOT METHOD ITSELF ELSE YOU WONT BE ABLE TO BOOT STOCK!
DO NOT FLASH PERMANENT TWRP ZIP ON STOCK KERNEL. IT WILL CAUSE TOUCH ISSUES DUE TO KERNEL DRIVERS.
Changelog
July 13 2020
Update to TWRP 3.4.0 Release
Merged with latest kernel changes
Misc fixes
29th Feb 2020
Fixed Migration and Higher versions of Gapps flashing
Update to Android 10 Kernel Release
Misc fixes
22nd Feb 2020
Updated to TWRP 3.3.1-10
Fixed Decryption for all (Stock and Custom Roms)
Added ability to flash Asus Stock OTA/firmware via TWRP
Fixed MTP
Update to Android 10 Kernel Release
Misc fixes
2nd August 2019
Updated to TWRP v3.3.1 Latest Release
Merged with latest changes from TWRP
Added support to flash persist img from TWRP
Fixed MTP
Updated TWRP Permanent Flash zip
Misc fixes
4th July 2019
Updated to TWRP v3.3.1 Latest Release
Merged with latest changes from TWRP
Remove /persist mounts
Updated TWRP Permanent Flash zip
4th June 2019
Added TWRP Permanent Flash zip
26th April 2019
Updated to TWRP v3.3.0 Latest Release
Added EDL Support ( Edl Mode is used to fully restore the bricked devices. For further information visit TWRP Website).
Removed DarkUI
Fixed few issues
24th Feb 2019
Updated with Latest TWRP Pie Recovery
Added Full Support for LOS16 Released here
20th Jan 2019
Updated with Latest TWRP Pie Recovery
Updated Blobs to Latest Asus Pie Release
Fixed few issues
Updates to TWRP UI with Dark Theme
Added Support for LineageOS-16 Flashing.
Backup / Restore Tested nd Working.
Fixed UI Lags
29th Dec 2018
Updated with Latest TWRP Pie Recovery
Updated Blobs to Latest Asus Pie Release
Fixed /data Decryption on Asus Pie
Revamped TWRP UI with Dark Theme
Fixed File Manager Bugs
Disabled MTP (Causes panic)
7th Nov 2018
Fixed Backup and Restore issue
6th Nov 2018
Fixed /data Decryption and Internal Storage Access!
Fixed TimeZone Selection bug
Updated to latest Asus Release!
Updated TWRP to Latest 9.0 Release.
2nd October 2018
Initial Release
Hi, thanks for recovery will you also try to port lineage or some other custom rom? We really need working device tree
Thank you!
Its good to see the devlopment on this device. I would love to see the development on this device. Its the competitor of one plus 6. And it should compete with one plus 6 in various development as well.
This is awesome, i think soon we can see some custom Roms for this device
Mister_Magister said:
Hi, thanks for recovery will you also try to port lineage or some other custom rom? We really need working device tree
Click to expand...
Click to collapse
There are plans for Lineage Development but it all depends on time availability! But yes its in process
jackeagle said:
There are plans for Lineage Development but it all depends on time availability! But yes its in process
Click to expand...
Click to collapse
Will you also share sources? I need lineage to start porting SailfishOS
hello
first of all, thanks for your hard work.
btw, i have zenfone 5z japanese varient, and i tried this twrp, twrp boots and works
but when tried to back to stock one, my device got soft bricked
so i saw ur device tree and i think this brick occured by ww version's boot.img and settings (bootloader)
can you make other twrp with japanese varient's boot.img and settings?
thanks
jpg3927 said:
hello
first of all, thanks for your hard work.
btw, i have zenfone 5z japanese varient, and i tried this twrp, twrp boots and works
but when tried to back to stock one, my device got soft bricked
so i saw ur device tree and i think this brick occured by ww version's boot.img and settings (bootloader)
can you make other twrp with japanese varient's boot.img and settings?
thanks
Click to expand...
Click to collapse
Hi,
Well the version added is latest release version. You didnt update it to latest version ?
jackeagle said:
Hi,
Well the version added is latest release version. You didnt update it to latest version ?
Click to expand...
Click to collapse
japanese varient didn't release 80.30.96.111 yet i'm on 80.30.96.80
Well im always getting bootloop after flashing this twrp. Steps:
>be on slot a
>set_active b
>flash boot boot.img
>set_active a
>boot
>boots and all working fine
>set_active b
>boot into recovery
>it booted twrp everything is nice
>set_active a or change slot from twrp
>boot
>bootloop
Seems like booting twrp changes something so i can no longer boot.
Stock: WW__ZS620KL_80.10.8.54_MP_user_20180517175955_release
Just be carefull with TWRP for now. I did not pull mine for nothing.
Verstuurd vanaf mijn ASUS_Z01RD met Tapatalk
---------- Post added at 08:01 PM ---------- Previous post was at 08:00 PM ----------
Where are the device specific sources?
Verstuurd vanaf mijn ASUS_Z01RD met Tapatalk
scanno said:
Just be carefull with TWRP for now. I did not pull mine for nothing.
Verstuurd vanaf mijn ASUS_Z01RD met Tapatalk
---------- Post added at 08:01 PM ---------- Previous post was at 08:00 PM ----------
Where are the device specific sources?
Verstuurd vanaf mijn ASUS_Z01RD met Tapatalk
Click to expand...
Click to collapse
I mean this device is useless as long as we dont have lineage anyway
Mister_Magister said:
I mean this device is useless as long as we dont have lineage anyway
Click to expand...
Click to collapse
Don't agree on that one [emoji16]. But hey if some more people are developing, perhaps we can join efforts.
Getting a good kernel and a good device tree is good for any room wether it is Omni or los.
scanno said:
Don't agree on that one [emoji16]. But hey if some more people are developing, perhaps we can join efforts.
Getting a good kernel and a good device tree is good for any room wether it is Omni or los.
Click to expand...
Click to collapse
well here are https://github.com/Jackeagle/twrp_device_asus_z01r Jackeagle sources
here is me trying pointlessly to convert your device tree to build lineage https://github.com/VerdandiTeam/android_device_asus_ZS620KL
Regarding GSI
@scanno @jackeagle
Phhusson said that If we had Devs he can help them to fix issues in gsi. Since u two are the only Devs ,maybe work with phh once you have time?
It's great to see 5Z finally getting some attention.
Mister_Magister said:
Well im always getting bootloop after flashing this twrp. Steps:
>be on slot a
>set_active b
>flash boot boot.img
>set_active a
>boot
>boots and all working fine
>set_active b
>boot into recovery
>it booted twrp everything is nice
>set_active a or change slot from twrp
>boot
>bootloop
Seems like booting twrp changes something so i can no longer boot.
Stock: WW__ZS620KL_80.10.8.54_MP_user_20180517175955_release
Click to expand...
Click to collapse
Well this does seem something odd but then since i cannot reproduce it, its difficult for me to debug it.
As of now i tried it on my device nd yet all boots fine even after switching of slots. But let me tell you there is a bug related to TWRP switching slots since some devices they have reported that switching slots does cause bootloops when its done from recovery but since i have never faced it i cannot say with full surety!
Related
Vanilla-ish AOSP 7.1.2_r13 ROM (N2G47X) for WiFi/LTE Nexus 9
This was created by building from N2G47X source, including SuperSU and cherry picking a few commits...
FOR ROOT - SuperSU no longer included!!!
Featuring:
Vanilla AOSP 7.1.2_r13 (N2G47X) for WiFi/LTE Nexus 9
June 5th 2017 security patch level in ROM AND Kernel
SuperSU Free v2.79 SR3 Removed in v1.11.170405
LTE works
NTFS/exFAT file system support (for OTG)
Advanced power menu
Nougat 7.1 boot animation from Pixel XL
Nav bar tuner, night light, brightness slider toggle
System UI Tuner now shows by default in Settings
Removed/sped up some animations for faster/smoother experience
Won't overwrite TWRP with stock recovery
OpenGapps compatibility - stock now working
busybox 1.22.1 removed in v1.11.170405
All future Nougat builds will all be based on this table - https://source.android.com/source/build-numbers.html#source-code-tags-and-builds
AdAway v3.1.2 Removed in v1.11.170405 since no longer including root
Amaze File Manager v3.1.1
You can skip setup wizard (if needed) by tapping all 4 corners in clockwise order starting with top left...
Self-compiled 3.10.103 kernel also from AOSP source (https://android.googlesource.com/kernel/tegra/+/android-tegra-flounder-3.10-nougat):
Current with June 5th 2017 security patch level
Audio issue fix (partial)
healthd charging issue fixed (v0.60)
No forceencrypt
UKSM
Permissive
f2fs supported on /cache
frandom support (added in v0.42)
SIO/FIOPS IO Schedulers (added in v0.42)
Advanced TCP congestion enabled
fsync togglable (added in v0.42)
2.0A charging support (added in v0.42)
Snappy compression library
Defaults
Governor - Interactive
IO Sched - FIOPS
TCP Congestion control - Cubic
UBERTC-4.9.4
Source:
https://github.com/bshiznit
{
"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"
}
Please use TWRP 3.0.2-1 PLEASE be at bootloader 3.48.0.0141 and have flashed the latest NMF26F vendor image (linked under downloads)!
You may not need to wipe between versions, if issues please wipe data and both caches (in TWRP got to Wipe --> "Swipe to Factory Reset")
Downloads
Before flashing scroll down and read NOTES!
ROM
DEODEX (for Xposed/GravityBox, theming, etc.):
https://www.androidfilehost.com/?fid=889764386195909301
md5 - 1170234b143704e7202baa72a9ec48f3
No ODEX yet ODEX (faster initial boot and overall performance potentially):
MEGA
Dev-Host
md5
3.50.0.0143 bootloader and N9F27C (N4F27E for LTE model) vendor.img - NOTE there are not 7.1.2 vendor images (Nexus 9 is not officially supported in 7.1.2) so I am pulling the latest 7.1.1 ones from https://developers.google.com/android/nexus/images
WIFI:
https://www.androidfilehost.com/?fid=961840155545575100
md5 - 515f1c328c7a0491f4d3a1e297264053
LTE:
https://www.androidfilehost.com/?fid=817550096634779382
md5 - 5f12990a299d304cdaa8ff843b2ba6c1
NEED fastboot
In fastboot:
WIFI/LTE (be sure you've got the right files!):
Bootloader:
fastboot flash bootloader bootloader-flounder-3.50.0.0143.img
fastboot reboot-bootloader
Vendor image:
fastboot flash vendor vendor.img
OR
Flash vendor.img using new feature in TWRP 3.0.0 (tested using 3.0.2-1) - in recovery's "Install" menu hit the "Install Image" button...
Then ROM
Open GApps (closer to STOCK - choose ARM64 for Platform, 7.1 for Android I pick Stock for Variant
http://opengapps.org/
Direct link:
http://opengapps.org/?download=true&arch=arm64&api=7.1&variant=stock
NOTE takes a WHILE (5-10 minutes) to boot up on first boot! ART is optimizing applications and it is set to EVERYTHING as we have sufficient system partition storage - for SPEED. There is no more dalvik-vm (no REALLY now - not even included in AOSP now)!
If you like it hit thanks! Donations are appreciated but never expected
I do this for a hobby and to keep my tablet running like new
Coming soon:
?
NOTES:
ALWAYS flash GApps even if updating from a prior AOSP 5.1.x/6.0/7.x release! ALL ROMs format the /system partition as part of the installation process and this is where the:silly: GApps are kept!
BACKUP using TWRP and/or Titanium - save those files off the device to a USB stick external HDD or whatnot! Not responsible for lost data!
WIPE Data in recovery
Be sure you are at bootloader 3.48.0.0141 and have flashed latest vendor image (steps in this post)
ONLY TESTED USING TWRP 3.0.2-1
MUST FLASH a GApps zip after the ROM for Play Store, etc.
If you like it consider donating! A nice big solid state hard drive will let me build faster and for more devices! (YAY my build box now has 411GB free even after all this developing - thanks to all who donated)
Thanks:
Nitrogen OS for a lot of things I cherry picked! (@Mr.MEX, @xyyx) - https://github.com/nitrogen-project
Pure Nexus for tons of cherry picks too (@BeansTown106) - https://github.com/PureNexusProject
Team OctOs (@hedwig34) for good SuperSU integration and other custom vendor ideas - http://www.github.com/Team-OctOs
@timduru for some great cherry picks from his TF300T ROM source - https://github.com/timduru
@USBhost - kernel ideas/source - https://github.com/USBhost/FIRE-ICE
@flar2 - kernel ideas/source - https://github.com/flar2/ElementalX-N9
@Beta1440 - kernel ideas/source - https://github.com/Sublime-Development/kernel_flounder
@Snuzzo for github familiarization and being a great dev and resource, as well as introducing me to kernel devving!
@sykopompos for ART build.prop tweaks.
@scrosler great dev and good resource
@Chainfire for SuperSU and keeping it updated!
Google for Android
AOSP for source!
Changelog
N2G47X... v1.11.170405 --> v1.12.170613:
Updated to N4F26X Nougat 7.1.1_r33 (April 5th 2017 security patch level)
Removed included automatically flashed SuperSU (also removed AdAway and busybox)...
N4F26X... v1.11.170306 --> v1.11.170405:
Updated to N4F26X Nougat 7.1.1_r33 (April 5th 2017 security patch level)
Removed included automatically flashed SuperSU (also removed AdAway and busybox)...
N4F26T... v1.11.170207 --> v1.11.170306:
Updated to N4F26T Nougat 7.1.1_r24 (March 5th 2017 security patch level)
Cherry picked partial audio fix into kernel - https://github.com/vartom/android_kernel_flounder/commit/b94b18d897d5d40b0d8fb382855d85d2e3340a71, https://github.com/vartom/android_kernel_flounder/commit/5c4645b56609a305ca147869616af61de578d492
N4F26Q... v1.11.170106 --> v1.11.170207:
Updated to N4F26Q Nougat 7.1.1 (February 5th 2017 security patch level)
N4F26M... v1.11.161206 --> v1.11.170106:
Updated to N4F26M Nougat 7.1.1 (January 1st 2017 security patch level)
NMF26F... v1.10.161117 --> v1.11.161206:
Updated to NMF26F Nougat 7.1.1
NDE63V... v0.71 --> v1.10.161117:
Updated to NDE63V Nougat 7.1!
Sounds and boot animation from the Pixel XL Android 7.1...
NRD91N... v0.70 --> v0.71:
Updated to NRD91N 7.0.0_r15 (November 5th 2016 security baseline)
NOTE - to be fully patched you MUST ALSO update to the vendor partition from NRD91N!!!
NRD91D... v0.60 --> v0.70:
Added ntfs-3g and exfat libraries and utilities (exFAT/NTFS file system support - useful for OTG) - https://github.com/bshiznit/platform_build/commit/269b4fbc1fb4a60db8d4986347b7be52702101b3
Re-added integrated SuperSU - https://github.com/bshiznit/platform_build/commit/ddcb3a0697ee4e904ed8680cdd1181b2129b8af5, https://github.com/Team-OctOS/platform_vendor_to/commit/4f8286815fc8be7c884cf370a6db5054600cd2cb
init.d support fixed (https://github.com/bshiznit/platform_vendor/commit/faa8839c075425831b59b9fd49711832e09a978e)
NRD91D... v0.50 --> v0.60:
healthd fixed in kernel (charging issue) - https://github.com/CyanogenMod/andr...mmit/f63db167706bb651562a262bc3169c0961769fe0
Stock GApps can now be flashed - commits:
https://github.com/AOSPA/android_frameworks_base/commit/d36582165d4694da101cc65755af0841d443c80e
https://github.com/AOSPA/android_frameworks_base/commit/b70f5994464cf6b3b29cedcc4efdd73807a27b0f
Boot animation from Pixel
RAMDisk hacked up (LOL) in kernel to allow SuperSU to flash correctly
Decided NOT to include automatic flashing of SuperSU (see poll - can add back!)
Bionic updates (some arm64, aarch64 stuff - busybox needed this updated for whatever reason in order to compile correctly)
Busybox now compiled in (thanks to Bionic updates)...
MixPlorer replaced with Amaze File Manager
False errors no longer show when flashing in recovery - https://github.com/bshiznit/platfor...mmit/5b1db93c0e05244a087feb6a5970183a75f53770
Thanks a lot man! Any bugs?
Sent from my ONEPLUS A3003 using Tapatalk
jaju123 said:
Thanks a lot man! Any bugs?
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
GApps doesn't seem to stick? SuperSU doesn't seem to flash right either! Still tweaking things but this is a very early build
Congratulations!!
Absolutely awesome my friend!! You are the first dev to get an N9 Nougat ROM up and running!!!
matthewgwilt said:
Absolutely awesome my friend!! You are the first dev to get an N9 Nougat ROM up and running!!!
Click to expand...
Click to collapse
Thanks - wish I had it working better!
IDEA - (still screwing around with builds or I'd try right now) - flash my ROM, Flash ElementalX kernel (N9-5.02 - http://forum.xda-developers.com/nexus-9/orig-development/kernel-elementalx-n9-0-02-alpha-t2931657) - then see if GApps/SuperSU work...
Will try ASAP and get back
EDIT - OK well - no SuperSU but flashing the ElementalX kernel DOES allow the GApps to install (and show up - without the kernel it appears to work but I see nothing when I boot)... Flash kernel, GApps - then got to Settings --> Apps --> Google Play services and click permissions then allow everything allow Location (that's all that is needed to fix)!
Ok, so I goofed...I thought I was on TWRP 3.0.2-1, but I was on 3.0.2-0 I flashed everything, and it boots, however I can't get past the "Google Play services keeps stopping" popup. Every time I try to close it, I'm pushed back to the wifi selection screen, and I can't get to the home screen. I tried going back into TWRP, and TWRP goes into a sort of bootloop where the splash screen will show, but it keeps rebooting to it :/ Any help would be much appreciated! Thx in advance
sabrdawg said:
Ok, so I goofed...I thought I was on TWRP 3.0.2-1, but I was on 3.0.2-0 I flashed everything, and it boots, however I can't get past the "Google Play services keeps stopping" popup. Every time I try to close it, I'm pushed back to the wifi selection screen, and I can't get to the home screen. I tried going back into TWRP, and TWRP goes into a sort of bootloop where the splash screen will show, but it keeps rebooting to it :/ Any help would be much appreciated! Thx in advance
Click to expand...
Click to collapse
Fastboot flash 3.0.2-1, then reflash the ROM.
cam30era said:
Fastboot flash 3.0.2-1, then reflash the ROM.
Click to expand...
Click to collapse
Thx so much! That was going to be my next resort, after mulling it over for a while
sabrdawg said:
Thx so much! That was going to be my next resort, after mulling it over for a while
Click to expand...
Click to collapse
Sounds like you did update the bootloader and vendor partition! In TWRP before 3.0.2-1 the new vendor partition is encrypted and TWRP has no idea how to decrypt it...
RE: the play services crashing (I did add this later to OP) - go to Settings --> Apps --> Google Play services and click permissions then allow Location
bshiznit said:
Sounds like you did update the bootloader and vendor partition! In TWRP before 3.0.2-1 the new vendor partition is encrypted and TWRP has no idea how to decrypt it...
RE: the play services crashing (I did add this later to OP) - go to Settings --> Apps --> Google Play services and click permissions then allow Location
Click to expand...
Click to collapse
Well, I successfully flashed the correct TWRP! The only problem is that the Google Play services error is still persisting I can't go into settings to allow location, because I can't get past the Checking Info screen. It keeps bumping me back to the wifi select screen. Argh Let me make sure I'm on the correct bootloader. I did flash the .img file via TWRP using the boot partition...I wonder if it took?
My bootloader version says
HBOOT-3.48.0.0135
Looks like it is indeed the wrong one. I'll have to figure out how to correctly flash it via TWRP.
sabrdawg said:
Well, I successfully flashed the correct TWRP! The only problem is that the Google Play services error is still persisting I can't go into settings to allow location, because I can't get past the Checking Info screen. It keeps bumping me back to the wifi select screen. Argh Let me make sure I'm on the correct bootloader. I did flash the .img file via TWRP using the boot partition...I wonder if it took?
Click to expand...
Click to collapse
I see - I flashed the PICO Opengapps (which bypasses setup I'm thinking is why the difference) - maybe try that next?
bshiznit said:
I see - I flashed the PICO Opengapps (which bypasses setup I'm thinking is why the difference) - maybe try that next?
Click to expand...
Click to collapse
Will try! Thx for all of your help. It's much appreciated
Well, I restored RR so I could download the Pico Gapps, which worked fine once I flashed the Marshmallow vendor image again. Now TWRP isn't working again. The TWRP splash screen flashed several times before booting into TWRP, and now it's doing that thing where it asks you to enter a password, meaning data is encrypted and it won't recognize any of my files...so now I can't even flash the Nougat files again. Argh Perhaps I need to flash the Nougat vendor image via adb, however TWRP 3.0.2-1 should work on Marshmallow as well, right? Sorry to be such a pain.
EDIT
I finally got it to work! I ended up flashing the previous version of TWRP via Flashify, and it worked without encryption. I went ahead and flashed all files and still kept getting the Google Play services popup, however, this time I was able to get to the home screen and enable all permissions in settings. It worked like a charm What's interesting is that I'm also still on the MM bootloader.
sabrdawg said:
Well, I restored RR so I could download the Pico Gapps, which worked fine once I flashed the Marshmallow vendor image again. Now TWRP isn't working again. The TWRP splash screen flashed several times before booting into TWRP, and now it's doing that thing where it asks you to enter a password, meaning data is encrypted and it won't recognize any of my files...so now I can't even flash the Nougat files again. Argh Perhaps I need to flash the Nougat vendor image via adb, however TWRP 3.0.2-1 should work on Marshmallow as well, right? Sorry to be such a pain.
EDIT
I finally got it to work! I ended up flashing the previous version of TWRP via Flashify, and it worked without encryption. I went ahead and flashed all files and still kept getting the Google Play services popup, however, this time I was able to get to the home screen and enable all permissions in settings. It worked like a charm What's interesting is that I'm also still on the MM bootloader.
Click to expand...
Click to collapse
You aren't being a pain - even though it gets lost A LOT the spirit of this community is to just try stuff - even WIPs - and report back experience
For me I realized very quickly something was wrong with TWRP 3.0.2 after doing:
fastboot flash bootloader bootloader-flounder-3.48.0.0139.img
fastboot reboot-bootloader
fastboot flash vendor vendor.img
So I pretty much checked the TWRP flounder forum here and realized I needed to wait for them to build off Nougat source (aka 3.0.2-1).
Keep me posted and I will try to get more updates going
EDIT - I always keep my tab decrypted - which means when I'm screwing around it invariably gets re-encrypted and I have to wipe it
Anyone using GApps that include the setup wizard (stock for example - ironically the one I direct linked to in OP LOL) - you WILL see FCs until you can get out of that wizard and grant location permissions to Google Play services - to to get off that wizard screen (thanks to @replica102 in N6 forum):
Just tap on the four corners of the screen, starting from top left, clockwise. Do it right, and you'll get sent to home screen
Or use Pico/Nano and grab only the GApps you want
I'm happy to report that the ROM is VERY smooth! Thanks for all your hard work!
bshiznit said:
EDIT - I always keep my tab decrypted - which means when I'm screwing around it invariably gets re-encrypted and I have to wipe it
Click to expand...
Click to collapse
As far as that goes, I just always head to twrp before first boot, and flash fed patcher v8. Never have to worry about it re-encrypting it
SuperSU?
I noticed that SuperSU got crossed out after I got started. Does that mean it isn't rooted yet? I have tried the latest beta but still no good. Any idea's?
wantowan2 said:
I noticed that SuperSU got crossed out after I got started. Does that mean it isn't rooted yet? I have tried the latest beta but still no good. Any idea's?
Click to expand...
Click to collapse
I tried flashing the latest beta and went into a bootloop. I tried fixing contexts, but still no dice. I just wiped and reflashed the ElementalX kernel. I still wish I could get root to work, too!
[RECOVERY][EXYNOS] TWRP 3.5.2_9 for S10e|S10|S10+ (UPDATE: 2021-06-07)
This project provides the TWRP recovery for the Samsung Galaxy S10e (SM-G970F, beyond0lte), S10 (SM-G973F, beyond1lte) and S10+ (SM-G975F, beyond2lte).
{
"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"
}
This recovery supports FBE decryption of AOSP based ROMs like LineageOS, OmniROM etc. There is no support for Samsung ODE in TWRP yet. If you're interested, help to provide it is welcome.
FEATURES
File-Based Encryption (FBE) support
MTP and ADB support
EXT4 support
F2FS support
EXFAT support
Provides unzip
Additional languages
KNOWN ISSUES
If you decrypt /data with TWRP, the trustzone thinks this is a failed unlock attempt and will lock the storage for 1d
'adb sideload' doesn't work
DOWNLOAD
Make sure you download the .img.xz and corresponding .asc.txt file (see INTEGRITY)! You can decompress the the recovery image using p7zip or xz.
You can always find the latest version of the recovery under the follwing links:
S10e
S10
S10+
INTEGRETY
The recovery images also come with an GPG armor file (.asc). With that file you verify that the image I created hasn't been altered.
How do you do that?
Download my gpg keyring here: https://cryptomilk.org/gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg.
Download the recovery.img.xz and recovery.img.xz.asc.txt file
Rename the recovery.img.xz.asc.txt file to recovery.img.xz.asc
Verfiy the signature using the following command:
Code:
gpg --keyring ./gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg --verify recovery.img.xz.asc
A good tutorial is: How to verify signatures for packages from the Tor Project.
SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you open your device for malware!
What a Wurst!
Contributors
modpunk, derf elot
Source Code: https://github.com/whatawurst/android_device_samsung_beyond0lte/tree/twrp-9.0
Version Information
Status: Stable
Current Stable Version: 3.4.0-0
Stable Release Date: 2020-06-12
Created 2020-03-16
Last Updated 2020-06-12
FAQ
How do boot into the bootloader/download mode?
Here are the steps:
Turn off your phone
Press and hold the volume down and bixby keys
Connect a USB cable attached to your computer
The 'Bixby' button is the button below the volume keys.
How do boot into recovery mode?
Turn off you phone
Press and hold the volume up and bixby and power key
You can also do the above when you reboot the phone, once the screen turn black press the buttons.
How do I reboot my phone?
Press and hold the volume down and power key for at least 7 seconds.
How do I unlock my device?
Not that if you unlock your device, your phone will be factory reset! Make sure to make backups.
To unlock your device:
Go to Settings -> About Phone and find the "Build Number"
Tab the build number several times till it tells you that you unlocked the Deverloper Settings
Go to Settings -> System -> Advanded -> Developer Settings
Enable "OEM Unlock"
Reboot to bootloader mode (see above)
Follow the instruction displayed on screen and unlock your device
How do I flash the recovery?
After you unlocked the bootloader:
Boot into download mode (see above)
Flash recovery.img and vbmeta-disabled.img using Odin or Heimdall.
What is VBMETA?
Your phone has a partition for storing cryptographic hashes to verify the validity of the flashed software to all the partitions on your system. This is called Android Verified Boot.
In order to flash a recovery.img you need to replace the VBMETA image with a custom image to disable the checks. You can find a vbmeta-disabled.img here.
CHANGELOG
2020-07-24
Update to Linux Kernel 4.14.189
Updated to CTF3 blobs
Removed TWRP app
2020-06-09
Update to TWRP 3.4 (Fixes for SAR and multi user decryption)
Update to Linux Kernel 4.14.183
Fixed ADB only mode
Good Job!
ExtremeGrief said:
Good Job!
Click to expand...
Click to collapse
Thank you
I'm working on S10 and S10+.
If someone is interested to get it working with stock we could look into Samsung ODE. I don't need it for LineageOS.
modpunk said:
Thank you
I'm working on S10 and S10+.
If someone is interested to get it working with stock we could look into Samsung ODE. I don't need it for LineageOS.
Click to expand...
Click to collapse
I don't think TWRP supports Samsung FDE.
By the way for S10(+) just change kernel.
Alright so what are the differences between this and the already available twrp by ian?
stefan243546 said:
Alright so what are the differences between this and the already available twrp by ian?
Click to expand...
Click to collapse
See the features list, this recovery has support for FBE decryption on AOSP based ROMs. Also USB is working correctly and not making your phone so hot that you can fry an egg on it.
It should be possible to format /data and use FDE encryption now.
@modpunk
Thanks a lot. I was waiting for this for some time now.
Two questions:
1) FBE: Do i need to come from stock to have FBE working? Or is it ok to format /data from within TWRP to activate FBE with the right settings in fstab? I am using Lineage. Did you try that combination? I tried to keep FBE in the past but upon rebooting LineageOS TWRP kept stuck in the splash screen because it was not able to handle FBE.
2) Would it be possible to provide the build steps or would you consider pushing your work on FBE into the official repo? As i can see Ianmac's TWRP version isnt capable of dealing with FBE yet so it would be great to have it official.
Thanks for all your hard work. Much appreciated.
angela5246 said:
@modpunk
Thanks a lot. I was waiting for this for some time now.
Two questions:
1) FBE: Do i need to come from stock to have FBE working? Or is it ok to format /data from within TWRP to activate FBE with the right settings in fstab? I am using Lineage. Did you try that combination? I tried to keep FBE in the past but upon rebooting LineageOS TWRP kept stuck in the splash screen because it was not able to handle FBE.
Click to expand...
Click to collapse
Normally, LineageOS sets up FBE by default if the fstab is configured to use FBE. I'm currently working on a LineageOS ROM for the S10e and FBE is working just fine. Normally all you have to to is to format /data. I dunno which ROM you're using and if it has FBE turned on by default.
angela5246 said:
2) Would it be possible to provide the build steps or would you consider pushing your work on FBE into the official repo? As i can see Ianmac's TWRP version isnt capable of dealing with FBE yet so it would be great to have it official.
Thanks for all your hard work. Much appreciated.
Click to expand...
Click to collapse
Take a look at https://github.com/whatawurst and check the corresponding twrp-9.0 branches (Kernel, platform, device).
I see.
So just for clarification: Do you say FBE should work in theory with LOS or did you try it actually? Let me tell you about my experience.
I came from stock to LOS 17 provided by Ivan. Kept the original fstab which has FBE enabled. Didnt format /data so FBE was kept. After flashing LOS from within TWRP i booted into LOS. All fine. But on the first reboot or shutdown the phone automatically goes to TWRP. And there it stucks at the splash screen. At that point only flashing to stock is helping. So Ianmac's TWRP is not able to handle FBE. Are you sure this is different with yours?
I've added TWRP for more devices.
With the current release MTP isn't working. However I think I have a fix.
Will this twrp work with one ui 2.1?
I dont think so. But the ctc9 sources are up now.
mcgomfer said:
Will this twrp work with one ui 2.1?
Click to expand...
Click to collapse
Why shouldn't it work?
hanspampel said:
I dont think so. But the ctc9 sources are up now.
Click to expand...
Click to collapse
I don't see what the recovery has to do with CTC9 kernel sources at all.
I've uploaded new versions which fixes MTP.
modpunk said:
I've added TWRP for more devices.
Click to expand...
Click to collapse
Can you support Note10+ devices?
Sent from my SM-N975F using Tapatalk
{
"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"
}
**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****
NOTE: I allow off topics in my thread. I'm also open for any fun. Discussion about ROMs is permitted as far suggestions. However what isn't tolerated is belittling of devs and or their work. Thank you.
DerpFest 11
About us:
Derpfest is an UNOFFICIAL, heavily customized build of AOSiP. It uses a base of AOSiP and adds features that AOSiP doesnt have.
note: AOSiP and DerpFest teams are in no way related.
Team DerpFest:
Alexander Brunswig (nurkeinneid)
David Setiawan
Bug reporting:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
[*]Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
[*]If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
[*]If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
[*]Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Click to expand...
Click to collapse
Latest Downloads:
DON'T FLASH GAPPS, ALREADY INCLUDED
Click to expand...
Click to collapse
DOWNLOAD
Click to expand...
Click to collapse
If you like my work, consider a donation
My Paypal
FAQ and Install instructions:
Pre-installation:
TWRP (Download from here)
First time installation:
If coming from any other ROM, it's recommended to flash MIUI 12 and boot to it once in order to update firmware.
Backup your data to PC, OTG flash drive
Reboot to recovery
Factory reset from recovery and format data (where you type "yes")
Reboot to recovery
Flash derp.zip wipe cacha & dalvik
Dont Flash gapps /its included/ only reboot to system
After passed setup screen, reboot to TWRP and flash Magisk zip if you want
Enjoy
Update installation:
Through recovery:
Boot to recovery (optional make a backup)
Flash updated Derp rom zip and TWRP installer zip then reboot the system
Enjoy
Current Issues/Information:
* If you want to use third party auto fill/password manager, you need to update Google app to latest beta version
Current Issues/Information:
* If you want to use third party auto fill/password manager, you need to update Google app to latest beta version
Credit/Thanks:
Mike Williams (founder and creator of AOSiP)
Google for Android and AOSP
LineageOS
AICP
ABC ROM
AquariOS
BootleggersROM
PixelExperience
OmniROM
Cory Collins
---------
Any others we may have forgotten to credit
And last but not the least, all our testers, who have helped us to squash many bugs so that we can try to release builds that as are flawless as possible
Click to expand...
Click to collapse
XDAevDB Information
DerpFest, ROM for the Miatoll devices
Contributors @bezke
ROM Source https://github.com/DerpFest-11
Kernel Source https://github.com/ArrowOS-Devices/android_kernel_xiaomi_sm6250
ROM OS Version: 11.x
ROM Kernel: Linux 4.14.
Based On: AOSP
Version Information
Status: Alpha
Created 2019-12-22
Changelogs:
2021. 01.17.
* 2021. jan security patch with updated fingerprint. Use Kdragon magisk patch for working cts.
* many new customizations /edge lighting + etc.../
2021. 01.03.
* Bluetotth fixed
* many new customizations
2020.12.22.
*Initial build /bluetooth bugs/
Screenshoots:
How to be decrypt??do I need to format all the time when I flash a rom??
ZeroVirus said:
How to be decrypt??do I need to format all the time when I flash a rom??
Click to expand...
Click to collapse
Which recovery use you?
Note::: @ A11 ROMS in Orangefox recovery always disable lockscreen and fingerpsint, so you can enter the recovery and will visible files..............
Will Bluetooth audio work?
bezke said:
First time installation:
If coming from any other ROM, it's recommended to flash MIUI 12 and boot to it once in order to update firmware.
Backup your data to PC, OTG flash drive
Reboot to recovery
Factory reset from recovery and format data (where you type "yes")
Reboot to recovery
Flash crDroid zip and TWRP installer zip
Reboot to recovery
Flash gapps and reboot to system
After passed setup screen, reboot to TWRP and flash Magisk zip
Enjoy
Update installation:
Through recovery:
Boot to recovery (optional make a backup)
Flash updated Derp rom zip and TWRP installer zip then reboot to recovery
Flash gapps, Magisk and reboot to system
Enjoy
Click to expand...
Click to collapse
Your steps don't make sense, the first install steps refer to crDroid when this is Derpfest, it also says to flash twrp via recovery when the default MIUI recovery does NOT have any option to do so or to flash any other zips (when in fact your link is of OrangeFox, that isn't TWRP) and both the "first time" and "update instructions" steps say to flash gapps when in bold letters above the link you say not to flash them.
clean up your post bruh, because these steps look like a copypaste ya took from a crDroid thread you grabbed
Update added!
Fixed bluetoth..
& Many new settings
I'm facing an issue. Gboard has a bad layout. I like the ROM but that bug is annoying to me
bezke said:
Update added!
Fixed bluetoth..
& Many new settings
Click to expand...
Click to collapse
You may wish to update the "TWRP" link in your OP to point to the "miatoll" folder (instead of "curtana" - which will only lead to a dead link).
is there a version of your rom without GAPPS?
@bezke
Hi, master.
I have a joyeuse and unfortunately it doesn't flash.
I think it's bad access to /system.
No Android 11 works on my joyeuse here on xda and unfortunately there aren't many phones here.
I tried your Android 10 RR, which works like a charm.
But unfortunately I'm not lucky with Android 11. I think the problem is in the dynamic partition (/system_root, /vendor, /product). Twrp can't mount it.
LiberteCzech said:
@bezke
Hi, master.
I have a joyeuse and unfortunately it doesn't flash.
I think it's bad access to /system.
No Android 11 works on my joyeuse here on xda and unfortunately there aren't many phones here.
I tried your Android 10 RR, which works like a charm.
But unfortunately I'm not lucky with Android 11. I think the problem is in the dynamic partition (/system_root, /vendor, /product). Twrp can't mount it.
Click to expand...
Click to collapse
which TWRP are you using?
i have installed the OrangeFox Recovery project and it works.
you must follow certain procedure and should be fine.
Not every Android 11 works for me but it is not due to access to the partitions (at least i believe)
i had problems with SimCards which were not recoginized.
at this moment i had installed the Legion Rom based on the Android 11.
works well, Magisk installed, Fdroid with all apps too.
Safetynet passed.
netflix runs w/o issues.
i followed this procedure:
1- install TWRP (Russian one exe file) and enter TWRP.
2 - click on Wipe, then on Format Data -> type "yes" (this will decrypt the phone)
3 - restart the phone to TWRP
4 - In TWRP, i installed the OrangeFox Recovery Project (Version 11 Alpha)
5 - Restart to System
you can find all links to download below:
TWRP / Orangefox recovery for Redmi Note 9 Pro (Joyeuse)
Edit April 29, 2023: - Latest MIUI.EU ROM MIUI14 based on Android 12: V14.0.3.0 - Fastboot install file, because Android 12 recovery was not yet available at the time of production...
xiaomi.eu
btw, i tried:
- Carbon (there were some missing features) - https://forum.xda-developers.com/t/rom-unofficial-11-0-carbonrom-cr-9-0-miatoll.4210823/
- Fluid (worked more than well) - https://forum.xda-developers.com/t/...-fluid-1-1-for-miatoll.4212633/#post-84226211
- LegionOS - https://forum.xda-developers.com/t/...rtana-excalibur-gram-joyuese-unified.4188403/
i had problems with:
- Pixel Experience (not recognized SimCards)
- LineageOS (crashing)
hope it helps you a bit.
@Seba_Poland
I tried these.
I didn't try OrangeFox because I think there is a problem with encryption, as Bezke wrote, if I understand it good..
twrp-3.4.0-14-curtana-unified-mauronofrio
PBRPMiatoll20201014
PBRP-miatoll-3.0.0-20201101-1929-BETA
TWRP-3.4.1B-joyeuse-fix.img
I'll probably try.
*I use magisk hide, magisk hide props and gpay fix, so the safety net works well for me. I do not use Netflix, I cannot confirm.
LiberteCzech said:
@Seba_Poland
I tried these.
I didn't try OrangeFox because I think there is a problem with encryption, as Bezke wrote, if I understand it good...
Click to expand...
Click to collapse
OrangeFox has no problem with encryption.
DarthJabba9 said:
OrangeFox has no problem with encryption.
Click to expand...
Click to collapse
I noticed there is a new version, beta R11.0.1 of the OrangeFox. is it worth to install?
LiberteCzech said:
@Seba_Poland
I tried these.
I didn't try OrangeFox because I think there is a problem with encryption, as Bezke wrote, if I understand it good..
Click to expand...
Click to collapse
Try latest OrangeFox ( 30 December 2020 ), the "decryption issues with custom Android 11 ROMs" fixed, you can find here: https://orangefox.download/device/miatoll
I have experience with Orangefox recovery on my previous phone, is the best recovery for Redmi note 7, using now on my note 9pro too, DarthJabba9 is a great developer.
vlouis said:
Try latest OrangeFox ( 30 December 2020 ), the "decryption issues with custom Android 11 ROMs" fixed, you can find here: https://orangefox.download/device/miatoll
I have experience with Orangefox recovery on my previous phone, is the best recovery for Redmi note 7, using now on my note 9pro too, DarthJabba9 is a great developer.
Click to expand...
Click to collapse
exectly, i updated and it has encrypted the partitions w/o issues.
btw. i have same experience with RN7 and OrangeFox.
the only bottleneck is the backup restore. it took some time until i released how to proceed.
@Seba_Poland @vlouis @DarthJabba9
All right, guys!
So OrangeFox the only recovery with which I can flash Android 11 and the system will boot!
Other recoveries must have a problem on Joyeuse.
Thanks for the help!
LineageOS 18.1 for Sony Xperia XZ Premium
{
"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"
}
RELEASE
This is an alternative ROM for the Sony Xperia XZ Premium, offering several privacy features.
Please report any issues you observe apart from the ones listed below. Logs are needed for fixing anything (preferably dmesg and logcat).
FEATURES
EAS kernel (thanks to @linckandrea )
Forced Encryption with FDE (Full Disk Encryption)
DOWNLOAD
Please check changelogs and download links at #2
maple (G8141):
twrp-3.5.0-0-20210117-maple
maple_dsds (G8142):
twrp-3.5.0-0-20210117-maple_dsds
INSTALLATION
Clean flash recommended when updating from Android 10 or stock:
1. Flash latest stock firmware (47.2.A.10.107) with newflasher.
2. Flash and boot the new twrp given in this thread.
3. Format data and wipe everything.
4. Flash the ROM, GApps (if needed) and root (if needed).
5. If you have IMS (VoLTE) working on stock, enable IMS in Settings - XperiaParts.
Note: If you are updating from Android 10 and can't boot the new TWRP, please backup your stuffs and format data by using either the old TWRP or fastboot -w. This is required because there are some adjusts in userdata image size to fix FDE encryption.
Note: There is not going to be a LOS su addon anymore. If you need root, flash a root manager of your choice. No guaranteed support from LOS for this.
Google Apps
Both OpenGApps and NikGApps should work. You can download and install the Google Apps from opengapps.org. You need ARM64 and 11.x. Open GApps for Android 11 is still in beta. You can download those releases here.
KNOWN ISSUES
WFD is not working
Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
Contributors
derf elot, modpunk, Rooted_Ansh, linckandrea
Telegram Group
[Tinder][EN/DE/♋] Xperia XZ Premium - Sticker Fightz Biatch
Development group for XZP - Lead by: Everyone Do not spam and cooperate with developers. Google first before asking any help
t.me
Source Code
maple: https://github.com/whatawurst/android_device_sony_maple
maple_dsds: https://github.com/whatawurst/android_device_sony_maple_dsds
kernel: https://github.com/whatawurst/android_kernel_sony_msm8998
Rom Information
ROM OS Version: Android 11
ROM Kernel: Linux 4.4
Version Information
Status: Stable
Stable Release Date: 2022-03-23
Thread Information
Created 2021-01-21
Last Updated 2022-03-23
2022-03-23
Last build of Lineage 18.1 (and probably nobody needs this anymore)
Lineage 19.1 is already available, check this thread.
G8141: https://androidfilehost.com/?fid=14655340768118440781
G8142: https://androidfilehost.com/?fid=14655340768118440782
2021-10-7
irregular update
G8141: https://www.androidfilehost.com/?fid=7161016148664819265
G8142: https://www.androidfilehost.com/?fid=7161016148664819266
2021-6-29
irregular update
G8141: lineage-18.1-20210628-UNOFFICIAL-maple.zip
G8142: lineage-18.1-20210628-UNOFFICIAL-maple_dsds.zip
2021-3-31
March Security Update
Vulkan fix (thanks to @linckandrea )
New IMS implement (Please enable IMS option in Xperia Parts if you have IMS working on stock.)
EAS kernel (thanks to @linckandrea )
Forced Encryption since this release.
Download links:
G8141: lineage-18.1-20210331-UNOFFICIAL-maple.zip
G8142: lineage-18.1-20210331-UNOFFICIAL-maple_dsds.zip
2021-01-20
Initial release. Download links:
G8141:lineage-18.1-20210120-UNOFFICIAL-maple
G8142: lineage-18.1-20210119-UNOFFICIAL-maple_dsds
Reserved.
No1Alien said:
LineageOS 18.1 for Sony Xperia XZ Premium
RELEASE
This is an alternative ROM for the Sony Xperia XZ Premium, offering several privacy features.
Please report any issues you observe apart from the ones listed below. Logs are needed for fixing anything (preferably dmesg and logcat).
FEATURES
Signed with dev keys
Up-to-date kernel
WireGuard kernel support
FDE Encryption support
DOWNLOAD
You can download the latest releases here:
maple (G8141):
twrp-3.5.0-0-20210117-maple
lineage-18.1-20210120-UNOFFICIAL-maple
maple_dsds (G8142):
twrp-3.5.0-0-20210117-maple_dsds
lineage-18.1-20210119-UNOFFICIAL-maple_dsds
INSTALLATION
Clean flash recommended when updating from Android 10 or stock:
1. Flash latest stock firmware (47.2.A.10.107) with newflasher.
2. Flash and boot the new twrp given in this post.
3. Flash the ROM, GApps (if needed) and root (if needed).
Note: There is not going to be a LOS su addon anymore. If you need root, flash a root manager of your choice. No guaranteed support from LOS for this.
Google Apps
Both OpenGApps and NikGApps should work. You can download and install the Google Apps from opengapps.org. You need ARM64 and 11.x. Open GApps for Android 11 is still in beta. You can download those releases here.
KNOWN ISSUES
WFD is not working yet (waiting for new non-BSP blobs)
Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
Contributors
derf elot, modpunk, Rooted_Ansh
Telegram Group
[Tinder][EN/DE/♋] Xperia XZ Premium - Sticker Fightz Biatch
Development group for XZP - Lead by: Everyone Do not spam and cooperate with developers. Google first before asking any help
t.me
Source Code
maple: https://github.com/whatawurst/android_device_sony_maple
maple_dsds: https://github.com/whatawurst/android_device_sony_maple_dsds
kernel: https://github.com/whatawurst/android_kernel_sony_msm8998
Rom Information
ROM OS Version: Android 11
ROM Kernel: Linux 4.4
Version Information
Status: Stable
Stable Release Date: 2021-01-21
Thread Information
Created 2021-01-21
Last Updated 2021-01-21
Click to expand...
Click to collapse
Awesome work mate!
just tried flashing twrp to my phone (single sim) running aosp 11, and it couldnt get past the splash screen.
also tried fastboot booting the image,and it just hangs on the sony logo.
it could be the kernel im using, ill try a complete wipe and reinstall of this rom and twrp tonight.
EDIT: flashing stock rom to start fixed it. everything works as it should now.
Gcam desteği?
The twrp-3.5.0-0-20210117-maple isn't working well on G8141 model with this ROM. I've using twrp 3.2.1 and I can say that it is more stable. I've seen that after the flashing I cannot reach the TWRP after reboot and I need to reinstalling the TWRP again. With others ROM's the issue not exist.
ted5300 said:
The twrp-3.5.0-0-20210117-maple isn't working well on G8141 model with this ROM. I've using twrp 3.2.1 and I can say that it is more stable. I've seen that after the flashing I cannot reach the TWRP after reboot and I need to reinstalling the TWRP again. With others ROM's the issue not exist.
Click to expand...
Click to collapse
On my g8141 all things work. I have flash twrp 3.5 with old 3.4 . Format data,reboot twrp,format data,reboot back to twrp. After this 2 format,i flash the rom+gapps mini.(no reflash stock)All runs good. But i miss the PixelExp
ted5300 said:
The twrp-3.5.0-0-20210117-maple isn't working well on G8141 model with this ROM. I've using twrp 3.2.1 and I can say that it is more stable. I've seen that after the flashing I cannot reach the TWRP after reboot and I need to reinstalling the TWRP again. With others ROM's the issue not exist.
Click to expand...
Click to collapse
i was having the same issue, i fixed it by flashing back to stock firmware before flashing twrp and this rom.
now running twrp 3.5.0 and lineageos 18.1 rooted with magisk 21.4 with no issues.
born2bkilled said:
just tried flashing twrp to my phone (single sim) running aosp 11, and it couldnt get past the splash screen.
also tried fastboot booting the image,and it just hangs on the sony logo.
it could be the kernel im using, ill try a complete wipe and reinstall of this rom and twrp tonight.
EDIT: flashing stock rom to start fixed it. everything works as it should now.
Click to expand...
Click to collapse
ted5300 said:
The twrp-3.5.0-0-20210117-maple isn't working well on G8141 model with this ROM. I've using twrp 3.2.1 and I can say that it is more stable. I've seen that after the flashing I cannot reach the TWRP after reboot and I need to reinstalling the TWRP again. With others ROM's the issue not exist.
Click to expand...
Click to collapse
No1Alien said:
Note: If you are updating from Android 10 and can't boot the new TWRP, please backup your stuffs and format data by using either the old TWRP or fastboot -w. This is required because there are some adjusts in userdata image size to fix FDE encryption.
Click to expand...
Click to collapse
Thank you for your feedback, but the situation is the same with TWRP. I've used fastboot -w. nothing changed. Then I format data from the new TWRP 3.5 and after reboot I can't go to TWRP again. Some other ideas what I can try? Regards
ted5300 said:
Thank you for your feedback, but the situation is the same with TWRP. I've used fastboot -w. nothing changed. Then I format data from the new TWRP 3.5 and after reboot I can't go to TWRP again. Some other ideas what I can try? Regards
Click to expand...
Click to collapse
Start from stock ROM. Use xperifirm to download the latest stock Rom and use newflasher to flash it. Then flash twrp, lineage and magisk.
Thats how I did it.
Thanks for your hard work on this. Flashed this, working great, love having 2 day battery life. With NO gapps. It’s all about privacy
Hopefully you are still working on is
First of all: Many thanks for spending all the effort to create this ROM for the old Sony XZ Premium!!!
So far I was using Bliss ROM but the new Android security issues made me to wake up and look for something fresher ;-)
I do have a G8141 (German) device. Flashing worked quite well and the system was booting up quickly. (ROM+TWRP 3.5+openGApps nano+Magist 21.4)
So far I detected just one issue yet which I would like to report:
WLAN and mobile connection not stable. I required me 4 reboot attempts to get a more stable connection. WLAN was constantly dropping out and only a reboot at the end made the device to reconnect. Same for cellular connection. After around 4 reboots I have a stable connection now.
I will monitor the behaviour and hopefully it will become stable after all Google Apps are installed etc..
I will let you know.
NFec__ said:
First of all: Many thanks for spending all the effort to create this ROM for the old Sony XZ Premium!!!
So far I was using Bliss ROM but the new Android security issues made me to wake up and look for something fresher ;-)
I do have a G8141 (German) device. Flashing worked quite well and the system was booting up quickly. (ROM+TWRP 3.5+openGApps nano+Magist 21.4)
So far I detected just one issue yet which I would like to report:
WLAN and mobile connection not stable. I required me 4 reboot attempts to get a more stable connection. WLAN was constantly dropping out and only a reboot at the end made the device to reconnect. Same for cellular connection. After around 4 reboots I have a stable connection now.
I will monitor the behaviour and hopefully it will become stable after all Google Apps are installed etc..
I will let you know.
Click to expand...
Click to collapse
Finally I am giving up. I am not able to get a stable WLAN or cellular connection. After installing it again and again (format data twice, factory reset etc., starting all over with latest stock FW) am not getting it working properly. After 1-2 hours, WLAN is not able to connect anymore and cellular is detected incl. carrier but dropping off and data connection not possible to establish.
Really strange was the latest/ last Sony FW everything works. With other ROMS I am running into similar problems. Sometimes cellular is not detected, but WLAN works and sometimes both are not working. Last fully working alternative ROM was Bliss from late September 2020. After reading that several of you are successfully using this ROM I start to believe that this is perhaps a problem with my device made for the German market...
Is there an option to hide the "hide keyboard" button at the bottom while typing? I've already used full gesture but it still shows a bar with hide keyboard button at the bottom while typing.
Thanks OP for bringing LOS18 to maple!!
The best Android 11 ROM. Using it for over a week and everything works. Battery life is two days with regular use.
Weird, after installation and enter the SIM pin and connect to the Wi-Fi network, it take me charge directly from the carrier network for data. Sould be better what connection I will choose during the first installation as primary (Wi-Fi or mobile ) and not connecting by default directly to the mobile internet. With others Android 11 ROMs this issue not exits. Some thoughts?
fastboot -w
install twrp-3.5.0-0-20210117-maple
install lineage-18.1-20210120-UNOFFICIAL-maple from twrp
I want to install gapps but after first run i cannot back to twrp - when I try to run in recovery mode I only see black screen.
I try to install oldest twrp - no results.
Any idea what is the problem ?
Margiel said:
fastboot -w
install twrp-3.5.0-0-20210117-maple
install lineage-18.1-20210120-UNOFFICIAL-maple from twrp
I want to install gapps but after first run i cannot back to twrp - when I try to run in recovery mode I only see black screen.
I try to install oldest twrp - no results.
Any idea what is the problem ?
Click to expand...
Click to collapse
That’s what just happened to me. But I didn’t install gapps. Just went black screen, won’t boot up. Also I’ve had it running for about 3-4 weeks with no issues. Now this. Can’t even get into twrp
LineageOS 20.0 for Sony Xperia XZ Premium
{
"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"
}
RELEASE
This is an alternative ROM for the Sony Xperia XZ Premium, offering several privacy features.
Please report any issues you observe apart from the ones listed below. Logs are needed for me to fix anything (preferably dmesg and logcat). I can't test NFC very thoroughly, to please report your findings.
FEATURES
Signed with dev keys
Up-to-date kernel
WireGuard kernel support
DOWNLOAD
You can download the latest releases and TWRP here:
ROM:
https://sourceforge.net/projects/yoshino/files/maple/lineage-20.0/
TWRP:
https://sourceforge.net/projects/yoshino/files/maple/twrp/
Suggested Gapps (MindTheGapps) - choose 13.0.0/arm64:
https://androidfilehost.com/?w=files&flid=322935
or
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
Check the ChangeLog below for firmware requirements!
INSTALLATION
Before first install: flash and boot into the TWRP provided in this thread, format data, reboot to recovery and wipe all internal partitions, then flash the ROM, GApps and root (if needed).
Or if you are coming from Lineage 19.x, dirty flash to 20.0 is possible too: flash the new TWRP, ROM, and GApps, su addons (if needed).
Note: There is not going to be a LOS su addon anymore. If you need root, flash a root manager of your choice. No guaranteed support from LOS for this.
When updating from previous builds, simply dirty flash the ROM is enough, decryption in new TWRP works now
Recommended GApps: MindTheGapps provided in this thread. (Important to flash with rom)
KNOWN ISSUES
You tell me...
Contributors
derf elot, modpunk, Rooted_Ansh
Thanks to the yoshino testers (let me know if I forgot to add you)
coin3x, feduss, GiaSen, Gizanagi, hsheemi, kaancaliskan, sohrab1985
Source Code
maple: https://github.com/whatawurst/android_device_sony_maple
maple_dsds: https://github.com/whatawurst/android_device_sony_maple_dsds
kernel: https://github.com/whatawurst/android_kernel_sony_msm8998
Rom Information
ROM OS Version: Android 13
ROM Kernel: Linux 4.4
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2023-05-10
All credits goes to derf elot and all the other developers involved, I only post it.
SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you welcome malware on your device!
How to get root?
As mentioned before, there will not be an official su addon from LOS anymore. If you need root, flash an unofficial solution.
REQUIRED FIRMWARE:
CHANGELOG
2023-05-10 | 1.2 | 47.2.A.10.107
Updated to T QPR2 release (LineageOS upstream)
Updated to May 2023 Security updates (both ROM and kernel)
Our kernel now includes updates by CIP and is up-to-date with tag st40 - thanks also to Flamefire for help with some of these (1)
Reduced zram size to 25% (1gb) of out total RAM to have more to use freely
Updated BT stuff for QPR2 (maybe offloading is working again? needs confirmation)
Added the option to reflash the mbn via OpenCS (see Xperia Parts) - thanks also to shank03 & Flamefire (2)
Fully enabled IMS on Congstar Germany via overlay on lilac
Possibly some battery/performance optimizations here and there
Fixed Android Auto support
Added new LineageOS "Charging control hal" for battery charging care (3)
Maybe more I forgot...
(1) The CIP kernel includes fixes for issues and security vulnerabilities from 4.14 kernel (see https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git)
(2) A somehwat lengthy explanation: This option is off by default on fresh installs. When upgrading, this should be enabled because we enforced this for everybody previously. However, this option is only required for certain carrier mbns that enable IMS. Personally, I know that the O2/Telefonica Germany mbn needs this, otherwise you get a crashing modem at every boot (unless you switch to 3g before rebooting and back to LTE after boot). I generally recommend playing with this option, and if you don't need it (e.g. modem doesn't crash on boot), just keep it off - like mentioned before, this is now the default behavior of OpenCS on fresh installs anyway.
(3) This is not finalized or merged upstream in LineageOS yet, but seems like a nice feature to have and test drive already. Some bugs may be possible.
2023-01-08 | 1.1 | 47.2.A.10.107
Updated to T QPR1 release (LineageOS upstream)
New default camera app (LineageOS upstream) - yes, we cannot change video fps currently (thanks Sony!)
Any other updates by LineageOS upstream
Kernel security updates (also thanks to Flamefire)
Dropped keyprovd service - it is useless on unlocked BL anyway
Show 4G instead of LTE icon - saves some space too
Enable IMS by default - this still only works if carrier is supported
Fix some selinux denials (also thanks to Flamefire)
Fixup ViLTE dependencies - this might in theory work again, but it's not enabled yet
2022-10-03 | 1.0 | 47.2.A.10.107
Initial release
Is it the same procedure as always?
first flash latest available Stock ROM(47.2.A.10.107) and boot into it once.
Then flash the twrp,
then flash the rom?
Gordon1979 said:
Is it the same procedure as always?
first flash latest available Stock ROM(47.2.A.10.107) and boot into it once.
Then flash the twrp,
then flash the rom?
Click to expand...
Click to collapse
Yes, That's it.
Flash gapps as well and maybe magisk if you want root.
Try it yesterday, it work fine.
But dirty flash from los19.1 lead boot loop
Nothing bug so far.
But light theme with white text bug seem fix from los 19.1.
THANK YOU for your Great Work
patrriot said:
THANK YOU for your Great Work . IT is perfect.
Click to expand...
Click to collapse
Hi all, and sorry, i forgot translate to english.
dirty flash, bootloop to recovery
clean flash, bootloop to recovery
delete all internal partitions, /firmware, /dsp, etc...
Now my phone a black screen wit the blue led blinking when press power button, o connect to charger, but my computer do no recognice the phone, combo keys do not work.
Only i am the reponse of the hard brick.
Sorry to all.
juanantofb said:
Hola a todos.
flash sucio, ........
Click to expand...
Click to collapse
It seems you don't know the first thing about xda
Can you put the network speed indicator ① in position ②?
juanantofb said:
Hi all, and sorry, i forgot translate to english.
dirty flash, bootloop to recovery
clean flash, bootloop to recovery
delete all internal partitions, /firmware, /dsp, etc...
Now my phone a black screen wit the blue led blinking when press power button, o connect to charger, but my computer do no recognice the phone, combo keys do not work.
Only i am the reponse of the hard brick.
Sorry to all.
Click to expand...
Click to collapse
You should not wipe those partitions. They are not wipeable in the GUI for a reason.
You should be bale to recovery this by going into flash mode and re-flashing stock.
juanantofb said:
Hi all, and sorry, i forgot translate to english.
dirty flash, bootloop to recovery
clean flash, bootloop to recovery
delete all internal partitions, /firmware, /dsp, etc...
Now my phone a black screen wit the blue led blinking when press power button, o connect to charger, but my computer do no recognice the phone, combo keys do not work.
Only i am the reponse of the hard brick.
Sorry to all.
Click to expand...
Click to collapse
Do a TWRP install again in Fastboot mode. Hold down the VOL + key and then connect the data cable to the PC. Led Blue ON .
Install the Universal ADB drivers.
Bbb
Hi all, not posible to enter in fastmode or flashmode, i waiting to discharge battery, if i can not enter in fastmode i think that this Sony is in the finale of your life.
juanantofb said:
Hi all, and sorry, i forgot translate to english.
dirty flash, bootloop to recovery
clean flash, bootloop to recovery
delete all internal partitions, /firmware, /dsp, etc...
Now my phone a black screen wit the blue led blinking when press power button, o connect to charger, but my computer do no recognice the phone, combo keys do not work.
Only i am the reponse of the hard brick.
Sorry to all.
Click to expand...
Click to collapse
I'm sorry that this happened to your device.
As other friends mentioned in other posts you can recover from this by flashing the stock firmware IF you can get it to flash mode.
Hi, do not worry, the battery in this phone is the end of your life, more rom has been flashed.
The problem is that i can not put phone in flash mode, only the last posibility is to wait tha the phone discharge battery and i can enter in flash mode.
Thank.
sohrab1985 said:
I'm sorry that this happened to your device.
As other friends mentioned in other posts you can recover from this by flashing the stock firmware IF you can get it to flash mode.
Click to expand...
Click to collapse
Found a small bug but not effect daily use.
When choose font or icon shapes.
It always default to last option.
The change effect normally through.
Installation complete, with minor difficulties.
My instructions:
1. flash last firmware (47.2.A.10.107) --> green LED
2. reboot once completely, Play Store not required to set up
3. reboot to fastboot --> blue LED
Link driver: https://developer.android.com/studio/run/win-usb
4. flash twrp: fastboot flash recovery twrp-3.6.2_12-0-20221002-maple
5. reboot to twrp
6. format data + restart in recovery
7. format dalvic , system , cache , data , internal storage + restart in recovery [ NOT Vendor Format !!!!! ]
8. flash the ROM,
8.1 Flash theGApps
8.2 Format Dalvic, Cache
9. reboooooooot
Have Fun
Hello,
This is the first rom I installed on my phone ever. I took me all day to figure it out how to unlock bootloader, install TWRP and then ROMS. I tried three roms: crDroid, Nusantara, and this one. I like this one best. It is amazing that one person can make such an OS and a whole sony corporation can not make an update
P.S. It works very well, but on my phone icons do not have bubbles when for example a message arrives. Maybe that is a bug or simply I do not know how to enable them (Notification dot on app icon is enabled).
At first I thought that there is a bug then I could not access files on a phone from a computer, but later I find out that it is a new security feature of newer android OS (I changed it to file transfer always on in Developers options)
Thank you