[ROM][AOSP][EAS][13.0][UNOFFICIAL][chiron] Evolution X v7.6.2 TAPSILOG [07/03/2023]

[darkness4every1]

Please, take a logcat of initial boot and config to see if I can see any problem.

File won't upload to here's a link

 

[Huexxx]

File won't upload to here's a link

Well, I can see a crash that must be the reason... but that problem doesn't appear in my case and we're talking about the same device and rom... so

¿Can you create a new gmail account and try to log into it?

Maybe it's related to your google account.

I'll look a bit more into this, but new screen shouldn't affect to this issue.

 

[darkness4every1]

Well, I can see a crash that must be the reason... but that problem doesn't appear in my case and we're talking about the same device and rom... so

¿Can you create a new gmail account and try to log into it?

Maybe it's related to your google account.

I'll look a bit more into this, but new screen shouldn't affect to this issue.

I can't even type my email address, the window will refresh and bootloop, appears for 1 second then goes back to "Getting more info"
The logs are from Ricedroid but it's the same on all your roms.

 

[Huexxx]

Which recovery? Encrypted or not?

 

[darkness4every1]

Which recovery? Encrypted or not?

Orangefox since I can't use anything else (gray screen), the logs are from not encrypted but I've tried both ways

 

[Huexxx]

Well, I have problems with OrangeFox in the past... so I would recommend to use TRWP...

Check if this new TWRP with updated kernel does the job for you.

If you can boot it and see it fine, follow the same steps indicated here and try.

 

[darkness4every1]

Well, I have problems with OrangeFox in the past... so I would recommend to use TRWP...

Check if this new TWRP with updated kernel does the job for you.

If you can boot it and see it fine, follow the same steps indicated here and try.

This release of TWRP works but still getting the same issue on freshly installed rom.

Also something interesting to note, I can't use touchscreen in any recovery but with RiceDroid rom, my touchscreen works in recovery.

 

[Huexxx]

Wow, interesting... but out of time to find out the reason...

Have you tried CherishOS Vanilla + FlameGapps?

MAybe with third party gapps the things go in a different way...

 

[Huexxx]

OP updated!

NOTE: Untested. Please do a backup prior to dirty flash.

 

[Huexxx]

Also, can U check if this feature is available? I'm on CherishOS nowadays and no time to check by myself.

 

[darkness4every1]

Have you tried CherishOS Vanilla + FlameGapps?

MAybe with third party gapps the things go in a different way...

Same result, this never happened on A12 rom

Also, can U check if this feature is available? I'm on CherishOS nowadays and no time to check by myself.

I also tried CherishOS now, but it wasn't present on EvolutionX either iirc

 

[spoo333]

Thank you @Huexxx for all your work. Much appreciated!!!

 

[Huexxx]

OP updated!

 

[11insomnium]

I would like to dirty flash new rom.zip and keep root after updating.
Official Magisk installation guide didn't answer my question:

To keep root, can I use my old magisk_patched-xxx.img, which is the patched boot.img from an older build or do I need to repatch the boot.img from new rom.zip and flash that file?
Sometimes the file size of boot.img changes with new builds. Is it always necessary to create a new associated magisk_patched-xxx.img before dirty flash?

Renaming magisk.apk to magisk.zip and flash it in TWRP is no longer recommended, so I don't want to use this method.

 

[Huexxx]

I would like to dirty flash new rom.zip and keep root after updating.
Official Magisk installation guide didn't answer my question:

To keep root, can I use my old magisk_patched-xxx.img, which is the patched boot.img from an older build or do I need to repatch the boot.img from new rom.zip and flash that file?
Sometimes the file size of boot.img changes with new builds. Is it always necessary to create a new associated magisk_patched-xxx.img before dirty flash?

Renaming magisk.apk to magisk.zip and flash it in TWRP is no longer recommended, so I don't want to use this method.

IMHO, flash the renamed magisk.zip without fear.

I allways do that when I want to use magisk without problems.

 

[11insomnium]

IMHO, flash the renamed magisk.zip without fear.

I allways do that when I want to use magisk without problems.

This way it works faster and easier, but it would still be interesting to understand how it works with the recommended method.

 

[seba1x111]

Hello. Does anyone know how to install a fully working original Pixel Launcher on this rom? I care about the fully functional As A Glace and the ability to select text in the App Drawer.
I tried addons for different gapps, Magisk pixelify plugin, Pixel Launcher Extended, etc. but there are always problems and crashes.
For earlier androids I installed opengapps micro which included Pixel Launcher and everything was fine. But not until the 13th yet.

 

[Huexxx]

OP Updated!

NOTE: It's mandatory to use an updated recovery with quota flag support. I recommend to use TWRP 3.7.0 by Nanhumly

If you stay on older recovery, you can flash the ROM without problems, but next time you access recovery you won't mount /data (and hence internal storage).

Regards!

 

[rmax78]

Thanx for update

 

[rogerty]

OP Updated!

NOTE: It's mandatory to use an updated recovery with quota flag support. I recommend to use TWRP 3.7.0 by Nanhumly

If you stay on older recovery, you can flash the ROM without problems, but next time you access recovery you won't mount /data (and hence internal storage).

Regards!

Hello,

-That twrp can be used with other android 13 roms for chiron (crDroid for example) ?

-The link you posted is a single img file from Google Drive; How can I make sure that "TWRP 3.7.0 by Nanhumly" is a legit file ? I've only found this page (https://github.com/Nanhumly-Staging/twrp_device_xiaomi_chiron), and it seems to be source code for OrangeFox. I don't want to install a recovery without being sure it's safe.

Thanks