I did not deliberately remove them... Something else occurred. Can anybody else confirm the camera/flashlight issue?Thanks brightness works fine ..... but now camera and flashlight isn't available in last build
I'll upload a new version today.
I did not deliberately remove them... Something else occurred. Can anybody else confirm the camera/flashlight issue?Thanks brightness works fine ..... but now camera and flashlight isn't available in last build
I did not deliberately remove them... Something else occurred. Can anybody else confirm the camera/flashlight issue?
I'll upload a new version today.
Yeah. For me too. Sorry. It will take a while to understand what is going on
No, it has not.This rom have gapps?
My devise have stock android 10.0 and twrp dont awaiable
Which is your device? Is it Treble compatible?my device come wih oreo 8.1 security patch june 2018
i instal crdroid arm 64 aonly < i have checked that my device support arm 64 a
after boot animation my device always back to fastboot mode (use stock boot.img)
any solution to fix this bootloop?
my device luna g60xWhich is your device? Is it Treble compatible?
Did you format data (not wipe) after installing the gsi image?
Does any of the steps mentioned on post 2 helps you?
Sorry not being useful for you. Your issue is beyond my knowledge :crying:my device luna g60x
my stock rom dont have vbmeta.img
i tried reflash to stock rom
and I tried to reflash crdroid
this is method what i use
unlock bootloader
1. erase userdata,erase system and flash system via fastboot . no succes always back to fastboot mode
2. clean through TWRP by wiping dalvik/artcache. system. data. cache and reflashing crdroid again. still no luck
3. permissiver 5 dmverity n force encrypt succes >> reboot>>> bootanimation>> fastboot mode (still no luck again)
by the way i used to instal phusson quack phh treble 220 and havoc 3.6 could run with no bootloop
perhaps this rom for device who has vbmeta.img
It is based on which version of crdroid?
My device is Sony Xperia XA2 (pioneer).
I have downloaded many official gsi all give me same problem for dark theme.
It has A/B arm64
Will it work on my device?
Can u say me solution to my problem?
Hello. I followed the installation guide, the device is supported in First release notes (2020.03.30) • updated overlay for Redmi 6 Pro but I get nothing after flashing in twrp-3.4.0-0-sakura install>installimage>crdrom-v224-201019-arm64-agN/crdrom-v224-201019-arm64-avN.img(BiTGApps-arm64-10.0.0-R18_signed.zip)>systemimage>flash nothing happens when rebooting, the phone boots to mi logo then the device turns off. the device is empty, clean install. thank you.
Not enough explanation or information to make it work in this itemIssues 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.
Disclaimer: I am not responsible for any damage you made to your device.
You have been warned!
You tell me. I've tested on just one phone.
Perfect on top of LOS171 base on Moto g7 River xt1962-1 and VZW (CDMA). Great job, thanks