• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

New T-Mobile Firmware Out. --> G930TUVU4PK1

Search This thread

esjames

Senior Member
Nov 8, 2013
398
105
Cheriton
This update brings us up to November security patch.
 

Attachments

  • 1.jpg
    1.jpg
    196.6 KB · Views: 1,524
  • 2.png
    2.png
    184.6 KB · Views: 1,520
  • Like
Reactions: KillerClaw321

jeremyvbk

Member
Feb 10, 2014
47
11
So far it does seem like it was the stated update to enable 256QAM and 64QAM. But for me only the upload speeds have increased, up to Just over 50Mbps. The speeds in general have been varying from 30Mbps-150Mbps dependent on site, but Just days ago I would be roughly 80Mbps almost everywhere I went, up to about 130Mbps
 
Last edited:

m52 power!

Senior Member
Mar 6, 2008
295
55
After updating to this pdanet force closes about 1 minute after connecting it. Seems there's some new system service that is force closing it. Really low move there tmo

---------- Post added at 10:27 PM ---------- Previous post was at 10:17 PM ----------

If anyone can grab the update files and figure out if there's a new service they introduced maybe I can disable it in package Disabler pro. I really need pdanet to work :(
 

CWBPHT

Member
Nov 7, 2016
6
0
Meaning you flashed the kernel, and used the root.bat but supersu doesnt work?

---------- Post added at 04:38 PM ---------- Previous post was at 04:37 PM ----------


Can you root? Or did you try?

I followed the root guide here - http://forum.xda-developers.com/tmobile-galaxy-s7/how-to/root-files-t-mobile-s7-t3488067

I got the boot file flashed and rebooted, but when I run root.bat it just sits there saying waiting-for-device and a security warning pops up on my phone. I have USB debugging enabled and no boot unlock requirement. I had root, then lost it with a previous build and decided to flash stock then update and try again. I'm at my wits end as to what is going on.

Edit - Also, when I type adb devices there are no devices attached, yet I have access to my sd card and phone folders through windows...
 
Last edited:

KillerClaw321

Senior Member
Jan 4, 2015
367
69
I followed the root guide here - http://forum.xda-developers.com/tmobile-galaxy-s7/how-to/root-files-t-mobile-s7-t3488067

I got the boot file flashed and rebooted, but when I run root.bat it just sits there saying waiting-for-device and a security warning pops up on my phone. I have USB debugging enabled and no boot unlock requirement. I had root, then lost it with a previous build and decided to flash stock then update and try again. I'm at my wits end as to what is going on.

Then run the cmd as admin
 

KillerClaw321

Senior Member
Jan 4, 2015
367
69
No dice, its still just sitting there and nothing is showing up with adb devices. I've tried switching usb ports, i'm currently trying to reinstall the adb drivers... I'm on windows 7 btw. Is it possible to downgrade the firmware?
I know it was possible to go from PG1 to PD8, idk about PIA-PG1 or PK1-PG1 ...
 

CWBPHT

Member
Nov 7, 2016
6
0
I know it was possible to go from PG1 to PD8, idk about PIA-PG1 or PK1-PG1 ...

I just tried and it wouldn't work through Odin. Getting really frustrated. Something i've read is that the Samsung Galaxy S7 drivers in the Device Manager can interfere with proper ADB functionality. Should I try removing those drivers?

Edit - Just uninstalled the adb drivers and reinstalled using the Android SDK usb drivers and it worked. I've successfully run the root bat, now I'm in a boot loop which I'm trying to fix with another factory reset. We shall see.
 
Last edited:

KillerClaw321

Senior Member
Jan 4, 2015
367
69
I just tried and it wouldn't work through Odin. Getting really frustrated. Something i've read is that the Samsung Galaxy S7 drivers in the Device Manager can interfere with proper ADB functionality. Should I try removing those drivers?

Edit - Just uninstalled the adb drivers and reinstalled using the Android SDK usb drivers and it worked. I've successfully run the root bat, now I'm in a boot loop which I'm trying to fix with another factory reset. We shall see.
Oh yes after root you will see a bootloop, but its fine. A factory reset will fixthe issues... just let us know if when you setup the phone you have root.
 

KyleK29

Senior Member
Oct 15, 2006
500
34
After updating to this pdanet force closes about 1 minute after connecting it. Seems there's some new system service that is force closing it. Really low move there tmo

---------- Post added at 10:27 PM ---------- Previous post was at 10:17 PM ----------

If anyone can grab the update files and figure out if there's a new service they introduced maybe I can disable it in package Disabler pro. I really need pdanet to work :(


If anyone else can confirm that? You could then send a message to the PDANet app team and maybe they'll work in a workaround of some sort.
 

CWBPHT

Member
Nov 7, 2016
6
0
Oh yes after root you will see a bootloop, but its fine. A factory reset will fixthe issues... just let us know if when you setup the phone you have root.

Got it up and running and even debloated it, got xposed on there, and I'm working on the tuning guide here - http://forum.xda-developers.com/ver...uide-fine-tuning-performance-battery-t3417804

The only minor annoyance I have as of right now is the phone keeps giving me a "health update" telling me that I have to update Samsung +, but thankfully it stopped giving me the stupid security warnings.

Thanks for the help!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    G930TUVU4APK1_CL9507190_QB11413802_REV02_user_low_ ship_MULTI_CERT.rar

    Here are the Odin files:

    G930TUVU4APK1_CL9507190_QB11413802_REV02_user_low_ship_MULTI_CERT.rar
    1
    This update brings us up to November security patch.
    1
    I assume this is rootable via Odin bootloader swap. Does this update finally enable vulkan?

    And how is battery life?

    Thanks ahead of time
    1
    I assumed it was but it doesn't seem to be picked up by the apps. For example dolphin emu doesn't pick it up
    1
    I just updated to PK1 and restored to exactly as before, including all apps/settings. I've used this method more than once on S7/S7E and it has worked well.

    PK1 is rootable with current methods.

    1) Enable/unfreeze all your disabled system apps
    2) FlashFire (FF) backup data and internal storage. Be sure to write to external SD.
    3) Flash via odin to PK1. I downloaded PK1 from sammobile
    4) Let it boot and complete initial, minimally required setup
    5) Re-root, FF fix/debloat, Xposed with the established method
    6) FF a) wipe user data, cache, dalvik, b) restore /data and /internal storage
    7) After boot, re-disable/freeze select system apps

    No FC, no issues, exactly as before, except you're on PK1.