Hello all, I need some help. I bought a used S4 from a local person here. It was on an old update, Version 4.3.
I rooted it, did not take the OTA. installed custom recovery and flashed latest NK2 via philz touch, at first the WiFi wasnt working, so I installed the wifi fix/NON-HLOS.bin via odin. I also installed Modem.bin to upgrade to the latest baseband of NK2 also. This is when the trouble started, I probably messed up.
Currently both baseband and build are now NK2
I've downloaded NK2 TAR and flashed them back to t-mobile stock in an effort to fix, I used triangle away, cleared the counters, flashed stock NK2 in odin. Still no sound through the speakerphone. It was working before I did all this so I don't think its a hardware issue, Anyone have any ideas? Best I can tell is its probably the NON-HLOS.bin I flashed. Is there a correct one I can do, or anyway I can fix this? I've tried all I know with my limited knowledge of this phone. I had first flashed modem.bin i found here on xda, but i think my mistake was flashing the LTE/NON-HLOS.bin. probably is an older one for my bootloader im on? not really sure. I have also tried these with no success. http://forum.xda-developers.com/showpost.php?p=55373341&postcount=22
Any help is appreciated! Thanks so much!
You only need the modem bin if you are staying on an older bootloader, that was your mistake. Check what bootloader you have right now and you need to match your NON-HLOS to whatever bootloader you currently have
serio22 said:
You only need the modem bin if you are staying on an older bootloader, that was your mistake. Check what bootloader you have right now and you need to match your NON-HLOS to whatever bootloader you currently have
Click to expand...
Click to collapse
I will try this, I guess I'm confused exactly how to find out what bootloader im on, and where to find the matching NON-HLOS.bin file for it?
EDIT: used Phone info app from play store,
bootloader is MK2
baseband says NH7
PDA is NK2
CSC is NK2
Anyway to just update to the latest? Or whats reccomended version to stay on here?
Skater4599 said:
I will try this, I guess I'm confused exactly how to find out what bootloader im on, and where to find the matching NON-HLOS.bin file for it?
EDIT: used Phone info app from play store,
bootloader is MK2
baseband says NH7
PDA is NK2
CSC is NK2
Anyway to just update to the latest? Or whats reccomended version to stay on here?
Click to expand...
Click to collapse
Well you can re-flash NK2 firmware. Sometimes you have to flash a couple times for it to fully update everything
serio22 said:
Well you can re-flash NK2 firmware. Sometimes you have to flash a couple times for it to fully update everything
Click to expand...
Click to collapse
Ok I Odin'd NK2 several times, still no joy so I ended up using Fenny's guide to return to complete official stock on 4.4.2, then took tmobile's OTA updates and got back to 4.4.4 NK2 official, now bootloader says official samsung, status says official.
Bootloader: M919UVUFNK2
Baseband: M919UVUFNK2
PDA : M919UVUFNK2
CSC : M919TMBFNK2
EDIT: FIXED! Ended up a terrible coincidence, I took off and reseated the speaker on the back and it worked! Thank you so much for your help and pointing me in the right direction serio22 its much appreciated, I hit thanks for ya!
Still no sound, As far I read there are only 2 bootloaders for this device, so Im pretty sure I'm on the new one since it mentions knox on it.
I suppose its possible the hardware happen to fail at same time as all this? Seems like a crappy coincidence, but I dont know what else to try. Any other ideas? Everything is stock/official non rooted and up to date at this point.
Cool thanks posting what worked for you
Related
I used the mobile Odin method of flashing back and I also used triangle away before I did this if it's worth mentioning. So after struggling with getting back to stock all day I finally make it happen I put my SIM card back in and notice I am getting no cell phone reception. WiFi works but without WiFi I can't do anything data wise. I contacted t-mobile support and they found no issues with the SIM card
Anyone have ideas on what I can do to fix this?
Anyone? I'm kind of stuck here
griffsbrown said:
I used the mobile Odin method of flashing back and I also used triangle away before I did this if it's worth mentioning. So after struggling with getting back to stock all day I finally make it happen I put my SIM card back in and notice I am getting no cell phone reception. WiFi works but without WiFi I can't do anything data wise. I contacted t-mobile support and they found no issues with the SIM card
Anyone have ideas on what I can do to fix this?
Click to expand...
Click to collapse
What version radio are you showing? Does it match the stock ROM you flashed?
elpmet27 said:
What version radio are you showing? Does it match the stock ROM you flashed?
Click to expand...
Click to collapse
How can I find this info out? I am kind of nooby at this stuff so I dont know
What Firmware version did you just flash ? Do you see the same value under Settings > About > Baseband ?
What firmware did you have before using Mobile Odin ?
Perseus71 said:
What Firmware version did you just flash ? Do you see the same value under Settings > About > Baseband ?
What firmware did you have before using Mobile Odin ?
Click to expand...
Click to collapse
Ok so more info, I used this unroot method and followed it very close:
http://www.androidrootz.com/2012/10/how-to-unroot-samsung-galaxy-s3-no.html
I'm guessing this is what is causing the problem, I flashed the modem from UVDMD5. Only the modem I could not get anything else flash on odin so it was only the modem. So if I had to guess its a problem of getting the right modem back on the phone.
(On a side note, will I ever be able to get my phone back to 100% stock/able to get official updates,ect? Is it even possible?)
Edit: As far as the baseband goes it says "unknown".
I have no idea what that version is. I Suspect its the dreaded UVUEMJC. You will need to flash UVUEMJC Modem for T999 from this thread.
EDIT- Yes its indeed possible to go back to complete stock in order to receive Stock updates. After your IMEI is restored, you can use KIES to go back to complete stock. Please realize, you can also get latest update from Sammobile.com and flash it via Odin
Perseus71 said:
I have no idea what that version is. I Suspect its the dreaded UVUEMJC. You will need to flash UVUEMJC Modem for T999 from this thread.
EDIT- Yes its indeed possible to go back to complete stock in order to receive Stock updates. After your IMEI is restored, you can use KIES to go back to complete stock. Please realize, you can also get latest update from Sammobile.com and flash it via Odin
Click to expand...
Click to collapse
Dont know if you remember but I am the guy you helped in the other thread get unrooted. I was the one having trouble with it getting stuck at "system" when I was trying to get back to stock with the firmware from sammobile.com. Do you think it would be ok to try it again now that I'm on stock?
Don't recall the conversation. But there is a easier way to unroot by removing SuperSU after you get your IMEI back.
Perseus71 said:
Don't recall the conversation. But there is a easier way to unroot by removing SuperSU after you get your IMEI back.
Click to expand...
Click to collapse
This thread in question: http://forum.xda-developers.com/showthread.php?t=2691892
Also so how do I go about flashing a different modem without being rooted? Do I just do it through odin like I did before? Or will I need to reroot/get a custom recovery?
If you don't have custom Recovery, then use mobile Odin to flash the Modem.
Better yet, please flash UVUEMJC Firmware via Odin again.
Perseus71 said:
If you don't have custom Recovery, then use mobile Odin to flash the Modem.
Better yet, please flash UVUEMJC Firmware via Odin again.
Click to expand...
Click to collapse
Ok I will get to flashing it right now. Hopefully the lack of root wont be a problem.
EDIT: Uh I have a feeling it might have been a problem. I dont know actually. Here is what happened:
http://puu.sh/7JqCb.png
Perseus71 said:
If you don't have custom Recovery, then use mobile Odin to flash the Modem.
Better yet, please flash UVUEMJC Firmware via Odin again.
Click to expand...
Click to collapse
Ok so after my last post I figured it needed to be rooted so I triedx to root66 method and got this message:
http://puu.sh/7Juux.png
In other words stuck in the same boat as the old thread.
Please post the complete log data from the second image of Root66.
You don't flash a modem that way. It can brick.
Way back on 4.1.1 I used CF Auto Root and everything was grand on my AT&T phone.
Then the OTA upgrade nagging started... I caved, it finally annoyed me too much yesterday at work so I let the update do its thing.. and thats when my nightmare started.
it downloaded, it updated, it rebooted and hung at the AT&T logo.
I pulled the battery and powered back up.. it wasn't going to budge.
I had all the content I wanted on the SD so I tried to format cache and restore.. no dice.
I fired up Odin and after a LOT of screwing around it finally came back to life.. booted up on 4.3 but the baseband is hosed.
My warranty bit is set, my fused count is 3 > binary 0.
I think I understand the basic problem, I probably have a 4.2 modem with a 4.3 bootloader and I can't downgrade, I can't upgrade to 4.4 OTA without a working modem.
ANY help pointing me in the right direction from this mess I've created will be greatly appreciated.
so now I'm really confused, I read this thread: http://forum.xda-developers.com/showthread.php?t=1831898
Downloaded this file to the flash card and installed it with twrp: modem_CWM_I747UCUEMJB.zip
did not change a thing, baseband still unknown.
Actually, I'm thinking you may have actually already updated to 4.4.2. That would explain why the 4.3 modem doesn't help.
Install terminal emulator and enter this:
getprop ro.bootloader
This will tell you what firmware you are on and what modem you need.
You are correct ro.bootloader = I747UCUFNE4
ro.build.PDA = I747UCUEMJB
there isn't an NE4 option on this thread: http://forum.xda-developers.com/showthread.php?t=1831898
I download the modem from page 3 of this thread and I am back in business!
http://forum.xda-developers.com/showthread.php?t=2788357&page=3
Thank you very much for your assistance!
rcouch00 said:
You are correct ro.bootloader = I747UCUFNE4
ro.build.PDA = I747UCUEMJB
there isn't an NE4 option on this thread: http://forum.xda-developers.com/showthread.php?t=1831898
I download the modem from page 3 of this thread and I am back in business!
http://forum.xda-developers.com/showthread.php?t=2788357&page=3
Thank you very much for your assistance!
Click to expand...
Click to collapse
Thank you for replying, You just saved my phone also haha
krycus21 said:
Thank you for replying, You just saved my phone also haha
Click to expand...
Click to collapse
Fair warning I can't get Wifi to turn on even after disabling Knox. I have unlimited data so I'm not that concerned, but it may be a deal breaker for anyone else.
Wifi should return once you update the rom to 4.4.2...
Sent from my SAMSUNG-SGH-I747 running TMS3KK-2.0
Viper67857 said:
Wifi should return once you update the rom to 4.4.2...
Sent from my SAMSUNG-SGH-I747 running TMS3KK-2.0
Click to expand...
Click to collapse
If I use a 4.2 modem I get Wifi but no baseband
If I use a 4.4 modem I get a baseband but no wifi
You need both to get 4.4.2 ota
Not clear how I can get upgraded.
Flash it in custom recovery.. There's a modified ota around here somewhere...
Sent from my SAMSUNG-SGH-I747 running TMS3KK-2.0
rcouch00 said:
Fair warning I can't get Wifi to turn on even after disabling Knox. I have unlimited data so I'm not that concerned, but it may be a deal breaker for anyone else.
Click to expand...
Click to collapse
In my case I just installed the wrong modem, Wifi and LTE still works for me. I hope you get that part fixed
WiFi is firmware/kernel dependant now. So if you are running a 4.3 rom/kernel, on top of 4.4.2 firmware, WiFi will not work.
Same is true if running a 4.4.2 rom/kernel on top of 4.3 firmware.
In both cases you need to flash a custom kernel such as kt747.
Viper67857 said:
Flash it in custom recovery.. There's a modified ota around here somewhere...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2789917
Step 6, downloading the file before I go to sleep, I'll give this a shot tomorrow, thanks for the tip.
If anyone is in the same boat, I performed the update in my previous post and now have 4.4.2 and wifi connectivity is restored.
Thank you to everyone
Hey guys,
I got a I747 I want to give to my mother as a gift.
I downgraded 4.1.2 to 4.1.1 and ran the secret menu unlock to unlock the sim card, that worked perfectly.
Now I want to update this out of 4.1.1 to 4.4.2 but I cannot find a stock firmware to run on odin anywhere.
Do I need to go to 4.3 first? Is there a stock firmware for that?
SamMobile stops at 4.1.2... OTA obviously doesn't work.
How Can I get this done..
Iz3man said:
Hey guys,
I got a I747 I want to give to my mother as a gift.
I downgraded 4.1.2 to 4.1.1 and ran the secret menu unlock to unlock the sim card, that worked perfectly.
Now I want to update this out of 4.1.1 to 4.4.2 but I cannot find a stock firmware to run on odin anywhere.
SamMobile stops at 4.1.2... OTA obviously doesn't work.
How Can I get this done..
Click to expand...
Click to collapse
You can just flash stock 4.1.2 firmware from sammobile and then run OTA updates.
I also found this on sammobile: Canada (Bell Mobile) (Black Edition), Version: Android 4.4.2, PDA: I747MVLUFNE6
CSC: I747MOYCFNE6, MODEM: I747MVLUFNE6
audit13 said:
You can just flash stock 4.1.2 firmware from sammobile and then run OTA updates.
I also found this on sammobile: Canada (Bell Mobile) (Black Edition), Version: Android 4.4.2, PDA: I747MVLUFNE6
CSC: I747MOYCFNE6, MODEM: I747MVLUFNE6
Click to expand...
Click to collapse
Will it work though.
I have it already on my pc, I updated my wife's with it.
If I update to 4.1.2 will OTA come? Even with the I747(not the I747m) on the Bell network?
Iz3man said:
Will it work though.
I have it already on my pc, I updated my wife's with it.
If I update to 4.1.2 will OTA come? Even with the I747(not the I747m) on the Bell network?
Click to expand...
Click to collapse
I have a Motorola Atrix from Bell. I flashed it with stock ATT firmware and received OTA updates from ATT over wi-fi.
Since you have the i747, start with stock pre-rooted ATT 4.1.1. This will flash the stock recovery, radio, and bootloader. Run triangle away, flash a stock unrooted ATT stock 4.1.1 ROM, and take the OTA updates.
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=135374642
audit13 said:
I have a Motorola Atrix from Bell. I flashed it with stock ATT firmware and received OTA updates from ATT over wi-fi.
Since you have the i747, start with stock pre-rooted ATT 4.1.1. This will flash the stock recovery, radio, and bootloader. Run triangle away, flash a stock unrooted ATT stock 4.1.1 ROM, and take the OTA updates.
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=135374642
Click to expand...
Click to collapse
Ok, so I guess it wasn't clear, my bad.
I have 4.1.1 stock firmware on my att 1747. It has never been rooted.
I run the Ota and I got an error, now it tells me "Your software is up to date".
Can I flash a bell i747m 4.4.2 image onto this i747 or will it brick?
Iz3man said:
Ok, so I guess it wasn't clear, my bad.
I have 4.1.1 stock firmware on my att 1747. It has never been rooted.
I run the Ota and I got an error, now it tells me "Your software is up to date".
Can I flash a bell i747m 4.4.2 image onto this i747 or will it brick?
Click to expand...
Click to collapse
You can flash i747m firmware on your phone but DO NOT flash the radios or bootloader from an i747m to an i747 and vice versa. Bricking is a really possibility if you do that.
Do you have a custom recovery? If you do, you will need to install a stock recovery.
Try resetting the phone (wiping cache, data) in recovery or through the ROM itself.
audit13 said:
You can flash i747m firmware on your phone but DO NOT flash the radios or bootloader from an i747m to an i747 and vice versa. Bricking is a really possibility if you do that.
Do you have a custom recovery? If you do, you will need to install a stock recovery.
Try resetting the phone (wiping cache, data) in recovery or through the ROM itself.
Click to expand...
Click to collapse
Alright, I have the stock recovery. How do I not flash the radio and boatloads when using the firmware from sammobile?
You cant. You cannot flash another devices firmware. Odin wont let it happen and if it did youd end up hard bricked due to mixed firmware. For example your sbl1, modemst and param partitions (plus others) would be i747 and youd be flashing sbl2, sbl3, rpm, etc from an I747M.
The only thing you could use are the system partition and kernel, nothing else. There are two ways to accomplish this, one is to build a rom from the firmware and flash that. The other is to flash with mobile odin, but that requires root and youd still have to be very careful.
Another priblem I see you encountering is you cannot run 4.4.2 without 4.3 or newer firmware. It will not boot otherwise.
You need to go to the General section and follow one of enewman17's tutorials to get to either 4.3 or 4.4.2. Personally, I dont see any other way you will be able to accomplish it.
audit13 said:
You can flash i747m firmware on your phone but DO NOT flash the radios or bootloader from an i747m to an i747 and vice versa. Bricking is a really possibility if you do that.
Do you have a custom recovery? If you do, you will need to install a stock recovery.
Try resetting the phone (wiping cache, data) in recovery or through the ROM itself.
Click to expand...
Click to collapse
Alright, based on Doc holiday, and others they say It cannot be done and from my experience I beleive them.
Thank you,
It's very difficult to do this when others are giving bad advice.
So for the record, cannot flash i747m firmware to i747.
Thanks!
The annoying part here is I can do it with my m7, I just flashed the Dev edition onto my Bell m7 with no problems.
All devices are different in many ways. What is perfectly safe to do with one brand or model can brick another.
And I wouldnt call it "bad" advice... I've seen audit13 and others helping lots of folks with very good advice. We all make mistakes and we all have more we can learn about these devices. No one knows everything about this stuff and shouldnt let that prevent them from trying to help.
Those who are trying to help are doing so with the best of intentions and tell people what they think could be the best way to solve a given problem. In cases like this one, its easy to see how anyone would think its ok to flash different firmware between similar models based on being able to do so on other devices they are familiar with. (If I had gone into those forums I wouldve been telling people the opposite and ended up being wrong there.)
All I can say is chalk it up as a new lesson on a different device, and I hope you still appreciate that someone was trying to help.
@audit13 I hope none of this discourages you from helping. Ive seen plenty of threads where your advice was sound and appreciated, and I am glad you have been around to help so many people out!
Now, back on the problem at hand... if you want to be running the latest 4.4.2 kk, you will have the option to use the OS (/system and kernel) from either the I747 or I747M firmware. But first you must fully update to a minimum of the 4.3 MJB firmware for the I747. Once you have this running for your base firmware/bootloader, you can then run the Bell or AT&T (4.3 or 4.4.2) system. (I hope this is making sense!)
So first, update the full 4.3, MJB, firmware via Odin. (Theres a thread in General with the file, ill post the link in a min).
If you want to update to 4.4.2 firmware, you can then follow enewman17's tutorial to do so via OTA.
You can then either stay with that, or use Mobile Odin to flash ONLY the system and kernel from the Bell firmware.
Let me know if any of that needs better clarification! Also let us know what your ultimate goal is. From the options you have, where do you want to end up?
---------- Post added at 10:32 AM ---------- Previous post was at 10:26 AM ----------
Ok, here are some links.
Stock MJB firmware (flash in Odin)
http://forum.xda-developers.com/showthread.php?t=2722660
enewman17's thread for updating to 4.4.2 (high success rate)
http://forum.xda-developers.com/showthread.php?t=2789917
Official, unmodified 4.4.2 OTA
http://forum.xda-developers.com/showthread.php?t=2788012
After updating with the 4.3 firmware, you can first try using the official ota to update. Then, if that fails you can go to enewman17's thread and try his method.
DocHoliday77 said:
All devices are different in many ways. What is perfectly safe to do with one brand or model can brick another.
And I wouldnt call it "bad" advice... I've seen audit13 and others helping lots of folks with very good advice. We all make mistakes and we all have more we can learn about these devices. No one knows everything about this stuff and shouldnt let that prevent them from trying to help.
Those who are trying to help are doing so with the best of intentions and tell people what they think could be the best way to solve a given problem. In cases like this one, its easy to see how anyone would think its ok to flash different firmware between similar models based on being able to do so on other devices they are familiar with. (If I had gone into those forums I wouldve been telling people the opposite and ended up being wrong there.)
All I can say is chalk it up as a new lesson on a different device, and I hope you still appreciate that someone was trying to help.
@audit13 I hope none of this discourages you from helping. Ive seen plenty of threads where your advice was sound and appreciated, and I am glad you have been around to help so many people out! ]
:thumbup::beer::sly:
err on the side of kindness
Click to expand...
Click to collapse
I REALLY apologize in advance if this has been covered, but I can't find anything else on point, even in the suggested links above.
I have:
Samsung-SGH-I747
CyanogenMod version: 12.1-20151117-SNAPSHOT-YOG7DAO1K6-d2att
Android 5.1.1
Kernel 3.4.109-cyanogenmod-gdf08faa build04
Build number: cm_d2att-userdebug 5.1.1 LMY48Y 6cd1743679
I recently bought a used Galaxy S3 to use as an MP3 player that worked great until I upgraded from 4.1 to 4.3. This borked my device sound (no speakers, no headphones, video playback would skip and freeze with no audio) except for Bluetooth, which worked fine and allowed for videos to work as well.
I upgraded to Cyanogenmod 12.1 which didn't fix the sound, and actually broke the Bluetooth.
I figured I would follow the tutorials for low sound issues and through ES File Explorer I discovered that I had no sound folder at “/device/etc/sound”. There is a file there called audio_policy.conf and audio_effects.conf in the etc folder itself. Not sure if that is even relevant.
I read a post on another forum with an S4 user having the same issue, and he found a solution here to install the files "NON-HLOS.bin modem.bin sbl2.mbn tz.mbn aboot.mbn rpm.mbn sbl3.mbn" which fixed all of his sound issues. Perhaps there is an equivalent for the S3.
Unless I can find a solution my next course of action is going to be to try downgrading back to a stock 4.1, but I would ultimately like to get 12.1 running.
Any help is appreciated!
The phone was running stock 4.3 (including bootloader, recovery, and modem) when the sound issue arose?
Once on stock a 4.3 bootloader, you cannot downgrade to a fully stock 4.1 ROM.
Crap - I thought I had read that. I figured there was always a way.
Is there a resource anywhere for specific drivers, such as audio drivers? This has to be driver related, unless upgrading systems somehow broke my hardware. I find that hard to believe.
Would a driver issue in 4.3 persist with successive system roms?
Thanks!
audit13 said:
The phone was running stock 4.3 (including bootloader, recovery, and modem) when the sound issue arose?
Once on stock a 4.3 bootloader, you cannot downgrade to a fully stock 4.1 ROM.
Click to expand...
Click to collapse
whoops, delete
Which bootloader and modem are currently on the phone? This is important to know before flashing anything else as the bootloader and will determine what can and cannot be flashed.
theres a stock Kitkat Rom by @enewman17 just look up in the forum... dat Rom fixed sound problem for me!!
audit13 said:
Which bootloader and modem are currently on the phone? This is important to know before flashing anything else as the bootloader and will determine what can and cannot be flashed.
Click to expand...
Click to collapse
Hi Audit -
Not sure about the bootloader.
Bootloader version is: I747UCUFNE4
Modem version: modem_CWM_I747UCUEMJB
Modem version is reporting unknown, but I flashed modem_CWM_I747UCUEMJB yesterday. I am not using any sim card in this, so I read that perhaps that is why it reports unknown.
alphaja said:
theres a stock Kitkat Rom by @enewman17 just look up in the forum... dat Rom fixed sound problem for me!!
Click to expand...
Click to collapse
Hi alphaja,
Do you mean this thread?
It says I need to have a certain firmware to use this...my phone says "firmware forbidden" under samsung phone app. Not sure why it won't report my firmware version...
I always recommend matching the bootloader and modem as an incomaptible modem/bootloader combination can hard brick the phone.
Since the phone has an ne4 bootloader, I recommend flashing an ne4 modem to see if the audio problem is resolved. Do NOT flash anything that attempts to downgrade the phone's ne4 bootloader.
audit13 said:
I always recommend matching the bootloader and modem as an incomaptible modem/bootloader combination can hard brick the phone.
Since the phone has an ne4 bootloader, I recommend flashing an ne4 modem to see if the audio problem is resolved. Do NOT flash anything that attempts to downgrade the phone's ne4 bootloader.
Click to expand...
Click to collapse
Great idea - I am downloading it now.
It is really impossible to downgrade bootloaders and then to android 4.1? Or just difficult?
Where can I find "full" rom that would work with this bootloader and potentially have all the uncorrupted files that I need?
It is Impossible to downgrade from 4.3 to an older ROM. You may be able to flash an older 4.4.2 bootloader over a newer 4.4.2 bootloader but I'm not sure why anyone would want to do that and take a chance on bricking the phone.
Once you are on NE4 bootloader and modem with TWRP, you could flash ne4 via TWRP.
Look here: http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
audit13 said:
It is Impossible to downgrade from 4.3 to an older ROM. You may be able to flash an older 4.4.2 bootloader over a newer 4.4.2 bootloader but I'm not sure why anyone would want to do that and take a chance on bricking the phone.
Once you are on NE4 bootloader and modem with TWRP, you could flash ne4 via TWRP.
Look here: http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
Click to expand...
Click to collapse
Holy crap that worked!
I flashed the NE4 modem from there and boom audio restored, as well as bluetooth functionality.
Who knew??
Thanks man, this is awesome.
Glad it worked. Now you know why I always recommend having a matching bootloader and modem
Hi everyone,
I know this problem is well known and solved many times already, but I'm not being able to solve it by myself. This is why I'm posting this thread as a last resort to try and get some help, just in case i missed something..
My phone is currently with unknown baseband and IMEI on stock 4.4.2 flashed via kies recovery. If I try to flash any 4.4.4 port ROM the phone locks up seconds after boot, it will only work with stock rom. I already tried a few modems i found on another threads but no success.
Can anyone help?
Thanks.
madz78 said:
Hi everyone,
I know this problem is well known and solved many times already, but I'm not being able to solve it by myself. This is why I'm posting this thread as a last resort to try and get some help, just in case i missed something..
My phone is currently with unknown baseband and IMEI on stock 4.4.2 flashed via kies recovery. If I try to flash any 4.4.4 port ROM the phone locks up seconds after boot, it will only work with stock rom. I already tried a few modems i found on another threads but no success.
Can anyone help?
Thanks.
Click to expand...
Click to collapse
restore efs backup
there is a thread about imei and patched DN4.
Update everything, modem, bootloader, get these from newest firmware downloaded from sammobile and post results
yaro666 said:
restore efs backup
there is a thread about imei and patched DN4.
Update everything, modem, bootloader, get these from newest firmware downloaded from sammobile and post results
Click to expand...
Click to collapse
Hi,
I already got latest firmware from kies temp directory but I have no idea where to get modem and bootloader.. Can you point me in right direction?
Firmware file from kies is N7100XXUFNI5_N7100ORGFNJ1_N7100XXUFNG1_HOME.tar
Thanks.
madz78 said:
Hi,
I already got latest firmware from kies temp directory but I have no idea where to get modem and bootloader.. Can you point me in right direction?
Firmware file from kies is N7100XXUFNI5_N7100ORGFNJ1_N7100XXUFNG1_HOME.tar
Thanks.
Click to expand...
Click to collapse
from sammobile, download newest firmware for your region and unpack it from stock rom and then pack it with 7zip to tar file and flash it with Odin.
you need sboot and modem
Double post
yaro666 said:
from sammobile, download newest firmware for your region and unpack it from stock rom and then pack it with 7zip to tar file and flash it with Odin.
you need sboot and modem
Click to expand...
Click to collapse
Isn't that a bit pointless? Maybe I'm missing the point, but if I already have flashed latest firmwares from both sammobile and kies, it kind of makes the point that modem and bootloader files from sammobile don't solve the problem, right?
Thanks.
Sent from my SM-G925F using Tapatalk
madz78 said:
Isn't that a bit pointless? Maybe I'm missing the point, but if I already have flashed latest firmwares from both sammobile and kies, it kind of makes the point that modem and bootloader files from sammobile don't solve the problem, right?
Thanks.
Click to expand...
Click to collapse
Well truly doesnt seem pointless
I got my baseband resolved (Previously showed 'Unknown') by flashing pure stock rom (got from SamMobile) THROUGH ODIN so might be there is a point.
Try stock rom flashing from odin as according to me stock rom has everything in it radio(Baseband),boot(efs), system, etc etc
The unknown baseband and imei can be due to a modem and bootloader mismatch.
To confirm the bootloader and modem on the phone, install the Samsung Phone Info app from the play store to confirm the version.