Database Users

Other kind of boot loop...

Hi all!
Here is a little problem that i didn't solved.
i have a N910F Note 4 that likes to boot loop . I received it as it is and don't know what caused it(i suppose that was a rooting issue because had the knox value 1)
During the all time, PC and MAC were unable to recognize the Note 4, despite of repeatedly reinstalled drivers(older and newer versions) , Keys and Smart Switch were unable to recognize the device, PC is failing to install the MTP driver for some reason. I changed the USB ports,restarted,updated drivers,updated windows etc. -NO RESULT. BUT : Somehow Keys is able to run recovery and initialization and install it on the device while saying Connecting device... , phone also doesn't appear in device manager or file explorer as external drive.NOTHING! Odin and Jodin says ''added!'' and starts the job with no comments
1. I tried different versions of boot loaders with different versions of ROM (all for my specific model) with no result.
The end of the boot is when Samsung logo ,sound and graphic appears but freezes before actually starting OS, then restarts. IT keeps restarting until battery goes off(even while connected to pc by usb!!! ). Then starts to charge the battery normally.
It boots in recovery and download mode with no problems, it did every time i flashed it…
2. I tried different versions of boot loaders with stock roms , custom kernels etc...and the problem was the same
3. I tried to flash with Odin the stock 4.4.4 without problems but….the problem was the same
4.I tried Device recovery and initialization with Keys and here something interesting happened:
First time when i did it, it went over the samsung logo and booted. I selected language,i skipped wifi network selection and i accepted the user agreement. No matter how fast i was moving, the boot loop didn't went over the user name selection which is after the user agreement. Then freeze and boot again.
Second time when recovered with Keys (tried more stuff in the mean time) it went over the logo and started to update like…''updating applications 2of 17'' the max reach point was ''3 apps of 17'' and then freeze and reboot
I am out of ideas so i suspect that the battery might be dead because it gets empty even if is charging while phone is ''boot looping''. I ordered a battery,should arrive soon.
If that don't work…i am gonna spend some cash and sent it to Samsung for repairs (i bet that it won't be cheap because they will probably tell me that is the motherboard fried so they make you pay for being a bad boy and tried to root). Far as i know is not a brick as long as download mode and recovery works just fine.
Is here someone that has any new ideas for bringing this phone to life? Any help is well received , maybe i skipped something….
Thank you in advance.

Boot into recovery and perform a factory reset, it will wipe the internal storage.

Battlehero said:
Boot into recovery and perform a factory reset, it will wipe the internal storage.
Click to expand...
Click to collapse
That was the first thing i tried , cache wiped also. After every rom when booting failed.

UPPME said:
That was the first thing i tried , cache wiped also. After every rom when booting failed.
Click to expand...
Click to collapse
Uninstall Kies, and install Samsung USB drivers: https://www.androidfilehost.com/?fid=24052804347849220
Take the battery out, leave it for approximately 10 seconds, enter the battery back in.
Hold volume down key + Home key and power on the device.
Then plug the mobile phone into the computer.
Run Odin as Admin: https://www.androidfilehost.com/?fid=24052804347851815
Then flash the firmware in the AP section.
Make sure that the firmware is for your region, you can download it from Sammobile or SamFirm.

i have the same problem, but mine doesn't let the samsung logo finish when it shows the letter S on samsung logo it goes restart again no sound or anything, recovery is accesible, download mode is also accessible, i can flash official firmware and factory reset but nothing change, still stuck in bootloop no one here in xda knows how to fix it i think.. or they just never encounter something like this
i know how to fix an ordinary bootloops or soft bricked.. but this one is different.. i think there's something with note 4 that causes this..

kerbiii said:
i have the same problem, but mine doesn't let the samsung logo finish when it shows the letter S on samsung logo it goes restart again no sound or anything, recovery is accesible, download mode is also accessible, i can flash official firmware and factory reset but nothing change, still stuck in bootloop no one here in xda knows how to fix it i think.. or they just never encounter something like this
i know how to fix an ordinary bootloops or soft bricked.. but this one is different.. i think there's something with note 4 that causes this..
Click to expand...
Click to collapse
Yes, it doesn't go after the Samsung graphics , mine does sound. Goes to app updates only after Kies recovery but doesn't go more far than updating apps 3/17 for ex…crushes there and starts over….weird.
One time i managed to actually go to setup menu, choose country,wifi, device name, and there crushed and started over…. So i am thinking now that the battery might be wasted because i saw posts saying that after the 5.0.1 update many Note 4's went to boot loop and the battery change solved the problem. Now i have new battery coming by post.

Hi I had a similar problem but I do not know if that works but always worth a try
1. download recovery - "twrp-2.8.1.0-trltexx"(.tar) cant post link fresh in forum
2. flash recovery through Odin (AP) ( run as administrator)
3. unplug the cable
4. Reboot to Recovery (home+power+wolume up)
5. Then go to Wipe/Advanced Wipe/check the boxes - Dalvik Cache,System,Data,Cache and Swipe to Wipe
6. Reboot to Download Mode
7. Open Odin ( run as administrator) choise the rom to flash
8 Connect the phone
7. Flash Your Stock Rom
8. Reboot
always in Odin load the file first to flash and then connect the phone
sorry for my English

UPPME said:
Yes, it doesn't go after the Samsung graphics , mine does sound. Goes to app updates only after Kies recovery but doesn't go more far than updating apps 3/17 for ex…crushes there and starts over….weird.
One time i managed to actually go to setup menu, choose country,wifi, device name, and there crushed and started over…. So i am thinking now that the battery might be wasted because i saw posts saying that after the 5.0.1 update many Note 4's went to boot loop and the battery change solved the problem. Now i have new battery coming by post.
Click to expand...
Click to collapse
if you can stay in recovery mode and download mode for more than 10mins i think its not battery problem, i think i have corrupted system files, i left my note 4 to samsung service center a while ago i will get it tom, i just hope they wont charge me too much for it,
uldyzjan said:
Hi I had a similar problem but I do not know if that works but always worth a try
1. download recovery - "twrp-2.8.1.0-trltexx"(.tar) cant post link fresh in forum
2. flash recovery through Odin (AP) ( run as administrator)
3. unplug the cable
4. Reboot to Recovery (home+power+wolume up)
5. Then go to Wipe/Advanced Wipe/check the boxes - Dalvik Cache,System,Data,Cache and Swipe to Wipe
6. Reboot to Download Mode
7. Open Odin ( run as administrator) choise the rom to flash
8 Connect the phone
7. Flash Your Stock Rom
8. Reboot
always in Odin load the file first to flash and then connect the phone
sorry for my English
Click to expand...
Click to collapse
nah it doesnt work thats the first thing I do, that only work on ordinary bootloop

I was stuck in a boot loop the other day trying to flash a stock ROM to get rid of encryption. I tried all the stuff mentioned in this thread which is just standard procedure but I couldn't get past the samsung logo. What it turned out to be was that you need to go to stock recovery after flashing the stock ROM via odin and do a factory data reset then it will boot to the OS. It worked in my case, maybe you can give it a try.

guts100 said:
I was stuck in a boot loop the other day trying to flash a stock ROM to get rid of encryption. I tried all the stuff mentioned in this thread which is just standard procedure but I couldn't get past the samsung logo. What it turned out to be was that you need to go to stock recovery after flashing the stock ROM via odin and do a factory data reset then it will boot to the OS. It worked in my case, maybe you can give it a try.
Click to expand...
Click to collapse
if you read the above post you will know that we already wipe and factory reset,
btw since i was not able to fix it, it brought it to samsung service center and they also cant fix it so they are changing the motherboard, so far they are not charging me anything and just asking to bring my receipt of purchase so it will be under warranty

kerbiii said:
if you read the above post you will know that we already wipe and factory reset,
btw since i was not able to fix it, it brought it to samsung service center and they also cant fix it so they are changing the motherboard, so far they are not charging me anything and just asking to bring my receipt of purchase so it will be under warranty
Click to expand...
Click to collapse
I read the post; however, it did not appear as though you did a factory reset after flashing the stock ROM only before. At any rate at least you're getting a new mobo out of it and problem solved.

guts100 said:
I was stuck in a boot loop the other day trying to flash a stock ROM to get rid of encryption. I tried all the stuff mentioned in this thread which is just standard procedure but I couldn't get past the samsung logo. What it turned out to be was that you need to go to stock recovery after flashing the stock ROM via odin and do a factory data reset then it will boot to the OS. It worked in my case, maybe you can give it a try.
Click to expand...
Click to collapse
guts100 said:
I read the post; however, it did not appear as though you did a factory reset after flashing the stock ROM only before. At any rate at least you're getting a new mobo out of it and problem solved.
Click to expand...
Click to collapse
yes thats the good thing and its under warranty even though im already rooted, with knox 01 and custom binary haha, i was already expecting to pay a huge amount of money but they said they will cover it, so its a blessing, but i hope the OP fixed his problem.

Can't reboot recovery S4

First, thank you to the mods for putting my last post in the right place (and now I know where the right place is).
Anyhoo, my previous problem was a hardware issue that I've had repaired.
Now, this is no longer critical since I bought a replacement phone (Xperia Z if anyone cares) that is happily rooted and running CM. However, I'd still like the S4 rooted with CM and ready to go in an emergency.
The downside of the repair was that the shop I took it too re-flashed it back to stock (I wasn't happy, but hell, it gives me something to do, practically risk free now). Having soft bricked the I9505 three times, I've brought it back to life. However, I'd like to get twrp on there (Honestly, CWM is stepping backwards rather than forwards IMHO, dumbing down to the lowest common denominator). I have the flash files, and for good measure, I have a stock G4 recovery.
Now my problem,. whilst the phone will boot normally without an issue (I said I brought it back from dead), I can't boot to any recovery, either from the phone itself with HW keys, or via adb. It simply sits there at the Samsung logo pretending to boot. This is with both TWRP and stock, so I'm stumped.
I get the Samsung logo, with the little blue too tiny to read text top left, and there it stays. Normal reboot works just peachy with both. Not rooted as best as I can tell (though it should be). i.e. In developer options, none of the root stuff (enhanced reboot, root options etc.) are missing.
So, whilst not critical (it will still be a handy backup phone), any ideas?

you wouldn't have any advanced reboot options unless they were in the rom, and you can't have TWRP without root. maybe the phone shop left you with nothing as a recovery because they forgot ???

In Odin, uncheck everything except f.reset time, flash the tar version of TWRP in Odin, when you see the word "reset" in the status window, remove USB cable from the phone, remove battery, wait 5 seconds, replace battery, use buttons to get into recovery.

Getting into recovery.
*Press the three button combo of vol.up+home+power button
*As soon as Samsung appears relase the combo and in a jiffy press only the volume up+home button.
Hurray! :')

In order:
I've reflashed TWRP, stock, and CWM - all the successful, but same result
No Odin,. Linux user exclusively - so Heimdall
Three button combo starts recovery reboot (the giveaway is the too small to read blue text top left), but there it hangs. Using abd results in the same.
It simply hangs on booting recovery, whichever recovery, but will boot normally without a problem. Tried with and without SIM/SDCard/both/neither.
Probably worth adding, I'm not new to rooting (done it with my last 7 phones, including the one I'm currently using (Xperia Z)), and the S4 was rooted with CM13 before the shop got their hands on it.

After flashing twrp, are you letting the phone auto reboot from Odin?

How many times. Linux user - no Odin (that's Windows) - Heimdall, and it's not just TWRP, it's stock, TWRP and CWM

Personally, recommend trying to flash with Odin. I use Mac OSX myself.

I only have two options for Odin, either via a VM or using wine, and neither lets it detect the phone in download mode.
However, heimdall has always worked well (previously on this phone) so I'm not convinced that's the problem.

Don't know why, but it's finally worked.
How do I mark solved?

SM-G950F won't boot, hard bricked?

I had to reboot my device due to problems with my speaker. Now i'm not able to boot anymore.
I'm only able to get into ODIN Mode, and flashing new FW or TWRP does nothing. It'll flash correctly, but as soon as it sends the reboot command the device powers off and does not boot, and no, it does not reach the "Galaxy s8, powered by android screen".
It does not want to power on, and only responds to the odin button combo, can't boot into recovery either since nothing works.
I was running the latest version of Renovate Ice if that matters.
I've searched trough some other threads, but it seems like i'm the only one that's having this problem.
Any help or thoughts would be greatly appreciated!
Edit 1: I've tried flashing both AQK7 and AQG5. Both flash fine, but as soon as odin sends the reboot command to my phone, it turns off and does not turn on.
Auto Reboot is ticked. Same goes for any version of TWRP, it will flash, but when it has to reboot the device turns off and does not turn on. There's nothing on the screen, its completely black and the only thing that does work is Download Mode. I've also tried ereasing nand, and repartitioning storage. Both seem to have 0 effect. As stated in one of my replies, i was running the latest build of renovate-ice with magisk, no other mods, or themes installed.

Im a bit confused - you can only boot into download mode (not into twrp?) and the phone is in bootloop? Have you flashed anything (mod?) before or activated a substratum theme which could cause this?
The only thing I can think of is a) you delete in twrp file manager the corrupted file, if there is something like this or b) a twrp restore from a backup. Boot into download mode and then do not press vol up to go into odin mode but press vol down to reboot - then immediately press the combo for twrp and you will get to the recovery. This helped my s8 many times when I was in a bootloop and couldnt boot up twrp

FloM94 said:
Im a bit confused - you can only boot into download mode (not into twrp?) and the phone is in bootloop? Have you flashed anything (mod?) before or activated a substratum theme which could cause this?
The only thing I can think of is a) you delete in twrp file manager the corrupted file, if there is something like this or b) a twrp restore from a backup. Boot into download mode and then do not press vol up to go into odin mode but press vol down to reboot - then immediately press the combo for twrp and you will get to the recovery. This helped my s8 many times when I was in a bootloop and couldnt boot up twrp
Click to expand...
Click to collapse
Thanks for the reply! Other than using the Renovate-Ice rom, and running magisk the thing was pretty much stock. wasn't messing around in twrp either. Its not stuck in a bootloop either, it just refuses to do anything other than go in and out of DL mode. The phone does not respond to any button imputs other than DL mode. As stated in the OP it does not boot at all, just a black screen. i've already tried to reflash a stock FW and TWRP, but that does not seem to work...

try the method I did - this is the last thing I could think of, before reflash the whole phone with odin

More info about your speaker problem

popmpopm said:
More info about your speaker problem
Click to expand...
Click to collapse
There isn't much to say about the problem ,it just stopped working, hence why i rebooted the phone, and ran in to the problem i'm having right now.

FloM94 said:
try the method I did - this is the last thing I could think of, before reflash the whole phone with odin
Click to expand...
Click to collapse
Doesn't work sadly, but thanks for the help anyways!

but you havent installed Viper4Arise or anything like that?
Because of this my speaker also stopped working a few weeks ago

if you can get into download mode then get into download mode and leave phone, then download samsung smart switch for your pc (older version like 4.1.17022_20 from here http://www.filehorse.com/download-samsung-smart-switch/29268/ that allows phone based recovery), once installed open it, then click on more at top right, (do not update the software if you get a prompt) select emergency device recovery...., then click on right tab (device initialisation) and fill in your phone details etc., connect your phone (in download mode) and follow the process, maybe it works, you'll need to root and install TWRP again but thats no big issue.

Jostian said:
if you can get into download mode then get into download mode and leave phone, then download samsung smart switch for your pc (older version like 4.1.17022_20 from here http://www.filehorse.com/download-samsung-smart-switch/29268/ that allows phone based recovery), once installed open it, then click on more at top right, (do not update the software if you get a prompt) select emergency device recovery...., then click on right tab (device initialisation) and fill in your phone details etc., connect your phone (in download mode) and follow the process, maybe it works, you'll need to root and install TWRP again but thats no big issue.
Click to expand...
Click to collapse
I've tried this just now, and it still gives me the same result, it goes trough the process, but as soon as it has to reboot it doesn't boot anymore.
Thanks for the suggestion though!

FloM94 said:
but you havent installed Viper4Arise or anything like that?
Because of this my speaker also stopped working a few weeks ago
Click to expand...
Click to collapse
i think phone is damaged by water or dropped s8 so fragile phone ! its happen to me with s5 the phone dead after speaker problem !!

popmpopm said:
i think phone is damaged by water or dropped s8 so fragile phone ! its happen to me with s5 the phone dead after speaker problem !!
Click to expand...
Click to collapse
I've had a case on the phone since day one, and I've checked for water damage, but there is non. The tab that is supposed to indicate it is untouched. But thanks for your input! I appreciate it

I have the same problem. Its look like is bootloader issue. try flash this soft :
G950FOWA1AQCC_Recovery
But if you are on newest rom it wont work.

Hello, you can solve this problem?

Galaxy S8 hardcore bootloop

Hi everyone,
When I tried to restart my Galaxy s8 it entered some kind of hardcore bootloop where I couldn't stop it from looping except by entering the download mode, letting it drain the battery or simply disconnecting the battery. When I exit the download mode it will just continue looping. It is also impossible to enter the recovery menu, which makes things much worse.
I have tried opening the phone and disconnecting everything except power supply (either battery or charger) and screen to see whether some detachable component is failing it (camera, speaker, etc.). But nothing.
I have also tried reinstalling the firmware (BL + CP + AP + HOME_CSC), it installs successfully but it doesn't fix the bootloop. I have also tried two most recent firmware, also without success. Somewhere on the Internet I have found a recommendation to install the firmware from June 2017 which I have tried but it doesn't work anymore because it's not possible to install earlier version of firmware on Samsung phones anymore (since November 2019 I believe).
Now I have started to believe that this could be a motherboard failure but it doesn't really make whole lot of sense because the phone can enter the download mode and reinstall firmware just fine. Or maybe there is a component which can make it able to enter the download mode, but nothing else would work?
Has anyone experienced something like this? How could it be fixed? Any recommendations? Is there any hope?
Edit: The phone has never been rooted, means it is in its original software state (currently on Android Pie with build number G950FXXS8DTC1). Is there any way to install anything on it (custom ROM, TWRP, etc.)?

Come on guys! Please don't tell me that I've tried everything and exhausted all the possibilities...

If there is still warranty on the phone, then send it in for repair. If there isn't, then I would take it to a repair shop and see what they can do about it. It is wierd that you can enter download mode, but can't flash stock firmware. I think it might be a motherboard problem

Nevin1901 said:
If there is still warranty on the phone, then send it in for repair. If there isn't, then I would take it to a repair shop and see what they can do about it. It is wierd that you can enter download mode, but can't flash stock firmware. I think it might be a motherboard problem
Click to expand...
Click to collapse
Unfortunately, there's no warranty and I'm pretty sure no one would repair this kind of failure for a price lower than the price of a used and fully functional Galaxy s8.
Yes, I can enter the download mode and I CAN flash stock firmware, but I can flash only the ones which are newer or the same as the one installed on the phone.
Yes, most probably it's a motherboard failure. In some YouTube videos I have seen people fixing similar issues by replacing the CPU (which I am unable to do by myself). Other suggestion I found on iFixit says that I could soak my motherboard in 99% Isopropyl alcohol and leave it overnight in it (I am going to try this if I get my hands on the alcohol).
BTW: One interesting thing I experienced while flashing the phone without its battery connected is that the phone's screen will go black when you press 'Start' button in Odin, but nevertheless the installation will finish normally and you can track its progress in Odin. At the end you'll need to restart your phone manually.

roberta-xda said:
Hi everyone,
When I tried to restart my Galaxy s8 it entered some kind of hardcore bootloop where I couldn't stop it from looping except by entering the download mode, letting it drain the battery or simply disconnecting the battery. When I exit the download mode it will just continue looping. It is also impossible to enter the recovery menu, which makes things much worse.
I have tried opening the phone and disconnecting everything except power supply (either battery or charger) and screen to see whether some detachable component is failing it (camera, speaker, etc.). But nothing.
I have also tried reinstalling the firmware (BL + CP + AP + HOME_CSC), it installs successfully but it doesn't fix the bootloop. I have also tried two most recent firmware, also without success. Somewhere on the Internet I have found a recommendation to install the firmware from June 2017 which I have tried but it doesn't work anymore because it's not possible to install earlier version of firmware on Samsung phones anymore (since November 2019 I believe).
Now I have started to believe that this could be a motherboard failure but it doesn't really make whole lot of sense because the phone can enter the download mode and reinstall firmware just fine. Or maybe there is a component which can make it able to enter the download mode, but nothing else would work?
Has anyone experienced something like this? How could it be fixed? Any recommendations? Is there any hope?
Edit: The phone has never been rooted, means it is in its original software state (currently on Android Pie with build number G950FXXS8DTC1). Is there any way to install anything on it (custom ROM, TWRP, etc.)?
Click to expand...
Click to collapse
I have an S8 with a similar issue. I can get to recovery menu but following similar steps to above by flashing combination firmware and still got stuck in bootloop. Subscribing to this thread in case anyone has a fix.

Just wanted to share a video I found. This is exactly how my s8 bootloops: https://youtu.be/gBlIcAJzgVA?t=5
PS: Obviously, the solution explained in the video didn't work for me.
PS2: This issue started by just restarting the phone. Before the restart it was in a perfect state, fully working, never had any hardware issues. Although there were some software issues introduced by an update (October or November 2019 I think) which made my phone need to restart 2 times to fully boot once if I wanted to restart it or turn it on after it was turned off. But those software issues were solved by a latter software update.

kjaved373 said:
I have an S8 with a similar issue. I can get to recovery menu but following similar steps to above by flashing combination firmware and still got stuck in bootloop. Subscribing to this thread in case anyone has a fix.
Click to expand...
Click to collapse
i know it's already an old comment, but was your phone also completely stock?

Leberkuchen said:
i know it's already an old comment, but was your phone also completely stock?
Click to expand...
Click to collapse
Yeah I believe so.

troubleshooting, bricked overnight

Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.

PinkElf said:
Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.
Click to expand...
Click to collapse
Hi, try to flash the stock firmware otherwise I really don't know :/

I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?

PinkElf said:
I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?
Click to expand...
Click to collapse
Are you using Lineage OS? If yes, then definitely yes. On my Xiaomi, I couldn't get into fastboot mode or into recovery, I don't know why and somehow I got there, I don't even know how I think I held the power mode for a long time and when the phone turned on I held the volume up button to get into recovery finally succeeded on the umpteenth attempt and from recovery I restarted the phone in fastboot mode and flashed the stock firmware. And yes, being able to boot your phone into fastboot is a good sign. It would be worse if it wasn't possible.

I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.

PinkElf said:
I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.
Click to expand...
Click to collapse
Yes, you can use download mode to install the firmware via Odin. Look

That means giving up hope for my personal data...
But even if I want to do this, I run into the problem, that I can't install anything due to "could not find PIT partition"...