[HELP] System does not boot after flashing custom OS - Samsung Galaxy A15

Simon Jarret

Member
Sep 3, 2024
6
0
1
Visit site
Flashed TWRP to the samsung galaxy A15 with odin in AP slot.
From within twrp i flashed lineageos to system.
After rebooting to system the device is now stuck in a bootloop.
For testing i tried flashing AOSP instead of lineageos, same result - eternal bootloop.
Why does this happen?
I had some errors showing in twrp when trying to mount data, after formating data and rebooting to twrp this issue was solved, there where no errors shown during the system image flash.
I also reflashed the stock-rom and tried from scratch, flashing twrp with odin, then flashing lineageos within twrp, either there’s something incompatible or it’s me doing something wrong.
ADB sideload returns “failed” in twrp. On the desktop terminal all i see is “Total xfer: 0.00x”
While on twrp "updating partition details, done, full se linux support is present, mtp enabled, starting adb sideload feature, installing zip file sideloadpackage.zip, then at the top it just says “failed”.
In fastbootmode the device will not even show up in the desktop terminal when entering fastboot devices, but it does when switching to adb.
Help would be greatly appreciated at this point.
 

Simon Jarret

Member
Sep 3, 2024
6
0
1
Visit site
Update:
I will try describing the issue more precisely and go into detail.

1) Flash TWRP with Odin in AP slot
1.PNG2) Flashing TWRP recovery successful
2.PNG
3) Phone in downloadmode while flashing twrp
3.jpg
4) After flashing phone shows bootloader warning
4.jpg
5) Samsung warning about non official software
5.jpg
6) Booted into TWRP recovery
6.jpg
7) Selecting lineageos GSI to be flashed as system
7.jpg
8) Flashing process
8.jpg

9) Flashing lineageos successful without any errors
9.jpg

Situation:
After flashing lineage to system and selecting reboot to system, the phone is stuck in a bootloop where it shows only the bootloader warning (4th picture) then it shows samsungs software warning (5th picture) after that the device powers-off itself and reboot, then the process repeats itself forever making the device stuck in a bootloop.

Additional info:
One thing i noticed when flashing twrp with odin, if i do not immediately boot the phone into twrp recovery mode it will instead boot the stock rom - native system os from google android.
After this happens when i power off the phone and then try to boot into twrp i am instead brought to the native android recovery. Is this to be expected?
I'm confused here because from my understanding i should boot into twrp not the standard recovery, otherwise what happened to flashing twrp prior?!
Is there maybe a vb-meta image to some other data that i must add to the various options in odin, BL, CP, CSC, USERDATA?
I really don't know what to do.
 

Forum statistics

Threads
948,843
Messages
6,940,439
Members
3,161,266
Latest member
kasini maansi