Develop Bugs

[Q] "Your call cannot be completed at this time" after root

Hi everyone
(ugh retyping this as the first time I hit submit and it went to a blank page without posting)
I have an ATT S3 i747 on the normal ATT Jellybean. I had rooted it with ICS, but after the Kies update it wasn't rooted anymore. I finally got around to rooting it again and had used the "galaxys3root" guy's tutorial the last time. I went to find it again and just clicked on the Root page he had on the front of his website. What I didnt realize is that I was looking at a tutorial for the international i9300 version. I flashed the TAR file with ODIN and it failed. I was then prompted to connect to KIES to fix the phone. I ended up just rebooting the phone and re-Rooting it with the correct version of the files. It started working again and I continued on with my day but had wondered if the failed root messed anything up.
Its been 2 days and my girlfriend told me she is having a hard time getting ahold of me. Yesterday this happened, but this morning it was really bad. From two different phones she would get "Your call cannot be completed at this time", no voicemail or anything while calling my phone. I decided to try it from my work land line and ran into the same message the first 3-4 times I called my cell. Finally the call went through, but the next time if failed again. After this, I called ~9 more times over 10 minutes and they have all gone through fine. The whole time i've had 4 bars and tried turning wifi off/on to see if it made a difference but it did not seem like it.
Is this a fluke with AT&T? Or is this related to what I did with the first root that failed? I dont know what all is changed when flashing the root TAR file, Would "un-rooting" do anything?
I appreciate your help, thanks:cyclops:

79TAKid said:
Hi everyone
(ugh retyping this as the first time I hit submit and it went to a blank page without posting)
I have an ATT S3 i747 on the normal ATT Jellybean. I had rooted it with ICS, but after the Kies update it wasn't rooted anymore. I finally got around to rooting it again and had used the "galaxys3root" guy's tutorial the last time. I went to find it again and just clicked on the Root page he had on the front of his website. What I didnt realize is that I was looking at a tutorial for the international i9300 version. I flashed the TAR file with ODIN and it failed. I was then prompted to connect to KIES to fix the phone. I ended up just rebooting the phone and re-Rooting it with the correct version of the files. It started working again and I continued on with my day but had wondered if the failed root messed anything up.
Its been 2 days and my girlfriend told me she is having a hard time getting ahold of me. Yesterday this happened, but this morning it was really bad. From two different phones she would get "Your call cannot be completed at this time", no voicemail or anything while calling my phone. I decided to try it from my work land line and ran into the same message the first 3-4 times I called my cell. Finally the call went through, but the next time if failed again. After this, I called ~9 more times over 10 minutes and they have all gone through fine. The whole time i've had 4 bars and tried turning wifi off/on to see if it made a difference but it did not seem like it.
Is this a fluke with AT&T? Or is this related to what I did with the first root that failed? I dont know what all is changed when flashing the root TAR file, Would "un-rooting" do anything?
I appreciate your help, thanks:cyclops:
Click to expand...
Click to collapse
Well rooting itself doesnt cause the phone to stop working in theory. But it can cause issues if dont incorrectly. So you said you installed the wrong TAR file, that would cause the issue of the phone not booting properly. Id suggest flashing the right TAR file from that site. It will overwrite your incorrect one.
If this still causes issues, Id suggest just use Kies and Initialize the phone back to stock Jellybean by just clicking the Emergency Repair/Initialization and it will ask for your model put in "SGH-I747" and it will basically completely erase and initialize the phone to stock. If that still has issues, then you have some hardware issue.
Also make sure in the About screen your IMEI still shows up.
Dixit

dixit said:
Well rooting itself doesnt cause the phone to stop working in theory. But it can cause issues if dont incorrectly. So you said you installed the wrong TAR file, that would cause the issue of the phone not booting properly. Id suggest flashing the right TAR file from that site. It will overwrite your incorrect one.
If this still causes issues, Id suggest just use Kies and Initialize the phone back to stock Jellybean by just clicking the Emergency Repair/Initialization and it will ask for your model put in "SGH-I747" and it will basically completely erase and initialize the phone to stock. If that still has issues, then you have some hardware issue.
Also make sure in the About screen your IMEI still shows up.
Dixit
Click to expand...
Click to collapse
That is what I did to get it working again was flash the correct TAR file. the IMEI still shows up. It sounds like the issue is still happening so I may back it up with titanium and reset it.

[Q] Failed Sprint Note 2 Root Stuck in Loop, Dev not answering

I attempted a root on Samsung Note 2 Sprint version (in white). Followed all steps, however phone got stuck in a reboot loop right after I put the option 2 (root only) Odin step in. Sprint ver LPH889 (I believe that is what Odin is calling it, option 72). Toolkit used was ADB 4.1.0.
Original symptoms were that the Android updater was looping trying to load everything; being new I made it worse and tried recoveries and reloads which also failed. Now it boots, goes to splash, circling blue oval image and...it stays there.
Good news: I have access to download mode and recovery reset mode (including sideloading).
Bad news: every thread I've followed has given me an issue.
I have recovery access but I need some idea of where to go from here and searches have shown near but not exact symptoms. I have unplugged it from the pc, removed the battery, done a factory reset, attempted to reflash via Odin (root) attempted to reflash stock via Odin and so far I am still stuck in a reboot loop. Windows detects the phone but shows a problem in device manager because possibly it won't stop rebooting. Any help you can provide is appreciated and if at all possible I need to recover some form of working phone here, and soon. My girl needs it for work and Sprint's network in my area barely works from day to day (which they admit but don't credit my account for). This phone has problems sending/receiving calls, they claim it's fine, and I was forced to try a root to get some form of working device. That failed too.
I'm a newb at this...it's been years since I flashed a phone (Razor v3), so...any help would be appreciated, otherwise I have to crawl to sprint/samsung and get it replaced, which I don't want to do. Thanks.

doesitwork? said:
I attempted a root on Samsung Note 2 Sprint version (in white). Followed all steps, however phone got stuck in a reboot loop right after I put the option 2 (root only) Odin step in. Sprint ver LPH889 (I believe that is what Odin is calling it, option 72). Toolkit used was ADB 4.1.0.
Original symptoms were that the Android updater was looping trying to load everything; being new I made it worse and tried recoveries and reloads which also failed. Now it boots, goes to splash, circling blue oval image and...it stays there.
Good news: I have access to download mode and recovery reset mode (including sideloading).
Bad news: every thread I've followed has given me an issue.
I have recovery access but I need some idea of where to go from here and searches have shown near but not exact symptoms. I have unplugged it from the pc, removed the battery, done a factory reset, attempted to reflash via Odin (root) attempted to reflash stock via Odin and so far I am still stuck in a reboot loop. Windows detects the phone but shows a problem in device manager because possibly it won't stop rebooting. Any help you can provide is appreciated and if at all possible I need to recover some form of working phone here, and soon. My girl needs it for work and Sprint's network in my area barely works from day to day (which they admit but don't credit my account for). This phone has problems sending/receiving calls, they claim it's fine, and I was forced to try a root to get some form of working device. That failed too.
I'm a newb at this...it's been years since I flashed a phone (Razor v3), so...any help would be appreciated, otherwise I have to crawl to sprint/samsung and get it replaced, which I don't want to do. Thanks.
Click to expand...
Click to collapse
What method are you using to root.....I used the "toolkit" and had no problems at all.
http://forum.xda-developers.com/showthread.php?t=1957155....try this if you haven't already

vel7wil said:
What method are you using to root.....I used the "toolkit" and had no problems at all.
http://forum.xda-developers.com/showthread.php?t=1957155....try this if you haven't already
Click to expand...
Click to collapse
I thought it would to but I did not want to dig through 70+ pages of the thread when searching failed...unless I really needed to. Most of it is old and doesn't apply.
I was directed by the referenced Youtube vid. I used the options referenced for the phone in this thread with that toolkit. I backed up existing files (not as one unit, but internal files and I think OS), went for the option 2, followed the instructions and things went great through odin...until android went to update and started looping with the 'updating files' percentages. At that point I tried to restore to basic and started clearing caches and such and that is how I got to where I am.
When that failed I started looking at the leaked stock flash and that failed on shoot.ini which that guy never addressed because he thought his international version was all versions (that's why I choose 'doesitwork?' as screen name ). So i'm down to sideloading or something. I really need guidance, and I emailed the toolkit author but I'm still waiting on a reply.
Any thoughts?

doesitwork? said:
I thought it would to but I did not want to dig through 70+ pages of the thread when searching failed...unless I really needed to. Most of it is old and doesn't apply.
I was directed by the referenced Youtube vid. I used the options referenced for the phone in this thread with that toolkit. I backed up existing files (not as one unit, but internal files and I think OS), went for the option 2, followed the instructions and things went great through odin...until android went to update and started looping with the 'updating files' percentages. At that point I tried to restore to basic and started clearing caches and such and that is how I got to where I am.
When that failed I started looking at the leaked stock flash and that failed on shoot.ini which that guy never addressed because he thought his international version was all versions (that's why I choose 'doesitwork?' as screen name ). So i'm down to sideloading or something. I really need guidance, and I emailed the toolkit author but I'm still waiting on a reply.
Any thoughts?
Click to expand...
Click to collapse
When used the toolkit a year ago, I found that I had to turned off all firewalls and antivirus apps for it to work properly. Once I did that it worked fine....give it a shot...can't hurt......might even be able to repair what you've done so far.....Good Luck!!!

I'll give this my best shot...download a rooted rom from the development section and place it on your SD card.
Download toolkit from here (I take no credit for this) http://d-h.st/iu0
Put phone in download mode.
Open ODIN and uncheck "auto reboot". Then click "PDA" and add the .tar file (recovery).
Plug phone into PC (make sure to have samsung drivers installed).
Once ODIN sees the phone you can click "start".
When the recovery flash is complete, pull your battery to ensure power down.
Boot into recovery : volume up, home, power all at the same time.
Flash rooted rom.

Toolkit is an extra and unnecessary step.
http://rwilco12.com/downloads.php?d...ung Galaxy Note II (SPH-L900)/Stock ROMs/MC2/
Grab the one click flavor of choice. Use the one with 1090526 in the name as that's the full version.
Open in windows, put phone in download mode and flash. Easy Peasy.
Let me know if you have any issues with this.

Sorry for the late reply, I had some issues with the "catchpa".
The one click fix worked like a charm, thank you! I will soon be making a contrib to the site. It's a shame I couldn't root as easily :laugh: .
I know the level of work that goes into this stuff and the desire to keep on top of new gear while maintaining support for the old and I appreciate the community coming to my aid, so again, thank you!

---------- Post added at 08:14 AM ---------- Previous post was at 07:36 AM ----------
[/COLOR]
doesitwork? said:
Sorry for the late reply, I had some issues with the "catchpa".
The one click fix worked like a charm, thank you! I will soon be making a contrib to the site. It's a shame I couldn't root as easily :laugh: .
I know the level of work that goes into this stuff and the desire to keep on top of new gear while maintaining support for the old and I appreciate the community coming to my aid, so again, thank you!
Click to expand...
Click to collapse
It is usually a pretty common courtesy to hit the "thanks button" when someone helps you out.
I am not at all trying to be mean, just letting you know.

garwynn said:
Toolkit is an extra and unnecessary step.
http://rwilco12.com/downloads.php?d...ung Galaxy Note II (SPH-L900)/Stock ROMs/MC2/
Grab the one click flavor of choice. Use the one with 1090526 in the name as that's the full version.
Open in windows, put phone in download mode and flash. Easy Peasy.
Let me know if you have any issues with this.
Click to expand...
Click to collapse
hello @garwynn im trying to do this same thing.. its been so long since ive odin'd, how would i put TWRP on this now after these steps? i tried goomanager and that didnt work. (couldnt find recovery) and i tried flashing in stock recovery and got a fail . im kind of lost right now and am wondering if there is another way or do i have to do the toolkit? thanks
edit: for some reason, the tool kit links have been pulled by a mod. ..but this video helped me get twrp back. phew. zedomax to the rescue.. http://www.youtube.com/watch?v=7leb9OznhqY

[Q] Any idea how to fix this issue? I'm a noobie who has been trying to trouble shoot

I posted this on the Sprint Note 2 forum as well so I hope this isn't taken as me spamming
I have a Sph-L900 Sprint Galaxy Note 2. About a month ago the device started acting up Saying it couldn't connect to my Samsung Account, and the only way I was able to fix it was a factory reset. That soon turned into not being able to connect to my Google account and knox issues where something was trying to access my device administrator, and the only fix was to keep updating the samsung security police. The device began shutting off and restarting about two to three times a day with the same error notifications popping up on start up. I kept doing a factory reset in order to get ride of the issues but would reappear shortly after.
I have never tried to root my phone because I wanted to wait for my contract to be up before messing around with it.The most I have done is install a few 3rd party apps and use the google launcher apk as my everyday launcher. Eventually because it keep restarting so often I thought I would try to put cyanogenmod on it using the installer app.Unfortunately it kept saying it couldn't communicate with my device and had to abandon that option. A few hours later the phone restarted again but this time became stuck on the Samsung Galaxy Note 2 logo on start up. I tried to another factory reset hoping that would fix it but this is what happened
View attachment 2714536
The whole thing is in red and keeps saying error and fail.
I have no idea what the issue being a noob, but started looking through forums and posts hoping to get an answer. I thought trying to reload the stock rom might be my best bet and started looking into how to unbrick the phone on youtube and forums.
I downloaded Odin and tried [ROM][ODIN]SPH-L900 MK4 (MK4 Modem/Kernel/Bootloader/ROM - Full Restore - Unrooted), Galaxynote2root.com, and QBking77 methods and files for putting factory stock rom back on the phone. I spent all day trying each one only to get "nand write start fail" when trying each tar file on odin.
I wanted to see if someone might actually be able to explain to me the exact issue and hopefully a possible solution.

try entering download mode and connect it to kies and run the emergency firmware reset or something like that (it will ask you some numbers that are writen in the battery slot) try disabling antivirus also, it should work.
best,
aka_sirok
Sent from my GT-N7100 using Tapatalk

When you tried to flash the stock with odin did you re-partition?

Upgrading to KITKAT on rooted Note II
Hi all, I want to install french KITKAT Rom through Odin. Before doing that I want to factory rest it with out external memory card, I believe if I do not do it, it would wipe off all the data from it. Is it possible to reset with out the card ?
Thanks for your help.

toulan said:
When you tried to flash the stock with odin did you re-partition?
Click to expand...
Click to collapse
I didn't re-partition. I keep hearing i need a Pit file for that. Plus A) haven't found one and B) not really sure of the process of how to do so since the videos online keep saying not to select it

mzbeg said:
Hi all, I want to install french KITKAT Rom through Odin. Before doing that I want to factory rest it with out external memory card, I believe if I do not do it, it would wipe off all the data from it. Is it possible to reset with out the card ?
Thanks for your help.
Click to expand...
Click to collapse
Why would you butt in with your question in this thread when the OP's concern is no where close to what your query is,so please post your question in the thread that pertains to it or make a new thread

5.1.1 OTA update not working

My phone is running the BOG5 5.0.1 software and it is a retail edition.
I recieved a notification on my device prompting me that a new update is available (finally! 5.1.1!) I tap "download now", the download eventually finishes and it proceeds to install.
My phone boots into recovery, "installing update" and very shortly after I see the droid triage error and below it says "error!" and then my phone reboots. When I unlock my phone it says, "Sorry, there was a problem updating your SAMSUNG SM-N910V. No changes were made."
I looked under software update in settings and it says "software not updated to N910VVRU2BOK3" and the error code is 410.
I also notice that when I go into recovery it says "dm-verity verification failed...."
I looked in Kies to see if the update was available there, and of course it wasn't. And I can't find the ROM anywhere as of yet to flash with ODIN.
I would appreciate all of the help I can get.
Thank you.

traceestarr said:
My phone is running the BOG5 5.0.1 software and it is a retail edition.
I recieved a notification on my device prompting me that a new update is available (finally! 5.1.1!) I tap "download now", the download eventually finishes and it proceeds to install.
My phone boots into recovery, "installing update" and very shortly after I see the droid triage error and below it says "error!" and then my phone reboots. When I unlock my phone it says, "Sorry, there was a problem updating your SAMSUNG SM-N910V. No changes were made."
I looked under software update in settings and it says "software not updated to N910VVRU2BOK3" and the error code is 410.
I also notice that when I go into recovery it says "dm-verity verification failed...."
I looked in Kies to see if the update was available there, and of course it wasn't. And I can't find the ROM anywhere as of yet to flash with ODIN.
I would appreciate all of the help I can get.
Thank you.
Click to expand...
Click to collapse
I'm having the exact same issue and symptoms, have you made any progress with this? If I find a solution I'll share here too. I've tried Kies and VZW Software Upgrade Assistant, neither finds the update, but I can get it on my retail VZ Note 4, just won't successfully install.

Keiller said:
I'm having the exact same issue and symptoms, have you made any progress with this? If I find a solution I'll share here too. I've tried Kies and VZW Software Upgrade Assistant, neither finds the update, but I can get it on my retail VZ Note 4, just won't successfully install.
Click to expand...
Click to collapse
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.

traceestarr said:
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
Click to expand...
Click to collapse
I have similar issue ,i don't have a update yet showing on my device so i await for it to show up. Please let us know if flashing it makes the difference.

traceestarr said:
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
Click to expand...
Click to collapse
Sounds like something worth trying, I'll watch for an update on how it goes for you. Thanks!

I have found a solution (albeit requires a full wipe, which is worth having 5.1.1 for me)
Firstly, I attempted flashing the "stock restore" file in odin and resulted in an error, I then tried the full firmware instead (mind you for BOG5, if you're having problems on your current version I'd suggest using your current build) with success, proceed with a data wipe in recovery and noticed that the "dm-verity verification failed...." message is now gone and now that bottom area of the screen has information about applying Multi-CSC.
Restart the phone, set up as normal and go straight for the software update. My phone downloaded and installed the update perfectly! For safety just boot into recovery and do a full wipe again, and there you have it!
The stock firmwares for RETAIL SM-N910V are here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937

traceestarr said:
I have found a solution (albeit requires a full wipe, which is worth having 5.1.1 for me)
Firstly, I attempted flashing the "stock restore" file in odin and resulted in an error, I then tried the full firmware instead (mind you for BOG5, if you're having problems on your current version I'd suggest using your current build) with success, proceed with a data wipe in recovery and noticed that the "dm-verity verification failed...." message is now gone and now that bottom area of the screen has information about applying Multi-CSC.
Restart the phone, set up as normal and go straight for the software update. My phone downloaded and installed the update perfectly! For safety just boot into recovery and do a full wipe again, and there you have it!
The stock firmwares for RETAIL SM-N910V are here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
Click to expand...
Click to collapse
Thank you for reporting back with what worked for you. I've tried following the same steps you took, but after flashing the full BOG5 firmware and doing a data wipe and then doing basic setup on my phone, the OTA is still failing, Error Code: 404. I'll try again, but so far no success. Still stuck on the buggy 5.0.1, the version where you can't flash back to 4.4.4....

Keiller said:
Thank you for reporting back with what worked for you. I've tried following the same steps you took, but after flashing the full BOG5 firmware and doing a data wipe and then doing basic setup on my phone, the OTA is still failing, Error Code: 404. I'll try again, but so far no success. Still stuck on the buggy 5.0.1, the version where you can't flash back to 4.4.4....
Click to expand...
Click to collapse
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.

traceestarr said:
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
Click to expand...
Click to collapse
You're right, I thought I had seen that message earlier in the week while trying to get the OTA for 5.1.1 to work, but I didn't write it down. Your description of symptoms matched mine so well I figured it had to be the same issue or something so similar that running through the same process would work for me too.
I may take the phone into Verizon to show them the update fail and see if they are willing to do anything for me....
Glad you got yours up and running, but I am just a little bit jealous

Keiller said:
You're right, I thought I had seen that message earlier in the week while trying to get the OTA for 5.1.1 to work, but I didn't write it down. Your description of symptoms matched mine so well I figured it had to be the same issue or something so similar that running through the same process would work for me too.
I may take the phone into Verizon to show them the update fail and see if they are willing to do anything for me....
Glad you got yours up and running, but I am just a little bit jealous
Click to expand...
Click to collapse
I've found that most times the OTA update fails prior to rebooting to install the update and I get the 404 error I reported earlier. However, when it does make it to the point of doing the OTA update after reboot, after that fails, I get the same 410 error you reported, see attached, and I also the dm-verity fail message in recovery. Then after using Odin to install BOG5, the verity fail disappears, replaced by a Multi-CSC message, I do a complete data wipe/factory reset, set up my basic google account and try the OTA, which fails every time. But once the dm-verity fail is gone, I can try doing an update from external storage, which I've tried with the BOK3 5.1.1 zip file posted here: http://forum.xda-developers.com/not...id-5-1-1-according-to-website-t3290683/page20 However, this still fails to load.
At this point I'm pretty convinced that I some other issue with my phone. I found elsewhere that someone was able to take their phone into Best Buy and have them flash the 5.1.1 update for them via Kies. That is probably my next step.
But I wanted to share what I've tried in case anyone else is experiencing the same dead end or in the off chance that someone has found a solution.
Sure would love to see the full 5.1.1 BOK3 tar.md5 sometime before Marshmallow hits, pretty sure using Odin to install the update that way would work....

traceestarr said:
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
Click to expand...
Click to collapse
The full OTA for 5.1.1 was posted and I was able to update using Odin, following the instructions on this post: http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
Just wanted to update this post with the solution which finally worked for me.

Please Help! - Galaxy S7 (SM-G930W8) not working post root and factory firmware reset

I'm posting this in a few places because I'm not sure which is more active, feel free to move/delete.
The past few hours have been a nightmare. I was trying to root my Galaxy S7 (SM-G930W8) so I could uninstall some of the bloatware and install some apks.
I first went to mobilesiri (Can't post links yet) to try and root my phone. I couldn't find the samsung usb driver but I figured since my phone could connect to my computer and it recognizes it perfectly, it should be fine, so I skipped that step. Through some searches I came across androidmtk's guide which seems a lot more thorough, so I compared the two guides and decided to follow the latter. That being said I downloaded the version of Odin in the first guide as it seemed less risky to do a one-click root than something more advanced, and since they were both using Odin, I figured there's no harm. Running through the steps I hit "start" in Odin and it started working, but it said "reset" when I clicked start, so I thought that was odd. A few auto-restarts later and it said "pass" but when it started to boot up there was a "recovery is not seandroid enforcing" message in red at the top left.
At this point I thought maybe it worked, and the second guide told me to look for SuperSU in the apps, but it wasn't there. What's more is the software update no longer worked, and my device status was custom... basically the worst of both worlds. At this point I figured what's best is to find a stock firmware from Samsung. No such luck, even chatting with live tech support, it seems this is only done through kies, smart switch, or the phone itself. I did find something on Samsmobile which after a painfully throttled 2 hour download, gave me a version of odin they wanted me to use, along with the firmware for my specific model. I went through their instructions word for word, and it seemed to have worked. I booted up my phone, and the status said "official", so I figured it worked.
Not wanting to have all that time go to waste, I tried doing the 2nd guide, (Androidmtk) again, being really careful not to miss any steps. Same red error message, same custom status. I now have the Samsung firmware so I went back to that, and again the status said official, but now I'm having a whole bunch of issues. The keyboard sometimes doesn't come up, I can't type on it when it does, it comes up really late, the shift key flickers, sometimes it will type one character in, then as soon as I type another, it replaces it, so I can't actually type a string of characters together. The manual software update says failed processing after it tries to register the device. I heard that maybe updating through kies might work, except now I can't get the phone to connect to kies, even after running through the troubleshooter and restarting my computer.
I'm at a loss. I would love to have a rooted version of the phone but at this point just a functioning factory reset would be heavenly. Any help would be kindly appreciated!

Initial Steps before Restore
Faster firmware download - Download and Install
Remove any samsung USB drivers.
Close your browser. Reboot computer.
Download G930W8 firmware - https://desktop.firmware.mobi/device:452
The rest follow my Galaxy S7 Canadian Thread
Let me know. :good: