Related
can anyone help to mod. a clean stock rom for Huaweil G700?
I bought this one ex China, it is quite a nice smartphone, well built and good hardware. yet I have some problems: since this model is only in China available, the phone comes with lot of for China-Markt specified apps, which I don't need. and the google app paket is missing completely.
I rooted the phone last night and cancelled the china apps with root explorer, it worked. then i installed the Gapps with recovery, it worked too. then I recovered the phone with Titanium, restart, since then, the phone hanged. it took over 30 mins and the phone didn't boot into system. I had to take out the battery and clear all cache and set it back to fault, otherwise the phone will not start.
my question is: can somebody modify the china-rom to a google stock rom? namley delete the china apps and add the Gapps with multi-language supporting. the phone is relatively new on the markt, bui I think it will find his way to european, for some european user it is quite ultimate: 2GB RAM, 8GM ROM, Quadcore.
there is a link to get the orginal rom for the Huawei G700, regretly I'm nut in this sense to modify the data. I know here are quite a few very capable experts who did excellent jobs in the past. hope some can help to finish this rom for us.
http://www.needrom.com/mobile/huawei-g700-u00-2/
I have an unlocked Lg G2 (D800 AT&T) that I'm using on T-mobile . Both T-mobile and AT&T have released the OTA update to lollipop however my G2 says device is up to date . How do I get the lollipop update with out rooting my phone ????
dawg11 said:
I have an unlocked Lg G2 (D800 AT&T) that I'm using on T-mobile . Both T-mobile and AT&T have released the OTA update to lollipop however my G2 says device is up to date . How do I get the lollipop update with out rooting my phone ????
Click to expand...
Click to collapse
can I use the tmobile update ???
dawg11 said:
can I use the tmobile update ???
Click to expand...
Click to collapse
This is the only way to get the Lollipop update
http://forum.xda-developers.com/att-g2/general/update-to-stock-lolipop-d80030f-root-t3084081
Except of course u get an at&t sim and hope u get the update pushed to u
dawg11 said:
can I use the tmobile update ???
Click to expand...
Click to collapse
you can't nor should use the tmobile update, it will brick your phone. if you don't have a ATT SIM to get it automatically you will have to do it all manually.
Beware the update break quite a couple things, including the battery life that gets all out of wack. I am still reading to check if it makes sense to update or to stay in a firmware that can be use as a daily driver with a good battery life.
ryantek said:
Beware the update break quite a couple things, including the battery life that gets all out of wack. I am still reading to check if it makes sense to update or to stay in a firmware that can be use as a daily driver with a good battery life.
Click to expand...
Click to collapse
I dont kniow what have you read but I have 2 weeks on 5.0.2 on my D800 and the battery is better, its true that the UI its a little bit in the laggy side but i have a lot of widges. The update its worthy, the things I miss from 4.4 are the wireless storage (accesible from the togle menu) and the album widget, everything else its ok for me
I update my D800 to 5.0.2 and I really love it.
danieldp1990 said:
I update my D800 to 5.0.2 and I really love it.
Click to expand...
Click to collapse
which method an ROM did you used?
ryantek said:
which method an ROM did you used?
Click to expand...
Click to collapse
My G2 was on stock 20u , I rooted my device using towelroot and then force the 20y to update. and then the lollipop.
elisi said:
I dont kniow what have you read but I have 2 weeks on 5.0.2 on my D800 and the battery is better, its true that the UI its a little bit in the laggy side but i have a lot of widges. The update its worthy, the things I miss from 4.4 are the wireless storage (accesible from the togle menu) and the album widget, everything else its ok for me
Click to expand...
Click to collapse
I did the OTA (using AT&T sim) and hard reset a few times through recovery to ensure everything was clean to start with. Most things work great, but battery life has been strange. Last weekend it was around 80% charged and I put it down. Came back a few hours later and it was off because the battery died. This morning I took it off the charger after being on all night (showed 100%). Plugged it into my computer and it then showed 33%.
I also see odd things in the battery control panel showing estimated remaining battery life of 48 hours sometimes. If I were to guess I'd say it's an issue with battery calibration, but who knows. My suggestion is to stick to kitkat for now until a newer version of Lollipop is released for the G2. If you do go with the current OTA version of KK, a hard/factory reset is highly suggested.
stroths said:
I did the OTA (using AT&T sim) and hard reset a few times through recovery to ensure everything was clean to start with. Most things work great, but battery life has been strange. Last weekend it was around 80% charged and I put it down. Came back a few hours later and it was off because the battery died. This morning I took it off the charger after being on all night (showed 100%). Plugged it into my computer and it then showed 33%.
I also see odd things in the battery control panel showing estimated remaining battery life of 48 hours sometimes. If I were to guess I'd say it's an issue with battery calibration, but who knows. My suggestion is to stick to kitkat for now until a newer version of Lollipop is released for the G2. If you do go with the current OTA version of KK, a hard/factory reset is highly suggested.
Click to expand...
Click to collapse
You can try instaling (if you have not already done it) a battery calibration app, for me its not a hardware fault but a software one, hope you can resolve it!
elisi said:
You can try instaling (if you have not already done it) a battery calibration app, for me its not a hardware fault but a software one, hope you can resolve it!
Click to expand...
Click to collapse
Thanks for the tip. Trying that now
stroths said:
Thanks for the tip. Trying that now
Click to expand...
Click to collapse
Nthing, you can press the "thanks" button too!
Reviving an old thread but even I have the same requirement. I currently use an unlocked AT&T G2 on Lycamobile (Tmobile MVNO) and never get the Lollipop OTA. It always says the current version is already installed.
My question is, if I get an at&t SIM somehow (does it needs to be activated?), will the Lollipop update show up immediately? Are all the initial issues with Lollipop currently resolved? Is it better to stay off the Lollipop version?
Hi guys,
My girlfriend purchased a brand new Xperia Z3 D6653 not too long ago (about 2 months ago?). I flashed the 5.1.1 pre-rooted firmware for her and it's working fine and all but it does a random reboot every day or so, at random times, with random applications.
I have tried 2 different pre-rooted 5.1.1 firmwares already (yes, the correct model D6653 as well) and it still does it. The System Incident reports don't really say much (in fact you only see details about when it crashed, nothing else), and it seems like Google Play Services is the only thing mentioned in the Application Report.
The same thing also happened (more frequently) when she was on the 5.0 pre-rooted firmware. I'm not sure why, I haven't unlocked the bootloader or anything, it's just stock pre-rooted ROM, that's it. I haven't flashed any other ROMs other than the official pre-rooted ones.
Furthermore, before I flashed the 5.0 and 5.1 firmware for her, the phone came with Android 4.4.4. She used it for a month and reported several crashes as well, so that's with the original factory firmware, unrooted, unmodified etc.
She doesn't run any dodgy or random apps, she's just a typical girl that use Facebook and texting, that's pretty much it. I've done a lot of research on this issue and it seems to be quite common, however there isn't really a solution to this. The same apps she currently use never caused any issues on her older phones.
Also in case anyone asks, the only reason I flashed the pre-rooted 5.1.1 firmware for her is because it makes it easier for me to manage her phone (with Teamviewer, you can remote into the phone as long as it's rooted). Also, I get to backup her phone and do tests etc, makes it easier for me.
Also, I'm not using any custom kernels or overclocking the CPU etc. Everything is just stock but rooted.
Could this be caused by a hardware fault in the phone? I'm not sure what else I can do and would appreciate some suggestions.
Nobody have this issue??
Well, how about you try to flash a full, clean, stock ROM, don't root it, don't install any unnecessary app and see where it goes? If the issue persists, try getting a logcat from the phone and we can take a look at it. If it works fine after returning to stock, there might be a problem with the ROM or some apps you are using.
If it really is Gapps that are causing all the trouble, go to APKMirror and download the latest apps available (Play Services, etc) and see where it goes.
As mentioned already, prior to flashing anything, my girlfriend was running a completely stock, factory version of the phone. It came with Android 4.4.
I could flash a completely stock 5.1 ROM but was hoping that someone would share their experiences or a potential solution to this, considering this is quite commonly asked. I would also like to avoid doing this if possible, because if I were to go back to rooting the device, I'd have to downgrade to v4.4 pre-rooted, then flash to 5.1 rooted with custom recovery. It's just a lot of work for a simple testing that could be answered by others if possible.
Anyway, she didn't have any apps installed other than Facebook and Whatsapp, that's it. I might test with GAPPS and see how it goes, but I thought I'd ask here in case someone knows it's definitely a hardware issue or something else.
i would definitely give a pure stock 5.1.1 a go. I used to get the random reboots on the previous versions but i no longer have such issue.. Make sure you do a clean wipe and do it a few times.
Hi all, it's been a while but I thought I'd post an update and share what I've found/learned so far....
Basically, I'm still getting the frequent random reboots. I've tried reflashing the ROM and also tested out the latest .232 pre-rooted stock ROM, still getting the same issue. I've noticed that other than Google Play Services, sometimes Gapps will crash as well. But most of the time, there's nothing reported in the system or application crash logs. I've tested with everything running as stock, no additional apps installed. I then decided to flash the Minimal GAPPS 5.1.x and that sort of made the phone a bit more stable, but still reboots randomly every now and then.
Later on, I decided to try a custom ROM that still works on a locked bootloader. I found this here:
http://forum.xda-developers.com/z3/development/d6603-23-1-1-28-t3102271
The chef has provided a .232 firmware for you to flash in recovery, as well as the ROM base for the D6603 model. Mine is a D6653, but luckily the chef has also provided a D6653 patch for you to flash as well. I've flashed the ROM like so:
1. Wipe everything except my external microSD in TWRP. So basically, wipe system, data, cache, dalvik, internal storage etc.
2. Install .232 firmware.
3. Install v10.5
4. Install v12.0
5. Install D6653 v5 patch
It boots up fine but after using it for a while, I still get the random reboots. What's interesting is that I've also tried without flashing the D6653 patch, which essentially means I'm running just the D6603 base ROM on my D6653. It works, but still crashes as well. I just found it quite surprising that a D6653 could run a D6603 ROM, but it does make sense considering the main differences is just the baseband/frequencies.
Anyway, I later on decided to flash the pure 5.1.1 stock ROM, still getting the crash. Again, everything is tested on pure stock, no additional apps etc installed.
I'm starting to think perhaps this is a hardware issue on my phone?? I noticed that sometimes, my screen will show a bit of tearing and then it'll crash not long after. BUT, I also know that as soon as gapps or google play services crash, the phone will crash not long after as well.....
In fact, I later on used Titanium Backup to convert Google Play Services from a System to a User app, the phone will just boot into the lockscreen and then restart every time. This is a bit ridiculous because I've done this several times on other phones before and they never had such an issue. Of course, I'm not saying I always run Google Play Services as a User app, but that was just for testing and I honestly don't think it should cause a bootloop just because of that. I've also cleared dalvik and cache by the way, so it doesn't make sense that the phone boots into the lockscreen and then just restarts randomly.
I haven't tried uninstalling Google Play Services completely, but at this point I'm back to square one as I've exhausted pretty much all my options and it's been a complete waste of time. I'm beginning to hate this phone more and more. The only thing left is to unlock bootloader and play with other custom ROMs. But yeah, flashing the .232 firmware didn't fix it, AND flashing pure stock 5.1.1 Android didn't fix it either...
Just wondering if others have the same issue and any ideas what could be causing it? If I provide some Logcat logs, would someone be kind enough to look into this for me?
Update:
I'm still getting the random reboots and I think it's very likely to be hardware related. But sometimes also a bit related to software, specifically with Google Play services. I've had more time to test out a few things since my last update, they are as follows:
- Tested complete stock 4.4 ROM without root. Still crashes every now and then, but not as much compared to 5.0 and 6.0 (doesn't matter if it's stock or custom ROM).
- Finally gave in and unlocked bootloader (backed up my DRM keys of course). I thought perhaps that the stock Sony roms (and even the stock-based Sony custom roms) have issues for some reason. They are all the same base, so I thought I'd do a fair test by trying a completely different based rom, such as AOSP. I've used CM 1.2.1 nightly here:
forum.xda-developers.com/z3/development/rom-cyanogenmod-12-nightlies-xperia-z3-t3010201/page117
And yes, I know that nightly have bugs, but the nightly build as of 2016-03-03 seemed pretty stable according to most users. I've tried various other AOSP based roms and stock based Sony roms (for unlocked bootloaders) and they all produce crashes.
I've flashed custom kernels as well and updated my recovery to TWRP 3.0, but all the same results. On all of the custom ROMs I've flashed, the only thing I've done was setup my Google account (so I have my contacts and Gmail) and that was it. No other apps installed. I wanted to limit the environment down to just the stock setup of the ROM itself, as this helps me rule out any potential bugs caused by 3rd party apps.
Having done all of the above and still resulting in crashes, it's safe to assume that this is most likely unrelated to the software, but hardware. I've noticed that sometimes when I scroll a page too fast and move it up and down with my thumb, the screen will freeze and restart.
However, sometimes I will get crashes related to Google Play Services. Anything that relies on Google Play Services will crash randomly. If you re-open the apps, it just crashes again. If you force stop the app and open it, still crashes. The ONLY fix is to restart the phone. I have tried flashing different GaPPs, starting with the pico and nano versions, as well as the ones recommended by the ROM chefs. Still the same result.
So the conclusion is, I haven't really gotten anywhere with this annoying issue. There's definitely an issue with the phone somewhere, maybe a bit of software related, but mostly hardware.
Ok,,,,here is my plight...
about 6 months ago my s5 became unusable due to the fact that concrete and GS5's dont play well together...becoming more and more frustrated having to use an older phone (HTC ONE M7) i went ahead and threw caution to the wind and bought a new LCD digitizer for my GS5 and hoped for the best...
replaced my digitizer and VIOLA !! my phone booted and was exactly the same as it was the day before concrete and LCD collided..
after booting it up went in to check everything and all seems well....root was still good,,,just had to upgrade everything and move on..
my problem is that since it has been a while there have been so many changes as far as updates,,ROMs,,and other techniques i need to find out the steps to take and what would be my best plan of attack..
i am on MOAR v2.2 NE5 and when i installed that back when i first got the phone tripped KNOX,,but i dont think that is too much of a concern at this point...or is it ??
i have read alot of things about going to Lollipop but am not sure if i need to do anything except find a Firmware and flash it with Kies or if ODIN is a better way to go....it would be great if i were able to just jump right to MM but i know the chances of that happening are <0....
any help would be appreciated
thank you in advance
Well the latest version for this phone currently is Marshmallow, and there is a great mm n5 rom that is still a work in progress, but i reccomend downloading the full marshmallow restore tar file and using odin to update, then flash recovery, and then a rom of your choosing (currently the n5 rom or a version of cm13). But to flash a lollipop rom download the OK4 lollipop restore file (last version of lollipop 5.0) and do the same process.
hadn't heard much so i went ahead and downloaded an OK4 firmware and flashed with ODIN....works flawlessly setting up now
surprisingly enough,,,it kept all of my settings from MOAR.....hafta say that i am shocked.....gotta love Android
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