Database Users

Resurrection Remix ROM 6.8 Build running Kernel 6.2 - Bootloop Issue Zenfone 5

Hello, Newbie Here!
So I recently flashed the Resurrection Remix ROM Build 6.8 and Kernel 6.2.
The Build is rather stable and In my honest opinion better than CM12.1 which I was on previously.
So the normal functions of the phone are normal and I feel this is a much stable build. I use a ASUS Zenfone 5(ASUS_T00F)
But I face random reboots where the phone restarts itself and gets stuck at the boot. Only when i try to force reboot from the bootloop screen does the phone restart normally and even that takes three or four attempts. First I thought it was just getting used to the new Kernel then when this started occurring frequently I became more aware that this might just be a potential risk.
Today afternoon, My Phone was literally stuck at bootloop for 2 hours.... Only when I tried to do three-four manual forced reboots by pressing my power key and with each instance entering the TWRP mode and doing a dalvik and cache wipe only then was I able to boot up my phone normally.....It totally drained the battery though. I was at 78% and when my phone finally booted up I was shocked to see just 1% charge left.
Everytime this issue occurs...either the phone is completly stuck in bootloop or goes to the "Android is upgraing your apps" notification and then again comes back to the bootloop.
I have also done two fresh flashes before this as well so I know its got nothing to do with a dirty flash.
I then started googling for the same issue that other Zenfone 5 users might be experiencing but to my shock...No threads on it could be found with the issue that Im experiencing.
Pretty frustrated right now I have no clue what to do.
Donot want to go back to STOCK ROM..It sucks.
Please help Guys!

Hello.
You should try to format system and reinstall the rom + xposed. After that you can format data, cache, internal storage. I hope that it will help you.
And did you have this problem on CM12.1?

tank0412 said:
Hello.
You should try to format system and reinstall the rom + xposed. After that you can format data, cache, internal storage. I hope that it will help you.
And did you have this problem on CM12.1?
Click to expand...
Click to collapse
Yup. Tried all this.

Just format again and re flash rom with xposed it fixed my bootloop.

The solution is,
Go back to stock rom. ???

Can anyone tell me how to back stock ROM from resurrection remix???

yasin0005 said:
Can anyone tell me how to back stock ROM from resurrection remix???
Click to expand...
Click to collapse
Download latest firmware from Asus' Support Page. And flash it via adb sideload.

I m now on Stock Rom without any problems no screen freeze no bootloops ...

can't update past LineageOS 14.1 20171013

Thanks to XDA, I've been running LineageOS 14.1 on my LEX727 for months now, updating to most nightly releases with no issues. However, when the phone rebooted after updating to the 10/20/17 nightly, it got stuck on the boot animation screen (green circle moving right to left on the arc) and would go no further. I rebooted into TWRP and flashed back to 10/13 which has been working fine. Same results after attempted updates to the 10/27 and 11/3 releases. I even tried a manual update from TWRP using USB OTG with the same result.
Any ideas of what's gone wrong here? Anything I can try? All I know to do at this point is wipe and install clean but I'd rather not if possible. Thanks!

fraxby79 said:
Thanks to XDA, I've been running LineageOS 14.1 on my LEX727 for months now, updating to most nightly releases with no issues. However, when the phone rebooted after updating to the 10/20/17 nightly, it got stuck on the boot animation screen (green circle moving right to left on the arc) and would go no further. I rebooted into TWRP and flashed back to 10/13 which has been working fine. Same results after attempted updates to the 10/27 and 11/3 releases. I even tried a manual update from TWRP using USB OTG with the same result.
Any ideas of what's gone wrong here? Anything I can try? All I know to do at this point is wipe and install clean but I'd rather not if possible. Thanks!
Click to expand...
Click to collapse
I'd say do a clean install. If i have any issues with a rom booting i'll factory reset and install again. If i still have issues i'll just use another rom.

fraxby79 said:
Thanks to XDA, I've been running LineageOS 14.1 on my LEX727 for months now, updating to most nightly releases with no issues. However, when the phone rebooted after updating to the 10/20/17 nightly, it got stuck on the boot animation screen (green circle moving right to left on the arc) and would go no further. I rebooted into TWRP and flashed back to 10/13 which has been working fine. Same results after attempted updates to the 10/27 and 11/3 releases. I even tried a manual update from TWRP using USB OTG with the same result.
Any ideas of what's gone wrong here? Anything I can try? All I know to do at this point is wipe and install clean but I'd rather not if possible. Thanks!
Click to expand...
Click to collapse
I am in the same situation. Have tried all combinations of wiping and resetting with all 3 of the latest nightlies and still cannot boot. I can successfully boot into a stock rom but, I'd rather not. I guess I will go back to the 10/13 nightly since it worked (mostly) before this debacle. Hopefully next week's update will solve this problem.

Thanks for your reply, islandlife98. I'm not super-confident at this ROM thing yet so backing up, wiping and reinstalling is something I'd undertake reluctantly. I was hoping this was a common situation with a simple fix that I just had been unable to find. Always prefer to actually solve a problem if possible rather than just wipe it out. (Although when it comes to tech, wiping it out is often the best or only solution. Almost always the quickest.)
JBealZy, thank you for letting me know you're in the same boat! After seeing no mention of this issue here, I assumed it was some weird glitch with my phone rather than a problem with the updates. If you've done a full wipe and re-install but still haven't been able to boot into any of the last three releases then I'm glad I hesitated. (That was a concern I'd had: that it might not work even after a clean install.) Think I'll stick with 10/13 for now and keep trying the new releases; easy enough to roll back if it fails now that I've figured it out.

Lmao same problem here with the 2017-11-11 and 2017-11-03 udpate. Not tested yet with 2017-10-27 or 2017-10-20 but that's my last choice because after 2017-10-13 update all links are removed. I do a clean install every time .. What other rom is better ?
Problem resolved .. i have wiped internal storage too and able to install the last version. I think i'm gonna use another ROM because i don't really want to reinstall all of my applications everytime i do an update. :/

Deediezi said:
Lmao same problem here with the 2017-11-11 and 2017-11-03 udpate. Not tested yet with 2017-10-27 or 2017-10-20 but that's my last choice because after 2017-10-13 update all links are removed. I do a clean install every time .. What other rom is better ?
Problem resolved .. i have wiped internal storage too and able to install the last version. I think i'm gonna use another ROM because i don't really want to reinstall all of my applications everytime i do an update. :/
Click to expand...
Click to collapse
I am using Paranoid ( latest version) and everything works flawlessly.
Sent from my LEX727 using XDA Labs

Deediezi said:
Lmao same problem here with the 2017-11-11 and 2017-11-03 udpate. Not tested yet with 2017-10-27 or 2017-10-20 but that's my last choice because after 2017-10-13 update all links are removed. I do a clean install every time .. What other rom is better ?
Problem resolved .. i have wiped internal storage too and able to install the last version. I think i'm gonna use another ROM because i don't really want to reinstall all of my applications everytime i do an update. :/
Click to expand...
Click to collapse
Another victim! So weird, I wonder what's going on there. None of the updates since my original post have worked so I've come to the conclusion that I'm going to have to do a clean install. Just need to find a time do it. Good to hear it worked for you.
LineageOS is the only ROM I've tried but since I have to wipe my phone anyway I may try some others. Paranoid Android looks interesting and Tsongming says it's working well.

fraxby79 said:
Another victim! So weird, I wonder what's going on there. None of the updates since my original post have worked so I've come to the conclusion that I'm going to have to do a clean install. Just need to find a time do it. Good to hear it worked for you.
LineageOS is the only ROM I've tried but since I have to wipe my phone anyway I may try some others. Paranoid Android looks interesting and Tsongming says it's working well.
Click to expand...
Click to collapse
Yea i'm downloading Paranoïd right now for testing it .. Don't want a broken operating system on my phone haha

If anyone's still interested, I first tried flashing Lineage after wiping all but internal storage and still couldn't get past the boot animation. Then did a full factory-reset wipe including the internal storage, re-flashed, and it finally booted. The first OTA update since then came through today and went off without a hitch so all seems well for now.
I did take a look at Paranoid before going back to Lineage. One big reason I use a custom ROM is to get security updates quickly and LOS reports the security patch level in the settings; I couldn't find this info in PA. Also, I use a pattern to unlock my phone and there didn't appear to be a way use a larger grid than the default 3x3. On the plus side (sort of), PA includes the LeEco remote control app, which seems to be the only way to use the IR hardware on this phone, but it asks for more permissions than I want to give (which, of course, is not PA's fault). So admittedly I didn't really give it a full and fair trial but those few little issues sent me back to the (usually) reliable familiarity of LOS.

I received a new LEX722 yesterday. The TWRP for zl1 is working fine, but I cannot get lineagos working.
I deleted:
- dalvik,
- system,
- cache
- data
- and also the internal storage
after rebooting into twrp I enabled usb debugguung and pushed the lineageos and gapps images via adb push to the phone.
I installed lineageos and gapps nano, but after booting to system, I get stuck in a black screen looping to a dark grey luminated display (no graphics at all).

Heistergand said:
I received a new LEX722 yesterday. The TWRP for zl1 is working fine, but I cannot get lineagos working.
I deleted:
- dalvik,
- system,
- cache
- data
- and also the internal storage
after rebooting into twrp I enabled usb debugguung and pushed the lineageos and gapps images via adb push to the phone.
I installed lineageos and gapps nano, but after booting to system, I get stuck in a black screen looping to a dark grey luminated display (no graphics at all).
Click to expand...
Click to collapse
Sorry, can't help you with that since I have a LEX727 which is apparently quite different from the LEX722. Official LineageOS is only supported on the LEX720 and LEX727: [ https://wiki.lineageos.org/devices/zl1 ]. The LEX722 (Elite) has it's own section here on the LeEco Pro 3 forum so check that out and see what they've come up with.

ZC553KL twrp failure - help!

Hello! Long time lurker on here but first time posting. I follow this guide to unlock bootloader and install twrp on the zc553kl. https://forum.xda-developers.com/zenfone-3/how-to/zenfone-3-max-zc553kl-bootloader-unlock-t3691837
It kind of worked, and it did flash twrp. The only problem is that the twrp although launching, didnt seem to have permissions to access storage, probably due to a data encryption problem. all the storages had 0mb sizes and i couldn't do anything.
So naturally i googled my problem and tried a few methods.
Nothing seemed to work, and i ended up doing an advance wipe. That also failed and it said it didnt have access or permission to do it (something along those lines). Next day i decide to try again and now my internal storage seemed to show.
So i ended up formatting it, and while the files seem to be still there, i changed .ext4 to .ext2 and back again, and then it stopped recognizing the stock rom i still had installed. Please note that before all of this, although twrp didnt work properly, the phone still worked fine and booted into android. My problem is now the stock rom is gone, twrp says no OS installed, and i have tried my best to reinstall the stock rom, but that hasn't worked. Any ideas or help would be welcome thanks guys

Nyoxx said:
Hello! Long time lurker on here but first time posting. I follow this guide to unlock bootloader and install twrp on the zc553kl. https://forum.xda-developers.com/zenfone-3/how-to/zenfone-3-max-zc553kl-bootloader-unlock-t3691837
It kind of worked, and it did flash twrp. The only problem is that the twrp although launching, didnt seem to have permissions to access storage, probably due to a data encryption problem. all the storages had 0mb sizes and i couldn't do anything.
So naturally i googled my problem and tried a few methods.
Nothing seemed to work, and i ended up doing an advance wipe. That also failed and it said it didnt have access or permission to do it (something along those lines). Next day i decide to try again and now my internal storage seemed to show.
So i ended up formatting it, and while the files seem to be still there, i changed .ext4 to .ext2 and back again, and then it stopped recognizing the stock rom i still had installed. Please note that before all of this, although twrp didnt work properly, the phone still worked fine and booted into android. My problem is now the stock rom is gone, twrp says no OS installed, and i have tried my best to reinstall the stock rom, but that hasn't worked. Any ideas or help would be welcome thanks guys
Click to expand...
Click to collapse
i downloaded a previous rom version from asus site and that flashed fine.

No Sim on Pie but works fine on Oreo backup??

Hi all
So i installed AICP 14, all worked fine, wanted Dt2W so put Fk r77 kernel on and within an hour i got a reboot while talking on the phone, then a strange error with my keyboard not working (not sure if both problems were kernel related but never had them before).
I had done a twrp backup before installing the kernel so i thought i can live without Dt2W i restored from the backup, BUT this i when i realised i had fkd up because i hadn't taken off my pattern lock before doing the backup.....so the restore didnt work(got an error at end of running the restore and phone hung on google screen)
So luckily i still had my Oreo back up, restored that and that works fine.
But now when i try a fresh install of any Pie rom (Tried AICP and RR) the sim card isnt detected? Did i quick google yesterday and ran some #*#*4636*#*# service code which reported there was no IEMI number?
So is it a EFS partition problem?
Tia.

r3k0 said:
Hi all
So i installed AICP 14, all worked fine, wanted Dt2W so put Fk r77 kernel on and within an hour i got a reboot while talking on the phone, then a strange error with my keyboard not working (not sure if both problems were kernel related but never had them before).
I had done a twrp backup before installing the kernel so i thought i can live without Dt2W i restored from the backup, BUT this i when i realised i had fkd up because i hadn't taken off my pattern lock before doing the backup.....so the restore didnt work(got an error at end of running the restore and phone hung on google screen)
So luckily i still had my Oreo back up, restored that and that works fine.
But now when i try a fresh install of any Pie rom (Tried AICP and RR) the sim card isnt detected? Did i quick google yesterday and ran some #*#*4636*#*# service code which reported there was no IEMI number?
So is it a EFS partition problem?
Tia.
Click to expand...
Click to collapse
Very likely corrupt radio. Try reflash stock rom before trying top flash a pie rom

ok, downloaded the last stock from google, twrp gave an error when trying to install it? wrong kind of zip ?

r3k0 said:
ok, downloaded the last stock from google, twrp gave an error when trying to install it? wrong kind of zip ?
Click to expand...
Click to collapse
Late Reply...Just Read it today
Stock factory files can be flashed through fastboot don't you know that?
And your problem got solved or not?

S5, Flashed TWRP and custom ROM, restored stock from another phone, how to unmess?

Hello.
This is my first post as I've done everything myself till now, but now I'm really lost in some uncharted territory.
All I wanted is to have a second DeGoogled phone and I messed my Samsung Galaxy S5 beyond my understanding
So, I flashed TWRP to my SM-G900F klte through Odin and then installed /e/ ROM through zip method and everything was working fine, then I wanted to flash Intelli kernel, but I got an error saying "Digest failed to match on '/external-sd/Intelli-Kernel-v15-klte.zip'. E: Aborting zip install: Digest verification failed. Error installing zip file '/external_sd/Intelli-Kernel-v15-klte.zip'". I double checked the md5 of TWRP, /e/ and Intelli Kernel zip's, reflashed TWRP, flashed IceMan's TWRP recovery, wiped all partitions, formatted data and re-installed /e/, tried Havoc ROM, but I still got the same message. The problem wasn't only with the kernel, but also with some (not all) other zip's like A2camforS5_TWRP_v1.4.zip and even Magisk (which flashed fine) modules like A2camforS5_Magisk_v2.zip were not flashing (the procedure got through, but once the phone restarted the module wouldn't show up). On my previous SM-G900F klte phone everything was working fine. (And yes, TWPR's check md5 option was disabled, so this wasn't the problem)
After a bit of chatting on Intelli kernel and /e/ Telegram support groups I found out it wasn't the kernel or /e/ problem and that I should go back to stock and start all over. I had a full NANDroid backup from my previous phone so I renamed the backup folder to match the new phone serial (so it would show the partitions to restore in TWRP) and as I (and nobody else) didn't know where the problem was I restored all partitions. Everything went through as it should except modem, which showed an error saying something about being read-only and efs, which went half way through and then gave an error I don't remember (but can reproduce if needed). The phone wouldn't boot to OS (it was stuck on SAMSUNG logo), so I re-flashed TWRP and /e/ again and tried to flash the kernel or other zips but they were still giving me "digestion" problems... but it got worse! Now when I boot to /e/ I'm not even able to use the phone normally as a pop-up saying "Bluetooth app has crashed" and "Bluetooth app keeps crashing" shows up continuously even if Bluetooth as other wireless connection work just fine. Did I mess something up with the unfinished efs restore?
How can I diagnose the problem and unmess my phone? What steps should I take? I'm afraid of bricking my phone if I just start to do random stuff so any useful information would be appreciated! Please help!
EDIT: Even if my description of the procedure looks like I flashed a ton of stuff all at once I have just WRITTEN A RESUME AS CONDENSED AS POSSIBLE - the procedure took me more than a week of flashing ONE THING AT A TIME and testing if everything works fine. At no point in my flashing procedure there were more than three things present on my phone: TWRP, ROM and MAGISK as kernel and camera mod refused to flash anyway. To exclude Magisk being a problem I clean installed everything so I had just TWRP and ROM and I was getting the same problem. Then I reflashed TWRP only, using the IceMan version (because it presumably solves all flashing problems) retested, then flashed /e/ only, retested, Havoc only, retested... well, you got the picture!
I was doing everything under the guidance of Intelli kernel Telegram support group members until I understood the problem was not the kernel, nor TWRP/IceMan, nor /e//Havoc and went with the stock recovery through TWRP and messed my phone beyond Intelli kernel Telegram group's scope.

ShalaMala said:
Hello.
This is my first post as I've done everything myself till now, but now I'm really lost in some uncharted territory.
All I wanted is to have a second DeGoogled phone and I messed my Samsung Galaxy S5 beyond my understanding
So, I flashed TWRP to my SM-G900F klte through Odin and then installed /e/ ROM through zip method and everything was working fine, then I wanted to flash Intelli kernel, but I got an error saying "Digest failed to match on '/external-sd/Intelli-Kernel-v15-klte.zip'. E: Aborting zip install: Digest verification failed. Error installing zip file '/external_sd/Intelli-Kernel-v15-klte.zip'". I double checked the md5 of TWRP, /e/ and Intelli Kernel zip's, reflashed TWRP, flashed IceMan's TWRP recovery, wiped all partitions, formatted data and re-installed /e/, tried Havoc ROM, but I still got the same message. The problem wasn't only with the kernel, but also with some (not all) other zip's like A2camforS5_TWRP_v1.4.zip and even Magisk (which flashed fine) modules like A2camforS5_Magisk_v2.zip were not flashing (the procedure got through, but once the phone restarted the module wouldn't show up). On my previous SM-G900F klte phone everything was working fine.
After a bit of chatting on Intelli kernel and /e/ Telegram support groups I found out it wasn't the kernel or /e/ problem and that I should go back to stock and start all over. I had a full NANDroid backup from my previous phone so I renamed the backup folder to match the new phone serial (so it would show the partitions to restore in TWRP) and as I (and nobody else) didn't know where the problem was I restored all partitions. Everything went through as it should except modem, which showed an error saying something about being read-only and efs, which went half way through and then gave an error I don't remember (but can reproduce if needed). The phone wouldn't boot to OS (it was stuck on SAMSUNG logo), so I re-flashed TWRP and /e/ again and tried to flash the kernel or other zips but they were still giving me "digestion" problems... but it got worse! Now when I boot to /e/ I'm not even able to use the phone normally as a pop-up saying "Bluetooth app has crashed" and "Bluetooth app keeps crashing" shows up continuously even if Bluetooth as other wireless connection work just fine. Did I mess something up with the unfinished efs restore?
How can I diagnose the problem and unmess my phone? What steps should I take? I'm afraid of bricking my phone if I just start to do random stuff so any useful information would be appreciated! Please help!
Click to expand...
Click to collapse
Idk what your phone's actual issue is, but you should probably not have restored efs from previous phone.
At this point, I would probably Odin back to latest stock firmware, to see if the phone will boot and recognize sim card. If so, I would go from there, flash latest official TWRP, format data, and either restore the backup sans modem and efs, or try a different ROM.
DO NOT INSTALL TWRP APP
Also, try to do things in small traceable steps to make it easier to see what is causing your problem.
Eg:
Flash just the bare ROM, nothing else, no Magisk, no hacky crap, just the ROM. Test it.
If everything is satisfactory, then try the next step and test again, working your way up to your desired ROM/kernel/Magisk/apps solution that makes you happy.
For maximum stability it's always preferable to format data (Advanced wipe>format>type yes) when flashing a ROM to ensure a clean slate for everything.
Also, try not too let your phone get too hot with lots of flashing. I've seen good phones do odd stuff when overheated.
That's all the advice I can think of right now, how it is some help to you.
Good luck! :good:

you should probably not have restored efs from previous phone.
Click to expand...
Click to collapse
Yeah, I assume that was the stupidest thing, but an online guide suggested it's ok to restore from another phone's NAND backup as long as it's the same model, so I thought it was safe.
At this point, I would probably Odin back to latest stock firmware, to see if the phone will boot and recognize sim card.
Click to expand...
Click to collapse
My phone works fine with /e/ ROM as before - SIM, Wi-Fi, Bluetooth and all, there is just a constant pop-up saying that the Bluetooth app has crashed interfering with everything I do that wasn't present before the stupid restore to stock.
If so, I would go from there, flash latest official TWRP, format data, and either restore the backup sans modem and efs, or try a different ROM.
Click to expand...
Click to collapse
Did all this except trying a different ROM, because it wasn't producing the Bluetooth app has crashed problem before restoring to stock, so I assumed it's not a ROM problem. The digest problem was present also in Havoc ROM.
DO NOT INSTALL TWRP APP
Click to expand...
Click to collapse
Why? Is this a general issue or just a problem in my case? Anyway I have disabled the option before restarting to system.
Also, try to do things in small traceable steps to make it easier to see what is causing your problem. Eg: Flash just the bare ROM, nothing else, no Magisk, no hacky crap, just the ROM. Test it.
Click to expand...
Click to collapse
Yeah, I was doing the things one step at a time, my message is just a condensed resume of all the steps I did to make it shorter. I stopped adding things once I was unable to flash the kernel, camera mod and Magisk modules - I didn't just add everything I was trying to understand if the problem was just with kernel or my phone wouldn't flash also some other zips.
If everything is satisfactory, then try the next step and test again, working your way up to your desired ROM/kernel/Magisk/apps solution that makes you happy.
Click to expand...
Click to collapse
Yes, yes, that was the plan, but now the bare ROM doesn't want to work anymore without giving me Bluetooth app crashes
For maximum stability it's always preferable to format data (Advanced wipe>format>type yes) when flashing a ROM to ensure a clean slate for everything.
Click to expand...
Click to collapse
I did that before every flash.
Also, try not too let your phone get too hot with lots of flashing. I've seen good phones do odd stuff when overheated.
Click to expand...
Click to collapse
Good to know!
That's all the advice I can think of right now, how it is some help to you. Good luck!
Click to expand...
Click to collapse
Thank you. So now I flashed the latest .tar.md5 file for my model and my CSC through Odin and the phone wouldn't boot to stock ROM (I guess because it had /e/ Pie on it already and the latest stock ROM is just Marshmallow so it's considered downgrading), got stuck at SAMSUNG logo and phone went extremely hot. I pulled out the battery, went in download mode, flashed TWRP, wiped all partitions, formatted data, flashed /e/, booted /e/, the message about Bluetooth app crashing persists, went to TWRP, tried to flash Intelli kernel, got the "digest" error, tried camera mod, got "digest error" again, magisk flashed fine, so flashing works... so what now? I checked inside the .tar.md5 file and there is no efs partition so I guess it wasn't written over by flashing through Odin
Should the phone be able to boot to stock? Is that even necessary - would it fix anything?

ShalaMala said:
My phone works fine with /e/ ROM as before - SIM, Wi-Fi, Bluetooth and all, there is just a constant pop-up saying that the Bluetooth app has crashed interfering with everything I do that wasn't present before the stupid restore to stock.
Click to expand...
Click to collapse
"If so, I would go from there, flash latest official TWRP, format data, and either restore the backup sans modem and efs, or try a different ROM."
A: Did all this except trying a different ROM, because it wasn't producing the Bluetooth app has crashed problem before restoring to stock, so I assumed it's not a ROM problem. The digest problem was present also in Havoc ROM.
Click to expand...
Click to collapse
Maybe try flashing just the baseband with latest modem, etc from haggertk's archive on AFH, here:
https://androidfilehost.com/?w=files&flid=59628
You can flash that without wiping and it only touches the baseband/firmware files, so should not affect anything else
"DO NOT INSTALL TWRP APP"
A: Why? Is this a general issue or just a problem in my case? Anyway I have disabled the option before restarting to system.
Click to expand...
Click to collapse
It's a general issue. The app is bloatware and is known to sometimes cause bootloops see @curiousrom 's post here:
TWRP App Causing Bootloop or Fail To Boot
It's frustrating that TWRP is setup to facilitate easy swiping to install the app
A: Thank you. So now I flashed the latest .tar.md5 file for my model and my CSC through Odin and the phone wouldn't boot to stock ROM (I guess because it had /e/ Pie on it already and the latest stock ROM is just Marshmallow so it's considered downgrading), got stuck at SAMSUNG logo and phone went extremely hot.
Click to expand...
Click to collapse
Unlikely due to /e/ ROM, I have had this happen before. Just pulled battery, hold power button with no battery or charge cable for at least 10 sec to clear remaining charge (I have one phone that will get itself so out of shape that I have to leave it overnight with no battery before it will boot), let it cool, reinstalled battery and try again. Usually it will boot after this.
I pulled out the battery, went in download mode, flashed TWRP, wiped all partitions, formatted data, flashed /e/, booted /e/, the message about Bluetooth app crashing persists, went to TWRP, tried to flash Intelli kernel, got the "digest" error, tried camera mod, got "digest error" again, magisk flashed fine, so flashing works... so what now? I checked inside the .tar.md5 file and there is no efs partition so I guess it wasn't written over by flashing through Odin
Should the phone be able to boot to stock? Is that even necessary - would it fix anything?
Click to expand...
Click to collapse
Flashing stock ROM can sometimes help fix EFS issues, so that is why I suggested that. I also like to see the stock ROM boot with all functions working to make sure the hardware is ok.
I don't assume you haven't done any of the things I suggest. I'm just brainstorming to see if I can help you from my personal experience with my S5s.
Hope you can get yours working:good:

Maybe try flashing just the baseband with latest modem, etc from haggertk's archive on AFH, here:
androidfilehost.com/?w=files&flid=59628
Click to expand...
Click to collapse
I'm reading some instructions: ohthehugemanatee.org/blog/2015/04/04/how-and-why-to-update-the-modem-slash-baseband-firmware-on-a-samsung-phone about how to flash baseband as this is something I've never done before and I'm afraid to mess my device even further... They say "Note that each carrier handles their own updates, so they package their own modem firmwares with slightly different serial numbers. There shouldn’t be any significant difference, but check which one comes from your country and provider".
So I searched for the CSC of the firmware you've linked and it seems to be XXU: samfrew.com/download/GALAXY__S5__/1l88/BTU/G900FXXU1CRH1/G900FOXA1CRH1, which turns out to be a "Multi-CSC for some of the countries and regions (“O” refers to Open)"... is that "some" that bothers me as XXU is not listed under my country's CSC list.
Should I worry? Is it possible to try out if this baseband solves my problems and if it will not work return to the previous version flashing the stock ROM again or am I risking to brick my phone? I didn't find a baseband for my country's csc (SIO) as I will not be receiving any official updates anymore should I change my phone's CSC to XXU first?
(I'm not able to post URL's yet, so they are truncated.)