Related
I have some related problems with my phone which started happening a couple of days ago after updating Google Maps and a few other programs from the Play Store (Twitter also). That may not be relevant.
It's an Australian i9505 from Telstra. I'm on an old version of Omega ROM - v12 - with Adam Kernel 3.4.0. It's the latest that (the currently stalled) jKay can run on.
The main issue is that the phone reboots frequently. It seems like a "soft reboot" - the uptime reported in System Settings - > About device -> Status doesn't reset, but the time reported by Battery, for instance, does (and the whole UI reloads, programs, widgets etc)
This can happen in my pocket, or can be pretty reliably triggered by uninstalling a program, sometimes installing/updating, and sometimes from using Google Maps (embedded or the program itself).
The first time it happened was after the programs updated on the 5th of Feb.
Related issues:
I can't update the modem in Odin or Mobile Odin.
I tried upgrading to the latest pre-KitKat version, v19, which requires updating the modem.
Flashing the modem I already have did succeed, but that doesn't prove much.
I can update the recovery though - but I haven't tried installing a new rom because of the modem problem.
Rebooting into Recovery or Download mode from software fails - i.e. any of the "boot menu" programs/features. The phone shuts down but then stays turned off.
I can boot into them using the hardware buttons though.
Things I've tested:
It's not the SD card - it happens with it removed.
It's not the battery - I've got 3 batteries, none of which suffer from bloat, and it happens with all.
It's not water damaged - the nearest it got to rain was a couple of days earlier
From what I can tell, rolling back Google Maps, clearing data/cache for Google Services Framework or Google Play Services, all don't fix it.
Any suggestions?
Is my phone toast? Is there a rom I can install with included modem, perhaps?
Or should I at try unrooting and going back to stock? Triangle Away currently fails too, so I'm concerned that if it's a hardware problem Samsung won't fix it for me anyway.
frogworth said:
I have some related problems with my phone which started happening a couple of days ago after updating Google Maps and a few other programs from the Play Store (Twitter also). That may not be relevant.
It's an Australian i9505 from Telstra. I'm on an old version of Omega ROM - v12 - with Adam Kernel 3.4.0. It's the latest that (the currently stalled) jKay can run on.
The main issue is that the phone reboots frequently. It seems like a "soft reboot" - the uptime reported in System Settings - > About device -> Status doesn't reset, but the time reported by Battery, for instance, does (and the whole UI reloads, programs, widgets etc)
This can happen in my pocket, or can be pretty reliably triggered by uninstalling a program, sometimes installing/updating, and sometimes from using Google Maps (embedded or the program itself).
The first time it happened was after the programs updated on the 5th of Feb.
Related issues:
I can't update the modem in Odin or Mobile Odin.
I tried upgrading to the latest pre-KitKat version, v19, which requires updating the modem.
Flashing the modem I already have did succeed, but that doesn't prove much.
I can update the recovery though - but I haven't tried installing a new rom because of the modem problem.
Rebooting into Recovery or Download mode from software fails - i.e. any of the "boot menu" programs/features. The phone shuts down but then stays turned off.
I can boot into them using the hardware buttons though.
Things I've tested:
It's not the SD card - it happens with it removed.
It's not the battery - I've got 3 batteries, none of which suffer from bloat, and it happens with all.
It's not water damaged - the nearest it got to rain was a couple of days earlier
From what I can tell, rolling back Google Maps, clearing data/cache for Google Services Framework or Google Play Services, all don't fix it.
Any suggestions?
Is my phone toast? Is there a rom I can install with included modem, perhaps?
Or should I at try unrooting and going back to stock? Triangle Away currently fails too, so I'm concerned that if it's a hardware problem Samsung won't fix it for me anyway.
Click to expand...
Click to collapse
Hi,
A couple of things that you might try:
1. Look HERE
This should help with the flashing of the modem.
2.Do you have the knox-pox?
Check in download mode.
Is there anything about knox?
malybru said:
Hi,
A couple of things that you might try:
1. Look HERE
This should help with the flashing of the modem.
2.Do you have the knox-pox?
Check in download mode.
Is there anything about knox?
Click to expand...
Click to collapse
Hi there,
Thanks - I'll try that, although I've attempted flashing the modem a number of times. I'll uncheck autoreboot, but it never gets there because it fails during Download Mode.
I don't have knox - I'm still on an earlier bootloader.
frogworth said:
Hi there,
Thanks - I'll try that, although I've attempted flashing the modem a number of times. I'll uncheck autoreboot, but it never gets there because it fails during Download Mode.
I don't have knox - I'm still on an earlier bootloader.
Click to expand...
Click to collapse
Hi,
If that fails , and you want to get back to stock, Google for the MGA firmware.
This is the knox-free version.
Bear in mind that this will wipe your phone clean.
It is flashed in odin , and will replace your ROM,kernel ,modem and recovery.
Triangle Away should also work and you could then send in your phone for repair.
One thing if you do that , they will probably upgrade your phone to the latest knox-pox version.
Good luck
I'm trying to flash the modem again, but I'm noticing this error:
There is no PIT partition.
Is it worth flashing with a .pit file?
Or can you *only* flash a pit file when flashing firmware, not modems or recoveries?
frogworth said:
I'm trying to flash the modem again, but I'm noticing this error:
There is no PIT partition.
Is it worth flashing with a .pit file?
Or can you *only* flash a pit file when flashing firmware, not modems or recoveries?
Click to expand...
Click to collapse
Hi,
I would go for the stock MGA firmware flash.
Back up your stuff first.
If you still get errors , post your questions HERE
samersh72 is the expert in pit files.
UPDATE: so, at home I only have a Mac and I do my Odin stuff in VMware. 99% of the time it's fine, but updating my modem in order to flash the latest Omega ROM wasn't working.
At work, I plugged in my Samsung cable to one of the back USB ports, and had no problem flashing modem and pit file.
The problem with rebooting (into download, recovery or whatever) via software has gone away - *phew*
Then I installed latest Omega, same problem.
So I tried installing with full wipe - and from what I can see, it wasn't randomly rebooting - I could use Maps and remove Play Store apps with no problems.
Unfortunately upon restoring apps & settings with Titanium Backup, the problem returned. But I'm confident now that it's settings, so I won't need to restore to stock and take it back to Samsung at least!
I'll wipe again and post here when I resolve where the problem lies. Next attempt will be to restore user apps + data but not system data, or vice versa, and to be more selective... I'll crack this
I've now reinstalled the ROM again with a full wipe, didn't allow Google to reinstall my apps but instead got Titanium Backup to restore only non-system apps and data.
Of system data I've restored SMS/MMS messages, accounts, and WiFi access points only I think. I've redone the settings for everything else.
So far, all systems go - no reboots.
Oh and conversely, restoring ONLY system apps/data immediately brought the problem back.
I'm not that keen to keep restoring system data till I encounter the problem, since for now I seem to be back in business. W00t! :laugh: :good:
I have had similar issues. It seems like the internal sd has been formatted incorrectly. So i Google the I9505 pit file for Odin and stock firmware Knox free and everything worked straight away. Odin will format the internal sd with the pit file and then it will begin to flash stock firmware and you will have fresh s4 to work with.
Sent from my GT-I9505 using XDA Premium 4 mobile app
glennd said:
I have had similar issues. It seems like the internal sd has been formatted incorrectly. So i Google the I9505 pit file for Odin and stock firmware Knox free and everything worked straight away. Odin will format the internal sd with the pit file and then it will begin to flash stock firmware and you will have fresh s4 to work with.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks - yes, I did flash a pit file for i9505 and it did help the problem with booting into recovery/download mode via software.
But the crashing problem comes back anytime I restore all the system settings, so it's some weird bug with some buried setting - it's not Google Play Services or Google Maps, even though it's related to them. I've just stayed away from restoring practically any system settings and it's working for me.
hey i was look for a way to reset root directory to default... on my s4 SGH-i337m i think some how flashing roms and stuff put something in there the is messing with my sound... because no matter what i do i cant get t sound working right again... it always cuts out and stops working until i reboot my phone.. i have tried everything like 6-7 roms and 3-4 different full stock roms and multiple flashes in odin.. with stock roms
so in there anyway to reset the ROOT directory ware the esf,etc,firmware,firmware-mdm,lib,mnt,persdata,preload,root,sys,system,data,dev,cache, etc............
will flashing Pit file with odin do this?
if not what will plz help....
Messing with PIT files without full knowledge of what you are doing is one of the surest ways to bring the phone. Don't do it.
Flashing your firmware (as describe in the Return to Stock section of the All things ATT guide) and doing a factory data reset takes you to stock. Given your description I think you have a hardware problem. I also had sound issues that got worse the longer the phone was up. Rebooting didn't "fix it" but made it less extreme (I got weird distortion / crackling). Factory service was required.
Hi
I reflashed my S5 with a stock rom to remove all the Carrier blocks and extras. After the flash the device booted up and instantly came up with the error saying acore has stopped working and then around around 5-10 seconds the phone reboots and does it again. What can I do?
Thanks
Wildey1771 said:
Hi
I reflashed my S5 with a stock rom to remove all the Carrier blocks and extras. After the flash the device booted up and instantly came up with the error saying acore has stopped working and then around around 5-10 seconds the phone reboots and does it again. What can I do?
Thanks
Click to expand...
Click to collapse
Data factory reset in recovery.
Wildey1771 said:
I reflashed my S5 with a stock rom to remove all the Carrier blocks and extras. After the flash the device booted up and instantly came up with the error saying acore has stopped working and then around around 5-10 seconds the phone reboots and does it again. What can I do?
Click to expand...
Click to collapse
It's hard to answer since you provided no crucial details about your phone, configuration or how you flashed it.
You didn't tell us which S5 model you have or your carrier. Nor what firmware file you flashed, so we don't know if it was a compatible file. No Odin log, so we don't know if the flash had errors or not. And you didn't describe how you flashed step by step so we don't know if you missed essential steps.
At a guess, try wiping the partition cache from recovery mode. Then if necessary, do a factory data reset as well (will delete user files!). If you have ongoing problems, then you should restore your backup and try again from that stable condition.
No backup? That is a bad habit to say the least. In that case, flash a full stock firmware image that matches the carrier that the phone was originally sold for.
.
fffft said:
It's hard to answer since you provided no crucial details about your phone, configuration or how you flashed it.
You didn't tell us which S5 model you have or your carrier. Nor what firmware file you flashed, so we don't know if it was a compatible file. No Odin log, so we don't know if the flash had errors or not. And you didn't describe how you flashed step by step so we don't know if you missed essential steps.
At a guess, try wiping the partition cache from recovery mode. Then if necessary, do a factory data reset as well (will delete user files!). If you have ongoing problems, then you should restore your backup and try again from that stable condition.
No backup? That is a bad habit to say the least. In that case, flash a full stock firmware image that matches the carrier that the phone was originally sold for.
.
Click to expand...
Click to collapse
The Model is SM G900F. Its On Three Carrier. I Flashed A STOCK (From SamMobile) Firmware 4.2.2.
The Flash Process Was Successful. No Errors.
Put Device In Download Mode
Connected To Computer
Loaded Firmware Into PDA
Ftime reset
Auto Reboot
Started The Flashing.
Completed.
Phone rebooted. Got Acore has stopped. Then the phone reboots.
But since I needed my phone working quickly I took the path of factory reset and that seems to have fixed it. I did try clearing the cache but no effect.
I believe I know the issue. I used a launcher called Themer. I have reasons to think that was causing the issue because as it was loading in the background I managed to quickly hit the continue button to close the crashed process boxes and as the Launcher finished "Loading" it when it rebooted.
WARNING FOR OTHERS. Always Remove Other Launchers Before Flashing As A Precaution! (Warnings From Newbies Hehe)
Hi,
I recently got the I337m s4 that was originally under Bell (canadian carrier). The first mistake, I think I made was immediately flashing it by using the chainfire autoroot method with odin. After I did, I installed the gummy rom. Ever since then, I cannot get the sound to work on my phone. I am not sure if it is a modem issue. I hope it is not a hardware issue. I already tried going to
From searching different threads on here, one user of the i9505 variant was able to get sound working by using odin to flash the stock rom. I linked the thread below:
http://forum.xda-developers.com/showthread.php?t=2698073
Is this the proper way to start troubleshooting? I already tried getting back to stock by using odin 3.07 and the firmware below that did not work:
http://www.sammobile.com/firmwares/?page=1&model=SGH-I337M&pcode=0#firmware
Should I try flashing stock again but this time by doing the battery pull method (pulling the battery, before rebooting, after flashing is complete) that a lot people suggest? Did I select the correct firmware from sammobile?
P.S. When I did go back to stock, the boot screen samsung always played sound.
some ideas
try flashing the modems
reflash rom and check md5 before flashing
restore your nandroid
i think 3.09 is latest odin, but never used it
are you wiping all including system before flashing rom--i do it 3x
I have not tried flashing the modem but I read on xda that when you flash the whole stock firmware from sammobile, you end up re-flashing the modem since it is in the firmware. I will try flashing modem separately since I have not done that, yet.
When I flash, I always wipe dalvik cache, cache and do a factory reset before I start.
Btw, I did go flash the firmware from sammobile today and unrooted my phone. I still get no sound when playing music. The only sound I get is the samsung boot sound, when booting my phone.
rsd79 said:
I have not tried flashing the modem but I read on xda that when you flash the whole stock firmware from sammobile, you end up re-flashing the modem since it is in the firmware. I will try flashing modem separately since I have not done that, yet.
When I flash, I always wipe dalvik cache, cache and do a factory reset before I start.
Btw, I did go flash the firmware from sammobile today and unrooted my phone. I still get no sound when playing music. The only sound I get is the samsung boot sound, when booting my phone.
Click to expand...
Click to collapse
Only other thing I can think of is to back up personal data and wipe your cards.
It seems like every time I do factory reset from the phone or flash using odin, the sound works for 5 minutes, when I play a track. Then I have to restart the phone and sometimes the sound comes back sometimes it doesnt. Otherwise, everything else working fine.
[FIXED]
Partly, because I had misplaced my OEM battery, I did not mention this before. The whole time my phone would randomly restart and not play sounds, I was using the anker 7800mah batter. After, I put the OEM stock battery back in, everything is working fine now! I am still on stock firmware but was able to root using chainfire with no issues.:good:
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.)