haha i do just wanted moreDon't use your sdcard as internal storage in any ROM. It causes issues, you need to format your SDcards.
You don't have enough space in ur POCO?![]()
haha i do just wanted moreDon't use your sdcard as internal storage in any ROM. It causes issues, you need to format your SDcards.
You don't have enough space in ur POCO?![]()
hehe yeah as i said don't do that, sdcard as internal causing issues not only in this ROM but generally.
hehe yeah as i said don't do that, sdcard as internal causing issues not only in this ROM but generally.
Anyways let me know if you fix ur issue.
Format it on TWRP not via the ROM.meh even when I try to format it as external it still starts bootloop at 60%
thank you that worked
Thanks so much for your continues great work on crDroid for our Poco F1Build 20230113 is ready
Changelog: https://crdroid.net/beryllium/9#changelog
Download: https://crdroid.net/beryllium/9
Join the chat on Telegram @ https://t.me/crDroidPoco
same issue I faced while updating via OTA, but I dirty flashed the older 13th Jan release crDroid build and it's back to stable.I updated via OTA the last version, the phone started freezes, when i reinstalled NKG kernel the freezes stopped. But now, when i check the version, it shows the previous version yet, why?
Now i dirty flashed manually with TWRP, and this 2022 version keeps popping up in updater
I'm encrypted.
Edit: I remember having this "problem" when using Awaken, I updated the version, but the updater kept showing a previous version, very strange.
The January 27th version is stable for me, my only doubt is that the updater shows an older version than the one I'm using. A user from the Telegram group recommended me to delete the zip file of the rom that I downloaded, I deleted it and the same error continues.same issue I faced while updating via OTA, but I dirty flashed the older 13th Jan release crDroid build and it's back to stable.
If you are DFE user:Need help please. I flashed the recommended Reinz TWRP and wiped system, data, cache, dalvik, vendor BUT KEPT internal storage. I then flashed the latest CR 9.1 Android 13 and DFE for A13 but the phone doesn't boot and instead reboots to TWRP. Searching online showed that i have to format data. Is there any way to make this work without formatting data. I am decrypted and can access internal storage from both inside TWRP and MTP.
Edit: TWRP shows this
Android Rescue Party trigger! Possible solutions ?
1. Wipe caches and/or
2. Format data and/or
3. Clean-flash your ROM
The reported problem is :
'--reason=set_policy_failed:/data/misc'
The guide shows A12. I will try A9 but do i have to use system_ext or Non Syste_ext version ?If you are DFE user:
Use TWRP by REIGNZ based on A9 > Wipe the partitions include system_ext > Flash ROM/Gapps > Mount vendor and flash DFE and Reboot.
The guide shows A12 since it assume you are gonna use what the ROMs offer and in that case encryption.The guide shows A12. I will try A9 but do i have to use system_ext or Non Syste_ext version ?
Now the phone gets stuck at recovery logo but is detected in both fastboot (in bootloader) and adb (in recovery logo). Is there a fix ?The guide shows A12 since it assume you are gonna use what the ROMs offer and in that case encryption.
You have to use System_Ext version.
Did you mount vendor before flash dfe? Do use DFE 13 or the old DFE? Try with both.Now the phone gets stuck at recovery logo but is detected in both fastboot (in bootloader) and adb (in recovery logo). Is there a fix ?
Yes I mounted vendor and used DFE13 as instructed. I was able to access storage through TWRP file manager and MTPDid you mount vendor before flash dfe? Do use DFE 13 or the old DFE? Try with both.
The easiest way is to backup your data to PC and do clean install + format data. Now it's a bit mess I guess you mixed things up.Yes I mounted vendor and used DFE13 as instructed. I was able to access storage through TWRP file manager and MTP
no
You can use reignz 3.7.0 A12 v2 twrpDo I need crdroid recovery for this update to apply? I am reluctant as I am happy with TWRP. Also the kernel is somethinkni don't want to change. As an aging device my PocoF1 mass battery issue while trying many ROMs, this ROM is good with battery. I am skeptical if battery or other issue will spring up with this update.
I searched about android system intelligence on telegram crdroid group and I found some ppl also got it with core nikgapps. Also it was shipping with the ROM in the past but gwolfu seems he removed it because causing issues. Don't know why this happening with the recent updates. I personally don't include asi in my gapps and I don't have it installed.I'll let alisensei confirm their source, but I have been facing this since the last four ROM releases at least. I did uninstall ASI, but was unable to find the app on the Play Store, so installed from apkmirror (from another user's suggestion).
I think the ROM might be installing it. Maybe @gwolfu can confirm since other users have reported this as well. Why should Settings Services crash though? I have seen this as well since the last four ROM versions. I'm not the only one facing this.
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
fastboot flash recovery recovery.img
adb sideload crDroid.zip
adb sideload crDroid.zip
I don't know how your official twrp is able to decrypt, encrypted ROMs since it's not working. Are u sure encrypted?This is it, firstly thanks for taking our f1 device to a higher level, secondly @gwolfu @Retrial how to update from crdroid A12 latest build, but using official twrp, I have no problem with decrypting data or anything like that, as long as official twrp stays where it should be and don't lose data, thank you very much crdroid team and especially for you @gwolfu thanks again to everyone here