Related
Hi,
I've been do many flash last 24 hours on my Galaxy S4(Model SGH-I337M, Telus). Initialy, i've the factory stock rom, rooted. So, yesterday, i've decided to install Cyanogen mods nightly on my phone. Not the first time i've been used it on my phone. No problem before. So, this night, after a friend show me the release canditate release seem to be more stable, i've been try to put it on my phone. So, accidentaly wipe all the data on my phone. When i'm back home, i've put again the samsung original rom from my operator(4.2.2), found here, on the website, whit odin. All completed succefully, but i've noticed that the wifi won't turn on after the flash, and no sound from the speaker. So, i've put Cyanogen nigthlies again to test if it rom relative, but same issues here, no sound, but the wifi was working. The phone was very instable, so. Then, finaly, put the original rom again, without any rooting. Stuck on samsung logo, that i've finaly got fixed by clear the data and cache. But, no sound, and no wifi. Instable too.
Precision about phone: Unlocked whit the service mode(work), and enabled AWS whit a software and file(tutorial found here)
My question is: Anything else i can do to make my phone work fine again, and does it's possible to make the phone totaly stock? When i boot up, i've noticed that the phone, whit all rom i've try, said on samsung logo: Kernel is not sendroid enfonced, warranty status: kernel, so i can't go to return my phone on warranty whit that. How i can erase that line, and make my phone seem to be no modified?
Just to specify, it's not the first time i flash a phone. Do many flash, whit galaxy s2, s3 and s4, and sure, mine. Got try Cyanogen, stock, know how Odin work and all, try many rom, and before today, never has any problem to do turn back, but now, it's seem to be impossible.
Thank you very much for your help, very appreciated!
I would flash the stock firmware with odin again. After flashing do a factory reset in the stock recovery.
jd1639 said:
I would flash the stock firmware with odin again. After flashing do a factory reset in the stock recovery.
Click to expand...
Click to collapse
I've just try this. Flash the stock rom whit odin, and factory reset on original recovery after. Same, no wifi, no any sound.
Just see yesterday, when i'm flashing, i'm flashing on the bootloader in odin(whit the tar for the stock rom). Today, correct this by flash on the pda section, still not work. Found here on the forum the stock bootloader, rom, csc, and modem, but when i do this whit odin, odin said fail.
Thank very much, i think my phone is dead, and nothing to do to exchange it on warranty.
I think Kies has an emergency firmware recovery mode.... maybe that'll work.
Found a nice guide here: http://forum.xda-developers.com/showthread.php?t=2261153
saj222 said:
I think Kies has an emergency firmware recovery mode.... maybe that'll work.
Found a nice guide here: http://forum.xda-developers.com/showthread.php?t=2261153
Click to expand...
Click to collapse
Just try this. Kies is the worst software i've ever see. The software completely freeze random. When i go to the emergency menu, never, kies recognize my phone here. I've tried to plug my phone, no recognized. Tried without plug it, no recognized. When i plug it, kies said connection in progress, and can stay here 30 min.
I'm a idea of what is my problem. Before do install of cyanogen, i've been applied the samsung official 4.3 update, whit knox. And, according to what i read on many forum, knox is not ereasable, So, it's completely freeze my phone, and nothing to do.
Anyone have the factory telus bootloader and other factory stock items because i want to put it stock.
Thank.
Finally get problems fixed by take the TELUS stock 4.3 ROM and flash it whit Odin. After, can flash cyanogen nightlies again and the phone work well again.
Whit the stock ROM, didn't see any line on the Samsung boot logo that i've rooted. After root this appear again. Knox regardless of ROM installed said 0x1.
If anyone have a fix to put it again 0x0 very appreciated otherwise the phone work fine and thank you very much for your help.
dardares said:
Just try this. Kies is the worst software i've ever see. The software completely freeze random. When i go to the emergency menu, never, kies recognize my phone here. I've tried to plug my phone, no recognized. Tried without plug it, no recognized. When i plug it, kies said connection in progress, and can stay here 30 min.
I'm a idea of what is my problem. Before do install of cyanogen, i've been applied the samsung official 4.3 update, whit knox. And, according to what i read on many forum, knox is not ereasable, So, it's completely freeze my phone, and nothing to do.
Anyone have the factory telus bootloader and other factory stock items because i want to put it stock.
Thank.
Click to expand...
Click to collapse
I've seen worse software, it's no better or worse than iTunes.
Sent from my SGH-I337M using Tapatalk
dardares said:
Finally get problems fixed by take the TELUS stock 4.3 ROM and flash it whit Odin. After, can flash cyanogen nightlies again and the phone work well again.
Whit the stock ROM, didn't see any line on the Samsung boot logo that i've rooted. After root this appear again. Knox regardless of ROM installed said 0x1.
If anyone have a fix to put it again 0x0 very appreciated otherwise the phone work fine and thank you very much for your help.
Click to expand...
Click to collapse
can u plz give me link for the flash file u just flash
i have same problem here after i flash with 4.2.2 no sound and phone freez all time
i like to flash 4.3 so i can fix my phone
thanks
mps5566 said:
can u plz give me link for the flash file u just flash
i have same problem here after i flash with 4.2.2 no sound and phone freez all time
i like to flash 4.3 so i can fix my phone
thanks
Click to expand...
Click to collapse
This is the link i've found whit all the factory stock operator ROM. This is what rescue me.
http://forum.xda-developers.com/showthread.php?t=2269304
@Spacemonkie4207 never my itune was freeze, and i can do basic operation like transfer music or create playlist without any problem. My kies stay on connection in progress, and turn, turn, turn, but never connect. And when it connect, only one operation, and kies completely freeze, stop responding, need to close it, and open it again. Tried many cable, usb cable, reinstalling software, two other computer, but nothing to do.
I recovered back to stock from custom to 4.3 however if you do so, depending on carrier you could lose root and the ability to install custom recovery.
I would revert back to 4.2.2 (as it's knox free) go to samsungupdates (google it) and pull the 4.2.2 for your region and carrier. flash with odin 3.9
you'll lose root, but you can always perform again as long as not on 4.3 (with 4.3 u can still root if you remove all the knox stuff, u just lose warranty).
Az
Here's the story
1. this phone wouldn't boot up after the OTA update, the screen read "firmware upgrade encountered an issue.
please use software repair assistant & try again."
2. used odin 3.09 to reflash pit and the latest nc4 official firmware (I know it can't be rooted, but that's the only choice I have).
3. phone came back alive, worked for t-mobile and verizon sim cards.
Problem:
after a few hours or maybe a day, or maybe a restart, phone won't detect sim card, baseband version shows unkwown, hardware
version is empty, imei, network, MIN, PRL version, ERI version, imeisv, iccid are all "unknown".
What I have done:
phone will be back to normal if I flash the firmware again, I've use odin 3.09 and kies 3 many times.
I also tried flashing different modems, for ex, MI9, MJE, NC2 even NC4. But phone will keep restarting, sometimes the phone is working after
a few restarts. But eventually I will have the same problem again.
I was wondering if someone could point me to the right direction?
nicedog said:
Here's the story
1. this phone wouldn't boot up after the OTA update, the screen read "firmware upgrade encountered an issue.
please use software repair assistant & try again."
2. used odin 3.09 to reflash pit and the latest nc4 official firmware (I know it can't be rooted, but that's the only choice I have).
3. phone came back alive, worked for t-mobile and verizon sim cards.
Problem:
after a few hours or maybe a day, or maybe a restart, phone won't detect sim card, baseband version shows unkwown, hardware
version is empty, imei, network, MIN, PRL version, ERI version, imeisv, iccid are all "unknown".
What I have done:
phone will be back to normal if I flash the firmware again, I've use odin 3.09 and kies 3 many times.
I also tried flashing different modems, for ex, MI9, MJE, NC2 even NC4. But phone will keep restarting, sometimes the phone is working after
a few restarts. But eventually I will have the same problem again.
I was wondering if someone could point me to the right direction?
Click to expand...
Click to collapse
When you flashed the different modems, did you check settings/about the phone to verify that the modem flash " took"? Recommend entering Odin from power off, especially when flashing modems. FWIW, I'm not at all sure this will fix your problem, but it's worth a shot.
cam30era said:
When you flashed the different modems, did you check settings/about the phone to verify that the modem flash " took"? Recommend entering Odin from power off, especially when flashing modems. FWIW, I'm not at all sure this will fix your problem, but it's worth a shot.
Click to expand...
Click to collapse
Yes I did. The baseband version showed MI9 when my phone was still working properly.
nicedog said:
Yes I did. The baseband version showed MI9 when my phone was still working properly.
Click to expand...
Click to collapse
OK. Hopefully someone else will chime in with some suggestions.
one more thing I've done many times so far is, sometimes a full reset will bring it back to normal too.
settings -> backup and reset -> factory data reset.
I don't mind bricking my phone, but maybe someone knows other possible way, say, flashing EFS? I don't even know what that is.
I've been searching for the right solution but I haven't found one yet.
Never ever give up!
I'm the OP and I finally got it working. I simply ran EFS Professional v2.1.73, did a backup and restore of the EFS. That's it!
Did you figure out what efs is?
Sent from my SM-N900V using XDA Premium 4 mobile app
It didn't last long, and using EFS profession for EFS backup/restore never worked again.
I then saw this page the other day,
http://forum.xda-developers.com/showthread.php?t=2610757
So I used odin to flash
pit
official kitkat rom
I also checked these two,
erase nand
erase EFS
the phone booted up fine, I then turned it off and entered recovery mode, did a data and cache wipe, then booted up the phone again, that brought back my imei, my sim card worked again.
Unfortunately I'll lose it again once I flash a custom rom, or perhaps even a reboot.
I'm still searching for a permanent solution. But at least now I can use my sim card with a stock rom
Rom based on which region?
nicedog said:
It didn't last long, and using EFS profession for EFS backup/restore never worked again.
I then saw this page the other day,
http://forum.xda-developers.com/showthread.php?t=2610757
So I used odin to flash
pit
official kitkat rom
I also checked these two,
erase nand
erase EFS
the phone booted up fine, I then turned it off and entered recovery mode, did a data and cache wipe, then booted up the phone again, that brought back my imei, my sim card worked again.
Unfortunately I'll lose it again once I flash a custom rom, or perhaps even a reboot.
I'm still searching for a permanent solution. But at least now I can use my sim card with a stock rom
Click to expand...
Click to collapse
Can you please tell the stock rom based on which CSC ? or country ?
I'm having the same issue. Lost baseband and imei, but never got it recovered. even with stock.
I use this one,
ALL_VZW_N900VVRUCNC4_N900VVZWCNC4_1487472_REV03_user_low_ship_MULTI_CERT.tar.md5
http://www.trueandroid.com/2014/05/n900vvrucnc4-android-442-kitkat.html
Same boat brother, this is what I've posted. So far I'm a week in this situation, battery pull brings it back, any mod like Xposed with module where you have to reboot looses the baseband, IMEI etc. I have backup of the EFS and restored it multiple time with no joy.
Need some advice guys for Verizon my Note 3, I'm currently stock NC4 ready to. flash this bad boy ROM, after root access with TowelRoot, installation of BusyBox and Supersu no SafeTrap yet. Once I reboot in this state, I have the Baseband unknown under Settings-About Phone status all unknown info on IME etc etc. Off course I loose 4G signal all together. I may reboot again and it comes back. I know about EFS partition corruption and have multiple backup of My note 3 EFs partition. Even with restore it would still happen. I have exhausted all my knowledge learned throughout the years from you guys. But, I'm asking some help again. I am very familiar with all the terms about flashing/rooting so please feel free to throw some genius on how I can fix this thing.
Sent from my SM-N900V using Tapatalk
I have a Canadian Koodo Galaxy S4 (Model: SGH-i1337m) and I need help on how to update my phone to the official touchwiz android 5.0.
The phone was originally locked to Koodo, but I took it to a local phone store where they unlocked it for me. I now use the phone with another carrier (Rogers). I don't know the method they used to unlock it but after the process, my phone had become rooted and its device status was changed to "Custom". Also the Knox warranty counter became 0x1 after the unlock.
Right now the phone is on 4.4.2 and I'm unable to check for updates through the settings app as it gives me the message "Your device has been modified. Software updates are not available."
I don't really use root for anything on my phone except for xposed (which I can live without) and I need help updating this phone to 5.0. I don't mind losing my data but I really need to keep this phone unlocked. If anyone can help me out, it would be greatly appreciated.
rhwn said:
I have a Canadian Koodo Galaxy S4 (Model: SGH-i1337m) and I need help on how to update my phone to the official touchwiz android 5.0.
The phone was originally locked to Koodo, but I took it to a local phone store where they unlocked it for me. I now use the phone with another carrier (Rogers). I don't know the method they used to unlock it but after the process, my phone had become rooted and its device status was changed to "Custom". Also the Knox warranty counter became 0x1 after the unlock.
Right now the phone is on 4.4.2 and I'm unable to check for updates through the settings app as it gives me the message "Your device has been modified. Software updates are not available."
I don't really use root for anything on my phone except for xposed (which I can live without) and I need help updating this phone to 5.0. I don't mind losing my data but I really need to keep this phone unlocked. If anyone can help me out, it would be greatly appreciated.
Click to expand...
Click to collapse
Hi,
I have the same phone, Canadian variant, SGH-i337M. Koodo.
Do you have a custom recovery installed? If not, I would suggest using TWRP.
Download it here (I have TWRP too, and always used the dd install method several times without problem. Just MAKE SURE you have the exact command!):
https://twrp.me/devices/samsunggalaxys4canada.html
Once TWRP is installed, really important to make a Nandroid backup ("Backup" menu). Would suggest copying the backup to PC as well (Backup everything, including EFS). TWRP is not needed to flash Lollipop, but it's important to keep a backup.
Next, flashing Lollipop using Odin (Doing this, your SD card/internal memory will be untouched, but you will loose your apps, SMS and stuff. Back these up before if you want. Otherwise, everything would be also in the TWRP backup you've performed earlier). Go to Sammobile to grab the update:
Koodo: http://www.sammobile.com/firmwares/download/45758/I337MVLUGOC4_I337MOYAGOC4_KDO/
Rogers: http://www.sammobile.com/firmwares/download/45777/I337MVLUGOC4_I337MOYAGOC4_RWC/
It doesn't matter much which one you choose - Their content remains the same, but maybe the radio/modem would differ between carriers I think. I would suggest choosing the Rogers firmware (I know that Koodo include a "Koodo" app in their firmware, for instance).
Then follow the instruction closely (Make sure to use a genuine Samsung cable, and reliable USB connection):
Instructions
Extract (unzip) the firmware file
Download Odin v3.10.6
Extract Odin ZIP file
Open Odin v.3.10.6
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
I did the same thing myself to update to Lollipop. Worked great. But word of warning, you will loose your root access, and will have to root again (Same method worked for me, while I had problem disabling Knox on Lollipop somehow. Returned back to KitKat with my Nandroid backup).
Also, on that same Lollipop ROM, I encoutered WiFi issue, WiFi wouldn't turn ON at all (What the hell). Still haven't figured out the problem. That's why I would suggest keeping a backup of KitKat, for sure.
Also, don't worry about your unlocked phone, it will remained unlocked without problem.
Good luck
I recently installed TWRP and then the latest snapshot of CM12.1 for my phone described in title. The android version was upgraded from KitKat (4.4 I believe) to 5.1.1. Everything works fine with the install except I have no network whatsoever. Can't text, can't call, can't use data etc. I made a post on the CM subreddit but didnt get a lot of help (can't post link) . Here is what I have tried: changing APN settings (which I have heard should at least let me call and text if incorrect); flashing various modems such as BOE3, BNL9, and BOD3 (all of them get a FAIL! (auth) in ODIN); restoring my KitKat backup (makes the phone unusable); trying to flash the default L rom for the phone (Also fail to flash in ODIN and TWRP). So at the current time I am basically stuck on CM12.1 and all of its amazingness with no phone functions, I basically have a small tablet at the moment lol.
Here is some information from the about of my phone, if it is helpful at all.
Model: SM-G900F
CM Version: 12.1-20151204-NIGHTLY-ktle (Installed the nightly after the snapshot didn't work, same problem persists)
Android version: 5.1.1
Baseband version: S902LUDU3AOG2
Carrier: Straight Talk
If any more info is needed, just let me know. I appreciate any help, as I am pretty much at square one still. I have googled for days to try to fix this, and haven't come up with anything. It seems no one has had this specific problem before.
If I can't fix this issue, is there any way I can downgrade back to what I had to begin with?
y tried with another sim card !!!
ty *#06# to verify imei
popmpopm said:
y tried with another sim card !!!
ty *#06# to verify imei
Click to expand...
Click to collapse
I only have one other sim card on me, and its through verizon. It didn't work on the phone either. I would definitely just buy a new sim card if that would mean it would work. The whole IMEI thing worked, but I am not sure what to do with that information.
(Definitely a G900F? Check what it says in download mode)
Checking the IMEI was to make sure you haven't wiped/corrupted the EFS partition, which contains the Radios needed to make and receive called, along with the IMEI (Hopefully you researched enough to back that up before messing with the phone)
Try flashing another stock ROM with ODIN 3.10.7, go for a different Lollipop ROM from sammobile. com
Some stock ROMs fail to flash, some work, (Phone dependant it seems)
Then boot into recovery and factory reset > try to boot
*Detection* said:
(Definitely a G900F? Check what it says in download mode)
Checking the IMEI was to make sure you haven't wiped/corrupted the EFS partition, which contains the Radios needed to make and receive called, along with the IMEI (Hopefully you researched enough to back that up before messing with the phone)
Try flashing another stock ROM with ODIN 3.10.7, go for a different Lollipop ROM from sammobile. com
Some stock ROMs fail to flash, some work, (Phone dependant it seems)
Then boot into recovery and factory reset > try to boot
Click to expand...
Click to collapse
I have tried 2 separate L roms for the G900F. It says in download mode the phone is a SM-S902L and I read somewhere to get the true model of the phone you look at the FCC id under the battery. Well the FCC id says it is a G900V. at one point in trying to fix it, I tried a stock L rom for the G900V and TWRP told me that it was intended for a kltevzw device and that mine is a klte, so that is why I assume that it is in fact a G900F. I have been using ODIN 3.10.7 to flash everything as well. (Have't tried TWRP for the most recent tries since it takes longer to setup and I doubt it would work but it's worth a try I suppose.
I looked on Sam Mobile for the SM-S902L and there is only one firmware for it, which is 4.4.2, the same one it was installed with when I got it. From my understanding SM-902L is the straight talk branding of the G900V, and trying to flash that firmware didn't work either. Every time I try to flash something it terminates with a FAIL! (auth). What I also understand is that Straight Talk has not released an official version of L for the phone. So it seems my options now are to somehow get the modem to work right in CM12, try to somehow downgrade to 4.4.2, or wait for Straight Talk to release an update for my phone which is not really an option. I just got this phone and I really don't want to have to buy a whole new one just because of software problems. In my mind there HAS to be some way to fix this.
EDIT: my bad, I should have mentioned when I tried to flash the G900V rom it was also CM12, not a stock.
EDIT AGAIN: I seem to have fixed this problem. I have no idea how I did it, but I finally got it to restore to the stock 4.4.2 rom. I seriously have no clue how it worked but it did. Texting and data once again work, but i am now having a problem where I can't make or receive calls. Call immediately ends/goes straight to voicemail. I don't suppose you know anything about that, if you do that would be awesome. I'm gonna call ST in the morning and see if they can tell me anything from their end. But otherwise, I guess my problem is solved. Lol.
I know it sounds simple or may sound stupid but have you tried entering your APN? I have to do that with most of the custom Roms I flash or I won't have service. Also, make sure the correct modem is flashed and up to date.
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.