[ROM][13][BERYLLIUM] crDroid v9.2 [12.03.2023]

[MasterFURQAN]

an

Did 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.

I used adb pull to copy a text file while its on the TWRP logo and it worked. It just isn't booting to TWRP for some reason

 

[MasterFURQAN]

an



I used adb pull to copy a text file while its on the TWRP logo and it worked. It just isn't booting to TWRP for some reason

For anyone with the same issue , I fixed it by using fastbboot to flash and boot into the a12 recovery and then flash the rom. Only after that was I able to make the A9 recovery work.

 

[fmhd]

I upgraded from A12 to A13. Encountered the screen freeze issue a few times. Dpi not getting lower as it used to be. The sound quality had gotten a bit low.
I also encountered a slower touch response on my display. Doe anyone else experienced it or is it just me? SOT has improved a bit.
Even when I was typing this comment , the display got stuck when I tapped on backspace and the whole text whatever I had typed got erased. I had to lock the screen and open it to bring it back to normal.
Update : For some reason my phone goes on random reboot.
Any idea how to change the crdroid recovery to twrp? The update from A12 to A13 has gone all wrong for me .

 

[umangloria]

I tried to do the fresh install via crdroid recovery, with the latest build and latest nikgapps full (1st Feb 2023) and it crashed after the setup wizard, Saying pixel launcher crashed same for crdroid launcher.
Then I tried omni build and it worked just fine so, then I again wiped the device and installed rom, nikgapps omni, and then pixel launcher addon and got the same issue I am guessing there is something specific with pixel launcher

 

[Alias X]

I upgraded from A12 to A13. Encountered the screen freeze issue a few times. Dpi not getting lower as it used to be. The sound quality had gotten a bit low.
I also encountered a slower touch response on my display. Doe anyone else experienced it or is it just me? SOT has improved a bit.
Even when I was typing this comment , the display got stuck when I tapped on backspace and the whole text whatever I had typed got erased. I had to lock the screen and open it to bring it back to normal.
Update : For some reason my phone goes on random reboot.
Any idea how to change the crdroid recovery to twrp? The update from A12 to A13 has gone all wrong for me .

I tried to do the fresh install via crdroid recovery, with the latest build and latest nikgapps full (1st Feb 2023) and it crashed after the setup wizard, Saying pixel launcher crashed same for crdroid launcher.
Then I tried omni build and it worked just fine so, then I again wiped the device and installed rom, nikgapps omni, and then pixel launcher addon and got the same issue I am guessing there is something specific with pixel launcher

Guys, always try a clean flash and use one of the smallest available GApps packages, anything else is just asking for trouble.

 

[Retrial]

I upgraded from A12 to A13. Encountered the screen freeze issue a few times. Dpi not getting lower as it used to be. The sound quality had gotten a bit low.
I also encountered a slower touch response on my display. Doe anyone else experienced it or is it just me? SOT has improved a bit.
Even when I was typing this comment , the display got stuck when I tapped on backspace and the whole text whatever I had typed got erased. I had to lock the screen and open it to bring it back to normal.
Update : For some reason my phone goes on random reboot.
Any idea how to change the crdroid recovery to twrp? The update from A12 to A13 has gone all wrong for me .

Clean install from one Android version to another. Imagine that, like you get a new phone.
Backup your data to PC, clean install the new ROM and transfer your data back.
You can also follow this guide to flash with TWRP.

I tried to do the fresh install via crdroid recovery, with the latest build and latest nikgapps full (1st Feb 2023) and it crashed after the setup wizard, Saying pixel launcher crashed same for crdroid launcher.
Then I tried omni build and it worked just fine so, then I again wiped the device and installed rom, nikgapps omni, and then pixel launcher addon and got the same issue I am guessing there is something specific with pixel launcher

Pixel Launcher is known to have issues. Do not use full bloated packages.
You can also use my build of NikGApps if you want to convert "vanilla" rom to "gapps" rom - without bloat.

Guys, always try a clean flash and use one of the smallest available GApps packages, anything else is just asking for trouble.

Depends what they using. Full bloated gapps packages will mostly have issues, but you can use gapps above core nikgapps ofc, like mine.

 

[alisensei93]

@Retrial I was one of the dumbasses and flashed full Gapps with clean flash following yours tutarial as always.
should i just flash your version of nikGapps again?
btw I have a weird issue I couldn't flash CRdroid recovery only boot to it. when i flashed latest 9.1 I still have PE+ recovery installed hhh

 

[gwolfu]

Build 20230203 is ready

Changelog: https://crdroid.net/beryllium/9#changelog
Download: https://crdroid.net/beryllium/9

Join the chat on Telegram @ https://t.me/crDroidPoco

 

[Alias X]

Depends what they using. Full bloated gapps packages will mostly have issues, but you can use gapps above core nikgapps ofc, like mine.

Well, I was using Basic + Setup wizard + GBoard, so I was VERY close to your package anyway. But I appreciate the effort.

 

[diskordia84]

Meanwhile I am disappointed with the Android 13 rom. It had a Bluetooth bug on the first try. The connection was gone after a short time. Now, after a while, the Opera browser and the xplore file manager no longer open. First the programs work, then suddenly they don't work anymore. A pity. I'm still on the latest Android 12 Rom.

 

[Alias X]

Meanwhile I am disappointed with the Android 13 rom. It had a Bluetooth bug on the first try. The connection was gone after a short time. Now, after a while, the Opera browser and the xplore file manager no longer open. First the programs work, then suddenly they don't work anymore. A pity. I'm still on the latest Android 12 Rom.

How did you install it? Full wipe including system and data? One of the smallest GApps packages? Stock kernel or NGK?

I can tell you exactly what I installed and how if you want, I don't have issues.

 

[Retrial]

Meanwhile I am disappointed with the Android 13 rom. It had a Bluetooth bug on the first try. The connection was gone after a short time. Now, after a while, the Opera browser and the xplore file manager no longer open. First the programs work, then suddenly they don't work anymore. A pity. I'm still on the latest Android 12 Rom.

I don't know what you did but the ROM working great.
Follow this guide to make a clean install, flash my NikGApps or core if you want, stay encrypted, let it boot and flash ngk after if u want.

 

[timbuctoo]

Meanwhile I am disappointed with the Android 13 rom. It had a Bluetooth bug on the first try. The connection was gone after a short time. Now, after a while, the Opera browser and the xplore file manager no longer open. First the programs work, then suddenly they don't work anymore. A pity. I'm still on the latest Android 12 Rom.

Right before the apps started crashing, did you switch the kernel to NGK? If so, make sure you optimize the apps with the NGK app and then your apps won't crash. I had the same issue with some apps but they work fine now after optimization.

Even if you weren't using NGK, I'd suggest you follow the steps @Retrial has so diligently documented for us at post# 4 of this thread, and optimize the apps with NGK app on first boot after flashing the NGK kernel.

 

[Alias X]

Right before the apps started crashing, did you switch the kernel to NGK? If so, make sure you optimize the apps with the NGK app and then your apps won't crash. I had the same issue with some apps but they work fine now after optimization.

Even if you weren't using NGK, I'd suggest you follow the steps @Retrial has so diligently documented for us at post# 4 of this thread, and optimize the apps with NGK app on first boot after flashing the NGK kernel.

Wait, are we supposed to wipe Dalvik/ART after flashing NGK? Never did that, never noticed an issue.

 

[that1]

Folks, thank you for making Android 13 for Poco F1.

Looks like I have not flashed this rom correctly.
The current major issue is that the keyboard does not appear on screen at all. Hence I cannot type anything.
This is how I flashed. Please suggest a solution. Thank you.

Was using Pixel Experience 10 till yesterday. There was no DFE on it hence it must have been running encrypted all along.
0. Created full backup on sd card using old twrp.
1. Downloaded the rom, twrp recovery, gapps as mentioned in post 4 and placed it on sd card.
2. Flashed the new TWRP using the old PE10's TWRP.
3. Booted into new TWRP. But IT was asking password. Couldn't do full wipe because of that password prompt.
4. So managed to flash crdroid recovery as an alternative.
5. Did full format as available in crdroid recovery.
6. Flashed the rom using crdroid recovery. Rebooted and flashed the said gapps.
5. Now the phone boots normally but no keyboard to be seen.
What to do now?
Does this mean that I dirty flashed?
Does it mean that it is unencrypted?
Please help.
Thanks for reading.

 

[Retrial]

Folks, thank you for making Android 13 for Poco F1.

Looks like I have not flashed this rom correctly.
The current major issue is that the keyboard does not appear on screen at all. Hence I cannot type anything.
This is how I flashed. Please suggest a solution. Thank you.

Was using Pixel Experience 10 till yesterday. There was no DFE on it hence it must have been running encrypted all along.
0. Created full backup on sd card using old twrp.
1. Downloaded the rom, twrp recovery, gapps as mentioned in post 4 and placed it on sd card.
2. Flashed the new TWRP using the old PE10's TWRP.
3. Booted into new TWRP. But IT was asking password. Couldn't do full wipe because of that password prompt.
4. So managed to flash crdroid recovery as an alternative.
5. Did full format as available in crdroid recovery.
6. Flashed the rom using crdroid recovery. Rebooted and flashed the said gapps.
5. Now the phone boots normally but no keyboard to be seen.
What to do now?
Does this mean that I dirty flashed?
Does it mean that it is unencrypted?
Please help.
Thanks for reading.

Do not flash gapps after first boot of the ROM. flash GApps, after when u flash the ROM and before you boot.
Also if you created backup of ur data as you said, in TWRP you should do full wipes and format data (don't know what you mean you couldn't - just skip the prompt), so you can be in clean state to install crDroid. Follow the steps I wrote and you will be fine.

 

[that1]

Do not flash gapps after first boot of the ROM. flash GApps, after when u flash the ROM and before you boot.
Also if you created backup of ur data as you said, in TWRP you should do full wipes and format data (don't know what you mean you couldn't - just skip the prompt), so you can be in clean state to install crDroid. Follow the steps I wrote and you will be fine.

Thanks Retrial.
I did try full wipe by skipping password promptin the new twrp, but it said it couldn't mount the partitions and hence couldn't wipe the partitions. I was going by the steps mentioned in post 4.
Now that I am on crdroid recovery, how do I get back the twrp to retry full wipe through twrp?

 

[Retrial]

Thanks Retrial.
I did try full wipe by skipping password promptin the new twrp, but it said it couldn't mount the partitions and hence couldn't wipe the partitions. I was going by the steps mentioned in post 4.
Now that I am on crdroid recovery, how do I get back the twrp to retry full wipe through twrp?

Did you tried to reboot again on twrp and try again to wipe/format? there is an issue with twrp by reignz and need to reboot to recovery twice to perform format data etc. Otherwise you can simply use twrp by reignz based on A9 wipe everything/format data/ then flash twrp by reignz based on A12 and flash ROM+Gapps. (I recommended my NikGApps or core if u just want play store)
Use fastboot to flash twrp (you can also check my install custom recovery guide here)

 

[that1]

Did you tried to reboot again on twrp and try again to wipe/format? there is an issue with twrp by reignz and need to reboot to recovery twice to perform format data etc. Otherwise you can simply use twrp by reignz based on A9 wipe everything/format data/ then flash twrp by reignz based on A12 and flash ROM+Gapps. (I recommended my NikGApps or core if u just want play store)
Use fastboot to flash twrp (you can also check my install custom recovery guide here)

Let me try that Retrial. Will report back here.

 

[diskordia84]

How did you install it? Full wipe including system and data? One of the smallest GApps packages? Stock kernel or NGK?

I can tell you exactly what I installed and how if you want, I don't have issues.

I did a full wipe (system, data, cache, internal memory) and format. use nikgapps core, stock kernel, DFE-Pocof1-A13 and magisk.
basically exactly the same procedure as with the twelfth rom. everything works there.

could it be because of the nikgapps? I just noticed that I had installed the twelve version. I completely missed it.