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.
Related
You all likely heard about FreedomPop's new beta this week featuring a "guaranteed 500 MBs of data, 500 text messages, and 200 anytime voice minutes for free each month."
http://www.freedompop.com/byod
Our phone is one of the supported models.
After you sign up, which involves giving them your phone's MEID and getting a new phone number, you're instructed to dial ##786# (which just ends in a dialing error for me), select the "reset" option, and use the MSL that they give you (which may be wrong, btw, so check it) to reset the phone and reboot.
Clarification: OK, so I discovered that the format is as follows for this phone, but I'm looking to avoid it: *#*#786#*#*
I don't want to reset my phone, however, and no one can explain why it's needed. Ting doesn't need it to activate:
https://help.ting.com/entries/25654386-Activating-a-BYOD-Phone-with-a-New-Number
Why does FreedomPop and is there any way around it? Surely there is.
Hmm. I just set up an account, gave them my MEID, updated profile and PRL and downloaded the app and didn't have to do any kind of reset whatsoever.
{
"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"
}
Here are the instructions they sent me
Well it won't let me attach anything grrr
bilgerryan said:
Well it won't let me attach anything grrr
Click to expand...
Click to collapse
I think I've now seen those other instructions, where they say to do a carrier wipe (*#*#72786#*#*), system update, profile update, and PRL update, so I tried that but was met with an immediate roadblock: you can't do those things on CM. So now I have to temporarily go back to a stock ROM. Sigh.
First, can you at least confirm that data will work on 3G? Because that's all I have in my area.
Second, if I do go back to a stock ROM and make the above changes, will a Nandroid of my CM, later restored, wipe out those changes?
rseiler said:
I think I've now seen those other instructions, where they say to do a carrier wipe (*#*#72786#*#*), system update, profile update, and PRL update, so I tried that but was met with an immediate roadblock: you can't do those things on CM. So now I have to temporarily go back to a stock ROM. Sigh.
First, can you at least confirm that data will work on 3G? Because that's all I have in my area.
Second, if I do go back to a stock ROM and make the above changes, will a Nandroid of my CM, later restored, wipe out those changes?
Click to expand...
Click to collapse
Well I am on TouchWiz (Project X) so probably. Idk about restoring a nand as this is my first day on it. 3G works great, seems like it uses Sprints towers (they mention Wimax on the website). So I would say flash back to TouchWiz, set everything up, make a backup and then try restoring your other backup. I would think after you're all set up you should be good because everything is done through their app. Kinda like Groove IP but with real service included.
PS- I didn't even do the carrier wipe
There, these are the instructions I got via email
I ended up going this route to update profile/PRL, and it worked:
http://e4gtcm.blogspot.com/2012/05/temporary-stock-e4gt-from-emmc.html
One unfortunate thing is that when you update profile, it forces a reboot, and when you reboot doing the above you go right back into CWM. So you have to install the ROM again just to get back in to GB so that you can also update the PRL. No doubt there's a better way of going about this, but I don't know what it is.
Anyway, once you've done that, you can intentionally go back to CWM and put CM back on. Nothing is lost in the process.
Could I get some help in figuring out why my epic 4g touch, which was on a Sprint account until 3 days ago.. and working fine... was not able to activate thru freedompop's website.
It said that the device was not supported. Anyone have an idea why this would occur?
Due to MSL-related issues or something else, they rolled back the devices that they're accepting. It is just a beta. As of 4 days ago, this was the list:
http://slickdeals.net/f/6449794-fre...voice-text-data-plans?p=63469084#edit63469084
Believe it or not, Facebook seems to be their primary support outlet, so perusing messages there should give you more current information. If you send them a private message, they're also good about responding. Fortunately, I signed up on the first day (which is not activating, btw), and that must be enough to bless you for later activation, since I only did that this weekend (after our device had been temporarily dropped from the list).
https://www.facebook.com/FreedomPop
rseiler said:
I ended up going this route to update profile/PRL, and it worked:
http://e4gtcm.blogspot.com/2012/05/temporary-stock-e4gt-from-emmc.html
One unfortunate thing is that when you update profile, it forces a reboot, and when you reboot doing the above you go right back into CWM. So you have to install the ROM again just to get back in to GB so that you can also update the PRL. No doubt there's a better way of going about this, but I don't know what it is.
Anyway, once you've done that, you can intentionally go back to CWM and put CM back on. Nothing is lost in the process.
Click to expand...
Click to collapse
Update PRL first.
bilgerryan said:
Update PRL first.
Click to expand...
Click to collapse
Oh, OK, so the order apparently doesn't matter. I might have tried that but I didn't know that the original order would ask for a reboot, so it was too late.
Install backup of Sprint Update app?
I'm hoping to resurrect this thread, but if it doesn't work, I'll start a new one.
I have a Samsung Galaxy S2 SPH-D710 that I'm using on FreedomPop. I've been able to successfully activate it on FreedomPop and get calls, texts, and data on a stock rom. I'd like to use Cyanogenmod 11, but I haven't been able to get the FreedomPop activation to work. I've tried flashing a stock rom, doing a prl and profile update, then flashing CM again, but can't get it to work.
While tinkering with the phone I had an idea: If I backup the Sprint Update app that updates the profile and prl on a stock rom with Titanium Backup or Root Uninstaller or something similar, can I then install the .apk that's generated on a CM install? I've tried this, but haven't been able to get it to work yet. Anyone with more knowledge have any ideas on this? I could post the apk I generated, if that would help.
I have a Sph-L900 Sprint Galaxy Note 2. About a month ago the device started acting up Saying it couldn't connect to my Samsung Account, and the only way I was able to fix it was a factory reset. That soon turned into not being able to connect to my Google account and knox issues where something was trying to access my device administrator, and the only fix was to keep updating the samsung security police. The device began shutting off and restarting about two to three times a day with the same error notifications popping up on start up. I kept doing a factory reset in order to get ride of the issues but would reappear shortly after.
I have never tried to root my phone because I wanted to wait for my contract to be up before messing around with it.The most I have done is install a few 3rd party apps and use the google launcher apk as my everyday launcher. Eventually because it keep restarting so often I thought I would try to put cyanogenmod on it using the installer app.Unfortunately it kept saying it couldn't communicate with my device and had to abandon that option. A few hours later the phone restarted again but this time became stuck on the Samsung Galaxy Note 2 logo on start up. I tried to another factory reset hoping that would fix it but this is what happened
View attachment 2714455
The whole thing is in red and keeps saying error and fail.
I have no idea what the issue being a noob, but started looking through forums and posts hoping to get an answer. I thought trying to reload the stock rom might be my best bet and started looking into how to unbrick the phone on youtube and forums.
I downloaded Odin and tried [ROM][ODIN]SPH-L900 MK4 (MK4 Modem/Kernel/Bootloader/ROM - Full Restore - Unrooted), Galaxynote2root.com, and QBking77 methods and files for putting factory stock rom back on the phone. I spent all day trying each one only to get "nand write start fail" when trying each tar file on odin.
I wanted to see if someone might actually be able to explain to me the exact issue and hopefully a possible solution.
Surgemidnight13 said:
I have a Sph-L900 Sprint Galaxy Note 2. About a month ago the device started acting up Saying it couldn't connect to my Samsung Account, and the only way I was able to fix it was a factory reset. That soon turned into not being able to connect to my Google account and knox issues where something was trying to access my device administrator, and the only fix was to keep updating the samsung security police. The device began shutting off and restarting about two to three times a day with the same error notifications popping up on start up. I kept doing a factory reset in order to get ride of the issues but would reappear shortly after.
I have never tried to root my phone because I wanted to wait for my contract to be up before messing around with it.The most I have done is install a few 3rd party apps and use the google launcher apk as my everyday launcher. Eventually because it keep restarting so often I thought I would try to put cyanogenmod on it using the installer app.Unfortunately it kept saying it couldn't communicate with my device and had to abandon that option. A few hours later the phone restarted again but this time became stuck on the Samsung Galaxy Note 2 logo on start up. I tried to another factory reset hoping that would fix it but this is what happened
View attachment 2714455
The whole thing is in red and keeps saying error and fail.
I have no idea what the issue being a noob, but started looking through forums and posts hoping to get an answer. I thought trying to reload the stock rom might be my best bet and started looking into how to unbrick the phone on youtube and forums.
I downloaded Odin and tried [ROM][ODIN]SPH-L900 MK4 (MK4 Modem/Kernel/Bootloader/ROM - Full Restore - Unrooted), Galaxynote2root.com, and QBking77 methods and files for putting factory stock rom back on the phone. I spent all day trying each one only to get "nand write start fail" when trying each tar file on odin.
I wanted to see if someone might actually be able to explain to me the exact issue and hopefully a possible solution.
Click to expand...
Click to collapse
Not sure what the issue is, but if your not rooted you can not use method you tried.. If you can get back into your phone, root it using the toolkit found here. http://forum.xda-developers.com/showthread.php?t=1957155 it will install a custom recovery for you during the process. once done you can us the restore method you tried.. You might want to also, uninstall all the apps you have installed one at a time, until you find the one, that might be given you the problem..
doubledragon5 said:
Not sure what the issue is, but if your not rooted you can not use method you tried.. If you can get back into your phone, root it using the toolkit found here. http://forum.xda-developers.com/showthread.php?t=1957155 it will install a custom recovery for you during the process. once done you can us the restore method you tried.. You might want to also, uninstall all the apps you have installed one at a time, until you find the one, that might be given you the problem..
Click to expand...
Click to collapse
Thanks for replying, unfortunately I'm not able to get into my phone as it is just stuck on the Galaxy note 2 logo image on start up. Someone on the google+ community said that it could of happened from the 4.1 to 4.3 update. I guess my best bet is to go to the Samsung kios at Best Buy and see if they can reflash my phone. If I do get it up and running I will install a custom recovery like you mentioned.
Can you reboot and hold the power, home button, & up arrow to get into download mode?
If you can, flash things from there. Odin. I would do the billiard back to stock. Or possibly try the philz recovery.
Please let us know what happens.
ColeTrain! said:
Can you reboot and hold the power, home button, & up arrow to get into download mode?
If you can, flash things from there. Odin. I would do the billiard back to stock. Or possibly try the philz recovery.
Please let us know what happens.
Click to expand...
Click to collapse
{
"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"
}
This is the best I can do with what I have to show you the process. I'm using this download SPH-L900_MK4_Full Restore_UNROOTED one click process as an example. It happens when I use the regular versions of oden and add the tar. files where it says PDA. I have used several versions like Sammobile that people have recommended, but In the end it always says Fail
I tried using the billiard one but since it's set up for twrp I'm not sure how to istall it with odin on the PC
I don't know. I'm just guessing. I'm not an expert. Post in the billiards forum.
I guess i would go to my "prepatory" thread and try flashing a new recovery. I guess try TWRP first. Then try the billiard back to stock. If still no. Try philz and then back to stock. I can't promise anything, but that is my advice.
Surgemidnight13 said:
View attachment 2718005
View attachment 2718006
View attachment 2718007
This is the best I can do with what I have to show you the process. I'm using this download SPH-L900_MK4_Full Restore_UNROOTED one click process as an example. It happens when I use the regular versions of oden and add the tar. files where it says PDA. I have used several versions like Sammobile that people have recommended, but In the end it always says Fail
I tried using the billiard one but since it's set up for twrp I'm not sure how to istall it with odin on the PC
Click to expand...
Click to collapse
That is a very old version of Odin I might add. Download and use Odin 3.07. When using make sure you right click and choose run as administrator. Flash philz 6.0.7.9 do a full wipe reboot into recovery then flash billards return to full stock with counter reset, you should not have any issues..
Hey. If i knew the answer i would tell you. Lol. I'm sorry that i don't. But you need to get something going through odin. Something is messed up on your phone and you need to replace it with something works. If you can't get Anything to flash from odin.... Well i can't imagine what else there would be to do. Except take it in for a replacement.
Sorry to hear this. I remember bricking my phone and was really scared as I did not want to go to the sprint store and go through all that nonsense. I hope you get it up and running. I know someone in this awesome community will help u out.
Wish I could help.
What version of odin are you using?
Let's see if this helps.
First download this Toolkit. It's an awesome tool. http://forum.xda-developers.com/showthread.php?t=1957155
(you will need to read those instructions for drivers install etc)
There really should be no reason why you can't simply reboot your phone into download mode and flash it back to stock. Just make sure you enable usb debugging mode within developer options BEFOREyou begin.
If you want a custom ROM right away, use the toolkit to root and install custom bootloader and recovery, then flash the ROM from recovery per usual.
From that point you can either flash a stock unrooted MK4 ROM or a stock rooted ROM or you can go with a custom rooted ROM. You will need to decide what you want right now.
If you want to stay on a stock unrooted MK4 ROM then you can go ahead and download this stock MC2 with flash count reset. http://forum.xda-developers.com/showthread.php?t=2086769 then once that completes you can simply let the OTA update your phone to MK4 and that will put you back at stock MK4.
You can also just flash the stock MK4 ROM via this page. Follow the instructions. http://forum.xda-developers.com/showthread.php?t=2591898
I, like everyone, am looking forward to installing this update. However, I have heard from others (people with other phones or carriers) that Android L isn't all that great, mainly because of some bugs. Of course this may have had to do with a carrier's modification of Lollipop, so while this would likely be fixed, it certainly gives me pause to go to the effort and update (restore stock recovery, unroot, and other necessary prep work) to find out it's really not that fantastic or T-Mobile needs to fix some things.
So, I was hoping that those if you who have successfully updated could tell me (and others who might want to know) how Lollipop is for you.
Also, if you could tell us what you were before updating (rooted, S-off, using Xposed, none of the above, etc.) it would give us an idea of the difference in systems.
Thanks!
I was rooted, boot loader unlocked, TWRP installed. So I restored a non-root version and restored the recovery.img (took me a bit as I had downloaded an older version not realizing that so the OTA failed).
Upon the first boot up after the OTA, my wifi failed to work at all no matter what I did. I ended up doing a factory wipe (which wiped all my programs and settings - ouch) and now all seems to be working (but I am still setting things up).
-brad
I was stock unrooted, with S-Off and SuperCID. It took the OTA without a hitch. Had a little trouble getting play services to update, but after a restart it did fine. So far everything seems to be working. No bugs that I've found yet. Liking the new features a lot. Really wish they had brought VoLTE with this update.
I'm a long-time user of Team Venom's ViperROM, and only come back to stock for things like this.
I used an RUU to go back to stock, as the stock recovery I had wouldn't work with the OTA from my backup, and AndroidFileHost is down, so I couldn't use the only link I could find to get the latest recovery before this update.
Anyway, I downloaded the update just fine, and it installed just fine, and everything works just fine so far. It feels a whole lot snappier than before. I like the new notification system. The only thing that's driving me crazy is that I can't make the recent apps button into the menu button without installing anything extra. Come on, HTC, add that!
In conclusion, everything is as snappy and pretty as ever before, Wi-Fi speeds are good, call quality is good, and I am thoroughly enjoying it. When Team Venom pushes out their custom ROM, I'll be ecstatic.
I installed the new update this morning and rerooted after. I can't get AdAway to work properly. Otherwise, everything has been much faster and more responsive than it was previously. Feels like a fresh install. Only big issue I've come across is it uses GPS constantly which heats up the phone and kills the battery. I had to turn off GPS to avoid this. I think it may be related to the new Trusted places feature, as the updated Google service uses the GPS a lot.
I RUU'd back to stock after realizing that just going back to an old backup would still result in "Software Status: Modified." After I did that, update installed smooth. I haven't had any of the problems with wifi or data that some people have complained about. I still am not a huge fan of all the t-mobile bloatware, and will probably root/rom it within the month to something a little(lot) cleaner.
StormChaser46 said:
I installed the new update this morning and rerooted after. I can't get AdAway to work properly. Otherwise, everything has been much faster and more responsive than it was previously. Feels like a fresh install. Only big issue I've come across is it uses GPS constantly which heats up the phone and kills the battery. I had to turn off GPS to avoid this. I think it may be related to the new Trusted places feature, as the updated Google service uses the GPS a lot.
Click to expand...
Click to collapse
Just out of curiosity, what method did you use to obtain root?
dysfunkshun said:
Just out of curiosity, what method did you use to obtain root?
Click to expand...
Click to collapse
It was already rooted and the bootloader was unlocked before the update. I just had to reflash TWRP recovery, reflash the supersu.zip file, and then reinstalled supersu from the Play store.
Voice Dial
Discovered today that when you use a bluetooth to activate voice dialing now it gives you the choice to use the google/now app instead of the pre packaged voice dialer.
I was full stock and locked and accepted the OTA without issue of course. Had a little trouble with Google Play Services wanting to update but failing to finish the update. Did some reading and found a solution on androidforums that worked - cleared data and cache on both Google Play Servies and Google Play and then the update succeeded. Since then all works well and I too feel it is much snappier than KitKat. Haven't tried all apps yet but so far so good.:good:
Edit: I had used lollipop on my M7 reconfigured as GPE and really liked the Nexus experience. Since Jumping to the M8, I have chosen not to unlock and root (yet) as I anticipate a jump to the M9. That being said, I like the added features I have seen so far in the pure Sense experience. Notification on the lock screen are better, the Smart Lock works great at home and at work, so far no issues. Loving it. Will write back after a few days of exercise.
Hey, sorry for the basic question here. Just bought an used HTC M8. When I booted, i got the message "this build is for development purposes only do not distribute outside of htc without written permission. Failure to comply may lead to legal action," which I gathered means the phone is unlocked. What steps can I get to get updated to Lollipop?
Can I just download TWRP and flash RUU 4.20.531.4 from http://forum.xda-developers.com/showthread.php?t=2714456 ?
Or do I need to find a way to get to stock t-mobile rom and then back up and recover to 3.32.531.2 recovery before I can get OTA updates?
Thanks!!
pewpew22 said:
Hey, sorry for the basic question here. Just bought an used HTC M8. When I booted, i got the message "this build is for development purposes only do not distribute outside of htc without written permission. Failure to comply may lead to legal action," which I gathered means the phone is unlocked. What steps can I get to get updated to Lollipop?
Can I just download TWRP and flash RUU 4.20.531.4 from http://forum.xda-developers.com/showthread.php?t=2714456 ?
Or do I need to find a way to get to stock t-mobile rom and then back up and recover to 3.32.531.2 recovery before I can get OTA updates?
Thanks!!
Click to expand...
Click to collapse
You can do an RUU, but the first thing I would do is get S-Off. I don't know if it is still Sunshine (an app that was $25) that is the leading method, but even still, it's worth it. If you have S-Off, there are really no mistakes you can make and can't undo....[well, you can't brick it or throw it in a lake].
I am so dependent on customizations, such as button modifications, definitely Ad-Away, and other things, most of which were possible with a custom ROM, or Xposed, but since Dalvik is gone, I understand Xposed won't work. This gives me pause. No matter how nifty Lollipop is, if there is no way to do certain customizations/modifications, and if Ad-Away won't work, I would seriously consider waiting until these things are remedied.
StormChaser46 said:
I installed the new update this morning and rerooted after. I can't get AdAway to work properly. Otherwise, everything has been much faster and more responsive than it was previously. Feels like a fresh install. Only big issue I've come across is it uses GPS constantly which heats up the phone and kills the battery. I had to turn off GPS to avoid this. I think it may be related to the new Trusted places feature, as the updated Google service uses the GPS a lot.
Click to expand...
Click to collapse
No luck on Ad-Away yet?
syntropic said:
No luck on Ad-Away yet?
Click to expand...
Click to collapse
It works fine, UNLESS you haven't disabled system RW protection but I thought everybody knew about that. If you are not s-off, or have not applied the mod to disable system RW protection, you will never be able to modify the hosts file while booted into Android system and so Ad Away app won't be able to either.
In this case all you can do is manually create a modified hosts file and push it with ADB or copy it through file manager while booted to recovery.
{
"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"
}
Messenger cannot send nor receive MMS
It's my only concern so far, HTC messages app works though, I've seen various reports about it but no fix so far. Everything else is running smoothly and I'm liking it. I wish wifi networks would be added to trusted locations but there are apps that allow this
I like T-Mobile Lollipop better than international, for one you don't get those annoying notification vibration.
Did they disable HTC Backup? Havent been able to get a backup to start when connected to wifi.
phil.culler said:
Did they disable HTC Backup? Havent been able to get a backup to start when connected to wifi.
Click to expand...
Click to collapse
Did you try manually running it? My backup didn't run properly and it managed to install apps that I had deleted.
Sent from my HTC One_M8 using XDA Free mobile app
Behold_this said:
It works fine, UNLESS you haven't disabled system RW protection but I thought everybody knew about that. If you are not s-off, or have not applied the mod to disable system RW protection, you will never be able to modify the hosts file while booted into Android system and so Ad Away app won't be able to either.
Click to expand...
Click to collapse
Ok, well I'm S-off, and the only thing I know about the system RW protection is that it exists and while I have one xposed module note that purports to enable it, it does not work. I know this because I can't get Root Logger to work. But right now ad-away on kit Kat is fine.
So is there an disable RW system protection mod I need to run? If so, when should I run it? Now before I upgrade (as I have been still hesitating, but it's getting difficult to resist at this point..especially with La Pollo replacement for Xposed (even though there are no modules written for it yet...at least we have the framework. )
Strange I didn't know about this system RW mod.... I will look around in the regular M8 forum, but if anyone can fill me in, I'd appreciate it.
{
"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.
Hi all. Since I haven't gotten any word as to when there will be official support, I wanted to go ahead and share a build of Lineage OS 16.0 for our Pixel 2 XL/Taimen. It's a completely stock build. If it's working for enough people, then I'll continue to provide builds until/unless we get official support. If you find an error, please try to post logs via logcat to aid in fixing it (better yet to submit it to the Lineage OS team directly as well).
{
"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"
}
Steps for First Install:
Flash latest google image
Boot using the latest version of TWRP: https://dl.twrp.me/taimen/twrp-3.2.3-1-taimen.img.html
Wipe cache and data
Flash latest ROM .zip file
Flash the TWRP installer: https://dl.twrp.me/taimen/twrp-pixel2-installer-taimen-3.2.3-1.zip.html
Reboot to recovery
Flash OpenGapps (Android 9.0, ARM 64, probably nano): https://opengapps.org/ or MindTheGapps: https://androidfilehost.com/?fid=3700668719832237178
If desired, flash a custom kernel
If desired, flash Magisk
Reboot and hopefully enjoy
Steps for Updates:
Follow steps 4- 10 above. You can skip steps 1 - 3 (latest Google image, booting with TWRP .img, wiping) and optionally 7 (flashing Gapps).
Latest ROM, 06-09-19:
Download
Old Releases:
Old Download
I usually like to provide updates every ~2 weeks or month to keep up with security updates and/or anything else important. Thanks for trying and God bless .
Special thanks to @draymond1987, @RaymanFX, and all the other developers for their continued hard work.
View changelog up to build date
/.repo/local_manifests/roomservice.xml is attached
A quick note: If you seem to get stuck on the Gapps setup wizard, you can touch each corner of the screen, going clockwise, starting in the top left corner, to skip it. I've seen the data transfer tool have issues lately. You can uninstall it and continue afterwards.
Any known bugs?
pimpdaddy00 said:
Any known bugs?
Click to expand...
Click to collapse
I had an issue at some point where it would shut off when unplugged, but I don't know if it was just something about how my phone is setup. The other thing I encountered was the setup wizard getting stuck before (but fixed after removing the data transfer tool manually later). I'm hoping to see someone else have it working as I know at some point I was able to boot without issue, other than Magisk possibly not working without flashing another custom kernel. Getting any feedback from logs would helpfully tell me what changed and possibly where to fix it at that point.
I checked the channelog and noticed a few minor changes that seemed nice. Overall, I just hope Active Edge gets working in future ROMs lol. Though I know it's difficult. Good job on this!
Can't even get this to boot.
LLStarks said:
Can't even get this to boot.
Click to expand...
Click to collapse
Do you see the lineage OS logo and then blank screen or very shortly after? I've been facing an issue where it looks like com.qualcomm.qti.telephonyservice stops due to not loading a reference properly if I'm not charging. Thanks for letting me know you've had issues.
I could never get past the Lineage logo. Initial boots are usually long, but it would just crap out and reboot to whatever recovery I put in.
LLStarks said:
I could never get past the Lineage logo. Initial boots are usually long, but it would just crap out and reboot to whatever recovery I put in.
Click to expand...
Click to collapse
Good news all! It looks like the boot issue and modem service failure is fixed. I installed it on my phone and it seems to be stable. Sorry for any/all frustration with the previous build. Hopefully all who have been waiting can use it now:
https://androidfilehost.com/?fid=11410963190603877722
calsurferpunk said:
Good news all! It looks like the boot issue and modem service failure is fixed. I installed it on my phone and it seems to be stable. Sorry for any/all frustration with the previous build. Hopefully all who have been waiting can use it now:
https://androidfilehost.com/?fid=11410963190603877722
Click to expand...
Click to collapse
Thanks a bunch! Flashing now!
Currently using a Pixel 2 XL, can't seem to complete the Android Setup. The app keeps crashing after I connect to WiFi and click continue, does anyone have some advice?
tranna said:
Currently using a Pixel 2 XL, can't seem to complete the Android Setup. The app keeps crashing after I connect to WiFi and click continue, does anyone have some advice?
Click to expand...
Click to collapse
Could try flashing a different gapps package. I always used the mini
tranna said:
Currently using a Pixel 2 XL, can't seem to complete the Android Setup. The app keeps crashing after I connect to WiFi and click continue, does anyone have some advice?
Click to expand...
Click to collapse
I think I went to app info and told it to force stop. If it's on the data transfer utility, I just told it to uninstall (as it seemed to be the culprit for me). I think I either reset/restarted or continued with the pixel setup after that. Either way, just getting to the data transfer utility from within setup or on the apps list and uninstalling it was the trick for me.
Trying this out today for the first time. WiFi calling isn't working, UK EE. Got google apps nano working but had to force quit the setup a few times. Otherwise its looking really nice, thanks!
Hi again all. I just wanted to let all of you who are using this ROM know that I'm planning on updating it very soon. I've been waiting for Google to release security patches for this month, but if I don't see them soon then I'll build with the latest Lineage OS changes anyhow.
On the 2nt or 3rd post is said to tap all for corners of the screen clockwise from top left and it will skip setup, then go into apps and uninstall the data transfer tool. When you do that it will let you move forward with the setup and still let you transfer anyway you want. Hope this helps.
It's amazing! I like it! Thank you so much
Hi again. Here's the latest build of the sources as of today:
https://androidfilehost.com/?fid=11410963190603892886
Something to note is that when I installed it, I simply went to recovery, flashed the new ROM .zip, then flashed the TWRP installation zip again. After that, I rebooted to recovery and installed Magisk again.
For some reason once I booted, the google play store was missing (even though previously having installed OpenGapps along with the previous ROM version). I went back to recovery, reflashed OpenGapps, and it was back again (along with having to go through setup once again, including removing the data transfer tool). Some of the apps (mostly Google's) wouldn't open correctly until I uninstalled and reinstalled them again). My Google account also wasn't present, so I had to add it back as well.
If you come across that same problem, these steps should work, otherwise you might want to just try a fresh install (wiping the old cache and data while in recovery). For anyone who comes up with an easier solution, could you please be sure to share what you did? Everything is still working fine afterwards, but it was just annoying to have to uninstall and add things back. I didn't use the latest OpenGapps, so that might have just been my problem.
I'm unable to complete the setup, since the setup always crashes after adding a google account. It will ask me if I want to select a backup from the cloud or skip, and any option I pick will crash the setup. As a result, Pixel Launcher will not work (maybe that's another issue entirely?) other than that, rom works.
Was wondering if anyone had had any problems with the now playing? I get a pixel ambient services keeps stopping when I ask the assistant but it will tell me the song name. But now playing seams to not work at all. I did try uninstalling the ambient services and reinstall it with no change.