Related
Hey all this is my first post on XDA.
So I was trying to unroot and relock my nexus 6 so i decided to replace the build.prop that i have edited with a copy of the original build.prop i had saved on my phone. I used root browser to do this. after I did this I restarted my phone and all I would get is a black screen with google in white and an unlocked lock. it will not boot back up.
My phone will go into recovery mode and that about all i can tell you.
I would truly appreciate your help.
Yaksh123 said:
Hey all this is my first post on XDA.
So I was trying to unroot and relock my nexus 6 so i decided to replace the build.prop that i have edited with a copy of the original build.prop i had saved on my phone. I used root browser to do this. after I did this I restarted my phone and all I would get is a black screen with google in white and an unlocked lock. it will not boot back up.
My phone will go into recovery mode and that about all i can tell you.
I would truly appreciate your help.
Click to expand...
Click to collapse
If your bootloader is unlocked, you can fastboot flash the stock factory image.
Or, if you have TWRP Recovery (I sure hope so, since you were modifying the build.prop) you can connect to your PC while in recovery, then transfer a custom ROM .zip from your PC to your SDcard. Then flash it in recovery.
I had the same thing happen, all you need to do is flash the system image only. Luckily you don't need to flash userdata. Still looking for a way to enable tethering.
Sent from my Nexus 6 using XDA Forums
you do realize that when you edit your build.prop, if you edit to something that doesnt support the n6 or you make a spelling error somewhere, then most likely it will not boot? anyways, the easy way around this is before you edit your build.prop, make a nandroid backup in recovery. so that when you mess up, it won't be a pain in the butt to get everything back.
simms22 said:
you do realize that when you edit your build.prop, if you edit to something that doesnt support the n6 or you make a spelling error somewhere, then mist likely it will not boot? anyways, the easy way around this is before you edit your build.prop, make a nandroid backup in recovery. so that when you mess up, it won't be a pain in the butt to get everything back.
Click to expand...
Click to collapse
This was a method to enable tethering under 5.1, but they've done something to disable it in 5.1.1.
Sent from my Nexus 6 using XDA Forums
Rogue_Blade said:
This was a method to enable tethering under 5.1, but they've done something to disable it in 5.1.1.
Sent from my Nexus 6 using XDA Forums
Click to expand...
Click to collapse
no, its still the way to enable FREE tethering, as long as it is all entered in correctly, it still works. but for tethering, you dont need to do anything, it works straight out of the box.
simms22 said:
no, its still the way to enable FREE tethering, as long as it is all entered in correctly, it still works. but for tethering, you dont need to do anything, it works straight out of the box.
Click to expand...
Click to collapse
Nope, not for me on LMY48I stock, unrooted. WiFi hotspot won't even turn on with 48I, for me. AT&T family share plan (which includes WiFi hotspot). But USB tethering does still work.
cam30era said:
Nope, not for me on LMY48I stock, unrooted. WiFi hotspot won't even turn on with 48I, for me. AT&T family share plan (which includes WiFi hotspot). But USB tethering does still work.
Click to expand...
Click to collapse
in your apn, try changing the IPv6 to IPv4 instead, that should fix the tethering issue(not free tethering, just wireless tethering).
simms22 said:
in your apn, try changing the IPv6 to IPv4 instead, that should fix the tethering issue(not free tethering, just wireless tethering).
Click to expand...
Click to collapse
Thanks. But it is IPv4. Standard AT&T "nextgenphone" APN.
Doesn't really matter for me, since I rarely use tethering. But other users may benefit.
cam30era said:
Thanks. But it is IPv4. Standard AT&T "nextgenphone" APN.
Doesn't really matter for me, since I rarely use tethering. But other users may benefit.
Click to expand...
Click to collapse
oh, for tmo ipv6 is standard. and sometimes wireless tether doesnt work, until tmobilers change it to ipv4.
simms22 said:
no, its still the way to enable FREE tethering, as long as it is all entered in correctly, it still works. but for tethering, you dont need to do anything, it works straight out of the box.
Click to expand...
Click to collapse
As reported many times in numerous locations it doesn't work. If you have a way it does please share.
Sent from my Nexus 6 using XDA Forums
Rogue_Blade said:
As reported many times in numerous locations it doesn't work. If you have a way it does please share.
Sent from my Nexus 6 using XDA Forums
Click to expand...
Click to collapse
well, i just shared, and he tried, said it didnt work. but, it works for tmobile users. its changing the IPv6 in your apn, to a IPv4.
No Joy No Tether
simms22 said:
you do realize that when you edit your build.prop, if you edit to something that doesnt support the n6 or you make a spelling error somewhere, then most likely it will not boot? anyways, the easy way around this is before you edit your build.prop, make a nandroid backup in recovery. so that when you mess up, it won't be a pain in the butt to get everything back.
Click to expand...
Click to collapse
Thanks. I deleted and changed this back to original before I shut down. Having fits trying to get wireless wifi tether from this new Nexus 6 5.1.1. Rooted with CM 12.1. Have yet to find tether? No joy
ray6279 said:
Thanks. I deleted and changed this back to original before I shut down. Having fits trying to get wireless wifi tether from this new Nexus 6 5.1.1. Rooted with CM 12.1. Have yet to find tether? No joy
Click to expand...
Click to collapse
tether is normally in main settings, more.. is it not in cm?
simms22 said:
tether is normally in main settings, more.. is it not in cm?
Click to expand...
Click to collapse
CM strikes again. LMAO
cam30era said:
Nope, not for me on LMY48I stock, unrooted. WiFi hotspot won't even turn on with 48I, for me. AT&T family share plan (which includes WiFi hotspot). But USB tethering does still work.
Click to expand...
Click to collapse
On LMY48I stock WiFi hotspot works great for me. I also have a AT&T family share plan and I connect my tablet to the WiFi hotspot quite frequently.
alryder said:
On LMY48I stock WiFi hotspot works great for me. I also have a AT&T family share plan and I connect my tablet to the WiFi hotspot quite frequently.
Click to expand...
Click to collapse
Working now, here too.
wifi tether unable to open log-file
simms22 said:
tether is normally in main settings, more.. is it not in cm?
Click to expand...
Click to collapse
Am new at this and in uncharted territory. I rooted my new Google Nexus 6 using the WugFresh, Nexus Root Toolkit 2.0.4, Root program downloaded. Also downloaded Busybox, ES File Explorer, Superuser, TWRP, Root Browser. I fail to understand which one gives me root control. Also loaded Cyanogen Mod 12.1 nightly build as a ROM. Also downloaded Wifi Tether 3.4 Experimental 1-07202013 which has worked in my old rooted Galaxy Nexus since 2013, and previous versions since 2011.
I'm thinking I am in over my head as I attempt to deal with a new system, Lollipop, and now Marshmallow 5.1.1 and new phone Nexus 6 and older tether program? Can you suggest or recommend a ROM with perhaps more compatibility and ease of tethering? Wife and I live deep in country and our phone tether only access we have over Verizon with the repeater.
Ray
Hey guys - I have a Google-bought Nexus 6 running on AT&T. I have never had MMS issues until now. I clean-flashed 6.0 and have had no problems except with MMS...most of they time they won't send/receive.
The APN settings are currently the default, set to nxtgenphone.
I have spoken to AT&T and verified that the settings are correct. I just received a new SIM card from AT&T and it hasn't changed anything.
Anyone have any suggestions or similar experience?
Thanks!
No problems here...unlocked N6 running on AT&T. You might check your MMS settings as to the file size. Maybe it's set too small. Also - make sure you have set your app to be the default sms/mms app.
I have run several message apps with no problem...currently using Next SMS (formerly Handcent)
OKAstro said:
No problems here...unlocked N6 running on AT&T. You might check your MMS settings as to the file size. Maybe it's set too small. Also - make sure you have set your app to be the default sms/mms app.
I have run several message apps with no problem...currently using Next SMS (formerly Handcent)
Click to expand...
Click to collapse
I don't believe there are MMS settings for size in the Messenger app...and it is set to default...not sure how that would help though.
The size is only a factor if the mms is over 600 kb. Att has that as their max limit. As long as your apns are correct you should be good.
zelendel said:
The size is only a factor if the mms is over 600 kb. Att has that as their max limit. As long as your apns are correct you should be good.
Click to expand...
Click to collapse
Well my APN is correct and I am not good :crying: lol
If the SIM card is good, the APN is correct...and now I've tried Hangouts instead of Messenger and it has the same problem...then it must either be something on my account on AT&T's side or perhaps I need to try and do a clean flash and test MMS with no modifications (not that I have many...just TWRP and root).
jeffreii said:
Well my APN is correct and I am not good :crying: lol
If the SIM card is good, the APN is correct...and now I've tried Hangouts instead of Messenger and it has the same problem...then it must either be something on my account on AT&T's side or perhaps I need to try and do a clean flash and test MMS with no modifications (not that I have many...just TWRP and root).
Click to expand...
Click to collapse
You don't have data disabled on your account do you?
If all is good then it has to be att that is the issue.
Delete all apn's except for the one your using by default had the same issue a while back in also on the n6 at&t
---------- Post added at 04:11 PM ---------- Previous post was at 04:10 PM ----------
jeffreii said:
Hey guys - I have a Google-bought Nexus 6 running on AT&T. I have never had MMS issues until now. I clean-flashed 6.0 and have had no problems except with MMS...most of they time they won't send/receive.
The APN settings are currently the default, set to nxtgenphone.
I have spoken to AT&T and verified that the settings are correct. I just received a new SIM card from AT&T and it hasn't changed anything.
Anyone have any suggestions or similar experience?
Thanks!
Click to expand...
Click to collapse
Delete all APN'S except the one you are currently using my guess is your gonna have about 5 in there you only need the one that is already selected when you first open the apn section
zelendel said:
You don't have data disabled on your account do you?
If all is good then it has to be att that is the issue.
Click to expand...
Click to collapse
Thanks - I use lots of data so definitely not that. I'm going to contact AT&T again and have them thoroughly look through my account.
galaxy s4 nutjob said:
Delete all apn's except for the one your using by default had the same issue a while back in also on the n6 at&t
---------- Post added at 04:11 PM ---------- Previous post was at 04:10 PM ----------
Delete all APN'S except the one you are currently using my guess is your gonna have about 5 in there you only need the one that is already selected when you first open the apn section
Click to expand...
Click to collapse
I saw this tip somewhere else and have already tried deleting the other APNs to no avail
jeffreii said:
Thanks - I use lots of data so definitely not that. I'm going to contact AT&T again and have them thoroughly look through my account.
I saw this tip somewhere else and have already tried deleting the other APNs to no avail
Click to expand...
Click to collapse
Have you tried using a different apn?
galaxy s4 nutjob said:
Have you tried using a different apn?
Click to expand...
Click to collapse
Yes I've tried both the default nxtgenphone and the second one: phone. The only one I didn't try is the third one: wap.cingular.
From everything I've read, there's no reason why nxtgenphone shouldn't work fine.
jeffreii said:
Yes I've tried both the default nxtgenphone and the second one: phone. The only one I didn't try is the third one: wap.cingular.
From everything I've read, there's no reason why nxtgenphone shouldn't work fine.
Click to expand...
Click to collapse
I feel like such a noob. All this random fix trying, and we don't even have a logcat.
Grab a logcat and post it up. This will tell use just what's going on.
Sorry. Should have suggested this before. Troubleshooting 101
I have the same thing on my oneplus one on all 6.0 roms with AT&T.
If I turn off mobile data and turn it back on, my group MLS send/receive fine for a little while.
Meanwhile I am streaming Netflix on the train endlessly without interruption.
jeffreii said:
Hey guys - I have a Google-bought Nexus 6 running on AT&T. I have never had MMS issues until now. I clean-flashed 6.0 and have had no problems except with MMS...most of they time they won't send/receive.
The APN settings are currently the default, set to nxtgenphone.
I have spoken to AT&T and verified that the settings are correct. I just received a new SIM card from AT&T and it hasn't changed anything.
Anyone have any suggestions or similar experience?
Thanks!
Click to expand...
Click to collapse
Try disabling Google hangouts and uninstalling Google hangouts updates
---------- Post added at 07:53 PM ---------- Previous post was at 07:47 PM ----------
jeffreii said:
Yes I've tried both the default nxtgenphone and the second one: phone. The only one I didn't try is the third one: wap.cingular.
From everything I've read, there's no reason why nxtgenphone shouldn't work fine.
Click to expand...
Click to collapse
Or you can freeze the Google hangouts temporarily with this
https://play.google.com/store/apps/details?id=ccc71.at.free
And see if that helps
---------- Post added at 07:58 PM ---------- Previous post was at 07:53 PM ----------
Or flash cataclysm works great for me full 6.0 experience and very close to stock
https://www.androidfilehost.com/?w=files&flid=40894
zelendel said:
I feel like such a noob. All this random fix trying, and we don't even have a logcat.
Grab a logcat and post it up. This will tell use just what's going on.
Sorry. Should have suggested this before. Troubleshooting 101
Click to expand...
Click to collapse
Ok - I started a CatLog recording session and then attempted to send an MMS through Messenger. I waited until it failed...then waited another 20 seconds...then deleted the message and stopped the recording. Hopefully that got everything. See attached.
Thanks!
SchmilK said:
I have the same thing on my oneplus one on all 6.0 roms with AT&T.
If I turn off mobile data and turn it back on, my group MLS send/receive fine for a little while.
Meanwhile I am streaming Netflix on the train endlessly without interruption.
Click to expand...
Click to collapse
I'm willing to try anything so I disabled data...turned it back on 15 seconds later and tried to send an MMS. Same failure.
galaxy s4 nutjob said:
Try disabling Google hangouts and uninstalling Google hangouts updates
---------- Post added at 07:53 PM ---------- Previous post was at 07:47 PM ----------
Or you can freeze the Google hangouts temporarily with this
https://play.google.com/store/apps/details?id=ccc71.at.free
And see if that helps
---------- Post added at 07:58 PM ---------- Previous post was at 07:53 PM ----------
Or flash cataclysm works great for me full 6.0 experience and very close to stock
https://www.androidfilehost.com/?w=files&flid=40894
Click to expand...
Click to collapse
I froze Hangouts with TiBu, rebooted the phone, and tried to send an MMS with Messenger. Failed again.
Are you connected to Wifi? Can you send any MMS with WiFi off? Right now Cricket is having some sort of MMS Proxy DNS issue. Just a thought, given Cricket runs on AT&T, maybe some AT&T users are affected too.
Reference: https://www.reddit.com/r/NoContract...y_with_cricket_wireless_mms/cw655vx?context=9
BinaryW01f said:
Are you connected to Wifi? Can you send any MMS with WiFi off? Right now Cricket is having some sort of MMS Proxy DNS issue. Just a thought, given Cricket runs on AT&T, maybe some AT&T users are affect too.
Reference: https://www.reddit.com/r/NoContract...y_with_cricket_wireless_mms/cw655vx?context=9
Click to expand...
Click to collapse
Thanks but this has been happening for a few weeks now...in all situations, including no wifi. I just tried it again just in case!
jeffreii said:
Ok - I started a CatLog recording session and then attempted to send an MMS through Messenger. I waited until it failed...then waited another 20 seconds...then deleted the message and stopped the recording. Hopefully that got everything. See attached.
Thanks!
I'm willing to try anything so I disabled data...turned it back on 15 seconds later and tried to send an MMS. Same failure.
I froze Hangouts with TiBu, rebooted the phone, and tried to send an MMS with Messenger. Failed again.
Click to expand...
Click to collapse
Wow there were a ton of errors in that logcat. Many dealing with package manager. I would advise you to do a clean flash. When I say clean I mean wipe the whole device. Then flash the stock image, there are errors all over the place with some system files. I also see you have push bullet installed. Try removing it.
Here is the main mms error.
11-04 22:30:09.664 E/MmsService( 2311): [[email protected]] HTTP: IO failure
11-04 22:30:09.664 E/MmsService( 2311): java.net.UnknownServiceException: CLEARTEXT communication not supported: []
The best advise I could give you is start from scratch. This way it will remove some of those other errors that may or may not be messing with other system apps.
Did you happen to restore some system app settings?
zelendel said:
Wow there were a ton of errors in that logcat. Many dealing with package manager. I would advise you to do a clean flash. When I say clean I mean wipe the whole device. Then flash the stock image, there are errors all over the place with some system files. I also see you have push bullet installed. Try removing it.
Here is the main mms error.
11-04 22:30:09.664 E/MmsService( 2311): [[email protected]] HTTP: IO failure
11-04 22:30:09.664 E/MmsService( 2311): java.net.UnknownServiceException: CLEARTEXT communication not supported: []
The best advise I could give you is start from scratch. This way it will remove some of those other errors that may or may not be messing with other system apps.
Did you happen to restore some system app settings?
Click to expand...
Click to collapse
Thanks for taking a look. When upgrading to 6.0, I wiped my device multiple times with TWRP - wiped everything, not just system. I then flashed 6.0 with ADB. The only modification I made were with Chainfire's boot.img to achieve root...and left TWRP in place as well. I also wiped the device again after flashing 6.0. I then clean installed everything and redid settings for 90% of my apps manually...only a few were restored via in-app restore process or TiBu - as always I would never restore data for any system apps.
I will try removing Pushbullet and see if that helps...perhaps another Logcat without Pushbullet, in case that's the culprit of these errors?
I can wipe and redo everything, but I don't see myself performing it any differently.
Thanks again!
jeffreii said:
Thanks for taking a look. When upgrading to 6.0, I wiped my device multiple times with TWRP - wiped everything, not just system. I then flashed 6.0 with ADB. The only modification I made were with Chainfire's boot.img to achieve root...and left TWRP in place as well. I also wiped the device again after flashing 6.0. I then clean installed everything and redid settings for 90% of my apps manually...only a few were restored via in-app restore process or TiBu - as always I would never restore data for any system apps.
I will try removing Pushbullet and see if that helps...perhaps another Logcat without Pushbullet, in case that's the culprit of these errors?
I can wipe and redo everything, but I don't see myself performing it any differently.
Thanks again!
Click to expand...
Click to collapse
Ok. Wait you wiped after flashing as well? This may cause an issue. only a small chance but a chance none the less.
Ok to trouble shoot this here is what I would do step by step.
1. Fully wipe the device, system, data, both caches, internal storage (back it up of course) (this is also a perfect time to remove encryption if desired)
2.Flash The stock rom and let it load. Try MMS
3.Flash Chains files for root, test mms again.
4.Keep going one by one until it breaks.
If it doesnt work on pure stock set up. Then grab another logcat and we can see where the error is then.
This is not something that will be done right away so set plenty of time aside for it. This way you dont get rushed and maybe just maybe we can figure this out.
Feel free to look at the logcat. I know it seems intimidating but it really isnt. You can see errors by just looking for the E/ after the time. While you might not completely understand what your looking at it will give hints on the issue and if you look at them enough times they kinda start to make sense.
zelendel said:
Ok. Wait you wiped after flashing as well? This may cause an issue. only a small chance but a chance none the less.
Ok to trouble shoot this here is what I would do step by step.
1. Fully wipe the device, system, data, both caches, internal storage (back it up of course) (this is also a perfect time to remove encryption if desired)
2.Flash The stock rom and let it load. Try MMS
3.Flash Chains files for root, test mms again.
4.Keep going one by one until it breaks.
If it doesnt work on pure stock set up. Then grab another logcat and we can see where the error is then.
This is not something that will be done right away so set plenty of time aside for it. This way you dont get rushed and maybe just maybe we can figure this out.
Feel free to look at the logcat. I know it seems intimidating but it really isnt. You can see errors by just looking for the E/ after the time. While you might not completely understand what your looking at it will give hints on the issue and if you look at them enough times they kinda start to make sense.
Click to expand...
Click to collapse
So after flashing all the files, I booted the system to make sure it was up and running fine. Then I went back to TWRP and wiped it for good measure.
Chainfire's boot.img was flashed with the rest of the 6.0 package (never flashed the standard boot.img) to insure that it didn't encrypt the device on first boot.
I just ran another Logcat after uninstalling Pushbullet and there are still a massive number of errors and the same failure to send the MMS...I guess I have a full wipe in my future again...I'll probably wait until we have images for the latest security fixes to do it all at once.
Thanks again!
Anybody get the ZVA Marshmallow update? Did if fix anything?
I have a Sprint G4 LS991 that was already running ZV9 Marshmallow. My phone has informed me today that I have an Android system update. I have no idea what the update is out what it does. Should I install it? What is the version.
. At that does it do?
Already have a theme... Read this.
To allow your phone to use lte plus. I don't know what the effect will be.
hodgestl said:
I have a Sprint G4 LS991 that was already running ZV9 Marshmallow. My phone has informed me today that I have an Android system update. I have no idea what the update is out what it does. Should I install it? What is the version.
. At that does it do?
Click to expand...
Click to collapse
I installed this update about 30 minutes ago. Now a bunch of my apps and widgets are no longer installed. I tried restarting my phone and some more apps were updates, but no all. I'm going to try reinstall the missing apps.
My phone is on Software version LS991ZVA and Android security patch level 2013-01-01. I do not remember what security patch level it was before the update.
Any idea about after update zva can we return back to ZV9 or ZV6 ?
Thank you
gLam16 said:
Any idea about after update zva can we return back to ZV9 or ZV6 ?
Thank you
Click to expand...
Click to collapse
Yes, i return to zv6.
How do you return to a previous version?
NickK60 said:
How do you return to a previous version?
Click to expand...
Click to collapse
use Lg up.
mayrer said:
Yes, i return to zv6.
Click to expand...
Click to collapse
Question then. Did you unlock the wifi tether with the ZV6 downgrade trick? If so, does it still work on ZVA? I've got mine set that way but not sure if the ZVA update kills the entire trick.
I was getting two errors consistently: 1) the phone wouldn't sometimes not hang up unless you reset the phone 2) MM texts wouldn't come through properly
Hope those are fixed.
tech_0912 said:
Question then. Did you unlock the wifi tether with the ZV6 downgrade trick? If so, does it still work on ZVA? I've got mine set that way but not sure if the ZVA update kills the entire trick.
Click to expand...
Click to collapse
I have not lost wi-fi tether.
My phone got an update 2 nights ago. Shows LS991ZVA now with Android 6.0. The Facebook widgets are gone as well as Facebook seems to be integrated into the software now as you can only Force Close or Disable it. No uninstall options. Not sure how I feel about that. Can anyone else confirm this is what they see?
I have the Sprint G4 LS991 that has been sim unlocked and now using simple mobile. Shortly after getting the phone it updated to MM 6.0. Also lost mobile data. Could not get support from LG or Simple due to imei number is from other. Software version says LS991ZFA. Is it possible to downgrade back to Lollipop 5.1 using the LGUP tool? Also after playing with the APN settings i managed to get the mobile data back on.
kadosg4 said:
I have the Sprint G4 LS991 that has been sim unlocked and now using simple mobile. Shortly after getting the phone it updated to MM 6.0. Also lost mobile data. Could not get support from LG or Simple due to imei number is from other. Software version says LS991ZFA. Is it possible to downgrade back to Lollipop 5.1 using the LGUP tool? Also after playing with the APN settings i managed to get the mobile data back on.
Click to expand...
Click to collapse
Yes. You can downgrade.
deanseavy said:
To allow your phone to use lte plus. I don't know what the effect will be.
Click to expand...
Click to collapse
hopefully it finally means simultaneous voice and data on LTE network
leond said:
hopefully it finally means simultaneous voice and data on LTE network
Click to expand...
Click to collapse
Not going to happen.
strider73 said:
I was getting two errors consistently: 1) the phone wouldn't sometimes not hang up unless you reset the phone 2) MM texts wouldn't come through properly
Hope those are fixed.
Click to expand...
Click to collapse
You have to change your APN settings. I noticed that this variant of LG G4 likes to auto rewrite MMS settings.
Check to see if it changed from your MMS api settings to a sprint one....
---------- Post added at 05:14 AM ---------- Previous post was at 05:13 AM ----------
kadosg4 said:
I have the Sprint G4 LS991 that has been sim unlocked and now using simple mobile. Shortly after getting the phone it updated to MM 6.0. Also lost mobile data. Could not get support from LG or Simple due to imei number is from other. Software version says LS991ZFA. Is it possible to downgrade back to Lollipop 5.1 using the LGUP tool? Also after playing with the APN settings i managed to get the mobile data back on.
Click to expand...
Click to collapse
it's an MMS apn setting. I noticed that this phone will try to auto rewrite the APN to default spring settings if a major change occurs.
I use it with t-mobile and noticed it changed on me back to the original after the update. I changed it back to tom's api settings....MMS comes through just fine.
How to change the APN in ZVA 6.0? My IOT shortcut from QuickShortcutMaker does not work. It says "Application is not installed".
cbr150r said:
How to change the APN in ZVA 6.0? My IOT shortcut from QuickShortcutMaker does not work. It says "Application is not installed".
Click to expand...
Click to collapse
That's because you have to open the menu in ZV6, not ZVA. Downgrade to ZV6, open the hidden menu (leaving it in recent apps list), upgrade all the way to ZVA and then go back to that menu. Make APN changes as necessary.
I'd like to unlock the phone legitimately, using the T-Mobile app. I'm rooting and running a custom ROM, though, so it's no surprise that it didn't work when I tried it earlier ("not compatible with this device") or after I unrooted with SuperSu's builtin function. I assume I need to unroot and then install the stock firmware before it'll work. I just want to try to get some confirmation before I go through all that. Will that do the trick or am I SOL?
I am rooted and have a custom ROM and as long as the efs folder is stock it will work. I was able to install the sim unlock app from the play store and just click unlock and it worked.
In that case, what else could be causing my incompatibility? I talked to customer service last night and they weren't helpful. I said the app wasn't working and maybe it was because I was on a custom ROM and she just said "Yeah, maybe that's it." Maybe I should call back and try to find someone more knowledgeable.
Thought I had it when I noticed my model number was SM-G920F. Edited the build.prop to make it 920T, uninstalled and reinstalled the app, and that still didn't do it.
robosllim said:
Thought I had it when I noticed my model number was SM-G920F. Edited the build.prop to make it 920T, uninstalled and reinstalled the app, and that still didn't do it.
Click to expand...
Click to collapse
You should just look at my post about perm unlocking the phone by modifying the NV_Data.bin file. I have not tested this 100% but it currently seems to be working on My phone and my wifes phone.
djalup said:
You should just look at my post about perm unlocking the phone by modifying the NV_Data.bin file. I have not tested this 100% but it currently seems to be working on My phone and my wifes phone.
Click to expand...
Click to collapse
I saw your post, but it was the night before my departure, and I just decided to go with the legit route for the sake of time. Hopefully your method will get further testing at some point, though, because it sounds interesting.
Also, to answer the question of the thread: yes.
How to enable wifi hotspot on Sprint Note 7 without ROOT....
Edit... Works on PHE update...
Make sure you have adb working on your computer...
Have USB Debuging enabled...
Connect your phone with your data cable....
Open Windows Explorer and go to your adb folder...
Hold shift and right click to open command prompt here.....
Type " adb devices " and hit enter to make sure your phone is recognized....
Once it is...
Type " adb shell " and hit enter...
Type " settings put global tether_dun_required 0 "
Hit enter....
Wait about ten seconds then unplug your phone and reboot...
Wifi tether should now work...
If not make sure wifi hotspot sharing is enabled in the hotspot settings....
ENJOY EVERYONE....
Yes we are interested why would you even ask that please post the instruction ASAP
t5mckinney said:
Yes we are interested why would you even ask that please post the instruction ASAP
Click to expand...
Click to collapse
+1 this. Of course we are interested. Thanks for this!
Edit: damn that looks easy. Will do this once I get home
Will definitely be setting this up! Thanks.
Assuming this enables unlimited tethering?
is that a zero or capital O at the end of required
t5mckinney said:
is that a zero or capital O at the end of required
Click to expand...
Click to collapse
Zero
Has anyone confirm that this worked for them
t5mckinney said:
Has anyone confirm that this worked for them
Click to expand...
Click to collapse
It is not working for me. Guess I'll be going back to root. This was really my reason to be rooted, but alas *sigh*
Edit: tried a few times, no go. I can see the change in ADB, it does change the value to 0. Still, after a minute or less it changes back to 1 by itself. Set it to 0, reboot...it's back to 1. Set it to 0, confirm at 0... Still goes back to 1 after a moment. There's no stopping that 1 damnit lol
themisterwilson said:
It is not working for me. Guess I'll be going back to root. This was really my reason to be rooted, but alas *sigh*
Edit: tried a few times, no go. I can see the change in ADB, it does change the value to 0. Still, after a minute or less it changes back to 1 by itself. Set it to 0, reboot...it's back to 1. Set it to 0, confirm at 0... Still goes back to 1 after a moment. There's no stopping that 1 damnit lol
Click to expand...
Click to collapse
Forgive my naivete if this is obviously not possible for whatever reason but is there a way to directly edit the APN settings via ADB or other tool/utility outside the UI? Is there a chance sammy might have just disabled the UI without restricting permissions to the values themselves. Just spit balling.
To clarify, I'm assuming "tether_dun_required 0" is an attempt to disable the authorization verification method by changing the flag to zero. Could there be some way to edit the value(s) (assuming they're APN related per the previous successful non-root tether enabling method) responsible for failing the "tether_dun_required" method?
techfuse12 said:
Forgive my naivete if this is obviously not possible for whatever reason but is there a way to directly edit the APN settings via ADB or other tool/utility outside the UI? Is there a chance sammy might have just disabled the UI without restricting permissions to the values themselves. Just spit balling.
To clarify, I'm assuming "tether_dun_required 0" is an attempt to disable the authorization verification method by changing the flag to zero. Could there be some way to edit the value(s) (assuming they're APN related per the previous successful non-root tether enabling method) responsible for failing the "tether_dun_required" method?
Click to expand...
Click to collapse
There are other methods, but they involve editing a database file. Unfortunately, you need root for that. Possibly other ways, but I haven't found one that works outside of root as of yet.
themisterwilson said:
It is not working for me. Guess I'll be going back to root. This was really my reason to be rooted, but alas *sigh*
Edit: tried a few times, no go. I can see the change in ADB, it does change the value to 0. Still, after a minute or less it changes back to 1 by itself. Set it to 0, reboot...it's back to 1. Set it to 0, confirm at 0... Still goes back to 1 after a moment. There's no stopping that 1 damnit lol
Click to expand...
Click to collapse
techfuse12 said:
Forgive my naivete if this is obviously not possible for whatever reason but is there a way to directly edit the APN settings via ADB or other tool/utility outside the UI? Is there a chance sammy might have just disabled the UI without restricting permissions to the values themselves. Just spit balling.
To clarify, I'm assuming "tether_dun_required 0" is an attempt to disable the authorization verification method by changing the flag to zero. Could there be some way to edit the value(s) (assuming they're APN related per the previous successful non-root tether enabling method) responsible for failing the "tether_dun_required" method?
Click to expand...
Click to collapse
themisterwilson said:
There are other methods, but they involve editing a database file. Unfortunately, you need root for that. Possibly other ways, but I haven't found one that works outside of root as of yet.
Click to expand...
Click to collapse
I had tried Hotspot edit via adb and had the same issue where it would auto revert back.
I ended up just editing the telephony.db via current KNOX friendly ROOTED ROM.
I may give CDMA Workshop a try later after Nougat update is available.
Then I should be able to keep edited APN indefinitely.
mariano3113 said:
I had tried Hotspot edit via adb and had the same issue where it would auto revert back.
I ended up just editing the telephony.db via current KNOX friendly ROOTED ROM.
I may give CDMA Workshop a try later after Nougat update is available.
Then I should be able to keep edited APN indefinitely.
Click to expand...
Click to collapse
Same here. I'm glad I kept a copy of the telephony.db I modified. Just went back to root and pasted the file and was back in business lol
I know nothing about CDMA workshop unfortunately. Never messed with it.
Works For me! Thanks OP!
maxcala said:
Works For me! Thanks OP!
Click to expand...
Click to collapse
What build are you on? And what exactly did you do (if any) other than the steps in the instructions?
hi all!! well, i have other problem. When i enter to SETTINGS, i dont have HOTSPOT menu. :/ someone can help me? my phone is Note 7 Sprint.
Regards!
I'm on PGC! I turned it on again and I still have it! I don't need root anymore since this is all I need. Where do you guys submit pics so I can link it here?
themisterwilson said:
Same here. I'm glad I kept a copy of the telephony.db I modified. Just went back to root and pasted the file and was back in business lol
I know nothing about CDMA workshop unfortunately. Never messed with it.
Click to expand...
Click to collapse
I have a Note 3 rooted still with Hotspot. Are you saying you transferred this over somehow or would that be something you had on a computer?
Lyvewire said:
I have a Note 3 rooted still with Hotspot. Are you saying you transferred this over somehow or would that be something you had on a computer?
Click to expand...
Click to collapse
No, I had rooted this phone and modified the right database. Just held onto it, just in case. Good thing I did lol
Running PGC and Hotspot confirmed
Greetings One & All,
I am currently using the Sprint Note 7 running PGC Unrooted, I followed the instructions provided in the first post by intenselyinsane and I not only rebooted my phone, I followed up by powering off my phone and restarting it. In both cases I retained my ability to use my Hotspot and Tethering. Like many, this is the primary reason I root my phone and can hold off for the time being until the developers are more comfortable with their rooting methods now that this is available to me.
Thank You intenselyinsane!