Develop Bugs

Need Help, No Service, after installing CyanogenMOD 10.1

No Service, after installing CyanogenMOD 10.1
Tried following the steps outlined in this post but do not feel totally comfortable in saying I did it correctly as that post is not specifically for Incredible 2's and the instructions are not very clear.
I can obviously follow instructions, as I have gotten this far issue free. But his foggy instructions and the lack of files specific to this issue for Dinc2's make fixing this a little tricky.
Has anyone else seen this issue on a dinc2?

No other users have had loss of Cell service (No reception, zero bars) from Cyanogenmod 10.1?
Or said differently, Borked Radio's...

Not that I know of
One ROM @ a time....VIA ELECTRICITY

Last night I did a Factory restore from within Clockwork, then downloaded an un-rooted stock rom from this site (very bottom rom) dropped it on the root of the sd card and renamed it to PG32IMG.zip and rebooted to install the stock rom. (This will NOT remove s-off, see results of the reinstall picture below)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After this the phone rebooted a few times and I figured it was just not working so I went to bed, then woke up did some stuff and then went to supper with the family. after we got home I picked up the phone and noticed that the phone had reception bars, so I did *228 and it started to initiate the activation and it actually started the process, but I hung up.
I then proceeded to re install clockwork recovery. after this was installed, the phone just boots over and over, did this for about 15 minutes before I pulled the battery and re initiated a Factory Reset from within clockwork. after rebooting from this factory reset, there was no reception again. so I then pulled, from the vzw stock zip, the file named recovery_signed.img and placed it into the same directory as my adb & fastboot files, pulled the battery from the phone, rebooted into hboot, chose fastboot and ran:
Code:
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
After boot loader rebooted, I selected bootloader to get back to Fastboot, chose recovery, rebooted into phone which was once again re-boot looping. Will try more after work tomorrow, too tired right now.

Last night, cleared the caches out several times each, then factory restored twice in a row, then installed clockworkmod, reinstalled the "andyBONESTOCK_5.10.605.9" image, then, re installed the radio image "6.01.605.05 OTA 1.09.01.0312" twice in a row. Still had no service.....
Went to work, got home and the friggin thing has service.... wtf
So I reboot the phone and now it has no service..... Anyone have any ideas?

Problems solved. Must have had a corrupted radio file. Found a different source, installed, all is good.

which radio, from where, link?
Akinraze said:
Problems solved. Must have had a corrupted radio file. Found a different source, installed, all is good.
Click to expand...
Click to collapse
I tried the .320 radio here: http://forum.xda-developers.com/showthread.php?t=1134451
and it bricked my phone, HBOOT (revolution), said invalid, then installed it and the phone was bricked. Took forever to recover even HBOOT and then revolution and that was reset plus Android SDK, adb.
Used ChillyBean's 10.1 , May 9 13 build date, plus Kernel from here:
http://forum.xda-developers.com/showthread.php?t=2315062
But the audio for phone calls can give no sound at all. Bugs seem to be in services, like one audio driver doesn't release the audio, or turn it off so it cannot be turned on when the phone call is made, or some audio routing problem from the call (radio) to the audio HW (any, speaker, mic, bluetooth, headset).
I can tell it is this because if I turn audio on/off before the phone call enough times I get back the actual call in progress audio.
I'm using 0.312 but the last thing to try is the radios but the ones at the first link are at minimum corrupted.
I also don't get the overall source tree for CM10.1, I thought you had to have a build for specific HW vs. taking just the nightly? Is there a build tree for DINC2 from the CM10.1 nightlies?
The current no sound during phone call is a real bug and not specific to my HW, something isn't releasing or turning on or routing the audio via the 3GGP/CDMA call path. Dunno the actual path in HW for the voice communications.
This should be in dev. thread but the system won't let me post due to newbie status.

Well, I eventually got only a few roms to work without issues to my liking.
The one I am using right now, is the one I first got my phone back up running issue free, that is Team Venom Presents ViperINC 1.3.1 Sense4.1...
The radio inside the ics firmware listed at the very top of the 1st post for Team Venom Presents ViperINC 1.3.1 Sense4.1 is where you get the ics firmware.
I am almost 100% sure the Android Harpoon Repository has the radio I am using now as well as several other roms and kernals, all of which have had NO ISSUES for all that I have tried.
Hope you get things working correctly. and make SURE, to correctly get the radio and or Kernal files installed correctly, you simply rename the firmware ZIP file, that has all the .IMG files inside, to be named PG32IMG.zip and place it in the ROOT of your sd card and reboot to it. do this AFTER you have installed the rom. And YES, it takes some time to get things working corectly immediately after installing the firmware PG32IMG.zip file, so BE PATIENT, go take a poop, eat a meal, get some poontang. when you come back, all should be good.
And though it may seem stupid... Put the back cover on your phone, so your antenna connections are complete.
The when your all done, things show promise, connect your phone to your PC and open windows explrer and delete that PG32IMG.zip so it doesnt repeatedly install over and over.

Thanks Akinraze
Akinraze said:
Well, I eventually got only a few roms to work without issues to my liking.
The one I am using right now, is the one I first got my phone back up running issue free, that is Team Venom Presents ViperINC 1.3.1 Sense4.1...
The radio inside the ics firmware listed at the very top of the 1st post for Team Venom Presents ViperINC 1.3.1 Sense4.1 is where you get the ics firmware.
I am almost 100% sure the Android Harpoon Repository has the radio I am using now as well as several other roms and kernals, all of which have had NO ISSUES for all that I have tried.
Hope you get things working correctly. and make SURE, to correctly get the radio and or Kernal files installed correctly, you simply rename the firmware ZIP file, that has all the .IMG files inside, to be named PG32IMG.zip and place it in the ROOT of your sd card and reboot to it. do this AFTER you have installed the rom. And YES, it takes some time to get things working corectly immediately after installing the firmware PG32IMG.zip file, so BE PATIENT, go take a poop, eat a meal, get some poontang. when you come back, all should be good.
And though it may seem stupid... Put the back cover on your phone, so your antenna connections are complete.
The when your all done, things show promise, connect your phone to your PC and open windows explrer and delete that PG32IMG.zip so it doesnt repeatedly install over and over.
Click to expand...
Click to collapse
Your post helped me so much. I've been working on the phone all day because it said there was no service. Turns out since I was working on it without the back, since I needed to go into fastboot so many times, the antenna wasn't completed. The signal in my house turns out to be just weak enough for it to barely show up with the back on. Thanks again.

Found my own fix
http://teamuscellular.com/Forum/topic/7584-cyanogen-no-service-fix/

Video and/or step by step firmware upgrade instructions available?

So let me explain the scenario; I have a T-Mobile M9 that's S-Off, running Venom, and wanted to update the firmware from 1.32 to 2.7. I had done this in late July and got the success, and the firmware was running fine, but eventually the phone decided to just shut off on me, and the only way to turn it back on was via forced reboot. For the two weeks after that I had tried just about every method I read on Sneakyghost's post on the subject (I did an RUU, changed to superCID and flashed 2.10, did the full wipe and no wipe firmware) and every single time if I updated to anything newer than what was on my M9 originally it would, inevitably, do that thing where it became unresponsive after a while.
Since this seems to be a problem that only I'm having, I assume it's something I have to be doing wrong. With that in mind, is there any sort of video that has been made or really, really simple and thorough step by step instructions that could guide me through the process in a detailed way? I hate that I have to ask this, but I feel like I've done my homework and tried several different methods, and all of them have failed. I have HTC sync installed, I've tried on two different computers, I've done everything. I even flashed back 1.32 in the exact same way that I flashed 2.7, and as soon as I put it back to the old one it immediately solves the problem. Without fail putting the new firmware on has made my phone do this at least once within two days of installing, and then multiple times after that (I must've tried this about four or five separate times over three weeks). The obvious problem here is that the phone is completely unresponsive, which means that if it does this overnight my alarm doesn't work. Not to mention the missed calls and annoyances that occur when it happens throughout the day.
I just want to be able to experience the new firmware. Because right now I still have to deal with a (relatively) crappy camera experience and a phone that overheats constantly. I'm also really worried that when the M update comes out it may force me to have a newer firmware, and if I can't do it correctly I'll be out of luck.
So if anyone could help it'd be so very appreciated, either by telling me something I could have done wrong (I flashed the firmware via fastboot method both over viper and later over a stock Sense build). I also have the newest radio, so I literally have no idea what I could be doing wrong at this point, but I hope someone does. Again, thanks in advance.

guyverzero said:
So let me explain the scenario; I have a T-Mobile M9 that's S-Off, running Venom, and wanted to update the firmware from 1.32 to 2.7. I had done this in late July and got the success, and the firmware was running fine, but eventually the phone decided to just shut off on me, and the only way to turn it back on was via forced reboot. For the two weeks after that I had tried just about every method I read on Sneakyghost's post on the subject (I did an RUU, changed to superCID and flashed 2.10, did the full wipe and no wipe firmware) and every single time if I updated to anything newer than what was on my M9 originally it would, inevitably, do that thing where it became unresponsive after a while.
Since this seems to be a problem that only I'm having, I assume it's something I have to be doing wrong. With that in mind, is there any sort of video that has been made or really, really simple and thorough step by step instructions that could guide me through the process in a detailed way? I hate that I have to ask this, but I feel like I've done my homework and tried several different methods, and all of them have failed. I have HTC sync installed, I've tried on two different computers, I've done everything. I even flashed back 1.32 in the exact same way that I flashed 2.7, and as soon as I put it back to the old one it immediately solves the problem. Without fail putting the new firmware on has made my phone do this at least once within two days of installing, and then multiple times after that (I must've tried this about four or five separate times over three weeks). The obvious problem here is that the phone is completely unresponsive, which means that if it does this overnight my alarm doesn't work. Not to mention the missed calls and annoyances that occur when it happens throughout the day.
I just want to be able to experience the new firmware. Because right now I still have to deal with a (relatively) crappy camera experience and a phone that overheats constantly. I'm also really worried that when the M update comes out it may force me to have a newer firmware, and if I can't do it correctly I'll be out of luck.
So if anyone could help it'd be so very appreciated, either by telling me something I could have done wrong (I flashed the firmware via fastboot method both over viper and later over a stock Sense build). I also have the newest radio, so I literally have no idea what I could be doing wrong at this point, but I hope someone does. Again, thanks in advance.
Click to expand...
Click to collapse
instructions are here >> http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
use the sdcard method and the DE RUU or the T-mobile RUU and your phone should work fine

clsA said:
instructions are here >> http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
use the sdcard method and the DE RUU or the T-mobile RUU and your phone should work fine
Click to expand...
Click to collapse
Would restoring my nandroid after flashing that RUU cause anything to go wrong?

guyverzero said:
Would restoring my nandroid after flashing that RUU cause anything to go wrong?
Click to expand...
Click to collapse
it's always better to start fresh after the RUU

Nope, it's doing the same thing again. This is my GSam from last night.
Now, let me stress that I did everything clean. RUU, did a clean setup, clean venom flash, etc. I didn't restore any settings. I don't know what to do, as the phone is completely normal under 1.32. Oh and I flash 1.32 in the same exact way I do 2.7 as well, there's no difference
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC One M9 using Tapatalk

How to Get Advanced Calling Working

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was able to get advanced calling back on my line. I was currently on Andy Bone's Fluent Rom but I lost my advanced calling feature when I first switched to Neo's Adrenaline Rom.
1) Log into your phones account on Verizon Wireless website, go to manage my apps and features and turn off advanced calling on your line.
2) The message from Verizon says to wait 15 minutes to see the changes take effect. During this time, I downloaded Dotatt's RUU.
3) RUU'd back to stock and then enabled the advanced calling feature on the PHONE
4) I did not restart my phone because it was downloading the OTA (2.xx to be specific). The OTA restarted the phone.
5) Advanced calling was back! Then I took the next OTA to 3.xxx
6) Advanced calling was still enabled, after the 3.xxx OTA, So then I installed TWRP/Root (all in one restart)
7) I then created a nandroid backup of my stock rooted configuration.
8) I then installed Andybone's deodexxed 5.1.1 Rom. (I wanted to install Fluent but I could not find confirmation that it works well with the new FW)
9) Now my phone is stock 5.1.1 with Xposed Modules installed and is running flawlessly with Advanced calling!!
The only reason I cared for advanced calling was because it would cut out my streaming music from Plex and then it would have trouble getting reconnected, now it never disconnects so when I receive calls i no longer have any issues.
Obviously your mileage may vary but I think this is an effective method of getting advanced calling back without having to send your phone into HTC.

Thanks for the post, I also lost advanced calling after a rom flash and have tried a similar process with no luck. I'll try again following your exact steps when i get the chance and report back.
Edit: No luck for me, followed the above steps exactly and still no advanced calling. I'd pretty much done the same before but just rebooted before applying the 1st OTA, tried again in the hopes that letting the ota install first would kick something in. Seems like some folks lose Volte permanently once it's gone with the only known resolution getting a replacement device. Guess i'm one of the lucky ones.
I may play with this some more but am giving up hope, and have not gotten very far with Verizon online support either. They just stated everything looked fine on their end after "looking into it" then closed the ticket, and just getting to that point took 3 different chat sessions with 3 different reps. I asked the last one I chatted with if this must be an issue with my specific device and if it should be replaced, to which the answer was a generic "well everything looks good so it should be working. if you have any more issues call 1-800-whatever" then they ended the session.

I was worried I had lost VoLTE for good, thanks for this. Worked like a charm! I can't stand not having data while in call. lol.

PrizmaticSmoke said:
Thanks for the post, I also lost advanced calling after a rom flash... have not gotten very far with Verizon online support either.... 3 different chat sessions with 3 different reps.
Click to expand...
Click to collapse
...and this is why Verizon works so hard to lock their phones down. Someone breaks a feature by loading non-VZW firmware, expects VZW to provide support for the phone, and gets mad (!!!) when VZW can't fix an issue of the user's own making.

mike.s said:
...and this is why Verizon works so hard to lock their phones down. Someone breaks a feature by loading non-VZW firmware, expects VZW to provide support for the phone, and gets mad (!!!) when VZW can't fix an issue of the user's own making.
Click to expand...
Click to collapse
You got me there, though i wouldn't really say that i'm "mad (!!!)" about losing VoLTE lol, just at VZW's support in general. I did my (very thorough) research before modifying anything on my device, and am not new to modifying devices or software. I was fully aware of the risks involved (including that some folks were reporting loss of VoLTE after device modifications) and pulled the trigger anyways, as the benefits outweigh the possible risks IMO.
But the truth is they don't know why it's broke, and if it could be fixed simply by sending me a new sim or a reconfiguration on their end of the network or something then I wanted to at least investigate. But their support for me has just been plain unhelpful in every way on numerous items, unless you like having scripted responses that aren't even relevant to your question/issue regurgitated to you at every turn.
And why do you have any sympathy in this scenario for the multi-billion dollar mega-corporation whose restrictions are what brought many of us here in the first place anyways? Maybe just playing devil's advocate?

If you're not mad, you shouldn't use the mad emoticon. If you break it, you own both pieces. It's unreasonable to expect them to know or spend any time trying to figure out why modified firmware breaks things. Can you point to someone who's always had stock firmware who's had VoLTE issues which VZW hasn't been able to fix?

mike.s said:
If you're not mad, you shouldn't use the mad emoticon. If you break it, you own both pieces. It's unreasonable to expect them to know or spend any time trying to figure out why modified firmware breaks things. Can you point to someone who's always had stock firmware who's had VoLTE issues which VZW hasn't been able to fix?
Click to expand...
Click to collapse
Nope. Didn't say I could.

more M9 Advanced Calling
If you know for sure that Advanced Calling is enabled on your line and it's not working now:
Just discovered that after 100% stock factory reset, then enable Advanced Calling on the phone, it will work perfectly
on first request. The feature will continue to work fine afterwards if you do not ever use TWRP recovery to do a complete
wipe of everything available to wipe.
To flash custom roms and nandroids (and have Adv. Calling still functioning) , only do the "Swipe to Factory Reset".
Then flash your favorite custom stuff.
Doing more wipe than that ruins the phone for Advanced Calling until there's been another factory reset done
with stock recovery and kernel.

michaelbsheldon said:
If you know for sure that Advanced Calling is enabled on your line and it's not working now:
Just discovered that after 100% stock factory reset, then enable Advanced Calling on the phone, it will work perfectly
on first request. The feature will continue to work fine afterwards if you do not ever use TWRP recovery to do a complete
wipe of everything available to wipe.
To flash custom roms and nandroids (and have Adv. Calling still functioning) , only do the "Swipe to Factory Reset".
Then flash your favorite custom stuff.
Doing more wipe than that ruins the phone for Advanced Calling until there's been another factory reset done
with stock recovery and kernel.
Click to expand...
Click to collapse
Has this been tried more than once? Just curious.
Sent from my HTC6535LVW using XDA Free mobile app

meandg5 said:
Has this been tried more than once? Just curious.
Sent from my HTC6535LVW using XDA Free mobile app
Click to expand...
Click to collapse
3 M9's on our family account: all 3 S-0ff and rooted.
Only 1 had HDVoice-Advanced Callling working correctly. Could not nandroid the
working system to one of the other phones with no HDVoice to get them running.
Did process above and got the 2 that weren't working to function correctly.
Took the original one whose HDVoice was good, did nandroid of it, did FULL MERCILESS
wipe on it and restored the nandroid. HDVoice no longer worked anymore.
Used dottat's files to restore to factory stock, got HDVoice working instantly,
then nandroided the previous backup that did not yield working HDVoice before, works again.
Now HDVoice works fine on all 3 devices. Proved to me that full wiping took away HDVoice.

So, I've lost VoLTE/Advanced calling on my m9. Not exactly sure when or what caused it. Not all that concerned. I have tried everything from RUU all the way back to 1.33.x and let it do the OTA updates up to MM as well as full wipes from stock recovery at every stage of the process. Or not wiping at all. If there is anything else someone would like me to try, I am more than willing to give it a shot. Would be nice to find a solution even though there probably isn't one except getting a replacement.

jsaxon2 said:
So, I've lost VoLTE/Advanced calling on my m9. Not exactly sure when or what caused it. Not all that concerned. I have tried everything from RUU all the way back to 1.33.x and let it do the OTA updates up to MM as well as full wipes from stock recovery at every stage of the process. Or not wiping at all. If there is anything else someone would like me to try, I am more than willing to give it a shot. Would be nice to find a solution even though there probably isn't one except getting a replacement.
Click to expand...
Click to collapse
Did you remove it from your account and then ruu and factory reset and attempt to add it from the phone again? If you did that exactly and nada it's time for replacement.

dottat said:
Did you remove it from your account and then ruu and factory reset and attempt to add it from the phone again? If you did that exactly and nada it's time for replacement.
Click to expand...
Click to collapse
Yep, tried that also. I've tried everything that has been posted and maybe even some other things. If there is anything off the wall that you want me to try, I'm game. Other than that, I'm just gonna keep it as I use CandySix which doesn't support VoLTE anyway and plan on getting m10 once it's out in a couple months.

jsaxon2 said:
So, I've lost VoLTE/Advanced calling on my m9. Not exactly sure when or what caused it. Not all that concerned. I have tried everything from RUU all the way back to 1.33.x and let it do the OTA updates up to MM as well as full wipes from stock recovery at every stage of the process. Or not wiping at all. If there is anything else someone would like me to try, I am more than willing to give it a shot. Would be nice to find a solution even though there probably isn't one except getting a replacement.
Click to expand...
Click to collapse
I've had two of my friends follow my instructions to the letter and both got Advanced Calling back.
I read somewhere that the full wipe is what causes the Advanced Calling to break (I'm 70 percent sure I read that somewhere and I am too lazy to find it)
So when you are trying to get it back via RUU and everything I would refrain from a "Full Wipe" and use "Factory Reset"
If all else fails send it to HTC

Threefifty said:
I've had two of my friends follow my instructions to the letter and both got Advanced Calling back.
I read somewhere that the full wipe is what causes the Advanced Calling to break (I'm 70 percent sure I read that somewhere and I am too lazy to find it)
So when you are trying to get it back via RUU and everything I would refrain from a "Full Wipe" and use "Factory Reset"
If all else fails send it to HTC
Click to expand...
Click to collapse
At what point did you Factory Reset? Or not at all? I am going to try again step by step. I just removed Advanced Calling via verizonwireless and downloaded dottat's ruu version 1.33.605.15 I am waiting for the 15 minutes to be up and I will install RUU via SDCard method.
Any other tips?

So, no luck with getting it working yet. I did the steps exactly, but no luck. I'm still not done though. Like I said, It doesn't really concern me that it's not working, but I'll keep trying to see if I can find a way to bring it back to life in case others have the issue.

jsaxon2 said:
At what point did you Factory Reset? Or not at all? I am going to try again step by step. I just removed Advanced Calling via verizonwireless and downloaded dottat's ruu version 1.33.605.15 I am waiting for the 15 minutes to be up and I will install RUU via SDCard method.
Any other tips?
Click to expand...
Click to collapse
I never really factory reset throughout my process.
However, I did RUU from the computer, not from SD card. I don't believe that is the case but if you're trying to replicate my steps exactly that's the only difference.

mobile installer application popup restarting phone?

About once a week, not really sure on the frequency, (if I notice the popup) it says it rebooting the phone with two toggles on the bottom of the box. (box and lettering all in black and white) Your choice on the toggles is reboot or later. Today I push later and it it popped up twice more. But on the third time, there was not toggles and was doing a count down for reboot.
Anyway, before it rebooted, I pulled down the notifications and and found the notification and did a long press on it and then went into info. I then it looked like I was in settings with two choices there. (when on this settings, there was not back button to see were I was at in settings) To block notifications with on or off and the other doing something with quite mode. I turn off notifications and minimized the box. After it rebooted, the box was still minimized until wanted to bring it back up in the screen, it disappears. Anyone know what this is??? or know how to figure out what's doing it?
Stock Sprint Note 4 running 5.1.1 software Ok1 with hotspot hack (why I'm not running current software)

Open root browser and see if you have this folder: /carrier/ItsOn
If so, you may also have this file in dalvik (i think that's the proper location for Lollipop but you could search keyword itson) : /data/dalvik-cache/carrier @itson@[email protected]@classes.dex
If your ROM is fully stock, you may have another folder at /system/vendor/ItsOn. If so, look inside that folder for resource zip. Extract that zip and look in the folder and file install locations then browse to those in your phone's folders and delete all that correspond to that mapping.
If you have those, delete all you find and reboot. Hopefully that cures the random reboots.
If this applies, ItsOn has a bootstrapper that tries to install itself. If you have a custom kernel, it cannot complete this process but will try repeatedly to complete that failed setup process, prompting you continually reboot. If you were to factory reset, the prompts would most likely be more persistent.
If you flash a stock tar, then flash custom ROM and don't wipe internal memory, ItsOn remains unless developer has a script in place to remove that from root of your carrier folder.
Sent from my SM-N910P using Tapatalk

Thanks for the info. Phone is not rooted, bone stock with the exception of the hotspot hack.
Only thing I found using File Viewer under Root (/) folder /system/vender/Itson. And it shows nothing is in there and one year old.
I believe all this started when I upgrade Lollipop about one year ago. Was rooted at the time and wanted the newer android. Then I found out I did not need to root to get the hotspot working.

btb601 said:
Thanks for the info. Phone is not rooted, bone stock with the exception of the hotspot hack.
Only thing I found using File Viewer under Root (/) folder /system/vender/Itson. And it shows nothing is in there and one year old.
I believe all this started when I upgrade Lollipop about one year ago. Was rooted at the time and wanted the newer android. Then I found out I did not need to root to get the hotspot working.
Click to expand...
Click to collapse
OK. Check ItsOn status next. Goto /data/local/tmp and look for ItsOn log. It shouldn't get added on boot if you've removed it but last successful bootstrapper log will be present, unless deleted.
FWIW, I don't have random reboots on rooted phone. When I had them, ItsOn was the culprit. I usually clean install, wiping internal memory before and after stock tar but didn't coming from Lollipop.
What I noticed was that ItsOn showed in hidden menu ##data# as NetworkSystemProvider. See before and after wiping internal memory screenshots. I suspect this carried over from Lollipop. Perhaps yours did too?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N910P using Tapatalk

I could not find /data/local/tmp and look for ItsOn log, but I did get into data and the NetworkSystemProvider is there. Got into in and hit button for more settings and little window say "intent sent."
Also under more settings it says two things,
Module 1 is insmoded
Module 2 is insmoded
And at the top, it has a green icon for on button and a blacken icon for the off button. It will not let me do crap there.
Since it's stock, I have done nothing to it. Can't remember how I did the update. My guess since it was rooted, I had to flash OK1 myself but I don't see my stock download from Samsung. I have major memory issues, way more than I should at my age and I have no idea on how I did things......LOL And not even sure what Itson is, only thing I found with quick search a sprint software to add software and updates easily. That would explain the random downloads and install I did not do.
So now what, I need to root my phone to make this go away? Oh, and thanks again for your help. Don't go out or your way to dig further. I'm wanting to upgrade to MM but don't know much about it (rootable or hotspot wise).

The way I got rid of it was to wipe data and internal memory, flash marshmallow stock tar and wipe both again and flash a ROM that has it removed. Dunno but maybe it works the same way with a TWRP backup if you prefer stock with hotspot only?
I can't confirm there's another method or if that's your problem. But my random reboots are gone. FWIW, my log was inactive but had an existing log that dated months back. I only had a few random reboots until I did a factory reset to see if that would help. Once I did that, the reboots were much more frequent. Some boots were resulting in immediate request to reboot again. I had to do something at that point.
I couldn't tell you if updating to marshmallow makes it better but you could still could go back to Lollipop if it didn't.
I dunno if you need to root to make it go away but I can tell you there is hotspot mods for marshmallow. You can go back to Lollipop if you don't like marshmallow.
Sent from my SM-N910P using Tapatalk

Thanks again, guess I'll give marshmallow a try here real soon. Maybe even try a custom rom, never played with any of those. But I getting to where I'll have to do something soon. I feel it's picking up the pace. Then again, new Notes will be coming out soon. We'll see what Samsung brings us. Thanks again.

btb601 said:
Thanks again, guess I'll give marshmallow a try here real soon. Maybe even try a custom rom, never played with any of those. But I getting to where I'll have to do something soon. I feel it's picking up the pace. Then again, new Notes will be coming out soon. We'll see what Samsung brings us. Thanks again.
Click to expand...
Click to collapse
I've had this happen before and the only way I was able to get rid of it was to flash a completely stock tar and let the device provision itself thru initial setup. Others have had luck with the removal of ItsOn, but this has happened on ROMS where ItsOn wasn't even present.

ianmb said:
I've had this happen before and the only way I was able to get rid of it was to flash a completely stock tar and let the device provision itself thru initial setup. Others have had luck with the removal of ItsOn, but this has happened on ROMS where ItsOn wasn't even present.
Click to expand...
Click to collapse
Thanks, I do just that when I decide where to go from here.

GPS Fix Issues

Is anyone with an HTC 10 having any GPS lock issues? I wasnt having issues for months and months of owning my Vzw HTC 10 but just recently I've been unable to get a lock almost always. I see that my phone can FIND satellites it just can't use them.
Currently rooted and s off, stock Rom with twrp.
I've tried resetting agps and refreshing, I've tried switching between Global and CDMA. I'm not really to keen on factory resetting as I'm afraid a. It won't help and b. I'll have to redo all my work with rooting, sunshine, etc. (I could be wrong about that... Forgive me I'm no expert with this stuff, just know enough to follow instructions to get to where I want to be lol)
Does anyone have any ideas or suggestions? I have a hard time believing there's anything actually wrong with my GPS sensor so to speak especially since it can find satellites it just isn't fixing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Launchpadmcqu4ck said:
Is anyone with an HTC 10 having any GPS lock issues? I wasnt having issues for months and months of owning my Vzw HTC 10 but just recently I've been unable to get a lock almost always. I see that my phone can FIND satellites it just can't use them.
Currently rooted and s off, stock Rom with twrp.
I've tried resetting agps and refreshing, I've tried switching between Global and CDMA. I'm not really to keen on factory resetting as I'm afraid a. It won't help and b. I'll have to redo all my work with rooting, sunshine, etc. (I could be wrong about that... Forgive me I'm no expert with this stuff, just know enough to follow instructions to get to where I want to be lol)
Does anyone have any ideas or suggestions? I have a hard time believing there's anything actually wrong with my GPS sensor so to speak especially since it can find satellites it just isn't fixing.
Click to expand...
Click to collapse
I have not had any issues, i am currently on 1.82.605.6 firmware & deodex base.
1. Have you installed a custom kernel?
2. In the locations settings, have you set the location to just GPS? (shouldn't matter anyways)
3. It looks as though you have a software update? i assume you are running santod rom, which should work anyways.
I would just RUU back to stock, it wont break sunshine. you will need to reinstall twrp & superSU after performing the RUU. then test it stock and go from there.
Good Luck

Launchpadmcqu4ck said:
. I'm not really to keen on factory resetting as I'm afraid a. It won't help and b. I'll have to redo all my work with rooting, sunshine, etc. (I could be wrong about that... Forgive me I'm no expert with this stuff, just know enough to follow instructions to get to where I want to be lol)
Click to expand...
Click to collapse
That's no issue.
Simply backup System, boot and User data in TWRP (well, actually you only need UserData. But if you have them all your safe whenever whatever ^^)
Go to advanced wipe and select UserData, Cache, Dalvik.
Don't select Internal Storage/ SD card this would delete all your data you don't want deleted.
So reboot your phone and setup your Google account again.
Sunshine and root and all that stuff will persist.
If it doesn't help you can easily restore UserData only, via TWRP.
but then you will have to try installing a ruu anyway, which will delete ALL your data.

Launchpadmcqu4ck said:
Is anyone with an HTC 10 having any GPS lock issues? I wasnt having issues for months and months of owning my Vzw HTC 10 but just recently I've been unable to get a lock almost always. I see that my phone can FIND satellites it just can't use them.
Currently rooted and s off, stock Rom with twrp.
I've tried resetting agps and refreshing, I've tried switching between Global and CDMA. I'm not really to keen on factory resetting as I'm afraid a. It won't help and b. I'll have to redo all my work with rooting, sunshine, etc. (I could be wrong about that... Forgive me I'm no expert with this stuff, just know enough to follow instructions to get to where I want to be lol)
Does anyone have any ideas or suggestions? I have a hard time believing there's anything actually wrong with my GPS sensor so to speak especially since it can find satellites it just isn't fixing.
Click to expand...
Click to collapse
i am having the same issue, did you find a fix by any chance?

HateSoul said:
i am having the same issue, did you find a fix by any chance?
Click to expand...
Click to collapse
Sadly nothing seemed to fix it. I did manage to again get a GPS fix but only in some places never the places I did when I first got the phone. It seems like the antenna is just weak all of a sudden. But to be honest I stopped working on it because my Verizon htc 10 was stolen shortly after posting this :/ I've got an Unlocked edition coming next week hoping to test the GPS and see if indeed it was my phone or if the areas I was in are the issue or what.