s4 Mini sm-s890l - Upgrading, Modifying and Unlocking

greetings, i have been having an issue and literally spent all day looking for answers yet nothing is working. I have a SM-S890L S4 Mini from Straight Talk. Anyway, I backed up my stock rom and then flashed cm10.2. My computer no longer recognizes it via usb and the menu and back buttons are no longer active. Restored image before flash and same issues. And I accidentally deleted the backup when I factory restored the phone. I can still boot into recovery and Odin, but I am unsure what to do. My research led me to believe that the S890L and I91505 were the same. Anyway this stuff is fun to tinker with and the best learning method. but my phone being down is not. any information is appreciated.
edit: ok so this is where i am at. I discovered that any unbranded rom will work as far as returning to stock. Where can I find the csc and modem information for straight talk? I chose the 9195 because it is an LTE just like mine, root process went fine and was able to flash cm 10.2, however i get NO audio and my soft keys are not there, they do not work

I know this post is pretty far outdated, but this may help others experiencing similar issues.
S-890L CM Port

Related

[Q] No Network or IMEI number, :-S

Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?
shirazi15 said:
Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?
Click to expand...
Click to collapse
I had this exact issue last week when flashing Kitkat AOSP ROM. Even restoring back to 4.3.1 no network connection was available, except for WiFi. Restoring your EFS will not even work. You just have to re-root your phone.
Not to worry, your phone is OK, perfectly OK. But just quite a bit of work needs to be done. Here: http://forum.xda-developers.com/showthread.php?t=2032849
1. Download original stock firmware for your country and telco
2. Download mode that firmware back to your phone using Odin
3. Download mode to install recovery, this will re-root your phone above steps will un-root your phone
4. Re-flash ROM of your choice, not Kitkat for now
After all i've gone through, and as much as i want to try Kitkat, i think this issue is recovery-related. Both TWRP and CWM needs updating for Android 4.4. I will wait until then.
All the best!
Gandicela said:
I had this exact issue last week when flashing Kitkat AOSP ROM. Even restoring back to 4.3.1 no network connection was available, except for WiFi. Restoring your EFS will not even work. You just have to re-root your phone.
Not to worry, your phone is OK, perfectly OK. But just quite a bit of work needs to be done. Here: http://forum.xda-developers.com/showthread.php?t=2032849
1. Download original stock firmware for your country and telco
2. Download mode that firmware back to your phone using Odin
3. Download mode to install recovery, this will re-root your phone above steps will un-root your phone
4. Re-flash ROM of your choice, not Kitkat for now
After all i've gone through, and as much as i want to try Kitkat, i think this issue is recovery-related. Both TWRP and CWM needs updating for Android 4.4. I will wait until then.
All the best!
Click to expand...
Click to collapse
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.
shirazi15 said:
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.
Click to expand...
Click to collapse
Mate, firstly this is the hard way of recovering from "Unknown Baseband" issue. Finally the simple solution was only to download and install an app called SELinux Mode Changer from PlayStore. Then using that app, change SELinux from Enforcing to Permissive resolved everything related to IMEI, EFS, and Unknown Baseband. So hard way I did; i didn't know any better then.
By the way the link is correct. Start from the procedure from the line that says "Installation Instruction [Mobile odin is now have support for NOTE2]"
You must be in download mode (Vol Down, Home, & Power button all pressed together) to flash the Stock ROM using Odin. But where is your status now? If in recovery, can you re-install a ROM? If u r able to reboot back up to OMNI, just install the SELinux app and u will be good to go.
Cheers!
shirazi15 said:
Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?
Click to expand...
Click to collapse
can you try what i did? http://forum.xda-developers.com/showthread.php?t=2567862&nocache=1
good luck.
"Just sharing my experience in solving this issue. Hopefully it will help solve those who have similar issues.
I flashed a file which messed up my EFS partition. I had a backup and tried to use the available programs to restore my EFS using my backup. None worked. I even brought it to the samsung store, but they said they would change the motherboard and reprogram, and replacement and service would cost more than half the cost of a new N7105. I purchased the phone in another country. The people who had stores to repair phones gave up on my phone. They also offered to replace the motherboard for US$175.00.
My phone was originally under a DMB2 rom (from Singapore I think). I flashed a DMC3 rom, and used this for five months, until i encountered the problem.
I initially gave up and got a note 3. But i could not believe the phone was junk and people in XDA (as I observed) do not seem to give up.
After two weeks, i found the solution below, which brought my phone to working condition.
1. I flashed the stock rom N7105ZHDMI2_N7105ZZHDMI2_TGY from sammobile.
2. I flashed a pit file using Odin. The pit file is found here:
http://forum.xda-developers.com/show....php?t=2137008
This restored the baseband. But IMEI was no longer NULL. However, it was still 0.
3. I downloaded and used the EFS Pro from this link:
http://forum.xda-developers.com/show....php?t=1308546
Before using EFS Pro, make sure you dial *#7284# and change the setting of Qualcomm USB Settings to
"RMNET + DM + MODEM"
I will not hurt your phone if you do, but EFS Pro will just not work. If you don't do this, the EFS Pro will display "Phone not responding" or something similar.
NOTE: I couldn't find the option with RMNET, but i used the option that also had an "RM*** + DM + MODEM".
After the phone is read, change back the IMEI to what it was originally.
Dial *#7284# again to change back to "MTP+ADB".
It's all working now.
Hope this is able to help someone. Now i have two working versions of Note.
Thanks to the authors of the program i used, and the people who uploaded the files used.
Cheers!
shirazi15 said:
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.
Click to expand...
Click to collapse
karlonicolas said:
can you try what i did? http://forum.xda-developers.com/showthread.php?t=2567862&nocache=1
good luck.
"Just sharing my experience in solving this issue. Hopefully it will help solve those who have similar issues.
I flashed a file which messed up my EFS partition. I had a backup and tried to use the available programs to restore my EFS using my backup. None worked. I even brought it to the samsung store, but they said they would change the motherboard and reprogram, and replacement and service would cost more than half the cost of a new N7105. I purchased the phone in another country. The people who had stores to repair phones gave up on my phone. They also offered to replace the motherboard for US$175.00.
My phone was originally under a DMB2 rom (from Singapore I think). I flashed a DMC3 rom, and used this for five months, until i encountered the problem.
I initially gave up and got a note 3. But i could not believe the phone was junk and people in XDA (as I observed) do not seem to give up.
After two weeks, i found the solution below, which brought my phone to working condition.
1. I flashed the stock rom N7105ZHDMI2_N7105ZZHDMI2_TGY from sammobile.
2. I flashed a pit file using Odin. The pit file is found here:
http://forum.xda-developers.com/show....php?t=2137008
This restored the baseband. But IMEI was no longer NULL. However, it was still 0.
3. I downloaded and used the EFS Pro from this link:
http://forum.xda-developers.com/show....php?t=1308546
Before using EFS Pro, make sure you dial *#7284# and change the setting of Qualcomm USB Settings to
"RMNET + DM + MODEM"
I will not hurt your phone if you do, but EFS Pro will just not work. If you don't do this, the EFS Pro will display "Phone not responding" or something similar.
NOTE: I couldn't find the option with RMNET, but i used the option that also had an "RM*** + DM + MODEM".
After the phone is read, change back the IMEI to what it was originally.
Dial *#7284# again to change back to "MTP+ADB".
It's all working now.
Hope this is able to help someone. Now i have two working versions of Note.
Thanks to the authors of the program i used, and the people who uploaded the files used.
Cheers!
Click to expand...
Click to collapse
Nice, thanks!
For all others that might face "unknown baseband" with 4.3 to 4.4 flashing of ROMS, SELinux Mode Changer app from Playstore will fix that problem. Install the app and set SELinux from Enforcing to Permissive.
i hope your problem is fixed.
i'm not too familiar with CM roms, as i have been using stock since gingerbread. but you have to first do a full wipe before flashing from CM to stock. did you do that? perhaps you can go to recovery, do a full wipe, include Dalvik and Cache. Then go to bootloader and flash your rom.
by the way, my chipset is qualcomm yours may be exynos. if so, then i'm not confident about this solution because i have tried this several times, but only on note 2 LTE.
good luck!

[Q] Made a n00b mistake on my 8.4 - How do I get back to Stock?

Hi all,
I made a dumb move and installed the CM11 port for my T320 without backing up my Samsung stock firmware. (I'd post over in the appropriate thread in the development section, but I haven't posted here frequently enough to be allowed over there). I want to go back to the Samsung UI for now because I am having some troubles with CM11 ... my tablet thinks it's a phone, so I'm not getting the tablet features and app versions. Plus something is off with my screen so that some apps (Flipboard, at least) runs everything off the right side and bottom of the screen. Anyway, does anyone have an idea of how to get me back to my Samsung UI? I can't get Kies to talk to my tablet (another thing that cropped up with this CM build) so I can't get that to reflash it for me.
I have downloaded an Odin-flashable Samsung stock firmware from Australia (I'm in the US) so I'm guessing that will work, but I'd rather find an easier option before I give my tablet a globetrotting split identity disorder or something.
Please understand, I've rooted, reflashed, and even unbricked devices before, so I'm not new to this, just made a dumb mistake.
I believe that is the only way to go. The good news is you can install twrp recovery now so it shouldnt be an issue again. Bad news is there isnt a flashable stock firmware that I know of yet. Im kinda hoping for cleanrom as he did a hell of a job on the note 3 and knows the system better than most.
fantasticrat said:
Hi all,
I made a dumb move and installed the CM11 port for my T320 without backing up my Samsung stock firmware. (I'd post over in the appropriate thread in the development section, but I haven't posted here frequently enough to be allowed over there). I want to go back to the Samsung UI for now because I am having some troubles with CM11 ... my tablet thinks it's a phone, so I'm not getting the tablet features and app versions. Plus something is off with my screen so that some apps (Flipboard, at least) runs everything off the right side and bottom of the screen. Anyway, does anyone have an idea of how to get me back to my Samsung UI? I can't get Kies to talk to my tablet (another thing that cropped up with this CM build) so I can't get that to reflash it for me.
I have downloaded an Odin-flashable Samsung stock firmware from Australia (I'm in the US) so I'm guessing that will work, but I'd rather find an easier option before I give my tablet a globetrotting split identity disorder or something.
Please understand, I've rooted, reflashed, and even unbricked devices before, so I'm not new to this, just made a dumb mistake.
Click to expand...
Click to collapse
I've used Samsung Kies from my PC several time to go back to stock.
When using Kies you may have to switch your connection from MTP to the other option and of course check debug.
I went back and forth from CM11 several time plus I did what you did also except I used the New Zealand version
Here's what I did to restore stock from Kies.
Plug in the tablet, open Kies, and click Tools then Firmware upgrade and initialization. Type in SM-T320, hit okay, then add your serial number.
Basically just follow the steps it asks you and make sure your tablet is in download mode. It will download the stock firmware image and flash it to the device.
My instructions might now be 100% accurate, but that's basically the process I took to restore it to factory.

Frustrating In-Call Audio/Modem Issue

To anyone more of an expert than myself on these matters (which I presume to be a large portion of users here), I'd greatly appreciate any help that can be provided. I'd also like for this thread to be a central collection of baseband/modem functions, behaviors, troubleshooting, etc...
I've had a T-Mobile S4 (SGH-M919) for a while now and have mostly used CyanogenMod derived ROM's and as of lately, more Google Play Edition/Nexus type ROM's (which generally appear to be written for the international i9505 and hence show the model number of my phone to be such; this may or may not be relevant). All of the sudden, the other day during a phone call I received, there was no audio on either end of the call. I couldn't hear the caller nor could the caller hear me. This also happens if I initiate the call. I know for a fact that the media speakers (speakers used during speakerphone) as well as the earpiece speaker are perfectly functional so it's not a case of hardware failure where it works on Bluetooth or speakerphone only. As soon as a call initiates, you hear no ringing or audio once the caller answers other than the tone when the call ends/disconnects. First thing I tried was switching from ART back to Dalvik just for the sake of troubleshooting. Second, I tried clearing the cache (and Dalvik, just for the hell of it). Still no success. So next I try a completely different ROM. I was presently on a GPE ROM with the Samsung kernel so I switched to plain CyanogenMod with a custom kernel. I even went back to a stock ROM! No success either way!!
It was at this point I decided that it had to be a hardware/firmware issue since the issue remained when changing ROM's so I naturally assumed baseband/modem. I don't understand why this issue just magically occurred one day when I hadn't changed anything, but I thought that if I reflashed a clean modem image or and updated one, then maybe it would fix it... I was on MDL so I reflashed the MDL modem. No success. Then (and here's where I f****d up), I tried flashing what I THOUGHT was a stock NB4 firmware file in ODIN. Turns out that despite being labeled as stock, it had a custom kernel built-in and tripped my KNOX counter (FFFFFUUUUUUCCCCCKKKK!!!) Well, since I really only intend to use AOSP/CM based ROM's, it's not such a huge deal for me but still, it sucks.
Here's where I had a break: Yesterday, I tried flashing the MDL modem again, then that didn't work so I tried flashing the MK2 modem. I booted up, made a call, and it worked! First time! Well, that was short lived success because I tried another call immediately after to verify and it started all over again. Now, even reflashing MK2 won't get it to work even once like it did this one time.
Does ANYone who understands baseband and modem firmware much better than I do have any insight or instruction on what I can do? Because of this one issue, I have an otherwise perfectly good S4 that I can't use just lying around. I've had a Nexus 5 for almost a year and love it but I just destroyed the screen after a drop the other day and wanted to switch to the S4 temporarily until the Nexus 6 comes out. ANY IDEAS????
Loss of call audio occurs when your rom and firmware versions dont match. Since you've tripped your knox counter, you have some more freedom now. I think you should (after someone confirms) use the samsung pc software to do a full restore of your phone. It will blow away everything you have and install the latest firmware and matching rom as if you were stock and accepted all otas. Then you can root, flash recovery, flash rom, restore backed up apps. You'll have the cleanest possible setup. Just wait for someone to confirm because i haven't been following closely in the past few months. Alternatively you can find the latest firmware and do it with odin but in your position theres no advantage to doing it piece-meal like that (unless i've missed something in the past few months) because you've already tripped knox
faiyo said:
Loss of call audio occurs when your rom and firmware versions dont match. Since you've tripped your knox counter, you have some more freedom now. I think you should (after someone confirms) use the samsung pc software to do a full restore of your phone. It will blow away everything you have and install the latest firmware and matching rom as if you were stock and accepted all otas. Then you can root, flash recovery, flash rom, restore backed up apps. You'll have the cleanest possible setup. Just wait for someone to confirm because i haven't been following closely in the past few months. Alternatively you can find the latest firmware and do it with odin but in your position theres no advantage to doing it piece-meal like that (unless i've missed something in the past few months) because you've already tripped knox
Click to expand...
Click to collapse
Thanks for the response! This was actually the approach I initially wanted to take when reflashing just the modem didn't work; that is, using Samsung Kies to do a complete Samsung official firmware download and restore. Unfortunately, every time ibtry and do the "emergency recovery" as they call it, once I type in my serial number and model like the app requires, it always tells me that the device is not supported! It's like the device's firmware has been programmed as another that isn't recognized by Samsung. At first I thought it was because I was on a custom ROM and it didn't recognize the software. I remember a while back I needed to do an official restore and I had to get the phone boot loader to read status "Samsung Official" and not just official. I actually put stock everything back on manually and got those status fields to read Samsung Official for the binary and kernel but it still won't restore with Samsung's software. It's my estimation that Samsung has now integrated the Knox counter into their software support. I'm assuming that with that sensor tripped, I can never be "official" and therefore supported again. That's why I've been doing everything Odin. With all of this in mind, do you have any other recommendation? I'll look a little further into the problems I've had with Kies and maybe why I can't restore in the meantime but otherwise, why do you think flashing MK2 modem worked for just ONE call and then stopped again? And why do you think that the issue just suddenly happened in the first place without a software change?
thair7391 said:
Thanks for the response! This was actually the approach I initially wanted to take when reflashing just the modem didn't work; that is, using Samsung Kies to do a complete Samsung official firmware download and restore. Unfortunately, every time ibtry and do the "emergency recovery" as they call it, once I type in my serial number and model like the app requires, it always tells me that the device is not supported! It's like the device's firmware has been programmed as another that isn't recognized by Samsung. At first I thought it was because I was on a custom ROM and it didn't recognize the software. I remember a while back I needed to do an official restore and I had to get the phone boot loader to read status "Samsung Official" and not just official. I actually put stock everything back on manually and got those status fields to read Samsung Official for the binary and kernel but it still won't restore with Samsung's software. It's my estimation that Samsung has now integrated the Knox counter into their software support. I'm assuming that with that sensor tripped, I can never be "official" and therefore supported again. That's why I've been doing everything Odin. With all of this in mind, do you have any other recommendation? I'll look a little further into the problems I've had with Kies and maybe why I can't restore in the meantime but otherwise, why do you think flashing MK2 modem worked for just ONE call and then stopped again? And why do you think that the issue just suddenly happened in the first place without a software change?
Click to expand...
Click to collapse
A few notes: i have a similar problem in the last few months. After about 12 hours of uptime i cannot hear the other caller. I thought it's because im using ****ty roms from these forums so i was about to go to the international forums and flash theirs. I only use touchwiz roms so far. And it manifests about a week after flashing the rom. And i have to reboot twice a day to keep it functioning So yeah.. i get it too even tho i had a matching baseband
I think the reason you tripped knox wasnt because of the kernel. It's because a stock firmware package will upgrade your bootloader, while you should have actually been pursuing a modem-only package to flash with odin (which preserves the MDL bootloader and prevents tripping knox).
Anyways, im not sure what you have done with the "Samsung offical" status or modifying the identifiers of the phone but i was pretty sure kies would restore it. If not, then you should be trying to flash stock firmware (full) for NH7 firmware which was released recently. Not just modem only, which is what some of the packages here contain (meant for people with MDL bootloaders who dont want to trip knox). Try to pursue the full firmware odin flash. Im pretty sure that would do it for you. It should be the full-on samsung stock.
About kies: i haven't used it but i've experienced weird things happen with adb and specific usb cables and usb ports on the computer, even with nexus devices. I hate to suggest this but try a different computer and different usb cable. Its an actual solution thats worked before. It messed me up before and a number of other people. Make sure its up to date too i kinda recall old versions had a compatibility issue
faiyo said:
A few notes: i have a similar problem in the last few months. After about 12 hours of uptime i cannot hear the other caller. I thought it's because im using ****ty roms from these forums so i was about to go to the international forums and flash theirs. I only use touchwiz roms so far. And it manifests about a week after flashing the rom. And i have to reboot twice a day to keep it functioning So yeah.. i get it too even tho i had a matching baseband
I think the reason you tripped knox wasnt because of the kernel. It's because a stock firmware package will upgrade your bootloader, while you should have actually been pursuing a modem-only package to flash with odin (which preserves the MDL bootloader and prevents tripping knox).
Anyways, im not sure what you have done with the "Samsung offical" status or modifying the identifiers of the phone but i was pretty sure kies would restore it. If not, then you should be trying to flash stock firmware (full) for NH7 firmware which was released recently. Not just modem only, which is what some of the packages here contain (meant for people with MDL bootloaders who dont want to trip knox). Try to pursue the full firmware odin flash. Im pretty sure that would do it for you. It should be the full-on samsung stock.
About kies: i haven't used it but i've experienced weird things happen with adb and specific usb cables and usb ports on the computer, even with nexus devices. I hate to suggest this but try a different computer and different usb cable. Its an actual solution thats worked before. It messed me up before and a number of other people. Make sure its up to date too i kinda recall old versions had a compatibility issue
Click to expand...
Click to collapse
So quick update/reply, I just stumbled upon a stock, lightly modified MK2 ROM flashable through recovery that I had buried on my microSD and decided to give it a go (since the MK2 modem was the only one that every gave me any success even though it was just one time, and even though the ROM I was using was custom so couldn't have really matched ANY Samsung baseband). Even though I really already knew and understood everything you told me, you were brilliant to remind me about the need for the modem to match the OS when it initializes. After booting up the Stock MK2, calls are now working, and consistently!!! Now I'm making a backup (just in case, even though I really don't want to use stock) and then I'm going to go for a custom ROM again, probably CM based. Thanks again for your help!
I know exactly how I tripped the Knox counter. I downloaded a firmware file that was LABELED as a stock NB4 ROM and that wasn't correct. It was a stock NB4 ROM with a MODIFIED CUSTOM KERNEL! That would have been a useful detail beforehand...
I'm also familiar with using adb and it's selectivity with USB cables. They need to be "fastboot" cables which usually only is the case with manufacturer included cables. Using Kies to restore firmware to a phone though should have nothing to do with fastboot or adb. First off, you don't need the adb Runtime or SDK to use Kies nor does Samsung include it in the installation. Second, when you're using Download mode, that's Samsung's proprietary software using their own proprietary API's and commands to communicate and interface directly with their hardware so I think the issues I've had with Kies is something else. I appreciate the suggestion though.
As far as the matching modem and software goes, I'm a bit confused... Why is it that you can use custom ROM's non-related to Samsung after updating your baseband if the custom ROM isn't matching that firmware? Perfect example, just now... I tried the stock MK2 and it worked. Now I just finished loading clean CyanogenMOd, and it worked! BUT - only one and a half times... It went through once, I tried again, and then it stopped mid ringing of the call, now doesn't work. AHHHH!!! How am I supposed to do this? And why did I never have trouble in the past? Once I get a stock ROM and matching, working modem installed, what am I supposed to do from there if I want to switch to a CM based ROM?
thair7391 said:
So quick update/reply, I just stumbled upon a stock, lightly modified MK2 ROM flashable through recovery that I had buried on my microSD and decided to give it a go (since the MK2 modem was the only one that every gave me any success even though it was just one time, and even though the ROM I was using was custom so couldn't have really matched ANY Samsung baseband). Even though I really already knew and understood everything you told me, you were brilliant to remind me about the need for the modem to match the OS when it initializes. After booting up the Stock MK2, calls are now working, and consistently!!! Now I'm making a backup (just in case, even though I really don't want to use stock) and then I'm going to go for a custom ROM again, probably CM based. Thanks again for your help!
I know exactly how I tripped the Knox counter. I downloaded a firmware file that was LABELED as a stock NB4 ROM and that wasn't correct. It was a stock NB4 ROM with a MODIFIED CUSTOM KERNEL! That would have been a useful detail beforehand...
I'm also familiar with using adb and it's selectivity with USB cables. They need to be "fastboot" cables which usually only is the case with manufacturer included cables. Using Kies to restore firmware to a phone though should have nothing to do with fastboot or adb. First off, you don't need the adb Runtime or SDK to use Kies nor does Samsung include it in the installation. Second, when you're using Download mode, that's Samsung's proprietary software using their own proprietary API's and commands to communicate and interface directly with their hardware so I think the issues I've had with Kies is something else. I appreciate the suggestion though.
As far as the matching modem and software goes, I'm a bit confused... Why is it that you can use custom ROM's non-related to Samsung after updating your baseband if the custom ROM isn't matching that firmware? Perfect example, just now... I tried the stock MK2 and it worked. Now I just finished loading clean CyanogenMOd, and it worked! BUT - only one and a half times... It went through once, I tried again, and then it stopped mid ringing of the call, now doesn't work. AHHHH!!! How am I supposed to do this? And why did I never have trouble in the past? Once I get a stock ROM and matching, working modem installed, what am I supposed to do from there if I want to switch to a CM based ROM?
Click to expand...
Click to collapse
I really have no idea about aosp roms for this device because i only used touchwiz to keep samsung features.. so i have no knowledge about firmware compatibility. I would think the creator of the rom should specify any firmware requirements.
On the thought of hardware failure, and i know you said the speakers work, but did you test the sim card slot? Perhaps it needs to be cleaned? Maybe the sim card is partially failing so try a different card? Maybe you cut it and it's loose (you wont believe the crooked sim cards i've seen). I think it's worth pursuing since you said it worked once and not again.. maybe you had just taken the cover off while flashing stuff and touched/pressed it but it's losing contact again after flexing during use. I dunno dude, the kind of call audio issues i've had were always resolved with a reboot & making sure the modem matches the touchwiz build.
Please make sure you are running a full stock firmware package & keep the touchwiz rom consistent with it. Some firmware packages are partial components
So now I've just updated to a FULL STOCK NH7 firmware package. My build number and baseband are matching. NO CALL AUDIO!!
For starters, up until a few days ago, I ran all types of ROM with an MK5 boot loader and 3 different modems and never had a call issue. After that said, I read a few months ago about a guy had your same issue. He ended up getting a new sim card and he got is audio back. He also had reception issues before getting the no audio issue.
thair7391 said:
So now I've just updated to a FULL STOCK NH7 firmware package. My build number and baseband are matching. NO CALL AUDIO!!
Click to expand...
Click to collapse
Try flashing the firmware again, some have to flash it twice for the bootloader to update, which may the trouble. If that doesn't work try a new sim like it was suggested before me
I know it's been a while but I basically gave up and just recently came back to it. I've since bought a Nexus 6 so it's not a priority issue anymore however I would still like to fix this otherwise perfectly fine Galaxy S4 that I have lying around! I seemed to believe that there was a special combination of custom ROM and specifically the MK2 modem that would sometimes cause the audio to intermittently work but it appears I was wrong. I flashed the full stock NH7 firmware/baseband etc back to my phone twice as suggested and NY audio worked! For a few calls that is... Then it stopped working again. Sometimes I could clear cache and reboot and it would work! Once or twice anyways before crapping out again... The bottom line is that there isn't a pattern aside from a cleared cache that makes the audio work again before it stops soon after which unfortunately leads me to believe it's a deep rooted hardware issue in the baseband itself. Anyone else have ideas?
Other than trying a new sim, I can't really think of anything else except to make sure the bootloader really did update. Download Samsung phone info from play store and check bootloader info to make sure it was updated to NH7
Unfortunately it is completely updated. I tried a new SIM and everything works still except audio in phone calls, including ringing. I guess it's hardware... Guess now I just have an internet browsing MP3 player with web browsing capabilities.

[Q] Help, phone will not activate after rom update.

Hey all, I've had my Samsung Galaxy S3 (SPH-L710 for Sprint) for some time now. Since the time I purchased (which was around the time it was released) I've had SlimRom installed. Never had any problems, updates always went through flawlessly, and I love the rom. Just the other day, I decided to update slimrom from to the newest stable version which is 7. Flash went through successfully, everything seemed fine and dandy as usual. But I had no service for some reason... Tried several methods of repairing the problem, to no avail.
In my about phone section, everything is all messed up; my phone number says "000-000-0016" my MIN "0000000016" PRL Version "1" IMEI "Unknown" and unfortunately I do not have a back up of anything, because I completely wiped my phone and did a full restore/unroot using rwilco's method here: http://forum.xda-developers.com/showthread.php?t=2755793.
So now I am unrooted, I still can not get my phone to activate. Talked to a sprint rep at this point to see if they could help. After telling me to do a few different commands, such as ##3283# and changing the info with my MSL and what not, nothing worked. He was stumped. Now I am stumped, and I've got an unrooted Wi-Fi only S3 at the moment.
I've gone through so many threads and different articles and just can not find an answer. I really didn't want to start a thread asking for help, as I've never had to before. But now I feel like a complete noob and need it! Please anybody!
murdercitydan said:
Hey all, I've had my Samsung Galaxy S3 (SPH-L710 for Sprint) for some time now. Since the time I purchased (which was around the time it was released) I've had SlimRom installed. Never had any problems, updates always went through flawlessly, and I love the rom. Just the other day, I decided to update slimrom from to the newest stable version which is 7. Flash went through successfully, everything seemed fine and dandy as usual. But I had no service for some reason... Tried several methods of repairing the problem, to no avail.
In my about phone section, everything is all messed up; my phone number says "000-000-0016" my MIN "0000000016" PRL Version "1" IMEI "Unknown" and unfortunately I do not have a back up of anything, because I completely wiped my phone and did a full restore/unroot using rwilco's method here: http://forum.xda-developers.com/showthread.php?t=2755793.
So now I am unrooted, I still can not get my phone to activate. Talked to a sprint rep at this point to see if they could help. After telling me to do a few different commands, such as ##3283# and changing the info with my MSL and what not, nothing worked. He was stumped. Now I am stumped, and I've got an unrooted Wi-Fi only S3 at the moment.
I've gone through so many threads and different articles and just can not find an answer. I really didn't want to start a thread asking for help, as I've never had to before. But now I feel like a complete noob and need it! Please anybody!
Click to expand...
Click to collapse
To my knowledge the only way to repair this problem would be to buy another device........but before you do that did you make a backup of the rom that was working perfectly and did you try restoring it before you went with Odin? What was your bootloader/modem before you flashed the initial slimrom?
6th_Hokage said:
To my knowledge the only way to repair this problem would be to buy another device........but before you do that did you make a backup of the rom that was working perfectly and did you try restoring it before you went with Odin? What was your bootloader/modem before you flashed the initial slimrom?
Click to expand...
Click to collapse
I did make a back up, unfortunately however, when I did the full restore I lost everything that was on my phone, including the back up. And I did not try restoring is before doing Odin. About the bootloader/modem, no idea.
Welp, seems like its done. I'm eligible for an upgrade anywho. Think I'm going in today and picking up a new LG G3, not sure yet though. Can't decide what phone I want...
Have you tried dialing ##72786#? It is a forced reactivation.

SGH-T999 Custom ROM with working 4G

Greetings,
I really don't want this to be a repeat post, so I have spent many days now searching for this answer, not just here on XDA if I was honest, I have links to prove it
The aim is to give a little new life to my old phone, and get off the 4.1 build it is on.
With that said, in summary, I have tried a few different custom ROMs; Cyanogenmod 11 - 13, stable to nightly. PAC MAN ROM for Lollipop, some other roms for KitKat I found else where, but in all these I have not been able to get 4G to work. I understand about updating the Modem, and got the latest version from DocHoliday77's post for the Galaxy S3, in point of fact I tried every modem version for 4.3+ on there
But for all this, and it's been time consuming I never managed to actually get 4G to work as stated
I tried playing with settings in Test Mode (*#*#4636#*#*), changed preferred settings, added APN's, rebooting during certain phases of the moon ... but somehow it all avails me diddly.
Finally I have genuinely tried searching for info on if this just isn't going to happen and that's how it is, but somehow I found lots of posts about other models or networks that made it work more than something saying this won't work (putting aside the info on CM 11 that states it's a known issue and won't work on some build I forget).
Which leads me to this post: I wondered if anyone could point me in either the direction of a 4.4+ custom ROM or other ROM, compatible for SGH-T999 (T-Mobile Galaxy S3), that has working 4G. Or how I can get 4G to work on one of the ROMs I have already tried, kind of partial to a nice CM but I am willing to venture.
Also happy to just hear other input about giving new life to the phone so any feedback welcome
Thanks for your time!
NOTES
======
Using TWRP 3.x for flashing
Phone is rooted
IMEI is visible & fine on custom ROM
4G works on stock ROM
not experienced at this but willing to read
Edit: something I had not noticed before, I install Gapps for most of my tests but never use it. I just tried to download from Play Store, it acts as though I have no connection; waiting to download appears, then eventually it says waiting for network. Yet I am able to browse the net fine with the phone floating between 3G & H+. I don't know if that might help, so figured I should add it.
Is the phone running the latest bootloader and modem? Maybe both are needed to properly get 4g on all Roms?
audit13 said:
Is the phone running the latest bootloader and modem? Maybe both are needed to properly get 4g on all Roms?
Click to expand...
Click to collapse
That's a really good question, let me see if I can find out how to get my bootloader info and I'll get back to you.
May I ask what the latest bootlader is for the SGH-T999, or where I could find this so I can compare it? I couldn't seem to find it, though the most resourceful post I did find related was T999 UVDMD5 Firmware / Bootloader by mnasledov, though it is also a little outdated it appears, I haven't read my entire way through it yet sorry, I also know the phone is a little outdated too .
So that wasn't too bad to find out
I don't have the latest bootloader if that should match the baseband I install.
Where after a ROM install I get my baseband to T999UVUEOH1, but the bootloader stays on T999UVDLJA.
I haven't quite found where to get the latest bootloader just yet, though I did really spend the last few minutes discovering about the bootloader; if you or someone could find the time to point me in that direction that would be awesome
Simplest way to make sure you have the latest would be to flash the most recent stock rom from sammobile.com in Odin.
Thank you very much @audit13, I do appreciate the time you took out to help me and I also appreciate the point in the direction of what next.
I'll go dig into that for a while and see what to do to be sure, before I start
Looks like this is the latest one, so I will give this a shot : PDA T999UVUEOH1 & CSC T999TMBEOH1, version 4.3.
So just as a quick question, since I've never upgraded the bootloader in this fashion etc., from what I have read this is a one way street correct? And since I am upgrading to stock, then I guess will I lose root, which I will have to go back down the path of for a reinstall, or could I flash my old back up over this from TWRP and in that fashion have the latest bootloader, but keep everything I have for the moment as I investigate a ROM that will offer 4G.
I guess what I am getting at is even if having the latest bootloader and some other ROM with the latest baseband doesn't give me 4G still, can I go back in terms of the OS version to my 4.1.1 and keep things as is with a newer bootloader?
I will investigate this myself too, I just always preferred some additional input when discovering things where possible.
I do appreciate your time, thanks again!
No, you cannot run stock 4.1.1 on a 4.3 bootloader unless it is a custom 4.1.1 rom based on a stock touch wiz rom.
I do not think it is a problem to run the latest bootloader and modem as the latest custom ROMs often require an updated bootloader and modem.
Once on a 4.3 bootloader, you can't downgrade to something older.
Thanks again @audit13, that matches what I have read, I appreciate the confirmation!
Looks like I will be undergoing a re-root etc. so I'll get my information together, have a little more read, see what I need to back up and then jump down the rabbit hole
I'm grateful for your time and help.
If you decide to run a custom rom, just flash a stock rom, then immediately flash twrp via Odin, then install the rom and gapps. No need to root before hand.
Ahh ok, that would have made the most sense. However I didn't have an opportunity to check back on this thread until now so even though you had awesome speedy reply I missed it.
I did manager to successfully flash the stock ROM from Sam's. It did also update the bootloader so THANK YOU very much for that.
I had to fiddle a little to get Odin to recognize the my Galaxy S3 in the end it was simple: after I installed Kies to get the drivers on, I disabled WI-Fi (I use it for my dev work, and then it didn't try to spend time getting other drivers and it all went great. But that's just a note incase maybe one day someone else reads the thread and wonders how, this might help.
I'm just actually restoring a couple f things on the stock ROM, I figured I would have it ready in the event a custom ROM doesn't suit immediately, as I find one I like, then I have a back up of the stock ROM on 4.3 to revert to. Incidentally I just used TWRP manager from Google play store to install TWRP, hopefully it's the same as the flash, except now I know I rooted when I didn't have to
@audit13 Thanks, I know I keep saying that but I appreciate your time the same way I would hope someone else appreciated mine.
Incidentally once ready I will post an update here about the success of getting 4G on Cyanogenmod 12 or even 13 maybe, or someone of the other custom ROM I try, to share that info.
So just an update, I can confirm even with both an updated bootloader and matching updated baseband there is still no 4G on Lollipop Cyanogenmod 12, haven't quite tried any other yet, that was the one I liked the most but I will carry on and get a list as I have time then update here.
If there are any further suggestions I'm all open to them
Thanks [email protected]
Do you get 4G on a stock ROM? You have an LTE capabale sim? You get 4G on another phone with the same sim card?
Right, this SIM gets 4G on 2 other phones it's been in, on this phone on stock ROM it gets 4G too. Reverting back to stock backup in TWRP, from CM12 looks like it tripped knox I think it is, so now the warranty bit is 1 oops. But I managed to Odin back to 4.3 stock, so now I also need to see if I can try to flash maybe to CM 11, which is 4.4.x, or if maybe I'm stuck here. If I can find out I certainly will update the result of 4G testing.
You've been really patient & helpful thanks!
First let me say I'm a noob. I've rooted and jailbroken devices but I admit it's all from falling instructions. I rooted my s3 a while ago and installed twrp 1.0.8.7 yesterday. I did a full wipe including system and all catches and installed the latest nightly of cm13. Everything is running great. I don't know if this helps but maybe it's your process. Good luck!
Sent from my Amazon Jem using Tapatalk
Shack70 said:
First let me say I'm a noob. I've rooted and jailbroken devices but I admit it's all from falling instructions. I rooted my s3 a while ago and installed twrp 1.0.8.7 yesterday. I did a full wipe including system and all catches and installed the latest nightly of cm13. Everything is running great. I don't know if this helps but maybe it's your process. Good luck!
Sent from my Amazon Jem using Tapatalk
Click to expand...
Click to collapse
That's really helpful thanks @Shack70, since updating to 4.3 I have only tried CM 12, I can certainly give 13 a shot, & you have 4G working then please?
incidentally I have actually recorded every step I performed, in the event I repeat this again or I had to explain it. But my process maybe at fault I agree; I rooted my phone with towelroot. Installed TWERP manager (3.0.2 something, maybe I should try 1.0.8?), rebooted into recovery & first thing was take a full backup on stock. Then I did a factory wipe, & advanced wipe. Then installed the ROM, wiped dalvik/cache. Installed Apps, wipe dalvik/cache, reboot
Hopefully that's not too much? I just wonder if any of those steps raise alarm?
Edit: mind if I throw a few questions on here at you please @Shack70?
what do you wipe from the options please?
after the install, do you run any other wipes please?
how did you get TWRP on your phone? Not sure if that or version matters but I'm willing to try
Morrigon said:
That's really helpful thanks @Shack70, since updating to 4.3 I have only tried CM 12, I can certainly give 13 a shot, & you have 4G working then please?
incidentally I have actually recorded every step I performed, in the event I repeat this again or I had to explain it. But my process maybe at fault I agree; I rooted my phone with towelroot. Installed TWERP manager (3.0.2 something, maybe I should try 1.0.8?), rebooted into recovery & first thing was take a full backup on stock. Then I did a factory wipe, & advanced wipe. Then installed the ROM, wiped dalvik/cache. Installed Apps, wipe dalvik/cache, reboot
Hopefully that's not too much? I just wonder if any of those steps raise alarm?
Edit: mind if I throw a few questions on here at you please @Shack70?
what do you wipe from the options please?
after the install, do you run any other wipes please?
how did you get TWRP on your phone? Not sure if that or version matters but I'm willing to try
Click to expand...
Click to collapse
In twrp I wiped system and all caches before installing the rom and gapps. I installed an older version of twrp using Odin and updated it to 2.0.8.7 using the twrp app in the play store. Yes I have 4g/lte. I've seen it switch from lte to h+ to 3g depending on my location so I'm sure it's working correctly. The camera and Bluetooth also work fine. I hope this helps, I'm still learning and most of what I've done is just by following others instructions here at XDA.
Sent from my Amazon Jem using Tapatalk
I definitely appreciate the reply thanks!
I gave the latest nightly CM 13 a shot just now, 7/31/16 version essentially. Not finding any issues with the ROM, can't get 4G to show up no matter what though , even with changes and attempts to APN settings etc. None the less maybe to give my phone a rest I'll just stick with this a while and decide if a newer nightly comes out I want to try, or better yet a stable version at some point. Then I can verify how much I really miss my 4G I guess.
All the previous attempts, including this one always results in 3G to H+ network with no issue, it's just that 4G that never shows up for me.
Incidentally without a serious search around I couldn't even find TWRP 2.0.8.7, it's not on the TWRP manager version I have so curious, I ended up just going with 2.8.0.7, thinking maybe it was a typo?
Otherwise I basically run the same type of install you mention, I also clean dalvik, cache, system & data in my case. Just to confirm that.
I have a slightly off topic question here, if I decide to go back to to stock I was wondering, if i went from UVUEOH1 4.3 JB build, to the previous UVUENC2 4.3 JB build; because I've seen this available as a clean route 66 version, is this still considered a downgrade and a bad idea? I'd be flashing with Odin from @DocHoliday77 post here.
@Shack70, thanks for the input, thanks for the guide on your steps, glad I've confirmed I'm doing the same even if I can't get my 4G, hopefully someone on a Galaxy S3 T-Mobile, went through this found a solution, and maybe will let me know what they did too, not sure if you are on T-Mobile or not. 
 @audit13, also thanks, you've been replying plenty too and I appreciate that also!
One small thing I just came across looking over the logs of the install.
When flashing CM 13 with TWRP, I noticed it said the Target: samsung/d2tmo/d2tmo:4.3/JSS15J/T999UVUEMJC:user/release-keys.
Is it normal and OK for it the be referencing a different baseband/bootloader than what I actually have on my phone?
UVUEMJC vs the UVUEOH1? Where the one as named by TWRP flash is 2 versions older than what I have installed? Not necessarily stating this is an issue, just asking please if this is normal, and I also understand it could be something I have overlooked in my reading, it's been a lot of reading
I would not worry about the referenced baseband as flashing CM13 does not change the bootloader or baseband during the flash process.
audit13 said:
I would not worry about the referenced baseband as flashing CM13 does not change the bootloader or baseband during the flash process.
Click to expand...
Click to collapse
That makes sense thanks @audit13, just a few of the questions I had building up.
So that my previous question doesn't get lost, and although I know it's a dying phone for users hopefully this might get some visual
if I decide to go back to to stock I was wondering, if i went from UVUEOH1 4.3 JB build, to the previous UVUENC2 4.3 JB build; because I've seen this available as a clean route 66 version, is this still considered a downgrade and a bad idea? I'd be flashing with Odin from @DocHoliday77 post here.
Click to expand...
Click to collapse

Categories

Resources