Database Info

Android 10 problem with sensors

Hello,
I'm calling you in because I'm having a problem with the sensors on my oneplus 6. I had omnirom to install in version 10 without microg and gapps and I had no problem. I wanted to reinstall omnirom with microg because I had some problems with applications. I did a fresh install.
I use MSM Download android 8 sensors ok camera ok
fastboot oem unlock
update to OTA 32 Android 9.0.7 Sensors ok camera ok
fastboot boot twrp-3.3.1-14-enchilada-pie-mauronofrio.img
I flash twrp-3.3.1-18-enchilada-installer-mauronofrio.zip and reboot
flash OnePlus6Oxygen_22_OTA_040_all_1910270546_42a63.zip
flash twrp-3.3.1-18-enchilada-installer-mauronofrio.zip
flash OnePlus6Oxygen_22_OTA_040_all_1910270546_42a63.zip
flash twrp-3.3.1-18-enchilada-installer-mauronofrio.zip
flash omni-10-20200330-oneplus6-WEEKLY.zip
flash twrp-3.3.1-18-enchilada-installer-mauronofrio.zip
flash omni-10-20200330-oneplus6-WEEKLY.zip
flash twrp-3.3.1-18-enchilada-installer-mauronofrio.zip
The sensors work but the camera doesn't.
I figure it's omnirom that's buggy. I try with a version I had installed earlier and I get the same problem. I have the same problem with Havoc OS 3.3. With or without root no difference.
So OxygenOS is the problem.
I try with OB5, 10.0.1, 10.3.0 and I have the same problem.
With versions 10.3.1 and 10.3.2 it's the other way around the camera works well but not the sensors (pocket mode, auto rotate, auto brightness etc).
I used msm download about ten times without success ....
I try without unlocking the bootloader with oneplus updates.
Update 9.0.7 camera ok sensors ok
Update 10.3.1 camera ok sensors nok
I'm getting a little desperate, I've spent many hours on the problem. I've searched the xda and oneplus forums without finding any solutions.
The USSD code *#808# for calibration displays a blank page.
I restarted my phone many, many times, erased all the data several times. I'm running out of ideas. I'm trying to drain the battery completely to see if that solves the problem.
I've been using custom roms since cyanogenmod and I've never encountered this kind of problem so I'm calling on you.
Thanks for your help

I have the same problem. Does no one use the OP6 anymore?

Same problem here and I need of help. Hope someone figures out a fix.
Sent from my ONEPLUS A6003 using Tapatalk

Reaven27 said:
Hello,
I'm calling you in because I'm having a problem with the sensors on my oneplus 6. I had omnirom to install in version 10 without microg and gapps and I had no problem. I wanted to reinstall omnirom with microg because I had some problems with applications. I did a fresh install.
I use MSM Download android 8 sensors ok camera ok
fastboot oem unlock
update to OTA 32 Android 9.0.7 Sensors ok camera ok
fastboot boot twrp-3.3.1-14-enchilada-pie-mauronofrio.img
I flash twrp-3.3.1-18-enchilada-installer-mauronofrio.zip and reboot
flash OnePlus6Oxygen_22_OTA_040_all_1910270546_42a63.zip
flash twrp-3.3.1-18-enchilada-installer-mauronofrio.zip
flash OnePlus6Oxygen_22_OTA_040_all_1910270546_42a63.zip
flash twrp-3.3.1-18-enchilada-installer-mauronofrio.zip
flash omni-10-20200330-oneplus6-WEEKLY.zip
flash twrp-3.3.1-18-enchilada-installer-mauronofrio.zip
flash omni-10-20200330-oneplus6-WEEKLY.zip
flash twrp-3.3.1-18-enchilada-installer-mauronofrio.zip
The sensors work but the camera doesn't.
I figure it's omnirom that's buggy. I try with a version I had installed earlier and I get the same problem. I have the same problem with Havoc OS 3.3. With or without root no difference.
So OxygenOS is the problem.
I try with OB5, 10.0.1, 10.3.0 and I have the same problem.
With versions 10.3.1 and 10.3.2 it's the other way around the camera works well but not the sensors (pocket mode, auto rotate, auto brightness etc).
I used msm download about ten times without success ....
I try without unlocking the bootloader with oneplus updates.
Update 9.0.7 camera ok sensors ok
Update 10.3.1 camera ok sensors nok
I'm getting a little desperate, I've spent many hours on the problem. I've searched the xda and oneplus forums without finding any solutions.
The USSD code *#808# for calibration displays a blank page.
I restarted my phone many, many times, erased all the data several times. I'm running out of ideas. I'm trying to drain the battery completely to see if that solves the problem.
I've been using custom roms since cyanogenmod and I've never encountered this kind of problem so I'm calling on you.
Thanks for your help
Click to expand...
Click to collapse
i had the same problem and this fixed it completely. read the advanced flashing guide it has the answers.
https://r.tapatalk.com/shareLink/to...5&share_fid=3793&share_type=t&link_source=app
[ROM][STOCK][FASTBOOT][OP6] Stock Fastboot ROMs for OnePlus 6
Sent from my ONEPLUS A6003 using Tapatalk

Just Flash Persist.img through fastboot (unlocked Bootloader). Google the img file and its easily available.
Commands are below. That is a known issue with OP6.
fastboot erase persist
fastboot flash persist persist.img

[CLOSED] Deleted

Here was a Guide. Someone said people don't care about Me or My Work so...​

Thank you

Hello,
I'm going into boot loop when I'm trying this :
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot continue
I have downloaded your img for Xperia 1
Can you help please ?

After multiple tentative your image was woking
But when I install your module in Magisk and restart, I get Pixel Launcher Stopped message (with rest pixel laucher or go to info) and I can do nothting : the message appears every time I click somewhere.
Thanks

kelly669 said:
After multiple tentative your image was woking
But when I install your module in Magisk and restart, I get Pixel Launcher Stopped message (with rest pixel laucher or go to info) and I can do nothting : the message appears every time I click somewhere.
Thanks
Click to expand...
Click to collapse
when you say "module" what you reffer? pixel launcher or boot image? it's seems that the author posted here only boot image.
Is bettwer to build your own image instead to use one build by others;
The pixel launcher problem may be from not installing proper magisk module; check download section in magisk for necessary modules and also search on forums for pixel launcher prerequisites.

kelly669 said:
After multiple tentative your image was woking
But when I install your module in Magisk and restart, I get Pixel Launcher Stopped message (with rest pixel laucher or go to info) and I can do nothting : the message appears every time I click somewhere.
Thanks
Click to expand...
Click to collapse
Thats due to the Gesture Navigation. Please enable 3 Button Navigation To fix it... :angel:
daphix said:
when you say "module" what you reffer? pixel launcher or boot image? it's seems that the author posted here only boot image.
Is bettwer to build your own image instead to use one build by others;
The pixel launcher problem may be from not installing proper magisk module; check download section in magisk for necessary modules and also search on forums for pixel launcher prerequisites.
Click to expand...
Click to collapse
It was about My Work. There are No other Modules for the Pixel Launcher...
Since My Threads got moved from the Development Section am i No longer contributing Images Myself. Thanks to XDA and the Moderators!

Guide overhauled like promised to some <3 Let Me know if i missed something

Updated the Guide

Updated the Thread again with more exactly Instructions and a typo fix

Attempting to flash the vbmeta.img I have this problem:
unknown option fastboot --disable-verity
Any idea why fastboot can't figure this command? adb version 30.0.5
Also, what exactly is the reason to flash the vbmeta.img? Is this to allow the phone to boot with the patched image..?
I was still able to boot into android but I can't confirm if the devices is rooted or not.. all programs just hang with no confirmation if root access is granted or denied...

Will this work with android 11?

I get a boot loop when trying to flash magisk img on android 11 with magisk 20.3
Miustone said:
Updated the Thread again with more exactly Instructions and a typo fix
Click to expand...
Click to collapse

jt23738 said:
I get a boot loop when trying to flash magisk img on android 11 with magisk 20.3
Click to expand...
Click to collapse
20.3 is totally outdated: https://github.com/topjohnwu/Magisk/releases

jt23738 said:
I get a boot loop when trying to flash magisk img on android 11 with magisk 20.3
Click to expand...
Click to collapse
Sorry I meant 22.1 magisk

Miustone said:
20.3 is totally outdated: https://github.com/topjohnwu/Magisk/releases
Click to expand...
Click to collapse
Any news on this ? I used the latest Magisk 23.0

My Xperia 5 is dead so i can't Test anymore... Sorry

Thank you @Miustone, your post has been a helpful reference. Some things change over time so it's good to have this guide that is current.
In your guide, I have been looking at the Flashing Firmwares and re-locking the Bootloader... section.
Miustone said:
If You want to relock Your Bootloader...
-Just go into fastboot mode any type in the command prompt (like before in this Guide):
Code:
cd\
cd platform-tools
fastboot oem lock
-Wait for Your Device and disconnect it from USB
-Download and Install the "Xperia Companion" from SONY
-Open the Xperia Companion and select Software Repair
-Select that Your Device can't get recognized (or is a Smartwatch 3 lol)
-Go to the next Page and select the Xperia Smartphone Option
-Continue and wait for the Initialization
-Press and hold Volume DOWN while connecting to USB (You will see the Green Flashmode LED again)
-Continue once Your Device gets recognized and let the Xperia Companion do his work...
Done. Your Bootloader is locked again and most of Your DRMs are restored. But please Note, that unlocking Your Bootloader erases Your unique Device Key FOREVER. That will flag Your Device as "it was unlocked". This can be checked by SONY and everyone else who has this Device in his Hands... (SONY knows it anyways).
Click to expand...
Click to collapse
Please can you advise, confirm that while rooted with Magisk (v23.0), I can relock the bootloader so as to be able to get Sony OTA updates for my Xperia 1?
I had to download firmware with XperiFirm anyway, to get the boot img for Magisk to patch. And because it is newer firmware I just went and flashed it - also because I needed to fix the broken camera/torch caused by rooting with Magisk. So now everything is working again.
So I lose root but I can just root again with Magisk. At that point can I relock the bootloader so that I can receive OTAs, and still be rooted?

OutOfSync said:
Thank you @Miustone, your post has been a helpful reference. Some things change over time so it's good to have this guide that is current.
In your guide, I have been looking at the Flashing Firmwares and re-locking the Bootloader... section.
Please can you advise, confirm that while rooted with Magisk (v23.0), I can relock the bootloader so as to be able to get Sony OTA updates for my Xperia 1?
I had to download firmware with XperiFirm anyway, to get the boot img for Magisk to patch. And because it is newer firmware I just went and flashed it - also because I needed to fix the broken camera/torch caused by rooting with Magisk. So now everything is working again.
So I lose root but I can just root again with Magisk. At that point can I relock the bootloader so that I can receive OTAs, and still be rooted?
Click to expand...
Click to collapse
You need to choose.
Unlocked = Magisk/Root, Freedom, Control
Locked = No Magisk/Root, Freedom, Control
I do also recommend to wait for Pixel Experience. It will come soon with Mainline Kernels for many Xperias... Including OTAs

Hi guys, I cannot watch Netflix after unlock bootloader my J9110, it shows error 5.8. Tried many workarounds but none of them work.
I'm on Android 12 beta 5. Please help!

Thread Updates coming soon including Android 12 GSI flashing + Magisk

[PATCH] Post-install patch for GSI ROMs 2.0.0

Hello XDA, this patch is intended to fix issues that arise from using phh-based Treble GSIs. This patch aims to make
life bearable on these ROMs and to add the functions that are missing from EMUI 8 and the OpenKirin ROMs. With
this patch you can use any working Pie or 10 GSI and have a complete experience, having to do as few manual tweaks as
possible.
What this patch does:
- Restores offline charging functionality
- Fixes crash on Bluetooth/NFC section in settings
- Fixes headphone jack detection
- Fixes the missing apps in Play Store
- Fixes battery stats behavior by supplying a correct power profile
- Fixes the lack of Night Light in AOSP-based ROMs
Tested P GSI ROMs:
- AOSP 9
- LineageOS 16.0 (AndyYan)
Tested Q GSI ROMs:
- AOSP 10
- LineageOS 17.1 (AndyYan)
Tested R GSI ROMs:
none
Installation:
1 - Flash eva_amend_x.y.z.zip on TWRP
2 - Wipe cache
3 - Reboot
Download:
here
Source:
You can analyze the patch to see the source code.
Credits:
lo_ol, hi6250 community, Wattsensi

Changelog
Code:
2.0.0
- Removed redundant fixes
- NFC is now responsibility of the GSI. This NFC fix was wrong on so many levels I can't even begin to describe.
- All prior versions removed from Google Drive
1.1.0
- Add HWComposer fixes
1.0.0
- Initial release

This looks really promissing - thanks a lot! How about fixing the issue with wifi hotspot for P9? Would that be doable as well?

@Wattsensi Hi. I'm the new owner of an old P9 (EVA-L09) and I would like to install an Android 10 GSI ROM. The only problem is it feels much more complicated than on my other phone. On my (much newer) Nubia RM3, I unlocked the bootloader, flashed recovery, flashed the GSI and tadaaa.
On the P9, I managed to unlock the BL, flashed TWRP and I'm contemplating what GSI should I flash. The treble checker app said the phone is not Treble compatible. It also shows as A-only ARM64.
Can you please guide me on what to install or point me towards a guide?
Thank you

Nightwish1976 said:
@Wattsensi The treble checker app said the phone is not Treble compatible. It also shows as A-only ARM64.
Click to expand...
Click to collapse
Basically you shall first rebrand and upgrade to Oreo to get treble support, here is how:
https://forum.xda-developers.com/showpost.php?p=77161313&postcount=2

@xaweryp Thanks a lot for the input, now I'm downloading the files necessary to rebrand and update to Oreo.
LE: just finished updating to Oreo.
Can I just flash an A only Arm64 GSI, or are there another steps? I have that new recovery (Pretorianos80 v4), but I think it cannot access the internal storage...

Nightwish1976 said:
@Wattsensi Hi. I'm the new owner of an old P9 (EVA-L09) and I would like to install an Android 10 GSI ROM. The only problem is it feels much more complicated than on my other phone. On my (much newer) Nubia RM3, I unlocked the bootloader, flashed recovery, flashed the GSI and tadaaa.
On the P9, I managed to unlock the BL, flashed TWRP and I'm contemplating what GSI should I flash. The treble checker app said the phone is not Treble compatible. It also shows as A-only ARM64.
Can you please guide me on what to install or point me towards a guide?
Thank you
Click to expand...
Click to collapse
Nightwish1976 said:
@Wattsensi Hi. I'm the new owner of an old P9 (EVA-L09) and I would like to install an Android 10 GSI ROM. The only problem is it feels much more complicated than on my other phone.
Click to expand...
Click to collapse
Hello. This device is abandoned, we're pretty much 1 or 2 developers working here. Yeah, I agree about the phone being complicated. It has so many quirks compared to my Galaxy S7 where everything just works out of the box.
This phone is not newcomer friendly, but with effort you can get through.
You can indeed install an Android 10 GSI but it's a poor user experience. Your choices are limited with this device, right now we have no working camera or NFC on 10. If you don't care running an older version of Android but still secure you can try @MSe1969's LineageOS 16.0 builds which incorporate the latest security patches and are updated monthly.
That ROM is designed to be used without GApps so keep that in mind.
Nightwish1976 said:
On the P9, I managed to unlock the BL, flashed TWRP and I'm contemplating what GSI should I flash. The treble checker app said the phone is not Treble compatible. It also shows as A-only ARM64.
Can you please guide me on what to install or point me towards a guide?
Thank you
Click to expand...
Click to collapse
First of all, do you have your unlock code in hand? You will need it when you perform the needed rebranding procedure. This will reflash your phone with a Chinese ROM so you can OTA-update to Oreo, which introduces Treble functionality into the device. Rebrand, update to Oreo and flash the latest (as of 09/2020) 8.0.0.550 firmware. Then flash the needed network patches to make your radio work, and then decrypt and install TWRP.
First, go there:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
The second post contains upgrade instructions and be careful. Cheers!

Updated the patch. Now NFC functionality is responsibility of the GSI and removed useless stuff.

Development Random Builds - A11 (PE+, Havoc OS, MSM Xtended, Project Sakura, dotOS)

So im kinda lazy, and don't want to make a new thread for each of my builds, so i will share them here if they are decent enough.
INSTALLATION:
You MUST have an unlocked bootloader
TINY FASTBOOT SCRIPT - First Time Install / Clean Flash
1. Download the ROM zip and TinyFastbootScript
2. Extract both zip files into the same folder on your PC
3. Run flash.bat and install latest Motorola drivers
4. Reboot device to bootloader mode and connect to PC
5. Select Flash Custom Firmware (option r)
6. Wait for the program to flash all images
7. After flashing, in the tinyfastboot main menu, press n, then press 3, then type fastboot -w and enter
8. Once finished, Reboot to System
Update / Dirty Flash
1. Download the ROM zip
2. Extract the ROM files into the same folder as previous update
3. Reboot device to bootloader mode and connect to PC
4. Select Flash Custom Firmware (option r)
5. Wait for the device to flash all images
6. Once finished, Reboot to System
All my builds will be GAPPS INCLUDED, and no, i WONT make you a vanilla version.
HAVOC-OS 4.16 (April security patch)
https://drive.google.com/file/d/16QLxXqCxdz_5socjV4sVGbHPOBbai-eG/view?usp=sharing
MSM Xtended (november security patch)
https://drive.google.com/file/d/1Irz9eExiix4o9u16AI7j6HDRziSkLnMN/view
Pixel Experience Plus (december security patch)
https://drive.google.com/file/d/1R10N9qay1Ku3TEErWxNIlifkNFET6NIk/view?usp=sharing
Project Sakura 5.2 - (january security patch)
https://drive.google.com/file/d/15v18B0z6m2lf1LyaL9MQJpvubtUiS5C1/view?usp=sharing
dotOS 5.2.1 (november security patch)
https://drive.google.com/file/d/1g9GL6H5dixe62DbEzcQRD95ljgZ5W_B7/view?usp=sharing
Kernel Source Code: https://github.com/moto-sm8250/android_kernel_motorola_sm8250
Device Source Code: https://github.com/moto-sm8250/android_device_motorola_nio
Device-Common Source Code: https://github.com/moto-sm8250/android_device_motorola_sm8250-common
Vendor-Common Source Code: https://github.com/moto-sm8250/android_vendor_motorola_sm8250-common
Vendor Source Code: https://github.com/moto-sm8250/android_vendor_motorola_nio
Special thanks to @Electimon for all his help!

18-11-21 - Havoc OS and MSM Xtended added
20-11-21 - Pixel Experience plus added (not fully tested, but all major things working)
22-12-21 - Havoc OS 4.12 added
02-01-22 - Pixel Experience Plus added (december patch)
21-1-22 - dotOS 5.2.1 added
29-1-22 - Project Sakura and Havoc updated to january security patch
18-3-22 - Havoc OS 4.14 added (feb patch)

Thank you will test these

Tested MSM Xtended dont boot on moto g100 just restarts on boot.

Pixel Experience plus is well dont boot on my g100 do i missing something to do ? did all instruction how to flash same just restarts to bootloader.

Any help how get running these all not working on g100

rackis18 said:
Any help how get running these all not working on g100
Click to expand...
Click to collapse
Try formatting data (fastboot -w) in the bootloader

rackis18 said:
Tested MSM Xtended dont boot on moto g100 just restarts on boot.
Click to expand...
Click to collapse
This one has been tested by a g100 user and i was told it boots up

Beetle84 said:
This one has been tested by a g100 user and i was told it boots up
Click to expand...
Click to collapse
That's interesting because on my g100 it won't boot just reboot into bootloader. I did format data etc in tiny script.

@rackis18 Open tiny fastboot script, press n and then 3 and type fastboot -w, enter and reboot

rackis18 said:
That's interesting because on my g100 it won't boot just reboot into bootloader. I did format data etc in tiny script.
Click to expand...
Click to collapse
Hey mate, just heard back from a guy on telegram with a g100, it boots up fine for him.

Beetle84 said:
Hey mate, just heard back from a guy on telegram with a g100, it boots up fine for him.
Click to expand...
Click to collapse
Which one you own, g100 or Edge S?

Windoors said:
Which one you own, g100 or Edge S?
Click to expand...
Click to collapse
I have the edge S mate

I can boot any other rom from here and they boots and works no problems but these 3 have issues on g100 i think needs to look at these mate. Thanks

rackis18 said:
I can boot any other room from here and they boots and works no problems but these 3 have issues on g100 i think needs to look at these mate. Thanks
Click to expand...
Click to collapse
The latest evo x (november build) is working?

Beetle84 said:
Could you try flashing a vbmeta
The latest evo x (november build) is working?
Click to expand...
Click to collapse
Yes works no problems I'm using it now. Anyway, nice build mate.

Beetle84 said:
@rackis18 Open tiny fastboot script, press n and then 3 and type fastboot -w, enter and reboot
Click to expand...
Click to collapse
This worked mate thanks for help.

rackis18 said:
This worked mate thanks for help.
Click to expand...
Click to collapse
So all good now?

Beetle84 said:
So all good now?
Click to expand...
Click to collapse
Yup. All good. I don't know if that's made any difference before I tried install from stock rom now from evo so just let you know because maybe a reason.

rackis18 said:
Yup. All good. I don't know if that's made any difference before I tried install from stock rom now from evo so just let you know because maybe a reason.
Click to expand...
Click to collapse
Definitely the data format was the problem i think. I changed the instructions to include that instead of the tinyfastboot reset

Realme C21Y (RMX3261,RMX3263,RMX3262) kernel source, boot.img....

Hello and welcome​NOTICE:This thread will be modified when new files are available.
Manufacturer: Rea*me
Device: Realme C21Y
Chipset: UNISOC T610
DEVICE CODENAME: RMX3263,RMX3261,RMX3262
Currently available files:
pre-built kernel(zImage) boot.img
device-tree.dtb(device tree blob)
device-tree-source.dts(device tree source)
kernel-configuration file, sepolicy, prop.default
EDIT:finaaaaally Rea*me released the kernel source for this device, I think it is time for you to compile !
https://github.com/realme-kernel-opensource/realme_C21Y-AndroidR-kernel-source/
unfortunately as you see, there is no kernel source and also a way to unlock the bootloader, the files are somehow not very important but maybe in the future they will be.
actually, you can build any custom rom for this device using the prebuilt kernel(zImage), without kernel source by using TARGET_PREBUILT_KERNEL="Path to zImage" variable, if you understood that's good, if not just search for it, then when you got the zip file you can use sp research tool to flash the built from source rom with a locked bootloader, because it is the only way to flash this phone's files with locked bootloader, these are the instructions that you'll need to do(please note that this is a theory only, i didn't test it and i am not responsible for bricked devices, at your own risk !):
Get the phone's stock rom for example from this link: https://romprovider.com/realme-rmx3263-flash-file-firmware-free/
then install the sp research tool(you need to use this one specifically, the sp flah tool works just in the factory): https://androidmtk.com/download-spd-research-tool
Link: then using this link follow the steps until you replaced the stock system.img to the GSI's system.img one.
then just flash it using the tool and you will success to flash the GSI rom.
Next the file device-tree-sorce.dts is the device tree source file.
To get the boot.img, download the boot.zip below, extract it and you'll have it, if you want to modify boot.img download AIK tool: then run the shell script on the boot.imh file(you can do it only in Linux).
well we hope we will find a way to unlock the bootloader, because it's the key for doing everything.

Have you tried realme Deep test App to unlock the bootloader.

Hey I was thinking of flashing the proton AOSP GSI on Realme C21Y. I have checked that realme c21y has Treble SUPPORT so I thought if you can give it a try if you happen to have a realme c21y available.
Here are the links of file and tutorials that I intend to follow .
Tutorial.
GSI ROM link : https://github.com/haridhayal11/treble_proton_aosp/releases/

The problem is that you can't unlock the bootloader. Not about installing a GSI.

Mamo_grag17 said:
The problem is that you can't unlock the bootloader. Not about installing a GSI.
Click to expand...
Click to collapse
I am really sorry. I just realised it Today when I was trying to unlock the bootloader.
the IN Depth test Apk simply refused to install on my device .
BTW , PLEASE Keep on posting if you find any update on this issue

Yes
kknitesh805 said:
Have you tried realme Deep test App to unlock the bootloader.
Click to expand...
Click to collapse

Mamo_grag17 said:
Yes
Click to expand...
Click to collapse
Yes , I tried but the App refused to install.
I was able to boot my phone into FASTBOOT by using " ABD REBOOT BOOTLOADER"
fastboot command does work there but when I tried " fastboot flashing unlock"
The command failed .

The problem is that the device's community is dead. You can't find a griup or something like that to discuss.
Unfortuanately, i don't own that device anymore.

Mamo_grag17 said:
The problem is that the device's community is dead. You can't find a griup or something like that to discuss th
wwi
Unfortunately, i don't own that device anymore.
Click to expand...
Click to collapse
Yeah...I guess you're right.
It was a bad decision to buy THIS smartphone.

Unlocking the bootloader requires a key from the company.
I'll give you an advice: don't buy realme,vivo,oppo or whatever company exept samsung , xiaomi oneplus if you plan to install a custom rom...
I have a galaxy a20e and it is awesome i am using android 12.1 now (ofc custom rom)

Mamo_grag17 said:
Unlocking the bootloader requires a key from the company
I'll give you an advice: don't buy realme are if you plan to install a custom rom...
I have a galaxy a20e and it is awesome i am using android 12.1 now (ofc custom rom)
Click to expand...
Click to collapse
Yes, I will take care of I buy a new smartphone in future.

kknitesh805 said:
Yeah...I guess you're right.
It was a bad decision to buy THIS smartphone.
Click to expand...
Click to collapse
Yes it is

kknitesh805 said:
Hey I was thinking of flashing the proton AOSP GSI on Realme C21Y. I have checked that realme c21y has Treble SUPPORT so I thought if you can give it a try if you happen to have a realme c21y available.
Here are the links of file and tutorials that I intend to follow .
Tutorial.
GSI ROM link : https://github.com/haridhayal11/treble_proton_aosp/releases/
Click to expand...
Click to collapse
We are our colleagues 4pda We were able to make a tutorial on the firmware gsi rom all fully working, even the firmware works through adb
Tutorial: Mod edit: 4pda link removed.

mamograg said:
Yes it is
Click to expand...
Click to collapse
Have you tried the new method to install GSI on realme c21y mentioned on 4pda.to website..
They told to change the boot file...
But I am not sure...whether it is safe or not ...
I mean what if the file is compromised..

kknitesh805 said:
Have you tried the new method to install GSI on realme c21y mentioned on 4pda.to website..
They told to change the boot file...
But I am not sure...whether it is safe or not ...
I mean what if the file is compromised..
Click to expand...
Click to collapse
I am one of those people who is the developer of the method, it is COMPLETELY SAFE, of course there are a lot of different tests, and lately we have almost completed twrp.

leanord said:
I am one of those people who is the developer of the method, it is COMPLETELY SAFE, of course there are a lot of different tests, and lately we have almost completed twrp.
Click to expand...
Click to collapse
Thanks for the reply,
One more question, why is that every GSI that is loaded by this method has some kind of audio problem..
Without audio , this is almost a deal breaker....
Is there any method to use headphones on booted GSIs ??

kknitesh805 said:
Thanks for the reply,
One more question, why is that every GSI that is loaded by this method has some kind of audio problem..
Without audio , this is almost a deal breaker....
Is there any method to use headphones on booted GSIs ??
Click to expand...
Click to collapse
Greetings, the problem with the headphones is partly related to the vendor, which is natural for A11, but for A12 and A13 it is not yet available, or rather it needs to be updated for this, which is comparable to know very well Same Kotlin.

kknitesh805 said:
Have you tried the new method to install GSI on realme c21y mentioned on 4pda.to website..
They told to change the boot file...
But I am not sure...whether it is safe or not ...
I mean what if the file is compromised..
Click to expand...
Click to collapse
I don't own this device anymore, i tried all what i can to unlock bootloader and customize phone, but that was 8 months ago, i don't know if there are some new methods.

leanord said:
Greetings, the problem with the headphones is partly related to the vendor, which is natural for A11, but for A12 and A13 it is not yet available, or rather it needs to be updated for this, which is comparable to know very well Same Kotlin.
Click to expand...
Click to collapse
Hello, brightness fix module link is broken, can you share it again?

Luuukiee said:
Hello, brightness fix module link is broken, can you share it again?
Click to expand...
Click to collapse
Will earphone work with GSI and also...will i be able to control brightness manually