Related
Hey guys,
I was hoping someone here could throw me a bone on a problem I am having with a Galaxy Tab 2 I recently got for my wife. For some reason it keeps telling her there is a software update. She has tried to install it multiple times and it appears to go through successfully but the prompt to update comes back again a few hours later. If we click "Later" it gives a a maximum time of 3 hours before it reminds us to update again. i saw someone else had asked about this in another part of the forum and they were directed here but I never found an answer.
So... The numbers:
Model: GT-P3113
Android Ver. 4.0.4
Kernel version: [email protected] #1 SMP PREEMPT TUE JUL 17 23:47:56 KST2012
Build Number: IMM76D.P311UEBLG5
I've gone in through the start menu and cleared the cache, next step I am considering is starting from scratch with a wipe to factory fresh. Before i did that though I thought I would check here.
Anyone have any advice?
**EDIT**
Just for clarification, this appears to be a system update. Not an app or anything like that. If I go intot he preferences and check for a software update it immediately prompts for it.
Rooted? If so, I was told to try to browse system/app folder for the Fota.apk. delete that and reboot. I've basically got the same problem and posed the same question HERE.
Its simple root your device you will get no ota notofications as when device is rooted ota is disabled on it....
And if it still shows up Then freeze software update,fota app and you are done...
Alternatively you can try resetting your tab or flashing a fresh stock rom or any other on your device..,,
Thanks for the replies guys. :highfive:
My wife has no need for a rooted device and I'd rather leave her in the somewhat walled garden on it. Not that she cant handle it but I'd rather not tempt fate with anything. I am after all her tech support. :laugh:
So this morning I decided to run it one last time before I did a factory wipe on it and oddly it took longer to update then on previous occasions. Now when I go check for system updates it tells me no updates are available.
What is strange is that we tried it several times before and nothing changed. Now we are seeing a new Kernel version and build number:
Model: GT-P3113
Android Ver. 4.0.4
Kernel version: 3.0.8-999349
[email protected] #1
SMP PREEMPT Thu Aug 23 23:43:39 KST 2012
Build Number: IMM76D.P3113UEBLH2
Of course murphy's law decided to wait until AFTER I posted here at XDA to get the update installed properly.
Ah well... At least it is resolved.
Droidlover123 said:
Its simple root your device you will get no ota notofications as when device is rooted ota is disabled on it....
And if it still shows up Then freeze software update,fota app and you are done...
Alternatively you can try resetting your tab or flashing a fresh stock rom or any other on your device..,,
Click to expand...
Click to collapse
Actually, I've been having the same problem. One thing I've noticed is that all of the Roms out there for SGT2 appear to be for the wifi/retail models (GT-P3xxx). The verizon models aren't versioned that way. It is simply the SCH-I705 (no GT-P model designation). Therefore, and correct me if I am mistaken, there are no roms compatible with this hardware.
Also, My device is rooted, I still get OTA notifications. For my device, there is no fota.apk in the system/apps folder, so I either need to find a rom that will work with this phone, unroot/update, or do a factory reset and hope it fixes it. Right now I'm pretty frustrated with this damn thing...
Hi,
I have a 1+ yr old Galaxy S3 (so out of the warranty period). I'm getting camera fail messages. When it's not working, here's what happens:
When I try to use the stock camera app, it goes into the camera interface, hangs for a bit, and then I get a message saying "Camera Failed"
If I try to use another app that uses the camera, I get a message that the camera is in use.
So it seems to me like there is some app that is hijacking my camera, rendering it unavailable. I got in touch with Samsung tech support, and they had me reboot into safe mode, test the camera, and then reboot normally. That works to reset the camera, and I can then access it, until it happens again.
Does anyone know what the problem might be, or which app might be interfering? Is there a way to get a list of all apps that use the camera, so I could do some trouble shooting?
Thanks in advance for any help you can give.
Could you post your about phone details? Are you sure you have a Verizon Galaxy SIII (sch-i535)? Because we do not have a stock, non-rooted 4.2.2 rom.
Oops, 4.1.2, not 4.2.2
SlimSnoopOS said:
Could you post your about phone details? Are you sure you have a Verizon Galaxy SIII (sch-i535)? Because we do not have a stock, non-rooted 4.2.2 rom.
Click to expand...
Click to collapse
Yes, and I made a mistake in the title, it's 4.1.2, not 4.2.2.
Model SCH-I535
Android 4.1.2
Baseband version 535VRBMF1
Kernel Version 3.0.31-1152558 [email protected] #1 SMP PREEMPT Sat Jun 8 17:20:08 KST 2013
Build Number JZO54K.I535VRBMF1
Hardware Version I535.10
seattlecubsfan said:
Yes, and I made a mistake in the title, it's 4.1.2, not 4.2.2.
Model SCH-I535
Android 4.1.2
Baseband version 535VRBMF1
Kernel Version 3.0.31-1152558 [email protected] #1 SMP PREEMPT Sat Jun 8 17:20:08 KST 2013
Build Number JZO54K.I535VRBMF1
Hardware Version I535.10
Click to expand...
Click to collapse
Ahh, ok haha kinda got my hopes up for a second lol hmm, as a stock user, your options are kinda limited. What I can suggest is that you use Odin (a Windows program) to flash VRBMB1 firmware and see if this will resolve your camera issues. This is the quick and simple method. Essentially doing this will downgrade your modem to VRBMB1 and several files to VRBMB1 4.1.2. Doing this is compatible with all ota's even older ones. You can download the tar file here and Odin from here. You can follow step one in that guide but all you're flashing is the VRBMB1 firmware that I linked. Alternatively, the more complete suggestion is to Odin flash a full 1 GB stock tar which will erase all of your data on the phone and it will be reset to out of the box stock. If your camera does not work still then it would very likely be a hardware issue.
Does anyone know what the problem might be, or which app might be interfering? Is there a way to get a list of all apps that use the camera, so I could do some trouble shooting?
Click to expand...
Click to collapse
I'm not too sure about this question btw. Maybe someone else can provide input on an app or utility that does this? For now, the best I could suggest is uninstalling any apps you know access the camera then trying to add them one by one until you can see the issue.
General Lollipop Information Thread
Since many users asking the same questions over and over again i'm going to start with many "basics" answers for you
Why? because you guys won't use the search button :silly:
Can i revert back to kitkat safely?
Yes And No, If you have upgraded the bootloader.
If you have upgraded with Bootloader you might have some IMEI issues, And afaik there is none that has fixed this. Thus who hasn't updated the booloader can still revert back.
I got no baseband or WIFI
Go to More > About Device
Scroll down until you see baseband. if you don't have HOA7 in the end that means you're wifi won't work with stock kernel
Make sure that you always read the OP and if OP hasn't stated it, you need to update your modem and NON-HLOS.bin
Make sure to uncheck auto reboot before flashing!
Battery life is terrible
Yeah ofc you haven't had the rom for more than x days so it hasn't been fully set.
Can i use CF-Auto Root
NO! People who used this also flashed update-su in recovery, however flashing CF-Auto root isn't needed and it will not work due to old binaries.
How can i root?
http://forum.xda-developers.com/galaxy-s4/general/guide-t3018625
Why does X And Y FC
because you didn't provide logcat.
Why does it takes 2x minutes for it to boot first time?
because samsung made some changes which i can't tell, i've never seen such a slow upgrading screen on lollipop neither on stock versions.
LastStandingDroid said:
General Lollipop Information Thread
Since many users asking the same questions over and over again i'm going to start with many "basics" answers for you
Why? because you guys won't use the search button :silly:
Can i revert back to kitkat safely?
Yes And No, If you have upgraded the bootloader.
If you have upgraded with Bootloader you might have some IMEI issues, And afaik there is none that has fixed this. Thus who hasn't updated the booloader can still revert back.
I got no baseband or WIFI
Go to More > About Device
Scroll down until you see baseband. if you don't have HOA7 in the end that means you're wifi won't work with stock kernel
Make sure that you always read the OP and if OP hasn't stated it, you need to update your modem and NON-HLOS.bin
Make sure to uncheck auto reboot before flashing!
Battery life is terrible
Yeah ofc you haven't had the rom for more than x days so it hasn't been fully set.
Can i use CF-Auto Root
NO! People who used this also flashed update-su in recovery, however flashing CF-Auto root isn't needed and it will not work due to old binaries.
How can i root?
http://forum.xda-developers.com/galaxy-s4/general/guide-t3018625
Why does X And Y FC
because you didn't provide logcat.
Why does it takes 2x minutes for it to boot first time?
because samsung made some changes which i can't tell, i've never seen such a slow upgrading screen on lollipop neither on stock versions.
Click to expand...
Click to collapse
Can u port soundcamp to s4 ?
i've flashed cf autoroot and it works perfectly
i did a completly downgrade,also bootloader and no issues
Sent from my GT-I9505 using XDA Free mobile app
i have installed official lollipop 5.0.1. If I root my phone, I will be able to flash official updates from samsung in the future? or I won't because of triggered knox
ViPER4Android
I managed to install Viper as system app but problem is How do I Activate it? In Sound settings there is No Music fx, (although it's installed), so I don't have the option switch Viper on, let only see Adapted Sound and in custom profile doesn't select it either. Am I missing something or is it because this update is so terrible
great info Droid! saw this thread in your signature
Revert from LL 5.0.1 to KK 4.4.2 is possible even if you flashed the Bootloader!
Personaly tested and working like charm!
No IMEI lost, no issues soo far found....
re
Is it possible to flash i9506 lollipop ROM on E330S?........... They are same hardware wise?
Xain47 said:
Is it possible to flash i9506 lollipop ROM on E330S?........... They are same hardware wise?
Click to expand...
Click to collapse
yeah..they are the same but i don t know if modems are diferent. i think you should not flash i9506 on E330s
I just flashed the latest CM12 and it's great. Also installed TWRP.
The only issue is that now when I boot my P900 shows in red: Kernel is not seandroid enforcing.
Is this a problem and, how do I get rid of it?
Agrajag27 said:
I just flashed the latest CM12 and it's great. Also installed TWRP.
The only issue is that now when I boot my P900 shows in red: Kernel is not seandroid enforcing.
Is this a problem and, how do I get rid of it?
Click to expand...
Click to collapse
your bootloader detects that, so there is no way to get rid of it.
my note 4 does this but I have actually never seen it on my P900, could you give more details on your exact model, rom, and kernel? I'm curious.
one way around that, I think, would be a kernel that is enforcing at boot, then use a script or an app to toggle it back to permissive (if necessary for your purposes)
edit: oops I see now -- CM 12, but still.. are you using the lollipop bootloader from the official update?
Hmmm.... I just rooted my Note Pro last night, stock rom with TWRP (latest). And though it boots up fine otherwise, I'm also getting the "Not SEAndroid enforcing" message. Would like that gone. And it is interesting that CM12 is having the same issue, because I was beginning to think about flashing it and ditching stock Lollipop.
Specifics: I used Odin 3.10 from a Windows 7 laptop for my initial boot flash of the CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 file to the tablet. No errors were reported. I also flashed TWRP 2.8.7 that way. Again, no errors. There was a beta version of SuperSU (2.49) but I didn't install that. Think I'll try it next... and hope for the best. I did install SuperSU Pro (2.46) once I'd booted the tablet, but maybe that's not available on boot?
Sterist said:
could you give more details on your exact model, rom, and kernel? I'm curious.
Click to expand...
Click to collapse
SM-P900 like you.
CyanogenMod Version: 12.1-20150707-UNOFFICIAL-v1awifi
Android version 5.1.1
Kernel version: 3.4.104-g7e89e2e
[email protected] #1
Tue Jul 7 19:20:11 MSK 2015
Agrajag27 said:
SM-P900 like you.
CyanogenMod Version: 12.1-20150707-UNOFFICIAL-v1awifi
Android version 5.1.1
Kernel version: 3.4.104-g7e89e2e
[email protected] #1
Tue Jul 7 19:20:11 MSK 2015
Click to expand...
Click to collapse
but did you at some point OTA or odin to Samsung lollipop before CM12.1?
Sterist said:
but did you at some point OTA or odin to Samsung lollipop before CM12.1?
Click to expand...
Click to collapse
Yes. I OTA 5.0.2.
I guess the big questions are:
1. Is there a fix that doesn't involve jumping back to KitKat?
2. Is having this issue in any way bad other than seeing that message on boot as everything else seems to be working.
Agrajag27 said:
Yes. I OTA 5.0.2.
I guess the big questions are:
1. Is there a fix that doesn't involve jumping back to KitKat?
2. Is having this issue in any way bad other than seeing that message on boot as everything else seems to be working.
Click to expand...
Click to collapse
I don't think there would be a way to go back to kitkat, even if you wanted to, after having installed the lollipop bootloader (happens when you OTA or Odin to stock lollipop)
to the user it's no problem at all -- it's just a visual notification to stores when you take the device back that it's been customized / modded, and voids the knox warrantee hence "Set warrantee bit: kernel"
knox, despite popular belief, is just a form of security and productive software for corporations to rely on when giving their employees a "work phone" to use, so they know that any potentially sensitive corporate information is safe from the security risks of rooting (though virtually never exploited, rest assured)
that's the most relevant answer I can give you, without repeating what I explained in my previous post *hint* lol
Slightly confused about something I'm seeing. The error is that it's NOT enforcing, but Settings, About Tablet says it IS enforcing.
Also, you mention setting to Permissive with an app (which I've found) but that sounds like it won't be enforcing either and thus we'll still have the message.
Agrajag27 said:
Slightly confused about something I'm seeing. The error is that it's NOT enforcing, but Settings, About Tablet says it IS enforcing.
Also, you mention setting to Permissive with an app (which I've found) but that sounds like it won't be enforcing either and thus we'll still have the message.
Click to expand...
Click to collapse
the display at boot is not an error, just a notification of sorts.
the only thing I can think of is the CM maintainer may have compiled the kernel to boot as permissive and switch back via script for compatibility.
I have seen some roms that do this. not many, nor recently. I wouldn't worry about it though, especially since it's a Wi-Fi device that doesn't have any reason to visit a carrier store.
also note that the notification will show when booting a permissive recovery kernel -- these notifications are not permanent nor need to be "cleared" or "reset" they just inform the user (or technician) of the S.E.A. mode of the respective kernel at the time of boot.
Thanks. I can live with that. I'm a bit OCD and an old QA professional so it'll give me pause every time I reboot and see it, but I'll get over it. <grin>
Otherwise, I have to say, the tablet is working better than EVER with CM 12.x. Apps that caused crashes no longer do. Bluetooth keyboard works again. It's faster. I have only a single bug (the running apps list sometimes has graphic issues).
I' m hoping some experts can chime in.
I rooted PK1 about 10 days ago. Followed the Verizon S7 forum that had clear instructions, and used the v15 fixes + debloater.
I made sure the governors were set to interactive.
Despite all this, my phone was extra buggy and had lag, compared to stock. It seemed to get worse with time.
Then on day 6, after root, my phone started boot-looping on the tmobile logo and vibrated.
I un-rooted back to PIA, and tmobile still seems to be monitoring hotspot use, I thought was part of the PK1 OTA.
So, my questions are:
1) are those rooted on PK1 stable, like stock? OR is there still stability issues, beyond adjusting the governors to interactive?
2) what are people using to successfully circumvent tmobiles new hotspot throttle. ( .5kbs or pay $25 per month).
xtether module in xposed, or WiFi Tether Router (root). ??
what is working?
thanks in advance !
I'm not on the PK1 firmware yet, but I just upgraded from PG1 to PIA.
As far as performance goes, I found this thread VERY helpful: http://forum.xda-developers.com/ver...uide-fine-tuning-performance-battery-t3417804
Maybe it will serve well for you as well. As far as rooting is concerned, not too sure from personal experience, but I heard the ENG boot works with the newest firmware and I'm guessing the modified SU should work for it too.
If you would like to try reverse engineering the files yourself, maybe these guides will help out:
http://arm.ninja/2016/03/04/reverse-engineering-samsung-s6-modem/
http://forum.xda-developers.com/android/software-hacking/how-to-reverse-engineer-kernel-t3137384
http://www.fortisfio.com/extract-android-rom-for-reverse-engineering/
In regards to removing bloatware, I prefer removing apps over services because you never know when you might need a service that you accidentally removed from a previous time. Also I've been going through many cases of trial & error with removing bloatware and a few times ended up messing up other apps in the process that would force crash, but with my current setup everything seems to be working well.
If you need help with removing bloatware, there are 3 apps that really helped me out.
https://play.google.com/store/apps/details?id=com.piriform.ccleaner <-- Surprisingly ccleaner is awesome for the android as well as the PC.
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en <-- this is very useful as well
Another tool I found very great and you run this from your computer is Debloater: http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Hope this helps. I'm trying to currently work on a way of creating custom odin flashable roms so I can optimize roms to the best of my ability and provide the community with more options as well. This is still a work in progress though. :S
EDIT:
Here is an output of my program list. It was too long for me to post directly in the message
adb shell pm list packages -f
thanks a lot!
I have read about ENG boot being an improvement as well, yet nobody is stating that it is stable as it is prior to root, just improved lag, performance and stability. I know in my experience, root, for the first time in 8 years of rooting is not worth the benefits. This is sad. Must be stable. (in addition -no roms, no nanroids, no samsung Sumsung Pay..etc..etc..) So I'm hopeful things will change soon, or will be forced away from Samsung. Tmobile privacy invasion issue, and bait-and-switch with their plans is even further less encouraging news. Imagine "unlimited" = less.... wow.
Well said, and I completely agree. I've been a BIG fan of previous Samsung models, but it seems with every new model that comes out there are less and less options for customizations. I'm currently in the process of trying to figure out how to repack tar.md5 files *properly*.
I've gotten close, but then it fails right at the very end. I'm still waiting for a response from someone hopefully with more knowledge than I, but I guess I have to be patient. Here was my thread: http://forum.xda-developers.com/tmobile-galaxy-s7/help/creating-flashable-odin-file-t3500139
Any way, I'd love to see more customization for the S7. I think it's a great phone and it has so much potential. I also love android and always felt it gave users more ability for customization as opposed to Apple. Like you, I just hate all the bloat ware and all the crap that comes on phones these days. Not only that but the markup price is ridicules. Having to pay $600+ for a phone that is "laggy" due to all the bloat on it is frustrating to say the least. This is why I'm trying to give the community more options or at least steer them in a direction to customize their devices easier. Currently despite all the various amounts of software that is provided through this community I feel like there aren't too many people that know how to properly use it.
Any who, good luck with your phone. Let us know if you figure anything out with it. Also, are there any significant advantages with the newest firmware over the PIA? I usually like to hold off from upgrading right away so that all the "kinks" get worked out first since it's difficult to downgrade afterwards.
xena499 said:
I' m hoping some experts can chime in.
I rooted PK1 about 10 days ago. Followed the Verizon S7 forum that had clear instructions, and used the v15 fixes + debloater.
I made sure the governors were set to interactive.
Despite all this, my phone was extra buggy and had lag, compared to stock. It seemed to get worse with time.
Then on day 6, after root, my phone started boot-looping on the tmobile logo and vibrated.
I un-rooted back to PIA, and tmobile still seems to be monitoring hotspot use, I thought was part of the PK1 OTA.
So, my questions are:
1) are those rooted on PK1 stable, like stock? OR is there still stability issues, beyond adjusting the governors to interactive?
2) what are people using to successfully circumvent tmobiles new hotspot throttle. ( .5kbs or pay $25 per month).
xtether module in xposed, or WiFi Tether Router (root). ??
what is working?
thanks in advance !
Click to expand...
Click to collapse
I was rooted stock and I used the fixes.zip , I stopped using the debloater because my phone had issues after.
Its bootlooping because you accepted the security update popup.
You know what, that happened to me once, I forgot. What I needed to do is reflash the ENG boot file then when I got back into the phone, remove and reinstall SU. After your phone restarts, go into playstore --> you apps --> and uncheck "Auto Update" for Super User.
KillerClaw321 said:
I was rooted stock and I used the fixes.zip , I stopped using the debloater because my phone had issues after.
Click to expand...
Click to collapse
thanks I tried going back to PIA and used fixes only, as the debloater might be the culprit !
I got it work now here:
@xena499 How were you able to downgrade the firmware? I tried downgrading through ODIN and it wouldn't let me.
m0d hipp¥ said:
@xena499 How were you able to downgrade the firmware? I tried downgrading through ODIN and it wouldn't let me.
Click to expand...
Click to collapse
yes. If your using the firmware in the verizon rooting forum, that stumped me too. It doesn't work.
Must be PIA (sept 27) or newer. I got the firmware from here The sammobile site.
and flashed fine with odin. Then used the established root method from the Verizon forum, using only the V15 fixes and NOT the bloatware remover.
Still testing the root stability (2 days driving). Seems ok, but not as stable as stock so far, but acceptable for me. Cool, no battery drain, but have noticed some lag/ and buggy things that I'm deciding whether or not was a settling that was not apparent on stock w/o root.
In addition, when I was given this loaner phone from the N7, the store migrated all my data and apps using the built in sammy prog. I was concerned how this would affect my phones performance in the long run. 3 "upgrades"/ swaps later of the same technique of migrating apps/settings/data between different phones took it toll. So the bootloop issue earlier forced me to unroot and start fresh, without a choice.... The proper PIA flashed on my device (no root of course) was rock-sold stable for the few days I tried it.
xena499 said:
yes. If your using the firmware in the verizon rooting forum, that stumped me too. It doesn't work.
Must be PIA (sept 27) or newer. I got the firmware from here The sammobile site.
and flashed fine with odin. Then used the established root method from the Verizon forum, using only the V15 fixes and NOT the bloatware remover.
Still testing the root stability (2 days driving). Seems ok, but not as stable as stock so far, but acceptable for me. Cool, no battery drain, but have noticed some lag/ and buggy things that I'm deciding whether or not was a settling that was not apparent on stock w/o root.
In addition, when I was given this loaner phone from the N7, the store migrated all my data and apps using the built in sammy prog. I was concerned how this would affect my phones performance in the long run. 3 "upgrades"/ swaps later of the same technique of migrating apps/settings/data between different phones took it toll. So the bootloop issue earlier forced me to unroot and start fresh, without a choice.... The proper PIA flashed on my device (no root of course) was rock-sold stable for the few days I tried it.
Click to expand...
Click to collapse
Thanks for the response. I have a SM-G930T and the firmware I am running currently is the " G930TUVU4APIA" stock. I just am using the ENG boot file and removed a bunch of apps myself (not using the v15 debloater or fix). Any way, the PIA firmware is still a little sluggish for me, and I was thinking of going back to "G930TUVU3APG1", but every time I try to flash it through ODIN I get an error. Something similar to "SW. REV CHECK FAIL : FUSED : 4, BINARY : 3".
And I didn't think that a verizon firmware would work on a tmboile phone? They're completely different hardware? Like GSM vs CDMA? Or am I missing something?
m0d hipp¥ said:
Thanks for the response. I have a SM-G930T and the firmware I am running currently is the " G930TUVU4APIA" stock. I just am using the ENG boot file and removed a bunch of apps myself (not using the v15 debloater or fix). Any way, the PIA firmware is still a little sluggish for me, and I was thinking of going back to "G930TUVU3APG1", but every time I try to flash it through ODIN I get an error. Something similar to "SW. REV CHECK FAIL : FUSED : 4, BINARY : 3".
And I didn't think that a verizon firmware would work on a tmboile phone? They're completely different hardware? Like GSM vs CDMA? Or am I missing something?
Click to expand...
Click to collapse
NO you need the Tmobile files, available in links here, or better from the sammobile.com site i mentioned above.
I would never flash verizon firmware on a tmobile-connected phone.
In addition, are you following the verison unroot method from the verizon s7 rooting guide? the verizon root references for me were just where the best info is for all S7 people, but the software links are to older firmware that didnt work...
Basically, you are using odin to flash ALL files at once (ie AP, BL, CP, CPC), then you are back at tmobile stock as per date of package used (PIA, PG1..etc).
Earlier versions before PIA do not flash, for me. I believe this is b/c i took an OTA security update that did something to prevent this. PIA worked fine for me, and is working not bad.
I'm satisfied for now, and I will wait for stable Nougat before anything else, and done with customizing and playing.
I hope this helps you
m0d hipp¥ said:
Thanks for the response. I have a SM-G930T and the firmware I am running currently is the " G930TUVU4APIA" stock. I just am using the ENG boot file and removed a bunch of apps myself (not using the v15 debloater or fix). Any way, the PIA firmware is still a little sluggish for me, and I was thinking of going back to "G930TUVU3APG1", but every time I try to flash it through ODIN I get an error. Something similar to "SW. REV CHECK FAIL : FUSED : 4, BINARY : 3".
And I didn't think that a verizon firmware would work on a tmboile phone? They're completely different hardware? Like GSM vs CDMA? Or am I missing something?
Click to expand...
Click to collapse
Getting the same Error while flashing from PK1 to PG1... My phone getting hot after PK1 update. Please help.....
Any luck?
sardor_x_z said:
Getting the same Error while flashing from PK1 to PG1... My phone getting hot after PK1 update. Please help.....
Click to expand...
Click to collapse
I need help with the G930TUVU4APK1 update as well. I can flash the TAR file, but I cannot run the root files.
silversusanoo said:
I need help with the G930TUVU4APK1 update as well. I can flash the TAR file, but I cannot run the root files.
Click to expand...
Click to collapse
I just rooted mine this morning. I played around with it a few times. What worked for me was run root.bat with my phone unplugged then plug it in. It took a few minutes for everything to go through. Hope this helps.
Sent from my SM-G935T using XDA-Developers Legacy app
Also would like to know bypass for limited tether greatly appreciated
Sent from my SM-G935T using XDA-Developers Legacy app