[10] [GSI] crDroid [ARM64-A/AB] [Experimental] - Treble-Enabled Device Development A/AB ROMS

[10] [GSI] crDroid [ARM64-A/AB] [Experimental] - Treble-Enabled Device Development A/AB ROMS

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
Disclaimer: I am not responsible for any damage you made to your device.
You have been warned!
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today.
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Screenshots:
https://crdroid.net
Note: some specific features maybe be missing due to the generic nature of GSIs.
Flashing Instructions:
Pre-installation:
Open bootloader
SHRP, OrangeFox or TWRP working recovery
Gapps: Download from here
Magisk 20.3 or newer for root (after first boot): Download from here - More info
First time installation:
The basic steps for flashing a GSI are:
1. Download the GSI file and uncompress the .7z archive
2. Uninstall Magisk if it was previously installed, by using its uninstaller and reboot the phone
3. Wipe Data, Dalvik, and Cache partitions
4. Flash the GSI to system partition, GApps, and maybe specific files for your phone (see post 2)
5. Boot and perform a minimal setup (enabling USB Debugging as a suggestion)
6. Reboot into recovery and flash Magisk
7. Reboot and enjoy!
There is more detailed information on GSI and how to flash it on phhusson’s wiki and in his thread here on xda. Also vince31fr brings useful info and workarounds.
Update installation:
1. Download the GSI file and uncompress the .7z archive to get the .img file
2. (Optional) Uninstall Magisk if it was previously installed, by using its uninstaller and reboot the phone
3. Wipe Dalvik and Cache partitions
4. Flash the GSI (.img file) to system partition, GApps, and maybe specific files for your phone (see post 2)
5. Boot and perform a minimal setup (enabling USB Debugging as a suggestion)
6. If you uninstall Magisk (step 2), reboot into recovery and flash Magisk
7. Reboot and enjoy!
Sources:
ROM: https://github.com/crdroidandroid
Patches: https://github.com/phhusson/treble_experimentations/releases
Known issues:
Camera
Download:
ROM: https://androidfilehost.com
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help crDroid Team pay their server costs

Issues and workarounds:
1. Check your phone compatibility with Treble before following these instructions.
2. Generally, smart charging feature (Settings > Battery > Smart Charging) does not work on Treble. You can have the same functionality using Battery Charge Limit app.
3. Can't flash Gapps due to error 70 (insufficient storage space available in System partition)? In TWRP, just go to Wipe menu > Advanced Wipe > check System partition > Partition options > Resize FS. Then flash Gapps again. In other recoveries, the steps are similar.
4. To get Viper4Android working on GSI ROMs, please, thank here or the Magisk modules.
5. For RAW support on cameras: Settings > Phh Treble Settings > Misc features > and select Expose Aux cameras (Qualcomm) if possible.
6. You may need to flash the vbmeta.img file specific for your device (firmware) before you first boot the GSI. Discover your actual slot: check in TWRP reboot options or in fastboot mode: fastboot getvar current-slot. Then run in the same slot you're flashing the GSI image:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
7. If you lose Wi-Fi and/or Bluetooth, you should flash the dtbo.img file specific for your device (firmware). Discover your actual slot: check in TWRP reboot options or in fastboot mode: fastboot getvar current-slot. Then run in the same slot you're flashing the GSI image:
For A/B devices, run:
fastboot flash dtbo_a dtbo.img
or
fastboot flash dtbo_b dtbo.img
For A-only devices, run:
fastboot flash dtbo dtbo.img
8. Additional files as Permissiver v5 and DM-verity, forced encryption, and disc quota disabler must be needed to boot.

Bugs?

vytska69 said:
Bugs?
Click to expand...
Click to collapse
You tell me. I've tested on just one phone.

Does not see the sim card. No 3g / 4g. Redmi Note 8 pro.

Technical said:
You tell me. I've tested on just one phone.
Click to expand...
Click to collapse
Perfect on top of LOS171 base on Moto g7 River xt1962-1 and VZW (CDMA). Great job, thanks

numser said:
Does not see the sim card. No 3g / 4g. Redmi Note 8 pro.
Click to expand...
Click to collapse
Thanks for testing it.
Probably you need to flash dtbo.img that comes with your firmware package in your active slot:
fastboot flash dtbo_a dtbo.img
or
fastboot flash dtbo_b dtbo.img
Please, let me know and I'll update post 2.

HueyT said:
Perfect on top of LOS171 base on Moto g7 River xt1962-1 and VZW (CDMA). Great job, thanks
Click to expand...
Click to collapse
Thank you for testing. Please, let me know if something goes wrong with sensors (the most delicate part of building gsi's imho).

Brightness and auto brightness dont work in Samsung J7 Pro (J730)

Gheartxz2017 said:
Brightness and auto brightness dont work in Samsung J7 Pro (J730)
Click to expand...
Click to collapse
Thank you for testing and reporting. I was expecting this due to failure to apply 0043-Add-samsung-light-2.patch from phh...
Is there any app that can help you by-passing it? Like https://play.google.com/store/apps/details?id=com.vitocassisi.luxlite or https://play.google.com/store/apps/details?id=com.velis.auto.brightness

Technical said:
Thanks for testing it.
Probably you need to flash dtbo.img that comes with your firmware package in your active slot:
fastboot flash dtbo_a dtbo.img
or
fastboot flash dtbo_b dtbo.img
Please, let me know and I'll update post 2.
Click to expand...
Click to collapse
Temporarily CFW. I will definitely check it out. Thank. :good:

Technical said:
Issues and workarounds:
6. On A/B devices, you may need to flash a vbmeta.img file specific for your device before you first boot the GSI.
must be needed to boot.
Click to expand...
Click to collapse
Hello.
how to flash vbmeta.img please ? thanks

skeeter92 said:
Hello.
how to flash vbmeta.img please ? thanks
Click to expand...
Click to collapse
1. Open bootloader and custom recovery are mandatory (see OP).
2. Download the latest (official) firmware for your device. Extract the vbmeta.img file and put into your adb/fastboot folder.
3. Go to fastboot mode and from command line, flash vbmeta.img:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

Technical said:
Thanks for testing it.
Probably you need to flash dtbo.img that comes with your firmware package in your active slot:
fastboot flash dtbo_a dtbo.img
or
fastboot flash dtbo_b dtbo.img
Please, let me know and I'll update post 2.
Click to expand...
Click to collapse
fastboot flash dtbo dtbo.img if so?

perfect and all is well on Moto G7 plus XT-1965-2...... I flashed gsi over stock 10....then flashed permissiver 4, then my device specific Twrp installer..... reboot repaired file system in advanced wipe to add space for gapps no issue... booted canary magisk....

numser said:
fastboot flash dtbo dtbo.img if so?
Click to expand...
Click to collapse
Yeah, if your device is A-only (not A/B partition).

Technical said:
Thank you for testing and reporting. I was expecting this due to failure to apply 0043-Add-samsung-light-2.patch from phh...
Is there any app that can help you by-passing it? Like https://play.google.com/store/apps/details?id=com.vitocassisi.luxlite or https://play.google.com/store/apps/details?id=com.velis.auto.brightness
Click to expand...
Click to collapse
Thanks brightness works fine ..... but now camera and flashlight isn't available in last build

numser said:
fastboot flash dtbo dtbo.img if so?
Click to expand...
Click to collapse
I think so.

May i know for samsung note10 plus the vbmeta.img is flash on which partition?? Tks

orbital_71 said:
May i know for samsung note10 plus the vbmeta.img is flash on which partition?? Tks
Click to expand...
Click to collapse
The same partition you're flashing the GSI (system.img). You can check in TWRP which is the actual slot you're using.
Also in bootloader, you can run:
fastboot getvar current-slot

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.

[10] [GSI] MSM-Xtended [ARM64-A/AB] [Experimental]

{
"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:
We're not responsible for bricked devices, dead SD cards, thermonuclear war,
or you get 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 blame me in any way for what happens to your device, I will laugh at you.
BOOM! goes the dynamite
Oh… Really I need to introduce them! .
Team "MSM Xtended" is here with new era of Android.
They have tried their best to blend it with all available options, features and stability of different ROMs in to one for better user experience.
Here
MSM Team
If you like their work you can buy them a cup of coffee:
SuperDroidBond
MSM-Xtended Website
MSM-Xtended Blog
ROM Download
Gapps Download
Magisk Download
For better user experience, it's recommended to flash Nano Gapps only.
Clean Flash
The basic steps for flashing a GSI are:
1. Download the GSI file and uncompress the .7z archive
2. Uninstall Magisk if it was previously installed, by using its uninstaller and reboot the phone
3. Wipe Data, Dalvik, and Cache partitions
4. Flash the GSI to system partition, GApps, and maybe specific files for your phone (see post 2)
5. Boot and perform a minimal setup (enabling USB Debugging as a suggestion)
6. Reboot into recovery and flash Magisk
7. Reboot to system and #GetXtended.
There is more detailed information on GSI and how to flash it on phhusson’s wiki and in his thread here on xda. Also vince31fr brings useful info and workarounds.
Dirty Flash
1. Download the GSI file and uncompress the .7z archive to get the .img file
2. (Optional) Uninstall Magisk if it was previously installed, by using its uninstaller and reboot the phone
3. Wipe Dalvik and Cache partitions
4. Flash the GSI (.img file) to system partition, GApps, and maybe specific files for your phone (see post 2)
5. Boot and perform a minimal setup (enabling USB Debugging as a suggestion)
6. If you uninstall Magisk (step 2), reboot into recovery and flash Magisk
7. Reboot to system and #GetXtended.
If you fail to follow these instructions, please don't bother reporting any bugs
If you use Xposed, please don't bother reporting any bugs
MSM-Xtended Sources
We would like to give thanks to everyone in the Android community, big or small.
That said, we would like to thank all These Teams for their contribution to the Open Source Community.
LineageOS/Cyanogenmod
GZOSP
ColtOS Team & Specially @Rakesh.Batra
OmniROM
Nitrogen OS
AICP
crDroid
DirtyUnicorns
Screwd AOSP
CypherOS
Liquid Remix
Benzo ROM
BootLeggers ROM
AOSP Extended ROM
Syberia-Project
PixelDust Project
Pixel Experience
Contributors: Technical
ROM OS Version: Android 10
Created: 2020-06-21

Thanks

Gheartxz2017 said:
Thanks
Click to expand...
Click to collapse
If it works, please, give me feedback

Hi, is based in phh v220?

Os_Herdz said:
Hi, is based in phh v220?
Click to expand...
Click to collapse
It has all the latest phh patches that I manage to apply without breaking the gsi. Shortly, yes.

Technical said:
If it works, please, give me feedback
Click to expand...
Click to collapse
Only stay in bootanimation I flash permissiver but doesn't work

Not boot[emoji24]
Gửi từ SM-G610F của tôi bằng cách sử dụng Tapatalk

Thanks for the feedback. I'll need to figure out what happened. It will take a while

No build with gapps installed?

Technical said:
It has all the latest phh patches that I manage to apply without breaking the gsi. Shortly, yes.
Click to expand...
Click to collapse
Bootloop in bootanimation, tried enforce, tried permissive and with magisk but no booted. The bootanimation is really good.

Stucks at bootanimation ! Waiting a boot fix ! I love Xtended ROM.

muhamet said:
No build with gapps installed?
Click to expand...
Click to collapse
Probably not, it takes a lot of space and time to build (compared to vanilla versions). I have limited resources and it's being very challenging even to boot Gapps are not the focus right now.

Technical said:
Probably not, it takes a lot of space and time to build (compared to vanilla versions). I have limited resources and it's being very challenging even to boot Gapps are not the focus right now.
Click to expand...
Click to collapse
Do you find a solution to boot please ?

Dan225 said:
Do you find a solution to boot please ?
Click to expand...
Click to collapse
Not yet. Trying not to give up

Technical said:
Not yet. Trying not to give up
Click to expand...
Click to collapse
No solutions?

Technical said:
Not yet. Trying not to give up
Click to expand...
Click to collapse
Hi got my device back from the dead after a long time (nubia z17 8gb128gb )but now the world got android 10 even my device (lineage os 17.1 offical) for me:good:
But i dont have even manage to get a gsi to boot (except android 11 R aosp) can you give me a tip?

Guys, I'm trying to bring back camera to work in crDroid and EvolutionX. Both are booting ok.
MSM-Xtended revelead a much more difficult ROM to build. If I find the way to bring back a working camera there, probably it'll be easier to move there. There is no features on MSM that are missing on EvolutionX, for instance.
And I won't have time and resources (disk space) for a 3rd GSI.

On latest Phh build?

Technical said:
MSM-Xtended revelead a much more difficult ROM to build. If I find the way to bring back a working camera there, probably it'll be easier to move there.
Click to expand...
Click to collapse
May be it will help - https://4pda.ru/forum/index.php?showtopic=892755&view=findpost&p=94999066
Quote from next message on 4pda:
Igor~s said:
ROM is built with the settings to increase the system speed and system services optimization.
Click to expand...
Click to collapse

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

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

Development Paranoid Android Topaz Beta 1 - Redmi Note 10

{
"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"
}
We are very excited to announce Paranoid Android Topaz, based on Android 13.
On the first launch, you’ll notice a clean setup with beautiful wallpapers from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhance the overall user experience. You can find all of the Paranoid Android wallpapers and many more in the Abstruct app from the PlayStore.
Our builds are based on the Code Linaro Organization Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features, performance, and stability. We are dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.
Notice
We kindly ask all of you that are in a position to donate anything, to help and support us so we can provide better and faster build releases, as well as increase the download speed of our servers, all looking for your enjoyment.
You can donate on the link below:
Donate
Device-specific issues
* You tell us
Requirements
Make sure you've latest platform tools for Android.
Make sure you've MIUI Global Firmware version V14.0.3.0 flashed before flashing the ROM.
Download
You can always get our builds from our website Paranoid Android website
Note: Custom kernels and Custom recoveries are NOT supported and GMS is included!
Changelogs
Keep an eye on our Twitter account, @paranoidaospa, as we will be posting about new features getting included in the release builds, as well as links to betas for those devices that will get them. For more detailed information please have a look at the second post of this thread of each build changelog on the website.
Instructions (Firmware flashing)
Download recommended firmware zip
Extract it
Boot to bootloader
Open a terminal / command prompt in firmware-update directory and execute the following commands to flash the firmware:
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash imagefv_a imagefv.img
fastboot flash imagefv_b imagefv.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash uefisecapp_a uefisecapp.img
fastboot flash uefisecapp_b uefisecapp.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_config_b xbl_config.img
Instructions (Recovery package)
Boot to bootloader
Download the recovery zip from here and run the following command:
fastboot update recovery-AOSPA-*.zip
Reboot to recovery with the following command:
fastboot reboot recovery
Select Wipe data/factory reset & confirm
Go back and select Apply update from ADB, and execute the following command:
adb sideload aospa-topaz-*.zip
After installation complete, Reboot to system.
Instructions (Fastboot package)
Boot to bootloader
Execute this to flash the ROM:
fastboot update --skip-reboot aospa-topaz-*-image.zip
Reboot to recovery with the following command:
fastboot reboot recovery
Select Wipe data/factory reset & confirm
Go back and reboot system.
Important / Useful links
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Download Channel (Telegram)
Paranoid Android Community (Telegram)
Redmi Note 10 Community (Telegram)
Device Tree
Kernel Tree
Vendor Tree
Cheers and #StayParanoid!

Changelog for Topaz Beta 1:
- Initial beta release.
- Build kernel fully with GCC.
- Utilize most AOSPA components such as adreno, audio, av, bt, charging, display, dsprpcd, gps, init, keymaster, media, overlay, perf, telephony, usb, vibrator, wfd, wlan.
- Drop PowerOffAlarm.apk as our device has issues with the PowerOffAlarm feature.
- Transition to AOSP BT stack.
- Update GPS stack to LA.UM.9.1.r1-12900-SMxxx0.0.
- Upgrade drm to v1.4.
- Drop DisplayFeatures.
- Implement AOSP HBM (Auto-HBM that works via Auto-Brightness).
- Configure overlay for Automated DC-Dimming.
- Configure color modes overlays.
- Fixup padding.
- Fix device MAC Address handling.
- Make AoD enter doze.
- Fix ST2W/DT2W on AoD.
- Bring back CarrierConfig overlay.
- Import WFD stack from LA.UM.9.1.r1-12900-SMxxx0.0 to fix WFD.
- Import cnss-daemon from stock to fix 5GHz detection.
- Drop FM as it is mostly redundant.
- Configure QTI Bservice for optimal memory management.
- Update blobs from MIUI V14.0.3.0.SKGMIXM.
- Cleanup tree.
Kernel:
- Allow setting brightness up to 4095 for AOSP HBM.

Reserved #1

Cool

Yeah! <3

AttentionFor windows user, you could use Platform Tools r31.0.3
It doesn't matter if you would to use r33 tho
You will encounter error : ANDROID_PRODUCT_OUT not set if you use latest version of r34.0.0
Dont forget to use proper Usb Driver for Android Bootloader Interface

Waxaranai said:
Cool
Click to expand...
Click to collapse
Cool

Nice

thank you

Donpablo0271 said:
Attention:
For windows user, you could use Platform Tools r31.0.3
You will encounter some error if you use latest version of r34.0.0
Click to expand...
Click to collapse
I have to flash tomorrow (waiting to unlock the bootloader).
I have platform tools r33.0.1 and r33.0.3
Do I absolutely have to use r31.0.3?

carlos974 said:
I have to flash tomorrow (waiting to unlock the bootloader).
I have platform tools r33.0.1 and r33.0.3
Do I absolutely have to use r31.0.3?
Click to expand...
Click to collapse
No you can use r33. The problem lies with r34.

cyberknight777 said:
No you can use r33. The problem lies with r34.
Click to expand...
Click to collapse
Thank you!
By the way to flash the firmware can I copy paste the commands from OP in cmd (the firmware files will be in the platform-tools directory)

carlos974 said:
Thank you!
By the way to flash the firmware can I copy paste the commands from OP in cmd (the firmware files will be in the platform-tools directory)
Click to expand...
Click to collapse
Yeah sure you can do that

I am sorry for noob questions, but which file should I download from the website? One is name "Recovery Option" and the other is "Fastboot Option". And in the instructions, how am I supposed to replicate the steps mentioned in "Instructions (Firmware flashing)"?

@ciberknight777
I unlocked my redmi note 10 this morning.
I flashed the firmware, the rom.
All went well.
I restarted the rom works fine.
But when the phone goes to sleep, I press the power button to wake it up, the screen appears but I can't unlock by sliding my finger on the unlocked canedas (I didn't put any lock)

WalinAhmed said:
I am sorry for noob questions, but which file should I download from the website? One is name "Recovery Option" and the other is "Fastboot Option". And in the instructions, how am I supposed to replicate the steps mentioned in "Instructions (Firmware flashing)"?
Click to expand...
Click to collapse
The choice is yours, you can choose whether to follow recovery option or fastboot option. Instructions are provided respectively.
As for firmware flashing, do what it says? You obviously need windows/Linux with cmd prompt / linux terminal to do so.

carlos974 said:
@ciberknight777
I unlocked my redmi note 10 this morning.
I flashed the firmware, the rom.
All went well.
I restarted the rom works fine.
But when the phone goes to sleep, I press the power button to wake it up, the screen appears but I can't unlock by sliding my finger on the unlocked canedas (I didn't put any lock)
Click to expand...
Click to collapse
What is "canedas" and I can't reprod this nor have I seen such issues being reported. I'd take it this is probably some rare AOSP meme. If you can reprod, provide logs for it. That said it's highly possible that it isn't device specific so yeah.

cyberknight777 said:
What is "canedas" and I can't reprod this nor have I seen such issues being reported. I'd take it this is probably some rare AOSP meme. If you can reprod, provide logs for it. That said it's highly possible that it isn't device specific so yeah.
Click to expand...
Click to collapse
Typo "padlock"
I changed a year ago already the broken screen by another screen not amoled but TFT

carlos974 said:
Typo "padlock"
I changed a year ago already the broken screen by another screen not amoled but TFT
Click to expand...
Click to collapse
Then it's your screen issue

Better Mobile App

welcome