At first, they all disappeared...... Then I finally got them to change, but return to stock with every reboot?
Forgot to do a backup before starting this..... So I'm stuck with what ever I end up with
tele_jas said:
Of course, I forgot to make a backup before doing anything.....So, is there any way I can get my emoji's back?
Click to expand...
Click to collapse
you have an idea where's the emoji's location?
i can pull those files and upload them for you or anyone else
P.S. Dude, Always Backup.....first rule while messing with root,system changes, etc :cyclops:
DrakenFX said:
P.S. Dude, Always Backup.....first rule while messing with root,system changes, etc :cyclops:
Click to expand...
Click to collapse
Yeah, I've been doing this for 4 years..... I just got over-excited and did a stupid thing
I think I know where they're located and I've replaced them with a different set, then rebooted and tried the emoji switcher again and I now have the "Emoji One" emoji's :highfive:
[EDIT] But every time I restart, the stock emoji's return?
Also flashed a different font
tele_jas said:
Yeah, I've been doing this for 4 years..... I just got over-excited and did a stupid thing
I think I know where they're located and I've replaced them with a different set, then rebooted and tried the emoji switcher again and I now have the "Emoji One" emoji's :highfive:
[EDIT] But every time I restart, the stock emoji's return?
Also flashed a different font
Click to expand...
Click to collapse
awesome dude,
P.S. you are show quiet the info there (phone number) just FYI LoL
DrakenFX said:
awesome dude,
P.S. you are show quiet the info there (phone number) just FYI LoL
Click to expand...
Click to collapse
Yeah, I realized that after I posted it....Was editing it when you replied
To have your changes persist you need to disable system write protection:
Code:
adb shell reboot disemmcwp
As discovered here:
http://androidforums.com/threads/zte-write-protection-for-zmax-and-other-zte-phones.1040331/
originally for other ZTE phones but works with the Axon 7 too.
Nameless One said:
To have your changes persist you need to disable system write protection:
Code:
adb shell reboot disemmcwp
As discovered here:
http://androidforums.com/threads/zte-write-protection-for-zmax-and-other-zte-phones.1040331/
originally for other ZTE phones but works with the Axon 7 too.
Click to expand...
Click to collapse
Awesome, that did it! Thank you!!
tele_jas said:
At first, they all disappeared...... Then I finally got them to change, but return to stock with every reboot?
Forgot to do a backup before starting this..... So I'm stuck with what ever I end up with
Click to expand...
Click to collapse
It's been a while since I've rooted. Do you have a file or file link to the emoji one emoji for the whole system and also a font package zip?
Sent from my ZTE A2017U using Tapatalk
osmosizzz said:
It's been a while since I've rooted. Do you have a file or file link to the emoji one emoji for the whole system and also a font package zip?
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I'm using "Emoji Switcher" from the play store (Root required). I don't have the actual .ttf file. There is a "write protection" on the system, once I rebooted, they came back (to stock)..... After I removed the write protection, I was able to successfully change my emoji's using the app. :good:
The font I got here off of XDA, I only have the "China Cat" font .zip
tele_jas said:
I'm using "Emoji Switcher" from the play store (Root required). I don't have the actual .ttf file. There is a "write protection" on the system, once I rebooted, they came back (to stock)..... After I removed the write protection, I was able to successfully change my emoji's using the app. :good:
The font I got here off of XDA, I only have the "China Cat" font .zip
Click to expand...
Click to collapse
Awesome man. Thanks. I used to use that app but stopped because it stopped working on Samsung devices after MM. Going to give it a try when I get a chance. Haven't unlocked my bootloader because I don't want spend 3 hours setting up the phone again. Maybe I'll wake up early Saturday and get it done
Sent from my ZTE A2017U using Tapatalk
osmosizzz said:
Awesome man. Thanks. I used to use that app but stopped because it stopped working on Samsung devices after MM. Going to give it a try when I get a chance. Haven't unlocked my bootloader because I don't want spend 3 hours setting up the phone again. Maybe I'll wake up early Saturday and get it done
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
Backup your phone (system and apps) to your SD card using the WeShare app included on your phone..... It will cut your restore time down quite a bit!
It's not perfect, but sure saved me a lot of time setting back up.
Related
I got the ota the other day and debated installing it because my M is rooted and the bootloader is unlocked and I have flashed ClockworkMod recovery. I searched for a while to see what others were saying and didn't really find anything of note so I decided to go ahead and run the install. When the phone rebooted into recovery and tried to install the update, it gave me the following Error: E: Failed to verify whole-file signature. Then there was an option to apply unsigned update (or zip, I can't remember the wording exactly). I chose not to do this and went back in the recovery menu and rebooted back into system. The phone booted normally and then immediately rebooted on its own back into recovery to try to install the update again, ending in the same results. This happened 2-3 more times before I finally formatted the Cache Partition through cwm which ended the bootloop (not sure that you can really describe that as a bootloop since it was actually doing what it thought it should be). My question is this, is it safe to go ahead and install the unsigned update via CWM? I have also since seen threads stating that if you had removed some of the bloatware apps, that the update would fail. I have removed many of these unneeded apps, should I reinstall them? I have seen a link or two to the bloat apks...
Having a unlocked bootloader doesn't matter. You just need to be stock 4.1.1 bloatware and all.
what he said^
you can update it with cwm but you have to have all the crapware that came stock still present.
Do you have to unroot first to get it to install? I have TWRP recovery on mine and can't get the update to install.
Sent from my XT907 using xda app-developers app
bobcheeks said:
Do you have to unroot first to get it to install? I have TWRP recovery on mine and can't get the update to install.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
No. You don't have to unroot. You must have modified something else.
Sent from my Nexus 7 using Tapatalk 2
antp121 said:
what he said^
you can update it with cwm but you have to have all the crapware that came stock still present.
Click to expand...
Click to collapse
So if I restore the bloatware, it is ok to choose the "install unsigned zip"?
Thanks for the quick reply, you guys rock!
bwat1009 said:
So if I restore the bloatware, it is ok to choose the "install unsigned zip"?
Thanks for the quick reply, you guys rock!
Click to expand...
Click to collapse
If its all there, yep. It'll be fine
Sent from my Nexus 7 using Tapatalk 2
antp121 said:
If its all there, yep. It'll be fine
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
bwat1009 said:
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
Click to expand...
Click to collapse
I RSDed back to 4.1.1 because mine hung on the clock app. I had installed the 4.2 clock.
bwat1009 said:
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
Click to expand...
Click to collapse
You could try grabbing the apk from /data/app and moving it to /system...
Or grab it from one of the many /system dumps around here...
Someone should turn the OTA into a flashable zip from CWM/TWRP that doesn't check for that.
I may do that...
sloosecannon said:
You could try grabbing the apk from /data/app and moving it to /system...
Or grab it from one of the many /system dumps around here...
Someone should turn the OTA into a flashable zip from CWM/TWRP that doesn't check for that.
I may do that...
Click to expand...
Click to collapse
I had the same thought about moving the apk to the system/app directory and did just that. My expectation was that I would still get the error but for a different app since I just tested with the one that had been throwing the error but it didn't change, still gave the error for the amazon mp3 app even though it was successfully installed in the correct directory. Thanks for the thought though. If you could turn it into a flashable zip, I would be much appreciated. I would love to do that myself but I have no idea how. I know just enough through trial and error (and a lot of forum reading) to be dangerous...
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
bwat1009 said:
I had the same thought about moving the apk to the system/app directory and did just that. My expectation was that I would still get the error but for a different app since I just tested with the one that had been throwing the error but it didn't change, still gave the error for the amazon mp3 app even though it was successfully installed in the correct directory. Thanks for the thought though. If you could turn it into a flashable zip, I would be much appreciated. I would love to do that myself but I have no idea how. I know just enough through trial and error (and a lot of forum reading) to be dangerous...
Click to expand...
Click to collapse
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
tehjolly81 said:
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
Click to expand...
Click to collapse
Have you tried using mattlGroff's DROID RAZR M Utility? Worked for me.
Sent from my XT907 using xda premium
Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
Alright, thanks for the tip and the link, I will give it a try and let you know...
tehjolly81 said:
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
Click to expand...
Click to collapse
I'm pretty sure you need an unlocked boot loader to downgrade.
netizenmt said:
Have you tried using mattlGroff's DROID RAZR M Utility? Worked for me.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
I did. It fixed an issue where my phone wasn't booting, but it did not revert me to 4.1.1. Just found your comment in the other thread about modifying the xml file.. I'll try that next. Thanks.
patehi nice
Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
That worked at getting the system apps that I had removed back into the /syste/app directory and now the update appears to be installing... Will let you know if it works.
*UPDATE*
Well that worked like a charm, update installed successfully, root access maintained, cwm allowed me to prevent reflash of stock recovery so all is right with the world... Thanks you guys!
Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
Thank you! I had missing Amazon_IMDb.apk, Facebook.apk, Kindle.apk, PlusOne.apk files. Copied these to my phone and updated successfully!
I have done some searching to see if anyone has done this already and not found anything. Has anyone ported the stock Nexus 4 boot animation to Nexus 5 resolution? I preferred that Nexus boot animation to the one that came with the N5, and would love to have it scaled up to fit the resolution of this phone.
I'll port it tomorrow when I have time (I have finals to study for).
Sent from my Nexus 7 using XDA Premium 4 mobile app
Thanks a lot! That would be awesome.
thor6577 said:
I'll port it tomorrow when I have time (I have finals to study for).
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Here, this should work. (Removed since it didn't work) Happy theming!
Thanks bud, unfortunately it didn't work. I replaced my stock one with this in Root Explorer, and it stayed on the boot up "Google" image all the way until loading the lock screen. It never played the boot animation.
thor6577 said:
Here, this should work. http://d-h.st/nNa Happy theming!
Click to expand...
Click to collapse
tebower said:
Thanks bud, unfortunately it didn't work. I replaced my stock one with this in Root Explorer, and it stayed on the boot up "Google" image all the way until loading the lock screen. It never played the boot animation.
Click to expand...
Click to collapse
Sorry for that. I'll fix it when I get home.
Sorry for the bug. I redid it so check if it works now : http://d-h.st/L0n Remember to put it in the system/media without renaming it. Backup your old bootanimation in case. Happy theming.
thor6577 said:
Sorry for the bug. I redid it so check if it works now : http://d-h.st/L0n Remember to put it in the system/media without renaming it. Backup your old bootanimation in case. Happy theming.
Click to expand...
Click to collapse
would love to try this.. do u just flash in recovery?? how would i go about backing up my current.. just make a back up in twrp>?
Using root explorer or other root file app, you rename the old bootanimation.zip to bootanimation.bak
The you copy and paste the new file you downloaded into the system/media folder
QUOTE=P.Mobile;48651546]would love to try this.. do u just flash in recovery?? how would i go about backing up my current.. just make a back up in twrp>?[/QUOTE]
Sorry to make another note on this, the image is super stretched out, so something may have gone wrong with the resolution.
thor6577 said:
Sorry for the bug. I redid it so check if it works now : http://d-h.st/L0n Remember to put it in the system/media without renaming it. Backup your old bootanimation in case. Happy theming.
Click to expand...
Click to collapse
tebower said:
Sorry to make another note on this, the image is super stretched out, so something may have gone wrong with the resolution.
Click to expand...
Click to collapse
They say 3rd times the charm! http://d-h.st/IEJ I tested it myself this time and made sure it worked. Happy theming!
So LG decided to update software. Is downloading now, i'm curious what version will be.
I think i will lose root and custom recovery after installing.
crissx said:
So LG decided to update software. Is downloading now, i'm curious what version will be.
I think i will lose root and custom recovery after installing.
Click to expand...
Click to collapse
Probably really minor. I hope for a QRemote update
Sent from my iPhone using Tapatalk
crissx said:
So LG decided to update software. Is downloading now, i'm curious what version will be.
I think i will lose root and custom recovery after installing.
Click to expand...
Click to collapse
I hope its a patch to fix the annoying blue line.
EdenGottlieb said:
Probably really minor. I hope for a QRemote update
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
It's 117.38 MB, but it's slow..slow dwl.
System ROM is 2GB so its unlikely to be anything significant
Sent from my LG-V500 using xda app-developers app
It will not install if you have custom recovery. Will reboot only in recovery. I had to restore to my latest back-up (edit: and same thing ) I think i will revert to stock.
This update : Apps enhancement.
Which base? Still jelly bean 4.2.2?
Can someone make a flashbacks zip we can update the new changes via twrp. Or cwm?
Sent from my LG-V500 using Tapatalk
No new update for mine as of yet.
Sent from my SCH-I535 using Tapatalk
err:0x13E
I downloaded the update files and rebooted the tablet but at 3% it gives me this error err:0x13E . After that the tablet was restarted and booted on android and shows me that the tablet is suspected of rooting and cannot be updated.I have android 4.2.2 stock firmware with root access What can i do?
Installed the upgrade but have no idea what the changes are.
Update
BogdanIT95 said:
I downloaded the update files and rebooted the tablet but at 3% it gives me this error err:0x13E . After that the tablet was restarted and booted on android and shows me that the tablet is suspected of rooting and cannot be updated.I have android 4.2.2 stock firmware with root access What can i do?
Click to expand...
Click to collapse
shadowgolf said:
Installed the upgrade but have no idea what the changes are.
Click to expand...
Click to collapse
Just downloaded the latest update via Wi-Fi no problems about 10 -15 min
There two LG updates /
One of them is a New Application called drive which seem a bit like a cloud system or organiser
The other is the weather widget now shows temp in Red
Sorry "No Kit Kat " :crying:
brian566 said:
There two LG updates /
One of them is a New Application called drive which seem a bit like a cloud system or organiser The other must be a App update
:crying:
Click to expand...
Click to collapse
Thanks for letting us know.
That sounds incredibly boring.
*yawn*
brian566 said:
One of them is a New Application called drive which seem a bit like a cloud system or organiser
:crying:
Click to expand...
Click to collapse
Is "Drive" its exact and complete name? I don't seem to have got that, it might be market-specific... Are you sure you are not mixing it up with Drive from Google?
Drive
xdapao3 said:
Is "Drive" its exact and complete name? I don't seem to have got that, it might be market-specific... Are you sure you are not mixing it up with Drive from Google?
Click to expand...
Click to collapse
Yes it is google drive but i have not downloaded it was not there before the update
Got this "V50010B" update via OTA yesterday (in Italy on an Italian G Pad).
Things I have noticed so far are they have corrected a couple of bugs: tap sounds randomly muted and then randomly working again (I have them on) and a bug where you have the "Auto-show the Remote in the lockscreen when on some AP" option ON and the time widget would "multiply", over time.
P.S. I didn't lose root and I forgot to disable Xposed before updating but it hasn't affected anything. Everything works perfectly well after the update.
I have noticed two changes after the update.
1. Screen seems to be brighter on minimum brightness. Those who was crying for the 7 led's leek, can be happy.
2. If you lock screen rotation, it will be locked on the current position, instead of going back to portrait mode. Now you can lie on your side, and use the tab on landscape:good: !
brian566 said:
Yes it is google drive but i have not downloaded it was not there before the update
Click to expand...
Click to collapse
Oh.. OK. They must have made it a "system app" now whereas it wasn't before :good:
---------- Post added at 04:07 PM ---------- Previous post was at 04:00 PM ----------
Furmint said:
2. If you lock screen rotation, it will be locked on the current position, instead of going back to portrait mode. Now you can lie on your side, and use the tab on landscape:good: !
Click to expand...
Click to collapse
Good to know! The few times I lock the screen (of both my smartphone and my tablet) I usually need it in portrait but I have always found VERY STUPID this behaviour some makers/devices have of locking the orientation always and only in portrait!!
My Note II unfortunately has it, I didn't notice the G Pad had it too (I have probably never tried to lock it in landscape, so far) but I am very glad it hasn't anymore! :good:
I still haven't got the update as of noon eastern time today. Do they push it in waves or something?
Sent from my SCH-I535 using Tapatalk
For anyone tryed to flash the update with TWRP recovery and stuck into "recovery bootloop" just do this.
1)Boot into recovery
2)Go to "Advanced" and then "Terminal Command" and choose root folder.
3)Type this and then hit enter. TRY TO TYPE IT RIGHT OR YOU WILL BRICK YOUR DEVICE
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PS:Without this command even restore will not work
Ps2:Credits to the thecubed
Chainfire has CF Auto root up for download. Follow this link and scroll down to Nexus 6 (Shamu)
http://autoroot.chainfire.eu/
Looks like it works!
Sent from my Nexus 6 using XDA Free mobile app
owenbeals said:
He said this is untested. Has anyone tried it out?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
No I don't have my phone yet.
Only post in here if you made it.
^ thanks
attrapp said:
Only post in here if you made it.
Click to expand...
Click to collapse
Sorry
Permissive Build
attrapp said:
Only post in here if you made it.
Click to expand...
Click to collapse
If we're going strictly by the book, this thread should be moved to General
feedtheducks said:
^ thanks
Click to expand...
Click to collapse
There is a :good: button
Yeah! Not going to be a test mule @Mudavo especially since there have been so many issues with the Nexus 4 variant of this root method. Rather wait for a permissive build.
Auto root seems to have worked for me. However, I didn't see the red android but the script text was there. After install, my device rebooted three times ... which was weird.
First Confirmed Root
zeiroe said:
Auto root seems to have worked for me. However, I didn't see the red android but the script text was there. After install, my device rebooted three times ... which was weird.
Click to expand...
Click to collapse
I would be freaking out over the possibility of bricking it so soon
First verification of working, with three reboots, hopefully that's normal.
zeiroe said:
Auto root seems to have worked for me. However, I didn't see the red android but the script text was there. After install, my device rebooted three times ... which was weird.
Click to expand...
Click to collapse
Thanks for being the guinea pig bro, tbh I'm afraid to root until a few folks confirm but thanks. Everything working? Tested any root apps etc?
:good::good::good:
glensta said:
Thanks for being the guinea pig bro, tbh I'm afraid to root until a few folks confirm but thanks. Everything working? Tested any root apps etc?
:good::good::good:
Click to expand...
Click to collapse
No worries ... We have the factory image now so bricking isn't a issue any mroe. Just titaniumed my restores on Authenticator and stuff. Working root! WOOT!
zeiroe said:
No worries ... We have the factory image now so bricking isn't a issue any mroe. Just titaniumed my restores on Authenticator and stuff. Working root! WOOT!
Click to expand...
Click to collapse
Nice! What is Authenticator ?
So we have to fastboot flash zip "filename".zip ?
I get this error:
writing zip...
<Bootloader> Permission denied
FAILED <remote failure>
Can we flash it from the recovery?
glensta said:
Nice! What is Authenticator ?
Click to expand...
Click to collapse
Google Authenitcator is an app for 2-step verification to google services and other applications that hook into the authenitcator API like Facebook or Last Pass.
XxKINGxX2580 said:
So we have to fastboot flash zip "filename".zip ?
I get this error:
writing zip...
<Bootloader> Permission denied
FAILED <remote failure>
Can we flash it from the recovery?
Click to expand...
Click to collapse
Did you unzip the autoroot files to a folder on your desktop, put your Nexus 6 in bootloader and run the extracted bat file?
Excellent the day is complete root and twrp
Seems to work just fine.
Mine also rooted fine after the reboots. I did not see the red sign either. It is a good day.
Will try when I get home. Anybody tried tethering dun?
I'm curious what rooting at the moment gains us. A few apps? Xposed doesn't work(yet). But for The moment I don't really have a huge urge to root. I will however unlock immediately. In case I'd like to root.
Besides titanium, what apps can we use?
No red logo either.
Had to run the bat 2 times, but looks good, root confirmed.
So recently it shut off around 50% which I have read others are experiencing but thats not the issue im here about. Since then the flashlight by holding power button has stopped working and the hotspot feature shuts itself off randomly. I also cannot delete any files from the ready to flash folder for some reason ive tried everything I know.
jcroy2828 said:
So recently it shut off around 50% which I have read others are experiencing but thats not the issue im here about. Since then the flashlight by holding power button has stopped working and the hotspot feature shuts itself off randomly. I also cannot delete any files from the ready to flash folder for some reason ive tried everything I know.
Click to expand...
Click to collapse
Use ex file explorer turn on root explorer and esare the ready to flash also revert to stock I believe you are using pure nexus
boxguy1 said:
Use ex file explorer turn on root explorer and esare the ready to flash also revert to stock I believe you are using pure nexus
Click to expand...
Click to collapse
switching file browsers did not work. Flashing stock through and then went back to the latest version of purenexus which was my goal to begin with Cheers. Now viper4 android is broken not detecting busybox fix one thing and another thing breaks.
jcroy2828 said:
switching file browsers did not work. Flashing stock through and then went back to the latest version of purenexus which was my goal to begin with Cheers. Now viper4 android is broken not detecting busybox fix one thing and another thing breaks.
Click to expand...
Click to collapse
Here is how to fix viper4arise
Using a file Explorer navigate to /vendor/etc and rename "audio_effects.conf" to "audio_effects.conf.bak", reboot and you should be good.
boxguy1 said:
Use ex file explorer turn on root explorer and esare the ready to flash also revert to stock I believe you are using pure nexus
Click to expand...
Click to collapse
jcroy2828 said:
So recently it shut off around 50% which I have read others are experiencing but thats not the issue im here about. Since then the flashlight by holding power button has stopped working and the hotspot feature shuts itself off randomly. I also cannot delete any files from the ready to flash folder for some reason ive tried everything I know.
Click to expand...
Click to collapse
You could also just use the file manager in TWRP to delete the "ready to flash" folder. Sounds like it's time for a factory reset. :laugh:
v12xke said:
You could also just use the file manager in TWRP to delete the "ready to flash" folder. Sounds like it's time for a factory reset. [emoji23]
Click to expand...
Click to collapse
Long overdue for a reset for me but I was hoping to grab some files off the phone before doing so and I couldn't due to a weird bug. I said **** it and reset anyway
Sent from my Nexus 6P using Tapatalk
boxguy1 said:
Here is how to fix viper4arise
Using a file Explorer navigate to /vendor/etc and rename "audio_effects.conf" to "audio_effects.conf.bak", reboot and you should be good.
Click to expand...
Click to collapse
That did it. Last time I installed purenxus I didn't have to do this which confused me. Should probably run through the usual checklist.
Sent from my Nexus 6P using Tapatalk
jcroy2828 said:
That did it. Last time I installed purenxus I didn't have to do this which confused me. Should probably run through the usual checklist.
Click to expand...
Click to collapse
Yeah try that