Develop Bugs

[ROM][Unofficial] Galaxy S9 Starlte and Star2lte crDroid 7.6

{
"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/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
step 1: Unlock BL
step 2: Flash TWRP and format data
step 3 Flash ROM, Gapps and Magisk
step 4 Reboot
step 5 Done
Update installation:
step 1 Flash ROM
step 2 Reboot
Do not wipe anything
Download:
Galaxy S9: Download
Galaxy S9 Plus (UNTESTED): Download
Known issues:
voLTE, Samsung proprietary apps, Screen Mirroring
Visit official website @ crDroid.net
crDroid S9/+/Note 9 Telegram
crDroid Community Telegram
Donate to help our team pay server costs
Credits go to:
The crDroid team: Website Github
Synt4x93: Github @Synt4x.93
Lineage os team: Website Github
Big thanks to DeinMathelehrer for helping me get everything up and running: Github @hisoka_simp

Epic! I'l try this on my star2lte and let you know.

CustomOsLover said:
Epic! I'l try this on my star2lte and let you know.
Click to expand...
Click to collapse
So, I'm waiting for 5 mins now. It doesn't boot for now

Nice it's working, hope you continue to work on custom Roms

CustomOsLover said:
So, I'm waiting for 5 mins now. It doesn't boot for now
Click to expand...
Click to collapse
UPDATE: it's working now. Might had some problems with my GAPPs

CustomOsLover said:
Epic! I'l try this on my star2lte and let you know.
Click to expand...
Click to collapse
Thankyou!

I've been using this for a day now and I gotta admit, it's so smooth and reliable for now, nothing to argue about! I absolutely love this rom! Thanks for creating this for the S9(+) Hope we'll get more ROMs like this

CustomOsLover said:
I've been using this for a day now and I gotta admit, it's so smooth and reliable for now, nothing to argue about! I absolutely love this rom! Thanks for creating this for the S9(+) Hope we'll get more ROMs like this
Click to expand...
Click to collapse
Perfect thank you so much. I am glad it works. I need a screenshot of it working though to get the dev's approval. His rules not mine. So just dm me a screenshot in xda of it working please, so I can get it validated. (Screenshot of About Phone > Android Version in settings would be best)
Also a word of warning, I may be unable to create a rom for crdroid S (android 12), as I have no idea how to make rom sources. I just know how to compile roms with preexisting sources. So unless someone builds android 12 lineage os or something for the s9 and s9 plus, then the road may end here for this rom unless someone else picks it up.

hisoka_simp said:
Nice it's working, hope you continue to work on custom Roms
Click to expand...
Click to collapse
Thanks for ur help. I might, but I also have a lot of other things to do.

CustomOsLover said:
UPDATE: it's working now. Might had some problems with my GAPPs
Click to expand...
Click to collapse
Yah, sry I don't use gapps, I try to avoid them as much as possible. So I didnt test that.

Linusrg1 said:
Perfect thank you so much. I am glad it works. I need a screenshot of it working though to get the dev's approval. His rules not mine. So just dm me a screenshot in xda of it working please, so I can get it validated. (Screenshot of About Phone > Android Version in settings would be best)
Also a word of warning, I may be unable to create a rom for crdroid S (android 12), as I have no idea how to make rom sources. I just know how to compile roms with preexisting sources. So unless someone builds android 12 lineage os or something for the s9 and s9 plus, then the road may end here for this rom unless someone else picks it up.
Click to expand...
Click to collapse
Here you go:

CustomOsLover said:
Here you go:View attachment 5312933
Click to expand...
Click to collapse
thankyou

@Linusrg1 I'm currently on crDroid 7.2, on the S9; can I update to 7.6 just by flashing the rom through twrp? Will that create any side effects maybe? Like losing data and such? I cba to make a backup as it's very high in size.

kidi said:
@Linusrg1 I'm currently on crDroid 7.2, on the S9; can I update to 7.6 just by flashing the rom through twrp? Will that create any side effects maybe? Like losing data and such? I cba to make a backup as it's very high in size.
Click to expand...
Click to collapse
Thats what I did and it worked fine. If not make a data backup then start off clean.

Linusrg1 said:
Thats what I did and it worked fine. If not make a data backup then start off clean.
Click to expand...
Click to collapse
I mean you sure it won't mess up with magisk manager and tasker? Since I'm just flashing the rom itself and not re-rooting?
EDIT: I've lost root, and it messed up with google apps, as in they were force closing. I've patched the boot.img for magisk to work again as in to re-gain root, and flashed google apps .zip, it seems ok for now. Also it seems it takes a second for the animation to pass through and to be able to enter the pin code on the lock screen after swiping, why's that?

kidi said:
I mean you sure it won't mess up with magisk manager and tasker? Since I'm just flashing the rom itself and not re-rooting?
EDIT: I've lost root, and it messed up with google apps, as in they were force closing. I've patched the boot.img for magisk to work again as in to re-gain root, and flashed google apps .zip, it seems ok for now. Also it seems it takes a second for the animation to pass through and to be able to enter the pin code on the lock screen after swiping, why's that?
Click to expand...
Click to collapse
Because you need to wipe system data cache and dalvik cache flash the rom and then flash data again.

Linusrg1 said:
Because you need to wipe system data cache and dalvik cache flash the rom and then flash data again.
Click to expand...
Click to collapse
It's all okay now, except I found the culprit to the 1-second delay for the animation to step in to enter the pin; when you set up face unlock, that bug appears. When you don't use face unlock but just pin/fingerprint combo, it doesn't have that delay when you swipe on the lock screen to enter pin.

I have the SM-960F/DS version of starlte, which I believe has the Exynos chipset, while the American version has the SnapDragon. Does anyone know if this ROM will have any issues on the SM-960F/DS or does the chipset not matter for the ROM?

DangerousDays said:
I have the SM-960F/DS version of starlte, which I believe has the Exynos chipset, while the American version has the SnapDragon. Does anyone know if this ROM will have any issues on the SM-960F/DS or does the chipset not matter for the ROM?
Click to expand...
Click to collapse
well, for starters, Snapdragon models mostly can't unlock the bootloader. But yes, the exynos models with the latest bootloader (you can install dev base first and then flash this, if you're uncertain) should run this with no problem.

lordsolrac2 said:
well, for starters, Snapdragon models mostly can't unlock the bootloader. But yes, the exynos models with the latest bootloader (you can install dev base first and then flash this, if you're uncertain) should run this with no problem.
Click to expand...
Click to collapse
Sorry, I am somewhat new to the custom ROM scene. Can you explain to me how to check if I have the latest bootloader, what is the dev base and where I can get it?

ANDROID 12L ROM ❯ 02 May 2022 ❯ ProtonAOSP 12.3.1

{
"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"
}
ProtonAOSP​Android 12 ROM for Pixel 2 - Maintained by @EnesSastim​
Spoiler: SPECIAL THANKS TO
@Lunarixus on XDA (using his device tree, mentorship, and fixes. Wonderful work)
@RealOkabe on XDA for his build process, we only reached bootable state thanks to his work.
@ReallySnow on XDA for his work on Android 12 vendor. I consider him my teacher, and most of the Android 12 heavy lifting was done by him.
None of this would've happened without them.
ProtonAOSP is a minimal Android fork (custom ROM) focused on UI/UX and performance, with a touch of privacy.
Screenshots are attached.
​
What's not working: ​
You tell me... post logcats using my tool in this thread or you may get support in Telegram: Pixel Development & Pixel 2 chat​
Click to expand...
Click to collapse
Download
Download from here: Source Forge
This does not include OTAs, so you will have to visit regularly for security updates and the like.
Installation
This ROM is currently distributed as OTA zips. Flash it the same way you would, in a custom recovery. Don't forget to wipe all data using "fastboot -w" or using my tool before booting the ROM.
Click to expand...
Click to collapse
Sources
ProtonAOSP: Github & build guide
Walleye: Github
Wahoo: Github
Vendor: Github
Kernel: Github
Click to expand...
Click to collapse

reserved ig

Excellent omw to flash now brb

XS37 said:
Excellent omw to flash now brb
Click to expand...
Click to collapse
i beg, let me know how it goes

just finishing backup downloads done fingers crossed no probs <3

recieve a bootloader error bootlinux failed:bad buffer size
Edit: and rebooting changes slot and gives slot unbootable error tried a
reflash aswell unsure
caught the first bit of the log before it scrolled but it seems to flash fine with no problems but gives bad buffer on first boot

XS37 said:
recieve a bootloader error bootlinux failed:bad buffer size
Edit: and rebooting changes slot and gives slot unbootable error tried a
reflash aswell unsure
caught the first bit of the log before it scrolled but it seems to flash fine with no problems but gives bad buffer on first boot
Click to expand...
Click to collapse
i also got this issue

Edited the thread with new build, try

Dollscythe said:
Edited the thread with new build, try
Click to expand...
Click to collapse
This build still fails for me with the same messages as XS37 above

aw... working on it. i dont have a walleye so its hard to test, so doesnt @RealOkabe (person building the rom)

Dollscythe said:
aw... working on it. i dont have a walleye so its hard to test, so doesnt @RealOkabe (person building the rom)
Click to expand...
Click to collapse
well with donations and support we shall work on getting one for you hopefully both the xl and non for support

XS37 said:
well with donations and support we shall work on getting one for you hopefully both the xl and non for support
Click to expand...
Click to collapse
How much is a used Pixel 2 in your area? Here in Australia they’re going for ~120 AUD & I’d definitely be willing to support you guys

notsidney said:
How much is a used Pixel 2 in your area? Here in Australia they’re going for ~120 AUD & I’d definitely be willing to support you guys
Click to expand...
Click to collapse
I'm in AUS. How can we do it!!!

Any news about this rom on walleye?
Thank you!!

Yes waiting for the walleye support

Hello, many thanks for this works, unfortunatly i missed the link.
2 questions, can you send me link to donate for the walleye developpement of this proton aosp unofficial rom ?
Also, is this would work with locked bootloader ? or does not making sens with the configuration of vendor from 11 etc...
Also if u have another test build could you provide it.
Thanks.

elggpxl said:
Hello, many thanks for this works, unfortunatly i missed the link.
2 questions, can you send me link to donate for the walleye developpement of this proton aosp unofficial rom ?
Also, is this would work with locked bootloader ? or does not making sens with the configuration of vendor from 11 etc...
Also if u have another test build could you provide it.
Thanks.
Click to expand...
Click to collapse
Currently the ROM is in in unknown state @Dollscythe is trying their best to fix it so no links are currently available as the ROM wasn't currently usable and and no nothing is flashable if your bootloader is locked for anything to be flashable your bootloader must be able to be unlocked or set in unlocked mode otherwise the device is unflashable and to donate to them its PayPal and the link

XS37 said:
Currently the ROM is in in unknown state @Dollscythe is trying their best to fix it so no links are currently available as the ROM wasn't currently usable and and no nothing is flashable if your bootloader is locked for anything to be flashable your bootloader must be able to be unlocked or set in unlocked mode otherwise the device is unflashable and to donate to them its PayPal and the link
Click to expand...
Click to collapse
Ok thanks, i was talking about re-locking feature, iam new as forum member but its years now that iam flashing on several devices.

elggpxl said:
Ok thanks, i was talking about re-locking feature, iam new as forum member but its years now that iam flashing on several devices.
Click to expand...
Click to collapse
I wouldn't recommend re-locking it but I know on the original you could but I would wait until @Dollscythe finishes up if they get the chance as things happen and they are supporting a phone they don't have so time is needed give them a few days hopefully they get a chance and they can answer better then I can as they are building it

XS37 said:
I wouldn't recommend re-locking it but I know on the original you could but I would wait until @Dollscythe finishes up if they get the chance as things happen and they are supporting a phone they don't have so time is needed give them a few days hopefully they get a chance and they can answer better then I can as they are building it
Click to expand...
Click to collapse
Ok many thanks, no rush at all really, this would be perfect to have at least one stable build with this feature and the classics proton aosp options (more option on the permission manager, the press squeeze, and other things). after all (to me) all will be good.

Development [ROM][Android 12L][UNOFFICIAL][OTA] LineageOS 19.1 for Redmi Note 9 5G and Redmi Note 9T

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 12.1 (S), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Downloads:
- Here
Flashing instructions
- Here
Bugs:
- Backlight does not turn off on offline charging
Notes:
- SELinux is enforcing
- SafetyNet passes by default
- Custom recoveries, like TWRP and OFRP, are not supported
- Custom kernels, like Eva Kernel, are not supported
- OTA support is present
- Kernel is prebuilt from stock since Xiaomi has not released the source code for cannon-s-oss (Taken from cannong 13.0.3.0)
Required firmware:
- MIUI 13 based (Up to MIUI 13.0.3.0. MIUI 12.x is not supported)
Sources:
- LineageOS
- Device sources
Telegram group:
- Here
Happy modding!

Reserved

Thank you for awesome work!

tried this, sim card stopped working

jokemaster21 said:
tried this, sim card stopped working
Click to expand...
Click to collapse
Send logs and check the reporting issues section of the guide
Also make sure you're doing everything properly, as I describe, since I haven't seen anything similar myself or in some other tester.

LinkBoi said:
Send logs and check the reporting issues section of the guide...
Also make sure you're doing everything properly, as I describe, since I haven't seen anything similar myself or in some other tester.
Click to expand...
Click to collapse
where do I find my logs
edit nvm I'll report the problem properly according to your guide

LinkBoi said:
Send logs and check the reporting issues section of the guide...
Also make sure you're doing everything properly, as I describe, since I haven't seen anything similar myself or in some other tester.
Click to expand...
Click to collapse
here are the logs
Edit also it keeps bootlooping when I insert an sd card

jokemaster21 said:
here are the logs
Edit also it keeps bootlooping when I insert an sd card
Click to expand...
Click to collapse
See below:

LinkBoi said:
Okay. Try one thing first. Flash from recovery the package that I've attached, it will make your SELinux be permissive.
PS: Consider joining Telegram for more direct communication
Click to expand...
Click to collapse
Also I will need boot logs just to be sure. You can get them by rebooting your device and when you see the bootanimation do the following:
- adb root
- adb shell
- logcat -b all > /cache/logcat-boot.log
Wait a little while and press control+C to stop the process
Afterwards, send me the file from the /cache partition. You can reboot to recovery and use 'adb pull' to grab it in your PC like this:
- adb pull /cache/logcat-boot.log

LinkBoi said:
Also I will need boot logs just to be sure. You can get them by rebooting your device and when you see the bootanimation do the following:
- adb root
- adb shell
- logcat -b all > /cache/logcat-boot.log
Wait a little while and press control+C to stop the process
Afterwards, send me the file from the /cache partition. You can reboot to recovery and use 'adb pull' to grab it in your PC like this:
- adb pull /cache/logcat-boot.log
Click to expand...
Click to collapse
here you go,
btw since I don't have a sim card to use atm I can't use telegram

jokemaster21 said:
here you go,
btw since I don't have a sim card to use atm I can't use telegram
Click to expand...
Click to collapse
Which stock MIUI were you using before flashing LineageOS?

LinkBoi said:
Which stock MIUI were you using before flashing LineageOS?
Click to expand...
Click to collapse
13.0.3.0 I believe. I tried flashing 13.0.2.0, but it kept giving me an error that the SPL would be a downgrade and it wouldn't allow me to flash

jokemaster21 said:
13.0.3.0 I believe. I tried flashing 13.0.2.0, but it kept giving me an error that the SPL would be a downgrade and it wouldn't allow me to flash
Click to expand...
Click to collapse
You should flash 13.0.2.0 from fastboot. You need to download the full fastboot ROM for your specific model and then flash it from fastboot by running flash_all.bat or flash_all.sh (Depending on your OS)

LinkBoi said:
You should flash 13.0.2.0 from fastboot. You need to download the full fastboot ROM for your specific model and then flash it from fastboot by running flash_all.bat or flash_all.sh (Depending on your OS)
Click to expand...
Click to collapse
ok tried flashing it and it said it was successful, but when I tried booting it up it got completely bricked

jokemaster21 said:
ok tried flashing it and it said it was successful, but when I tried booting it up it got completely bricked
Click to expand...
Click to collapse
Check a couple of things:
- If your device powers up in any way, see if you can go into fastboot. If your device, on the splash screen says something like 'vbmeta verification failed, press the power button to continue', just press the power button to proceed (this would be due to AVB checks)
- If your device does not power up, then try plugging it in to your computer and see if it gets detected in any way
If it does, send a screenshot of Device Manager (Windows) or 'lsusb' (Linux)
Also, do you have the Global model or the Chinese one? I assume you got the Chinese one since 13.0.3.0 is not out for Global yet.
Either way, your issues before most likely stem from using newer firmware than the one I recommend.
PS: You should already have some technical knowledge to resolve such issues yourself if you're flashing custom ROMs and also keep in mind that 'bricked' says pretty much nothing (You must be more detailed when mentioning your phone's behaviour, like if it boots but stays on the splash screen, if it boots but stays on the boot animation etc)

LinkBoi said:
Check a couple of things:
- If your device powers up in any way, see if you can go into fastboot. If your device, on the splash screen says something like 'vbmeta verification failed, press the power button to continue', just press the power button to proceed (this would be due to AVB checks)
- If your device does not power up, then try plugging it in to your computer and see if it gets detected in any way
If it does, send a screenshot of Device Manager (Windows) or 'lsusb' (Linux)
Also, do you have the Global model or the Chinese one? I assume you got the Chinese one since 13.0.3.0 is not out for Global yet.
Either way, your issues before most likely stem from using newer firmware than the one I recommend.
PS: You should already have some technical knowledge to resolve such issues yourself if you're flashing custom ROMs and also keep in mind that 'bricked' says pretty much nothing (You must be more detailed when mentioning your phone's behaviour, like if it boots but stays on the splash screen, if it boots but stays on the boot animation etc)
Click to expand...
Click to collapse
it doesn't turn on in anyway, when I plug it into my computer it makes the windows sound that it's connected, but shows nothing on the device manager. it's a brick now

jokemaster21 said:
it doesn't turn on in anyway, when I plug it into my computer it makes the windows sound that it's connected, but shows nothing on the device manager. it's a brick now
Click to expand...
Click to collapse
You can recover anything on MTK anyways. Check mtkclient and this link for more info.

New LineageOS 19.1 Update // cannon and cannong // 27.08.22
Download:
- GitHub Releases
Changelog:
- Fixed minimum brightness issue (Thanks to @ganomin for finding out)
Bugs:
- None that I know of
Notes:
- Selinux is enforcing
- SafetyNet passes by default
- Custom recoveries, like TWRP and OFRP are not supported
- Custom kernels, like Eva Kernel, are not supported
- OTA support is present

LinkBoi said:
You can recover anything on MTK anyways. Check mtkclient and this link for more info.
Click to expand...
Click to collapse
no idea how to use this, too technical for me. maybe I could bring it into a repair shop.

How To Guide Unofficial twrp 3.6.0 for Xiaomi 11T (Agate)

{
"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"
}
Twrp 3.6.0 Root Xiaomi 11T (Agate):​unofficial build of twrp 3.6.0 have Now been available for the Xiaomi 11T user Who own Xiaomi 11T can Root it by following the below Instructions. to Install twrp Recovery on Xiaomi 11T first You need to unlock it’s bootloader after that You can Root it by Flashing Magisk 21.4.zip.
Xiaomi 11T Run on Mediatek Dimensity 1200 SoC along with Android 11 8GB of RAM and 128GB of Internal Storage. The device come with 6.6 Inch AMOLED display with the Resolution of 1080 X 2400 Pixels.
Disclaimer:​
Rooting May Void Your device warranty
Make a backup & Move it to Safe Place Like Pen drive or PC.
Make sure Your Phone at-least 50% charge to Prevent accidental shut down during the Rooting Process.
Download Files:​Note:
to make magisk flashable rename Magisk-v23.0.apk to Magisk-v23.0.zip
unlock bootloader using official unlock method or use MTKClient
How to Install twrp Recovery on Xiaomi 11T:​
First Enable developer options. for that Go to Setting>About phone>tap 5-6 times on software version>done. Now Go back /additional settings/ developer options & USB debugging > Turn ON, OEM unlocking > Turn ON.
Download & Install latest adb fastboot driver on your computer
Download & setup platform tools with in your computer.
extract Downloaded recovery.img & vbmeta.img in platform tool folder
switch off Phone, Now press power & volume down key, once you see fastboot logo connect it to computer by using the usb cable
Open command Window in Platform tool folder and send below code to disable AVB by sending below code
fastboot flash vbmeta vbmeta.img
fastboot format userdata
Flash recovery
fastboot flash recovery recovery.img
fastboot boot recovery.img
once done, don’t bootup Phone, directly go to recovery (by holding Volume+ & Power Key) & Flash magisk 23.0.zip & No verity opt encrypt.zip
How to Root Xiaomi 11T:​
Download & Move Magisk 23.0.zip, No_verity_opt_encrypt.zip to device storage.
Reboot Phone to twrp recovery by Pressing volume up and Power button
Make a Nandroid backup
wipe userdata
Flash Magisk 23.0.zip and No_verity _opt_encrypt.ZIP
Reboot system now

You do not specify if it is a version for A11 or A12?

NOSS8 said:
You do not specify if it is a version for A11 or A12?
Click to expand...
Click to collapse
It might be A11, A12 is not available for this vbemta file.

NOw stuck in a bootloop after flashing recovery. Probably a A11/A12 issue? I'm on Miui 13 stable

Nah this happened to me also on a11

I was on Xiaomi 11T MIUI 13.0.9. Tried this "guide" and now stuck in bootloop after flashing recovery.img.
Booting recovery.img errors out as well...
"FAILED (Status read failed (Too many links))"...
Starting to think Xiaomi 11T's are not able to have TWRP. Can't fn find anything online with anyone who has successfully gotten TWRP flashed to 11T AGATE.

This will not work,
I will create a TWRP version/image for this device:
Xiaomi/vnd_agate/agate:12/SP1A.210812.016/V13.0.9.0.SKWEUXM:user/release-keys

GitHub - Allesanddro/xiaomi_agate
Contribute to Allesanddro/xiaomi_agate development by creating an account on GitHub.
github.com
will add images soon
Please look if you would have normally 11 if so I will do this one too
currently compiling

Allesanddro said:
GitHub - Allesanddro/xiaomi_agate
Contribute to Allesanddro/xiaomi_agate development by creating an account on GitHub.
github.com
will add images soon
Please look if you would have normally 11 if so I will do this one too
currently compiling View attachment 5809859
Click to expand...
Click to collapse
When will the thing get uploaded i have linux on my pc and probably could also try to compile

Allesanddro said:
GitHub - Allesanddro/xiaomi_agate
Contribute to Allesanddro/xiaomi_agate development by creating an account on GitHub.
github.com
will add images soon
Please look if you would have normally 11 if so I will do this one too
currently compiling View attachment 5809859
Click to expand...
Click to collapse
i have the amber version of this device but it has the exact same specs and firmware version i just cant find info about it.
Do you think you can make a version compatible with this phone as well?

Allesanddro said:
GitHub - Allesanddro/xiaomi_agate
Contribute to Allesanddro/xiaomi_agate development by creating an account on GitHub.
github.com
will add images soon
Please look if you would have normally 11 if so I will do this one too
currently compiling View attachment 5809859
Click to expand...
Click to collapse
when will it be released to the public, sir ?

Maybe it didn't boot for him and he wasn't able to fix his phone just like me so he threw it into the bin because stupid mediatek closed source it's time to do something about that

Allesanddro said:
GitHub - Allesanddro/xiaomi_agate
Contribute to Allesanddro/xiaomi_agate development by creating an account on GitHub.
github.com
will add images soon
Please look if you would have normally 11 if so I will do this one too
currently compiling View attachment 5809859
Click to expand...
Click to collapse
The current unofficial TWRP only works on Android 11, the dev confirmed this to me.
Do I understand correctly that you are compiling one yourself?
And will this work on Android 13? The Global Beta ROM is already at Android 13...
If it's just Android 12, can you please also do one for Android 13 too?
It's great to have you working on this!!! I've needed TWRP for this device so badly.

Allesanddro said:
This will not work,
I will create a TWRP version/image for this device:
Xiaomi/vnd_agate/agate:12/SP1A.210812.016/V13.0.9.0.SKWEUXM:user/release-keys
Click to expand...
Click to collapse
"V13.0.9.0.SKWEUXM" - this will still work on Global ROM, right?

Hallohannes123 said:
"V13.0.9.0.SKWEUXM" - this will still work on Global ROM, right?
Click to expand...
Click to collapse
Yes until they release miui 14 for this device
downloading the source of his tree since it would take years till he release the twrp

waiting for the release also. thank you for the efffort guys.

aorias said:
waiting for the release also. thank you for the efffort guys.
Click to expand...
Click to collapse
I wasn't able to build because I only know how to build roms but not custom recovery I'll have to try again today
Plus his device tree didn't work properly
Maybe I'll have to make my own tree

Stephanizgo said:
Maybe I'll have to make my own tree
Click to expand...
Click to collapse
How is the progress?

Hallohannes123 said:
How is the progress?
Click to expand...
Click to collapse
Honestly quite bad the TWRP when I try to build says something like this file which is required by that file is missing and there is no rule on how to make it
<Moderator Edit>: Telegram link removed. See Post #5 "WhatsApp/Telegram Groups and Channels - Going Forward"
If anyone wants to help i want some people to join this any help appreciated

Stephanizgo said:
<Moderator Edit>: Telegram link removed. See Post #5 "WhatsApp/Telegram Groups and Channels - Going Forward"
If anyone wants to help i want some people to join this any help appreciated
Click to expand...
Click to collapse
Thats sad to hear. I'll see if I can help, but I dont really know a lot about TWRP

Paranoid Android Topaz 3 - OnePlus 7

{
"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're on fastboot version 33.0.3p2
fastboot version 34.0.0-9570255 **is broken**
Device Firmware: OOS 11
Recovery zips have firmware included
Download
You can always get our builds from our website Paranoid Android website
EDIT: XDA moderation has removed the device specific posts.
OnePlus 7, 7 Pro, 7T and 7T Pro are supported. You can navigate devices with sidebar to the left on the PA website.
Note: Custom kernels are NOT supported unless the kernel says it supports PA.
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.
Paranoid Android Topaz released
Instructions
Fastboot option (OOS 11 FIRMWARE REQUIRED):
1. Download the "FASTBOOT OPTION" from our website.
2. Enter fastboot, while the bootloader is unlocked, and enter:
fastboot update aospa-topaz-3-oneplus7*-DATE-image.zip
Click to expand...
Click to collapse
3. After flashing and rebooting, enter the recovery and factory reset the device
Recovery option:
1. Download the "RECOVERY OPTION" from our website.
2. Extract and flash the "recovery.img" (7T, 7T Pro), or "boot.img" (7, 7 Pro) with payload-dumper
3. Enter recovery, select "Apply update from ADB"
4. On your PC, enter:
adb sideload aospa-topaz-3-oneplus7*-DATE.zip
Click to expand...
Click to collapse
5. Reboot into recovery and factory reset the device
Kernel source.
Important / Useful links
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Download Channel (Telegram)
Paranoid Android Community (Telegram)
Cheers and #StayParanoid!

Thank you so much for this ROM. I want to try out this ROM. Do we have to be on OOS 12 or 11 before flashing this?

Barbiox Dogg said:
Thank you so much for this ROM. I want to try out this ROM. Do we have to be on OOS 12 or 11 before flashing this?
Click to expand...
Click to collapse
Device firmware is included now
Click to expand...
Click to collapse
ROM comes with firmware, you'll be able to flash it regardless of OOS version as long as your bootloader is unlocked.
Thank you for all the effort, Timo. It's all fine for now.

Halacoglu said:
ROM comes with firmware, you'll be able to flash it regardless of OOS version as long as your bootloader is unlocked.
Thank you for all the effort, Timo. It's all fine for now.
Click to expand...
Click to collapse
Ok great. I'm using Evolution X ROM which is based on OOS 12. Do I download the fastboot option then flash?
Does this ROM support Quick Unlock??

Barbiox Dogg said:
Does this ROM support Quick Unlock??
Click to expand...
Click to collapse
If that's unlocking as soon as the correct pin is entered, yes. Disabled on SIM pin however to prevent accidentally getting it blocked

Im on stock OOS12.1 locked , Whats the procedure to flash this custom rom?

unlocked the bootloader but couldn't fastboot flash it . getting FAILED (remote: (system_b) No such partition) issues, some one help

Where can we download fastboot version 33.0.3p2 for windows?

lolorider said:
Where can we download fastboot version 33.0.3p2 for windows?
Click to expand...
Click to collapse
You can get any 33.0.3 version platform tools, They work pretty fine.

Thanks for answer but I don't find any place to download an older version

amazing , thank you so much

lolorider said:
Thanks for answer but I don't find any place to download an older version
Click to expand...
Click to collapse
Modify download address
Change r34.0.0 to r33.0.3

Thanks

Great Job

tsaiajie said:
Modify download address
Change r34.0.0 to r33.0.3
Click to expand...
Click to collapse
What does it means?

Alexoxo said:
What does it means?
Click to expand...
Click to collapse
Hi there,it means that you search on google for 33 version.btw flashed Rom,really really god.installation went without any error.but i'm curious about pitch black theme.does paranoid have that implemented and possibility to hide pillow bar.good job

timo_capa said:
moderation has removed the device specific
Click to expand...
Click to collapse
Hi timo first of all thank you for this amazing rom i want to know about the nfc toggle tile i cant find it is this normal?

@timo_capa or if anyone can please kindly provide simple instructions on how to flash this custom ROM. Provide a simple guide on how to install it via Recovery option and Fastboot option.
I tried flashing it and I ended up softbricking my OnePlus 7 Pro. Please it is not everyone that is on Telegram so kindly provide installation instructions on the first post. Thank you

Open boot loader with
Code:
fastboot oem unlock
boot into fastboot mode
place rom file inside adb folder & run
Code:
fastboot update romname.image.zip
Make sure you download the .image.zip file
On first boot it will ask you to reset data, Reset your data & thats it

thanks for your hard work,,,
i flashed and used for one day,,,
battery timing was best, even better than oos10..
i faced some minor UI glitches,, as this is first built,, it's ok.. ROM id smooth.
charging speed is better than oos10..
the reason why i have to come back to oos10, was Snapchat chatting bug,,,
example if i send a msg , it will not show in settings and will send after hours.. some msgs even weren't send....
please fix Snapchat issue or if someone know how to solve Snapchat chat issue, please reply to this comment...
2nd it's showing device isn't certified, please solve it too.
Note: if anyone facing issue related fastboot option,, i mean if your device stuck on Bootloader warning,,, even after format data,,,, then please flash all partitions manually then then restart to recovery, format data then reboot to system... this is how i was able to boot ROM