[RECOVERY][UNOFFICIAL]TWRP 3.6.0 for 2020 Galaxy Tab A7 10.4[SM-T500] - Samsung Galaxy Tab A series ROMs, Kernels, Recover

{
"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

Related

[ROM][Unofficial][20180617]CarbonROM | cr-6.1 [payton]

Credits
Moto X4 is getting some custom rom love, because @erfanoabdi worked in BEAST mode and created the trees for this device, even though he does not own the device.
Obligatory Warning: This guide and ROM assumes you know the fundamentals of fastboot, flashing TWRP, and running a flash all. Your warranty is voided because of the unlocked bootloader. This is a Third Party ROM. Things may not work as expected compared to stock (for better or for worse).
Warning 2: If you can't do fastboot commands, do a flash all, root your device or flash TWRP/ROM, please do not ask for help here. If you cannot flash all back to stock, please stay stock for everyone's sake.
Warning 3: if you don't flash the firmware zip so both slots have the firmware, when you boot after flashing, you WILL have a bootloop or even a brick.
Warning 4 : This is an Engineering build, which means it's pre rooted and all apps have access to root. Only the SU binary is missing.
Warning 5 : Kernel is permissive.
This is an initial release and it WILL have bugs. If your phone is a daily, and you cannot afford downtime or random reboots then please do not flash.
I am new to this, DO NOT expect fixes on the fly. Post logcats and I will see what I can do.
{
"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:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
​
About Carbon ROM :
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Not Working :
[*] Engineering Build - you will get a strict mode red-rectangle flash.
no moto onenav gestuers
You tell me
How to Boot into fastboot/bootloader mode
1. Reboot phone, and keep volume down pressed while device is rebooting until you see bootloader mode screen.
2. While phone is off, press volume down and then press power button. Keep holding both until you see bootloader mode screen.
How to Install
Video is for LineageOS, but process is same for Carbon ROM as well.
Video
Moto X4 A/B Slots Explained
Steps
1. Download the ROM, TWRP (zip and Image), Gapps (optional) from Downloads section. Place TWRP image zip in same folder as where you have fastboot.
2. Prepare your phone for AOSP style ROMs. (download one of the firmwares depending on your model). Boot into bootloader mode.
Flash the firmware with the flash_all.bat (Windows) file or the flash_all.sh (Linux & Mac) (See links on Post #2).
Windows
Code:
flash_all.bat
Mac/Linux
Code:
./flash_all.sh
Tested only on XT1900-1 on Android 8.0 model for now. Feel free to try on other models. Check for any errors in the process, DO NOT proceed if you have any errors. Once flashed successfully, reboot into Android to make sure all is well.
Windows
Code:
fastboot reboot
Mac/Linux
Code:
./fastboot reboot
3. Wipe internal data. Reboot back into bootloader mode and run the command "fastboot -w" (this will erase EVERYTHING from your phone, even internal SD, but is needed to have these ROMs work). Make sure to remove your external sdcard before doing this. Once done, REBOOT into Android to make sure all is well. Skip all the setups.
Windows
Code:
fastboot -w
Mac/Linux
Code:
./fastboot -w
4. Transfer ROM zip and TWRP zip to internal memory of device. Reboot device into bootloader mode.
5. Boot to TWRP using fastboot. Using command prompt/terminal navigate to folder where fastboot is.
Windows
Code:
fastboot boot twrp-3.2.1-1-payton.img
Mac/Linux
Code:
./fastboot boot twrp-3.2.1-1-payton.img
5. Once booted into TWRP, click on Install - and select TWRP zip transferred in Step 1. Once done, Reboot back into system to check all is well.
6. Boot into TWRP again (reboot device, keep volume down pressed while device is rebooting. When you see bootloader mode, let go of volume down. Press volume up until you see recovery mode, press power button to select. Now you will boot into TWRP recovery).
8. Once in TWRP. Go to Wipe and swipe to factory reset. Go back, select Install and select Linage OS Rom zip, also add the TWRP zip file and click on install. Once done, wipe cache/dalvik.
Do note, recovery is built into kernel with our device so flashing any rom or kernel will result in TWRP being overwritten. DO NOT flash Magisk (any root package) or Gapps. Once ROM (and optional TWRP) have flash successfully, go to main menu :-
Now you have two options. If you WANT gapps do step 9. else go to 10. If you install gapps after booting into rom, gapps will crash. So, make your choice now.
9. Go back to TWRP main menu. Click on reboot, note down the slot you are on and select recovery.
You will now boot back into TWRP recovery. Click on reboot, and you should be on the other slot. Go back to main menu, transfer the gapps package to internal memory and install gapps.
10. Go back to TWRP main menu. click on reboot and select bootloader.
11. Once in bootloader mode. issue below command.
Windows
Code:
fastboot -w
Mac/Linux
Code:
./fastboot -w
Once done, reboot.
Windows
Code:
fastboot reboot
Mac/Linux
Code:
./fastboot reboot
11. To ROOT, booting into Android once is necessary whether you want gapps or not. After booting into Android once reboot back into TWRP, and then flash your root package zip, reboot and enjoy.
How to Update
Transfer rom, gapps and twrp zip to internal storage.
Boot to TWRP.
flash Rom + TWRP zip
Boot back to TWRP recovery
Flash GApps
Wipe Cache + Dalvik
Reboot to System
Coming from Another custom ROM, have already flashed firmware zip
Transfer rom, gapps and twrp zip to internal storage.
Boot to TWRP.
Wipe -> Swipe to factory reset
flash Rom + TWRP zip
Boot back to TWRP recovery
Flash GApps
Wipe Cache + Dalvik
Reboot to System
How to go back to stock
Support :
1) Search. Search, search, search. If you make the effort of reading atleast 5 pages back, most if not all your questions will be answered. I personally, will ignore any questions, if I know they have been answered in the last 5 pages. Not being rude, but please read.
2) If you can't find answers in last 5 pages, ask here, be respectful and have a good time.
Downloads :
TWRP (Zip + Image, Download 3.2.1-1): TWRP for Payton
ROM : Unofficial Carbon ROM (payton)
Gapps : OpenGapps
Magisk : Stable Magisk
Notes :
Only Clean Installation Please
Bug Report Without logs means nothing
3rd PARTY ADDONS/MODS :
While we have no issues with people using supersu/magisk/xposed/custom kernels/etc, we can't provide support for users who have them installed.
This thread is not the right place to discuss about mods/addons.
Reporting Bugs :
DO NOT Report bugs if you installed Xposed.
DO NOT Report bugs about Magisk Modules.
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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
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. Any bug not reported in the bug report format above may be ignored.
Sources :
Carbon ROM
Device tree :
moto-sdm660-common
payton
Kernel :
moto-msm8998
Vendor tree :
moto-sdm660-common
payton
XDA:DevDB Information
Unofficial Carbon ROM cr-6.1 for Payton, ROM for the Moto X4
Contributors
erfanoabdi, mightysween, gee one, Lineage Team, Carbon Team
Donations
Donate to Carbon ROM
Buy me Coffee.
ROM OS Version: 8.1.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: No Requirements
Based On: AOSP
Version Information
Status: Testing
Created 2018-06-13
Last Updated 2018-06-17
Firmwares
Firmwares
https://forum.xda-developers.com/showpost.php?p=76775043&postcount=2
mine002
Changelog
17th June 2018
* fixed FM radio
* userdebug build (no more red border) Thanks again @erfanoabdi
Excellent work. What would you say are the main differences between Carbon and Lineage?
sizz-lorr said:
Excellent work. What would you say are the main differences between Carbon and Lineage?
Click to expand...
Click to collapse
Lineage is pure stock android, whereas Carbon offer some customizations! I have not tried the ROM yet, i am on RR right now! But as far as I know, it is going to be stable! :fingers-crossed:
I would like to try this ROM, however, I'm hesitant to due to I have the TWRP v 3.2.1-0 which doesn't make nandroid backups that can be restored.
Does the posted TWRP version (3.2.1-1) make restorable nandroid backups?
------------
NetSpeedZ said:
I would like to try this ROM, however, I'm hesitant to due to I have the TWRP v 3.2.1-0 which doesn't make nandroid backups that can be restored.
Does the posted TWRP version (3.2.1-1) make restorable nandroid backups?
------------
Click to expand...
Click to collapse
I've restored from a nandroid on the newest twrp and haven't had an issue. Just remove any pin or lockscreen security before buying into twrp or you can't decrypt.
brandontowey said:
I've restored from a nandroid on the newest twrp and haven't had an issue. Just remove any pin or lockscreen security before buying into twrp or you can't decrypt.
Click to expand...
Click to collapse
Copy that. I don't have lock screen enabled, just the 'screen saver' that shows when phone senses motion nearby and shows the clock, etc.
Appreciate the clarification.
------------
New build is up.
Changelog in post 2.
brandontowey said:
I've restored from a nandroid on the newest twrp and haven't had an issue. Just remove any pin or lockscreen security before buying into twrp or you can't decrypt.
Click to expand...
Click to collapse
Follow-up question to your reply:
When you made your backup, did you include System Image? If so, when you restored did you enable Boot, Data, System and/or System Image?
------------
NetSpeedZ said:
Follow-up question to your reply:
When you made your backup, did you include System Image? If so, when you restored did you enable Boot, Data, System and/or System Image?
------------
Click to expand...
Click to collapse
I did whatever the default in TWRP was, backup and restore. I googled what I should do but there wasn't anything definite. I did get an error 255 from resting the Bluetooth thing so i just omitted it.
I'm on the fence looking at these new custom ROMs available for our X4, so please help me clarify a few points:
1) does Lineage have the option to set navigation bar height? If I'll take the plunge I'm interested in having a navigation bar narrower than Android' standard;
2) is it possible to tweak the kernel with Kernel Adiutor or something similar?
3) is it possible to install and use Moto Display in some way?
Thanks!
P.S. Plese bear with me as I'm asking the same questions all over the three custom ROMs threads.
One button navigation
Is one button navigation still not working on this rom?
superj1018 said:
Is one button navigation still not working on this rom?
Click to expand...
Click to collapse
not yet.

12-19 - ViperExperience Beta 14 | Android 13 | November 2022 Security Patch |GSI

{
"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"
}
ViperExperience 12L GSI for U12+
"Choose your flavor! - The next Generation Viper ROM"
Dear Community,
Venom ROMs takes the next big step for your HTC, as well as other Treble A/B devices out there! You want Android 11, but don't want to miss out on the hardware benefits of your HTC U12+? Or you want to enjoy all of your beloved HTC Apps on another OEM? Then we have the best of both worlds for you today (or very soon)! Decide for yourself between an Android Stock Experience, or an HTC Sense Experience by choosing between Pixel Launcher and HTC Sense 10 UI Launcher. On your HTC U12+ you can in addition continue to use your popular HTC features like HTC Edge Sense, HTC FaceUnlock and the HTC Camera!
We at Venom ROMs are using the AOSP GSI based on Android 11 to bring you the best HTC features paired with the latest Android AND Pixel experience from Android 10.
Thanks to @phhusson for his Treble experimentations repos, @JEANFRIVERA, @5m4r7ph0n36uru, @Captain_Throwback, @MassStash, @donmarkoni for all tests you did for me to make this ROM.
mikalovtch
Must have unlocked bootloader from htcdev.com or factory S-OFF
Download Viper Experience 11 GSI from Androidfilehost.com
Download „vbmeta_noverity.zip“ from Androidfilehost.com
Download latest TWRP from #2 post or Download latest PBRP from here: PBRP
Boot your Device in Bootloader Mode
Boot to TWRP or PBRP, using the following command:
Code:
fastboot boot nameoftwrpimage.img
Rename „vbmeta_noverity.zip“ to „update.zip“ and place it inside your adb/fastboot folder
Push „update.zip“ to your device, using the following command:
Code:
adb push update.zip /update.zip
Make sure you are on slot A on reboot page of TWRP or PBRP if not switch to slot A and fasboot boot twrp.img again
Flash „update.zip“ from recovery UI
Reboot to Download from recovery UI
Erase userdata and system using the following commands: (THIS WILL FORMAT INTERNAL STORAGE!)
Code:
fastboot erase userdata
and:
Code:
fastboot erase system
Flash Viper Experience 10 GSI, using the command:
Code:
fastboot flash system nameofimage.img
Rebootyour device, using the command
Code:
fastboot reboot
Setup and enjoy an mew ROM on your HTC U12+!
​
XDA:DevDB Information
12-04 - ViperExperience Beta 12 | Android 12L | April 2022 Security Patch |GSI , ROM for the HTC U12+
Contributors
mikalovtch, JEANRIVERA
Source Code: https://github.com/phhusson/treble_experimentations
ROM OS Version: Android 12L
ROM Kernel: Linux 4.x
ROM Firmware Required: Android 9 Pie
Based On: AOSP HTC Sense
Version Information
Status: Beta
Beta Release Date: 2020-12-22
Created 2020-03-07
Last Updated 2020-12-22
​
Prerequisites
PIE_noverity_vbmeta_both_slots-TWP.zip: This zip patches the stock vbmeta for BOTH slots to ensure the device will boot after flashing the GSI. The zip in the OP only patches slot A, so you would have to ensure you are on slot A when flashing the system image. This zip allows either slot to be used. Thanks @The_Walking_Playground for posting the updated zip!
Fixes
UPDATE-BeyondStock™_U12+_Exodus_Vendor_Fixes-CPTB-signed.zip: This zip patches the vendor partition on U12+ and Exodus devices to fix Bluetooth streaming/headset compatibility, and enables exFAT support with the stock and BeyondStock™ kernels (NOTE: The exFAT portion of this fix is no longer needed, but has no negative side effects).
Patches
UPDATE-BeyondStock™_Header_Patch_U12+_Exodus-CPTB-signed.zip: This zip patches the boot.img header of the installed kernel so that decryption will work in permanently installed TWRP. This zip should be used if you're using a custom kernel that doesn't require patching for touch.
UPDATE_BeyondStock™_U12+_Exodus_Remove_Forced_Encryption_CPTB_signed.zip: This zip disables forced encryption on the device so that it doesn't automatically get encrypted after Formatting Data in TWRP.
Custom Recovery
Official TWRP for U12+: This is the recommended TWRP version to use with the ROM, with full Android 11/12 decryption support.
Kernels
UPDATE-BeyondStock™-Kernel-Pie-v0.02-U12+_Exodus-signed.zip: This zip installs the BeyondStock™ kernel which has patched touch for permanently installed TWRP older than 3.4.0, and patches the boot.img header so that decryption will work. It also supports the stock exFAT implementation.
UPDATE-BeyondStock™-Kernel-Pie-v0.02-U12+_Exodus_TWRP_3_4_0_CPTB.zip: This zip installs the BeyondStock™ kernel which has patched touch for permanently installed TWRP 3.4.0 (and higher), and patches the boot.img header so that decryption will work. It also supports the stock exFAT implementation.
[MANUAL] Fix CTS Profile Mismatch
Initial situation: most GSIs are rooted to a certain extent. This also applies to the AOSP GSI, which is the basis of our ViperExerience ROM.
Precondition: To correct the CTS mismatch, it is necessary that Magisk is installed.
If the precondition is fulfilled, proceed as follows:
Install the Magisk modules "Busybox" from Osmosis, and "MagiskHide Propst Config" from Didgeridoohan
After a device restart, open a Terminal App on your HTC U12+ and go through the following steps
Request root privileges by typing
Code:
su
Start the Props module by typing
Code:
props
Type
Code:
1
to set a new fingerprint for the device
Follow the instructions in order by selecting
Code:
f
and
Code:
7
(for HTC).
finally type
Code:
4
(for U12+ Pie).
How to permanently flash TWRP via the TWRP.img file inside TWRP
1. Make sure you have a working fastboot and adb environment! Your device´s bootloader must be unlocked!
2. Download the twrp.img file from here: https://github.com/CaptainThrowback/android_device_htc_ime/releases
3. Boot to TWRP. Navigate to Advanced -> Install Recovery Ramdisk -> Choose the twrp.img downloaded earlier. Wait for the flash to be completed successfully and do either
4. Download BeyondStock™-Kernel This zip installs the BeyondStock™ kernel which has patched touch for permanently installed TWRP, and patches the boot.img header so that decryption will work. It also supports the stock exFAT implementation.
5a. If you want to be rooted flash the magisk.zip
5b. If you don't want to be rooted navigate to Advanced -> Fix Recovery Bootloop to be able to boot into system
Thanks to @JEANRIVERA
reserved
reserved3
reserved4
reserved5
reserved6
Support
Hi users, I was a noob once too, believe it or not I had questions & stupid questions too but I was never afraid to ask, in my way to be part of this amazing team I have known all kind of Devs, with different levels of friendliness , but being honest in some way or another I have learned from all of them a little something, Now I want to give back to the community as much as I can, I am no Dev, but I do know a trick or two, if I don't know the answer to your questions, I will try my best to get an answer for you from the Team.
The instructions in the OP have been updated for better understanding and corrected some points, if anyone has tried unsuccessfully to flash this ROM please follow the updated instructions, if anyone have trouble or not booting device please feel free to ask, I will try to guide anyone as much as I can and as friendly as possible. I see there is 73 downloads on AFH of the ROM but only few users reported their experience here, maybe if you are afraid to ask, don't be, if you navigate through the thread you will see only friendly responses, and I will try my best to keep it that way, don't be afraid to tag me for support
And I'll take this one, just for the kicks.
I am running android 8 with viper 2.0 and i tried to update to this but ADB says that my file system is read-only. What is the recommended course of action?
Code:
adb: error: failed to copy 'update.zip' to '/update.zip': couldn't create file: Read-only file system
I read elsewhere that 'adb root' would be needed but i figured it would be better to ask here instead of following some random post about a somewhat similar situation.
First off: don't install this ROM on Android 8 firmware. It's an Android 10 GSI and all development an testing has been done on the latest EMEA firmware.
So the way to go from ViperU12+ would be to go back to full stock unsung a RUU and upgrade to Android Pie. This is to make sure you start from the correct base and environment. Then boot the device and copy the vbmeta zip onto /sdcard. Then reboot to bootloader and boot to TWRP, and follow the instructions from post #1 to the point.
Use the latest TWRP from @Captain_Throwback, found here: https://github.com/CaptainThrowback/android_device_htc_ime/releases/tag/3.3.1-2
Sent from my Pixel 4 XL using XDA Labs
it should be: 9 Reboot to Download from TWRP UI not
9 Reboot to bootloader from TWRP UI
on Production Units in Bootloader you get an error:
FAILED (remote: Erase is not allowed on PRODUCTION device)
This ROM is been running quite fantastic for me, I am so excited to help test and get this released for everybody to use! Can't believe we have Android 10 on this u12 plus Beast, it's so amazing! LOL thank you so much @mikalovtch, @JEANRIVERA, @Captain_Throwback, &
Sent from my HTC U12+ using Tapatalk
Oh man, you`ve done brilliant work:highfive::good:
it is almost perfect, butter smooth and fully functional except few bugs.
some issues are:
1. time and date automatically reset to 2020.03.07 4:47 after reboot, which can be quite annoying.
2. edgesense squeeze gesture feedback is weird. it`s not like the feedback of power btn but vibrating.
3. edgesense setting does not show in the settings.
some Pro tips:
1. flash system.img via twrp or via usb under DOWNLOAD mode. you can not flash it under BOOTLOADER mode.
2. you can access edgesense settings by this method:
goto Setting.Apps, show all system Apps and find out edgesense service app. In the detail screen(where you can clear the cache and force stop, idk the exact term), tap Advanced, Additional settings in the app.
3.kirisakura kernel tested, all good.
btw i use China version u12+, hope this will help you.
Thanks you bro!
issue has been fixed
JEANRIVERA said:
without the vbmeta.zip the ROM will not boot at all, the instructions fail to specify you must be on slot A to flash the vbmeta.zip and ROM, instructions will be updated soon, if you are on slot B another vbmeta zip should be used.
Click to expand...
Click to collapse
thank you! but i still boot without flashing vbmeta.
neoncloud4399 said:
thank you! but i still boot without flashing vbmeta.
Click to expand...
Click to collapse
is your device S-OFF? that would be the only possible reason it boots
JEANRIVERA said:
is your device S-OFF? that would be the only possible reason it boots
Click to expand...
Click to collapse
no, it still s-on.
i followed this procedure:
clear system, flash system, clear userdata under twrp
flash vbmeta.zip under twrp By sideload
reboot, failed to boot, show warning messages.
run fastboot oem rebootRUU to ruu flash mode and downgrade to 1.21
fastboot erase persist
boot to 1.21 China then upgrade to PIE.
boot to DOWNLOAD, erase system, userdata, flash system both system_a and system_b and it boots.

[OFFICIAL&TESTS]TWRP for the Motorola Moto X4 (Payton)

{
"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?

Development [KERNEL] [OFFICIAL] [MIUI/AOSP] [UNIFIED] LegionX V2.0 - By Venom_Stark

{
"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 & INFO »​
Code:
# include <std_disclaimer.h>
/*
* Your warranty is... Still valid??.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this KERNEL
* 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.
*/
Note: I'm just a library man all works saved to their owners this kernels made by love check credits. All copyright saved here with developer premison ​
Click to expand...
Click to collapse
​​Name of Kernel: LegionX​
​Version of kernel: 2.0 NEW​
​Lates stable Update: 2021/sep/03​
​Supported Roms: MIUI & AOSP​
​Status: Stable​
UNIFIED = MOJITO / SUNNY​
​
« Changelogs »
[ Latest Release Changelog ]
Check Post #2 (click number) for changelogs
« NOTES »​• In MIUI / MIUI based ROMs, kernel version will show "Unavailable" because MIUI doesn't support long names (because I used proton clang and lld) but kernel working perfectly you can see name in FKM tough.
​• It's AIMING on Performance, stability,..
​• If you can't flash with TWRP , use FK manager to flash it "root required".
• KCAL works fine .Everytime you changed value in KCAL just screen off (Don't power off) and open screen .
New value will apply.
• If your device not booting to system just bootloop or fastboot only. Don't panic. re-flash your rom file without wiping data. And please report here with the name of rom and any details.
• If you update TWRP recovery, reflash the kernel again too.
• You don't need to Wipe data ! Only cashe and Dalvik.
• Report for any bugs/issues with logs if available.
« DOWNLOADS »​Latest Stable Build (LegionX V2.0):
• Click here to download LegionX V2.0 (MIUI/AOSP)
​Previous Stable build:
• Click here to download V 1.0-LTO (AOSP Only) Build
« INSTALLATION »​1- Download Kernel & save it on internal storage.
2- Boot to recovery (TWRP).
3- Flash the kernel zip file.
4- Wipe Cashe & Dalvik. “Don't Wipe Data”
5- Reboot to system.
NOTE: For pixel experience rom, use this Guide:
Spoiler: GUIDE FOR Pixel experience Rom
IT'S can safely installed on Pixel experience. Just follow this:
1- Boot TWRP recovery with this command:
Code:
fastboot boot twrp.img
2- Don't Install ramdisk or anything just go to LegionX Kernel on your storage and flash it.
3- Wipe Cashe & Dalvik.
4- Power Off then power on your device.
Done.
« CREDITS »​• Kernel by: @venom_stark , Thanks
• Thanks to @ZIDAN44 , @CloudedQuartz ,@cyberknight777 & @Shararti1 .
• Thanks @AnomYT for Banner
• XDA-OP: @Abdullah.Csit
• #All testers.
• GitHub Source Link: https://github.com/venom-stark/mojito...
​
SHOW YOUR SUPPORT BY HITTING LIKE ​
Click to expand...
Click to collapse
#Kernel Changelogs 2021/9/03:
Code:
LegionX v2.0:
-schedtune_assist: Cleanup and update
-sched/tune: Only force UX tasks to big cores
-f2fs: Enlarge min_fsync_blocks to 20
-diag: Add timer to make sure wakelock no stuck
-fs: Reduce cache pressure
lib/string: optimized memcpy,memmove, memset
-arm64: Import latest memcpy()/memmove() implementation
-ARM64/dts: qcom: Disable CoreSight DT entries for sdmmagpie
-scsi: ufs: Scrap Qualcomm's PM QoS implementation
-scsi: ufs: Scrap Qualcomm's PM QoS implementation
-msm: adreno: Relax CPU latency requirements to save power
-sched/fair: fix misfit with PELT
-qos: Don't allow userspace to impose restrictions on CPU idle
-mmc: Disable SPI CRC
-iommu: msm: Rewrite to improve clarity and performance
-PM: sleep: Don't allow s2idle to be used
-rcu: Speed up calling of RCU tasks callbacks
-Enable JUMP_LABEL and added some jump lebel patches
Spoiler: Old changelog
Code:
➡️ 2021/8/4 |
• MIUI not supported in this update ( On V2.0 will get update)
• Used LTO binary optimization
• Complied using proton clang with lld linker.
• Performance improvement
• Battery backup improvement
#Thread Changelog:
// 2021.august.4 //
- Introduce the new LOGO
- Kernel Updated ! 2021/8/4
- Added new note about MIUI in new update To «NOTES» section (IMPORTANT)
//
Can i flash this for MIUI EU rom?
lakshmish said:
Can i flash this for MIUI EU rom?
Click to expand...
Click to collapse
Yes
Abdullah.Csit said:
#Thread Changelog:
// 2021.july.22 //
- Added new note To «NOTES» section about KCAL (IMPORTANT)
//
Click to expand...
Click to collapse
Okay, lets try flashing this one
IMHO, this kernel is a little bit better than Neternal in battery utilization. Anyway tanx to the devs.
Pachunko said:
Okay, lets try flashing this one
Click to expand...
Click to collapse
Glad to know if it success
Anish Louis said:
IMHO, this kernel is a little bit better than Neternal in battery utilization. Anyway tanx to the devs.
Click to expand...
Click to collapse
Which rom?
Abdullah.Csit said:
Glad to know if it success
Click to expand...
Click to collapse
Unfortunately it wasn't, fastboot too. I quit kernels for good I guess.
EDIT: Maybe I need to flash latest stock firmware? Just an idea.
You must have a broken system. Flash Miui from MiFlash with cleanup and then reload the desired custom ROM. This will align all partitions.
Kernel tested on PE+, camera error persists.
Wouldn't it be obvious if a system is broken? crDroid is working flawlessly atm.
StaryMuz said:
You must have a broken system. Flash Miui from MiFlash with cleanup and then reload the desired custom ROM. This will align all partitions.
Kernel tested on PE+, camera error persists.
Click to expand...
Click to collapse
Reported to developer
Developer answer : “Ok I will flash PE+ now and test camera.”
Tested : Camera working perfectly on PE+.
Pachunko said:
Wouldn't it be obvious if a system is broken? crDroid is working flawlessly atm.
Click to expand...
Click to collapse
At less test flashing Latest firmware it won't be hard and it's good for your device anyway.
Here's what I tried now:
1. Flashed stock firmware (clean all)
2. Booted up to MIUI - Copied crDroid rom, kernel, gapps to internal storage
3. Rebooted to fastboot - flashed twrp.img via fastboot command
4. Rebooted to recovery, installed everything: ROM, Gapps, kernel
5. Wiped data/cache
6. Reboot - stuck at crDroid logo (at least it's no longer fastboot loop)
Update: Rebooted to recovery, data cannot mount - encrypted. "default_password" doesn't work.
Pachunko said:
Here's what I tried now:
1. Flashed stock firmware (clean all)
2. Booted up to MIUI - Copied crDroid rom, kernel, gapps to internal storage
3. Rebooted to fastboot - flashed twrp.img via fastboot command
4. Rebooted to recovery, installed everything: ROM, Gapps, kernel
5. Wiped data/cache
6. Reboot - stuck at crDroid logo (at least it's no longer fastboot loop)
Update: Rebooted to recovery, data cannot mount - encrypted. "default_password" doesn't work.
Click to expand...
Click to collapse
Just use fastboot recovery OTA tool flash CRdroid with it. Then wait till you boot in TWRP
Wipe data
Flash kernel
Reboot system
[Tool] Flash Custom ROMs through Fastboot [mojito / sunny]
Are you struggling to install custom roms on this device? Lots of recovery errors? Can't boot to any rom? Don't worry. Fastboot is a good way to avoid such nonsense... Install any custom rom & miui recovery rom through fastboot Steps: 1...
forum.xda-developers.com
Pachunko said:
Here's what I tried now:
1. Flashed stock firmware (clean all)
2. Booted up to MIUI - Copied crDroid rom, kernel, gapps to internal storage
3. Rebooted to fastboot - flashed twrp.img via fastboot command
4. Rebooted to recovery, installed everything: ROM, Gapps, kernel
5. Wiped data/cache
6. Reboot - stuck at crDroid logo (at least it's no longer fastboot loop)
Update: Rebooted to recovery, data cannot mount - encrypted. "default_password" doesn't work.
Click to expand...
Click to collapse
Pachunko said:
Here's what I tried now:
1. Flashed stock firmware (clean all)
2. Booted up to MIUI - Copied crDroid rom, kernel, gapps to internal storage
3. Rebooted to fastboot - flashed twrp.img via fastboot command
4. Rebooted to recovery, installed everything: ROM, Gapps, kernel
5. Wiped data/cache
6. Reboot - stuck at crDroid logo (at least it's no longer fastboot loop)
Update: Rebooted to recovery, data cannot mount - encrypted. "default_password" doesn't work.
Click to expand...
Click to collapse
It's a dynamic virtual A/B phone traditional way of flashing won't work.
First flash los recovery
Fastboot flash boot LosRecovery.img
Then boot to los recovery and format data.
Then click apply updated and flash rom thorough sideload..
After flashing rom reboot and rom will boot.
Then install twrp
Type command - fastboot boot twrp.img
After booting to twrp then go to advance click "flash current twrp". Then reboot system.
Then open twrp like normally by pressing vol+ and power button (you know)
Then flash kernel.
Edit: Don't need to flash TWRP in rom in which it pre-installed.
venom_stark said:
It's a dynamic virtual A/B phone traditional way of fishing won't work.
First flash los recovery
Fastboot flash boot LosRecovery.img
Then boot to los recovery and format data.
Then click apply updated and flash rom thorough sideload..
After flashing rom reboot and rom will boot.
Then install twrp
Type command - fastboot boot twrp.img
After booting to twrp then go to advance click "flash current twrp". Then reboot system.
Then open twrp like normally by pressing vol+ and power button (you know)
Then flash kernel.
Click to expand...
Click to collapse
I think he doesn't need to flash twrp again since CRdroid included TWRP.
Best way is using fastboot tool to flash his recovery rom
My regards
Pachunko said:
Here's what I tried now:
1. Flashed stock firmware (clean all)
2. Booted up to MIUI - Copied crDroid rom, kernel, gapps to internal storage
3. Rebooted to fastboot - flashed twrp.img via fastboot command
4. Rebooted to recovery, installed everything: ROM, Gapps, kernel
5. Wiped data/cache
6. Reboot - stuck at crDroid logo (at least it's no longer fastboot loop)
Update: Rebooted to recovery, data cannot mount - encrypted. "default_password" doesn't work.
Click to expand...
Click to collapse
the critical error is, you don't start the ROM after installing the rom.
flash the rom, start the rom, create a password/pattern so you get /data encryption key (you can disable it right after, but let system set it up once)
then, start flashing the rest. (installing gapps however might be necessary before booting it up for the fist time, idk)
if system can't decrypt /data, you will end up in a bootloop and/or fastboot loop.
I
Abdullah.Csit said:
I think he doesn't need to flash twrp again since CRdroid included TWRP.
Best way is using fastboot tool to flash his recovery rom
My regards
Click to expand...
Click to collapse
Yeah I forgot. But flashing through LOS or PE recovery will give 100% success boot.
I can't flash stock now at all... I get this error in mi flash:
error: Writing 'metadata'
FAILED (remote: 'Flashing of metadata is not allowed in snapshotted state')
so phone is bricked, not sure what to do. I can only get to fastboot currently

[UPDATED][RECOVERY][UNOFFICIAL]TWRP 3.6.2 for 2020 Galaxy Tab A7 10.4[SM-T500]

{
"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.5.2_11
For device: gta4lwifi
Device Tree: https://github.com/juic3b0x/twrp_android_device_samsung_gta4lwifi
Maintainer/Authors build: ragarcia87
Installation Instructions
If TWRP Already Installed
Download recovery.img from below
Copy recovery.img to device
Install > Install Image > recovery.img to Recovery
Reboot > Recovery
Enjoy
From PC
Download Odin Flashable Tar from bellow
Put tablet into Odin Download Mode
Flash Blank vbmeta via Userdata
Flash Odin Flashable Tar via AP
Enjoy
Working
ADB
MTP
Everything, except decryption of internal data (havent tested)
Bugs
(My tablet is already decrypted so haven't tested this, please advise)
OS-encrypted storage (Internal Data) not able to be decrypted in TWRP.
Downloads
recovery.img
https://mega.nz/file/bkcimDCK#tkv6ATvxx_gEUJJ4OD2WQ1WsRPTINRZCc2hTFPg62aY
Blank vbmeta
https://mega.nz/file/74dAUBSQ#w_XN49p8TRppiOVEvI_eGXkzf6jgZWXarN4Qi6BFr-4
Odin Flashable Tar
https://mega.nz/file/C0NgmD6S#lWD70RUXsXs_sv-0E5BOHPoitQc8keyorarW0xtXV-4
Thanx a lot bro. was looking for it. working fine. is there any custom or modified samsung rom without bloat sothat we can use this recovery for that.
Glad it's working well for you. And to be honest, I've tried a few GSI roms and they work well, like crDroid GSI and CAOS GSI... I've been trying to cook up my own port of a few ROMs also to no avail yet but soon...
ragarcia87 said:
Glad it's working well for you. And to be honest, I've tried a few GSI roms and they work well, like crDroid GSI and CAOS GSI... I've been trying to cook up my own port of a few ROMs also to no avail yet but soon...
Click to expand...
Click to collapse
How do I install the GSI ROMs because I only get Boot Recovery dtbo vbmeta_samsung VBMeta and Super (system vendor odm product)
EdwardTCM said:
How do I install the GSI ROMs because I only get Boot Recovery dtbo vbmeta_samsung VBMeta and Super (system vendor odm product)
Click to expand...
Click to collapse
You have to use a patch called DynaPatch v1.5. It patches TWRP to be able to install individual images to the super dynamic partition... I don't know if I can post a link but if you Google DynaPatch v1.5 you'll be able to find it, just flash via TWRP and then reboot to Recovery and it will show system, vendor, product etc in the install
ragarcia87 said:
You have to use a patch called DynaPatch v1.5. It patches TWRP to be able to install individual images to the super dynamic partition...
Click to expand...
Click to collapse
Oh alright thanks
ragarcia87 said:
You have to use a patch called DynaPatch v1.5. It patches TWRP to be able to install individual images to the super dynamic partition... I don't know if I can post a link but if you Google DynaPatch v1.5 you'll be able to find it, just flash via TWRP and then reboot to Recovery and it will show system, vendor, product etc in the install
Click to expand...
Click to collapse
I got the file but nothing happened
Edit: Never mind I fixed it
Enter TWRP recovery
Select Install – select DynaPatch-v1.5.zip, Swipe to confirm Flash
Select Reboot – Recovery or Turn Power off
One time only to flash this patch except you reflash the TWRP recovery
The images attached are to show that it works.. I show a before the patch is installed and then after its installed... make sure you follow the directions above.
Aight, after i unlocked the bootloader, everytime i try to flash the vbmeta or even the twrp, it fails. any idea why?
"Only official released binaries are allowed to be flashed(vbmeta)"
Liloabouu said:
Aight, after i unlocked the bootloader, everytime i try to flash the vbmeta or even the twrp, it fails. any idea why?
"Only official released binaries are allowed to be flashed(vbmeta)"
Click to expand...
Click to collapse
After unlocking, did you re-enable Dev mode and check OEM?
Could you please refresh your device tree on GitHub with the changes you made for Android 11?
Magendanz said:
Could you please refresh your device tree on GitHub with the changes you made for Android 11?
Click to expand...
Click to collapse
I can certainly try, lol... Been super busy lately, 7days a week, two jobs no time off till after the new year lol... I'll keep ya posted
I'm having a problem with stock recovery overwriting TWRP. I have the latest stock, BUJ1, installed. I flash vbmeta and recovery with Odin and boot into TWRP. Format data and reboot recovery. Everything works fine. Reboot to system and go through the setup, make sure developer mode still enabled. Again, everything appears to work. Download the DynaPatch and copy it to the T500 SD card. Turn off the tablet and attempt to boot TWRP. It's gone. Back to stock recovery. What am I doing wrong????
read post below... sorry ... tried to edit and it double posted...
lewmur said:
I'm having a problem with stock recovery overwriting TWRP. I have the latest stock, BUJ1, installed. I flash vbmeta and recovery with Odin and boot into TWRP. Format data and reboot recovery. Everything works fine. Reboot to system and go through the setup, make sure developer mode still enabled. Again, everything appears to work. Download the DynaPatch and copy it to the T500 SD card. Turn off the tablet and attempt to boot TWRP. It's gone. Back to stock recovery. What am I doing wrong????
Click to expand...
Click to collapse
Thats my bad, youll want to use the multidisabler to fix that.. I have added it to the twrp.. once twrp is installed go to Advanced > Terminal and then type multidisabler then press enter. This will disable the stock recovery restoration.
What if I don't have TWRP installed yet but the tablet is rooted with Magisk? Is it okay to flash TWRP from within a running system?
ragarcia87 said:
Thats my bad, youll want to use the multidisabler to fix that.. I have added it to the twrp.. once twrp is installed go to Advanced > Terminal and then type multidisabler then press enter. This will disable the stock recovery restoration.
Click to expand...
Click to collapse
Thanks. That worked but I flashed DynaPatch and then lineage-19.0-20211216-UNOFFICIAL-treble_a64_bvS-vndklite.img in super and it bootloops. Any ideas? Of course this was after format of data and factory reset wipe.
lewmur said:
Thanks. That worked but I flashed DynaPatch and then lineage-19.0-20211216-UNOFFICIAL-treble_a64_bvS-vndklite.img in super and it bootloops. Any ideas?
Click to expand...
Click to collapse
You'll have to reflash stock super or extract the stock super img and flash vendor, product, odm, then the lineage to system
Also @lewmur will need the lineage-19.0-20211216-UNOFFICIAL-treble_arm64_bvS-vndklite.img variant. Not a64
paziusss said:
Also @lewmur will need the lineage-19.0-20211216-UNOFFICIAL-treble_arm64_bvS-vndklite.img variant. Not a64
Click to expand...
Click to collapse
paziusss said:
Also @lewmur will need the lineage-19.0-20211216-UNOFFICIAL-treble_arm64_bvS-vndklite.img variant. Not a64
Click to expand...
Click to collapse
Thanks. Got LOS 19 to boot. Do you know what gapps to use with it?

Categories

Resources