Device can not boot the OS and solution

[monsiu]

Hello, i had tried the latest Evo XYZ buld along with Crdroid and both had bootloops and i think its the QPR2 A14 release cause i could not boot but when i went back to the previous release before QPR2 A14 it boots. I will say that there is something with this release that causes some devices not to boot. I am going to try the previous release for Evo XYZ before this to prove it as i also could not boot into the latest release.

Edit: sorrry the older builds are way larger that i can not flash it on my Samsung Galaxy Tab A8 2021 gta8wifi. This is the device with the issue but i can not tell why but what i know its due to the QPR2 base(which is the only one i can flash). I say this is the issue since other ROMS flashed before this QPR2 release boot normally.

[brusakas]

Unfortunately, Google is so stupid that they majorly changed the devices that could boot to qpr2 or above, however you can "bypass" this by flashing it to the super partition, but don't take it word for word, WiFi or SIM won't be detected, or it might not boot to system. However you can flash the latest version of RisingOS GSI without any problems.

[monsiu]

Unfortunately, Google is so stupid that they majorly changed the devices that could boot to qpr2 or above, however you can "bypass" this by flashing it to the super partition, but don't take it word for word, WiFi or SIM won't be detected, or it might not boot to system. However you can flash the latest version of RisingOS GSI without any problems.

Ah yes. Open source but open however much i want it. Google sucks man. Also yeah I realized its a kernal issue for 4.14 and above on some roms. I went on and stumbled on Rising OS and its beautiful and cool but a bit bloated for its own good that it hangs. I hope other ROMS hop over this hitch honestly cause rising is not that optimized. Also Rising is on hiatus so there is that too.

What could the Rising dev have done to bypass this and what was the issue in their own terms?

[brusakas]

What could the Rising dev have done to bypass this and what was the issue in their own terms?

I don't really know how the RisingOS dev bypassed this, I think it might be because of the vendor partitions or something...

[monsiu]

What could the Rising dev have done to bypass this and what was the issue in their own terms?

I don't really know how the RisingOS dev bypassed this, I think it might be because of the vendor partitions or something...

Yeah anyway more devs are moving through this issue smoothly. saw this other ROM and the dev confirmed its QPR2 and its booting nicely.

https://github.com/ChonDoit/treble_superior_patches/releases/tag/A14-v20240608

[brusakas]

What could the Rising dev have done to bypass this and what was the issue in their own terms?

I don't really know how the RisingOS dev bypassed this, I think it might be because of the vendor partitions or something...

Yeah anyway more devs are moving through this issue smoothly. saw this other ROM and the dev confirmed its QPR2 and its booting nicely.

https://github.com/ChonDoit/treble_superior_patches/releases/tag/A14-v20240608

Update: flash this: https://androidfilehost.com/?fid=6006931924117940902 after you flashed your qpr2 gsi and it will not bootloop, this will change selinux into permissive (there will be no problems)