[RECOVERY][3.4.0-10][Unified]Official/Unofficial TWRP for OnePlus 7/7 pro/5G (Stable) - OnePlus 7 & 7 Pro Cross Device Development

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface 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.
Code:
#include <std_disclaimer.h>
/*
*
* We are 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.
*
*/
Features:
- Seems is working all except vibration
- Android Q Support
- Android 11 Decryption
Install guide (Reccomended):
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line (if you want to have it permanently you should flash the installer)
5. If you will flash the installer and you are stock you need also to flash magisk or your phone will not boot again
6. Enjoy it
Other Install guide (More articulated but fully functional):
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line
5. Copy the recoveryimgfilename.img in the phone memory
6. Go in advanced menu
7. Click on "Install Recovery Ramdisk"
{
"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"
}
8. Choose the recoveryimgfilename.img
9. Swipe to install
OLD Install guide (Much more articulated but perfectly functional):
1. Follow this guide to root your device: https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-root-oneplus-7-pro-patched-boot-t3931205
2. Flash the TWRP installer like a magisk module
3. Flashing the TWRP installer you will lose the root, so you will need to flash magisk again from magisk manager before reboot the device or you can reboot the device and flash magisk in twrp
HOW TO UPDATE a ROM and KEEP TWRP and ROOT:
Before all Disable all magisk modules for boths methods
- Put rom.zip, twrp installer.zip and magisk.zip on your internal storage;
- Flash Rom;
- Flash TWRP Installer;
- Flash magisk;
- Reboot.
If you want you can also update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- Menu/modules/+ button/select the twrp installer.zip and flash it;
- Always in Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
BugReport:
Please all, when you got a problem, bootloop, error in twrp, unable to do something, please be sure you have followed the guides properly and when you write here you have problem just follow this guidelines for the bugreport:
- Write what rom and version you have actually;
- Write which device you have, gm1910, gm1913, gm1917, gm1915, gm1920, gm1911.
- Write which twrp you are using (Unofficial, Officia and the version);
- If you got an error in the twrp flashing a zip, after got the error make a log using this command : "cat /tmp/recovery.log" or if you are using adb with "adb shell cat /tmp/recovery.log". Copy the output in a text file and send me it.
- Write what are you trying to do;
- Write how you flash the twrp and magisk, just write what you do.
If you don't give me this infos i can't help you.
If something doesn't work, don't just complain, but try to get the problem resolved by giving all the information you have.
Tips:
If you alread have a twrp flashed you can only flash the new installer zip or the new installation method to update your TWRP (remember to flash again magisk or your system will not boot).
If you have some problems with backup, like 255 error or something similar please check this guide: https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
For the Bacups use always "system_image" and "vendor_image" instead of "system" and "vendor".
Download:
India Fake Partition Deleter by mauronofrio
Official Builds
TWRP 3.4.0-10 Unified Unofficial Q by mauronofrio
TWRP 3.4.0-10 Unified Unofficial Installer by mauronofrio
TWRP 3.4.0-0 Unified Unofficial Q by mauronofrio
TWRP 3.4.0-0 Unified Unofficial Installer by mauronofrio
Spoiler: Show old builds
TWRP 3.3.1-79 Unified Unofficial Q by mauronofrio
TWRP 3.3.1-79 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-79 Unified Unofficial Installer by mauronofrio
TWRP 3.3.1-76 Unified Unofficial Q by mauronofrio
TWRP 3.3.1-76 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-76 Unified Unofficial Installer by mauronofrio
TWRP 3.3.1-75 Unified Unofficial Q by mauronofrio
TWRP 3.3.1-75 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-75 Unified Unofficial Installer by mauronofrio
TWRP 3.3.1-74 Unified Unofficial Q by mauronofrio
TWRP 3.3.1-74 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-74 Unified Unofficial Installer by mauronofrio
TWRP 3.3.1-70 Unified Unofficial Q by mauronofrio
TWRP 3.3.1-70 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-70 Unified Unofficial Installer by mauronofrio
TWRP 3.3.1-65 Unified Unofficial by mauronofrio
TWRP 3.3.1-65 Unified Unofficial Installer by mauronofrio[
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/mauronofrio/android_device_oneplus_guacamoleb_TWRP
https://github.com/mauronofrio/android_device_oneplus_guacamole_unified_TWRP
Android Pie IMG: https://gitlab.com/HolyAngel/op7
Android Q IMG: Precompiled stock one
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
Thanks to @HolyAngel for the kernel
Created 2019-05-23

Have where test this? I get my OP7 today and need root.

mauronofrio said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface 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.
Features:
-Seems is working
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line
5. Copy the recoveryimgfilename.img in the phone memory
6. Go in advanced menu
7. Click on "Install Recovery Ramdisk"
8. Choose the recoveryimgfilename.img
9. Swipe to install
Other Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line (if you want to have it permanently you should flash the installer)
5. If you will flash the installer and you are stock you need also to flash magisk or your phone will not boot again
6. Enjoy it
Install guide:
Actually seems "fastboot boot twrp.img" is not working so we need to use another guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Now you should check which slot are you using with this command "fastboot getvar current-slot"
5. Now you should change the slot in use with this command "fastboot --set-active=*" you should replace with the slot is not in use, for example if you are using slot a the command will be "fastboot --set-active=b"
6. Now you should flash the twrp in the boot partion using this command "fastboot flash boot twrp.img"
7. Now reboot the device with in recovery mode scrolling the menu with the volume button and selecting "Recovery Mode" with the power button
8. First thing go in reboot menu and restore the old active slot
9. Now you can flash the installer (Actually you can do it using sideload, start sideload server from twrp advanced menu and from pc use this command "adb sideload twrpinstaller.zip")
If you are already rooted, you can skip all and directly flash the installer like a magisk module. Always remember that after you flashed the installer you will be unrooted.
Tips:
If you alread have a twrp flashed you can only flash the new installer zip or the new installation method to update your TWRP (remember to flash again magisk or your system will not boot).
If you have some problems with backup, like 255 error or something similar please check this guide: https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
For the Bacups use always "system_image" and "vendor_image" instead of "system" and "vendor".
Download:
TWRP 3.3.1-2 Unofficial by mauronofrio
TWRP 3.3.1-2 Unofficial Installer by mauronofrio
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/mauronofrio/android_device_oneplus_guacamoleb_TWRP
https://gitlab.com/HolyAngel/op7
Donations:
Credits:
Thanks to @HolyAngel for the kernel
Created 2019-05-23
Click to expand...
Click to collapse
great! very useful! :good:

Hot-Proton said:
Have where test this? I get my OP7 today and need root.
Click to expand...
Click to collapse
I made the twrp for.oneplus 7 pro, they have a common kernel so the twrp is really similar, it should work without problems

recovery works but anyone got the stock recovery ?

Dragonlord07 said:
recovery works but anyone got the stock recovery ?
Click to expand...
Click to collapse
Stock recovery is in stock boot.img, flash the stock boot.img to restore the stock recovery

mauronofrio said:
Stock recovery is in stock boot.img, flash the stock boot.img to restore the stock recovery
Click to expand...
Click to collapse
i probably sound stupid but where is the stock boot.img???

Dragonlord07 said:
i probably sound stupid but where is the stock boot.img???
Click to expand...
Click to collapse
`boot.img` can be obtained from the stock ROM I guess. Extract the zip file to find it. Currently it's unavailable I think. You can search for it or check OnePlus website.

There is no stock rom for download now. I get my 7 non-pro now and test twrp. Why are there three install guides?

I can confirm that the recovery is working. I managed to flash it and use it to install Magisk. Thank you!

I found I could flash this version of TWRP and then flash the Magisk zip no problem. Magisk works fine. However, the Magisk uninstaller fails with "Unable to mount partitions" when trying to flash it in TWRP.

Ok, before push this twrp as official one, i want you test the stock rom flashing. For magisk uninstaller it's better if it gave you an error. If you want to unroot you should use the stock boot.img

I can't find the stock boot.img for standard Oneplus 7 but need to uninstall magisk via TWRP. I'm currently stuck in a bootloop to TWRP recovery after an OTA update. Any advice?

readysound said:
I can't find the stock boot.img for standard Oneplus 7 but need to uninstall magisk via TWRP. I'm currently stuck in a bootloop to TWRP recovery after an OTA update. Any advice?
Click to expand...
Click to collapse
Flash again magisk and the bootloop will stop

Thanks - that sorted it after "fastboot flash boot twrp-3.3.1-1.img" on the patched slot. If you need me to test anything give me a shout. Thanks for all of your work btw!
---------- Post added at 08:13 PM ---------- Previous post was at 08:11 PM ----------
With my 6T, selecting Uninstall / Restore Images in Magisk would work for patching OTA updates to other slot. Now I get "Stock backup does not exist" both before the OTA and after.

readysound said:
Thanks - that sorted it after "fastboot flash boot twrp-3.3.1-1.img" on the patched slot. If you need me to test anything give me a shout. Thanks for all of your work btw!
Click to expand...
Click to collapse
You should not use "fastboot flash boot " command but "fastboot boot " command. The first one will flash the twrp in the boot partition, the second one will only.boot the twrp for one time.

Thanks a lot!

mauronofrio said:
You should not use "fastboot flash boot " command but "fastboot boot " command. The first one will flash the twrp in the boot partition, the second one will only.boot the twrp for one time.
Click to expand...
Click to collapse
Just an update, when performing a "fastboot boot twrp-3.3.1-1.img" command in the bootloader I get the following error (and TWRP doesn't boot) :
Sending 'boot.img' (56016 KB) OKAY [ 1.787s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
I'm currently trying to get slot A to boot (slot B received the OTA update and I want to revert). Switching to slot A I am having the same recovery boot loop. Flashing magisk again via ADB doesn't resolve this.

readysound said:
Just an update, when performing a "fastboot boot twrp-3.3.1-1.img" command in the bootloader I get the following error (and TWRP doesn't boot) :
Sending 'boot.img' (56016 KB) OKAY [ 1.787s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
I'm currently trying to get slot A to boot (slot B received the OTA update and I want to revert). Switching to slot A I am having the same recovery boot loop. Flashing magisk again via ADB doesn't resolve this.
Click to expand...
Click to collapse
If fastboot.boot.command doesn't work you should use the old guide, it happened also on the op7 pro, recently they included again the fastboot boot command

Can I boot thi recovery temporarily just to install magisk and not flash the installer so that I can keep the stock recovery?

Related

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.

[ROM] Dirty Unicorns 14.7 {Marlin} (09/13/20)

{
"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"
}
About Us:
Dirty Unicorns is an AOSP based project built to enhance the stock Android experience.
Our focus has been and is always to contribute back to the community. That is ultimately why we do what we do.
We DO NOT accept, nor ask, for donations. We do not believe in that. Everything that is necessary to keep this project going comes out of our own pocket. This includes, but is not limited to; Devices, Gerrit, our websites and services, etc.. The only thing that we ask in return is that you have patience, search the thread for answers prior to posting, read diligently, and try to enjoy the process with us!
Kernel Source:
https://github.com/DirtyUnicorns/android_kernel_google_marlin
Flashing Instructions:
If you have a device that uses TWRP
Verify that you're using the latest version of TWRP
Perform a FULL WIPE: (A full wipe is when you wipe system/data/cache/dalvik)
Flash the latest version of this ROM
Flash vendor image (once only to both slots if coming from another ROM) via bootloader:
Code:
fastboot flash --slot all vendor vendor.img
Reboot and ENJOY!
If you have a device that does not use TWRP
Download boot.img and ROM zip from DU server
Reboot into bootloader and flash the boot.img
Code:
fastboot flash --slot all boot boot.img
Reboot to recovery
Go to recovery select factory reset
Select Apply update from ADB to flash the zip
Code:
adb sideload nameofbuild.zip
Flash vendor image (once only) via bootloader:
Code:
fastboot flash --slot all vendor vendor.img
Reboot and ENJOY!
If you're just updating DU on a device without TWRP
Download ROM zip from DU server
Reboot into recovery and select Apply update from ADB to flash the zip
Reboot system now and ENJOY!
**All bugs and feature requests must be reported to JIRA**
**If you use Xposed, please don't bother reporting any bugs**
**If you use another kernel, please don't bother reporting any bugs**
**If you fail to follow these instructions, please don't bother reporting any bugs**
Download Links:
Build(s) - Marlin
Other Links:
ROM Source - https://github.com/DirtyUnicorns
Gerrit - http://gerrit.dirtyunicorns.com
Crowdin (translations) - https://crowdin.net/project/dirtyunicorns
JIRA (Bug Reporting / Feature Requests) - http://jira.dirtyunicorns.com/
Telegram - https://t.me/dirtyunicorns / https://t.me/DirtyUnicornsSupport
XDA:DevDB Information
Dirty Unicorns, ROM for the Google Pixel XL
Contributors
NYCHitman1
Source Code: https://github.com/DirtyUnicorns
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 14.7
Stable Release Date: 2020-09-13
Created 2020-08-08
Last Updated 2020-09-13
one of the BEST ROMS for Marlin, loving it
imna357 said:
one of the BEST ROMS for Marlin, loving it
Click to expand...
Click to collapse
Is it available for Sailfish or can this build can be flash on Sailfish
rom
thanks
kiran8631 said:
Is it available for Sailfish or can this build can be flash on Sailfish
Click to expand...
Click to collapse
Sorry, Marlin only.
Cool beans.....
Tried a few rom from other developers but the battery drains fast. This one have no problem. Thanks for good rom.
Was anyone able to install Magisk?
Whenever I try to install Magisk I get stuck in a Bootloop at the Google Logo.
Doesn't matter if I do KEEPFORCEENCRYPT=true & KEEPVERITY=true in the .magisk for or false.
Wanted to test disable DM-Verity but TWRP is unable to mount /system_root (Neither TWRP 3.4.0.0 or 3.3.1 work)
My Phone has an encrypted Storage if that helps narrowing down the issue
Darthsternie said:
Was anyone able to install Magisk?
Whenever I try to install Magisk I get stuck in a Bootloop at the Google Logo.
Doesn't matter if I do KEEPFORCEENCRYPT=true & KEEPVERITY=true in the .magisk for or false.
Wanted to test disable DM-Verity but TWRP is unable to mount /system_root (Neither TWRP 3.4.0.0 or 3.3.1 work)
My Phone has an encrypted Storage if that helps narrowing down the issue
Click to expand...
Click to collapse
Try using the orangefox recovery when flashing the magisk, never had this issue
Ok this looks sick. Gunna flash tonight.
Darthsternie said:
Was anyone able to install Magisk?
Whenever I try to install Magisk I get stuck in a Bootloop at the Google Logo.
Doesn't matter if I do KEEPFORCEENCRYPT=true & KEEPVERITY=true in the .magisk for or false.
Wanted to test disable DM-Verity but TWRP is unable to mount /system_root (Neither TWRP 3.4.0.0 or 3.3.1 work)
My Phone has an encrypted Storage if that helps narrowing down the issue
Click to expand...
Click to collapse
Magisk 19.3 installed without any issue using twrp 3.4.0.0
bhaskarjyotisarmah51 said:
Magisk 19.3 installed without any issue using twrp 3.4.0.0
Click to expand...
Click to collapse
So you have TWRP permanently installed on Android 10? I can't get it to work
GalaxyWhy said:
So you have TWRP permanently installed on Android 10? I can't get it to work
Click to expand...
Click to collapse
download both files, twrp.img and the twrp.zip, fastboot boot twrp.img then once in TWRP flash the twrp.zip...note, make sure to remove any PIN, password or any security on the ROM first, or else it will not decrypt:good:
GalaxyWhy said:
So you have TWRP permanently installed on Android 10? I can't get it to work
Click to expand...
Click to collapse
No TWRP permanently installed. Temporary boot into TWRP using fastboot flashed magisk.
Magisk 19.3 or 20.4 both work
Just don't set any pin/password lock on the rom
imna357 said:
download both files, twrp.img and the twrp.zip, fastboot boot twrp.img then once in TWRP flash the twrp.zip...note, make sure to remove any PIN, password or any security on the ROM first, or else it will not decrypt:good:
Click to expand...
Click to collapse
Does that mean that you actually managed it to install TWRP permanently on a Pixel XL running the latest version on any Android 10 ROMs?
And what about when there's an OTA available. Do you have to reflash it then?
I'm seriously impressed, because TWRP themselves said flashing TWRP on Android 10 wouldn't be possible yet (at least on Marlin)
And last, but not least, can I put the pin/password/safety features back to activation after I installed TWRP?
Help The Peace said:
Does that mean that you actually managed it to install TWRP permanently on a Pixel XL running the latest version on any Android 10 ROMs?
And what about when there's an OTA available. Do you have to reflash it then?
I'm seriously impressed, because TWRP themselves said flashing TWRP on Android 10 wouldn't be possible yet (at least on Marlin)
And last, but not least, can I put the pin/password/safety features back to activation after I installed TWRP?
Click to expand...
Click to collapse
How you mangaed to install TWRP on Android 10?
When I flashed TWRP after installing custom rom my phone won't boot. I have to flash a stock image to make it boot.
Help The Peace said:
Does that mean that you actually managed it to install TWRP permanently on a Pixel XL running the latest version on any Android 10 ROMs?
And what about when there's an OTA available. Do you have to reflash it then?
I'm seriously impressed, because TWRP themselves said flashing TWRP on Android 10 wouldn't be possible yet (at least on Marlin)
And last, but not least, can I put the pin/password/safety features back to activation after I installed TWRP?
Click to expand...
Click to collapse
Yup, I'm on Bliss rom right now, tried all except GSI treble. When I'm doing update, I reboot to TWRP and wipe system and cache then flash the new update afterwards flash TWRP.ZIP again.
Can't install TWRP permanently, you need to flash it everytime you are doing an upgrade, that's just me
GalaxyWhy said:
So you have TWRP permanently installed on Android 10? I can't get it to work
Click to expand...
Click to collapse
Head back over to the TWRP screen on your phone and swipe the slider that says "Swipe to Allow Modifications" if needed. Now you should be sitting on the TWRP main menu where you can then go into the "Advanced" section. From there, tap the "Install Recovery Ramdisk" option, and finally, navigate to the "Download" folder where you copied the TWRP image file.
Tap the image file once to bring up the "Install Recovery" main screen and check the "Back up existing image first" option to backup your current recovery for safekeeping. Now slide the "Swipe to Install" button at the bottom to begin installing the permanent version of TWRP onto your system partition. After it finishes installing, press the home button, go to "Reboot," then "Recovery".
Help The Peace said:
Does that mean that you actually managed it to install TWRP permanently on a Pixel XL running the latest version on any Android 10 ROMs?
And what about when there's an OTA available. Do you have to reflash it then?
I'm seriously impressed, because TWRP themselves said flashing TWRP on Android 10 wouldn't be possible yet (at least on Marlin)
And last, but not least, can I put the pin/password/safety features back to activation after I installed TWRP?
Click to expand...
Click to collapse
Yep i got it working, had to flash "twrp-pixel-installer-marlin-3.3.0-0.zip" and not the latest... dunno why but hey, it works!
rodken said:
Head back over to the TWRP screen on your phone and swipe the slider that says "Swipe to Allow Modifications" if needed. Now you should be sitting on the TWRP main menu where you can then go into the "Advanced" section. From there, tap the "Install Recovery Ramdisk" option, and finally, navigate to the "Download" folder where you copied the TWRP image file.
Tap the image file once to bring up the "Install Recovery" main screen and check the "Back up existing image first" option to backup your current recovery for safekeeping. Now slide the "Swipe to Install" button at the bottom to begin installing the permanent version of TWRP onto your system partition. After it finishes installing, press the home button, go to "Reboot," then "Recovery".
Click to expand...
Click to collapse
Does this work with latest TWRP as of june?
*EDIT*
Doesn't but "twrp-3.3.0-0-marlin.img" works following rodken's guide. Cheers!
https://mobile.twitter.com/_DirtyUnicorns_/status/1300601420903854080

[ROM] [OFFICIAL] [STABLE] [R] DotOS 5.2.1 [MOTO X4 - PAYTON] [23/11/2021]

View attachment 5438975
" #DroidOnTime "
ROM Version: 5.2.1
Device: PAYTON
Maintainer: AADITYAZEO
Build Status: OFFICIAL
View attachment 5438991​
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.​
Click to expand...
Click to collapse
"This is a user-friendly thread, all your suggestions are important to us and will be taken into consideration."
View attachment 5438997
dotOS is an Android ROM that focuses on performance, stability, and User Experience. We focus on making our rom look and feel great without struggling on Performance and Battery! So that one can get the most out of your device.....
View attachment 5438999
CLEAN FLASH/First Time Installation :
01. Download the ROM, Firmware and GApps from the links above.
02. If you're coming from Oreo Flash the PIE Firmware (Factory Image or Firmware ONLY) for your device.
03. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
04. Create backup. i.e. EFS
## YOU ONLY NEED THIS STEP ONCE.. When updating Firmware's ##
05.At this point Flash "Copy Partitions Zip" In TWRP "SLOT A"
06. Flash the ROM and TWRP installer.
07. Choose Reboot -> Recovery
08. Install GApps & Magisk.
09. Reboot -> Bootloader
10. fastboot -w
11. Reboot and Enjoy.
*Note-1: Slots, ROMS install to opposite (inactive) slot
If you FLASHED ROM from "Slot A", then ROM is installed to "Slot B", If you Flashed ROM from "Slot B", then ROM is installed to "Slot A"
*Note-2: Firmware's
* Recommended to install to "Slot A" unless you have PIE firmware fully installed on "Slot B" (you can achieve this with Firmware ONLY Links or copypartitions.zip ran from Slot A after a full stock update)
DIRTY FLASH :
1.Download the latest build.
2.Reboot to recovery.
3.Flash the latest build along with the twrp.
4.reboot to recovery. (very Important)*
5.flash optional packages like gapps and magisk.
6.Wipe Cache.
7.Reboot.
Note: If upgrading from 5.0.* to 5.1.* a clean flash is required.
Note: GApps only has to be flashed once whereas Magisk/Su is to be flashed every time you Dirty Flash the OTA Update.
View attachment 5439003
CLICK ME
View attachment 5439005
COMPLETE CHANGELOG : https://changelogs.droidontime.com/
View attachment 5439007
AOSP
Lineage OS
Pixel Experience
Dirty Unicorns
Project Lighthouse
And all other open-source Devs/Teams.
View attachment 5439009
Mohan CM - Founder/Core Developer
Iacob Ionut - UI, UX Developer/ Core Developer
Sipun Kumar - Developer/Maintainer
Special thanks:
Manish Bajpai - Web Developer
Important Links
If you liked our Project, please consider supporting us. - Donate - https://www.paypal.me/MOHANCM
Donate to device maintainer. - Donate - https://www.paypal.me/jackvortexhd
dot OS source
dotOS-Device Sources
{
"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"
}
Telegram Group
Telegram Channel
Website
Downloads page
REPORTING BUGS !
As soon as the problem occurs, take a LOGCAT!
for more READ THIS
and do not forget to send it to us
View attachment 5439011
Contributors: AadityaZeo
Source Code: https://github.com/DotOS
GitHub : - https://github.com/aadityazeo
ROM OS Version: 11.x Android R
Version Information
Status: STABLE
Current Stable Version: v5.2.1
Stable Release Date: 23-11-2021​
Hi there. First time trying Dot. Despite trying lots of different combinations of flashing, and trying to ensure I followed the instructions above exactly (with the exception that I do not want Gapps or Magisk), rebooting to System always reboots into Recovery instead.
For grins, I tried the latest unofficial lineage (lineage-18.1-20211112-UNOFFICIAL-payton), which installed and booted up just fine.
Suggestions appreciated.
Same problem be my.
Randy Power said:
Hi there. First time trying Dot. Despite trying lots of different combinations of flashing, and trying to ensure I followed the instructions above exactly (with the exception that I do not want Gapps or Magisk), rebooting to System always reboots into Recovery instead.
For grins, I tried the latest unofficial lineage (lineage-18.1-20211112-UNOFFICIAL-payton), which installed and booted up just fine.
Suggestions appreciated.
Click to expand...
Click to collapse
Which Verison of twrp you're using?
Aaditya ZeO said:
Which Verison of twrp you're using?
Click to expand...
Click to collapse
twrp-3.6.0_9-0-payton
I've also tried installing dot without installing twrp. When I do this, booting to system gives me the booting animation (3 colored circles that look like two planets circling the sun). But it gets stuck there. One time, I waited for several hours, enjoying the planets animation.
Randy Power said:
twrp-3.6.0_9-0-payton
I've also tried installing dot without installing twrp. When I do this, boring to system gives me the booting animation (3 colored circles that look like two planets circling the sun). But it gets stuck there. One time, I waited for several hours, enjoying the planets animation.
Click to expand...
Click to collapse
There're quite few things which you need to remember.
1st
2nd
If you were stuck on boot logo, you should perform fastboot - w in bootloader.
3rd - as per your comment u want vanilla edition. So i suggest u to stick with two 3.5xxx (latest prior to version 3.6xx) and follow the steps as stated below
a) completely wipe the phone
b) rom + twrp
c) reboot to recovery
d) wipe data in twrp
e) reboot to system.
This should work as I've also installed vanilla Verison with same process.
Thank you very much, @Aaditya ZeO. I will try again with those steps when I get back to my x4 today.
If i want to install the gapps version, should I use twrp 3.6 instead of 3.5?
Randy Power said:
Thank you very much, @Aaditya ZeO. I will try again with those steps when I get back to my x4 today.
If i want to install the gapps version, should I use twrp 3.6 instead of 3.5?
Click to expand...
Click to collapse
I don't think it matters, I've use twrp 3.2 and 3.6 to install gapps and had no issues in either case.
I appreciate the suggestions. I think I've tried everything, including installing twrp 3.5.xxx, but I still get the same result.
If I clean install dot and fastwipe -w , I still get the spinning planets.
If I clean install dot, install twrp 3.5 or 3.6, and fastwipe -w, a "reboot system" always brings up twrp again.
In case it matters, my device is payton XT1900-1 32GB P4.
Randy Power said:
I appreciate the suggestions. I think I've tried everything, including installing twrp 3.5.xxx, but I still get the same result.
If I clean install dot and fastwipe -w , I still get the spinning planets.
If I clean install dot, install twrp 3.5 or 3.6, and fastwipe -w, a "reboot system" always brings up twrp again.
In case it matters, my device is payton XT1900-1 32GB P4.
Click to expand...
Click to collapse
Can you try to install gapps version for once?
I just did this:
fastboot boot twrp
completely wipe the phone
install rom 5.2.1 (dotOS-R-v5.2.1-payton-GAPPS-20211123-1226.zip)
install twrp (twrp-installer-3.5.2_9-0-payton.zip)
reboot to bootloader
fastboot boot twrp (in retrospect, I could have rebooted to twrp without fastboot)
wipe data in twrp
format data in twrp
reboot to bootloader; fastwipe -w
reboot to system.
Result: Spinning planets (boot animation).
I'll try again with the above, except step 5-6 reboot directly to twrp.
By the way, is this the expected result of "fastboot -w" on the x4?
Code:
>fastboot -w
Erasing 'userdata' OKAY [ 0.322s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
After the above, I formatted data from twrp. It completed without errors, so I rebooted to system.
Result: Still stuck on spinning planets.
Randy Power said:
I just did this:
fastboot boot twrp
completely wipe the phone
install rom 5.2.1 (dotOS-R-v5.2.1-payton-GAPPS-20211123-1226.zip)
install twrp (twrp-installer-3.5.2_9-0-payton.zip)
reboot to bootloader
fastboot boot twrp (in retrospect, I could have rebooted to twrp without fastboot)
wipe data in twrp
format data in twrp
reboot to bootloader; fastwipe -w
reboot to system.
Result: Spinning planets (boot animation).
I'll try again with the above, except step 5-6 reboot directly to twrp.
By the way, is this the expected result of "fastboot -w" on the x4?
Code:
>fastboot -w
Erasing 'userdata' OKAY [ 0.322s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
nope this shouldn't be the output after the fastboot -w.
Aaditya ZeO said:
nope this shouldn't be the output after the fastboot -w.
Click to expand...
Click to collapse
I appreciate that. I've tried many combinations of formatting data in TWRP, which seems to work. Resizing the partition and fsck on the partition work fine, all in TWRP. I can even copy files from /externalsd to /sdcard, and the fs survives a reboot.
However, fastboot -w always fails (error shown above), and booting the system gives spinning planets animation forever.
I'd be grateful for pointers on fixing the fastboot -w problem, if that is what's needed.
Hello
I installed dotOS 5.2.1 and when it's time to enter the PIN code it says that the sim card is locked. Tried both PIN and PUK, but none works. What should I do?
OK, so I solved it by basically following these instructions:
However, I now have a new problem. If I power off the phone while the USB charger is connected, it restarts the phone instead. And if it's powered off and I connect the charger, it turns itself on. This didn't happen with Android 9. How can I fix it? I do not want my phone to switch itself on when charging.
Randy Power said:
Hi there. First time trying Dot. Despite trying lots of different combinations of flashing, and trying to ensure I followed the instructions above exactly (with the exception that I do not want Gapps or Magisk), rebooting to System always reboots into Recovery instead.
For grins, I tried the latest unofficial lineage (lineage-18.1-20211112-UNOFFICIAL-payton), which installed and booted up just fine.
Suggestions appreciated.
Click to expand...
Click to collapse
Are you flashing to the appropriate slot?
For those having problems with the phone rebooting after a few seconds after upgrading from an Android 9 rom:
You might need to upgrade the modem firmware. That happened to me while upgrading from Lineage 16.0 to Lineage 18.1. After investigating a bit, I figured out the problem happened when connecting to the mobile network or (sometimes) wifi.
This is (roughly) how I solved the problem:
- flash your choice of recovery/system (not needed if already done - if you do this later your updated firmware might be overwritten)
- download the latest payton stock rom from lolinet's obsolete phones archive
- unzip and cd to unzipped folder
- connect phone and reboot to bootloader
- make sure you have fastboot and run the following commands (adapt to your OS as needed):
mfastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot erase carrier
fastboot erase userdata (I did it after backing up my data, but I think it was not necessary)
fastboot erase ddr
fastboot reboot
- have fun!
Notes:
- you might just flash a subset of the binaries above, I flashed what I thought was needed. The original reddit thread mentioned only NON-HLOS.bin and fsg.bin
- after having tried many things I ended up with dotOS 5.2.1 and will try it for a while
References
- this reddit comment
- Method 2 at rootmygalaxy
rodrigopitanga said:
Are you flashing to the appropriate slot?
Click to expand...
Click to collapse
I think yes. It's been a few weeks now, so my memory on the details is fuzzy. But I'm familiar with the A/B monkey business, copy partitions, etc. And flashing lineage worked out successfully. Thank you for the reply.
Does adoptable storage work?

[RECOVERY][UNOFFICIAL]TWRP 3.6.0 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.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

Development [RECOVERY][12][UNOFFICIAL] OrangeFox-R11.1_A12.1

OrangeFox Recovery Project
{
"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.
*
* 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 recovery
* 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.
*
*/
OrangeFox is FREE SOFTWARE
Information
Status: unofficial Beta
Android 12 only
Version: R11.1_1
Release Date: 11th October 2022
Updated: February 2023
Maintainer: @CFKod
Sources
Device Tree: https://github.com/forforksake/recovery_device_motorola_kyoto
Kernel: Prebuilt
Downloads:
onedrive
github releases
Installation:
This is an A/B device, it does not have a recovery partition
It also does not allow fastboot boot command
Only option is this case it to fastboot flash boot ofox.img from bootloader, then select recovery mode, once booted into recovery, flash your stock boot image followed by flashing the ofox.zip (to install the recovery to ramdisk)
Code:
fastboot flash boot ofox.img
Select recovery mode from the bootloader menu
Once ofox has loaded
install your stock boot.img to boot parition
Install ofox.zip
Reboot to bootloader and then select recovery mode
You are now in Orangefox recovery
Install magisk from files menu included
https://wiki.orangefox.tech/en/guides/installing_orangefox
Documentation (FAQ):
https://wiki.orangefox.tech/en/guides
Source changelog:
https://wiki.orangefox.tech/changelog
Unlocked Bootloader required
Moto unlocking site
vbmeta flags
From bootloader, Flash vbmeta from your firmware zip using two important flags
(--disable-verification --disable-verity)
Code:
fastboot flash vbmeta --disable-verification --disable-verity vbmeta.img
Torch not yet working and in order to fit into the devices small boot image AAPT has also been removed.
XDA : DevDB Information
OrangeFox Recovery Project, Tool/Utility for Kyoto
(Tested on Motorola Edge 20 lite 5G)
Contributors
@CFKod
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
* Maintainer @CFKod
ADB sideload not working with the img, it terminates sideloads with the following error: Failed to unmount vendor
The image is purely to allow you to flash your own stock boot image... Then install orange fox recovery ramdisk over your stock boot by flashing the zip
Unlocked Bootloader required
Moto unlocking site
vbmeta flags
From bootloader, Flash vbmeta from your firmware zip
using two important args
--disable-verification --disable-verity
Makefile:
fastboot flash vbmeta --disable-verification --disable-verity vbmeta.img
Thanks!
installation
From unlocked BL with patched vbmeta,
Fastboot flash boot ofox.img
Select recovery mode in bootloader > boot into ofox recovery
install your stock A12 boot.img **do not reboot**
flash release zip _this simply installs recovery ramdisk_.
flash magisk.zip if required
CFKod said:
installation
From unlocked BL with patched vbmeta,
Fastboot flash boot ofox.img
Select recovery mode in bootloader > boot into ofox recovery
install your stock A12 boot.img **do not reboot**
flash release zip _this simply installs recovery ramdisk_.
flash magisk.zip if required
Click to expand...
Click to collapse
i cant neither boot or flash the recovery
i have magisk installed anf i have ramdisk. what is wrong here??? thx for help
hmmm, now i 'm getting error E3004: this package is for kyoto. this device not supported
update: i'm now able to flash orangefox.img, but when i boot to recovery ,instead it reboots bootloader :\
freakologik said:
update: i'm now able to flash orangefox.img, but when i boot to recovery ,instead it reboots bootloader :\
Click to expand...
Click to collapse
Sorry for the delay
I have now resolved that issue
Please see the ofox Img...
This will allow you to boot recovery
Then install stock
Followed by ofox zip
ofox
Folder
1drv.ms
freakologik said:
i cant neither boot or flash the recovery
View attachment 5729847
i have magisk installed anf i have ramdisk. what is wrong here??? thx for help we
Click to expand...
Click to collapse
freakologik said:
i cant neither boot or flash the recovery
View attachment 5729847
i have magisk installed anf i have ramdisk. what is wrong here??? thx for help
Click to expand...
Click to collapse
Wait..
The device doesn't have a recovery partition and it also doesn't allow us to fastboot boot
It only allows us to fastboot flash boot boot.img
I tried to make that clear on the release download
I will update the main thread
CFKod said:
Wait..
The device doesn't have a recovery partition and it also doesn't allow us to fastboot boot
It only allows us to fastboot flash boot boot.img
I tried to make that clear on the release download
I will update the main thread
Click to expand...
Click to collapse
yeah in the meantime i've understand it
i try install now
thanks for your work and time
freakologik said:
yeah in the meantime i've understand it
i try install now
thanks for your work and time
Click to expand...
Click to collapse
Thanks, I overly panicked haha.
If you are on telegram
Feel free to message me directly
@cardiffian
it's working,finally!!!
a question : to use the recovery can i never use pin/fingerprint? it's not clear for me
freakologik said:
it's working,finally!!!
a question : to use the recovery can i never use pin/fingerprint? it's not clear for me
Click to expand...
Click to collapse
Fantastic news
Well, try rebooting to android,
Create the lockscreen protection again;
Reboot to OrangeFox
Decrypt... Fingers crossed
So I successfully decrypted user data on my first beta dated 03-10-22
Used it perfectly for quite a few days.
I've added a folder to onedrive as 03102022 with the zip, feel free to try it if you can't get anywhere with user decryption in current build.
However, I have since had to make some build tweaks to try and improve what we had... Testing backup restore etc...
Now Userdata decryption only works for me when lockscreen pin is removed...
I'm correcting some annoyances and mount errors in the logs... And reverting some of the changes I have since made. So will let you know once I have uploaded.
Also some excellent advice on the ofox wiki - I have format /data already to test the feature, so perhaps my next step is fastboot - w and start a fresh
https://wiki.orangefox.tech/en/guides/encryption
Only tested on a 12
Unfortunately I no longer have a working kyoto device
Smashed the LCD for a 2nd time.
I can access the device itself via adb, so I get to mess around with phonesploit / metasploit framework without any worry if I break it
I can't see the lcds for these things becoming cheap and widely available for a while, so for now it joins the graveyard of android devices in mydrawer
Purchased a pixel 6a
@CFKod
How to upload these Recovery?
Thank you in advance.
I need help in my thread, do you know how to do it?
Questions about firmware
Hi. I want to change the software channel from pluspl to RETEU. How to do it? Anyone help? Thanks in advance, best regards.
forum.xda-developers.com
.

Categories

Resources