WIFI not working after using KIES to update - Galaxy S 4 Q&A, Help & Troubleshooting

Hi all,
Phone Details:
Spring Galaxy S4
Baseband Version L720TVPUBNG5
Used CF autoroot
This all started a few days ago. The latest OTA update came out and my phone kept telling me I had insufficient storage for the update. I figured it was because I had it rooted. I followed QBking77's video for Unroot / Unbrick. Downloaded all files recommended in the video.
Every time I try to flash with ODIN I get a failure. I have tried three different .tar versions at this point, it always seems to fail after "aboot" attempts to flash. Two different cables, both came with an SGS4.
I finally had enough and used the factory reset. After factory reset I used KIES for my update. The phone took it fine and rebooted. Although now I have no WIFI.
When initiating WIFI it will tell me that the security application has rejected a request to protect my phone. I deleted lookout security even though I have never used it.
Does this have something to do with KNOX? Knox flag is at 0x1 so I know it is tripped. Is there a way to completely flash my phone back to a stock state with the original recovery and rom?
Are there any options for me to get my phone back in order. I really dont give a **** about root or roms, I just need my WIFI. Would my best bet be to use a custom firmware?

Your correct thread have to go: HERE.

Related

Update Error

Hi guys! I hope someone could help me. I just bought a Galaxy Note 3 (international version) yesterday. The phone's fine. It's just that I am unable to update. I am able to download it but when my phone reboots it shows a dead android with a red triangle on its chest. I read flashing the firmware via odin can fix it but problem is our internet is hella slow. I couldn't even complete downloading my brother's Note 2 firmware. Any way I can make it install the firmware successfully? By the way it's OTA. I am able to download the update, just won't let me finish installing it. Goes around 35% then the android on the black screen dies with a red triangle on its chest.
EDIT:
I have official firmware, never rooted, just got it yesterday. Still factory new.
version 4.3, build # JSS15J.N9005ZHUBMI7, baseband version N9005XXUBMI5, Kernel version 3.4.0-1626679
Have you tried reseting your phone go into recovery mode factory reset
Mygadgetgeek.com
mygadgetgeek.com said:
Have you tried reseting your phone go into recovery mode factory reset
Mygadgetgeek.com
Click to expand...
Click to collapse
not yet, but i have a lot of data now on my phone. will try that though. in case that doesn't work, any other advice?
cptnappy said:
Hi guys! I hope someone could help me. I just bought a Galaxy Note 3 (international version) yesterday. The phone's fine. It's just that I am unable to update. I am able to download it but when my phone reboots it shows a dead android with a red triangle on its chest. I read flashing the firmware via odin can fix it but problem is our internet is hella slow. I couldn't even complete downloading my brother's Note 2 firmware. Any way I can make it install the firmware successfully? By the way it's OTA. I am able to download the update, just won't let me finish installing it. Goes around 35% then the android on the black screen dies with a red triangle on its chest.
EDIT:
I have official firmware, never rooted, just got it yesterday. Still factory new.
version 4.3, build # JSS15J.N9005ZHUBMI7, baseband version N9005XXUBMI5, Kernel version 3.4.0-1626679
Click to expand...
Click to collapse
Was your phone brand new? And did you check your KNOX status? -- reason I ask, after you've rooted a phone you are unable to recieve OTA updates, unless you use Wanam to fake system status, then you can download the OTA update but it stalls on the install about 35% or so in..
Best advice, is grab the stock image from sammobile (ballache to download I know) then use ODIN to flash her back to original state.
radicalisto said:
Was your phone brand new? And did you check your KNOX status? -- reason I ask, after you've rooted a phone you are unable to recieve OTA updates, unless you use Wanam to fake system status, then you can download the OTA update but it stalls on the install about 35% or so in..
Best advice, is grab the stock image from sammobile (ballache to download I know) then use ODIN to flash her back to original state.
Click to expand...
Click to collapse
i didn't root the phone when i got it. it's fresh and on official firmware. have no idea about KNOX, that's new to me. if it helps, my device status says "official"
unfortunately the internet in my area is very slow, i couldn't download firmwares from sammobile. i tried several times
cptnappy said:
i didn't root the phone when i got it. it's fresh and on official firmware. have no idea about KNOX, that's new to me. if it helps, my device status says "official"
unfortunately the internet in my area is very slow, i couldn't download firmwares from sammobile. i tried several times
Click to expand...
Click to collapse
Ah Ok, if it says Official it should be good to go. Seems like maybe the download has gotten corrupt due to an intermittent internet connection.
cptnappy said:
i didn't root the phone when i got it. it's fresh and on official firmware. have no idea about KNOX, that's new to me. if it helps, my device status says "official"
unfortunately the internet in my area is very slow, i couldn't download firmwares from sammobile. i tried several times
Click to expand...
Click to collapse
OK, then maybe you should learn a few things before trying to update - Knox is a security system in latest Samsung phones that is supposed to be triggered/set when you root (or install any custom kernel/recovery). Your initial (old) firmware could still let you root without triggering the Knox flag, and then you can update to the latest firmware for your region using Mobile Odin Pro and still keep your root AND without triggering the Knox flag. However once you update using Samsung OTA / Odin / Kies to a firmware more recent than MJ3 you can no longer root without also triggering your Knox warrany flag - read more about this in the Universal Root De La Vega thread!
i gave up after several tries, since i'm on 4.3 i think that would do for now. maybe it's just downloading a stability update or something? everytime i do an OTA update, it tells me that the download of the new firmware is complete then reboot. when i get to 32% the droid falls flat on its back and shows the red triangle on its chest, over and over. i don't lose my phone data or anything. just won't update. i'll wait for 4.4 Kitkat instead. hope i'll be able to update to that when it comes out.
EDIT: i tried going into recovery mode, wiping cache, and factory reset.. still no dice. maybe Odin's the only way i guess. problem is my internet connection lol
@cptnappy - i also have the same problem...got my note3 n9005 a week ago and I also have the same problem as you....error at 30+%
tried update thru Kies with no luck...same error appears
Sent3 said:
@cptnappy - i also have the same problem...got my note3 n9005 a week ago and I also have the same problem as you....error at 30+%
tried update thru Kies with no luck...same error appears
Click to expand...
Click to collapse
i managed to update mine using Samsung Kies3 (not Kies, but Kies3). Hope updating OTA is fixed in the future with the update i just did

Able to again get OTA updates on Sprint S5 after root - Knox flag still 0x1

So I initially rooted my Sprint S5 using the old fashioned way, which tripped my Knox flag seen at bootup in Odin mode. That part I cannot seem to get reset (going to try Triangle Away shortly).
However I now have it reloaded using the Samsung Kies Windows program with the latest firmware, and in the phone settings Device Status where it used to say "Custom" it now again says "Official". I first tried to use Odin to put the stock firmware image back on, which did not help at all.
I went into Kies version 3.2.14072_12 with my S5 plugged in and clicked Tools menu -> Firmware upgrade and initialization". It may ask you for model and serial number, which I put in for mine just fine, and then it launched saying the device will be initialized to original settings. However this is different from doing factory reset from within the phone. It reboots to odin and then recovery and performs a handful of things. When it completed I had to re-setup a bunch of things, but the phone basically unrooted itself without me telling SuperSU to do an unroot. I ran supersu and it said it couldnt run on an unrooted phone... So I checked the About info in settings and voila, back to Official status, and OTA updates work again!
Unfortunately the knox flag didnt un-set, but Im less worried about that and more worried about missing enhancement OTA patches and updates - well I was before I will update here if that Triangle program can reset the counter. I thought that counter was a hard-wired fuse piece of hardware, not flash memory, so Im not sure that it can be done, but worth a try. Hope this works for everyone and Good Luck!!
This is already known.... And FYI no known method can reset the Knox counter.
Sent from a Galaxy 5 light years away
Herby6262 said:
So I initially rooted my Sprint S5 using the old fashioned way, which tripped my Knox flag seen at bootup in Odin mode. That part I cannot seem to get reset (going to try Triangle Away shortly).
However I now have it reloaded using the Samsung Kies Windows program with the latest firmware, and in the phone settings Device Status where it used to say "Custom" it now again says "Official". I first tried to use Odin to put the stock firmware image back on, which did not help at all.
I went into Kies version 3.2.14072_12 with my S5 plugged in and clicked Tools menu -> Firmware upgrade and initialization". It may ask you for model and serial number, which I put in for mine just fine, and then it launched saying the device will be initialized to original settings. However this is different from doing factory reset from within the phone. It reboots to odin and then recovery and performs a handful of things. When it completed I had to re-setup a bunch of things, but the phone basically unrooted itself without me telling SuperSU to do an unroot. I ran supersu and it said it couldnt run on an unrooted phone... So I checked the About info in settings and voila, back to Official status, and OTA updates work again!
Unfortunately the knox flag didnt un-set, but Im less worried about that and more worried about missing enhancement OTA patches and updates - well I was before I will update here if that Triangle program can reset the counter. I thought that counter was a hard-wired fuse piece of hardware, not flash memory, so Im not sure that it can be done, but worth a try. Hope this works for everyone and Good Luck!!
Click to expand...
Click to collapse
Thanks for th3 info. When I need ota then I know what to do. Its pretty obvious that I am new to this but I'm learning
Where can I find the numbers required for kies update ? SN is no where on the phone or under battery
MagnumPOS said:
Where can I find the numbers required for kies update ? SN is no where on the phone or under battery
Click to expand...
Click to collapse
phone info.apk

Looking for the right stock ROM

Hello all, first post here so please be gentle, I've searched and been at this for the better part of the last 12 hours.
I have a US Cellular Note 3 and I plan on trading it in towards a new phone soon (hopefully tomorrow if I can get everything going.) I've never had a custom ROM, I rooted it with towelroot and have used supersu for superuser access and have been using it like that for the past year and a half. From what I understand in order for everything to go over smooth trading it in I need knox to be at 0x0, and for it to show stock official ROM and official device status. As of right now knox is at 0x0, it shows official ROM, but device status shows custom, also in device status in my settings it shows custom and it won't update. I deleted all of my root apps, did a full unroot with supersu, still says custom. I unmounted my SD card and wiped my partition cache, still says custom.
at this point here's what I'm attempting to do based on a few hours of digging, download and flash a stock ROM (Have Odin ready, phones plugged in, drivers installed, downloading what I hope is a good ROM) re root my phone with towelroot, reinstall supersu, run triangle away, full unroot with supersu again, factory reset.
I can't post my download link due to being a new user, I went to sammobile firmwares and punched in my model number and found a download link.
my device model number (SM-N900R4)
Also my baseband version is N900R4TYUCNAB and I'm running 4.4.2.
Now for my questions: Will flashing a stock ROM trip Knox? How do I know for sure if it's a good stock ROM? Is this the appropriate course of action? In hindsight I probably should have asked that question first.
I really hope somebody can help me out with this, I've rooted every phone I've ever had but I feel pretty over my head at the moment.
UPDATE:::: I'M AN IDIOT!
Updated to lollipop through kies fixed the issue. If google leads anybody here in the future just use kies to update.
In all my years of flashing stock Samsung ROMs, none of them have ever tripped the Knox counter.

[GT-I9506] Need help resetting my device software status

So, a few months ago I decided to root my phone with towelroot to give a try on a few root applications, as i was curious, but after that, I decided to remove through supersu it as, even with supersu, was more of a vunerability since I wasn't really using it.
Fast foward a month, I attempted to update my software and was denied with the reason that my device was custom.
Some important info:
- I'm running Android Jelly Bean 4.3, that has never been updated.
- I've attempted a factory reset through the phones recovery mode and made no difference.
- My KNOX waranty value is 0x0, and I would like to keep it that way if possible.
- Phone is factory unlocked.
Also, I've though of using Odin to flash the firmware back, but then I read that there is a possible that KNOX warranty gets triggered, even with a samsung official rom, is this true or am I safe to use it?
My objective is to have my phone back to factory settings (this means wannan xposed is out of the question), in order to be able to update my phone and keep using it, and while there is a lot of similar threads around, most of them reffer to GT-I9505 and GT-I9500 and mine is GT-I9506, which leaves me in somewhat of a doubt wether I should follow those or not.
Thank you for your time.
Diaz_ said:
So, a few months ago I decided to root my phone with towelroot to give a try on a few root applications, as i was curious, but after that, I decided to remove through supersu it as, even with supersu, was more of a vunerability since I wasn't really using it.
Fast foward a month, I attempted to update my software and was denied with the reason that my device was custom.
Some important info:
- I'm running Android Jelly Bean 4.3, that has never been updated.
- I've attempted a factory reset through the phones recovery mode and made no difference.
- My KNOX waranty value is 0x0, and I would like to keep it that way if possible.
- Phone is factory unlocked.
Also, I've though of using Odin to flash the firmware back, but then I read that there is a possible that KNOX warranty gets triggered, even with a samsung official rom, is this true or am I safe to use it?
My objective is to have my phone back to factory settings (this means wannan xposed is out of the question), in order to be able to update my phone and keep using it, and while there is a lot of similar threads around, most of them reffer to GT-I9505 and GT-I9500 and mine is GT-I9506, which leaves me in somewhat of a doubt wether I should follow those or not.
Thank you for your time.
Click to expand...
Click to collapse
Flashing a stock rom trough Odin will NOT trip Knox. So just go ahead and flash the firmware you want.
Lennyz1988 said:
Flashing a stock rom trough Odin will NOT trip Knox. So just go ahead and flash the firmware you want.
Click to expand...
Click to collapse
Alright, I assume the proccess is about the same as on the other versions.
Also, should I flash 4.4.2 instead of 5.0.1? The reason I ask is due to this thread.
Update: I flashed 4.4.2 with Odin3 3.10, and it went smooth and knox is still safe, however, for some reason, so thank you Lennyz1988 for the reassurance .
However, I'm not able to update to 5.0.1 Lolipop through OTA, as attempting to update states that im fully up to date.
My phone is running as NL (T-Mobile), factory unlocked and due to my quick research, seems that there is no official OTA update for it. Is it correct or am I looking in the wrong place to update my phone?

GS5 verizon 4.4.4 to rooted marshmallow

I have a Verizon GS5 that has been towelrooted on 4.4.4 for close to 2 years. It's worked ok, but I've started seeing various issues that required a factory reset. Since I'm back to no settings, I was thinking updating the OS would be a good idea. I would like to move to either Lollipop or Mashmallow but it looks like the latter may be a problem with my phone (CID 11 and Verizon) while keeping Knox 0x0.
I'm having a problem following the guide that I've found here:
https://www.androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
bkenobi69 said:
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
Click to expand...
Click to collapse
Try to dial *#0808# in the stock phone application.
You should see a menu with several options.
Select "MTP+ADB" under USB settings and press "OK".
Then you'll be able to connect your phone via MTP or ADB to your PC.
If there's no menu, then (assuming you're rooted) open a good file browser (ES, Root Explorer or something) and open the file /efs/carrier/HiddenMenu (it's a simple text file) and replace OFF with ON there.
Save the changes and reboot the phone.
Now the menu should be operational.
Unfortunately, I already tried to update to 6.0.1 so this very helpful info is a little to late.
I followed all directions on the linked page above but didn't get things working. I repeated 2 or 3 times now and I'm clearly missing something. I can get through installing busybox, but then when I reset, it hangs at the samsung screen and just vibrates 3 times repeatedly. I'm going to have to figure this out tonight as I don't really have a backup phone.
bkenobi69 said:
Unfortunately, I already tried to update to 6.0.1 so this very helpful info is a little to late.
I followed all directions on the linked page above but didn't get things working. I repeated 2 or 3 times now and I'm clearly missing something. I can get through installing busybox, but then when I reset, it hangs at the samsung screen and just vibrates 3 times repeatedly. I'm going to have to figure this out tonight as I don't really have a backup phone.
Click to expand...
Click to collapse
Currently root is impossible for MM on G900V CID11.
Impossible means you cannot gain it now, most likely it's forever.
There's no internet site which can help.
You must choose: root on LP or unrooted MM.
You must decide if you want a stock ROM or something (TW-based) else too.
It's a good idea to flash and use a stock firmware for the time while you're thinking.
Interesting... I guess I must have been reading things wrong because I thought I could go to MM with root. I'll try going to Lollipop then but first I'm going to just flash back to JB 4.4.4.
I downloaded 4.4.4 from Samsung and was going to write it with Odin, but it says FAIL when I try to flash. I suspect I just tripped Knox...
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
I'll look around to find a guide, but if you have a suggestion, I'd certainly listen!
bkenobi69 said:
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
Click to expand...
Click to collapse
This means that you've upgraded your phone's firmware while experimenting.
Now you cannot directly flash 4.4.4 with Odin, you're limited to 5.0 (BOK3) and above.
Ok. I'll read the guides on the head of this list and see if I can find the right information.
FWIW, I was following the same how-to that most of the stickies point to and say is safe. I wonder how I got to a position that I'm in now when I did the same as recommended. Painiac's thread points to the same thing I did:
https://forum.xda-developers.com/ve...al/guide-painiacs-essential-guide-to-t3319848
I think I may have tried to flash a MM stock rom though when it got into a boot loop. I suspect that would be the issue.
Bootloop is not a problem in this case.
Just reboot to the recovery and perform a factory reset from there.
The phone will boot but the first boot will take 10-15 min.
bkenobi69 said:
I have a Verizon GS5 that has been towelrooted on 4.4.4 for close to 2 years. It's worked ok, but I've started seeing various issues that required a factory reset. Since I'm back to no settings, I was thinking updating the OS would be a good idea. I would like to move to either Lollipop or Mashmallow but it looks like the latter may be a problem with my phone (CID 11 and Verizon) while keeping Knox 0x0.
I'm having a problem following the guide that I've found here:
https://www.androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
Click to expand...
Click to collapse
Marshmallow can not be rooted on CID 11 devices. The Samsung drivers are found here: https://www.samsung.com/us/support/owners/product/galaxy-s5-verizon You can follow the 5.0 root guide here: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529 to downgrade to 5.0. If you want to downgrade past that to a version lower than 5.0, you will still have to follow that guide then follow the instructions here (I recommend you to follow the root guide for 5.0 above then skip steps 1 and 2 on this page): https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858 . You can find stock firmwares here: https://forum.xda-developers.com/showthread.php?t=2784880 (stock firmware, kernel, and modem files) and if you get bootlooped or bricked, just reflash the combination file from the root guide. If you want to root 4.4.4, follow the downgrade method using all of the NK2 files but the flash the NGC kernel, run through the setup, then use towelroot and flash the NK2 kernel after that. If you ever get stuck on the red Verizon screen, just pop the battery out and reboot.
That's about all anyone can do and a run down of everything.
Thank you for posting specific guides. I'll go back to step 1 and try again. The primary issue I have at this point isn't reading the guide and following directions, its finding the right guide to reduce the number of images I need to download. I'm on 1.5mbps DSL so d/l a 2GB file takes most of a day. I have several that don't appear useful at this point which means I've lost several days.
bkenobi69 said:
Thank you for posting specific guides. I'll go back to step 1 and try again. The primary issue I have at this point isn't reading the guide and following directions, its finding the right guide to reduce the number of images I need to download. I'm on 1.5mbps DSL so d/l a 2GB file takes most of a day. I have several that don't appear useful at this point which means I've lost several days.
Click to expand...
Click to collapse
Understandable, I can't believe it is 2018 and we still haven't invented a way to compress 1.7GB into 1.7MB archives to make life easy on low connections. How is battery life on 4.4.4 and which update of 4.4.4 are you on? I've been having an issue with my phone dropping a percent every 2 minutes on 5.0/6.0. It would be nice find a version to root along with excellent battery life.
The reason I was looking at updating was due to battery issues. I had the phone for around a week before I rooted it (a couple years ago). After rooting, I started seeing immediate battery issues. My wife has the same unrooted phone (currently on MM) and has never had the type of issues I have. I figured the issue was likely a bad kernel and was thinking I'd just update to something newer (LL or MM) to help. I assume a new battery would help since mine is 1-2 years old, but I swapped with my wife's phone and she still gets lots better performance. Once I get this back up, I'll probably buy a new battery for each phone.
So it appears that I must have upgraded the bootloader to a point where towelroot no longer works as was previously suggested. I believe then that I need to follow the second guide to be able to downgrade to a rootable Lollipop version:
https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858
I am downloading the PB1 rom and lolliroot and need to also get a system restore, kernel, and modem. As I said, my connection is terrible so it would be great if someone could suggest which version of restore I should go with. I was going to install Lollipop in the end (that was the original goal). I figured I'd just get OC4 since it's likely to have the least bugs and best performance. If that is a mistake and I should go with an earlier version of LL PLEASE throw it out there!
Ok, I tethered to my wife's phone and am burning her data (shhhh, don't tell her).
I grabbed all of the OC4 files, the PB1 rom, and lolliroot. I think I have everything I need so long as OC4 is a good place to end up.
bkenobi69 said:
The reason I was looking at updating was due to battery issues. I had the phone for around a week before I rooted it (a couple years ago). After rooting, I started seeing immediate battery issues. My wife has the same unrooted phone (currently on MM) and has never had the type of issues I have. I figured the issue was likely a bad kernel and was thinking I'd just update to something newer (LL or MM) to help. I assume a new battery would help since mine is 1-2 years old, but I swapped with my wife's phone and she still gets lots better performance. Once I get this back up, I'll probably buy a new battery for each phone.
So it appears that I must have upgraded the bootloader to a point where towelroot no longer works as was previously suggested. I believe then that I need to follow the second guide to be able to downgrade to a rootable Lollipop version:
https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858
I am downloading the PB1 rom and lolliroot and need to also get a system restore, kernel, and modem. As I said, my connection is terrible so it would be great if someone could suggest which version of restore I should go with. I was going to install Lollipop in the end (that was the original goal). I figured I'd just get OC4 since it's likely to have the least bugs and best performance. If that is a mistake and I should go with an earlier version of LL PLEASE throw it out there!
Click to expand...
Click to collapse
Here are some files (that I been hunting for about an hour for). Just gonna reference this for future use and anyone who comes across this thread. http://rootjunkysdl.com/files/?dir=Galaxy S5
Nice find!
I have the phone up and running on stock PB1 currently. I'm going to let it sit to see what the battery is like prior to rooting. While I haven't gotten it hooked back up to my account yet nor do I have it rooted, I feel pretty confident now that I'm on the right track. Thanks!
Just to finish out this topic, I have not successfully completed attaining root on 5.0. I flashed PB1 to the phone and then followed this guide for installing KingRoot:
https://androidforums.com/threads/root-question.1120150/
I got the lolliroot files from here:
https://www.androidfilehost.com/?fid=312968873555011514
Thanks to all who offered help!
Qyuck question... I've got my phone working well bow, but there's one issue with apps I'm not sure how to address. I want to use Verizon Visual Voicemail but I can't find it on the Play store. I disabled updates so I wouldn't get the marshmallow update and break root. but, with updates turned off, VVM won't get pushed. Any suggestions?

Categories

Resources