S4 i9505 - Stuck booting - Galaxy S 4 Q&A, Help & Troubleshooting

Hope someone can help with some ideas, im really lost how to fix this now.
I have my S4 on the latest stock 5.0.1 Lollipop which is rooted with CFAutoRoot.
I9505XXUHQK1 (edit: Samsung international update 2017 - only installed in a hope to cure the problem in Feb 2018 but made no difference)
Since about last October I have a problem booting about once every 6 weeks, basically it runs great then something starts acting up like you get with all phone, so I do a restart to get things running smoothly again.
It goes through the splash screen no problem, I get the music and it stats booting with the colourful samsung logo with fireworks behind but it just sticks there forever and won't finish a boot, I notice when I get a good boot there is a vibration as it finishes, this vibration never comes when it fails.
The first time, I put changed the recovery to (twrp-3.2.1-0-jfltexx) thinking next time it would be easy wipe the cache and dalvik/art and get it booted, using twrp to clear the cache and dalvik/art did not help so I was forced to reset it again.
Next I noted there was an unexpected update to the S4 from Samsung, I thought applying this update might help things so went ahead and installed it giving my phone all the latest security updates etc, but again the same happened a few weeks later.
Here post 979 (Bootloader, Modem & kernel): https://forum.xda-developers.com/ga...rom-untouched-stock-rom-t3419034/post75164948
I then decided after another painful reset I would keep a weekly Nandroid backup so I could at least get it up and running again quickly.
Last week it failed again, this time I the data icon light would not turn off without clicking through and unticking the checkbox, even then with the data off the green light was on in notification, so a restart and as expected a freeze....
This time I had my Nandroid backup and I had a fresh(ish) Titanium Backup and has backed up my texts and call lists via Samsung so after an hour it was all backup and normal and this time only lost a few days texts and call logs.
Really i'm in a situation where all I can be is spend my life being prepared to restore my phone with good backups but completely unable to prevent it.
My only thought is there must be an app that is playing up during boot, but how do I identify it, the symptoms are never the same (except the boot freeze), no apps are showing high battery use and my battery usage is great, I have hardly used today but it's been off charge since 9am (its now 3.20pm) with 82% left and estimating 27 hours more usage.
Does anyone have any ideas what could be causing this or any tips on how to identify the problem, I would rather spend time fixing it that spend my time preparing for an inevitable recovery.
Thanks in advance for any thoughts.
Edit: Just for info, I regularly reboot it to do a Nandroid backup and it restarts just fine, just fails about once every 6 weeks or so.

I9505XXUHQK1 is meant for branded Greek and German networks only, if your device is unlocked international you will experience problems, especially at boot as it looks to load the branded stuff. Eventually it will give up and just boot.
Although this last update looks all sexy, it's almost identical to XXUHKP2 just a newer security patch and a few minor changes, really not worth the hassle of getting it (or the problems your having).
I believe the latest "MachineX" ROM is built off this firmware which has the branding stuff removed and also links to the correct XXUHQK1 boot loader. Have a look in the ROM section.

cooltt said:
I9505XXUHQK1 is meant for branded Greek and German networks only, if your device is unlocked international you will experience problems, especially at boot as it looks to load the branded stuff. Eventually it will give up and just boot.
Although this last update looks all sexy, it's almost identical to XXUHKP2 just a newer security patch and a few minor changes, really not worth the hassle of getting it (or the problems your having).
I believe the latest "MachineX" ROM is built off this firmware which has the branding stuff removed and also links to the correct XXUHQK1 boot loader. Have a look in the ROM section.
Click to expand...
Click to collapse
Thank you but the I9505XXUHQK1 update is not the issue, the problems started months before this update
I can easily revert this but it is really not the cause of the issues.
are you sure about I9505XXUHQK1? XXU is international unbranded is it not?
XXU= international
H=5.0.1
Q=2017
K=November
1=version 1
Refference:
What do the letter-codes mean?
Example: XXUHPA1 for the I9505
XXU: is the region, in this case international.
H: is the android version, in this case ‘5.0.1’
P: is the year in alphabetical order, P is the 16th letter, thus 2016
A: is the month, again in alphabetical order, thus it’s January.
1: is the revision. In this case 1st
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s4/general/ref-galaxy-s4-i9505-modems-bootloaders-t3315987
Also:
Samsung bootloader /modem /firmware NAMING:
GT-I9505XXU#(version)
Example: GT-I9505XXUCNE4
GT-I9505 = phone model
XXU = baseband cellular network
XXU is Global and valid almost everywhere, any country regardless of carrier
C = baseband build version
NE4 = version
Version translated
N = year = 2014 (14th letter of alphabet)
E = month of year (May in this case, 5th letter of the alphabet)
4 = build # of that month ( they start 1-9, then letters, A=10,...)
Example:
NE4 = 2014, May, Build 4
NE5 = 2014, May, Build 5
OH2 = 2015, Aug, Build 2
Click to expand...
Click to collapse

kudos1uk said:
Thank you but the I9505XXUHQK1 update is not the issue, the problems started months before this update
I can easily revert this but it is really not the cause of the issues.
are you sure about I9505XXUHQK1? XXU is international unbranded is it not?
XXU= international
H=5.0.1
Q=2017
K=November
1=version 1
Refference:
https://forum.xda-developers.com/galaxy-s4/general/ref-galaxy-s4-i9505-modems-bootloaders-t3315987
Click to expand...
Click to collapse
OK i'll try explain
XXU can mean international as in 2 different branded networks in different countries or regions, understand? Also In with that firmware are the csc codes for the country you;re in, detected off the SIM at start up, sometimes the correct csc codes are loaded sometimes they're not and then you get stuck on boot. This why you should only flash firmware which is device AND region specific.
Anyway, flash XXUHKP2, run it for a few weeks with frequent restarts, if no boot loops then you have your answer.

cooltt said:
OK i'll try explain
Anyway, flash XXUHKP2, run it for a few weeks with frequent restarts, if no boot loops then you have your answer.
Click to expand...
Click to collapse
Thanks but it wont make any difference, I had that for months and was on the phone when this all started, I did several resets and an odin reflash of XXUHKP2 but still had the problem, I only flashed XXUHQK1 a month ago in a last ditch hope it might cure the issue but I have had one boot problem since I installed it.
Both XXUHKP2 & XXUHQK1 behave exactly the same, they work for weeks with no issue, I can reboot as many times as I like without a problem then all of a sudden something will start playing up on the phone (start running slow or unable to turn off data etc) and the restart freezes.

cooltt said:
OK i'll try explain
XXU can mean international as in 2 different branded networks in different countries or regions, understand?
Click to expand...
Click to collapse
You don't need to explain anything XXUHKP2 and XXUHQK1 are both international and will work in almost any country that's what XXU means, not a couple of regions or countries, I don't think Samsung have this classification.

More information, had problems overnight last night.
During the night I was woken by the phone restarting, I looked at it and it was in the middle of preparing all my apps, this normally only happens after a wipe, I left the phone and went to sleep.
I woke this morning to find the phone restarted and asking for my sim pin, my happiness was soon gone as it then asked my which launcher to use and only listed the two Touchwiz, Google Now which I normally use wa not listed. I chose Touchwiz full but after a few second the phone went into a soft reboot loop (not asking for a sim pin).
I did my last nandroid 4 days ago, so I set that going but it failed right at the end with error 255, next I tried an old nandroid I have used twice before but it failed in the same way. Next I did a file system check and restore and reformat (saves personal files), still error 255. Next I reformatted the data partition as a full reformat (this TWRP method deletes personal files) and finally the latest nandroid ran without problems and I'm up and running.
There must have been something wrong with my internal personal files which TWRP was trying to preserve. I actually keep very little on my internal as everything is stored on my external sd.
All this is making me start to think my internal storage may be beginning to fail, on the other hand TWRP check and repair did not find any problems, still at a complete loss what the problem is and every time the issue is slightly different but always points at data corruption causing the bootloop.

Related

[Q] Phone wouldn't connect to WiFi with Stock Rom & won't play any SOUND OR MEDIA

I've spent a lot of time now trying to fix my phone and i'm really quite worried.
It's a Samsung Galaxy S4 SGH-I337M (CSC I337MOYAAAMDJ, Baseband I337MVLUAMDJ, version 4.2.2).
I have had CM 10 on it running perfectly fine for about a year. I decided to update it though and didn't know that you could update CM right from the phone , so I downloaded the software from their site onto my phone and onto my PC. Followed the instructions installation froze and didn't move forward for over a day .... so I gave up.
I went looking for and downloaded the phone's stock firmware for both my carrier (Virgin Mobile, Canada) and for Bell's, so I installed TWRP with Odin 3.07 without issue. When I install the stock firmware my WiFi will not turn on.
So i've tried installing several rom's putting them on the SD card and using TWRP on my phone and i've found out that if I use Goldeneye and tell it my phone is an I9505, or hyperdrive (I9505) or at the moment Google Play Edition (JFLTE 5.01, kernel = Googy-Max3) that the WiFI DOES TURN ON as soon as the rom is loaded !!! So I thought I was good, but no
When flashed with either it's stock I337M firmware or these custom I9505 rom's my phone will play no audio. Chrome just crashes if I go to play any music or video. If someone call's, the ringer doesn't work but after several 'rings' my phone start's to vibrate indicating they called (aka the dialer lags out and then crashes). I can make calls too but when I talk the recipient can't hear me, nor I them.
It downloaded and re-installed all the app's of my google backup totally fine and using wi-fi. It play's games fine (but with no sound), i can txt fine, etc. It notices and connects to the network (Virgin Mobile) fine (I turned off wifi and tried downloaded stuff, txts go back and forth, and my phone labels Virgin)
I'm on a stupid 2 year contract and this phone cost $650 at the time I got it. It's knox 0x1 so no warranty to have it repaired. Does ANYONE have ANY idea what might be causing my phone not to play any sound's? I've tried pretty much everything I can think of.
I'd be willing to live with a totally cripples phone ... but it's got to at least work for receiving or sending phone calls and this sound issue crashes the dialer and even if I manage to pickup when it's vibrating before the other person has hung up there's no sound, neither of us can hear each other .
Does ANYONE have ANY idea what could be doing this or how to fix it? I'm so depressed and worried right now that I just a phone I spent a lot of money and am on a stupid contract on :/. I fixed the wifi problem by flashing with a rom that 'makes it' a GT-I9505G, baseband I337MUMUAMDL (v 5.0.1) (vs SGH-I337M, baseband I337MVLUAMDJ (v 4.2.2)), but the same sound and audio/media problem exist's no matter what firmware or version the phone ends up being .
I should have just left it with CM as it was but *sigh* here I am, please help.
masterof1010 said:
I've spent a lot of time now trying to fix my phone and i'm really quite worried.
It's a Samsung Galaxy S4 SGH-I337M (CSC I337MOYAAAMDJ, Baseband I337MVLUAMDJ, version 4.2.2).
I have had CM 10 on it running perfectly fine for about a year. I decided to update it though and didn't know that you could update CM right from the phone , so I downloaded the software from their site onto my phone and onto my PC. Followed the instructions installation froze and didn't move forward for over a day .... so I gave up.
I went looking for and downloaded the phone's stock firmware for both my carrier (Virgin Mobile, Canada) and for Bell's, so I installed TWRP with Odin 3.07 without issue. When I install the stock firmware my WiFi will not turn on.
So i've tried installing several rom's putting them on the SD card and using TWRP on my phone and i've found out that if I use Goldeneye and tell it my phone is an I9505, or hyperdrive (I9505) or at the moment Google Play Edition (JFLTE 5.01, kernel = Googy-Max3) that the WiFI DOES TURN ON as soon as the rom is loaded !!! So I thought I was good, but no
When flashed with either it's stock I337M firmware or these custom I9505 rom's my phone will play no audio. Chrome just crashes if I go to play any music or video. If someone call's, the ringer doesn't work but after several 'rings' my phone start's to vibrate indicating they called (aka the dialer lags out and then crashes). I can make calls too but when I talk the recipient can't hear me, nor I them.
It downloaded and re-installed all the app's of my google backup totally fine and using wi-fi. It play's games fine (but with no sound), i can txt fine, etc. It notices and connects to the network (Virgin Mobile) fine (I turned off wifi and tried downloaded stuff, txts go back and forth, and my phone labels Virgin)
I'm on a stupid 2 year contract and this phone cost $650 at the time I got it. It's knox 0x1 so no warranty to have it repaired. Does ANYONE have ANY idea what might be causing my phone not to play any sound's? I've tried pretty much everything I can think of.
I'd be willing to live with a totally cripples phone ... but it's got to at least work for receiving or sending phone calls and this sound issue crashes the dialer and even if I manage to pickup when it's vibrating before the other person has hung up there's no sound, neither of us can hear each other .
Does ANYONE have ANY idea what could be doing this or how to fix it? I'm so depressed and worried right now that I just a phone I spent a lot of money and am on a stupid contract on :/. I fixed the wifi problem by flashing with a rom that 'makes it' a GT-I9505G, baseband I337MUMUAMDL (v 5.0.1) (vs SGH-I337M, baseband I337MVLUAMDJ (v 4.2.2)), but the same sound and audio/media problem exist's no matter what firmware or version the phone ends up being .
I should have just left it with CM as it was but *sigh* here I am, please help.
Click to expand...
Click to collapse
try with this firmware
lets me see
k thanks i'll try it (once it's slow download is done) and update this post. Looks the same except I guess it's android v5.0.1 (well and it's a different CSC/PDA).
K well i've tried that firmware and it's given me some abnormal problems.
Odin typically just writes in like two minutes and boom done, but when I tried to flash with the firmware you suggested like every 15 seconds it would say ...
"Receive Response from boot -loader"
"Transmission Complete.."
"Now Writing .. Please wait about 2 minutes"
It kept cycling through those 3 messages until it FINALLY finished and it say's PASS but it took 9 min 53 seconds which is like 5 times longer then it's ever taken.
Wheather this is relevant or not i'm not sure just trying to give as much details as I can.
Anyways, after booting the phone the samsung logo came up as usual and usually it takes like 5-10 min sitting at this logo before the phone completes loading, presumably setting up the firmware I imagine.
It's been now sitting at that logo for over 20 minutes and i'm about to try wiping with TWRP the davlic cache/cache/data/internal and either trying again with odin (v3.07) OR
If that contines to not work I might put the tar.md5 on the external SD card and recover a saved backup I have on the SD card (with the stock firmware I had before that doesn't allow Wi-Fi to be enabled nor audio/media to play) and use Mobile Odin Pro .apk (I paid for the pro version) from within that restored recovery to flash the firmware you suggested to my phone again.
This is probably redundant but I just figure I might as well try absolutely everything I can possibly think of with your firmware.
If you have any idea why I might be experiencing these abnormal Odin flashing and/or initial loading conditions of the firmware you (or anybody ) suggested i'd appreciate any advice you can give.
I'm going to try and reflash with Odin on my PC again right now (i'm certain thing's like the USB cable are fine and my PC and phone can transfer data without issue .. but that's why i'm going to try mobile odin if after this next attempt doesn't work either).
I'll keep the thread updated, any and all advice is welcomed and highly appreciated
EDIT: OMG it made a like startup theme sound ... that's the first time it's outputted sound in 3 day's !!! It's at the Samsung screen loading the newly flashed firmware so hopefully that completes because wow my phone made noise finally !! Now to wait, and wait....
It won't go past the Samsung logo. So I guess i'll try Mobile Odin. I don't have much faith but it's worth trying.
Uh the backup of the stock firmware I made won't load ... but the hyperdrive rom did. Sound and the dialer work perfectly fine in this rom now, so I guess thing's are more or less fixed. Even though i've wiped the cache/davlic/internal/data in order to prepare to flash the other firmware or this hyperdrive rom (I wipe it every time) in this rom it's reporting my phone's baseband to be I337MVLUGOC4 which is that of the firmware you suggested ...
I'd still rather not use this rom, I thought it was ok at first but meh i'm going to try to go back to CM (after all this *rolls eyes*), trying to use Mobile Odin to install the firmware that you recommended and that appears to have ... somehow fixed the sound can't detect the model of my phone and is dumping, this is not something that has happened with the app before so I don't think i'll be flashing the firmware you suggested.
If it did something to globally fix the crashing when an app was instructed to play audio as it appears to have I guess i'm going to just go download the full CM now, put it on the SD card and install it with TWRP.
So uh, not 100% there yet but it does appear what you've suggested has solved my problem (because worst case scenario i'll just be stuck with the Hyperdrive rom ... but i'll have a working phone) so thanks so much bud I was quite upset and worried about what I was going to do still paying off a useless phone on a contract i'm stuck with for another year still.
I suppose there's no real need in continuing to update this thread as it appears my problems are solved and all that's left are things i'm doing not to fix anything but just because of personal preference over what rom to use but if you want to know anything more just ask, otherwise thank you so much you saved my ass and i'm very grateful.

Galaxy A5 2016 / Restart on its own

Hello,
My girlfriend bought new Galaxy A5 2016 (gold) on 15/03. Already while I was completing some settings (Google acc / Sams acc "in" and install of such mere apps as viber, skype, facebook..) the phone restarted on its own twice, without any logical explanation (no significant load, no root, since the divice was almost stock).
This bug has occured while this week two or three times a day. Unfo I cannot associate it with any app or particular action. The phone reboots even in sleep mode or when screen is active.
It doesn't look like hardware deficiency. I tried to delete Google Play Services updates (suggested by local Sams support), hardreset and etc., however - no success. The phone continues to restart its own
Have no idea what to do Can you help me?
best regards
Teleri said:
Hello,
My girlfriend bought new Galaxy A5 2016 (gold) on 15/03. Already while I was completing some settings (Google acc / Sams acc "in" and install of such mere apps as viber, skype, facebook..) the phone restarted on its own twice, without any logical explanation (no significant load, no root, since the divice was almost stock).
This bug has occured while this week two or three times a day. Unfo I cannot associate it with any app or particular action. The phone reboots even in sleep mode or when screen is active.
It doesn't look like hardware deficiency. I tried to delete Google Play Services updates (suggested by local Sams support), hardreset and etc., however - no success. The phone continues to restart its own
Have no idea what to do Can you help me?
best regards
Click to expand...
Click to collapse
Are you use memory card/sd card? Try to remove that...
It happened to me the same thing on my old Desire S... The battery were not firmly pushed in its location... So, you could verify that!
hi,
i have the same trouble with my new A5 2016. the phone reboot from itself during the night or the day without any reason... happened 4-5 since March, 14.
a friend with the same a5 2016 has same issues.
We have no SD card, no root, stock.
if anyone have a solution, that would be great !
Model : SM-510F
HellBouy said:
hi,
i have the same trouble with my new A5 2016. the phone reboot from itself during the night or the day without any reason... happened 4-5 since March, 14.
a friend with the same a5 2016 has same issues.
We have no SD card, no root, stock.
if anyone have a solution, that would be great !
Model : SM-510F
Click to expand...
Click to collapse
Reflash stock rom...
I don't have this issue at all , try a factory reset or flash a stock rom.
Hi,
I've bought a A5 2016 in February (Rom stock, No root, dev options unmasked) - Since then, I've Had 3 power off on its own. I've followed forums and wiped my cache. But this morning I had my phone restart on its own.
I'm quite mad at Samsung for now.
Maybe try calling samsung support?
I have had this problem with my A5 too. Whenever the device updates some app, it re starts.
What exactly occurs during the restart? Does the phone vibrate and show "samsung galaxy a5 (6) powered by android" or does it simply play the boot animation without audio.
If the second option is happening with you., then I suggest you re flash the stock Rom. You can get the stock rom from you mobile or San mobile.
I have the A5(2016) from 2/3 weeks but I never had this problem. If you have the A510F model you can try the German firmware (A510FXXU2APC4 - (build version LMY47X.A510FXXU2APC4). Flash it via odin and donwload the firmeware from sammobile.com. for odin guide see here http://forum.xda-developers.com/samsung-a-series/help/rom-stock-firmware-samsung-galaxy-a5-t3305863
To Ahmad89:
Thanks for your response. I actually had logo A5-6 powered by android during restart. I remember to have switched on WiFi connection before it restart (i know that updates occurs only when WiFi's on). That may be an explanation. there may may have been an attempt to update. But the "switch off on its own" event seems more annoying. I did remember one time my phone went off when charging and at that time i used non official Samsung charger. perhaps it was linked to fast charging and a powerless charger that shuted the phone off. What about the two others occurrences when it went off? (the phone being in stand by mode). I can imagine every scenario but no valid explanation.
To zyxw :
I've had the phone update to XXU2APC4 since 3 hours.
I'll do my best to stay in touch for relevant news.
Thanks.
Parmaggedon said:
To Ahmad89:
Thanks for your response. I actually had logo A5-6 powered by android during restart. I remember to have switched on WiFi connection before it restart (i know that updates occurs only when WiFi's on). That may be an explanation. there may may have been an attempt to update. But the "switch off on its own" event seems more annoying. I did remember one time my phone went off when charging and at that time i used non official Samsung charger. perhaps it was linked to fast charging and a powerless charger that shuted the phone off. What about the two others occurrences when it went off? (the phone being in stand by mode). I can imagine every scenario but no valid explanation.
To zyxw :
I've had the phone update to XXU2APC4 since 3 hours.
I'll do my best to stay in touch for relevant news.
Thanks.
Click to expand...
Click to collapse
which one ?? Germany (DBT) firmware ??
Tell me if you will have again the random reboots!
zyxw-androidiani said:
which one ?? Germany (DBT) firmware ??
Tell me if you will have again the random reboots!
Click to expand...
Click to collapse
I had the update by Kies I presume. I did it by updating the phone in settings/software update. I had several times used Odin for my note 3 but for my A5 i didn't want to flash the whole ROM. My country is France. The New baseband is A510FXXU2APC4 and the version Number is LMY47X.A510FXXU2APC4.
At this time no restart or shut off by its own - but too soon to validate.
I will do a wipe cache very soon.
I'll warn you once restart or shut down happen, if so. :fingers-crossed:
We have the same build version so maybe you will not have the problem!
I have PC4 too , no issue so far.
Sent from my SM-A510F using XDA-Developers mobile app
I have the phone fro 7 days and reboot it himself one time. I dont remember if do this after or before update to apc4. Will see. For now, I'm happy with this phone. I'm dissapointing about no screenmirror.
Trimis via Tapatalk
No restart on its own since my 8 day's last post. Hope this will last...
Pd1 firmware version, 128mo usd kingston, official usim from provider, no reboots at all, same with february and march update, everything fine, everything smooth...
i had also same problem in my new galaxy A7 2016 but after hard reset it works fine..and i observed this happens bcoz of poor ram managment n samsung touch wiz software issue ...so might b it will ressolve after marshmallow update..i m also waiting for new update.
i have same problem when i use VPN
I have android 6 and not use touchwiz. I use another launcher and OpenVPN and work fine from 1 year.
Trimis via Tapatalk

May i Install KK Bootloader after having flashed Lollipop update?

Hi people. As you may imagine, i've been trying to update to Lollipop since it was released for my device like a month ago (i have a SM-G530M, LTE version in Argentina), but i'm experiencing, like some people, a weird problem whenever i try to flash the last firmware through ODIN ( G530MUBU1BPH2_G530MUUB1BPH2_G530MUBU1BPG1_HOME.tar.md5 ).
>>I'll give details about my issue to make myself clear
The thing is that, Odin shows me the "Passed" message, and when the phone should reboot and make a fresh start (i made sure to wipe /data, /cache and dalvik), it shows the initial "Samsung Galaxy Grand Prime - Powered by Android" screen (which i must tell..., shows up for many seconds, and then, the screens turns gray with many bars, so after a couple of minutes, it restarts again.
In this scenario, i can't access the recovery mode, though i can still fortunately get into download mode, so i had to stick in kitkat searching for a solution.
After some googling, i came across with this:
htcmania. com/showthread .php?t= 1067200
Effectively, the problem is caused by owning a NON-original touchscreen replacement, and to make sure, i asked for help to my friend to disconnect the screen while trying to boot into Lollipop. The idea behind this was to wait for the typical startup sound since the system didn't even show the boot animation during the failure (and the phone would get warm too). So, with the display and digitalizer disconnected, we could hear the startup sound! and the heat was gone. So my problem is that i have the touchscreen of another Grand Prime variant, made for the G530H "Duos". It works ok, but only in Kitkat.
I tried to get the original replacement specifically for my variant (G530M), but i can't get it even on the internet.
In the meanwhile, i thought about installing lollipop and then, restoring/installing the previous Kitkat bootloader over, but i suspect this may be dangerous.
Would this brick my device? I'm aware that Lollipop brought changes to the bootloader so the problem is to make the system boot in the first place.
Just that, thanks a lot in advance!
alpha-ro said:
Hi people. As you may imagine, i've been trying to update to Lollipop since it was released for my device like a month ago (i have a SM-G530M, LTE version in Argentina), but i'm experiencing, like some people, a weird problem whenever i try to flash the last firmware through ODIN ( G530MUBU1BPH2_G530MUUB1BPH2_G530MUBU1BPG1_HOME.tar.md5 ).
>>I'll give details about my issue to make myself clear
The thing is that, Odin shows me the "Passed" message, and when the phone should reboot and make a fresh start (i made sure to wipe /data, /cache and dalvik), it shows the initial "Samsung Galaxy Grand Prime - Powered by Android" screen (which i must tell..., shows up for many seconds, and then, the screens turns gray with many bars, so after a couple of minutes, it restarts again.
In this scenario, i can't access the recovery mode, though i can still fortunately get into download mode, so i had to stick in kitkat searching for a solution.
After some googling, i came across with this:
htcmania. com/showthread .php?t= 1067200
Effectively, the problem is caused by owning a NON-original touchscreen replacement, and to make sure, i asked for help to my friend to disconnect the screen while trying to boot into Lollipop. The idea behind this was to wait for the typical startup sound since the system didn't even show the boot animation during the failure (and the phone would get warm too). So, with the display and digitalizer disconnected, we could hear the startup sound! and the heat was gone. So my problem is that i have the touchscreen of another Grand Prime variant, made for the G530H "Duos". It works ok, but only in Kitkat.
I tried to get the original replacement specifically for my variant (G530M), but i can't get it even on the internet.
In the meanwhile, i thought about installing lollipop and then, restoring/installing the previous Kitkat bootloader over, but i suspect this may be dangerous.
Would this brick my device? I'm aware that Lollipop brought changes to the bootloader so the problem is to make the system boot in the first place.
Just that, thanks a lot in advance!
Click to expand...
Click to collapse
Did you ever try to buy it at Samsung Store? They maybe have it
I didn't consider that, i'll see if i can contact them directly, hopefully i can get the replacement i need. Thanks friend!

Sm-g955f bricked - flashing stock firmware only made it worse

Hi All,
So, I have spent 2 days trying to get my Galaxy s8+ back to normal. However, I seem to only have made it worse. It all happened when I decided to change the /data partition from ext4 to another format and then back again to get the /data partition to mount in TWRP after flashing Pascal Rom. However when I rebooted, nothing worked, no boot up screen, no recovery, no life, but all I could get was download mode. It then must of froze up after another restart and I couldn't get anything for 12 hours or so.
The next step I tried once i got download mode again was to flash stock firmware for the G955F, I can't remember the version of this firmware, but I still had nothing change. So then i flashed the latest firmware from SamFirm's downloading client, which was G955FXXU2CRF7 - Australian Optus Branded Firmware (OPS). I was able to get as far as the "hello start screen" and then my phone restarted, it then tried to upgrade my system again, then started "erasing" and then it rebooted and I still had the same issue, nothing but download mode and still no recovery, it still wouldn't turn on. So I flashed the latest International/Unbranded Australian firmware (XSA) - G955FXXU3CRGH, still the same result. I now can't go back to the OPS version of firmware because I get the Check error with the bootloader (since it's a more recent version), so I can't go backwards. I also can only flash "Official Binaries" now. Oh and to make things worse, I read that Odin Option "Nand Erase" just erased user data, so I thought I might as well try it, and as a result, I now can't flash even the (XSA) firmware because of ODIN failing and I now have an "An Error has Occurred while updating the device software. Use the emergency recovery function in the smart switch PC Software.". I am a bloody idiot :good: . Oh, I have tried multiple versions of Both Samsung Kies & Smart Switch (Which both had the option for "recovery & initialisation"), however, I get a message that my device is unsupported after adding in my device model and S/N. I tried a PIT file and then found out it's now included in all the latest firmware img files.. so yeah lol. Fun times. Soooo I feel like I am out of Options, nothing I do is working. The worst of all this is my wife is not happy haha which means after years of tinkering with android phones (flashing custom ROMS, Kernels, Root Solutions, e.c.t ), this may be the end of the road for me if I can't fix this phone. I really hope this thread isn't true too : https://forum.xda-developers.com/galaxy-s8+/help/sm-g955fd-access-download-mode-t3748228
So Please, someone help me out if it is at all fixable even if it requires opening the phone up lol.
The stats i have on download mode are the following:
RMM State as Prenormal
OEM Lock: OFF
FRP Lock: OFF
CARRIER_ID: OPS (which is super weird because it only accepts XSA to be flashed :S )
Secure download: Enabled
System Status: Custom
Warranty Void: 1
Current Binary: Samsun Official
If you need more, just let me know.
Ok, quick update: I have got rid of the error that I mentioned. I managed to flash XSA firmware again, it went to the blue Andriod is updating the system screen, then started "erasing" then rebooted and nothing again, still only download mode available. Nothing happens when I try to turn it on or try recovery mode.
This firmware you mentioned XSA - G955FXXU3CRGH i would double check. As far as I know Australia doesn't have a version 3 bootloader yet whether unbranded.telstra or Optus.
Quick Update: Maybe Fixed now!
Even though no one has replied yet, as it's only been an hour or so. I just wanted to let anyone else know who is experiencing a similar issue in the future on how to possibly fix it.
This was a real nightmare, however quick disclaimer, I am not responsible for any damage incurred to your device/property by following my instructions.
So the way I have fixed it, is I flashed the AP file only (from the firmware zip i had downloaded from SamFirm) with "Auto Reboot" Off. When ODIN finished, I held the Vol Down + power button, to reset it. It gave me a blue "No Command" Screen, I then waited and it then went black and the recovery screen appeared. I cleared the cache, rebooted to bootloader, which it didn't turn back on, so I left it because I thought it was the same thing. Came back 10 mins later and turned it on (or hard restarted, can't remember) and it worked. It booted!
I did soon learn it looks like it was having a charging problem because it had no charge and kept telling me there was water in the port (even though it was dry), I restarted it again after putting it on a wireless charging pad and it is seeming fine so far with the USB charger. So big note to anyone in the future, that it could be possibly bugging out with charging as well if you can't get it back on. I did have the device tell me here and there the last two days that there was water in the port when it was off. So kinda weird.
I know this all sounds a little hocus pocus, superstitious almost, but hey, my phone is working, so maybe replicating my actions may just help lol. :cyclops:
spawnlives said:
This firmware you mentioned XSA - G955FXXU3CRGH i would double check. As far as I know Australia doesn't have a version 3 bootloader yet whether unbranded.telstra or Optus.
Click to expand...
Click to collapse
Oh right, well, I did hear that SamFirm is not supported anymore, as that's where that firmware came from. Maybe it's dishing out incorrect firmware now? Possible the structure of where ever it is getting its firmware from (pretty sure it's pulled from samsung) has possibly been altered?
Just for reference I use www.updato.com for downloading firmware it is usually up to date. No reference to the firmware you mentioned (not for Australia anyway)
The screenshot I took: Imgur link:
https://imgur.com/a/lqyzWW7
Interesting I'll keep a lookout for it. Still on nougat 7.0 (XSA) no plans to upgrade yet until some issues are fully resolved ( out of beta stage that is ).
spawnlives said:
Interesting I'll keep a lookout for it. Still on nougat 7.0 (XSA) no plans to upgrade yet until some issues are fully resolved ( out of beta stage that is ).
Click to expand...
Click to collapse
Yeah, it's seeming to work now, but my fast charge isn't working. However, my other oreo ROM didn't work with fast charge either. So i am unsure if it is my phone or an orio bug :/ lol
Well at least you got it working and not using as a door stop
that was really sad story man.....
spawnlives said:
Well at least you got it working and not using as a door stop
Click to expand...
Click to collapse
Yeah haha, so glad it's not a door stop haha

Help with NFC Crashing - AT&T S8 Active

Hey,
Need some help. My brand new AT&T S8 Active arrived yesterday. Since I am located outside the US I'm stuck with utilising Odin to update the software.
The current version listed on the AT&T website was 5CSK1 and I was able to track down the update:
https://forum.xda-developers.com/showpost.php?p=81251867&postcount=743
It installed successfully, everything is going well however I am unable turn on NFC. The toggle found in the settings menu is off and when I attempt to switch it on it greys out for a few seconds then the 'NFC keeps stopping' error appears on the bottom of the screen.
I've cleared the cache/data for the NFC app - no luck,
I've performed a factory reset via recovery menu - no luck.
I've installed the previous build 5CSJ3 from: https://forum.xda-developers.com/showpost.php?p=80903399&postcount=187 with a factory reset straight after - no luck.
I'm currently back on the latest K1 build.
Logcat shows errors with 'libnfc_nci' and a 'Fatal Exception' for the 'com.android.nfc' process. And to top it all off the NFC app is draining my battery.
If anyone can help me that would be awesome.
dchalkley said:
Hey,
Need some help. My brand new AT&T S8 Active arrived yesterday. Since I am located outside the US I'm stuck with utilising Odin to update the software.
The current version listed on the AT&T website was 5CSK1 and I was able to track down the update:
https://forum.xda-developers.com/showpost.php?p=81251867&postcount=743
It installed successfully, everything is going well however I am unable turn on NFC. The toggle found in the settings menu is off and when I attempt to switch it on it greys out for a few seconds then the 'NFC keeps stopping' error appears on the bottom of the screen.
I've cleared the cache/data for the NFC app - no luck,
I've performed a factory reset via recovery menu - no luck.
I've installed the previous build 5CSJ3 from: https://forum.xda-developers.com/showpost.php?p=80903399&postcount=187 with a factory reset straight after - no luck.
I'm currently back on the latest K1 build.
Logcat shows errors with 'libnfc_nci' and a 'Fatal Exception' for the 'com.android.nfc' process. And to top it all off the NFC app is draining my battery.
If anyone can help me that would be awesome.
Click to expand...
Click to collapse
ugh, the active line... there hasnt ever been much support for those. All you can really do is keep flashing the stock firmware and hope that the errors resolve themselves.
Side note: have you noticed how they stopped making the active phones? They were a dismal failure. All they are is the regular phone in a case that you cant take off :/
dchalkley said:
Hey,
Need some help. My brand new AT&T S8 Active arrived yesterday. Since I am located outside the US I'm stuck with utilising Odin to update the software.
The current version listed on the AT&T website was 5CSK1 and I was able to track down the update:
https://forum.xda-developers.com/showpost.php?p=81251867&postcount=743
It installed successfully, everything is going well however I am unable turn on NFC. The toggle found in the settings menu is off and when I attempt to switch it on it greys out for a few seconds then the 'NFC keeps stopping' error appears on the bottom of the screen.
I've cleared the cache/data for the NFC app - no luck,
I've performed a factory reset via recovery menu - no luck.
I've installed the previous build 5CSJ3 from: https://forum.xda-developers.com/showpost.php?p=80903399&postcount=187 with a factory reset straight after - no luck.
I'm currently back on the latest K1 build.
Logcat shows errors with 'libnfc_nci' and a 'Fatal Exception' for the 'com.android.nfc' process. And to top it all off the NFC app is draining my battery.
If anyone can help me that would be awesome.
Click to expand...
Click to collapse
Might try redownloading a different firmware from a differ location. I had this issue on a lg back in the day the camera wouldnt work no matter what I always restored stock with one firm I had. And it ended up being a bad download. Another possibility is a bad NFC chip. If it's new I'd have it warranted
Thankyou, Thankyou Youdoofus and TheMadScientist for your advice.
Woke up early today (3am) with coffee in hand I tried again downloading the K1 and J3 builds; neither worked.
Unfortunately there's no alternative download for them... Google points to the XDA forums which seem to come from some Russian forum.
I've gone to an earlier build - 5CSI3 - https://forum.xda-developers.com/showpost.php?p=80505887&postcount=186 which works.
So it's not a NFC chip issue, yay. Now, just need to figure out what I'll do when the next update hits at the end of this month.
dchalkley said:
Thankyou, Thankyou Youdoofus and TheMadScientist for your advice.
Woke up early today (3am) with coffee in hand I tried again downloading the K1 and J3 builds; neither worked.
Unfortunately there's no alternative download for them... Google points to the XDA forums which seem to come from some Russian forum.
I've gone to an earlier build - 5CSI3 - https://forum.xda-developers.com/showpost.php?p=80505887&postcount=186 which works.
So it's not a NFC chip issue, yay. Now, just need to figure out what I'll do when the next update hits at the end of this month.
Click to expand...
Click to collapse
Make sure your using the latest odin build 3.13. I dont have an active. **** I read it wrong so it does work on other builds?
TheMadScientist said:
Make sure your using the latest odin build 3.13. I dont have an active. **** I read it wrong so it does work on other builds?
Click to expand...
Click to collapse
Yeah, it's working on the 5CSI3 build from October 2019, there's been two recent updates since then (and another will come at the end of the month). I don't know what's happening as no one else has reported this issue .
Just wanting to be on the most recent version for security and the annoyance of having data wiped every update.
Edit: Yeah, Odin v3.13.1 . No errors being displayed, all green.
This issue is very likely to be caused by 3rd party sim unlock or FRP removal and meddling with knox.
I have been trying to get around this problem and it seems it is either a security measure to disable nfc payments on triggering knoxguard or problem with modem.
this problem started after CSJ3 update afaik and only on some phones, if someone can explain this would be great.
Solution:
You will lose all data so backup is recommended
Remove your SIM card, re-install the firmware with ODIN and check Nand Erase auto reboot and F. reset time
Check your KG status(checking or prenormal) on the bootloader, and in settings>device care you will see Security is disabled and it crashes when you click it.
I also noticed the settings menu is weird with many broken options and dailer codes dont work anymore.
EDIT: Workaround Solution:
THIS IS FOR G892A ONLY who have problem with NFC after updating to builds after December 2019
Disclaimer: do at your own risk and can break your phone signal or system detected as rooted/custom
note: you will lose all data, ONLY check "Auto Reboot" and "F. Reset Time" in odin
1) Backup your data
2) Delete your google account, so FRP : OFF in bootloader (this can cause problems if not done)
3) Flash 5 firmware files G892AUCS5CTC1 (latest rom with march 2020 security) and get back to bootloader
4) Flash 3 files from G892AUCS5CSI3 : BL, CP and CSC
(odin will say PASS, but recovery will give error)
5) select wipe data partition then reboot to system
when the phone starts you will see NFC logo in statusbar means you are successful
if you get errors while using odin: flash combination file : G892AUCU5ASD1 if this doesnt work it means you have different problem (cable, socket, pc, bad chip)
i tried flashing CP file only and phone booted into UPLOAD mode, so dont panic if you get into UPLOAD mode just reboot with 3 buttons to recovery and start over
Vcek said:
This issue is very likely to be caused by 3rd party sim unlock or FRP removal and meddling with knox.
I have been trying to get around this problem and it seems it is either a security measure to disable nfc payments on triggering knoxguard or problem with modem.
this problem started after CSJ3 update afaik and only on some phones, if someone can explain this would be great.
Solution:
You will lose all data so backup is recommended
Remove your SIM card, re-install the firmware with ODIN and check Nand Erase auto reboot and F. reset time
Check your KG status(checking or prenormal) on the bootloader, and in settings>device care you will see Security is disabled and it crashes when you click it.
I also noticed the settings menu is weird with many broken options and dailer codes dont work anymore.
EDIT: Workaround Solution:
THIS IS FOR G892A ONLY who have problem with NFC after updating to builds after December 2019
Disclaimer: do at your own risk and can break your phone signal or system detected as rooted/custom
note: you will lose all data, ONLY check "Auto Reboot" and "F. Reset Time" in odin
1) Backup your data
2) Delete your google account, so FRP : OFF in bootloader (this can cause problems if not done)
3) Flash 5 firmware files G892AUCS5CTC1 (latest rom with march 2020 security) and get back to bootloader
4) Flash 3 files from G892AUCS5CSI3 : BL, CP and CSC
(odin will say PASS, but recovery will give error)
5) select wipe data partition then reboot to system
when the phone starts you will see NFC logo in statusbar means you are successful
if you get errors while using odin: flash combination file : G892AUCU5ASD1 if this doesnt work it means you have different problem (cable, socket, pc, bad chip)
i tried flashing CP file only and phone booted into UPLOAD mode, so dont panic if you get into UPLOAD mode just reboot with 3 buttons to recovery and start over
Click to expand...
Click to collapse
Hello There!..kind of new about this so..long story short..
Phone had Android 8, and I really love Night mode on Android 9, so...I've found BL, AP, CP, CSC, USER Data ROM for GALAXY S8 ACTIVE AT&T Unlocked, however..I am a little bit afraid of any NAND Erase.
I am not an expert, but I can tell you are. By any chance do you have any vide or graphic tutorial abot how you can perform these actions? It is very odd that I am unable to have any *# codes working, and lately, I've received this odd message about NFC Service has stopped, so...any graphic step by step guide will be highly appreciated it.
I've tried ....soft reset, then factory reset, then flash again ODIN (BL, AP,CP, CSC and USER DATA ) But I have no idea how to back up my data, and it will be very helpful to have G892AUCS5CSI3 as well.
Thank you very much for your time, I hope you can help me and I appreciate very much your time.
The one that I have is AP_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar
BL_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
CP_G892AUCS5CTC1_CP15398738_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
CSC_ATT_G892AATT5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
USERDATA_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
SOLVED!
So...I've followed the steps to install only BL, CP and CSC using G892AUCS5CSI3...however, the system started as usual, and actually did not work =(
RESOLUTION:
INSTALL THE FULL G892AUCS5CSI3. Worked as magic =)
thank you for the thread!!
moncd6 said:
Hello There!..kind of new about this so..long story short..
Phone had Android 8, and I really love Night mode on Android 9, so...I've found BL, AP, CP, CSC, USER Data ROM for GALAXY S8 ACTIVE AT&T Unlocked, however..I am a little bit afraid of any NAND Erase.
I am not an expert, but I can tell you are. By any chance do you have any vide or graphic tutorial abot how you can perform these actions? It is very odd that I am unable to have any *# codes working, and lately, I've received this odd message about NFC Service has stopped, so...any graphic step by step guide will be highly appreciated it.
I've tried ....soft reset, then factory reset, then flash again ODIN (BL, AP,CP, CSC and USER DATA ) But I have no idea how to back up my data, and it will be very helpful to have G892AUCS5CSI3 as well.
Thank you very much for your time, I hope you can help me and I appreciate very much your time.
The one that I have is AP_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar
BL_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
CP_G892AUCS5CTC1_CP15398738_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
CSC_ATT_G892AATT5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
USERDATA_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
Click to expand...
Click to collapse
You can backup your data with Samsung backup and restore to Samsung cloud or to your PC with Samsung's Smart Switch app.
As for tutorial I'll try to make one with images for the latest ROM G892AUCU5CTF4 dated 20-Aug-2020 with August security patch. I'll upload it later as I still have to backup my phone before updating.
Thanks!
Thank you so much!
Is it G892AUCU5CTF4 a estable versión for S8 Active? Or does it has any other bugs? I had to "downgrade" and now things are pretty cool, however, I would love to have the newest version. Thank you!
moncd6 said:
Thank you so much!
Is it G892AUCU5CTF4 a estable versión for S8 Active? Or does it has any other bugs? I had to "downgrade" and now things are pretty cool, however, I would love to have the newest version. Thank you!
Click to expand...
Click to collapse
It doesn't have any bugs but some people have issue with flashing new builds, if you have this issue just install CSI3 build or earlier
dchalkley said:
It installed successfully, everything is going well however I am unable turn on NFC. The toggle found in the settings menu is off and when I attempt to switch it on it greys out for a few seconds then the 'NFC keeps stopping' error appears on the bottom of the screen.
I've cleared the cache/data for the NFC app - no luck,
I've performed a factory reset via recovery menu - no luck.
I've installed the previous build 5CSJ3 from: https://forum.xda-developers.com/showpost.php?p=80903399&postcount=187 with a factory reset straight after - no luck.
... And to top it all off the NFC app is draining my battery.
Click to expand...
Click to collapse
Same. I also tried CTA2 and CTL1. Everything after CSI3 has NFC crashing and excessive battery drain. I've tried multiple flashes on multiple phones.
dchalkley said:
I tried again downloading the K1 and J3 builds; neither worked.
Unfortunately there's no alternative download for them... Google points to the XDA forums which seem to come from some Russian forum.
I've gone to an earlier build - 5CSI3 - https://forum.xda-developers.com/showpost.php?p=80505887&postcount=186 which works.
So it's not a NFC chip issue, yay. Now, just need to figure out what I'll do when the next update hits at the end of this month.
Click to expand...
Click to collapse
Same.
dchalkley said:
I don't know what's happening as no one else has reported this issue .
Edit: Yeah, Odin v3.13.1 . No errors being displayed, all green.
Click to expand...
Click to collapse
Same here. I used Odin 3.14.1, though.
Vcek said:
Solution:
You will lose all data so backup is recommended
Remove your SIM card, re-install the firmware with ODIN and check Nand Erase auto reboot and F. reset time
Click to expand...
Click to collapse
This did not work for me, not even with "Nand Erase" checked.
moncd6 said:
It is very odd that I am unable to have any *# codes working, and lately, I've received this odd message about NFC Service has stopped, so...
Click to expand...
Click to collapse
Same. The problem of the secret dialer codes not working parallels the NFC problem for me; that is to say that it doesn't work on any firmware after CSI3.
moncd6 said:
SOLVED!
So...I've followed the steps to install only BL, CP and CSC using G892AUCS5CSI3...however, the system started as usual, and actually did not work =(
RESOLUTION:
INSTALL THE FULL G892AUCS5CSI3. Worked as magic =)
thank you for the thread!!
Click to expand...
Click to collapse
Can you please upload G892AUCS5CSI3? it's all dead links i got
rerenz said:
Can you please upload G892AUCS5CSI3? it's all dead links i got
Click to expand...
Click to collapse
Same. I'm not sure where I originally got it from, but here's a reupload from my archives. I created a list of MD5 checksums if you care to check the five files for corruption.
voidxor said:
Same. I'm not sure where I originally got it from, but here's a reupload from my archives. I created a list of MD5 checksums if you care to check the five files for corruption.
Click to expand...
Click to collapse
Finally, it works! My NFC is back. Thanks, pal.

Categories

Resources