Develop Bugs

[Q] Two issues I am .

I have been having
Issue 1:
In the past 2-3 weeks, when I am on a phone call I am able to hear the other person, but they are not unable to me.
This does not happen every call, just some, both inbound and outbound.
I have tried multiple ROMs but it does not seem to help (ROMs tested: CM7, Virtuous Doubleshot v1.0.1 and RCMix3D KINGDOM)
If it matters, I'm with VodaFONE in Australia, but this happens even when I have full coverage.
Looking at the whole next to the micro usb port it seems to be clear.
Is this a software or hardware issue? Is there anything I can do to fix it besides un-root and RMA?
Issue 2:
While listening to music or watching a movie, my phone will start to use "voice search" without me prompting it to.
Is this a common issue or something that I can easily fix? (I have no real need for this, so if there's a way to uninstall it, I really wouldn't mind).
If I need to un-root and RMA I will, but I would prefer not to. If there is other information requested, just ask and I will do my best to answer.

kernels And Radio
Have you tried changing radio and kernel of the phone??

Flash a newer radio and change the ril's in the rom you're using to fully utilize the new radio properly.
You may be using an older radio, and the rom probably is probably using ril's for a newer or different radio than what's installed on you device, thus causing your issues.

flash it back to original and send it to Vodafone, because this sounds like a bigger problem....

Freak2011 said:
flash it back to original and send it to Vodafone, because this sounds like a bigger problem....
Click to expand...
Click to collapse
I dont think the problem is quite that big. It doesnt seem like a hardware fault because if it was a hardware fault then it would be most if not all calls that are affected if the microphone didnt work. He says that it is only some which leads me to believe it is a software error. A different radio and matching RIL's should fix it.
Look on the ROM description page of the ROM you are using and install the radio that it recommends. It will already have matching RIL's for it.

... a lot of people do the downgrade to 1.32 to root, and forget to update the radio when they start using custom rom's built off newer builds that originally come with newer radio builds...
mind you, the op's problems are some of the lesser that i've come across... quite tame actually
If you're using the RCMix Kingdom Rom, use Radio_12.56.60.25_26.10.04.03_M

Thanks for all the help. Will try flashing a new radio and shall come back here to say if it worked or not.

[Q] Rooting Questions

Hi, I have looked around for a while, but have not received direct answers to these questions, any help would be appreciated. I am not new to rooting since I have rooted and flashed my previous phone (HTC Wildfire S), but these questions were unanswered to me, irregardless of where I looked.
-First, I know that when you gain root access you may toy around with your phone, but by rooting your device do you damage it? I am concerned about this because when I had a Wildfire S I rooted it and within a week it had MAJOR bugs, without flashing or moving any setting.
-Second, how do you perform a nandroid backup? I know that this is kind of a safety net to your device if it ever gets soft-bricked, but how do you do it? I have not had a clear explanation on how to do it.
-Third, I know that CyanogenMod is one of the most stable custom ROMS that there is out there, but does it offer Pure Android?
-Fourth, if any of you know any good (and stable) custom ROMS for the T-Mobile Galaxy S3, could you send them to me please?
-Fifth, I know that with some ROMS you lose certain features (such as video playback in some ROMS, yeah I know sounds terrible) but if I flash a ROM that does support this, do I gain the feature back or do I lose the feature forever?

Going through the same process
amezcuaesteban said:
Hi, I have looked around for a while, but have not received direct answers to these questions, any help would be appreciated. I am not new to rooting since I have rooted and flashed my previous phone (HTC Wildfire S), but these questions were unanswered to me, irregardless of where I looked.
-First, I know that when you gain root access you may toy around with your phone, but by rooting your device do you damage it? I am concerned about this because when I had a Wildfire S I rooted it and within a week it had MAJOR bugs, without flashing or moving any setting.
-Second, how do you perform a nandroid backup? I know that this is kind of a safety net to your device if it ever gets soft-bricked, but how do you do it? I have not had a clear explanation on how to do it.
-Third, I know that CyanogenMod is one of the most stable custom ROMS that there is out there, but does it offer Pure Android?
-Fourth, if any of you know any good (and stable) custom ROMS for the T-Mobile Galaxy S3, could you send them to me please?
-Fifth, I know that with some ROMS you lose certain features (such as video playback in some ROMS, yeah I know sounds terrible) but if I flash a ROM that does support this, do I gain the feature back or do I lose the feature forever?
Click to expand...
Click to collapse
I'm going through this same process now, and am new also--I rooted an old mytouch 3g slide and flashed CM7 on it. Afterwards it was bit buggy, but it was a bit buggy before too, hardware issues I think.
I think rooting in and of itself shouldn't mess up your phone, but if you don't do it correctly it could surely screw things up.
Do you have the T999 or T999L? which version will matter in terms of ROM flashing details (for example, I have the T999L, which is the LTE version)
Let me know of the progress you have on these questions!

I'm going through this same process now, and am new also--I rooted an old mytouch 3g slide and flashed CM7 on it. Afterwards it was bit buggy, but it was a bit buggy before too, hardware issues I think.
I think rooting in and of itself shouldn't mess up your phone, but if you don't do it correctly it could surely screw things up.
Do you have the T999 or T999L? which version will matter in terms of ROM flashing details (for example, I have the T999L, which is the LTE version)
Let me know of the progress you have on these questions!
Click to expand...
Click to collapse
I unfortunately have the T999. I know that mine won't be able to get LTE which is sad, but is this something that I MUST look into before flashing a ROM? Like are the t999 and T999L that different, I mean it is ONE chip.

amezcuaesteban said:
I unfortunately have the T999. I know that mine won't be able to get LTE which is sad, but is this something that I MUST look into before flashing a ROM? Like are the t999 and T999L that different, I mean it is ONE chip.
Click to expand...
Click to collapse
It's something to be aware of. I believe most of the T-mobile gs3 ROMS are built with the T999 in mind though, so you shouldn't really worry too much.
DocHOliday77's thread [INFO] [FAQ] Galaxy S3 w/ LTE - SGH-T999L & SGH-T999N points to some discrepancies between the T999 and T999L though
If you find my answers useful, push my thanks button! I need 10 to get full xda credentials

amezcuaesteban said:
Hi, I have looked around for a while, but have not received direct answers to these questions, any help would be appreciated. I am not new to rooting since I have rooted and flashed my previous phone (HTC Wildfire S), but these questions were unanswered to me, irregardless of where I looked.
-First, I know that when you gain root access you may toy around with your phone, but by rooting your device do you damage it? I am concerned about this because when I had a Wildfire S I rooted it and within a week it had MAJOR bugs, without flashing or moving any setting.
Rooting does nothing but give you SuperUser access to your phone. That is literally all it does. Now what you do with it can cause major headaches.
-Second, how do you perform a nandroid backup? I know that this is kind of a safety net to your device if it ever gets soft-bricked, but how do you do it? I have not had a clear explanation on how to do it.
Install a custom recovery such as TWRP or Clockwork (CWR), then boot into recovery via key combo (Power+VolDown+Home, see blue light at top left and release the keys). From there you will see how Back Up/Restore options.
-Third, I know that CyanogenMod is one of the most stable custom ROMS that there is out there, but does it offer Pure Android?
Many ROMs out there. Just need to read the OPs for what you want.
-Fourth, if any of you know any good (and stable) custom ROMS for the T-Mobile Galaxy S3, could you send them to me please?
Not allowed and don't ask this type of question. All it ever turns into is an EPeen contest and will surely get the thread closed down.
-Fifth, I know that with some ROMS you lose certain features (such as video playback in some ROMS, yeah I know sounds terrible) but if I flash a ROM that does support this, do I gain the feature back or do I lose the feature forever?
This is exactly what a Nandroid backup is for. Something that you don't like or something borks, then just boot into recovery and restore your last working ROM backup. Kind of the point. Not sure I have ever heard of a ROM losing video playback as all are pretty much optimized nowadays.
Click to expand...
Click to collapse
See my edits in Red.
el_garicimo said:
I'm going through this same process now, and am new also--I rooted an old mytouch 3g slide and flashed CM7 on it. Afterwards it was bit buggy, but it was a bit buggy before too, hardware issues I think.
I think rooting in and of itself shouldn't mess up your phone, but if you don't do it correctly it could surely screw things up.
Do you have the T999 or T999L? which version will matter in terms of ROM flashing details (for example, I have the T999L, which is the LTE version)
Let me know of the progress you have on these questions!
Click to expand...
Click to collapse
See my part above about Rooting. You are correct in that it doesn't affect anything whatsoever. It is what you do with it.
I am pretty sure that most are based off T999 code and in order to have the LTE, you have to flash the LTE modem. Might want to ask Doc about that as he has/had the T999L.
Also, CM7 was a long time ago and things have massively progress since then.
amezcuaesteban said:
I unfortunately have the T999. I know that mine won't be able to get LTE which is sad, but is this something that I MUST look into before flashing a ROM? Like are the t999 and T999L that different, I mean it is ONE chip.
Click to expand...
Click to collapse
See my reply above.
el_garicimo said:
It's something to be aware of. I believe most of the T-mobile gs3 ROMS are built with the T999 in mind though, so you shouldn't really worry too much.
DocHOliday77's thread [INFO] [FAQ] Galaxy S3 w/ LTE - SGH-T999L & SGH-T999N points to some discrepancies between the T999 and T999L though
If you find my answers useful, push my thanks button! I need 10 to get full xda credentials
Click to expand...
Click to collapse
This is false. You don't need 10 Thanks to get your credentials. You need 10 posts in order to lose the Captcha and be able to post in the Development threads. Please do not post a question in the Dev thread or even worse a "Thanks". This link should explain it all for you.

Solution for anyone with incoming calls issue after Marshmallow update

Hello everyone, I currently have AT&T HTC M8,
I recently came across this issue after I installed an Android M rom (SkyDragon, CM13 etc), I wasn't able to receive any incoming calls, they were all redirected to voicemail, I tried to change roms, change different settings, nothing worked.
Finally I searched for Android M's firmware and came across 6.12.1540.4, just search for it and flash it in fastboot.
Once you'll flash that firmware, do a clean install of TWRP recovery & ROM of your choice, it should work with all Marshmallow roms.
Not sure if it'll work if you'll restore it back to Android L (may get stuck in boot-loop or something, not sure).
I'm not taking responsibility if anything happens to your device, if you have any questions, feel free to write & I'll try my best to answer.
Thanks.

I think what you experienced is a kernel problem and not a firmware problem.
And even so, not everybody can do this as you need S-OFF.

Mr Hofs said:
I think what you experienced is a kernel problem and not a firmware problem.
And even so, not everybody can do this as you need S-OFF.
Click to expand...
Click to collapse
I never modified the kernel, it was always stock, for some reason, it worked for me after updating the firmware from 4.xx to 6.12.xx.
I agree about S-OFF, we really need that to mess around with the device.

rawfire said:
I never modified the kernel, it was always stock, for some reason, it worked for me after updating the firmware from 4.xx to 6.12.xx.
I agree about S-OFF, we really need that to mess around with the device.
Click to expand...
Click to collapse
That's probably a reason. If you installed international/wwe/gsm roms then AT&T/verizon/sprint it could be a problem. Have you checked the specific AT&T subforum for the M8....it's there for a reason because it holds differences.
I personally think you are one step ahead of the real solution. I think it's kernel related. Check the subforum for some info. See if it comes up with something.
I could be wrong......so don't hold that against me, just giving my thoughts

Mr Hofs said:
That's probably a reason. If you installed international/wwe/gsm roms then AT&T/verizon/sprint it could be a problem. Have you checked the specific AT&T subforum for the M8....it's there for a reason because it holds differences.
I personally think you are one step ahead of the real solution. I think it's kernel related. Check the subforum for some info. See if it comes up with something.
I could be wrong......so don't hold that against me, just giving my thoughts
Click to expand...
Click to collapse
That's really a thought, I'm definitely gonna check it and see if it's something related to kernel. Thanks for the suggestion.
And yeah, firmware upgrade was the last resort I guess lol,
Really appreciate that.

rawfire said:
That's really a thought, I'm definitely gonna check it and see if it's something related to kernel. Thanks for the suggestion.
And yeah, firmware upgrade was the last resort I guess lol,
Really appreciate that.
Click to expand...
Click to collapse
If you find anything please let us know. So we all can learn something if possible

Android Upgrade / Root?

Hello,
I've got a Galaxy Tab Pro 8.4 that I bought during the few months when it was the top of the line small tablet from Samsung (before the S series came out). Since it seems clear that Samsung has abandoned it and it won't get an Android update, I want to see what it'll take to upgrade to at least Lollipop. I'm pretty tech savy, but I've never tried to do anything like this with Android and I'm not at all sure where to start.
I've started to read the thread on rooting, but I quickly got a bit lost as I don't understand the terminology.
My goal would be to simply get to stock Lollipop or Marshmallow and have a stable, functional tablet that I don't have to tweak or mess with much. I'd also like to be able to go back if it proves too buggy. Is that feasible, or is rooting plus upgrading pretty much something that will require constant maintenance and tweaking? If it is possible, can someone point me to a how to for complete newbies?

Rooting will not help you upgrade your tablet to Lollipop or Marshmallow as they aren't available for your device. You might want to google "what is rooting" and find out what it does before proceeding.
The only thing you could do to get L or MM is install a custom ROM such as this:
http://forum.xda-developers.com/gal...5-1-x-cyanogenmod-13-0-nightlies-tab-t3256093

CafeKampuchia said:
Rooting will not help you upgrade your tablet to Lollipop or Marshmallow as they aren't available for your device. You might want to google "what is rooting" and find out what it does before proceeding.
The only thing you could do to get L or MM is install a custom ROM such as this:
http://forum.xda-developers.com/gal...5-1-x-cyanogenmod-13-0-nightlies-tab-t3256093
Click to expand...
Click to collapse
What makes you thin that his device is not have any Third Party ROMs (i.e CyanogenMod)? FYI this is the Tab Pro Fourm, and his Device should damned well be able to get to Lollipop or Marshmallow. e.g. CM12.1, or CM13.
As for rooting which you have to do at the start. Will most likely send him back to SamFirmware's where he'll need to likely first downgrade his Firmware to one that has a rootable exploit. i.e. a 'BOC1' ROM for the T325. (Which is the version I have). Through Odin (Samsung's Android Firmware Windows PC flashing Software). Then run something like the CFRoot App to get root.
NOTE: THIS WILL THROW YOUR KNOX FLAG!
This means that you'll never be able to use Knox services on that Device ever again. It will also throw the Warranty Flag as well Alerting Samsung that the Firmware was tampered with. For the moment (As I gather there is no known way to reset either of these Flags.) Not that this should stop you from installing either CM12.1 Lollipop (Seems to have lost support to) CM13 Marshmallow which is currently on a nightly release.
So the better question to ask is which T32x does Op even have? The T320 (Wi-Fi) The most common, and cheapest version has the greatest support. Where as the T325 (LTE), and T321 (3G) versions seem to be leaving behind. though even these are currently well into Marshmallow, and like with most ROMs there are some small bugs. But, on the whole My Device is more or less working as it should be.

Ichijoe said:
What makes you thin that his device is not have any Third Party ROMs (i.e CyanogenMod)? FYI this is the Tab Pro Fourm, and his Device should damned well be able to get to Lollipop or Marshmallow. e.g. CM12.1, or CM13.
As for rooting which you have to do at the start. Will most likely send him back to SamFirmware's where he'll need to likely first downgrade his Firmware to one that has a rootable exploit. i.e. a 'BOC1' ROM for the T325. (Which is the version I have). Through Odin (Samsung's Android Firmware Windows PC flashing Software). Then run something like the CFRoot App to get root.
NOTE: THIS WILL THROW YOUR KNOX FLAG!
This means that you'll never be able to use Knox services on that Device ever again. It will also throw the Warranty Flag as well Alerting Samsung that the Firmware was tampered with. For the moment (As I gather there is no known way to reset either of these Flags.) Not that this should stop you from installing either CM12.1 Lollipop (Seems to have lost support to) CM13 Marshmallow which is currently on a nightly release.
So the better question to ask is which T32x does Op even have? The T320 (Wi-Fi) The most common, and cheapest version has the greatest support. Where as the T325 (LTE), and T321 (3G) versions seem to be leaving behind. though even these are currently well into Marshmallow, and like with most ROMs there are some small bugs. But, on the whole My Device is more or less working as it should be.
Click to expand...
Click to collapse
1) I read the OP. He said, "stock Lollipop or Marshmallow."
2) You don't have to root TouchWiz to install a custom ROM. All you have to do is install TWRP, but it doesn't matter because of #1 above.

Well yes if he wanted Stock then he'd be outta luck. But that is not how I read it. I read it that he has accepted the fact that Samsung have left us in the lurch concerning any future updates.
That's how I read it, so the question follows in how to install a Custom ROM. Granted it should be possible to install TWRP v. 3.0.1-0, though Odin, and then the Device appropriate ROM. It should go without saying that the T320, and T325 are not the same Device, even if they are both collectively known as Galaxy Tab Pro's 8.4. As such it would be upnto the owner to know which version he might need.

Ichijoe said:
Well yes if he wanted Stock then he'd be outta luck. But that is not how I read it.
Click to expand...
Click to collapse
The problem, is folks really need to stop using the word "stock" as it really doesn't mean jack. Or at the least, means so many different things to different people, as to be basically meaningless. I would take stock to mean, what belongs on the device per the manufacturer, so that would be Kitkat TouchWiz in this case. To others (and probably what the OP is getting at) is a "pure" unskinned Google experience like Nexus. But seeing as Nexus is limited to such a small number of devices, I don't personally feel you can consider that "stock". CM is AOSP based, and at one time considered by many to be close to a pure AOSP experience. But those days are long gone, and there are so many proprietary CM features and apps now, you can't even begin to consider this "stock" by any means.
---------- Post added at 03:36 PM ---------- Previous post was at 03:22 PM ----------
_salguod said:
My goal would be to simply get to stock Lollipop or Marshmallow and have a stable, functional tablet that I don't have to tweak or mess with much. I'd also like to be able to go back if it proves too buggy. Is that feasible, or is rooting plus upgrading pretty much something that will require constant maintenance and tweaking?
Click to expand...
Click to collapse
What you are asking for is CM12 or CM13 (LP or MM) or one of the CM based ROMs. Those are really your only choice when it comes to anything past KK on this device. The CM ROMs are are very stable at this point. You might run into an obscure bug, but to be honest, its less laggy and overall a much better experience than the official Samsung TouchWiz ROM. And if you want to be free of Samsung bloat, CM definitely does that as well.
Tweak or maintain? You don't have to do anything after flashing the ROM, if you don't want to. You can decide to update to newer nightly CM builds from time to time, but that is completely optional. And to be honest, even CM13 is so stable at this point, that the nightly updates don't really change much of anything.
Go back? That's a breeze. Just do a backup in TWRP custom recovery before flashing a ROM, and you can restore to that backup (basically a snapshot of your existing configuration).
_salguod said:
If it is possible, can someone point me to a how to for complete newbies?
Click to expand...
Click to collapse
Honestly, just searching and reading are your best friend. You'll learn a lot more that way, than folk spoon-feeding you the info. The process isn't really all that hard. There may be a lot of esoteric lingo, but you can easily Google or use the XDA site search to find out what those terms mean. And once you've gone through the process, you'll likely be happy for the learning experience.
XDA is a wealth of information, for those willing to take the time to learn and search. All the answers you want are here in one form or other. Difficult to wade through at first, I'll agree with that. But all of us here had to go through the same thing at one time or other.
Its really hard to help someone when they say is "I'm a newb, tell me how to do this". Make a lot more sense for you to just dive in, then come back here with some specific questions, which we will gladly answer.

it would help to know what version OS you're running and the build #.
I rooted my tablet late last year (bought it in May 2015). Wasn't hard to do after some reading. Knox is still good too...1 yr warranty will be over soon.

Thanks all, I appreciate it. I've been doing some more digging to try to learn what everything means so I might know what I'm talking about. I started with the Lifehacker rooting guide (I can't post links yet, add this to lifehacker dot com: /5789397/the-always-up-to-date-guide-to-rooting-any-android-phone) and their how to flash a ROM guide (/how-to-flash-a-rom-to-your-android-phone-30885281) as well. Let me know if those aren't good places to start. I've also read through the CyanogenMod how to for the 8.4, which seems pretty thorough.
I definitely appreciate the push to search and learn, but it can feel like drinking from a firehose. Most "how to" posts are written assuming the reader knows the terminology and every post I read means Googling a half a dozen terms to understand it. For example, I have no idea what the Knox flag is or why I'd care if it got triggered. I don't care about the warranty flag, I'm past the 1 year mark so it doesn't really matter, right?
When I said "stock" I was referring to stock out of the box Android, not stock Samsung. Stock Samsung means staying with KitKat which I'd rather not do. My phone is a Motorola Droid Turbo, which I think is pretty close to stock Android Lollipop, so that I'm familiar with that.
However, I think I'm seeing that going stock Android isn't necessarily possible, or rather, other ROMs are easier to come by. Cyanogenmod seems to be the most popular and sounds very stable, I'll likely try that.
So, I don't need to root in order to flash a new ROM. What's unclear is do I need to do anything special to make sure I can go back to the out of the box Samsung KK that I have now in case I really screw it up or just don't like it and want to go back? Will the process of installing Cyanogenmod wipe my device (apps, files, accounts, data, etc.?
Any other surprises that a guy who has never done this might want to know before going in?
Thanks again for your patience and help.

I forgot to mention, I've got the wifi model, T-320. It's running 4.4.2, build number KOT49H.T320UEU1AOC1.

Well you have a number of choices for your T320 (WiFi), Sadly nonmof those stock. Since Samsung has never seen fit to ever giving us one. For me the Samsung (e.g. Vender ROMs), were always the 'Stock' ROMs. 'Pure' ROMs (al-la Nexus), are clearly Custom ROMs.
The best, and quickest way to learn how to update from Stock to Custom would be to hit up YouTube for a few short Vids on the subject.

_salguod said:
I've been doing some more digging to try to learn what everything means so I might know what I'm talking about. I started with the Lifehacker rooting guide (I can't post links yet, add this to lifehacker dot com: /5789397/the-always-up-to-date-guide-to-rooting-any-android-phone) and their how to flash a ROM guide (/how-to-flash-a-rom-to-your-android-phone-30885281) as well. Let me know if those aren't good places to start. I've also read through the CyanogenMod how to for the 8.4, which seems pretty thorough.
Click to expand...
Click to collapse
Those aren't bad general guides, to just introduce you to the basic concepts and terms. Just keep in mind that every different Android device has its nuances, which vary by manufacturer and over time (from one device to another - even from the same manufacturer). So you'll be referring back to Tab Pro 8.4 specific guides eventually.
_salguod said:
I have no idea what the Knox flag is or why I'd care if it got triggered. I don't care about the warranty flag, I'm past the 1 year mark so it doesn't really matter, right?
Click to expand...
Click to collapse
Basically, if you don't know what the Knox flag is, then it probably doesn't matter.
The longer story, Knox is a enterprise mobile solution made by Samsung. If you company doesn't use Knox (and you don't use your device for work), you don't need it. The huge majority of folks will never need Knox or want it.
You're right, that if the warranty is expired, the warranty flag doesn't matter. And honestly, I rooted my device while it still had a valid warranty. I'd rather have a device that I can use how I wish, and install what software I want (especially if Samsung isn't going to support it with updates) and warranty is a secondary concern, at most.
_salguod said:
What's unclear is do I need to do anything special to make sure I can go back to the out of the box Samsung KK that I have now in case I really screw it up or just don't like it and want to go back?
Click to expand...
Click to collapse
Once you install TWRP custom recovery, you can make a backup of the current Samsung TouchWiz KK ROM; and revert to that if needed or desired.
But honestly, you won't want to go back. CM runs faster and smoother, with no Samsung bloat. You won't want to go back to the crappy TouchWiz ROM, that is 2 generations (Android versions) obsolete.
But it is a good idea to have a backup, in case flashing CM doesn't go right the first time, and the device won't boot.
_salguod said:
Will the process of installing Cyanogenmod wipe my device (apps, files, accounts, data, etc.?
Click to expand...
Click to collapse
You will absolute want to wipe user data when installing CM. Not doing so will likely cause major bugs and/or failure to boot. This is the general rule whenever flashing a new ROM. Although for similar ROMs (such as minor CM updates) you can try to keep user data. This is called a "dirty flash".
You can backup a lot of your data before flashing CM:
Apps: After root, you can use the app Titanium Backup (highly recommended) to backup apps and app data
Accounts: Titanium can backup a lot of this stuff, as well. Depends on what you are talking about, specifically.
Files: just move them to SD card or your computer. Or use a cloud solution (there are many)
You should always be backing up your data, anyway, if its important to you.

_salguod said:
I forgot to mention, I've got the wifi model, T-320. It's running 4.4.2, build number KOT49H.T320UEU1AOC1.
Click to expand...
Click to collapse
Same firmware as what I had prior to rooting it.
The cyanogen articles give a good rundown on how to install it. The only thing that I'm not sure about is whether getting the sdcard to be formatted/recognized is still an issue or not.
When last I checked back in Feb. it seemed like that was still unresolved. I have a 64gb card and getting it to be read by CM13 was absolutely critical. So any move to CM13 was postponed.
Running Kitkat is fine for me...after rooting it, I uninstalled/froze a lot of software incl. a lot of Samsung crap that was eating the battery. The battery is my only complaint with the tablet.

AndroidPrince1 said:
The cyanogen articles give a good rundown on how to install it. The only thing that I'm not sure about is whether getting the sdcard to be formatted/recognized is still an issue or not.
When last I checked back in Feb. it seemed like that was still unresolved. I have a 64gb card and getting it to be read by CM13 was absolutely critical. So any move to CM13 was postponed.
Click to expand...
Click to collapse
The SD card issue on CM13 was solved in early March. It was holding me back as well (stayed on CM12.1) , until I saw it was solved. Now I've been using CM13 for over a month. My 64GB card works great with CM13.
AndroidPrince1 said:
Running Kitkat is fine for me...after rooting it, I uninstalled/froze a lot of software incl. a lot of Samsung crap that was eating the battery. The battery is my only complaint with the tablet.
Click to expand...
Click to collapse
If you flash CM, you'll see its a lot smoother and snappier, especially on the home screens, app drawer, etc.

Thanks all, I plan on biting the bullet some time soon. Too much other stuff on my plate (like car repairs, etc.) so it'll have to wait for a bit. I'll check back in when I do. I'm looking forward to it.

redpoint73 said:
The SD card issue on CM13 was solved in early March. It was holding me back as well (stayed on CM12.1) , until I saw it was solved. Now I've been using CM13 for over a month. My 64GB card works great with CM13.
If you flash CM, you'll see its a lot smoother and snappier, especially on the home screens, app drawer, etc.
Click to expand...
Click to collapse
Good to know on the sdcard thing...looks like I'll have to read up again on how to do.
Thanks for the note.

_salguod said:
What's unclear is do I need to do anything special to make sure I can go back to the out of the box Samsung KK that I have now in case I really screw it up or just don't like it and want to go back?
Click to expand...
Click to collapse
BTW, you can always restore your device to 100% stock (Samsung) by downloading the firmware from sammobile.com/firmwares and flashing it using Odin. If you get into trouble, this will help get you back out.
But since flashing CM13 nightlies is relatively easy, I don't think you'll have any serious trouble, just the normal learning curve.
I've had my SM-T320 on Cyanogenmod since the day after I bought it in 2014 and never looked back :good:

CafeKampuchia said:
BTW, you can always restore your device to 100% stock (Samsung) by downloading the firmware from sammobile.com/firmwares and flashing it using Odin. If you get into trouble, this will help get you back out.
But since flashing CM13 nightlies is relatively easy, I don't think you'll have any serious trouble, just the normal learning curve.
I've had my SM-T320 on Cyanogenmod since the day after I bought it in 2014 and never looked back :good:
Click to expand...
Click to collapse
I don't see any US firmwares on the sammobile.com site. Am I looking in the wrong place?

_salguod said:
I don't see any US firmwares on the sammobile.com site. Am I looking in the wrong place?
Click to expand...
Click to collapse
Cellular South is the US firmware for some reason.

I'm trying to load the latest CM 13.0 nightly this morning and running into issues.
I'm following the install instructions on the CM website and the loading of a custom recovery is failing at step 7. I get the start of the blue bar on my tablet, but I get this error in the command prompt:
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...​
I've tried twice with the the factory cable and a third time with an alternate cable same result.
How do I fix that?

I should mention that I'm working on a Windows 10 computer.

[Q] M8 SIM problem, cycles on/off

Good day,
I've had my M8 for a couple years with no issues. A couple weeks ago it started disconnecting data and calls.
I noticed the SIM state keeps changing (i.e. unknown, ready) and cycling back and forth with the message "preparing SIM card".
If I let the phone sleep a bit, airplane mode will often show "turning off" and greyed out.
Tried a new SIM, no change.
Restored an earlier NAND, saved before the problem showed up, no change.
Was on the phone with the network provider (straight talk), no change.
Aside from running TWRP it's still the original VZW version Kitkat 4.4.2
I'm not sure how to trouble shoot this. If it's hardware, firmware?
Just wondering if anyone has encountered the issue. I read a couple posts elsewhere, but no insights.
Thanks

You have the M8 right? as this section if specific to the M8s (a different device from the M8). I know it's a bit confusing (not crazy about the forum structure on that note).
If so (M8), then it sounds similar to the guy in this thread: https://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-sim-emergency-calls-t3836108
Not the first guy (who replaced the screen) but the 2nd post (which happened spontaneously).
Besides the thing I suggested in that thread (Scotch tape on SIM trick, and/or flashing RUU - in your case Verizon only!) I don't think there is too much that can be done, as it might be a hardware failure.

redpoint73 said:
You have the M8 right? as this section if specific to the M8s (a different device from the M8). I know it's a bit confusing (not crazy about the forum structure on that note).
If so (M8), then it sounds similar to the guy in this thread: https://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-sim-emergency-calls-t3836108
Not the first guy (who replaced the screen) but the 2nd post (which happened spontaneously).
Besides the thing I suggested in that thread (Scotch tape on SIM trick, and/or flashing RUU - in your case Verizon only!) I don't think there is too much that can be done, as it might be a hardware failure.
Click to expand...
Click to collapse
Thanks for the reply. I'll try the tape trick. Flashing a newer RUU is an option. Re-flashing the firmware is something I am going to try.
I did read another post that did that, and no-joy. I'll keep poking around. For expedience I bought a LG G6 today, new. The US cell version unlocked. I will say the HTC M8 feels more solid still.
I should mention that Wifi, and bluetooth work fine. I can re-establish call/data connection temporarily with a reboot. Oddly, the the connection/SIM seems more stable at my office than at home. Makes me wonder if it's in the network, or it aggravates the issue.
PS - thanks for clarifying the forum, I missed the "s" in the title. I do have the M8 only.
I'll post, if I fix anything.

Cremnomaniac said:
Flashing a newer RUU is an option. Re-flashing the firmware is something I am going to try.
Click to expand...
Click to collapse
Certainly can't hurt to install a newer RUU. If nothing else, it's typically good from a security perspective to have the phone as updated as possible.
Something I eluded to earlier, but just to be clearer: Make sure you only try RUUs specific for Verizon M8. Those RUUs can be found here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
RUU for any other version M8 are not compatible with your device. Flashing them will result in a radio brick!

redpoint73 said:
Certainly can't hurt to install a newer RUU. If nothing else, it's typically good from a security perspective to have the phone as updated as possible.
Something I eluded to earlier, but just to be clearer: Make sure you only try RUUs specific for Verizon M8. Those RUUs can be found here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
RUU for any other version M8 are not compatible with your device. Flashing them will result in a radio brick!
Click to expand...
Click to collapse
Thanks for heads up. I do have all the appropriate RUU's already 4.4.4 to 6.0 S/on and S/off
I did a lot of research before, but at some point I got busy and never followed through. I have another LG phone here. So now is as good a time as any to update. I still enjoy my M8. Hardware trouble shooting is beyond my skill level, but does anyone do it?