So, I'm having a particularly strange issue here. I recently got this Sprint Note 4 and activated it. However, there appears to be a missing option under settings. Tethering and Hotspot is straight up gone. To clarify, I have pictures attached showing the item listing, and one without it.
Clarifications of troubleshooting I've tried so far:
I have attempted a factory reset of the device
I have attempted to do a reset with ##72786#
I have tried updating Profile, PRL,
I am using a DeOdexed PH4 6.0.1 ROM. I have tried reflashing per instruction (triple wiping Cache, Dalvik, Internal, System, etc)
I have tried flashing a STOCK OTA PH4 ROM to see if it would show up there. It does not.
I called Sprint technical support to reprovision my phone. They pushed out a a reprovisioning that I accepted. No change.
At one point, Wanam/Xposed was attempted to be installed. I checked for system/csc/features.xml. It was not there
http://forum.xda-developers.com/note-4-sprint/development/rom-stock-ph4-bloated-deodexed-t3473610/ is the custom ROM i'm using. However, it doesn't seem like a ROM specific issue.
If I use Activity Launcher or itools, i can access the actual wifi hotspot MENU (the toggle off and on, LAN settings, etc). I can enable it and the system will broadcast the SSID. However, if I try connecting to it, no devices are able to successfully connect.
here is the Activity Launcher referenced, for other readers:
http://forum.xda-developers.com/showpost.php?p=66713935&postcount=7
but anyways, regarding devices not being able to connect, sometimes the data connectivity (through hotspot only, not for the entire phone) will go dead if you don't start using it immediately after first unlocking and activating tether.
in my experiences, if you keep data alive by immediately connecting a device after your first time turning tether on (after unlock) by downloading a large file or somewhat frequently reloading web pages (on the connected device!) -- anything that will keep data sending and receiving -- it will stick, and the data service to connected device issues will stop.
it's not foolproof, it's not a silver bullet, but this is the method to the madness I have learned and worked for me many times when changing roms and even getting new phones.
it's been a couple months since I had to fiddle with it last, so I can't remember if it was necessary to re-unlock after a failed attempt at keeping data alive. you might only have to toggle data off then back on for another attempt.
when I had the problem of connected devices losing internet access, it would only happen after having worked for a few seconds to a few minutes. it'd work then abruptly stop, and this is my "fix"
My issue seems more in line with the devuces failing to validate to begin with. Not losing connection.
I had something like this before, I vaguely recall it having to do with using Odin vs. OTA stock. So did you try wiping your phone completely then Odin the stock PH4 tar, or did you OTA to PH4?
beezar said:
I had something like this before, I vaguely recall it having to do with using Odin vs. OTA stock. So did you try wiping your phone completely then Odin the stock PH4 tar, or did you OTA to PH4?
Click to expand...
Click to collapse
The very very very first time, I OTA'd to PH4. The next two tries were wiping completely and using the PH4 tar file. So both methods have been attempted.
I was referring to loss of internet connection, not signal related. I thought that was clear, sorry
Sterist said:
I was referring to loss of internet connection, not signal related. I thought that was clear, sorry
Click to expand...
Click to collapse
I thought you meant loss of internet connection in the sense of anti-tether provisioning from Sprint. My phone's LTE never goes down (and I am able to still browse the internet from the mobile device while tethering).
The connected devices never successfully "connect". They aren't listed as connected devices under the mobile hotspot. My other Android phone (without mobile data) is forever connecting. My macbook claims it has an assigned IP but is "unable to access the internet". So I'm not sure what the hell is going on with that.
At this point, I have restored my Note 3 as my active device until I get this resolved. I'm willing to re-write everything down to the barest metal I can.
Somebody in another topic mentioned something about PIT. I don't know anything about that sort of thing. My knowledge extends about as far as installing recovery and flashing ROMs.
I'm confident I could follow procedure, but could use a guiding hand on where to go from here.
sounds like the tether unlock method you used was not done correctly, whether by whoever made it or yourself
method 2 in Galaxy Tools should work just fine. there are several threads in the Sprint note 4 seconds that contain the apk or ppl that will pm it to you. the author discontinued the public/free version of the app and now chargers $35+ per person for a 1 time use lol once you get a copy of the free one, make copies and store on multiple devices forever.
it's primarily for Sprint Sammy devices, so you prob won't see much if anything about it here in the collective note 4 forum.
may work on some boost or even tmo, but yeah.
edit:
you'll want either 3.1.5, easy install n msl read broken on MM and less features
or 3.1.8, troublesome install with msl read working but unreliably, more features.
Sterist said:
sounds like the tether unlock method you used was not done correctly, whether by whoever made it or yourself
method 2 in Galaxy Tools should work just fine. there are several threads in the Sprint note 4 seconds that contain the apk or ppl that will pm it to you. the author discontinued the public/free version of the app and now chargers $35+ per person for a 1 time use lol once you get a copy of the free one, make copies and store on multiple devices forever.
it's primarily for Sprint Sammy devices, so you prob won't see much if anything about it here in the collective note 4 forum.
may work on some boost or even tmo, but yeah.
edit:
you'll want either 3.1.5, easy install n msl read broken on MM and less features
or 3.1.8, troublesome install with msl read working but unreliably, more features.
Click to expand...
Click to collapse
Came back around to this, as I am running a multi-rom and am still encountering this issue. I never attempted any hotspot unlockers. The hotspot was missing from the get-go.
Gamemaster1379 said:
Came back around to this, as I am running a multi-rom and am still encountering this issue. I never attempted any hotspot unlockers. The hotspot was missing from the get-go.
Click to expand...
Click to collapse
Just a thought and question: when you Odin stock tar to recover from this condition, are you using the rooted extended power menu to boot to download mode? Or, do you prevent the auto reboot of stock tar flash with Odin options?
A noted developer, @idone from Galaxy Tool app, once shared with me that rooted shortcut or preventing auto reboot can prevent the normal flash of Odin booting to recovery momentarily to set csc options. csc options flashed may not restore on any boots if you skip that initial auto boot.
The suggested method is to power down and pull battery for 30 seconds our more before reinserting battery and manually booting to downloaded mode. And do not uncheck auto reboot or pull battery but use Odin defaults and let phone auto boot. Doing this allows the phone to boot into recovery to do its thing briefly before booting system. I usually just let it perform the setup wizard and didn't activation just in case.
I rarely do the the data profile update or PRL because if letting the phone setup this way and phone prompts to reboot later, I believe this all done. But since this may allow ItsOn to bootstrap initialize, after flashing TWRP and backing up, I wipe internal memory and factory reset before flashing a custom ROM. Data format is optional; I don't always do that.
But if you do all that and don't see hotspot in Settings of stock, that's a problem. Maybe from dead stock, try KIES or Smart Switch to restore latest stock and check again?
Sent from my SM-N920P using Tapatalk
Related
Okay so I have a Samsung Galaxy S4 from sprint, I love the phone it’s great. I was on the mdl update stock rooted and everything was working fine with wifi. Then I did a factory reset updated to mf9 (the latest update) and then rooted it still stock. Now my phone will connect to wifi if I manually connect to it and works fine, however, if I disable and reenable wifi or restart the phone or leave my house and come back, it will not reconnect to my network automatically, I have to select it myself and put the security key in everytime. When I disable and reenable my wifi it will show “secured” under my network, making it seem as if it never tried to save the network in the first place, So it won't automatically connect like it use to on the mdl update, because it seems as if it forgets it when it disconnects.
I tried even connecting and then forgetting the network and then connecting again to see if that would fix it but it didn’t.
The weird thing is that at my work it remembered the network and connects automatically and when I’m in range. And when I’m away from work I can see it saying “not in range”. Why isn’t my home network doing the same thing, and how do I fix this? (btw I really don’t want to do another factory reset if I don’t have to.)
-I have a 2wire 3800HGV-B router.
kickstand03 said:
Okay so I have a Samsung Galaxy S4 from sprint, I love the phone it’s great. I was on the mdl update stock rooted and everything was working fine with wifi. Then I did a factory reset updated to mf9 (the latest update) and then rooted it still stock. Now my phone will connect to wifi if I manually connect to it and works fine, however, if I disable and reenable wifi or restart the phone or leave my house and come back, it will not reconnect to my network automatically, I have to select it myself and put the security key in everytime. When I disable and reenable my wifi it will show “secured” under my network, making it seem as if it never tried to save the network in the first place, So it won't automatically connect like it use to on the mdl update, because it seems as if it forgets it when it disconnects.
I tried even connecting and then forgetting the network and then connecting again to see if that would fix it but it didn’t.
The weird thing is that at my work it remembered the network and connects automatically and when I’m in range. And when I’m away from work I can see it saying “not in range”. Why isn’t my home network doing the same thing, and how do I fix this? (btw I really don’t want to do another factory reset if I don’t have to.)
-I have a 2wire 3800HGV-B router.
Click to expand...
Click to collapse
Okay well I fixed it by unrooting and using odin to go back two updates prior to mf9, then did 2 ota's back to mf9 and rooted again. all is working fine, also fixed the phone's getting too hot problem and battery last longer than ever.
it's your kernel that was causing this...for future reference, if you're on mf9 with the stock mf9 kernel and do not want to have to wipe your phone to fix this, you can use ShabbyPenguin's kernel...i had this issue before on my s4 and this worked for me...why the rooted stock rom doesnt like the stock kernel for wifi blows my mind...lol
How was it going on? Do you still have the problem with the wifi?
Perhaps you can try this: http://forum.xda-developers.com/show...56&postcount=2 (Greatly appreciated and high credit to dajumper's work.)
This works on my I337 NI1 Unlocked Rooted. I uses ES Explorer with Root Explorer enabled.
I went to the "system " folder in the device, scrolled down until I found "build prop" then edited using ES Explorer Note Editor.
yhendra said:
How was it going on? Do you still have the problem with the wifi?
Perhaps you can try this: http://forum.xda-developers.com/show...56&postcount=2 (Greatly appreciated and high credit to dajumper's work.)
This works on my I337 NI1 Unlocked Rooted. I uses ES Explorer with Root Explorer enabled.
I went to the "system " folder in the device, scrolled down until I found "build prop" then edited using ES Explorer Note Editor.
Click to expand...
Click to collapse
the link you refere to, is not properly linked, can u fix it please? having the same issue
Neikosr0x said:
the link you refere to, is not properly linked, can u fix it please? having the same issue
Click to expand...
Click to collapse
I am sorry for the belated response. I think the link might change to http://forum.xda-developers.com/showthread.php?t=2685519
I do apologize for this inconvenience. Good luck.. :good:
Hi,
About two days ago I posted a forum topic about upgrading a relative's AT&T S4 here in Canada (Rogers Wireless). After a while, I was finally able to upgrade the bloody phone to 4.4 from 4.3 by following these two threads: I337UCUFNB1_100%_Stock_Rooted_ROM & I337_MK2toNB1_KeepRoot_OTA.zip and
I337_NB1toNC1_KeepRoot_OTA.zip & I337UCUFNC1_100%_Stock_Rooted_ROM(4/24/2014)
However I now have a problem with the Lock Screen Options, Removing Safestrap, and the Mobile Hotspot. First, when I go to set a PIN for the lockscreen, I only have the two options Swipe and PIN (which doesn't work at all but is an available option) while the rest have this message under them "disabled by administrator encryption policy, or credential storage". I've tried googling a fix but none of the fixes seem to work. It is said in the first thread posted above, that the MK2 bootloader users will experience a lockscreen settings issue but I can't apply the other bootloader provided that resolves the issue as it is stated that it may cause a hardbrick to the phone since I'm on the NC1 bootloader. I'm not sure what can fix the lock screen problem.
My second problem is removing Safestrap. Stated in the second thread above, there is a known issue that Safestrap will force close after updating to NC1, but Safestrap will continue to function normally after. I tried the method of manually uninstalling it by using ES File Explorer and tried deleting the safestrap folder under system/etc/ and the e2fsck file under system/bin/e2fsck, but I get an error that those files/folders can't be deleted even though I gave ES File Explorer root permission.
My third and final problem is the Mobile Hotspot that comes with the phone from AT&T. I tried to run the mobile hotspot today, but I get a message saying that Mobile data not available or Invalid SIM. I'm assuming since this is an AT&T Phone and AT&T is using their own software to override the System Default Hotspot Tether program, It doesn't let you run it without having a AT&T SIM. Is there someway to restore the System Default one that Samsung ships with it's phones and remove or disable the AT&T one?
Thanks.
Bump?
Monkeymo13 said:
Hi,
About two days ago I posted a forum topic about upgrading a relative's AT&T S4 here in Canada (Rogers Wireless). After a while, I was finally able to upgrade the bloody phone to 4.4 from 4.3 by following these two threads: I337UCUFNB1_100%_Stock_Rooted_ROM & I337_MK2toNB1_KeepRoot_OTA.zip and
I337_NB1toNC1_KeepRoot_OTA.zip & I337UCUFNC1_100%_Stock_Rooted_ROM(4/24/2014)
However I now have a problem with the Lock Screen Options, Removing Safestrap, and the Mobile Hotspot. First, when I go to set a PIN for the lockscreen, I only have the two options Swipe and PIN (which doesn't work at all but is an available option) while the rest have this message under them "disabled by administrator encryption policy, or credential storage". I've tried googling a fix but none of the fixes seem to work. It is said in the first thread posted above, that the MK2 bootloader users will experience a lockscreen settings issue but I can't apply the other bootloader provided that resolves the issue as it is stated that it may cause a hardbrick to the phone since I'm on the NC1 bootloader. I'm not sure what can fix the lock screen problem.
My second problem is removing Safestrap. Stated in the second thread above, there is a known issue that Safestrap will force close after updating to NC1, but Safestrap will continue to function normally after. I tried the method of manually uninstalling it by using ES File Explorer and tried deleting the safestrap folder under system/etc/ and the e2fsck file under system/bin/e2fsck, but I get an error that those files/folders can't be deleted even though I gave ES File Explorer root permission.
My third and final problem is the Mobile Hotspot that comes with the phone from AT&T. I tried to run the mobile hotspot today, but I get a message saying that Mobile data not available or Invalid SIM. I'm assuming since this is an AT&T Phone and AT&T is using their own software to override the System Default Hotspot Tether program, It doesn't let you run it without having a AT&T SIM. Is there someway to restore the System Default one that Samsung ships with it's phones and remove or disable the AT&T one?
Thanks.
Click to expand...
Click to collapse
The manual method of removing ss is only for older versions, but good try. (I tried the same thing, myself)
Given the lockscreen and safestrap issues, rather than try and troubleshoot, I recommend starting fresh. It will be easier than troubleshooting. I'm not sure what method you used in the first place, but I've never seen safestrap fc after initial install. Try these steps and see if you have better luck... http://forum.xda-developers.com/showthread.php?p=51130818
***Note - The settings for safestrap are stored in the TWRP folder on your extsdcard. To get get the clean install, you will want to delete that folder before odin back to stock. (If you have any backups stored in there, you'll want to copy them out first.)
As for the hotspot issue, I am not in your situation (ATT phone on another carrier), so I cannot verify if these will work, but they sound good...
1. Do nothing. Maybe Odin back to stock fixed issue
2. http://forum.xda-developers.com/showthread.php?p=53509265#post53509265
3. Following your own advice of moving off ATT software, flash one of the roms in post 2 here that are i9505 based (or Maple Leaf, the Canadian based ROM)... http://forum.xda-developers.com/showthread.php?p=53758259
Hi, I have a very bad problem and need some tips on how to fix the problem. If you successfully fix the problem for me I will pay you a reward of $20 via PayPal or Bitcoin.
I have a Rooted Samsung Galaxy S5 Verizon (SM-G900V) Running Android 4.4.4
Everything has been going fine and I have used my Galaxy S5 with no problems for around 6 months now, however I ran into an issue a week ago. My issue started after I tried changing my Mac Address (Spoofing it). I used PryFi:
● PryFi
*play.google.com/store/apps/details?id=eu.chainfire.pryfi&hl=en&referrer=utm_source%3Dgoogle%26utm_medium%3Dorganic%26utm_term%3Dpryfi&pcampaignid=APPU_1_ujKoVb-zO4Su-AGNiIC4AQ
I granted root access to the application via SuperSU. I also enabled the 'Mac Spoofing While Connected' option.
When I turned off the application my WiFi was fine for a while, I could turn the WiFi on and off, my problem didn't happen until I did a reboot when I rebooted I was unable to turn on WiFi ever again.
The application PryFi broke my entire WiFi, now I am able to only use the Internet with my data connection WiFi does not work at all.
I have tried a few things, however none have been successful yet.
I have did a factory reset and it still has not fixed my WiFi problem.
The WiFi will not turn on at all. It is stuck on Gray.
Bluetooth works fine, however WiFi does not.
If you're able to help me with this issue successfully I will reward you with $20 via PayPal, or Bitcoin.
Thank you,
Ferragamo
Ferragamo said:
Hi, I have a very bad problem and need some tips on how to fix the problem. If you successfully fix the problem for me I will pay you a reward of $20 via PayPal or Bitcoin.
I have a Rooted Samsung Galaxy S5 Verizon (SM-G900V) Running Android 4.4.4
Everything has been going fine and I have used my Galaxy S5 with no problems for around 6 months now, however I ran into an issue a week ago. My issue started after I tried changing my Mac Address (Spoofing it). I used PryFi:
● PryFi
*play.google.com/store/apps/details?id=eu.chainfire.pryfi&hl=en&referrer=utm_source%3Dgoogle%26utm_medium%3Dorganic%26utm_term%3Dpryfi&pcampaignid=APPU_1_ujKoVb-zO4Su-AGNiIC4AQ
I granted root access to the application via SuperSU. I also enabled the 'Mac Spoofing While Connected' option.
When I turned off the application my WiFi was fine for a while, I could turn the WiFi on and off, my problem didn't happen until I did a reboot when I rebooted I was unable to turn on WiFi ever again.
The application PryFi broke my entire WiFi, now I am able to only use the Internet with my data connection WiFi does not work at all.
I have tried a few things, however none have been successful yet.
I have did a factory reset and it still has not fixed my WiFi problem.
The WiFi will not turn on at all. It is stuck on Gray.
Bluetooth works fine, however WiFi does not.
If you're able to help me with this issue successfully I will reward you with $20 via PayPal, or Bitcoin.
Thank you,
Ferragamo
Click to expand...
Click to collapse
Have you done a reflash? A factory reset just wipes /data, won't really fix anything...
Sent from my Tw5ted SM-G900A using Tapatalk
Get TWRP.
Clear Cache, dalvik
clear data, system
Flash stock firmware via odin. Will fix the issue.
Ferragamo said:
Hi, I have a very bad problem and need some tips on how to fix the problem. If you successfully fix the problem for me I will pay you a reward of $20 via PayPal or Bitcoin.
I have a Rooted Samsung Galaxy S5 Verizon (SM-G900V) Running Android 4.4.4
Everything has been going fine and I have used my Galaxy S5 with no problems for around 6 months now, however I ran into an issue a week ago. My issue started after I tried changing my Mac Address (Spoofing it). I used PryFi:
● PryFi
*play.google.com/store/apps/details?id=eu.chainfire.pryfi&hl=en&referrer=utm_source%3Dgoogle%26utm_medium%3Dorganic%26utm_term%3Dpryfi&pcampaignid=APPU_1_ujKoVb-zO4Su-AGNiIC4AQ
I granted root access to the application via SuperSU. I also enabled the 'Mac Spoofing While Connected' option.
When I turned off the application my WiFi was fine for a while, I could turn the WiFi on and off, my problem didn't happen until I did a reboot when I rebooted I was unable to turn on WiFi ever again.
The application PryFi broke my entire WiFi, now I am able to only use the Internet with my data connection WiFi does not work at all.
I have tried a few things, however none have been successful yet.
I have did a factory reset and it still has not fixed my WiFi problem.
The WiFi will not turn on at all. It is stuck on Gray.
Bluetooth works fine, however WiFi does not.
If you're able to help me with this issue successfully I will reward you with $20 via PayPal, or Bitcoin.
Thank you,
Ferragamo
Click to expand...
Click to collapse
The wifi system is corrupted..
if u need to fix this you must get the whole rom(os)...download latest stock rom or any cusom rom and flash it via odin..or recovery..this will fix the wifi problem...always take a nandroid backup before doing any changes to system...even i had this issue on my redmi note 4g but its fixed by nandroid backup..coz i regularly take backup....i hopr this helps
HIT THANKS BUTTON IF ITs HELPED
I am really upset about myself for not taking a backup as stated. I will from now on take backups all the time before doing anything that could corrupt my phone from now on.
I still haven't tested this to see if it will fix my phone, I will test this within the next day or so.
I do have a question, right now I'm on vacation in the Outer Banks with no computer access at the moment. Is there a way to do what I require to fix the WiFi problem without a computer?
Ferragamo said:
I am really upset about myself for not taking a backup as stated. I will from now on take backups all the time before doing anything that could corrupt my phone from now on.
I still haven't tested this to see if it will fix my phone, I will test this within the next day or so.
I do have a question, right now I'm on vacation in the Outer Banks with no computer access at the moment. Is there a way to do what I require to fix the WiFi problem without a computer?
Click to expand...
Click to collapse
Yes you can do it through mobil odin or flashfire, i would wait though incase something goes haywire and you get stuck on vacation with no phone, i've been there, take it from me, you don't.
Sent from my Tw5ted SM-G900A using Tapatalk
Ferragamo said:
I am really upset about myself for not taking a backup as stated. I will from now on take backups all the time before doing anything that could corrupt my phone from now on.
I still haven't tested this to see if it will fix my phone, I will test this within the next day or so.
I do have a question, right now I'm on vacation in the Outer Banks with no computer access at the moment. Is there a way to do what I require to fix the WiFi problem without a computer?
Click to expand...
Click to collapse
better flash twrp or cwm custom recovert and download the stock rom and keep the rom file on sdcard...anytime anywhere you can flash rom...and get fixed....
HIT THANKS BUTTON IF ITs HELPED
---------- Post added at 03:52 PM ---------- Previous post was at 03:52 PM ----------
Ferragamo said:
Hi, I have a very bad problem and need some tips on how to fix the problem. If you successfully fix the problem for me I will pay you a reward of $20 via PayPal or Bitcoin.
I have a Rooted Samsung Galaxy S5 Verizon (SM-G900V) Running Android 4.4.4
Everything has been going fine and I have used my Galaxy S5 with no problems for around 6 months now, however I ran into an issue a week ago. My issue started after I tried changing my Mac Address (Spoofing it). I used PryFi:
● PryFi
*play.google.com/store/apps/details?id=eu.chainfire.pryfi&hl=en&referrer=utm_source%3Dgoogle%26utm_medium%3Dorganic%26utm_term%3Dpryfi&pcampaignid=APPU_1_ujKoVb-zO4Su-AGNiIC4AQ
I granted root access to the application via SuperSU. I also enabled the 'Mac Spoofing While Connected' option.
When I turned off the application my WiFi was fine for a while, I could turn the WiFi on and off, my problem didn't happen until I did a reboot when I rebooted I was unable to turn on WiFi ever again.
The application PryFi broke my entire WiFi, now I am able to only use the Internet with my data connection WiFi does not work at all.
I have tried a few things, however none have been successful yet.
I have did a factory reset and it still has not fixed my WiFi problem.
The WiFi will not turn on at all. It is stuck on Gray.
Bluetooth works fine, however WiFi does not.
If you're able to help me with this issue successfully I will reward you with $20 via PayPal, or Bitcoin.
Thank you,
Ferragamo
Click to expand...
Click to collapse
i am waiting for your reward.....lol
HIT THANKS BUTTON IF ITs HELPED
devwaseem said:
better flash twrp or cwm custom recovert and download the stock rom and keep the rom file on sdcard...anytime anywhere you can flash rom...and get fixed....
HIT THANKS BUTTON IF ITs HELPED
---------- Post added at 03:52 PM ---------- Previous post was at 03:52 PM ----------
i am waiting for your reward.....lol
HIT THANKS BUTTON IF ITs HELPED
Click to expand...
Click to collapse
They dont have a computer to flash a recovery, furthermore, even if they did, or if they used flashfire or mobile odin(assuming they have root), you cant get a recovery on a G900V, attempting your instructions would certaintly brick the phone.
Sent from my Tw5ted SM-G900A using Tapatalk
Ferragamo said:
I am really upset about myself for not taking a backup as stated. I will from now on take backups all the time before doing anything that could corrupt my phone from now on.
I still haven't tested this to see if it will fix my phone, I will test this within the next day or so.
I do have a question, right now I'm on vacation in the Outer Banks with no computer access at the moment. Is there a way to do what I require to fix the WiFi problem without a computer?
Click to expand...
Click to collapse
Ferragamo,
Verizon's S5 has a locked bootloader, meaning any attempt to load/flash/Odin anything besides the factory firmware will fail (and sometimes end up in tears).
It seems that a major cleanup and then reflashing the latest firmware should resolve the issue.
You can follow my directions bellow to get it done at home (takes about 30 minutes on a fast internet connection), but yes, you'd need your computer.
Or you can stop by BestBuy and have them flash a new firmware on your phone for you.
Step-by-step Directions:
1- Start by downloading the correct USB drivers for your phone, and install them (open the exe file as administrator on your PC):
http://www.samsung.com/us/support/owners/product/SM-G900VZKAVZW
2- Download and install Samsung Kies 3 software on your PC:
http://www.samsung.com/us/kies/
3- Back up your files from the phone using Kies or copy your files, photos, etc. to your PC
4- Time to clean the phone! Use the 3-button combo (hold volume up + home buttons and press the power button) to enter recovery.
7- use volume keys to scroll down to factory reset and press power to select it. Select Yes to wipe the phone. And repeat this step one or two more times for good measure.
8- hit reboot phone, once the phone's screen goes blank (phone vibrates), pull the battery. Don't let it boot.!
9- Load up Samsung kies on your PC, select Tools tab, and reinitialize firmware, answer the on screen questions to input your serial number from the sticker inside the phone.
10- Once ready to flash the new firmware, put the battery in and boot the phone to download mode (3- button combo hold volume down+home and press power)
11- connect the USB cable to PC and make sure Kies recognizes your phone, if not uninstall and reinstall the USB driver. Reboot PC etc...
FAQ's
http://www.samsung.com/us/support/answer/ANS00043306/997388244/
Downloading the firmware will take a while depending on the connection speed. The file size is around 1.5-2GB.
Be patient and baby sit it until flashing is done.
Important: Do not break the cable connection, and prevent the computer from going to sleep or turning off during this process!
Happy flashing
Thanks everyone for trying to help me out. I'm still in the Outer Banks as of now (10:41pm EST). I won't be home until around Sunday, so if I'm not able to do this process without a computer it will have to wait until at least Sunday.
I have got a general picture on what I will have to do to resolve this problem. Hopefully when I get home I will be able to fix this situation.
Thank you Commodore for pointing out those nice tips and the guide. I noticed you mentioned I could take my phone to BestBuy, unfortunately in the Outer Banks they do not have a BestBuy as far as I can see. The only store I can find is a Walmart, so that probably will be of no use for me.
I would have gone to a public library to try and fix this issue, however this location has no library kind of dissatisfied a little, but if it did have one I would have took time out of my vacation to fix my phone.
If there is somehow a work around via the phone some how I would be willing to test it and hear it out, if the computer is my only option than so be it.
When I get home and fix this situation I will reward those who have helped and reached myself to restore access to the WiFi on my phone.
Thanks,
Ferragamo
Ferragamo said:
Thanks everyone for trying to help me out. I'm still in the Outer Banks as of now (10:41pm EST). I won't be home until around Sunday, so if I'm not able to do this process without a computer it will have to wait until at least Sunday.
I have got a general picture on what I will have to do to resolve this problem. Hopefully when I get home I will be able to fix this situation.
Thank you Commodore for pointing out those nice tips and the guide. I noticed you mentioned I could take my phone to BestBuy, unfortunately in the Outer Banks they do not have a BestBuy as far as I can see. The only store I can find is a Walmart, so that probably will be of no use for me.
I would have gone to a public library to try and fix this issue, however this location has no library kind of dissatisfied a little, but if it did have one I would have took time out of my vacation to fix my phone.
If there is somehow a work around via the phone some how I would be willing to test it and hear it out, if the computer is my only option than so be it.
When I get home and fix this situation I will reward those who have helped and reached myself to restore access to the WiFi on my phone.
Thanks,
Ferragamo
Click to expand...
Click to collapse
Do you have root? If so try flashfire, i dont have any specific instructions or anything, but it can flash most odin tars, still like i saod before i would wait, i would much rather not have wifi than not have a phone.
Sent from my Tw5ted SM-G900A using Tapatalk
how to fix
I promise, this is not one of those "reset your access point" or "clean your networking settings" question.
Some background: the phone is not rooted, using stock Android with latest OTA update, locked and never been played with. This problem happened all the sudden with no major changes or accidental drops. Bluetooth and Mobile Data works fine, I can receive and makes phone calls too.
The Problem: the phone can discover available access points and SSIDs, connect to them, performs authentication also, but it fails to get an IP. Android tries to get an IP up to 5 times by issuing a DHCP discovery, eventually failing with the message "IP configuration error"
Why is it weird? because I tried all of the following:
- Tried 4 different access points, 4 different brands, configuration and setup, they all produced the same result of "IP configuration error"
- Tried configuring the phone with a Static IP address, that gave me the error "Connected, no internet".
- Performed a "Factory Data reset", no go.
- Flashed the latest 7.1.1 factory image from Google "angler-n4f26i", no go.
- Flashed the first 7.0 factory image from Google "angler-nbd91k", no go.
- Flashed the first 6.0 factory image from Google "angler-mda89d", no go.
- Tried to use the Backup and Rest -> Network Settings Rest, no go.
- Tried to use the Developer Options -> Use legacy DHCP client, no go.
- Enabled tethering on the phone and tried to connect my laptop to it, my laptop can discover the SSID network on the phone, connect to it, perform authentication, but also fails to get an IP address.
At this point I'm running out of options and dunno what to try next, any lead or recommendation from you guys would be really appreciated. RMA is very hard, nearly impossible to perform where I live "Middle East" :/
Help?
Noorish said:
I promise, this is not one of those "reset your access point" or "clean your networking settings" question...
Click to expand...
Click to collapse
How were you flashing? Sideloading OTA images, or unlocked bootloader, full factory image flashing?
On first boot after clean install, exactly what happens when prompted for your Wi-Fi connection? If it fails there, no point in going further into the OS.
Have you tried using a custom kernel like Franco or EX Kernel that handle the Wi-Fi? (To rectify the problem, not what caused it)
Have you tried formatting modem partition and flashing to the latest radio? (v03.78)
v12xke said:
How were you flashing? Sideloading OTA images, or unlocked bootloader, full factory image flashing?
On first boot after clean install, exactly what happens when prompted for your Wi-Fi connection? If it fails there, no point in going further into the OS.
Have you tried using a custom kernel like Franco or EX Kernel that handle the Wi-Fi? (To rectify the problem, not what caused it)
Have you tried formatting modem partition and flashing to the latest radio? (v03.78)
Click to expand...
Click to collapse
Let me try to answer one by one:
How were you flashing? Sideloading OTA images, or unlocked bootloader, full factory image flashing?
I've gone the unlocked boot loader full factory image way. all my images were downloaded from: https://developers.google.com/android/images#angler
On first boot after clean install, exactly what happens when prompted for your Wi-Fi connection? If it fails there, no point in going further into the OS.
It shows a full list of available access points, I select my SSID and provide a password, the authentication succeeds and the phone proceeds to enable the DHCPClient, it broadcasts a request over wireless but never gets an IP, it tried the process again up to 5 times eventually failing with the error message "IP Configuration Error", configuring an IP address gives the error message "No Internet Connection". I've been able to test this today using a 4th access point brand (tried TP-Link, Cisco, Huawei, ZTE), I'm 100% sure that there's nothing wrong with the access points, as everything else I have works just fine (PS4, laptop, wife's mobile, tablet... etc)
Have you tried using a custom kernel like Franco or EX Kernel that handle the Wi-Fi? (To rectify the problem, not what caused it)
I haven't, but will be doing so today or tomorrow and will be reporting back my results. this is a new lead to follow.
Have you tried formatting modem partition and flashing to the latest radio? (v03.78)
This was done in part of the full image flash, I've tried different full images as stated in my original post, so basically I've had 1.29, 3.72, 3.78 and even the latest 3.79 but those didn't work, do you suggest to do the radio image alone? after performing the full image flash?
Noorish said:
Have you tried formatting modem partition and flashing to the latest radio? (v03.78)[/I]
This was done in part of the full image flash, I've tried different full images as stated in my original post, so basically I've had 1.29, 3.72, 3.78 and even the latest 3.79 but those didn't work, do you suggest to do the radio image alone? after performing the full image flash?
Click to expand...
Click to collapse
Yeah, it was more just formatting and flashing the radio separately, but I'm pretty sure the kernel is handling WiFi on our device. Try one of the custom kernels.... you may have a hardware issue. Good luck.
If you have a main modem then access point internet set-up try doing the following steps:
1.) Forget the Wi-Fi network on your phone. Afterwards enable Airplane mode.
2.) Next turn-off your AP and allow 10 seconds to pass.
3.) Then turn-off your main modem and allow 30 seconds to pass.
4.) Once the alloted time has passed sequentially power back on your equipment. So power back on your main modem, allow another 30 seconds, then power back your AP.
5.) Give the AP another 30 seconds after which disable airplane mode, enable Wi-fi then re-attempt to connect.
*I just wanted you to give those steps a shot juat to eliminate the main modem as a possible factor (in case you have such set-up). Your router/AP is clearly not causing the issue so at this point the problem could either be caused by:
A.) A modem glitch preventing an IP to be handed to your phone when it's MAC address is detected.
B.) Or possibly an issue with the phone's Wi-fi hardware.
v12xke said:
Yeah, it was more just formatting and flashing the radio separately, but I'm pretty sure the kernel is handling WiFi on our device. Try one of the custom kernels.... you may have a hardware issue. Good luck.
Click to expand...
Click to collapse
I've been able to install Lineage OS with EX kernel, and I can confirm that my wireless chip is to blame. I ran every possible combination/setup I could think of that involves software, I keep having the same result... sooo.... yup, dead piece of a: https://www.broadcom.com/products/wireless/wireless-lan-bluetooth/bcm4358
blitzkriegger said:
If you have a main modem then access point internet set-up try doing the following steps:
1.) Forget the Wi-Fi network on your phone. Afterwards enable Airplane mode.
2.) Next turn-off your AP and allow 10 seconds to pass.
3.) Then turn-off your main modem and allow 30 seconds to pass.
4.) Once the alloted time has passed sequentially power back on your equipment. So power back on your main modem, allow another 30 seconds, then power back your AP.
5.) Give the AP another 30 seconds after which disable airplane mode, enable Wi-fi then re-attempt to connect.
*I just wanted you to give those steps a shot juat to eliminate the main modem as a possible factor (in case you have such set-up). Your router/AP is clearly not causing the issue so at this point the problem could either be caused by:
A.) A modem glitch preventing an IP to be handed to your phone when it's MAC address is detected.
B.) Or possibly an issue with the phone's Wi-fi hardware.
Click to expand...
Click to collapse
Thanks for the suggestion, but this didn't work. I've been able to do an extra step and test connectivity using 4 different types of access points / modems, even using tethering from different mobiles that was acting as access points. it's no good.
Looks like the only option left is to do a repair with one of the local shops, hopefully they'll know what a Nexus is and how to handle it (it's not officially sold here yet), according to iFixIt, it'll be very hard to do so: https://www.ifixit.com/Teardown/Nexus+6P+Teardown/51660
Thanks for all the help everyone, really appreciated.
Noorish said:
Thanks for all the help everyone, really appreciated.
Click to expand...
Click to collapse
Sorry to hear. This is the first time I've heard of Wi-Fi failing due to a hardware issue. I doubt it is repairable. It may be located on the motherboard, which although readily available is not really economical to replace. May be the end of the road. This appears to be one more blot on Huawei's QA/QC.
Exactly my thought. Never had such a case in my life, and I'm a tier 3 support engineer in network infrastructures. go figure!
To add even more light into the case, I've ran a packet sniffer in my LAN to check if the mobile is performing a DORA against the DHCP service in my network, but nope, there is no trace for it's MAC address or any broadcast messages from the mobile.
This is the second Nexus that I own and have failed within a year of its life span (previously a Nexus 5 owner, charging station at phone died). I think I'm going to give OnePlus a try very soon.
1. Thanks to @FP_XDA and GSMZambia for the great directions found here
2. The other stuff and ideas:
The above method does put the U firmware on your phone. I had trouble getting it to connect to the network. I did try different combinations of files in the AP tar; CP; and CSC, but it would either not connect after a factory data reset or loop with the message about my SIM has changed, please restart.
I tried just flashing the following combinations through flashfire, but maybe this is a Sprint SIM issue and it works on other SIM cards; however, I have Sprint.
The U firmware seemed to work fine on the software. Including boot.img in flashfire would take away the eng_boot and root. I just had trouble connecting to the Sprint network.
Do you need to use the v5 combo file and flash a certain CP/CSC before going through the rooting steps? The U firmware CSC file is different in size, so is it a partition (PIT) issue since that will write the cache.img.ext4 file and those vary in size from stock to the U? Is there a certain order to flash in flashfire to get it to work properly?
Anyway, I downloaded several U CSC firmwares (XAA, XAS, SPR (last two are sprint)), but ran into some network issue every time. The operating system seemed stable, but the lack of connection and some random entries under settings make it so close, but yet so far.
I don't mind the Sprint firmware, but can you unlock additional LTE bands if you use the stock sprint firmware on another carrier?
Thanks for any help!
Here is more info about the Settings submenu options:
Here is some more detailed info:
The submenus under settings give me options like K twophoneservice; T roaming; Giga LTE. I think it is CSC related as those carriers are Korean based. I think this may be my issue along with a few others I've seen on reddit. Just wondering why it says that though. I used the G930U version, so not sure why this would appear.
Any help or suggestions?
Thanks
Bootloop
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.
Aggiedude said:
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.
Click to expand...
Click to collapse
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.
lvpre said:
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.
Click to expand...
Click to collapse
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
XMayhem2099 said:
7. Disable the following packages via bk or adhell
Chameleon
Sprint OMADM
Sprint OMADM Phone Interface
MDMApp
SecurityLogAgent
Security Policy Updates
Security Storage
Click to expand...
Click to collapse
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself
elesbb said:
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself
Click to expand...
Click to collapse
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.
lvpre said:
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.
Click to expand...
Click to collapse
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed?
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.
elesbb said:
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD.
Click to expand...
Click to collapse
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
Click to expand...
Click to collapse
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed? .
Click to expand...
Click to collapse
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.
Click to expand...
Click to collapse
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?
lvpre said:
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
Click to expand...
Click to collapse
Yeah I am currently rooted with the U firmware BL4. I want to upgrade to Oreo, hoping for performance improvements, better battery, etc. But I guess since the Oreo U firmware is still BL4, I can just downgrade if I can't get root back.
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
Click to expand...
Click to collapse
I never mentioned a bootloop? Is this about something else? The point I am trying to address is the loss of Sprint connectivity after flashing eng boot. This is because of the packages that need to be disabled.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
Click to expand...
Click to collapse
So you flash everything, eng boot, and are currently rooted. You then flash the provided file via flash fire, factory reset, and now you no longer are able to connect to Sprint network? When you say "can't connect to Sprint network", are you referring to data or to Sprint network entirely? If you go under your "about phone" section, what does your IMEI and phone number display? Don't actually type it here, but it should be something comprehensible. It shouldn't say "unknown" or a bunch of zeros, etc. [/quote]
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
Click to expand...
Click to collapse
True..
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?
Click to expand...
Click to collapse
I do. A lot of people want to be back to BL4. There is NO difference in the newer bootloaders EXCEPT a special "key" type of thing that prevents downgrading. That is the only thing different. This is why the U firmware is still on BL4 despite having an Oreo update. Sprint changes the BL version just so people like us have extra hurdles to overcome when we want something different. Its very stupid tbh.
But, I would like to help you guys out, however, I AM NOT upgrading to the BL5/6. Noway nohow.
It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.
lvpre said:
It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.
Click to expand...
Click to collapse
Hmm. That's weird. What does your about phone section say for IMEI and phone number? Everything good? I wonder if something is affecting the PRL. Try updating that via settings menu before you flash the firmware and factory reset. The CSC shouldn't really affect that part. I have changed mine multiple times to just eff around and see what/if anything changed. Its more for the phone to know what menu options are available and such. For instance, call recording shows up when its not a US branded carrier.
Sadly I will never flash the newer BL. But I will definitely keep trying via the thread and if you would like to discord or something similar I would be down. School starts in about 2 weeks so I'm basically free till then
sim boot loop
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.
Aggiedude said:
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.
Click to expand...
Click to collapse
Thanks for posting this!!! I'm glad that I wasn't the only having this issue. I tried it again using a different method and still got the SIM boot loop. This method probably works great if you have anything other than Sprint or Sprint MVNO, but something is conflicting like it does during a typical root of the G930P. Anyway, hopefully, someone else will be able to figure this out.