How to install a gsi onto your Mi 11t > Pro
This will wipe your phone and I'm not responsible for any bricked device's.
you can always go back to stock and try again.
Clean install suggested!
1.0 Start with downloading things
Latest Platformtools Here
stock miui 13 Here fastboot rom I use EEA 13.0.8.0
Gsi of choosing Here or get latest gsis from Telegram
Spoiler: Screenshot
{
"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"
}
vbmeta miui13 from you fastboot rom.
If you choose to install magisk use this module to help hinding from security apps
and patch one your self.
safetynet
1.1 Start the process
Start with flashing stock 13 on your mi11tpro.
reboot to fastboot (shutdown phone then hold power and voldown till you see fastboot)
unzip the platform tools and move your gsi, vbmeta and magisk.img(if needed) to the folder
in the platform tools folder open a terminal.
unzip the stock miui 13 .tgz until you get the folder with the flash_all.bat file
copy flash_all.bat and images to your fastboot folder
Connect your phone to your pc then
launch the flash_all file and let your phone boot
Reboot to fastboot
1.2 Flash gsi
./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img(stock or google)
./fastboot erase system
./fastboot flash system Gsi.img
./fastboot reboot recovery
factory reset the phone here
reboot to system and your done.
1.3 Flash magisk
how to patch own boot.img
extract boot.img from the stock rom
copy over to working phone with magisk app installed
open magisk and select install / select file to patch
select your boot.img
then copy your patched boot.img to your fastboot folder
Boot prepatched image.
./fastboot boot Patchedboot.img
t
when booted open magisk app/install the apk from github.
cancel the first message if you get any and just click install, direct install.
then just reboot and you have root.
And your done
2.0 Extra's and fixes
Some times if you reboot it get stock to fix this use the google vbmeta
go to settings/ phh teble settings and enable these settings
qualcomm features/disable soundvolume effects &&
use alternate audio policy --fixes audio bugs
xiaomi features/enable dr2w --double toch to wake
misc features/force fps/120hz --( Only if you want 120hz)
ims features/install ims apk for qualcomm vendor --Makes sms work
than reboot to apply fixes
volume steps to high fix Here Not needed for all gsi's
Get lSpeed to improve battery and performance
Get better camera use Gcam I use MTSL_Snapcam 7.1 with antykat_v13
Thanks to phhusson, bhammler,
Good guide. But not a DD. Good job
Android 12 finally out. How fast do devs usually put out ROMS for Xiaomi devices?
Really looking forward for Pixel Experience as always
I'm using GSI PixelExperience_arm64-ab-vndklite-12.0-20220208-UNOFFICIAL. It's really working good and it's my daily driver.
The missing auto brightness could be fixed with the Velis Autobrightness App. It passes SafteyNet, too
DT2W is not working, but I use GravityScreen App instead.
It's a lot of work if you switch from MIUI to GSI, but it's worth it.
I've tested all other GSi builds, and I had only trouble. I stick with PixelExperience
bhammler said:
I'm using GSI PixelExperience_arm64-ab-vndklite-12.0-20220208-UNOFFICIAL. It's really working good and it's my daily driver.
The missing auto brightness could be fixed with the Velis Autobrightness App. It passes SafteyNet, too
DT2W is not working, but I use GravityScreen App instead.
It's a lot of work if you switch from MIUI to GSI, but it's worth it.
I've tested all other GSi builds, and I had only trouble. I stick with PixelExperience
Click to expand...
Click to collapse
Do you have a link for VBMETA image?
first I made a clean fastboot flash using:
vili_global_images_V12.5.10.0.RKDMIXM_20211211.0000.00_11.0_global
I took the vbmeta thats inside the image folder.
working commands:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot fastboot (=fastbootd)
fastboot flash system PixelExperience_arm64-ab-vndklite-12.0-20220208-UNOFFICIAL.img
fastboot reboot recovery
wipe data (Mi Recovery)
After your setup flash magisk.img
fastboot (NOT fastbootd !) flash boot magisk.img
That worked for me
Finally got it to boot. Thx
Really weird sound from the speakers. Sounds almost like bass is broken :/ Fixed in PHH settings
bhammler said:
first I made a clean fastboot flash using:
vili_global_images_V12.5.10.0.RKDMIXM_20211211.0000.00_11.0_global
I took the vbmeta thats inside the image folder.
working commands:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot fastboot (=fastbootd)
fastboot flash system PixelExperience_arm64-ab-vndklite-12.0-20220208-UNOFFICIAL.img
fastboot reboot recovery
wipe data (Mi Recovery)
After your setup flash magisk.img
fastboot (NOT fastbootd !) flash boot magisk.img
That worked for me
Click to expand...
Click to collapse
Thank you for more information updated the form.
Finally I found a better and perfect working solution:
Pixel Experince SLIM works, because its under 3 GB. Here are my new steps:
1. fastboot flash_all vili_global_images_V12.5.10.0.RKDMIXM_20211211.0000.00_11.0_global
2. let it reboot to the setup screen and turn it off
3. fastboot boot twrp.img (no need to install)
4. update through twrp to miui_VILIGlobal_V13.0.1.0.SKDMIXM_e7e8f0ef90_12.0.zip
5. it shows some errors, but it's still booting up to the setup screen. Turn off
6. From now on: everything in FastbootD (fastboot reboot fastboot)
7. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (see attached extracted vbmeta from MIUI 13)
8. fastboot erase system
9. fastboot flash system PixelExperience_arm64-ab-slim-12.0-20220221-UNOFFICIAL.img
10. fastboot reboot recovery
11. wipe data in Mi Recovery
12. reboot and done
13. for magisk you will find attached the pachted boot image from MIUI 13, and the extracted vbmeta. I flashed magisk in regular fastboot mode. Don't know if thats right, but it's working.
P.S. everything was flashed into slot_b (didn't change anything)
Now the screen brightness works, d2tw is working and it passes safetynet
bhammler said:
Finally I found a better and perfect working solution:
Pixel Experince SLIM works, because its under 3 GB. Here are my new steps:
1. fastboot flash_all vili_global_images_V12.5.10.0.RKDMIXM_20211211.0000.00_11.0_global
2. let it reboot to the setup screen and turn it off
3. fastboot boot twrp.img (no need to install)
4. update through twrp to miui_VILIGlobal_V13.0.1.0.SKDMIXM_e7e8f0ef90_12.0.zip
5. it shows some errors, but it's still booting up to the setup screen. Turn off
6. From now on: everything in FastbootD (fastboot reboot fastboot)
7. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (see attached extracted vbmeta from MIUI 13)
8. fastboot erase system
9. fastboot flash system PixelExperience_arm64-ab-slim-12.0-20220221-UNOFFICIAL.img
10. fastboot reboot recovey
11. wipe data in Mi Recovery
12. reboot and done
13. for magisk you will find attached the pachted boot image from MIUI 13, and the extracted vbmeta. I flashed it in regular fastboot mode. Don't know if thats right, but it's working.
P.S. everything was flashed into slot_b (didn't change anything)
Now the screen brightness works, d2tw is working and it passes safetynet
Click to expand...
Click to collapse
Can you send me screenshots of the rom thank you
Sure
bhammler said:
Finally I found a better and perfect working solution:
Pixel Experince SLIM works, because its under 3 GB. Here are my new steps:
1. fastboot flash_all vili_global_images_V12.5.10.0.RKDMIXM_20211211.0000.00_11.0_global
2. let it reboot to the setup screen and turn it off
3. fastboot boot twrp.img (no need to install)
4. update through twrp to miui_VILIGlobal_V13.0.1.0.SKDMIXM_e7e8f0ef90_12.0.zip
5. it shows some errors, but it's still booting up to the setup screen. Turn off
6. From now on: everything in FastbootD (fastboot reboot fastboot)
7. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (see attached extracted vbmeta from MIUI 13)
8. fastboot erase system
9. fastboot flash system PixelExperience_arm64-ab-slim-12.0-20220221-UNOFFICIAL.img
10. fastboot reboot recovey
11. wipe data in Mi Recovery
12. reboot and done
13. for magisk you will find attached the pachted boot image from MIUI 13, and the extracted vbmeta. I flashed it in regular fastboot mode. Don't know if thats right, but it's working.
P.S. everything was flashed into slot_b (didn't change anything)
Now the screen brightness works, d2tw is working and it passes safetynet
Click to expand...
Click to collapse
Does everything work without any issues? can you please link the pixel experience rom?
all ROMs have issues even Miui
Releases · ponces/treble_build_pe
Script and patches for building PHH-Treble Pixel Experience - ponces/treble_build_pe
github.com
donjamal said:
Does everything work without any issues? can you please link the pixel experience rom?
Click to expand...
Click to collapse
Haptic feedback when typing not working .
bariz143 said:
Haptic feedback when typing not working .
Click to expand...
Click to collapse
That's all? Camera, Bluetooth, Gpay, internet, all works?
donjamal said:
That's all? Camera, Bluetooth, Gpay, internet, all works?
Click to expand...
Click to collapse
Never use Gpay but yeah all other things works. Sound is verry bad at first boot. But you can disable sound enchantments in PHH settings and viola
Tried flashing magisk.img in magisk manager but no root for me.
bariz143 said:
Never use Gpay but yeah all other things works. Sound is verry bad at first boot. But you can disable sound enchantments in PHH settings and viola
Tried flashing magisk.img in magisk manager but no root for me.
Click to expand...
Click to collapse
Did you try patching the boot.img and flashing it back?
donjamal said:
Did you try patching the boot.img and flashing it back?
Click to expand...
Click to collapse
I can't find any boot.img anywhere and don't remember how to patch and extract images . I'm a flashoholic only
working:
-GPay
-Bluetooth
-5G, VoLTE, VoWifi (with fix)
-Stereo-Speakers
-Auto-Brightness (but better with Velis Autobrightness App)
-Fingerprintsensor
-Double Tap to Wake
-Camera (I use Gcam)
not working:
-raise to wake
-OK Google (because of Slim Version)
The Rom is working very smooth, no reboots and no issues
bariz143 said:
Never use Gpay but yeah all other things works. Sound is verry bad at first boot. But you can disable sound enchantments in PHH settings and viola
Tried flashing magisk.img in magisk manager but no root for me.
Click to expand...
Click to collapse
magisk.img is for fastboot
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.4.0
PitchBlack version: 3.0.0
For device: Realme 6 Pro(RMX2061/2063)
Authors build: @ishu88
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/PitchBlackRecoveryProject/android_device_realme_RMX2061-pbrp
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
Disable DM Verity
Use AromaFM as default file manager
Various tools are included
Universal flash-able file for all variant of a device
Many bug fixes ,optimization & much more
Click to expand...
Click to collapse
Installation Instructions
WARNING
If you are flashing this recovery for the first time /or/ If you are flashing this after installing the stock ROM,
You will get a "Current Image Destroyed Error".
To fix it, Just flash the original vbmeta.img extracted from the ozip file of current realmeui ROM and flash it in fastboot mode by disabling Verity.
Fastboot code to flash vbmeta below
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Flashing from previous version or other recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
From PC
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
Changelog
PBRP Side Changelog
Code:
v3.0.0
- Fully Redesigned UI
- Added new Keychecks While Flashing PBRP or recovery.img or Ramdisk
- Fully Redesigned Website https://pitchblackrecovery.com
- New Android like Power Menu (Activated via power key hold)
- Flashlight toggled by Vol up(+) on hold
- New Scrollable Advanced menu
- Totally Redesigned Icons
- Removed old unnecessary Theming Stuff
- Tested on almost all handy Resolutions
- Flashlight toggle on Lockscreen
- More checks for SAR/Non-SAR
- New Navbar
- Support on almost all Android version (5.0+)
- Update ozip decrypt
- Fix up ozip print logs & take all paths
- Update FUNDING.yml
- Fixed encrypted removal checks & buttons
- Add Flag for disabling treble compatibility by default
- Is_Data_Wiped: Simplify function signature
- Unified AB_OTA_UPDATER
- Change AB device log storage to /data/recovery
- Delay start if specified in board
- Optimize touchscreen driver initialization delay.
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Device Side Changelog
Code:
initial build
Bugs
- Stock ROM Ozip flashing error (use twrp for now)
- Flashlight not working
- MTP only works for SD card
Downloads
Flashable zip
https://drive.google.com/file/d/14BgBiKlfMXnKRwBp5YZh2g0N85gm6sJY/view?usp=drivesdk
XDA:DevDB Information
Pitch Black Recovery Project, Tool/Utility for the Realme 6 Pro
Contributors
Kevin Saiza, ishu88
Version Information
Status: Testing
Created 2020-08-19
Last Updated 2020-08-19
Screenshots
Take a look what pbrp offers
Reserved 2
wow thank you friend & hope to fix all problems asap
all support to your work
do you need a patcheed vbmeta to installl this fresh to a bootloader unlocked 6 pro? Im very new sorry if this is a obvious answer.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Okay so i just straight up flashed the recovery image and yep theres something else you need to make it work. Probably refer to the TWRP guide in this same device forum to figure it out.
Thanks for your work, now i have a phone to fix lol not complaining tho! i might be able to get my android skills up!
SKELEKINETIC said:
Okay so i just straight up flashed the recovery image and yep theres something else you need to make it work. Probably refer to the TWRP guide in this same device forum to figure it out.
Thanks for your work, now i have a phone to fix lol not complaining tho! i might be able to get my android skills up!
Click to expand...
Click to collapse
Just flash the original vbmeta extracted from the ozip file of current stock ROM and flash it in fastboot mode by disabling Verity
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Kevin Saiza said:
Up-to-date kernel, built from sources
Click to expand...
Click to collapse
Can you share how you got the 6 pro kernel compiling, and most of all, running?
Kevin Saiza said:
Just flash the original vbmeta extracted from the ozip file of current stock ROM and flash it in fastboot mode by disabling Verity
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Why the above command gives me the error as below?
--------------------------------------------------------------
PS C:\Users\Administrator\Desktop\platform-tools> fastboot devices
eaaf29e6 fastboot
PS C:\Users\Administrator\Desktop\platform-tools> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
C:\adb\fastboot.exe: unknown option -- disable-verity
PS C:\Users\Administrator\Desktop\platform-tools>
--------------------------------------------------------------
neoxcool said:
Just flash the original vbmeta extracted from the ozip file of current stock ROM and flash it in fastboot mode by disabling Verity
Why the above command gives me the error as below?
--------------------------------------------------------------
PS C:\Users\Administrator\Desktop\platform-tools> fastboot devices
eaaf29e6 fastboot
PS C:\Users\Administrator\Desktop\platform-tools> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
C:\adb\fastboot.exe: unknown option -- disable-verity
PS C:\Users\Administrator\Desktop\platform-tools>
--------------------------------------------------------------
Click to expand...
Click to collapse
Try to use latest version of minimal adb and fastboot , and , platform tools
Do you have twrp 3.4 built for this device? Or does nullexceptiosn 3.3 work to flash stock ozips?
Kevin Saiza said:
Just flash the original vbmeta extracted from the ozip file of current stock ROM and flash it in fastboot mode by disabling Verity
Click to expand...
Click to collapse
Thank you. Where can I learn more about "dm-verity" and vbmeta? They are anti tamper protection right? W
I know xda really isnt for noob but a step by step with prerequisites would be amazing. currently i cant get FBE to work.
Pitchblacl no longer decrypts internal storage!
neoxcool said:
Just flash the original vbmeta extracted from the ozip file of current stock ROM and flash it in fastboot mode by disabling Verity
Why the above command gives me the error as below?
--------------------------------------------------------------
PS C:\Users\Administrator\Desktop\platform-tools> fastboot devices
eaaf29e6 fastboot
PS C:\Users\Administrator\Desktop\platform-tools> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
C:\adb\fastboot.exe: unknown option -- disable-verity
PS C:\Users\Administrator\Desktop\platform-tools>
--------------------------------------------------------------
Click to expand...
Click to collapse
I had the same issues with the commands, even after updating my Fastboot, and for some reason, they worked fine in Command Prompt, instead of Powershell, give it a try!!
Link doesnt work. google says the file is in the owners trash
SKELEKINETIC said:
Link doesnt work. google says the file is in the owners trash
Click to expand...
Click to collapse
It works
SKELEKINETIC said:
Do you have twrp 3.4 built for this device? Or does nullexceptiosn 3.3 work to flash stock ozips?
Click to expand...
Click to collapse
To flash stock ozip,use twrp only
I couldn't download this L.R. TWRP from russian site pda. Does anyone have this file (LR.TWRP-3.4.2b_RMX2061.img)?
It looks to be incompatible with the latest firmware, A.33. I'm going to downgrade and see if PBRP works with A.31. It did work before I upgraded to A.33.
I was able to make it work after I downgraded to A.17 but it broke the moment I flashed anything to do with the system partition.
WARNING: THIS IS EXPERIMENTAL BETA MEANT FOR DEVELOPERS AND TESTERS NOT AS DAILY DRIVER
Caution: Android 11 builds are incompatible with Android 12. Beware!
Credits:
@Woomymy
@J6idot
@mastersenpai05
@myst33d
https://github.com/notmyst33d
Developers WoomyMy, J6idot , mastersenpai05 and Myst33d have helped develop an unofficial TWRP for rosemary - xiaomi redmi note 10s
Installation Video:
Code:
https://www.mediafire.com/file/f4zcls9sgi3nkoj/352+redmi+note+10s.rar/file
http://www.mediafire.com/file/p3zhivru97bdlke/no-verity-opt-encrypt-6.1.zip/file
https://github.com/RedmiNote10S/recovery_device_xiaomi_rosemary
Since this is not yet official, only proceed if you are competent enough and brave.
(If you need instructions on how to flash, please do not flash this with fastboot method)
Feel free to discuss any bugs or issues and fixes so that everybody can benefit from our findings.
TWRP 3.6+ Development Build status, fixes, bugs and downloads: [here]
TWRP -3.6.2_11-2
NameModifiedTWRP-3.6.2_11-208/03/2022
Changelog
Fix brightness when max brightness is 255
Render GUI at 60FPS
Reposition statusbar icons and remove top offset
A lot of code cleanup
Update TWRP sources
DONT INSTALL THIS ON MIUI 13
Install instructions
Without TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download TWRP .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Install -> Install Image -> Select stock boot.img -> “Flash to: Boot”)
Next, go in Advanced -> Flash current TWRP and swipe to flash TWRP.
Reboot and enjoy!
With custom recovery
Download TWRP .ZIP installer and flash it in recovery (you can also use adb sideload for recoveries like LineageOS recovery)
Compatibility
Android 11 Roms: YES
Android 12 Roms: NO
TWRP-3.6.2_12-rc1
NameModifiedTWRP-3.6.2_12-rc108/04/2022
Changelog
Sync TWRP sources
Add support for Android 12 decryption
Fix booting on MIUI13
DONT INSTALL THIS ON MIUI 12.5
Install instructions
Without TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download TWRP .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Install -> Install Image -> Select stock boot.img -> “Flash to: Boot”)
Next, go in Advanced -> Flash current TWRP and swipe to flash TWRP.
Reboot and enjoy!
With custom recovery
Download TWRP .ZIP installer and flash it in recovery (you can also use adb sideload for recoveries like LineageOS recovery)
Compatibility
MIUI 13 vendors: COMPATIBLE
MIUI 12 vendors:
A11 GSI / MIUI 12 system: FULLY INCOMPATIBLE
A12 GSI: COMPATIBLE, but you CAN NOT flash the boot.img, you need to flash the UPDATE ZIP using a custom recovery / Magisk
OrangeFox-R11.1_1-Unofficial
NameModifiedOrangeFox-R11.1_1-Unofficial07/01/2022
Changelog
Fix brightness when max brightness is 255
Render GUI at 60FPS
Reposition statusbar icons and remove top offset
A lot of code cleanup
Update OrangeFox sources
DONT INSTALL THIS ON MIUI 13
Update Magisk OrangeFox addon to v25.2
Install instructions
Without TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download OrangeFox .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Select stock boot.img -> “Flash to: Boot”)
Next, go in Menu -> Flash current OrangeFox and swipe to flash OrangeFox.
Reboot and enjoy!
To get Fox addons working, you need to reflash OrangeFox .zip file
With custom recovery
Download OrangeFox .ZIP installer and flash it in recovery (you can also use adb sideload for recoveries like LineageOS recovery)
Compatibility
Android 11 Roms: YES
Android 12 Roms: NO
Older versions:
NameModifiedBeta-07-11-30-202112/17/2021
🗞 Changelog
Sync TWRP sources (Version number updated to 3.6.0)
Symlink /dev/block/bootdevice -> /dev/block/platform/bootdevice (required by some scripts like OrangeFox installer)
Allow flashing VBMeta
Disable "Reflash TWRP after flashing ROM". (Causes AVB problem when installing MIUI, can still be done manually)
Build ZIP TWRP installer
Publish build logs for more transparency
Known bugs
Mounting Adopted storage
Vibrator
NameModifiedRC-01-01-09-20221/9/2022
🗞 Changelog
Fix Bootctrl
Fix vibrator
Known bugs
Mounting Adopted storage
TWRP Version 3.6.1_11-1
NameModifiedTWRP-3.6.1_11-13/13/2022
🗞 Changelog
Fix BootCTRL
Update TWRP sources
Fix vibrator
Enable DT2W in recovery
Install instructionsWithout TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download TWRP .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Install -> Install Image -> Select stock boot.img -> “Flash to: Boot”)
Next, go in Advanced -> Flash current TWRP and swipe to flash TWRP.
Reboot and enjoy!
With TWRP/OrangeFox
Download TWRP .ZIP installer and flash in recovery
TWRP Version 3.6.2_11-1
NameModifiedTWRP-3.6.2_11-16/14/2022
🗞 Changelog
Sync TWRP sources
Orangefox Recovery Version R11.1_1-Beta
NameModifiedOrangeFox-R11.1_1-Beta3/13/2022
🗞 Changelog
Fix BootCTRL
Update OrangeFox sources
Fix vibrator
Enable DT2W in recovery
Update Magisk OrangeFox addon to 24.2
Install instructionsWithout TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download OrangeFox .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Select stock boot.img -> “Flash to: Boot”)
Next, go in Menu -> Flash current OrangeFox and swipe to flash OrangeFox.
Reboot and enjoy!
To get Fox addons working, you need to reflash OrangeFox .zip file
With TWRP/OrangeFox
Download OrangeFox .ZIP installer and flash in recovery
Nice, it's beta 2
to apply encrypt patch, you must decrypt first.
So
- you have to disable security password/fingerprint in your parameter first.
- then reboot in recovery
- format data
- reboot again to recovery and apply patch.
How to use redmi note 10s unofficial twrp recovery
test (beta 2) after disabling security (fingerprint and pin)
- flashing magisk.zip -> ok
- backup -> ok
- restore -> ok
- MTP internal SD -> ok
- MTP external SD -> nok, file manager stuck on it (win10 or linux mint)
Please full prosses explain and 1 question flash fastboot method
This the link of the Official Tutorial from the Unofficial TWRP Website:
unofficial twrp 3.6.1 Root Redmi Note 10s (rosemary) - unofficial twrp
Download unofficial twrp 3.6.1 root Redmi Note 10s, user who own Redmi Note 10s can root it by following the below instructions
unofficialtwrp.com
Great
miravision said:
Developer WoomyMy has released an unofficial TWRP for rosemary - xiaomi redmi note 10s
Installation Video:
Code:
https://www.mediafire.com/file/f4zcls9sgi3nkoj/352+redmi+note+10s.rar/file
http://www.mediafire.com/file/p3zhivru97bdlke/no-verity-opt-encrypt-6.1.zip/file
Since this is not yet official, only proceed if you are competent enough and brave.
(If you need instructions on how to flash, please do not flash this with fastboot method)
Feel free to discuss any bugs or issues and fixes so that everybody can benefit from our findings.
Click to expand...
Click to collapse
I'm sorry but, do you atleast have the permission to share this?
Also, WommyMy should be the guy to upload it, not you.
Edit: thanks for fixing the thread
Also you're missing the device tree.
Hello. As one of the developpers of this TWRP DT, I am not really OK with that.
Firstly, you linked the wrong device tree Real link here
Also, I didn't published this on XDA because this TWRP is still in BETA. And it contains major bugs, like flashing dynamic partitions in fastbootd. Even if bugs will me fixed, I was planning to wait a release candidate before publishing the release here (this will require even more testing, if people want to help us testing, this will be even better).
So please, can you delete this or add clear warnings about the beta state?
Regards, Woomy
@miravision I think we should also add credits to people like @J6idot , @mastersenpai05 and Myst33d who did a great job helping building twrp.
Woomymy said:
@miravision I think we should also add credits to people like @J6idot , @mastersenpai05 and Myst33d who did a great job helping building twrp.
Click to expand...
Click to collapse
Yes, I believe they should get their work credit.
Will be fix soon.. don't too hurry.
mastersenpai05 said:
Will be fix soon.. don't too hurry.
Click to expand...
Click to collapse
Thanks bro
Keeps restarting when i try to flash a custom ROM from xiaomi eu, any Fix please ?
Wow., Hoping for releasing custom roms for our handsets.,keep up the good work devs
Katho536 said:
Keeps restarting when i try to flash a custom ROM from xiaomi eu, any Fix please ?
Click to expand...
Click to collapse
Xiaomi eu has no support for 10s iirc
No support for Mediatek devices on Xiaomi.eu, Global.rom and other
@miravision can u provide the vbmeta.img file?
Original post updated with attached vbmeta.img
langithitam said:
@miravision can u provide the vbmeta.img file?
Click to expand...
Click to collapse
Hi and thanks for sharing
Is it possible just to boot from TWRP recovery via Fastboot without flashing it on the phone?
I have also a Poco X3 NFC with stock MIUI 12.5 with Magisk root, but with stock recovery (so I can do all OTA updates) where I'm doing the same.
When I need it, I just do
fastboot boot TWRP-file.img
Thanks
i have unlocked booloader. i have installed custom recovery pitch black. after that i downloaded custom rom from xda (xtended rom) (evolution x rom) (havoc os rom) miui (12.5 beata rom)
i cleared the folders like dalvik, data,, magisk module, substratum overlays etc
after that i reset data, cache, and dalvik cache
then, format data by writing yes
for evolution x, i chose install option and i select evolution x rom
i slide to the right to start flashing.
after completing mobile stuck into fastboot screen.
none of them worked for me.
for havoc os, i tried the same procedure. this time screen struck on logo redmi (bootloop)
for miui, i tried same procedure and after quarrelling with my mobile, i got success to install it but i had greed so i tried ti nstall evolution x, havoc etc but they get installed but they dont get reboot. either fastboot screen appears or bootloop starts (on-of)
where am i making mistake ?? please help me.
alien2021 said:
i have unlocked booloader. i have installed custom recovery pitch black. after that i downloaded custom rom from xda (xtended rom) (evolution x rom) (havoc os rom) miui (12.5 beata rom)
i cleared the folders like dalvik, data,, magisk module, substratum overlays etc
after that i reset data, cache, and dalvik cache
then, format data by writing yes
for evolution x, i chose install option and i select evolution x rom
i slide to the right to start flashing.
after completing mobile stuck into fastboot screen.
none of them worked for me.
for havoc os, i tried the same procedure. this time screen struck on logo redmi (bootloop)
for miui, i tried same procedure and after quarrelling with my mobile, i got success to install it but i had greed so i tried ti nstall evolution x, havoc etc but they get installed but they dont get reboot. either fastboot screen appears or bootloop starts (on-of)
where am i making mistake ?? please help me.
Click to expand...
Click to collapse
For havoc os, you should flash no oss vendor before havoc rom
I flashed the HavocOS without no oss Vendor on my Redmi 9T and all works perfect. Use no oss vendor only on Poco M3.
FOR JUICE!
1. Reflash the Firmware using MiFlash (From clean all and lock, change it to clean all Only)
2. Boot your device to Fastboot mode and Connect your device again to the PC
3. Download Minimal ADB and Fastboot and Install it, as follow the Instructions.
4. Download the OrangeFOX Recovery, download the Xiaomi.eu Rom, and download your Favourite Custom Rom.
5.Go to the Directory of Minimal ADB and Fastboot ----> C:\Program Files (x86)\Minimal ADB and Fastboot
and paste the recovery.img from the Archive in the Directory of Minimal ADB and Fastboot
6. Launch the Minimal ADB and Fastboot.exe Shotcut from the Desktop and type these commands:
1. Fastboot flash recovery recovery.img
2. If you want to reboot the device Fast type Fastboot reboot
7. Boot the device to the OrangeFOX Recovery, go to the Menu and open the Settings
8. From the Settings select General and uncheck Mount system and vendor read-only
9. Important! To install Successfully the Rom u need first to format the Data, go to Wipe section, select Format Data, type yes and Confirm.
10. Disconnect the Phone, connect it again to the USB and drag the Xiaomi.eu rom zip and the Custom Rom zip to the Phone
11. First u need to Install the Xiaomi.eu Rom zip this is Important!
12. When the flashing of the Xiaomi.eu Rom zip is Complete, u can flash your Favourite Custom Rom
13 Final Step: Format the Data with typing Yes again and Reboot the device, Enjoy!
Atanassoww said:
I flashed the HavocOS without no oss Vendor on my Redmi 9T and all works perfect. Use no oss vendor only on Poco M3.
FOR JUICE!
1. Reflash the Firmware using MiFlash (From clean all and lock, change it to clean all Only)
2. Boot your device to Fastboot mode and Connect your device again to the PC
3. Download Minimal ADB and Fastboot and Install it, as follow the Instructions.
4. Download the OrangeFOX Recovery, download the Xiaomi.eu Rom, and download your Favourite Custom Rom.
5.Go to the Directory of Minimal ADB and Fastboot ----> C:\Program Files (x86)\Minimal ADB and Fastboot
and paste the recovery.img from the Archive in the Directory of Minimal ADB and Fastboot
6. Launch the Minimal ADB and Fastboot.exe Shotcut from the Desktop and type these commands:
1. Fastboot flash recovery recovery.img
2. If you want to reboot the device Fast type Fastboot reboot
7. Boot the device to the OrangeFOX Recovery, go to the Menu and open the Settings
8. From the Settings select General and uncheck Mount system and vendor read-only
9. Important! To install Successfully the Rom u need first to format the Data, go to Wipe section, select Format Data, type yes and Confirm.
10. Disconnect the Phone, connect it again to the USB and drag the Xiaomi.eu rom zip and the Custom Rom zip to the Phone
11. First u need to Install the Xiaomi.eu Rom zip this is Important!
12. When the flashing of the Xiaomi.eu Rom zip is Complete, u can flash your Favourite Custom Rom
13 Final Step: Format the Data with typing Yes again and Reboot the device, Enjoy!
Click to expand...
Click to collapse
Do you get Widevine L1 on havoc os?
Qpb said:
Do you get Widevine L1 on havoc os?
Click to expand...
Click to collapse
Yes don't worry about this. Everything works!
Atanassoww said:
I flashed the HavocOS without no oss Vendor on my Redmi 9T and all works perfect. Use no oss vendor only on Poco M3.
FOR JUICE!
1. Reflash the Firmware using MiFlash (From clean all and lock, change it to clean all Only)
2. Boot your device to Fastboot mode and Connect your device again to the PC
3. Download Minimal ADB and Fastboot and Install it, as follow the Instructions.
4. Download the OrangeFOX Recovery, download the Xiaomi.eu Rom, and download your Favourite Custom Rom.
5.Go to the Directory of Minimal ADB and Fastboot ----> C:\Program Files (x86)\Minimal ADB and Fastboot
and paste the recovery.img from the Archive in the Directory of Minimal ADB and Fastboot
6. Launch the Minimal ADB and Fastboot.exe Shotcut from the Desktop and type these commands:
1. Fastboot flash recovery recovery.img
2. If you want to reboot the device Fast type Fastboot reboot
7. Boot the device to the OrangeFOX Recovery, go to the Menu and open the Settings
8. From the Settings select General and uncheck Mount system and vendor read-only
9. Important! To install Successfully the Rom u need first to format the Data, go to Wipe section, select Format Data, type yes and Confirm.
10. Disconnect the Phone, connect it again to the USB and drag the Xiaomi.eu rom zip and the Custom Rom zip to the Phone
11. First u need to Install the Xiaomi.eu Rom zip this is Important!
12. When the flashing of the Xiaomi.eu Rom zip is Complete, u can flash your Favourite Custom Rom
13 Final Step: Format the Data with typing Yes again and Reboot the device, Enjoy!
Click to expand...
Click to collapse
Which did you flash? Eu stable or weekly beta?
Qpb said:
Which did you flash? Eu stable or weekly beta?
Click to expand...
Click to collapse
There is no EU version of Xiaomi.eu for Redmi 9T. There are only Chinese based, Weekly and Stable with gapps. Blame Xiaomi for that..
Atanassoww said:
There is no EU version of Xiaomi.eu for Redmi 9T. There are only Chinese based, Weekly and Stable with gapps. Blame Xiaomi for that..
Click to expand...
Click to collapse
By EU I mean Xiaomi.eu rom
Qpb said:
By EU I mean Xiaomi.eu rom
Click to expand...
Click to collapse
{
"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"
}
Only Poco M3 have Global
Atanassoww said:
View attachment 5472137
Only Poco M3 have Global
Click to expand...
Click to collapse
Yeah I mean China rom without ads, bloatware, and more languages
Qpb said:
Yeah I mean China rom without ads, bloatware, and more languages
Click to expand...
Click to collapse
Of Course!
{
"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"
}
Notes:
What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive tablet.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for metadata encryption (which causes mounting errors in log)
Downloads:
twrp_3.7.0_12-2_X200XXS1CWA3.tar.md5
twrp_3.7.0_12-2_X200XXS1CWA3.img
Change Log:
v3.7.0_12-2 (2023-02-28):
Updated to X200XXS1CWA3 (Android 13) OEM stock kernel (Jan 2023 Update).
v3.7.0_12-1 (2023-01-22):
Updated to X200XXU1CVL5 (Android 13) OEM stock kernel (Dec 2022 Update).
v3.7.0_12-0 (2023-01-01):
Fixed issue with MTP sometimes not starting until state is toggled in the Mount panel.
Switched to TWRP 3.7.0 release built from new AOSP-12.1 branch.
Updated to X200XXS1BVJ1 (Android 12) OEM stock kernel (Oct 2022 Security Update).
v3.7.0_11-1 (2022-10-24):
Adjusted dynamic partition size and removed redundant backup image.
v3.7.0_11-0 (2022-10-09):
Updated to TWRP 3.7.0 release built from AOSP-11 branch.
Updated to X200XXU1BVI6 (Android 12) OEM stock kernel.
v3.6.2_11-1 (2022-09-11):
Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.
v3.6.2_11-0 (2022-09-04):
Initial TWRP 3.6.2 release built from AOSP-11 branch.
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to Recovery
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch the boot.img file. More details on this process are available here. Note that you should just patch the boot.img file and not the whole AP tarball, since this device's bootloader doesn't like the empty vbmeta.img that Magisk will provide.
Source:
android_device_samsung_gta8wifi
Donations:
Your support is always appreciated! Just click here.
Additional Notes:
Ian's Multidisabler script has an issue on this device preventing it from disabling stock recovery auto-restoration. I'm hoping that a fix is forthcoming.
If you root this device with Magisk, be sure to patch only the boot.img file. Patching the AP tarball will generate a blank vbmeta.img, which this device's bootloader doesn't like for some reason.
Works on LTE version sm-x505 ??
Also which is better tab A7 or tab A8 ??
works perfectly. what i did was after rooting with magisk, i downloaded the official twrp app from playstore and downloaded your img to my tab. then i just flashed it from within the app. no issues.
Magendanz said:
Notes:
What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive tablet.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for metadata encryption (which causes mounting errors in log)
MTP doesn't start until you disable and reenable in the Mount panel
Downloads:
twrp_3.6.2_11-0_X200XXU1AVG1.tar.md5
twrp_3.6.2_11-0_X200XXU1AVG1.img
Change Log:
v3.6.2_11-0 (2022-09-04):
Initial TWRP 3.6.2 release built from AOSP-11 branch.
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to Recovery
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch the boot.img file. More details on this process are available here. Note that you should just patch the boot.img file and not the whole AP tarball, since this device's bootloader doesn't like the empty vbmeta.img that Magisk will provide.
Source:
android_device_samsung_gta8wifi
Donations:
Your support is always appreciated! Just click here.
Click to expand...
Click to collapse
I am so delighted to see that there is major development for this device.
This will open the door for future custom ROMs.
Thank you Magendanz for your effort in bringing this to us.
I can say that is working as expected, thank you so much man. I thought that with TWRP we could be able to install a GSI ROM at least, but nothing at all lol
Tony Ronaldo Matute said:
I can say that is working as expected, thank you so much man. I thought that with TWRP we could be able to install a GSI ROM at least, but nothing at all lol
Click to expand...
Click to collapse
I think it's possible, but just using ChonDow_Flasher didn't work for me...I suspect because the bootloader isn't seeing an AVB hash footer on the GSI image. I had a similar experience when I built TWRP without the hash footer.
Unfortunately, I'm getting a segmentation error when trying to add a hash footer to the GSI using avbtool. It's probably a partition size issue, but I haven't had the time to troubleshoot.
Magendanz said:
I think it's possible, but just using ChonDow_Flasher didn't work for me...I suspect because the bootloader isn't seeing an AVB hash footer on the GSI image. I had a similar experience when I built TWRP without the hash footer.
Unfortunately, I'm getting a segmentation error when trying to add a hash footer to the GSI using avbtool. It's probably a partition size issue, but I haven't had the time to troubleshoot.
Click to expand...
Click to collapse
I had tried different ways also but I give up, the only thing that I can think now is try to use the "reboot to bootloader" feature in TWRP. But well, this processor is going me crazy.
Magendanz said:
Reserved
Click to expand...
Click to collapse
Once we get TWRP can't we just flash Magisk's zip file within TWRP like normally we do?
Also, after restart the tablet, when I tried to get back into TWRP it took me back to Android regular recovery. I had to flash TWRP again using Odin, after enabling MTP, local storage doesn't mount, I wasn't able to copy data in it.
zfk110 said:
Once we get TWRP can't we just flash Magisk's zip file within TWRP like normally we do?
Also, after restart the tablet, when I tried to get back into TWRP it took me back to Android regular recovery. I had to flash TWRP again using Odin, after enabling MTP, local storage doesn't mount, I wasn't able to copy data in it.
Click to expand...
Click to collapse
No, you should patch the boot.img using the Magisk app, then flash it using TWRP or pack in a tarball and use Odin. Don't patch the whole AP, as Magisk will substitute a blank vbmeta.img that the bootloader on this device doesn't like.
Rularick5 said:
works perfectly. what i did was after rooting with magisk, i downloaded the official twrp app from playstore and downloaded your img to my tab. then i just flashed it from within the app. no issues.
Click to expand...
Click to collapse
Was just going to try this method but I'm on AVC1...I'm assuming I need to be on AVG1?
As long as the binary number is the same, im assuming dont quote me, you should be able to flash avg1 then magisk then twrp. Just update to the latest firmware.
I figured that's what I had to do but was trying to avoid that....just rooted a week ago and had no idea about AVG1.
So if I want to upgrade to AVG1 or any other firmware in the future I have to do the whole process again of patching boot.img, flashing through Odin, factory reset and setting up everything again? There's no way to upgrade and retain root?
Not unless you can recieve ota while rooted.
New release is posted...
Downloads:
twrp_3.6.2_11-1_X200XXU1AVG1.tar.md5
twrp_3.6.2_11-1_X200XXU1AVG1.img
Change Log:
v3.6.2_11-1 (2022-09-11):
Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.
Magendanz said:
New release is posted...
Downloads:
twrp_3.6.2_11-1_X200XXU1AVG1.tar.md5
twrp_3.6.2_11-1_X200XXU1AVG1.img
Change Log:
v3.6.2_11-1 (2022-09-11):
Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.
Click to expand...
Click to collapse
Any news for GSI?
Tony Ronaldo Matute said:
Any news for GSI?
Click to expand...
Click to collapse
I successfully tested fastbootd with OEM images, but the LineageOS GSI I tried was still getting kernel panics. I assume it has to do with this bootloader's AVB 2.0 requirements, which we can't seem to work around in the usual way with a blank vbmeta.img.
Magendanz said:
I successfully tested fastbootd with OEM images, but the LineageOS GSI I tried was still getting kernel panics. I assume it has to do with this bootloader's AVB 2.0 requirements, which we can't seem to work around in the usual way with a blank vbmeta.img.
Click to expand...
Click to collapse
"OEM images", so the Google GSI? Also, maybe could the vb meta zip disabler works?
Tony Ronaldo Matute said:
"OEM images", so the Google GSI? Also, maybe could the vb meta zip disabler works?
Click to expand...
Click to collapse
No, the OEM for this device is Samsung. Please provide a link for this vbmeta disabler, since I've just been using the ones generated by Magisk and my own using avbtool make_vbmeta_image --out vbmeta.img.
Magendanz said:
No, the OEM for this device is Samsung. Please provide a link for this vbmeta disabler, since I've just been using the ones generated by Magisk and my own using avbtool make_vbmeta_image --out vbmeta.img.
Click to expand...
Click to collapse
So, first you can try this disabler:
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
as well, you can try to use this fastbootd command:
[Solved] VBmeta Flashing and Disable Verity Verification Command Problem
Thought to share with you guys, as many of people like me face problem while disabling the verification while flashing VBMETA.img. Most of the time the below command does not work and causes bootloop, when Installing Custom recovery. So i...
forum.xda-developers.com
{
"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"
}
PixelExtended ROM for Oneplus8T [kebab]
What is this?
PixelExtended ROM (or PEX for short), We are Combining Pixel Goodies with some essential features you were missing in Pixel Experience, delivering a ROM that promise you stabilty and being feature-rich at the same time . TBH this ROM will keep it's Pixel' idea intact and won't be bloat with unwanted features .
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 13 (T)
FeaturesEverything You've Always Wished For With Pixel Experience> OOS (Oxygen OS) Styled Traffic Indicators
> VoLTE Icon Customization
> Smart Charging
> Adaptive Media Playback
> Notification Counter/Logs
> G-Visual Mod
> FOD (Fingerprint On Display) Customizations
> Status Bar Customizations
> Volume Panel Customizations
> LS (Lock Screen) Clock
> Switch Styles
> Tinted QS (Quick Settings) Tiles
> App Lock with Face Unlock
> QS Customizations
> Gesture Customizations
> New Accents/Fonts/Primary Colors
Whats working?
All
First Time Install / Clean Flash
1. Be on the OOS13 (F13 or F15, F62)
2. Download copy_partitions, vbmeta, dtbo, recovery, and rom for your device from here
3. Reboot to bootloader
4.fastboot flash vbmeta vbmeta.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot reboot recovery
5. While in recovery, navigate to Apply update -> Apply from ADB
6. adb sideload copy_partitions.zip (press "yes" when signature verification fails) and then reboot to recovery
7. Repeat step 5 and adb sideload rom.zip (replace "rom" with actual filename)
8. Format data, reboot to recovery
Update
1. Reboot to bootloader
2. While in recovery, navigate to Apply update -> Apply from ADB
3. adb sideload rom.zip (replace "rom" with actual filename)
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from Mega
Android OS version: 13.0_r43
Security patch level: May 2023
Build author/Device Maintainer: bojantanasic
Source code: https://github.com/PixelExtended
Prebuilt kernel:
GitHub - bojantanasic/android_kernel_oneplus_sm8250: Android 13 kernel for oneplus 8T
Android 13 kernel for oneplus 8T. Contribute to bojantanasic/android_kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
PixelExtended Developer: Aryan Gupta
Changes 23.05.2023.
-brightnes fix
-fix for theme and fonts
-switch to erofs (now system is fluid like butter)
-add App lock (Settings/Security/More security/App lock)
Kernel
- update kernel to v4.19.283
Includes OOS Cam?
kuto232 said:
Includes OOS Cam?
Click to expand...
Click to collapse
OOS cam not include in rom, you can use LMC8.4 for better result then OOS cam.
Hasli: LMC8.4_R13
Download LMC8.4_R13 by Hasli.
www.celsoazevedo.com
and use config for better result.
Thank you for the ROM.
I would like to ask if anybody knows - does dual SIM work on this ROM (specifically enabling and disabling certain SIMs on the fly)? I know Lineage has issues with that along with auto brightness (jumps from low brightness to too bright with no in between) on KB2005.
netusername said:
Thank you for the ROM.
I would like to ask if anybody knows - does dual SIM work on this ROM (specifically enabling and disabling certain SIMs on the fly)? I know Lineage has issues with that along with auto brightness (jumps from low brightness to too bright with no in between) on KB2005.
Click to expand...
Click to collapse
Brightness working just fine,as you can see in screenshot.I don't have second sim card to test, but I think that is fine too.
Can't download the vbmeta and copy partition files from the link you provided.
silverhazesupreme said:
Can't download the vbmeta and copy partition files from the link you provided.
Click to expand...
Click to collapse
Sourceforge delete files from server, very strange. I will upload on mega today.
For install temporary use this files
recovery:
https://mirrorbits.lineageos.org/recovery/kebab/20230119/lineage-20.0-20230119-recovery-kebab.img
vbmeta:
https://mirror.math.princeton.edu/pub/lineageos/full/kebab/20230119/vbmeta.img
copy_partitions:
https://mirrorbits.lineageos.org/tools/copy-partitions-20220613-signed.zip
Thanks LineageOs team for files
Sourceforge has problem with files today!
Good as a daily driver? No stuttering, just fluid?
Goat24K said:
Good as a daily driver? No stuttering, just fluid?
Click to expand...
Click to collapse
Here is small video how fluid is rom, no stuttering. Kernel is great in turns of battery and performance.
Kernel is Illusionx with small performance upgrade by me.Thanks Blaster4385 for kernel.
Video
Streamable Video
Watch this video on Streamable.
streamable.com
Does USB-C video out work? I haven't run a customer rom in a while and I specifically want to install one that has video out working. I can't recall if it was a pixel experience rom or not the last time I had it working.
bookofjoshua said:
Does USB-C video out work? I haven't run a customer rom in a while and I specifically want to install one that has video out working. I can't recall if it was a pixel experience rom or not the last time I had it working.
Click to expand...
Click to collapse
I don't have adapter to test, if you are on OOS13 and if it is working and if this is essential for you than is better to stay on OOS13. If I find cable I will test.
bojantanasic said:
I don't have adapter to test, if you are on OOS13 and if it is working and if this is essential for you than is better to stay on OOS13. If I find cable I will test.
Click to expand...
Click to collapse
Thanks for the reply. I am not, I have a KB2007 and there isn't a OOS13 available (yet, as far as I know). I can just load it and see I guess.
bookofjoshua said:
Thanks for the reply. I am not, I have a KB2007 and there isn't a OOS13 available (yet, as far as I know). I can just load it and see I guess.
Click to expand...
Click to collapse
This rom is for F13 or F15 firmware, if you are on Android 12 then this rom is not for you, because touch wil not work.
I was upgrading from clean OOS13 F15 and when sideloading the ROM, I've got:
Error applying update: 63 (ErrorCode::kPostInstallMountError)
ERROR: recovery: Error in /sideload/package.zip (status 1)
Full logs here: https://gist.github.com/ivirtex/3a1c8fc464050e0310c37c795346aaae
ivirtex said:
I was upgrading from clean OOS13 F15 and when sideloading the ROM, I've got:
Error applying update: 63 (ErrorCode::kPostInstallMountError)
ERROR: recovery: Error in /sideload/package.zip (status 1)
Full logs here: https://gist.github.com/ivirtex/3a1c8fc464050e0310c37c795346aaae
Click to expand...
Click to collapse
You need to update the recovery through the bootloader before you can flash the Rom.You on Los recovery now?
bojantanasic said:
You need to update the recovery through the bootloader before you can flash the Rom.You on Los recovery now?
Click to expand...
Click to collapse
Yes, I flashed provided lineage-20.0-20230119-recovery-kebab
ivirtex said:
Yes, I flashed provided lineage-20.0-20230119-recovery-kebab
Click to expand...
Click to collapse
Did you format data?
And did you copy partition?
You mast format data and after that copy partition.
And after that adb sidload rom.zip.
I just update mega directory with pixelextended recovery, try to install and then tray to install rom.
Sorry if install instructions not clear
Did you install dtbo.img, if not that is problem.
Here is install instruction
Flashing additional partitions
warning
Warning: This platform requires additional partitions to be flashed for recovery to work properly, the process to do so is described below.
Download the following files from the directory named with the latest date here.
dtbo.img
vbmeta.img
Power off the device, and boot it into bootloader mode:
With the device powered off, hold Volume Up + Volume Down + Power.
Flash the downloaded image files to your device by typing (replace <...> with the actual filenames!):
fastboot flash dtbo <dtbo>.img
fastboot flash vbmeta <vbmeta>.img
bojantanasic said:
Did you format data?
And did you copy partition?
You mast format data and after that copy partition.
And after that adb sidload rom.zip.
I just update mega directory with pixelextended recovery, try to install and then tray to install rom.
Sorry if install instructions not clear
Did you install dtbo.img, if not that is problem.
Here is install instruction
Flashing additional partitions
warning
Warning: This platform requires additional partitions to be flashed for recovery to work properly, the process to do so is described below.
Download the following files from the directory named with the latest date here.
dtbo.img
vbmeta.img
Power off the device, and boot it into bootloader mode:
With the device powered off, hold Volume Up + Volume Down + Power.
Flash the downloaded image files to your device by typing (replace <...> with the actual filenames!):
fastboot flash dtbo <dtbo>.img
fastboot flash vbmeta <vbmeta>.img
Click to expand...
Click to collapse
Thanks, flashing dtbo.img allowed me to install the ROM and everything seems to work fine, please update your instructions, so others won't have this problem.
New build are up
Happy flashing
Decent but the sound externally is awful. Very low and static-like. I usually have to turn it down, but i had to turn this ll the way up and i barely heard the song. *sigh* any suggestions? It's the same with the ring tones, they're VERY low.. what is going on here?