Just switched to Sprint Note 4 and OTA to lollipop the the next day. I am completely stock and would like direction on wi-fi tether and a way to get rid of all the bloteware. Thank in advance.
akaimana said:
Just switched to Sprint Note 4 and OTA to lollipop the the next day. I am completely stock and would like direction on wi-fi tether and a way to get rid of all the bloteware. Thank in advance.
Click to expand...
Click to collapse
From what ive found from another thread:
"Originally Posted by MasterTentacles
The only think you need ahead of time is your MSL. This isn't too hard to get from Sprint customer service. I got mine via an app called MSL Utility, which it seems now crashes every time I try to use it on Lollipop.
The steps:
Go to Dialer and enter ##DATA# (##3282#)
Press "Edit" then enter your MSL.
Click on APN Settings
For both "APN2 EHRPD internet" and "APN2 LTE internet" change APN Type from "default,mms" to "default,mms,dun"
After you enter the change, hit Menu -> Save before going to the next APN."
However seems like they changed it with the new lollipop update so that you cant go in and find your msl number, I even tried to find it with terminal emulator after being rooted and couldnt find it. Should be noted though that you can supposedly find your msl on a lower android. If you by chance call in to get this number write it down and keep it safe as doing a prl update will put it back to normal and lose this function
However If you are rooted download Galaxy tools and it will work perfect. Plus you will have the option to get all of your quick notification toggles like wifi hotspot and data if you so wish with the .apk
Galaxy Tools
For your debloating you can just uninstall the apps you dont want and disable the others that wont go away so that they wont update or show up in your app drawer.
If you are rooted you can use this System app remover (ROOT)
good luck
I guess next question would be what is the safest way to root and what is needed.
akaimana said:
I guess next question would be what is the safest way to root and what is needed.
Click to expand...
Click to collapse
For me the safest and easiest way was to use skipsofts' Unified Android Toolkit. I personally choose this as it finds and downloads all the latest files and drivers and just prompts you with options as well as clear instructions on what to do next. You also have an option to inject a custom recovery and backup too. Im lazy and let it organize my files for me
If you feel pretty confident you can do search the interwebs for the latest odin and chainfire tar Put your phone into download mode (power down and boot back up holding down the volume ↓ + pwr + menu button) make sure auto reboot is ticked along with f. reset in odin plug in your phone then go to the pda/ap spot and locate that tar file. Hit start and let it run. It should take only like 30 seconds or so. Aftwards power your phone go to supersu and update the binaries. Later flash a custom recovery like twrp or clockwork if you care to flash more things later.
Thats a pretty quick run down of how to do it. If you want more details you can always google it
EDIT: It should be noted that rooting will trip KNOX
Related
I tried rooting to chainfires root process but after doing this 6 times after it boots back i get the message that Unfortunately SuperSu has stopped working and on top of that i keep getting the notification Unauthorized access to a secured area has been blocked. Im not sure if i did something wrong cause i followed his instructions step by step exactly right am i missing something or what is the deal.. please help
update i realize i forgot to say what phone im rooting lol
i have samsung galaxy note 2 with 4.3
I am in the same situation. I was able to root my S4, but I can't get my wife's Note 2 to root. Every issue you have I am having also. Hopefully someone will be able to help us.
critter1332 said:
I tried rooting to chainfires root process but after doing this 6 times after it boots back i get the message that Unfortunately SuperSu has stopped working and on top of that i keep getting the notification Unauthorized access to a secured area has been blocked. Im not sure if i did something wrong cause i followed his instructions step by step exactly right am i missing something or what is the deal.. please help
update i realize i forgot to say what phone im rooting lol
i have samsung galaxy note 2 with 4.3
Click to expand...
Click to collapse
+1.
Frustrated. :banghead:
Any help would be appreciated.
Sent from my SPH-L900 using Tapatalk
chconser said:
+1.
Frustrated. :banghead:
Any help would be appreciated.
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
I finally got mine rooted. Do everything in this post. I was able to remove KNOX and finally get my damn phone rooted! This was used to root my wife's Sprint Note 2 with the OTA 4.3 update. here
is the complete thread if you want to see it all. The link I posted first is the 3rd post from that thread.
Doing those steps WILL FIX your issues with not being able to root your Note 2.
I actually boot looped my wife's Note 2 in the process, so if you do brick/boot loop it, then follow these instructions. That put the phone back to the OTA 4.3 stock version. I had to put my wife's SD card into my phone and add the files to her SD card (provided in the link I just posted) to get it to work. Me being an idiot is how I boot looped her phone. This was the ONLY way I could get it to work... and I tried so many methods I found here, youtube, and online.
Good luck gentleman! Let me know if I can help you anymore!
baseband version
i was wondering if the baseband version could have anything to do with it (im still new to rooting) i have L900VPUBMK4 on my phone but when i looked around in other places i noticed people having L900VPAMK4 is there a difference an could this be why mine wont root
i will try your method above an thanks so much for posting this i will let you know of my outcome
oops miss spelled the baseband version i have LP900VPUBK4 but others have L900VPAMK4
tried
smashedixnay said:
I finally got mine rooted. Do everything in this post. I was able to remove KNOX and finally get my damn phone rooted! This was used to root my wife's Sprint Note 2 with the OTA 4.3 update. here
is the complete thread if you want to see it all. The link I posted first is the 3rd post from that thread.
Doing those steps WILL FIX your issues with not being able to root your Note 2.
I actually boot looped my wife's Note 2 in the process, so if you do brick/boot loop it, then follow these instructions. That put the phone back to the OTA 4.3 stock version. I had to put my wife's SD card into my phone and add the files to her SD card (provided in the link I just posted) to get it to work. Me being an idiot is how I boot looped her phone. This was the ONLY way I could get it to work... and I tried so many methods I found here, youtube, and online.
Good luck gentleman! Let me know if I can help you anymore!
Click to expand...
Click to collapse
I tried this but when i did the kingo software it immediately asked me to grant supersu an had a button on bottom of kingo that said ok so i look at my phone but no supersu so i still kept going thru the process an then noticed in kingo where its suppose to say what phone type is connected it says samsung device an from seeing it on other sites of people connecting there devices it had there device names reconised so not sure if its not doing that correctly for my phone or what but after running the software which frozen for awhile when it came to the part that said checking root an then it said waiting for device for awhile an then stopped an said root failed
i cant even get passed step one
I finally rooted my note 2
i tried cf's method an im not sure what went wrong but something did an it wouldnt root so i then tried kingo but at first i noticed that when connecting my note to kingo it just said samsung device it didnt reconize it fully to it saying samsung sphl900 so i knew something wasnt right an then after trying to root it failed so i then noticed that in download mode it said it was customized so i downloaded USER_L900_SPT_MC2_to_MK4_Update_FWD an used odin an then opened the download again on my phone an it finally said samsung official so i then went back to kingo an it did reconize my phone an it did finally root it ,,, im new to rooting an not sure if this will actually help anyone but its what i went thru to get mine rooted an thanks to everyone that has helped me
I was able to fix the same issue...
chconser said:
+1.
Frustrated. :banghead:
Any help would be appreciated.
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
I had the same issue and fixed it like this -
1. Installed ES File explorer and open it.
2. Press Menu on the phone and scroll down and turn ON Root Explorer and hit Back.
3. Choose Device from the top menu (dropdown)
4. From the bottom menu, choose search and search for super and you should see superuser.apk.
5. Choose that and install it.
From there you should be able to disable KNOX and open SuperSu
kkgiyer said:
I had the same issue and fixed it like this -
1. Installed ES File explorer and open it.
2. Press Menu on the phone and scroll down and turn ON Root Explorer and hit Back.
3. Choose Device from the top menu (dropdown)
4. From the bottom menu, choose search and search for super and you should see superuser.apk.
5. Choose that and install it.
From there you should be able to disable KNOX and open SuperSu
Click to expand...
Click to collapse
I tried this to no avail, getting error message 'Application not installed'. The thing is, when I go into the Play Store it says SuperSU IS installed but I only have the option to open it. There is no 'update' option available like I keep reading everyone suggests to do to fix this problem. And when I attempt to open SuperSU, I get the error message 'Unfortunately, SuperSU has stopped' followed by the KNOX security notice 'Unauthorized access to a secured area has been blocked'.
Sent from my SPH-L900 using Tapatalk
Ahh
I am having a similar issue
PhonezDoctor said:
I am having a similar issue
Click to expand...
Click to collapse
Same.
Everyone I figured out a simple solution to this. I got my phone back on the 13 from replacement. On the 16 I tried to root for the first time. And KNOX led me into a panic. Reading all the forums and knox blocked every attempt I made, but I neat that ***** into the ground.
1. Get some kind of file Explorer and find the SuperSU apk.
2. ReInstall that bad boy.
3. Immediately after install a message will appear asking if SuperSU can try to disable KNOX.
4. Click it quickly, if you don't knox will try to block it again.
5. You should now have KNOX out of the way. You should now be free to delete that slut!
I chose system app safe remover and searched for all files with KNOX and deleted it. I feel you could probably kill it with any root explorer and know the files you are looking for.
Sent from my SPH-L900 using xda app-developers app
kkgiyer said:
I had the same issue and fixed it like this -
1. Installed ES File explorer and open it.
2. Press Menu on the phone and scroll down and turn ON Root Explorer and hit Back.
3. Choose Device from the top menu (dropdown)
4. From the bottom menu, choose search and search for super and you should see superuser.apk.
5. Choose that and install it.
From there you should be able to disable KNOX and open SuperSu
Click to expand...
Click to collapse
For further clarification, simply clicking on it did not work for me. It gave me an "There is a problem parsing the package."
If you long press on the file then select More from the bottom menu then select Install, it will install properly.
Just wanted to clarify for anybody else who ended up with that issue.
It worked!
kkgiyer said:
I had the same issue and fixed it like this -
1. Installed ES File explorer and open it.
2. Press Menu on the phone and scroll down and turn ON Root Explorer and hit Back.
3. Choose Device from the top menu (dropdown)
4. From the bottom menu, choose search and search for super and you should see superuser.apk.
5. Choose that and install it.
From there you should be able to disable KNOX and open SuperSu
Click to expand...
Click to collapse
This worked for me. Once I reinstalled the SuperUser APK, ES asked for access and everything else fell into place. Thanks!
use esfile to solve it
chconser said:
I tried this to no avail, getting error message 'Application not installed'. The thing is, when I go into the Play Store it says SuperSU IS installed but I only have the option to open it. There is no 'update' option available like I keep reading everyone suggests to do to fix this problem. And when I attempt to open SuperSU, I get the error message 'Unfortunately, SuperSU has stopped' followed by the KNOX security notice 'Unauthorized access to a secured area has been blocked'.
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
I got this done by the following:
1. Do exactly as aforementioned instruction, untill you find superuser.apk
2. Hold your finger on that apk icon untill a little squre show up that you can mark it
3. Find "more"(my is at the right lower corner of the screen), choose it and find "install" on your right.
4. Then install.
I dont know why this apk can be installed through es file, basically it still needs to Android to run the installation, yet it works in this way.
have a try and good luck
I keep having to go back into the file explorer and installing it. It will work for a while then out of the blue it pops up and says it has quit. I am very skeptical to try and go through the flash process to install a different ROM. Currently bone stock 4.3 eff bomb. Any suggestions?
JD
Try and use ODIN to flash TWRP then flash @billard412 to get back to MC2 stock, it will remove KNOX and reset flash counters, if any. Then ODIN TWRP again since it will re-install the stock recovery you can then flash the MK4 kernel, WIFI Fix and MK4 ROM of your choice.
flynhawn2002 said:
Try and use ODIN to flash TWRP then flash @billard412 to get back to MC2 stock, it will remove KNOX and reset flash counters, if any. Then ODIN TWRP again since it will re-install the stock recovery you can then flash the MK4 kernel, WIFI Fix and MK4 ROM of your choice.
Click to expand...
Click to collapse
I have warranty bit 1 showing.
JD
jdougs said:
I have warranty bit 1 showing.
JD
Click to expand...
Click to collapse
Ok....since you tripped KNOX you cant get rid of that but its ok if you are not returning your phone (maybe out of warranty?) then just ignore it.
Flash away!
Ya the warranty didn't mean squat...I went ahead and tried the SGS3 JELLYBOMB VER 20.0.0.MD5 and it went with no problems. Haven't got the SuperSU has stopped since flashing. Thanks for the encouragement here. So far so good.
JD
Are you on AT&T, rooted with CWM or TWRP recovery, and don't want to update to the new, currently un-rootable ROM, or take the chance that AT&T will push the FOTA update to your phone and attempt to install it without your knowledge? Here's one way to block it:
1. Download Autorun Manager from the Play Store.
2. Run Autorun Manager, give it SU privileges, and enter its Recommended Advanced Mode.
3. Go to Settings, check both "Show system entries" and "Enable system app disable", and return to the list of apps.
4. Scroll down to "Google Services Framework" and open it.
5. Scroll down the list until you see "com.android.gsf.update.SystemUpdateService$Receiver" (mine was at the bottom of the list). Uncheck this to Disable it.
6. Exit Autorun Manager.
That's it. FOTA updates are now blocked.
This info is available in various places here on XDA, and other places on the web. I'm just reposting it here for those that don't want to be bothered with the problems that can be caused by AT&T's pissy little update.
visionlogic said:
Are you on AT&T, rooted with CWM or TWRP recovery, and don't want to update to the new, currently un-rootable ROM, or take the chance that AT&T will push the FOTA update to your phone and attempt to install it without your knowledge? Here's one way to block it:
1. Download Autorun Manager from the Play Store.
2. Run Autorun Manager, give it SU privileges, and enter its Recommended Advanced Mode.
3. Go to Settings, check both "Show system entries" and "Enable system app disable", and return to the list of apps.
4. Scroll down to "Google Services Framework" and open it.
5. Scroll down the list until you see "com.android.gsf.update.SystemUpdateService$Receiver" (mine was at the bottom of the list). Uncheck this to Disable it.
6. Exit Autorun Manager.
That's it. FOTA updates are now blocked.
This info is available in various places here on XDA, and other places on the web. I'm just reposting it here for those that don't want to be bothered with the problems that can be caused by AT&T's pissy little update.
Click to expand...
Click to collapse
F#$K man. This is great...
I have been hit three times in a row by the latest little update from AT&T, and have each time ended with CWM Recovery loop. This is so effing wrong !! I have a post here on how to get out of the recovery loop
http://forum.xda-developers.com/showthread.php?t=2603454&page=7 post #70.
EDIT: This did not completely remove the painful notification and for somereasoon I could not delete the downloaded in "/system/cache". So I applied the update, then used adb to recover from the CWM loop and delete the Fota.img, rebooted. Then I also installed the FOTAkill.apk app here
http://forum.xda-developers.com/showthread.php?t=2249350
Now the update is dead !!
chappatti said:
F#$K man. This is great...
I have been hit three times in a row by the latest little update from AT&T, and have each time ended with CWM Recovery loop. This is so effing wrong !! I have a post here on how to get out of the recovery loop
http://forum.xda-developers.com/showthread.php?t=2603454&page=7 post #70.
Click to expand...
Click to collapse
Damn right it's WRONG! Deliberately borking folks that don't follow the master's rules. Especially those folks that have had the update pushed and automatically attempted install without their consent. Pure crap!
chappatti said:
EDIT: This did not completely remove the painful notification and for somereasoon I could not delete the downloaded in "/system/cache". So I applied the update, then used adb to recover from the CWM loop and delete the Fota.img, rebooted. Then I also installed the FOTAkill.apk app here
http://forum.xda-developers.com/showthread.php?t=2249350
Now the update is dead !!
Click to expand...
Click to collapse
Good! Whatever works for you. My own experience with Android has been that a given "cure" will not necessarily work for everyone. As for the method I mentioned above I've gone 72+ hours without any data transfer related to the update. So far, so good.
Official OTA's aren't pushed out to those using an unlocked AT&T version on other carriers right?
Update FYI - 10 days now since making the adjustment in the OP and still no indication of my phone attempting any update.
I followed and used this thread ( http://forum.xda-developers.com/show....php?t=1963790 ) to root my phone, and i have no troubles following the steps. I searched around the thread and found out that i can unroot my phone with the SuperSU app, so i went into the app and selected the unroot button. To my knowledge it worked, since when i went into my Root Check app it said that there wasn't any root found. But here is my problem, when i go into my phone settings and select the stock update for my phone it gives me a message of "Your device has been modified. Software updates are not available", so am I missing something? Is there another step i must do to be able to update my phone from 4.1.2. My phone is the Galaxy S3 SGH-I747M. Thanks for taking the time to read my post!
BAWTH said:
I followed and used this thread ( http://forum.xda-developers.com/show....php?t=1963790 ) to root my phone, and i have no troubles following the steps. I searched around the thread and found out that i can unroot my phone with the SuperSU app, so i went into the app and selected the unroot button. To my knowledge it worked, since when i went into my Root Check app it said that there wasn't any root found. But here is my problem, when i go into my phone settings and select the stock update for my phone it gives me a message of "Your device has been modified. Software updates are not available", so am I missing something? Is there another step i must do to be able to update my phone from 4.1.2. My phone is the Galaxy S3 SGH-I747M. Thanks for taking the time to read my post!
Click to expand...
Click to collapse
Try doing 2 things: First do a hard wipe/reset from settings (after backing up your data, of course). Then boot into download mode and see what your settings are especially if you have a custom or official binary. Sometimes though OTA update availability may take 24-48 hours to register. Finally, if you really want to update your phone to the latest OS, this could be done manually and I'd be glad to point you in the direction of this. Since you are still on 4.1.2, I would suggest you take the opportunity to free unlock your phone on 4.1.1 (if you haven't done this already).
Thanks for the reply,
Won't this method delete all my settings (in my phone settings and app settings)?
BAWTH said:
Thanks for the reply,
Won't this method delete all my settings (in my phone settings and app settings)?
Click to expand...
Click to collapse
Yes, it may which is why you need to do a back-up. You could do a simple back with Kies and restore your apps and settings afterwards.
Suggestion
I would use KingoRoot to unroot the phone, without losing anything! (It's free too just Google it)
im wanting to do the update to ZVD, mostly to get rid of the notification!
but id rather not have to do a full wipe, and start all over again ( i hate loosing my texts!) but i have twrp and the hotspot mod.
i think i can go back to stock recovery with a recovery image i downloaded, but the hotspot mod is the only thing i need to figure out how to reverse.
ive read to just replace with the stock files, but i dont have the stock files.
any info will help. ive searched, but theres just too much to look through on the update, rcovery and hotspot, that i figured it would be faster to just ask. i was hoping there would be a flashable zip at some point, but doesnt look like it,
thanks for all help!
majorahole said:
im wanting to do the update to ZVD, mostly to get rid of the notification!
but id rather not have to do a full wipe, and start all over again ( i hate loosing my texts!) but i have twrp and the hotspot mod.
i think i can go back to stock recovery with a recovery image i downloaded, but the hotspot mod is the only thing i need to figure out how to reverse.
ive read to just replace with the stock files, but i dont have the stock files.
any info will help. ive searched, but theres just too much to look through on the update, rcovery and hotspot, that i figured it would be faster to just ask. i was hoping there would be a flashable zip at some point, but doesnt look like it,
thanks for all help!
Click to expand...
Click to collapse
If all you care to do is get rid of the notification, tap and hold on the notification, tap on "App Info" and uncheck "Show notifications." This will block the update notification.
As far as losing text messages and such, use Helium to back up your device's app data, WiFi settings, Dictionary, Messages, and Call Log. If you use the Helium Server it will create a "backup.zip" on your computer so that after you reset the phone, just install Helium, run the server, and restore the apps. As far as hotspot mod, I have no idea, sorry. Hope this helped anyways. If you have any questions let me know.
I just purchased a new Sprint Note 4 and have not powered up the device yet. It is new and still in the box.
I believe that the Note 4 as shipped is on Android 4.4.4. And if so, upon powering up the device for the first time, how do I prevent the device from automatically updating to Android 5.1.1???
Should I not set up the wifi until I am completely past the setup process?.......that way it will alert me and I can decline the installation???
Would it update automatically?....
Sent from my LG-D722 using XDA Free mobile app
jt404 said:
I just purchased a new Sprint Note 4 and have not powered up the device yet. It is new and still in the box.
I believe that the Note 4 as shipped is on Android 4.4.4. And if so, upon powering up the device for the first time, how do I prevent the device from automatically updating to Android 5.1.1???
Should I not set up the wifi until I am completely past the setup process?.......that way it will alert me and I can decline the installation???
Click to expand...
Click to collapse
Yes, when youre setting it up, just dont provide a wifi password when your wifi is detected in the beginning. that way it wont even download the update to begin with.
When Connections Optimizer comes up, if you dont want it. click Manage and uncheck the first box.
And if youre quick enough... after the first,last name ending of the setup up, get ready to hit the APP drawer icon on the far right bottom, quickly swipe to the right and settings should be on the middle right, quickly scroll down to system update and uncheck the first box.
Its a 50/50 chance before the bloatware starts, but it is possible..
If it does have 4.4.4, tap build number 7 times and enable USB Debugging, tap on the USB icon to switch from MTP to camera, then back to MTP, allowing ADB to allow your phone to recognize your computer. then....
http://forum.xda-developers.com/note-4-sprint/help/sprint-successfully-t3184581
jt404 said:
I just purchased a new Sprint Note 4 and have not powered up the device yet. It is new and still in the box.
I believe that the Note 4 as shipped is on Android 4.4.4. And if so, upon powering up the device for the first time, how do I prevent the device from automatically updating to Android 5.1.1???
Should I not set up the wifi until I am completely past the setup process?.......that way it will alert me and I can decline the installation???
Click to expand...
Click to collapse
Do you plan on rooting right away? Maybe it's Xposed availability that motivates you from preventing update?
IDK if this works prior to root but you could try it with adb or Odin TWRP, and use its file manager (not sure if mount is required or not, mount if needed):
delete /data/fota (KitKat)
or delete /cache/fota (Lollipop)
[Delete whole folder]
That should stop any prompt to update during or after the setup wizard. But I don't think the update is ever automatic; it will install and prompt you to update AFAIK. I can't guarantee you have KitKat out of the box either. Pray.
Sent from my SM-N910P using Tapatalk
xxSTARBUCKSxx said:
Yes, when youre setting it up, just dont provide a wifi password when your wifi is detected in the beginning. that way it wont even download the update to begin with.
When Connections Optimizer comes up, if you dont want it. click Manage and uncheck the first box.
And if youre quick enough... after the first,last name ending of the setup up, get ready to hit the APP drawer icon on the far right bottom, quickly swipe to the right and settings should be on the middle right, quickly scroll down to system update and uncheck the first box.
Its a 50/50 chance before the bloatware starts, but it is possible..
If it does have 4.4.4, tap build number 7 times and enable USB Debugging, tap on the USB icon to switch from MTP to camera, then back to MTP, allowing ADB to allow your phone to recognize your computer. then....
http://forum.xda-developers.com/note-4-sprint/help/sprint-successfully-t3184581
Click to expand...
Click to collapse
Got it! Thanks for the advice! Will do.
samep said:
Do you plan on rooting right away? Maybe it's Xposed availability that motivates you from preventing update?
IDK if this works prior to root but you could try it with adb or Odin TWRP, and use its file manager (not sure if mount is required or not, mount if needed):
delete /data/fota (KitKat)
or delete /cache/fota (Lollipop)
[Delete whole folder]
That should stop any prompt to update during or after the setup wizard. But I don't think the update is ever automatic; it will install and prompt you to update AFAIK. I can't guarantee you have KitKat out of the box either. Pray.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice! I do plan on rooting right away. I want to keep it at 4.4.4 (if possible) because the most stable roots through both Chainfire and Skipsoft only go up to 4.4.4.
Not to step on anyones toes , but that wont solve the issue, itll just delete whats been downloaded and reprompt the download of lolliFLOP once connected to WiFi. Before you connect to a WiFi, root, use a Root Explorer(and yes, you will need to remount it to Read/Write once in system to allow the renaming(adding .bak ot the end) of the files.
Go to System/priv-apps
and find
SprintDM.apk and
SyncmlDM.apk and add .bak to both of those files
leaving you with
SpringDM.apk.bakand
SyncmlDM.apk.bak
and reboot and youll be good.
xxSTARBUCKSxx said:
Not to step on anyones toes , but that wont solve the issue, itll just delete whats been downloaded and reprompt the download of lolliFLOP once connected to WiFi. Before you connect to a WiFi, root, use a Root Explorer(and yes, you will need to remount it to Read/Write once in system to allow the renaming(adding .bak ot the end) of the files.
Go to System/priv-apps
and find
SprintDM.apk and
SyncmlDM.apk and add .bak to both of those files
leaving you with
SpringDM.apk.bakand
SyncmlDM.apk.bak
and reboot and youll be good.
Click to expand...
Click to collapse
Not a problem at all; my mistake. I just dirty installed a beta version of tapatalk and didn't see your post prior posting myself. I'm wiping data and cache for tapatalk; they're experimenting with its cache optimization and it doesn't refresh well since they started.
The other files you mention I'm not having to delete them on Lollipop but you're more familiar with KitKat than I. It could also be the debloat I'm doing in Lollipop that makes a difference.
My toes are fine. Thanks.
Sent from my SM-N910P using Tapatalk