Database Users

Wifi issue on Galaxy S4 I9505

Hi all,
Ever since updating to the latest MGA via OTA firmware nearly 2 weeks ago the Wifi has been causing me a lot of issues. The following evening after updating the firmware, the wifi just randomly turned itself off and would refuse to turn on again. When I attempted to turn it back on via the widget, it would go grey as it's attempting to turn on but then it would just stay at that and it will not turn on at all. After a few minutes it will either go back to being completely turned off or the phone would just reboot itself.
Now, I have tried several things to rectify the problem i.e. applying the MGA wifi fix, factory restoring the phone via the settings and also in Kies, downgrading back down to the MEA firmware, re-flashing the stock MGA firmware via Odin and re-flashing both the MEA & MGA modems seperately - all to no sucess!
At the same time while all this is going on, the phone itself will sometimes randomly reboot itself when attempting to turn on the wifi or even in the rare case when the wifi does turn on and it will work for 5 or so minutes - the phone will reboot itself again while trying to simultaneously update various apps through the play store.
Lastly, the phone has already been sent back to Samsung a few days ago regarding this issue and the phone was returned back to me yesterday with Samsung apparently stating that they had diagnosed and found an issue with the phone (even though they could not tell me what??) and that they had sucessfully repaired it. Upon turning the phone back on going through setting up the phone again, I come to the wifi connection and guess what... it doesn't turn on. Yep that's right, I'm still stuck with the same problem!
I got straight onto Samsung on the phone and complained about this as I'm not happy at all, and they have agreed to have the phone back in for another repair and apparently something will be done properly this time.
It's not good enough though, to me all it looks like that Samsung have done their end on the original repair is re-flash it with the MGA firmware once again, shove it back in the box back to me and hope for the best. Even the Samsung agent on the phone yesterday could not tell me exactly how they apparently repaired the phone as there was not anything on the repair report what so ever, unbelievable!
Anyway, do any of you guys have any ideas with what else I can do my end to try and rectify the problem? To me though, this sounds like a physical hardware fault that only Samsung themselves can sort out...
Thanks - Liam

AndroidLEK said:
Hi all,
Ever since updating to the latest MGA via OTA firmware nearly 2 weeks ago the Wifi has been causing me a lot of issues. The following evening after updating the firmware, the wifi just randomly turned itself off and would refuse to turn on again. When I attempted to turn it back on via the widget, it would go grey as it's attempting to turn on but then it would just stay at that and it will not turn on at all. After a few minutes it will either go back to being completely turned off or the phone would just reboot itself.
Now, I have tried several things to rectify the problem i.e. applying the MGA wifi fix, factory restoring the phone via the settings and also in Kies, downgrading back down to the MEA firmware, re-flashing the stock MGA firmware via Odin and re-flashing both the MEA & MGA modems seperately - all to no sucess!
At the same time while all this is going on, the phone itself will sometimes randomly reboot itself when attempting to turn on the wifi or even in the rare case when the wifi does turn on and it will work for 5 or so minutes - the phone will reboot itself again while trying to simultaneously update various apps through the play store.
Lastly, the phone has already been sent back to Samsung a few days ago regarding this issue and the phone was returned back to me yesterday with Samsung apparently stating that they had diagnosed and found an issue with the phone (even though they could not tell me what??) and that they had sucessfully repaired it. Upon turning the phone back on going through setting up the phone again, I come to the wifi connection and guess what... it doesn't turn on. Yep that's right, I'm still stuck with the same problem!
I got straight onto Samsung on the phone and complained about this as I'm not happy at all, and they have agreed to have the phone back in for another repair and apparently something will be done properly this time.
It's not good enough though, to me all it looks like that Samsung have done their end on the original repair is re-flash it with the MGA firmware once again, shove it back in the box back to me and hope for the best. Even the Samsung agent on the phone yesterday could not tell me exactly how they apparently repaired the phone as there was not anything on the repair report what so ever, unbelievable!
Anyway, do any of you guys have any ideas with what else I can do my end to try and rectify the problem? To me though, this sounds like a physical hardware fault that only Samsung themselves can sort out...
Thanks - Liam
Click to expand...
Click to collapse
Well I have only had this problem with rooting phones etc... to me this happened with so many ROMs I tried. Even certain stock roms. I am not sure fully how I fixed it, but I know now I am running the OMEGA rom and this seemed to have worked for me so possible to try that? Just an option

PSPNikos said:
Well I have only had this problem with rooting phones etc... to me this happened with so many ROMs I tried. Even certain stock roms. I am not sure fully how I fixed it, but I know now I am running the OMEGA rom and this seemed to have worked for me so possible to try that? Just an option
Click to expand...
Click to collapse
When I first downgraded back down to the MEA firmware that I was linked to from another forum, I discovered straight after flashing that it was a pre-rooted ROM and the wifi still would not turn on then.
The phone has been sent back to Samsung again today for another repair but last night as a last ditched attempt, I downloaded & flashed the stock XXUAMDM firmware from April and the wifi still refused to turn on.
I'm still convinced that the problem itself is hardware related rather than software based going by that the problem is still present regardless of what ROM I'm on, it's just a case of trying to get Samsung to see that. I can understand now why that Samsung the first time round probably only did a fresh re-flash of the MGA firmware instead of going ahead and taking the phone apart/replacing parts as I imagine it's very labour intensive/standard procedure and not only that - the S4's mainboard (from what I've seen the wifi module is part of the mainboard) retails at over £200 which is a hefty repair cost on their part.
Liam

It is some sort of permissions issue.
If you do chmod 777 on /dev/*, /system/etc/wifi/* it should be working.
The only thing I haven't figured out is why
And it has to be done again after rebooting the phone, wich makes me sad.....

How I fixed my WiFi and sound problems after updating to latest firmware over
Hi there. (Sorry for any mistake about my English). By the way, I'm newbie on Android.
After freaking out about my WiFi problem, i didn't even care about the others problems like the sound, and I don't know if there were or if there is still some, but WiFi and sound got fixed.
After a lot of research on Google and XDA I came to the conclusion that if I could just re-install the firmware, I had
1- I Download the same firmware you are on (i guess it safer this way) I got the same (I9505VJUEMKE) that had caused the problem when was update trough Kies.
GT-I9505_PDA_I9505VJUEMKE_4.3
Changelist: 2210919
Build date: Wed, 27 Nov 2013
CSC: I9505ZTOEMKE_ZTO_Brazil
MODEM: I9505VJUEMKE
Gdrive: (créditos ao +Alexandre Affonso - Vlw)
Two links for download this firmware. (really fast download since its on gdrive)
goo.gl / UrZWAE .
goo.gl / omJC9e  "
2- Unpack the Zip File
3- Putt the phone in "Download Mode"
4- Open Odin 3.07 and Connected the cable. (check if Odin linked a port to your phone, i didnt get any color change, just the COM Port number and the "added" mentioned on Odin)
5- Load the firmware on "PDA", wait a few seconds till Odin load it.
6- Click Start and wait the whole process. Don't disconnect the cable until Odin says that it was Successfully.
Finished!
After all I did the root with Odin + CF Auto Root + Supersu and So far everything is fine and better than before.
Hope I can help few of you guys.
Thanks.

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

S4 i337M - No sound on calls (in/out) after flashing Stock 5.01 Loliipop ROM

Flashed stock 5.01 ROM and phone call function stopped working.
When calling, there is a connection but no sound can be heard on either end of call.
It WAS working briefly and briefly managed to 'fix' it. Everything else functions correctly. Wifi calling works perfect. SMS works perfect.
I have searched forums and Googled this (about 9 hours worth so today) so quite at a loss how to proceed.
Tried forums suggestions to:
- disable Google Now/OK Google voice functions
- disable S Voice functions
- removing and replacing SIM/SD card
- wiping cache
- air dusting earphone port
- clear Google Play services cache and data
- clear Drive cache
- boot into Safe Mode, still not working
Additionally tried re-wipe cache/DALVIK/data/entire device and re-installed different stock ROM, same problem
I flashed both BELL and Rogers stock Lollipop ROM from XDA post (http://forum.xda-developers.com/galaxy-s4-att/general/sgh-i337m-canadian-stock-official-t3082758) via Odin
Any suggestions???
The only thing that worked briefly was:
In App Info for the Phone App, I did 'clear data' and 'clear cache' for all THREE Phone Apps (yes, there are three, I don't know if this is normal or not as this is first time with Lollipop). This allowed the phone to work BRIEFLY, then problem returned.

Try flashing the latest stock from sammobile.com.

Hi,
Attempting this but both Bell and Rogers Lollipop firmware .ZIP are corrupt from Sammobile.com I've contacted their admin to advise of this as I have tried downloading multiple times with the same corrupt file result.
Are there any other reputable download site?
audit13 said:
Try flashing the latest stock from sammobile.com.
Click to expand...
Click to collapse

I did a nandroid / efs backup with TWRP. Would there be any problems in restoring to 4.4.2 Kitkat using that???
audit13 said:
Try flashing the latest stock from sammobile.com.
Click to expand...
Click to collapse

Anything to be concerned about reverting via TWRP to Kitkat
Tried Emergency Firmware recovery via KIES, no luck, re-wiped cache, did factory reset in stock recovery, still no good.
Tried swapping Sim card tray and Earphone port (had a parts phone kicking around that is stuck on boot logo ((TWRP/ODIN Flashing does not recover this phone sadly)))
Will try to revert to Kitkat via TWRP next.
Note: I AM able to make normal calls as long the device is connected via Bluetooth to my car or to my bluetooth headset. Discovered this after more googling/forum searching.
rogue_element said:
I did a nandroid / efs backup with TWRP. Would there be any problems in restoring to 4.4.2 Kitkat using that???
Click to expand...
Click to collapse

What are you using to download from sammobile? I always use a win 7 machine.
What are program is being used to unzip the rom? You're only unzipping once?

Hi,
I'm using Win7 x64 Home Premium. WinRAR to unzip.
Since posting last I have restored Nandroid backup - phone function still didn't work and Google Play Services glitched out.
So, next downloaded 4.4.2 Kitkat from Sammobile, extracted no problem, flashed via Odin (no errors)- still no phone function
Wiped phone yet again, re-installed Kitkat one more time with Odia (no errors) - still no phone function
Used Kies to do Firmware Update and Initialization, (no errors) - still no phone function
Re-wiped again and used Kies once more, this time not doing App Restore function in case there is App causing issues and not signing into Google or Samsung Account to avoid anything restoring - still not working but interestingly there was a OTA update to 5.01 that installed fine - end result... phone function still not working.
If anybody can offer me another suggestion to try, I'll be happy to attempt but at this point I'm prepared to say f**k it and buy another phone.
I've been at this since last Saturday.
audit13 said:
What are you using to download from sammobile? I always use a win 7 machine.
What are program is being used to unzip the rom? You're only unzipping once?
Click to expand...
Click to collapse

After flashing with Odin, are you able to confirm that the bootloader and baseband match each other and the rom that was flashed? The imei is correctly displayed?
Since you are able to make calls via Bluetooth, are you able to hear the other party and the other party can hear you? What about calls via speakerphone?

Yes, I've attached a screenshot. Bootloader and baseband do match. This last round of install was done via OTA update that popped up after installing Kitkat. I just rolled with it as I figured if it's coming from Samsung directly, why not.
When making calls via Bluetooth, there are no issues. It functions as normal. It is just through the Phone App itself.
Interestingly, I discovered I can make outbound call no problem via Google Hangouts dialer as well. This is incredibly frustrating.
audit13 said:
After flashing with Odin, are you able to confirm that the bootloader and baseband match each other and the rom that was flashed? The imei is correctly displayed?
Since you are able to make calls via Bluetooth, are you able to hear the other party and the other party can hear you? What about calls via speakerphone?
Click to expand...
Click to collapse

Did you try reflashing the OH1 ROM? Sounds redundant but I'm not sure what else to suggest short of putting the motherboard into another phone and trying it out.

Hi audit13,
Haven't tried installing mobo in another phone, will give that a whirl for sh*ts''grinz.
Been an incredibly frustrating process. Another interesting thing that has been happening is that I notice the boot up sequence takes a lot longer than I recall.
Have been trying to avoid using the phone.
Re-flashed OH1 using ODIN and earlier tonight, Kies. Still not working.
I'm wondering if doing something like reverting to very old ROM may do the trick instead.
Do you happen to know how old I can go? Jellybean? I will check sammobile and see what the oldest they have there.
Phone functions perfectly fine via Bluetooth still, IP calls via WhatsApp and Hangouts Dialer also work per normal. Just trying to place normal calls does not work.
Have also had bootloops lately too I notice.

You can go as far back as 4.4.2 from my experience.
You'r performing a factory wipe right after flashing in Odin?
Initial boot up after flashing and wiping usually takes a long time but it should become quicker as the cache builds up with each reboot.

@rogue_element have you found a solution?
My wife's phone is having the exact same problem.
It started happening like a couple months ago. Haven't flashed anything to it. It just suddenly happened.

Hi ImpheOtus,
No, I'm still searching for a solution. I tried reflashing and then factory reset per audit13 suggestions but still no luck. I even tried swapping the ear piece module from a parts phone and no go. Extremely frustrating. Shopping for a new phone at this point but I'm still trying for a resolution as I'm stubborn and don't like giving up.

Hi audit13,
I'm actually suspecting the something else at this point (virus/malware, etc.) in the bootloader or deeper. There has been other random odd behavior, and while I don't rule out something like a hardware problem either, the behavior has been very strange.
Perversely, my wife's phone briefly experienced the same issue as mine but it cleared up after a reboot.
I will go hunting for a tut on flashing bootloader and kernel only next to see if that helps. If you have any suggestions of where to look for tutorial and/or files please feel free.
I tried flashing 4.4.2 but no luck there either btw

Okay, try flashing with a pit file and the latest stock rom from sammobile.

audit13 said:
Okay, try flashing with a pit file and the latest stock rom from sammobile.
Click to expand...
Click to collapse
Any particular suggestions regarding locating/selecting a pit file?

Is your phone a 16 GB sgh-i337m from Rogers, Telus, or Bell?

audit13 said:
Is your phone a 16 GB sgh-i337m from Rogers, Telus, or Bell?
Click to expand...
Click to collapse
Its a Bell SGH-I337M 16gb phone

I attached a 16 GB pit file from my i337m.

Weird software mix nougat/oreo

Hi there. The strangest thing happened to me today.
Didn't have the patience to wait an oreo update on my galaxy s8 and downloaded it (official firmware not beta version), installed it using odin and ran the software for a week without any issues. I admit the firmware was ment foe germany, not for my country but i know that it doesn't matter as long as the firmware is an official one. Today in the morning got a notification that phine memory is almost full and notices that my oreo saw only 16gb of memory instead of 64. Did a quick factory reset and from this point on my pfone went crazym enterd into a nasty bootloop, couldn't do a thing with my phone. Tried erase/restore factory setting /erase cache partition, the same result. Ok, downloaded nougat, installed it, phone seems ok with one exception. My nougat looks kinda oreo! Some icons in the phones settings look like oreo icons, bixby under oreo does not have a disable key option under nogat there is a disable key - i don't have that though i use nougat, some icons in the settinga menu are doubled and so many other weird things. If i check software version it states 7.0. Ok, later in the afternoon saw that there was released oreo for my country, checked software update...says that it is up to date. My friends's phone is identical to mine, he got the oreo update, i didn't. Any idee what is going on? How in the world can i have nougat on my phone with oreo icons after a fresh nougat install? I know it sound weird but i have had several samsung phones and have played around with official firmwares but never saw such a great mess my phone is in. Or maybe i am missing something. Thanks alot for your time. Cheers.

Lolobacsi said:
Hi there. The strangest thing happened to me today.
Didn't have the patience to wait an oreo update on my galaxy s8 and downloaded it (official firmware not beta version), installed it using odin and ran the software for a week without any issues. I admit the firmware was ment foe germany, not for my country but i know that it doesn't matter as long as the firmware is an official one. Today in the morning got a notification that phine memory is almost full and notices that my oreo saw only 16gb of memory instead of 64. Did a quick factory reset and from this point on my pfone went crazym enterd into a nasty bootloop, couldn't do a thing with my phone. Tried erase/restore factory setting /erase cache partition, the same result. Ok, downloaded nougat, installed it, phone seems ok with one exception. My nougat looks kinda oreo! Some icons in the phones settings look like oreo icons, bixby under oreo does not have a disable key option under nogat there is a disable key - i don't have that though i use nougat, some icons in the settinga menu are doubled and so many other weird things. If i check software version it states 7.0. Ok, later in the afternoon saw that there was released oreo for my country, checked software update...says that it is up to date. My friends's phone is identical to mine, he got the oreo update, i didn't. Any idee what is going on? How in the world can i have nougat on my phone with oreo icons after a fresh nougat install? I know it sound weird but i have had several samsung phones and have played around with official firmwares but never saw such a great mess my phone is in. Or maybe i am missing something. Thanks alot for your time. Cheers.
Click to expand...
Click to collapse
Flash it again with the current release for your region using ODIN with CSC that will wipe your phone also.
Should fix it.

rigocalin said:
Flash it again with the current release for your region using ODIN with CSC that will wipe your phone also.
Should fix it.
Click to expand...
Click to collapse
Hi,
Found out what was the problem. Each and every time when i was using odin to flash my phone, used only the AP file. Saw somwhere that someone added in odin the AP, BL, CP, CSC files too. Sammobile says that ony the AP file should be used (no doubt) but didn't work in my case.
So, added all 4 files in odin and could sucessfully flash nougat, then update to oreo. Got curios if i flashed oreo only, would my phone lose it's mind and flashed it BUT added in odin all the 4 files and worked like a charm.
Thanks alot for your time.
Cheers.

Device not starting/black screen after stock-ROM flash via Odin

Hello, everyone,
I tried to install LineageOS on my S10 Plus yesterday. That worked so far, but I found that it didn't have a decent camera app and the Samsung Watch wasn't that easy to connect either. So I thought I'd just go back to the Stock ROM again. I then downloaded the latest stock firmware according to this guide and installed it with Odin. The installation also runs through, after the installation the mobile phone starts and after the start screen there is an Android man with the signature "Erasing". After a few seconds, the device turns off and stays black. Even if I put it on the charger or try to restart it, nothing happens. I keep getting into download mode and recovery, but that's about it. Multiple reinstallations and resets via the recovery didn't help - the phone just won't start.
I used the CSC_... and not the HOME_CSC_... at the firmware is the right one for my phone.
Is there any way I can salvage the device? I'm afraid that something in the memory is defective now, which has nothing to do with the flashing itself. Do you have any ideas?
Many thanks!

tefracky said:
Hello, everyone,
I tried to install LineageOS on my S10 Plus yesterday. That worked so far, but I found that it didn't have a decent camera app and the Samsung Watch wasn't that easy to connect either. So I thought I'd just go back to the Stock ROM again. I then downloaded the latest stock firmware according to this guide and installed it with Odin. The installation also runs through, after the installation the mobile phone starts and after the start screen there is an Android man with the signature "Erasing". After a few seconds, the device turns off and stays black. Even if I put it on the charger or try to restart it, nothing happens. I keep getting into download mode and recovery, but that's about it. Multiple reinstallations and resets via the recovery didn't help - the phone just won't start.
I used the CSC_... and not the HOME_CSC_... at the firmware is the right one for my phone.
Is there any way I can salvage the device? I'm afraid that something in the memory is defective now, which has nothing to do with the flashing itself. Do you have any ideas?
Many thanks!
Click to expand...
Click to collapse
same thing happened to me today. but I flashed my s10e the bootloader and modem file of android 9 from twrp, the phone did not boot up and I loaded the stock rom again, then when I open it, it's the same as yours, I really need urgent help.
Releases · corsicanu/9820-bootloaders_and_modems
Contribute to corsicanu/9820-bootloaders_and_modems development by creating an account on GitHub.
github.com
EDİT: Anyway, I solved the problem, I flashed the bootloader and modem file that is suitable for my current version from the same site with twrp and the phone turned on. maybe you can solve it by flashing the bootloader and modem file suitable for the current version. try if you want

Thanks a lot, this worked!

tefracky said:
Thanks a lot, this worked!
Click to expand...
Click to collapse
I'm glad it worked.
I was very afraid that the phone died, what did you do for 5 days in this state?
Now I have a question in my mind: When Samsung releases an update in the future, will the bootloader and modem files be updated when we update it with odin? won't it be updated? After that, do we will always update manually as twrp? do you have any idea?

Well, I simply didn't use a mobile phone in these days. It was a very "interesting" experience, but not a huge problem. I sometimes opened WhatsApp as Windows App (interestingly, which works without phone).
I don't know, what happens at a Samsung Update, but until Android 13, I will not update (so probatly never). In our German forum (www.android-hilfe.de), a pre rooted and debloated "Stock"-Firmware is provided, but I can't install it, since my Bootloader is too new (V15 instead V14 for the ROM). When it is possible, I will install this firmware. If you are interested, here is the link: https://www.android-hilfe.de/forum/...3-2022-stock-rom-v2-0-pre-rooted.1000713.html

tefracky said:
Well, I simply didn't use a mobile phone in these days. It was a very "interesting" experience, but not a huge problem. I sometimes opened WhatsApp as Windows App (interestingly, which works without phone).
I don't know, what happens at a Samsung Update, but until Android 13, I will not update (so probatly never). In our German forum (www.android-hilfe.de), a pre rooted and debloated "Stock"-Firmware is provided, but I can't install it, since my Bootloader is too new (V15 instead V14 for the ROM). When it is possible, I will install this firmware. If you are interested, here is the link: https://www.android-hilfe.de/forum/...3-2022-stock-rom-v2-0-pre-rooted.1000713.html
Click to expand...
Click to collapse
thanks, if i'm going to use stock rom i prefer to root it myself