Database Develop

Stuck in an odd bootloop, can't get out of it (SGH-T599N)

Hello all. I have been in the Android root community for a little over three years, and even after tinkering with the various devices I've owned since, I cannot get my T599N to come out of its current bootloop.
A background: I had been checking some things in my settings app (running stock, rooted), and I ended up just force closing the settings app to get out of it quickly. Well, this action deleted all of my text messages, and later on it removed my notification bar and made my wallpaper go black. I ended up booting into recovery mode to try and clear the cache. After it cleared, I rebooted, and bam, the bootloop started.
Now, here's what's interesting. The phone is in a bootloop where it displays the first boot message (SGHT599N Galaxy Exhibit or whatever), and then it tries to boot into cwm recovery, displays the loading screen for that for 2 seconds, and just reboots again. I've tried installing a stock rom from ODIN with no success. The rom apparently loads onto the device but it's still in the bootloop. After this, I tried to install philz recovery to try to install a zipped rom to get the device to somehow boot. I tried to factory reset it for installing purposes, and it just reboots. The device will literally clear everything but /data, so that makes me think that it may be a file system problem. I really need to get it to work, as I am out of a phone right now.
Does anyone have any suggestions? I've tried everything I know.

Need assistance reinstalling twrp

For a while I've been using the nonsense rom (provided on this forum) and it's worked fine. Just the other day however I tried turning on my phone, it would get to the boot screen with the animation of the android bot peeing on the apple logo and it would just play that animation over and over until eventually the phone turns off. I figured I just had to restart, but it was the same issue. After trying to reinstall that same rom, I had the same problem. I then tried different roms and the same issue with those, they would get to their respective boot animations and play them until the phone turns off, never going past the boot screen. The one rom that sort of worked with the cayonogenmod 12.1 rom, but the issue with that is after the boot animation, it appears to be starting the set up for the phone, but prompts me to enter a password, which I have no idea what it is. Doing a bit more research, it seems that there may be a problem with twrp and it not formatting (term?) properly.
As of right now, I've done a factory reset on the phone several times to no avail. I just need help getting this phone to work. I've tried looking at a few places and using adb, but the device wasn't found and I didn't have time to look any further because I'm busy with a project I'm working on and with moving. Some places I've looked said to put the phone into usb debug mode, which I can't do since i can't get past any of the boot screens.
Edit / Solved:
I went into twrp and instead of choosing "wipe data" i went to "format data" and that seemed to fix the problem. Although I did have an issue with the nonsense rom, it got past the boot animation, but then gave an error "unfortunately the process com.android.systemui has stopped". I instead installed the raptor rom and it's working fine.

please help a person who doesn't know much about ROMs, kernels, root and so on.

i'm in desperate need for guide please,
so i first off i had some questions (excuse my stupidity but i really couldn't find any answers around)
1) can an never-rooted android device's build number change or is it always the same? like with stock/official updates only?
2) my recovery mode (stock/system recovery) aborts every single installation file (official rom from the Asus website) without even opening the package, it's like i press 'install update from sd card' then as i press the zip file, it immediately says 'installation aborted' without even typing any other significations/steps, and the same happened for the kernals zip files too. so does that mean my recovery mode is corrupted or something is wrong with it?
3) i noticed some slight changes in my recovery since the last bootloop i had and had to use it back then, for example the dead android screen appearing after choosing the recovery mode, at first it used to say 'no command' under the dead android, but this time it doesn't say anything, just the dead android image only until i press power button and volume up to get the recovery options. so does that mean my firmware version changes since last time or my recovery is corrupted or it just means nothing?
4) is there aNYWAY to know my build number of a phone in bootloop (not rooted but bootloader unlocked)
so my initial problem is; i had my asus zenfone go zc500tg on march 2016. it was working so fine actually (using it like a default user not actually knowing anything about roms/flashing/recovery etc) until july of 2017 when i noticed my phone was a bit slow (out of the ordinary) and it used to get SO hot while using it normally and battery drained pretty faster than before, but i didn't know what to do tbh so i just kind of ignored something was off. but not long after these symptoms, the booting of my phone got slower and slower, until it reached its max by staying more than three hours just doing the 'optimizing apps' on the booting screen until it booted, so i thought it was a virus that would go away after a factory reset, and after the reset, it got worse, until it stopped booting and got into a bootloop. I panicked then because i didn't have the slightest idea what was happening until some internet searching guided me into the world of bootloops and custom roms and recovery. so i eventually managed to fix the bootloop and it worked fine for several months until it started to lag again and boot slowly and got the second bootloop, and that i fixed like the first one by installing the rom from the asus website then putting it on the sd card sand flashing it through recovery,
the third bootloop was quite the same, except that i did something additional in recovery mode, i pressed "backup user data" and that did a nandroid backup then i restored it smoothly after flashing the rom.
the fourth bootloop was a bit different, i as always downloaded the same firmware as the times before and flashed it and backed up user data too, but the odd thing that happened was me getting a message box that won't go away that said "unfortunately, the process com.android.phone has stopped" the phone worked but the sim cards weren't recognized and the message box was coming and going every second, so i noticed that the message box went away (nearly) when i got my sd card out, but still the phone app and the sim cards were corrupted,i thought the issue was from my sd card at first but i eventually, (coincidentally tbh) managed to fix it by doing the OTA update that was due, (that bootloop was fixed on the date of January 13th 2018)
then my phone was working so fine and everything was alright.
then shortly after (january 20th 2018) i was on whatsapp normally then suddenly ALL the things on my phone came crashing in front of me : TONS of endless message boxes saying things like "unfortunately, the process com.(any app on my phone) has stopped"
that i literally panicked and tears welled up in my eyes, so i rebooted the phone and while rebooting it did a (relatively quick) "optimizing apps" but as it booted everything was the dreaded same, all the apps crashing, then with the second rebooting was the current bootloop. i thought it was the same as before and just downloaded the usual zip file i use everytime but while flashing it (it did the same as mentioned in question 2 above) but it aborted instantly so i went and downloaded every rom there but it was the same so i went and tried the kernal zips too but always the same (i can't read my build number through the system recovery because it is like not fitting well in the screen si half the number isn't there that's why i asked question number 4)
so can anyone help me please? i'm in desperate need for help, i'm literally crying while typing this because i can't afford another phone and i'm so scared.

also is there a way to install custom recovery to not rooted device while in bootloop?
or if the system recovery was actually corrupted what do i do? :crying:

P10 boot loop and "Getting package info failed"

Dearest forum,
I'm a little desperate:
My P10 randomly crashed yesterday evening without any obvious reason and got stuck in a boot loop for a few rounds. After 10 mins or so, it got its **** together and worked normally throughout today. Unfortunately, in the evening the same problem happened again. This time, I tried the "Download latest version and recovery" in the eRecovery menu but sadly, after installation it got stuck again during reboot (loop) and probably couldn't finish the recovery process completely.
So when I try to do the same thing again now over wifi, it displays the error message "Getting package info failed". The other two options "Emergency backup" (thankfully I used today to create some backups) and "Wipe data/factory reset" are greyed out and not selectable.
I haven't tried a factory reset yet, as I am hoping to still find a solution without losing my data. Is there a possibilty to do what eRecovery is supposed to do via fastboot? The HiSuite unfortunately just says, that my device is not supported for recovery...
Strange thing is, my phone is neither rooted nor unlocked. These times are way in the past for me, so I lost all my knowledge about all that stuff.
I first suspected the battery to have caused the initial problem, since that's the only thing I have changed over the years (Polarcell), but it didn't display any strange behaviour and all cable connections were in place, too. But now, after the unsuccessful recovery attempt, I suspect a soft brick?
Would appreciate any help!

Try to unlock it via potatoNv
(PotatoNV is free)
And then flash any firmware you like
Have a nice day

Phone randomly shows boot animation on custom rom

Hi everyone! I have been suffering with this problem for 2 full days on my S10 (SM-G973F/DS) and now i just have absolutely no idea how to fix it, so I thought it was worth writing about it here.
On stock, I used one old and outdated application that made user certificates system certificates, but which worked. Having tried it on EvolutionX 5.9.1 (Android 11), it brought the phone into a bootloop. I didn’t have a backup and because in order not to go through the installation process on a new one again, I decided that I would try to delete the folders from the data partition ONLY, but after half a day of attempts, nothing happened and I started to install the rom from scratch, but then weird things began to happen: after reinstallation/factory reset, boot animation randomly started (check attached video), which either went into an endless boot, or loaded the system back, but then if boot animation started on loading then this loading become endless, and the buttons (in the system) "Reboot to recovery", "Reboot to bootloader" and etc simply turning off the phone without booting into the recovery or bootloader, and if this happened, then somewhere in 2 minutes after turning it off.
I think i tried almost everything: re-installation according to the instructions, re-installation according to the way I did it before, I even tried to install the stock, and after the recovery again and then rom, but absolutely nothing changes, I cannot use custom rom if it is up to this worked fine and everything started on the same version as I was trying to install like before, I even tried to download the rom installation file again, not installing magisk-patch in boot, installing multidisabler, even find my old backup for TWRP that has every partition, but absolutely nothing changes, maybe someone knows how to fix it?
Thanks in advance!
P.S Stock rom works perfectly (android 11), but i want to use custom anyway (also android 11)