Database Users

Yureka Reboots after YU logo continuously

Hello Friends,
I am facing a strange problem with my yureka , phone is rebooting continuously after YU Logo.
Phone is detecting in the fast boot mode and I was able to flash it using the official cm-12.1-YOG4PAS8A4-tomato-signed-fastboot-a7a306cebd.zip from cyanogen. After flashing it will boot as normal for the first time and when I try to setup my Google account it will restart and then onwards it will keep restarting after the YU logo. If anyone knows any solution for this problem please let me know.
Thanks in advance
Arun

Try re flashing your previous ROM from flashboot n use adb software
Sent from my YU5510 using XDA Free mobile app

my yureka suddendly switched off and it reboots continuously after yureka logo. i have cleared my cache .but nothing happens i updates the incremental also but no use ... it reboots continuously..what i want to do plz help me.

Same Problem
Have been using it since more than a year without problems. Two days back it suddenly re-started and kept re-booting at the YU Logo. Absolutely no idea, why. Had updated to CM 12.1 over official OTA six months back. Tried to flash original CM 12.1 after clean wipe in TWRP recovery, same result. Flashed CM recovery, flashed factory image over adb using flash-all.bat in bootloader mode, same result. Flashed latest TWRP, did clean wipe, again flashed factory image over adb, nothing. same result. This is driving me nuts. Don't really know what I'am doing wrong in the sequence. But tried everything I could with all the help described in the forums. Still the same result every time. I even tried to flash CM 13 after a clean wipe, but somehow the phone seems to be adamant in repeating its actions. Like its in a coma or something. Just not responding to anything. The better part is I can get to recovery and bootloader mode. Thats all. Would be really thankful and obliged if someone out here knows the secret for this. Please help.
Thanks to each and everyone on XDA for helping people keep their phones alive for a longer period. I also tried changing the battery for that sake, don't know if it really matters. Still nothing.
Problem solved : http://forum.xda-developers.com/yureka/help/recover-yu-yureka-softbricks-hardbricks-t3477139

is there any solution for your problem i am also facing same problem

TheIndianSinger said:
Have been using it since more than a year without problems. Two days back it suddenly re-started and kept re-booting at the YU Logo. Absolutely no idea, why. Had updated to CM 12.1 over official OTA six months back. Tried to flash original CM 12.1 after clean wipe in TWRP recovery, same result. Flashed CM recovery, flashed factory image over adb using flash-all.bat in bootloader mode, same result. Flashed latest TWRP, did clean wipe, again flashed factory image over adb, nothing. same result. This is driving me nuts. Don't really know what I'am doing wrong in the sequence. But tried everything I could with all the help described in the forums. Still the same result every time. I even tried to flash CM 13 after a clean wipe, but somehow the phone seems to be adamant in repeating its actions. Like its in a coma or something. Just not responding to anything. The better part is I can get to recovery and bootloader mode. Thats all. Would be really thankful and obliged if someone out here knows the secret for this. Please help.
Thanks to each and everyone on XDA for helping people keep their phones alive for a longer period. I also tried changing the battery for that sake, don't know if it really matters. Still nothing.
Problem solved : http://forum.xda-developers.com/yureka/help/recover-yu-yureka-softbricks-hardbricks-t3477139
Click to expand...
Click to collapse
Maybe u should try replacing ur current ROM with stock rom
---------- Post added at 10:55 PM ---------- Previous post was at 10:50 PM ----------
Mohan2123 said:
is there any solution for your problem i am also facing same problem
Click to expand...
Click to collapse
Just try flashing stock ROM of ur device using the custom recovery u r using,......

Try replacing battery
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
Whoever facing problem of continues restart with YU logo they must try to replace battery. This is problem of almost every device after certain period. Thank you

Yu yureka restarting frequently
I had the same problem, after i changed the battery it worked

Phone crashing and shutting down randomly when not On charge

. For the past few days my phone has been crashing and turning off randomly, when the phone is off the charger. The screen just goes black and Shuts down. When I try to reboot the phone it will get upto the boot animation and then freeze and shutdown again. I have to connect my phone to a charger and then reboot, only then does it fully boot up. My battery is 100% btw.
What I have done so far is:
1) flashed the latest build of exodus
2) cleared dalvik and cache
3) flashed an earlier build (25/07) without flashing XPOSED and SUPERSU. However problem still present.
Can someone help please and tell me what other steps I can take. My phones important to me at the moment as I'm away in Turkey for an internship. It's a really strange problem I can't figure out what to do. Thanks alot

Did you try to go bacm for stock oneplus OS? Try to do a full recovery via the tool it will wipe root twrp back to stock. It may help.

Does it happens with other roms?

hi, i solved the problem by flashing stock oxygen. i tried flashing oxyslim and cyanogen however both of them still had the same problem. Anybody have a idea of why this might have happened? it was completely random, and if it was the kernel then it would have been solved when i flashed the other roms...strange

Zeeshansafdar1 said:
hi, i solved the problem by flashing stock oxygen. i tried flashing oxyslim and cyanogen however both of them still had the same problem. Anybody have a idea of why this might have happened? it was completely random, and if it was the kernel then it would have been solved when i flashed the other roms...strange
Click to expand...
Click to collapse
It could be that te ROMs u DL were corrupted. This happens, thats why is always good yo verify HASH from your dl ROM and HASH from the developers topic

So you haven't read up on the official CM13 thread about the latest unstable builds?

[solved] Phone is acting weird ... random reboots shortly after boot

Hi there,
I started this topic because I am out of options and I don't know what to do at this point.
My Phone is a XT1562 DualSim.
I recently flashed http://forum.xda-developers.com/moto-x-play/development/rom-spetrum-mm-volte-t3462690 and I also installed "MODEM" (MPD24.107-70) from page 1, but not right away.
First I wiped everything expect "internal storage". The phone booted but it restarted during boot (which might be okay) but then it rebooted again during boot. The boot process finally finished and I got to the screen "Android is starting - Optimising app x of y." The phone rebooted even during that process and that is definitely not normal I think. So after a couple of reboots android did finally optimise all apps but the phone did still reboot withing the first 30 seconds after it was booted.
From here I did a lot of testing and doing. These are my findings:
- When I set phone to flight mode / airplane mode it does NOT reboot... Hurray!
- When I flash another ROM (Official CM 13, http://forum.xda-developers.com/mot...m-cyanogenmod-13-preview-moto-x-play-t3252255) the phone runs like a charm, NO reboots whatsoever.
- - But as soon as I flash gapps and the phone is booted, I get the reboots again (usually within the first 30 seconds).
- - Again setting the phone to flight mode prevents itself from rebooting.
- - Apparently it doesn't matter what version of gapps I flash. I even tested the light version (ARM, 6.0, Pico, from http://opengapps.org/). It still reboots. I also tried gapps mini and stock.
Oh and I don't think its MODEM (mentioned above) related, because I faced these problems already before I installed / updated the MODEM. Well I thought its MODEM related, that's why I went back to MODEM stock version MPD24.107-52 but that did't help either. I should mention that I am not sure if I had MPD24.107-52 installed originally but spetrum (the rom developer) pointed me to that version: http://forum.xda-developers.com/showpost.php?p=69129552
I also restored my working TWRP backup from an android I used for month and guess what, yep, reboots
brrrrr this is frustrating
I never experienced that before and frankly I am out of ideas.
Anything is welcome and appreciated
Thank you

If nothing helps reflashing the whole firmware is always an option

minimale_ldz said:
If nothing helps reflashing the whole firmware is always an option
Click to expand...
Click to collapse
Thanks I haven't done that.
To be clear, you mean firmware as in stock rom / factory image?

I always go back to flashing stock rom with rsdlite whenever things went wrong and I can't solve it by flashing small fixes.

rancor187 said:
Thanks I haven't done that.
To be clear, you mean firmware as in stock rom / factory image?
Click to expand...
Click to collapse
I mean full stock firmware you flash with fastboot or RSD. Roms are usually only system + kernel, so not very helpful in your case

Guys! Good news. I did go back to stock firmware and from there to official CM13. Of course I had to root and install TWRP again but it was worth it.
I lost a few days spending my time with it but I'm glad its all good now thanks to you.

Battery acting weird after upgrade los15(oreo,dotos)

Hello guys
I was on b14 custom stock rom,i had no problems at all.
Upgraded to dotos oreo with the required bootstack and modem and stuff with oki twrp labs.
But my battery acts weird after that.When it reach 35% it can drop to 27% in 20 seconds and than stay on 27% for like 5 or 10 minutes,then it drops from 26% to 19% in 10 or 20 seconds,and again it stays at 19% for a couple of minutes.Then when i shut down my phone and try to turn it on,it says i need to charge my device and it turns off again.Then i try to boot in twrp,and that succees,when in twrp it shows battery 0% but the phone keep remaining on.
Also when i put on charger,it charge that same amount of lost,like 10%,in 10 seconds.
But when ther is no OS installed(all partitions wiped) and i boot in twrp,adn put it on charger...it charges fine,no big gapps.
When there is a OS installed and it drops less than 30%,this acting happens again
I did calibrations,clean flashes,all i could.
Note that this happend when i switched to dotos,so it cant be bad battery,because 10 minutes earlier everything was fine.
Can the problem be on EFS,Persist Partition? if yes,how can i solve this? Can the problem be in the sys folder? I do think some of these 3 has to do with it
I think it got vendor/system problems.Sometimes it also dont boot the system,or random bootloops
I did full EDL flash ( G oreo b02),booted and set up.
Now i flashed twrp treble nfound,wiped all partitions,and did edl vendor flash.I booted twrp and it tells my data is encrypted,i went to wipe,selected data partition...and it says the partition is emmc,also the same on system partition...how is this possible? Ofcourse i know how to get back to ext4,but i want to know why now it says emmc.Also before i booted because of vendor flash,battery was 22%.When i did the flash and booted in twrp the battry was 26%.
Definattely ( lol bad english in text) something wrong here,instead of the easy claims they say the battery is bad

I have had the same problem. Performed EDL Nougat B12 stock via EDL. Now no more isssues with battery. I am on 2017G.

doesnt work for me,this acting only happens when a rom(OS) is installed.
With all partitions wiped,i can charge fine in twrp.
My battery was on 100%,i did full wipe,rebooted in twrp (stil 100%) and flashed dotos+gapps+kernel.After the flashing battery sit on 96%.
Not good,something wrong

Now it drained from 30% to 18% in 1 minute,and now its stuck on 18% for 10minutes+ or longer.
If I put on charger now,it charge the same amount I lost in that minute , in like 2minutes or less
Don't know what is going on here

@Predatorhaze: Are you absolutely sure that your battery isn't going bad? I ran the same setup as you for a few days, I got none of the behavior you've described. It's normal for TWRP to sometimes show 50%, just ignore it. I've seen this in every TWRP build I've tried on my A7, regardless of installed ROM, bootstack, etc.
If you go back to stock does this behavior stop?
Another thing, I ditched DotOS because it can only be rooted with Magisk, and I have an intense dislike of Magisk. And I have an A2017U, whereas you have a G. Not sure how much difference that would make.

AnonVendetta said:
@Predatorhaze: Are you absolutely sure that your battery isn't going bad? I ran the same setup as you for a few days, I got none of the behavior you've described. It's normal for TWRP to sometimes show 50%, just ignore it. I've seen this in every TWRP build I've tried on my A7, regardless of installed ROM, bootstack, etc.
If you go back to stock does this behavior stop?
Another thing, I ditched DotOS because it can only be rooted with Magisk, and I have an intense dislike of Magisk. And I have an A2017U, whereas you have a G. Not sure how much difference that would make.
Click to expand...
Click to collapse
that 50% is just a bug.everyone got this.
And this happened when i switch to dotos.1 hour before that everything was fine.
So you believe a battery can be broken due the flashing? it happened on los uni bootstack oki twrp dotos and swifty kernel.

now my phone connected to pc on usb,phone is turned on,stays on and battery says 0% hahaha ,this is getting funny

what does this do? Button to disable the eMMC write protection (disemmcwp)
i have read this somewehre :
Now I'm not saying that's what's happening, but I noticed these phones get really hot flashing deodexed roms. And just wondering if this could be a possibility, that the emmc chips are getting hot and breaking solder points.
My battery can act weird when i use intense gpu resources (heavy videogame)

@Predatorhaze: No, I don't think flashing will break a battery. What I was trying to say is that your battery might have been slowly going bad even before you flashed DotOS. Batteries generally don't fail overnight, it takes time. Unfortunately I have no way for you to test further so you will have to look into this on your own. How old is the phone? The longer you have had it, the more likely that the battery needs to be replaced.

AnonVendetta said:
@Predatorhaze: No, I don't think flashing will break a battery. What I was trying to say is that your battery might have been slowly going bad even before you flashed DotOS. Batteries generally don't fail overnight, it takes time. Unfortunately I have no way for you to test further so you will have to look into this on your own. How old is the phone? The longer you have had it, the more likely that the battery needs to be replaced.
Click to expand...
Click to collapse
Phone 1 year old.My battery wasn't going bad,it happen direct when I flashed dotos.(botstack+patch splash screen)
I'm on los14 and it looks like the problem is gone.Or not,at least it got a little better
I think its related to vendor,cus i have many times issues with vendor partition for example in deleting and creating.Once, i deleted the vendor partition,rebooted twrp and the vendor was gone.I installed other twrp,boot it,and the vendor was back/still ther.
Also when all partitions are wiped,it charge normal...all ok
In accub,it's still 2800mah...but sometimes it show 3600mah.How more cycles i charge,how higher the estimated mah goes up
By the way,i NEVER charge at night ( while sleep),also never drop it less than 10%
Somethign screwd up my battery,maybe some solder point on motherboard
Where is this folder for? vendor/lib64/.... ( note that i have not a vendor partition active) can i delete it?

@Predatorhaze: I would suggest clean flashing the earliest stock Nougat EDL you can find for A2017G (B19 for A2017U, but that wont work for you). Then unlock bootloader again (if necessary), reinstall TWRP, and try your tests again. I have often found that flashing a stock EDL fixes many issues I previously encountered. I prefer Nougat because it is more stable (for me) than Oreo/Pie. B32 is the baseline EDL package that I use.
Try to avoid flashing other bootstacks/modems unless you absolutely have to (like LOS bootstack). B32 bootstack boots all AOSP/LOS Nougat ROMs, and can also boot any Oreo ROM as long as it isnt based on Treble and doesnt have a vendor partition. Of course with N bootstack there will be issues with dual SIM and camera 2 API/HDR, but I dont use those, so no issues there. And B32 bootstack doesnt have the system partition read-only issue. All stock bootstacks based on B35 and higher seem to have this last issue, LOS bootstacks dont but then there is no EDL with the hardware buttons.
And before I forget, dont try to use @Oki's custom TWRP with an N bootstack, it probably wont work (didnt for me when I tried it once). Stick to official TWRP, or @NFound's TWRP 3.2.1-7.

AnonVendetta said:
@Predatorhaze: I would suggest clean flashing the earliest stock Nougat EDL you can find for A2017G (B19 for A2017U, but that wont work for you). Then unlock bootloader again (if necessary), reinstall TWRP, and try your tests again. I have often found that flashing a stock EDL fixes many issues I previously encountered. I prefer Nougat because it is more stable (for me) than Oreo/Pie. B32 is the baseline EDL package that I use.
Try to avoid flashing other bootstacks/modems unless you absolutely have to (like LOS bootstack). B32 bootstack boots all AOSP/LOS Nougat ROMs, and can also boot any Oreo ROM as long as it isnt based on Treble and doesnt have a vendor partition. Of course with N bootstack there will be issues with dual SIM and camera 2 API/HDR, but I dont use those, so no issues there. And B32 bootstack doesnt have the system partition read-only issue. All stock bootstacks based on B35 and higher seem to have this last issue, LOS bootstacks dont but then there is no EDL with the hardware buttons.
And before I forget, dont try to use @Oki's custom TWRP with an N bootstack, it probably wont work (didnt for me when I tried it once). Stick to official TWRP, or @NFound's TWRP 3.2.1-7.
Click to expand...
Click to collapse
I'm on nuclearom,problem look gone.4 hours sot,could be 6 probably.Also didn't notice any weird drain.Thanks.
I think it was due vendor partition issues,or the vendor has a bug.
I can remember it took months they find out the headphone jack CPU bug,after many complains..so I would not look weird if they find a bug in vendor...

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.)