Related
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
So, after months of tinkering and toying around with my TMO GN2... I have ran into nothing but problems with the ROM's I have installed... Tweaked, CM11, Liquid, Slim... doesn't matter - something doesn't work the way I want. At any rate, I upgrade in 2 months to a new phone and would like this thing just to go back to bone stock. Unroot, factory image, everything. Since I am on a 4.4.4 ROM, how would I do this? I know it involves a factory image and ODIN, but when I tried it locked the phone up twice. Lucky me, I had a backup ready to go...
Thanks.
svavrek said:
So, after months of tinkering and toying around with my TMO GN2... I have ran into nothing but problems with the ROM's I have installed... Tweaked, CM11, Liquid, Slim... doesn't matter - something doesn't work the way I want. At any rate, I upgrade in 2 months to a new phone and would like this thing just to go back to bone stock. Unroot, factory image, everything. Since I am on a 4.4.4 ROM, how would I do this? I know it involves a factory image and ODIN, but when I tried it locked the phone up twice. Lucky me, I had a backup ready to go...
Thanks.
Click to expand...
Click to collapse
Try visiting this link http://forum.xda-developers.com/showthread.php?t=1955423 thread is by simplelife
svavrek said:
So, after months of tinkering and toying around with my TMO GN2... I have ran into nothing but problems with the ROM's I have installed... Tweaked, CM11, Liquid, Slim... doesn't matter - something doesn't work the way I want. At any rate, I upgrade in 2 months to a new phone and would like this thing just to go back to bone stock. Unroot, factory image, everything. Since I am on a 4.4.4 ROM, how would I do this? I know it involves a factory image and ODIN, but when I tried it locked the phone up twice. Lucky me, I had a backup ready to go...
Thanks.
Click to expand...
Click to collapse
Factory reset. Odin the current TW tar file from sammobile. Boot phone and make sure it runs. Fuggeddaboutit.
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.
Just some background: Running an unrooted Galaxy S4 since the S4 first came out w/ T-mobile and everything was ok. Sometime this summer T-mobile came out with the 4.4.2 OTA update and since then everything went to hell. On my 2nd replacement phone from T-mobile and the issue of the phone suddenly not being able to make or receive calls after a successful Bluetooth car connection persists. Everything else works BUT that. I'm just no longer comfortable in pulling off on highway shoulders to speak on the phone. T-Mobile did a shoulder shrug and told me to deal with Samsung directly...which i wont even bother with. So..... I'm ready to flash the phone. My question is. What is the MOST stable, least loaded with bloatware ROM that is available (where all the functions work). I currently run the NOVA launcher and plan to do same. I do not care about the ROM having specific graphical functions and just prefer the stock T-mobile ROM look. Thank you guys in advance (if someone can direct me to a link with FLASH instructions I'd appreciate it too... (haven't flashed since my Evo3D a few years back) Once again, Thank you for your time.
At lunch now so just time for a few quick thoughts:
You might as well update to 4.4.4 first to get the latest LTE modem.
Then use Odin to flash the latest TWRP recovery.
Look into the Google play edition or slimkat ROMs. They are debloated and tend to be safe choices.
Sent from my SGH-M919 using Tapatalk
First thing is to backup your phone on your pc, since you don't have a custom recovery.
http://forum.xda-developers.com/showthread.php?p=55374113
This is simple and debloated, stock with some developer features.
Or you can flash stock samsung and debloat yourself.
Plenty of material on YouTube to get you started.
I'm currently running factory stock debloated, no knox, no samsung junk or tmobile junk. Also running CWM recovery. Everything works, bluetooth works perfectly on my Kenwood ddx 714.
Pp.
PanchoPlanet said:
First thing is to backup your phone on your pc, since you don't have a custom recovery.
http://forum.xda-developers.com/showthread.php?p=55374113
This is simple and debloated, stock with some developer features.
Or you can flash stock samsung and debloat yourself.
Plenty of material on YouTube to get you started.
I'm currently running factory stock debloated, no knox, no samsung junk or tmobile junk. Also running CWM recovery. Everything works, bluetooth works perfectly on my Kenwood ddx 714.
Pp.
Click to expand...
Click to collapse
Pancho, how does one backup phone to PC?
Thanks for the link on the debloated ROM. Are there step by step instructions on how to flash it from stock? I havent done this in a while. Thanks.
All you do is copy your internal/external sd's to a folder, you never know what can happen. make sure you sign into google/play store so all your apps/contact info can be restored. You will find instructions in rom tread Op and from other members as they post. You Tube is very handy also.
Pp.
KEVIN88GT said:
Pancho, how does one backup phone to PC?
Thanks for the link on the debloated ROM. Are there step by step instructions on how to flash it from stock? I havent done this in a while. Thanks.
Click to expand...
Click to collapse
Samsung KIES product will backup your phone:
http://www.samsung.com/us/kies/
And, installing it will install the drivers that you need for when you need to use ODIN.
Rob
Kies can be cantankerous if your not stone stock, once you root kies won't recognize your phone but you should be able to access the backed up files with windows explorer. I use it with my wife's note 3 only because its stock, never rooted, and it works OK.
Pp.
PanchoPlanet said:
Kies can be cantankerous if your not stone stock, once you root kies won't recognize your phone but you should be able to access the backed up files with windows explorer. I use it with my wife's note 3 only because its stock, never rooted, and it works OK.
Pp.
Click to expand...
Click to collapse
Since the OP is running un-rooted stock, KIES should work fine for backing up the phone. Now, when/if he roots, and installs a custom recovery/ROM, then it may not.
So, OP, use KIES to backup what you have now with stock. Then, when/if you install a Custom Recovery, you can do a NAND backup to the SD card.
Rob
My S3 overheats and drains battery when I'm on a call and when I surf the net Are there apps that manage the phone so it doesnt heat a lot? Are there modems I can download that better manage the battery?
I'm not sure that the modem has much of a role to play in saving battery power.
I always recommend running the latest modem and bootloader to ensure compatibility with the latest custom ROMs.
audit13 said:
I
I always recommend running the latest modem and bootloader to ensure compatibility with the latest custom ROMs.
Click to expand...
Click to collapse
Hi audit. Well I'm not usong a custom rom. I'm using a rooted stock rom, whichbis JB.
But is it possible to install the latest bootloader and modem on JB? Would tjey be compatible? If so, where do I download them from?
The latest bootloader and modem for a T-Mobile phone is a jb. For a Canadian version, which is what I have, the latest modem and bootloader is kk. I don't think the two bootloader or modems are interchangeable.
I honestly can't think of a reason as to why the software would cause the heat issue.
audit13 said:
I honestly can't think of a reason as to why the software would cause the heat issue.
Click to expand...
Click to collapse
I think its got to do with busy box or process by which I rooted the phone. I say this because after I backed up and tried to restore my phone through a nandroid, the restore was a total mess. The restore was incomplete. Ever since then, the phone hasnt been the same. I then tried wiping the cache, dalvik, data, did a reset and reformatted the phone. And that didnt help at all. I'm as dumbfounded as you are about this.
You did a full restore via Odin and did a full wipe via stock recovery before first booting the phone?
Rooting should not cause a heat issue and I don't see how busy box would either.
audit13 said:
You did a full restore via Odin and did a full wipe via stock recovery before first booting the phone?
Rooting should not cause a heat issue and I don't see how busy box would either.
Click to expand...
Click to collapse
Well regardless, my trouble began after I did a restore and the restore wasnt an exact restore. So somewhere in the phone there lies a major bug especially when the restore wasnt an exact duplicate of the backup.
BTW, since I'm running JB and got the regular task manager, do you know how I can get the card stack-like task manager thats prevalent in Lollipop?
All I can recommend at this point is flashing back to stock, performing a factory reset via stock recovery, and use the phone unrooted to see what happens.
Sorry, not sure how to get the stacked manager,
audit13 said:
All I can recommend at this point is flashing back to stock, performing a factory reset via stock recovery, and use the phone unrooted to see what happens.
Sorry, not sure how to get the stacked manager,
Click to expand...
Click to collapse
But I flashed to stock like I told you before.
I know but I wasn't sure if you left it unrooted and tab it that way to see if things changed.
All I can say is mine gets warm during use but not hot.
audit13 said:
I know but I wasn't sure if you left it unrooted and tab it that way to see if things changed.
All I can say is mine gets warm during use but not hot.
Click to expand...
Click to collapse
I understand. I'll just leave it at that. Dont want to waste any more time than I already have on this phone. Not worth all the trouble.