I took the 4.4.2 OTA while rooted and am now stuck at "SAMSUNG" logo.
I can get into download mode, however, Odin refuses to connect, while my gf's identical phone connects fine.
I can get into CWM which I have since updated to PhilZ latest.
I've been shuffling around files on an SD card, but other than the recovery update I haven't been able to do anything.
In download mode I do have "Warranty Bit: 1". Not that I care (several year old phone moved from Sprint to Ting a while back). I have taken OTA updates before and expect that I was current before this one.
Any help would be greatly appreciated!
~cd
UPDATE:
I've tried the SD unbrick without JTAG and still can't connect. It keeps coming up as "Unknown Device", but I'm doubting driver issue because I've tried several and the other phone connects right away.
Is there anything I can load through the custom recovery that will knock some since into the thing?
UPDATE 2:
I was able to flash a rom with CWM and am back up now. Still can't connect to Odin or ADB. I'm starting to suspect a HW problem with my USB port.
I'm uncomfortable suggesting flashing anything in recovery without being able to know for sure if the OTA at least successfully updated your bootloader and modem.
Without knowing this, flashing the wrong thing will hard brick your phone, and I don't want to take your phone out of the frying pan and stick it directly into the fire, so to speak.
I would suggest trying longer and harder to solve the Odin connect problem.
Try a different USB port, try a different cable, reboot the PC, and do you have access to try a different PC if necessary?
Sent from my Sprint Samsung Galaxy SIII with M.O.A.R. v9.0, dkp kernel dated 3/20/2014 and TWRP v2.7.0.0.
I've tried everything you mentioned except a different PC, which won't be real easy. At this point I'm suspecting HW because my gf's S3 will connect right up. It's been a nightmare and to top it off, before I found my new one, the POS card reader I had close by fried both of my SD cards with all my backups. :crying:
ATM I'm on MOAR v9.0.1 MK3
Android ver: 4.3
Baseband ver: L710VPUND8
Not sure how to find bootloader ver..?
Thanks for the suggestions!
charlesdindy said:
I've tried everything you mentioned except a different PC, which won't be real easy. At this point I'm suspecting HW because my gf's S3 will connect right up. It's been a nightmare and to top it off, before I found my new one, the POS card reader I had close by fried both of my SD cards with all my backups. :crying:
ATM I'm on MOAR v9.0.1 MK3
Android ver: 4.3
Baseband ver: L710VPUND8
Not sure how to find bootloader ver..?
Thanks for the suggestions!
Click to expand...
Click to collapse
I think you're right. Since your Baseband (modem) is ND8, most likely the OTA successfully upgraded your bootloader, too.
You can stay on MK3 MOAR v9.01 if you want, or flash any of the ND8-based ROMs (Wicked 6.0 or completely stock but rooted, either Odexed or DeOdexed), or any other ROM for that matter.
I think there's even a completely stock, unrooted ND8 zip you could flash with the latest Philz Recovery if your phone's under warranty and you want to take it to the Sprint store or Best Buy to see if they'll fix your microUSB port.
One guy was out of warranty and they still fixed that got him for free at a Sprint store but I wouldn't count on that kind of luck.
Sorry to hear about your SD cards. Try r free Windows program USBit and use it to try resetting your cards to see if you can at least format and use them again.
You're welcome!
Sent from my Sprint Samsung Galaxy SIII with M.O.A.R. v9.0, dkp kernel dated 3/20/2014 and TWRP v2.7.0.0.
Yeah, I've tried multiple ports and cables on another machine and neither the phone nor the machine do anything other than charge the phone. I have the tools and experience for SMT rework so I'll throw in a new port if it doesn't just need cleaned or re-soldered.
Related
So here is the situation:
Samsung Galaxy S3 T999 with no external SD card (at the moment).
Locked to TMobile, but running on StraightTalk.
Rooted using ODIN and Root66.
Installed CWM (whatever the most recent version is) by way of ROM Manager.
Installed Cyanogenmod 10.0.0-d2tmo.
Dorked around for a while.
Attempted to encrypt phone.
Encryption failed, and I am now faced with the ubiquitous "Encryption unsuccessful" error.
I can still access CWM, and can still put the phone in Download Mode. I have attempted to delete/clear all partitions/caches through CWM, but, unsurprisingly, that did nothing. Internal SD card will not mount.
I have been doing some reading throughout the various forums here, and while I am fairly sure how to proceed, I want to make sure before diving in:
1. Is this recoverable through ODIN / Root66?
1. a. Will I need an external SD Card for ODIN?
2. Barring that, has anyone found a better work-around than using an external SD card to boot your phone, and apparently ignoring the onboard storage?
Thanks for whatever help you can provide... I know just enough to root and flash, but this went *way* over my head .
ODIN was the trick - plugged in the phone, flashed it back to a rooted stock, it rebooted, had the whole "Encryption Unsuccessful" screen when it came back up, I may have uttered a few choice words, pushed the "reset" button, the phone sat there for a good long while, and came back up in the rooted stock. Flashed CM on the phone, and we are back at work again.
Note to self - no more whole-phone encryption. Bummer.
Coming from an HTC Incredible, this whole "ODIN" thing is downright awesome.
Glad you figured it out.
The Encyption Bug is affecting the S3s now?!?! I though it was only prevalent on the first Galaxy S Devices. Is this a Cyanogenmod issue?
I cannot say if it is THE "encryption unsuccessful" bug, but I cannot think of any other reason this would have happened - the phone was chugging merrily along at encrypting itself (about 35% last I paid attention to it) until it was not, in a safe location, away from pets / small children / etc. It was plugged in, charged adequately, and had a PIN already set.
Annoying as hell, but at least it was recoverable!
I just experienced the same issue. Encrytion fail galaxy s3 while I was on custom rom. I tried everything. First you need to go to sammobile and download the firmware that matches your device. Download the newest version of odin. Download the newest samsung drivers. Go in to odin and attach the tar file in the pda section of odin. Flash it! Ta Da! Back to stock. Now all you have to do is root and install cwm.
Here's the situation,
My USB port has failed. I am unable to charge my phone or connect to my computer via USB. I have tried multiple USB cables, chargers and computers without any luck. I have insurance with sprint, but I am under the impression I need to revert to a stock rom (without root) in order to qualify. Here in lies the problem! I am unable to connect to odin to perform the one-click exe. that I am familiar with. I have mobile odin pro, as well as dropbox, but I am very unfamiliar with how to revert with these programs. I have read a number of threads trying to figure out the best way to go about this, but I am unsure on the order in which I need to proceed to avoid bricking my phone.
I thought about just bringing my phone in as is and seeing if they would replace it, but right now I have the yellow caution triangle at bootup, the binary counter says 1, and I am running andriod 4.2.2. I am worried that if they say I voided the warranty, I will be unable to get the phone repaired.
Right now the phone is working without any other problems, until the battery dies (25% left) and I can't charge it (again). I am running the following setup:
Baseband version: S: D710.10 S.FL24
Kernel version: 3.0.64 -CM-g31f128d, [email protected] #1
CyanogenMod version: 10.1-20130705-unofficial-d710
Build number: cm-d710-userdebug 4.2.2 JDQ39E eng.dastin1015.20130705.092856 test-keys
I also have CWM-based Recovery v6.0.3.3, but like an idiot I apparently did not create a backup before flashing 4.2.2
Questions
Can I complete a one-click exe. with mobile odin that will revert me to stock?
Which one should I choose?
Do I need to DL and install a different bootloader, modem, kernel, etc before completing the one-click?
I am still a rookie when it comes to flashing, but I am able to follow instructions well. Any advice one what steps to take is greatly appreciated!
I would not flash with that little amount of battery left. I would do one of two things. Get an external charger and flash back to stock(gb27 stock unrooted), can be flashed with MO, or flash triangle away and take it into the Sprint store. If you have more than one Sprint store in your area, I'd try the latter first, but that's just me. And one clicks install everything, modem, kernel, etc.
Sent from my SPH-D710BST using xda premium
So I decided to go with the external charger. After I had a battery that had some life again, I called sprint to switch back to my GS2 from a pile of crap flip phone I am using. Unfortunately, the sequence of numbers they told me to get the pop-up screen would not work. I assume that is because I am running 4.2.2 with the cyanogenmod phone rather than the standard dial-er. Is there anyway around this or should I just flash my device back to stock and start over from scratch? Thanks
Matt
memogensen said:
So I decided to go with the external charger. After I had a battery that had some life again, I called sprint to switch back to my GS2 from a pile of crap flip phone I am using. Unfortunately, the sequence of numbers they told me to get the pop-up screen would not work. I assume that is because I am running 4.2.2 with the cyanogenmod phone rather than the standard dial-er. Is there anyway around this or should I just flash my device back to stock and start over from scratch? Thanks
Matt
Click to expand...
Click to collapse
I would try flashing back to stock and then retrying the sequence. From what I've heard in regards to AOSP ROMs, you can't do things like update your PRL or activate that device for a mobile carrier (although i may be wrong about the latter)
If you're still having trouble with your USB cable i would suggest looking into Mobile Odin for flashing a stock kernel and firmware. You can check the second post of the Mobile Odin thread for instructions on how to do it, and if you're still unsure about the process you can drop a question in that thread and have it answered there.
EDIT: It seems that this thread sounds like some problems you're experiencing with your USB port. As for the Sprint Activation you may have to revert to a stock ROM/kernel, but you can try the method listed in that thread and hopefully it would work out and allow you to connect through USB
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
gvazquez82 said:
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
Click to expand...
Click to collapse
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
MrHaPpY66 said:
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
Click to expand...
Click to collapse
First of all thank you for trying to help me, I hope you are having a good Thanks Giving.
I used the thread you linked to, and downloaded the version with out knox. I followed the instructions
transferred ROM and flashed kernel file to SD card
used odin to flash TWRP,
used twrp to flash rom and kernel file.
and it takes the file thankfully, there's only one issue. My phone can't make or receive calls/texts. Is yours able to?
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Next Update
the bootloader I flashed apparently flashed to the external sd card? I flashed another one and it is booting from the internal sd. I had to flash a different modem the one in the bootloader/modem file I flashed from the link above didnt take? I got most everything sorted out, but im getting tired, it has been an all night adventure. its 08:23 est now
sorry for the delay in updating this I had to get some rest.
theramsey3 said:
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Click to expand...
Click to collapse
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
spongdangly said:
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
Click to expand...
Click to collapse
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I will give that a shot, but what's an APN, sorry. And how do I create one, and is it needed for me to do so?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
It should be, I'm working right now so I don't have time to fine the guide on how to inject your IMEI. If I remember correctly it involves using QPST. If you have an old (or any) working Nandroid backup that should fix the problem.
FYI, make sure you don't use the guide for the international S3 as it has different hardware and folder structure/contents.
As for the APN, it should automatically fill itself in since it reads it off the SIM Card (I might be wrong).
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I tried it and it work!!!!!!!!!!!!!!!!!
67 texts just came in. Sir, I thank you oh so kindly. You have made this gloomy rainy day oh so joyous.
No problem. Glad I could help you.
The real credit should go to -Mr.X-, loserskater and anyone else(no disrespect there were alot of files) whose stuff I tried to flash lastnight thank you all in the dev community who contribute.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
gvazquez82 said:
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
Click to expand...
Click to collapse
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
flexfulton said:
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
Click to expand...
Click to collapse
do you know of a good stable kit kat like ROM I could use for the s3? And any speculation as to why the ROMs werent taking for me?
First off I'd like to say hello my name is Fred and this is my first thread so please don't hang me if this is a common problem.
Now onto the problems...
A few days back my wife's sph-l710 (stock) was up for an system update. She let it do its thing and update and shortly thereafter it went I to an Infinite loop of rebooting itself. She asked me to fix it. So what I did was try and bypass any issue that was going on my simply wiping everything and rooting the device. All that went successful no more random reboots but in doing so a few more problems came about. I flashed over a stock rooted Rom and lost wifi capabilities. So I decided to flash it over to cyanogen (which I have been running for a long time on my gs3) but the phone would not take the Rom. Kept getting error messages, I tried out both cwm and twrp both of which had the same results. I also tried pretty much every cm version for the phone and only one worked cm10.0. After flashing over cm10 everything worked beautifully except for the camera. I did a small amount of research and found that this (was) a common issue. I've tried flashing the camera fix .zip file I found on the net after wiping the phone again. No results, I tried many other camera apps and still no camera function. Just keeps saying could not connect to camera.
So I got to thinking my phone is on cm11 and has never had such problem so why don't I just upgrade the version of cm. I attempted again to upgrade and the phone will not take any other Rom but cm10.0. I am totally lost at this point, I even tried copying the cm11 zip file from my own gs3 and tried flashing that still no results.
So after all that (sorry for the essay) I'm stuck wondering what I can do to upgrade my wife's phone to cm11 like mine is.
Thanks in advance,
Fred
Sent from my SPH-L710 using Tapatalk
Hi! Let's take things one step at a time.
First, can you still access the internal "SD" by booting the phone up and plugging it in to your PC?
If so, back up all your wife's files from there that you want, or you can use an Android file manager like X-plore and copy everything from internal to your external SD.
Then find the stock ND8 tar thread in Development and use Odin on your PC to flash the 1.5GB tar that's inside the zip you'll download.
From there she should be set unless you want to go to optional efforts of flashing a custom recovery, rooting, etc.
Hey that far at least, though, first.
Sent from my Sprint Samsung Galaxy SIII with M.O.A.R. v9.0, dkp kernel dated 3/20/2014 and TWRP v2.7.0.0.
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.