I have a question about, if a SM-G900A is ever fixable for the "Broadpwn" issue.
Now that AT&T has decided to stop patching the SM-G900A back after the April 2017 update, it seemed that the S5 was at the end of usable life using stock ROM without being vulnerable to the "Broadpwn" hack when the wifi is ever turned on or the high accuracy location is turned on as the wifi is turned on to help with location.
With the bootloader being locked by AT&T, on the SM-G900A, the highest version of alternate ROMs we can load is Lollipop (5.0), so that makes me wonder. Will lollipop custom ROMs for the SM-900A ever be patched for the "Broadpwn"? And since we can't load Marshmallow or Nugget with the patch included, is the SM-G900A now ever going to safe usable phone??
Thoughts?
That's exaggerating. Just make sure to turn off WIFI when away from home, the chance that you'll actually be hacked is very small.
More information on broadpwn
BrianSamsungTab said:
That's exaggerating. Just make sure to turn off WIFI when away from home, the chance that you'll actually be hacked is very small.
Click to expand...
Click to collapse
I think you are not informed. Here is some information, including a break down of the hack WITH source code for it that was published.
Yes, turning off wifi will help but what you don't seem to know is that the wifi is turned on from time to time by the locations subsystem to use wifi to get a better location when GPS is not getting a good signal.
https://www.wired.com/story/broadpwn-wi-fi-vulnerability-ios-android/
http://hackaday.com/2017/07/29/broadpwn-all-your-mobiles-are-belong-to-us/
https://blog.exodusintel.com/2017/07/26/broadpwn/
So my question still stands, will Lollipop builds ever get the patch that Marshmallow and Nugget got.? If not then AT&T short sightedness just made our phones vulnerable forever.
Photofix said:
I have a question about, if a SM-G900A is ever fixable for the "Broadpwn" issue.
Now that AT&T has decided to stop patching the SM-G900A back after the April 2017 update, it seemed that the S5 was at the end of usable life using stock ROM without being vulnerable to the "Broadpwn" hack when the wifi is ever turned on or the high accuracy location is turned on as the wifi is turned on to help with location.
With the bootloader being locked by AT&T, on the SM-G900A, the highest version of alternate ROMs we can load is Lollipop (5.0), so that makes me wonder. Will lollipop custom ROMs for the SM-900A ever be patched for the "Broadpwn"? And since we can't load Marshmallow or Nugget with the patch included, is the SM-G900A now ever going to safe usable phone??
Thoughts?
Click to expand...
Click to collapse
Unless we somehow receive patched, compatible, pre-built binaries, we most likely won't have a fix for Broadpwn. Nevertheless, the G900A should be relatively safe.
You can also turn off Location and the setting that uses Wi-Fi to help location services.
BrianSamsungTab said:
You can also turn off ... the setting that uses Wi-Fi to help location services.
Click to expand...
Click to collapse
To be honest I don't believe android respects that setting. I have it and wifi disabled and battery usage will still show wifi being occasionally powered on.
for reference, for other S5 Variants look here: https://forum.xda-developers.com/showpost.php?p=73744951&postcount=8076
('cause google linked me here for my G900F i posted a reply there)
But we are on marshmallow 6.0.1
Though not helpful concerning the worm, the April 1 2017 patch is in fact marshmallow 6.0.1. I have it on my unlocked g900a right now.
For those who use Bluetooth devices on the go there is an even bigger security vulnerability that's been recently discovered. I know Samsung released a patch for the Broadcom issue for foreign variants so perhaps AT&T is waiting on them to release a fix for this new vulnerability and combine them in one update. I can't imagine testing for a simple security update would take this long otherwise.
However it's also possible that AT&T feels this is no longer a priority and simply expects S5 users to upgrade.
Related
So I have the T-Mobile variant of the LG G4. I had it unlocked straight from the carrier a while ago and all seemed well. Recently I noticed a huge amount of battery drain and 4G LTE usage from T-Mobile's pre-installed apps--mainly com.tmobile.pr or something which is the "My Account" app (imagine being at 60% left with 27% of the drain having been an app and only 9% the screen. Yeah, it was that bad)
This I obviously found unacceptable, so I went ahead to try and uninstall the bloatware. Lo, much to my dismay, Tmobile has locked it down so you can't uninstall the bloatware, and you can only disable it. This alone irked me enough that I wasn't satisfied with just a disabling. I knew I wouldn't rest until I had obliterated it.
I've had plenty of android phones over the years and done my fair share of rooting and flashing ROMs and the like, but I hadn't touched that aspect of my G4 because I wanted a dependable device for school and I didn't want to mess around with it. I knew I'd have to root it to get rid of the tmobile bloatware so I went and did that using the Low effort root method (http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765). When this was done a lot of my background processes started to continuously crash. I decided to go ahead and put TWRP as the custom recovery and just go ahead and get some dependable 6.0 ROM, and I found a couple of them.
When I flashed the first ROM, the play store services were crashing so I found the google apps package for marshmallow and flashed that too. It seemed to fix the issue. Yet when I would click on my School's WiFi at the setup (which is WPA2 Enterprise) it would crash and say "Unfortunately WiFi has stopped working." I thought that perhaps I mucked something up in the flashing of the ROM, or that maybe there was an issue with the ROM in general, so I decided to just flash another ROM entirely (after factory resetting it all the way). Along the same time as this I found a slightly more modified and feature packed version of marshmallow by this lad here (http://forum.xda-developers.com/g4/development/h815-genisys-rom-1-0-classic-v10g-t3192649). I decided to go ahead and use this one since it had a h811 version there, that involved flashing a h815 and then flashing a patch.
The "Unfortunately WiFi stopped working" issue persisted, however. I found this odd. I then noticed that if I click any other network that ISN'T the WPA2 enterprise network my school is working that everything seems to work fine.
I went ahead and factory reset it all the way again in the hopes that would fix it. No luck.
I booted it to safe mode and tried to connect to the WiFi network from there. No luck.
I downloaded a third party WiFi app off cellular and tried to connect from there. No luck.
I can't enter the WiFi's name and try to enter directly because it crashes there too.
I can't "Forget" the network as it's never joined that network before so there's nothing to forget. It does let me enter the advanced options but a direct press causes it to crash.
So throughout ROMs and wipes and safe modes and all, this one issue has persisted, where my phone's WiFi will crash when it tries to connect to my school's WPA2 Enterprise network. I've tried plentiful fixes short of flashing back to a 5.0/5.11 stock (which I'm hesitant to do because I read something about phones bricking after they downgrade from Marshmallow using the .kdz files or something?).
I'd really appreciate any help that y'all can provide. I've read these forums for ages but this will be my first time making an account because I can't find anybody else with the same issue and its proving to be quite a pain.
tl;dr wifi isn't working with only one particular network and no fix I've tried under this sun has worked so far. help will be appreciated pls
Have you tried flashing this rom here --> http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-xtreme-rom-v1-0-7-28-15-t3167667
I am using this one here and I have no issues using wifi. I cannot speak for the 6.0 roms because LG has not dropped the sources for the Tmo variant yet.
esjames said:
Have you tried flashing this rom here --> http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-xtreme-rom-v1-0-7-28-15-t3167667
I am using this one here and I have no issues using wifi. I cannot speak for the 6.0 roms because LG has not dropped the sources for the Tmo variant yet.
Click to expand...
Click to collapse
I got the brown leather variant from Tmobile and it only says H811 as far as I can tell. Not sure of if its the "n" version or not.
I have not tried that rom but ill be sure to give it a go, hoping it will help solve the issue. I did some additional testing and can confirm the issue lies with all WiFi networks that employ WPA2 Enterprise security.
Will there be any issue with the Rom when downgrading from Android 6.0? I was reading about phone's bricking when trying to downgrade certain versions or bootloaders on the tmobile variants.
I'm pretty sure going back to stock 5.1 will be fine. The Tmo variant hasnt been upgraded to 6.0 yet and the ports don't update the bootstacks. Read here --> http://forum.xda-developers.com/tmobile-g4/development/global-marshmallow-6-0-port-to-h811-t3232760
Update: It seems that any Android 6.0 flash cuts off the ability to connect to Enterprise wireless networks. I went ahead and flashed to the debloated stock rom on the thread you mentioned, but it cut off the ability to record video. As such, I went for the xTreme version that you mentioned, and flashed the camera restores and all.
Everything works fine now as far as I can tell. I also got rid of the Tmobile applications draining the battery and all that. All should be well. Thanks again for the help
So up till now I hadn't really tried using NFC on my phone since Android Pay didn't support Chase. For the past month or two I've been trying to get it work without any luck.
These are the things I've tried already,
Turning S-Beam Off, leaving Android Beam On
Tried transferring images with HTC M8 (Android Pay works on this one), didn't work, not even a beep
Wiping Data and Cache, to see if any of the apps might have been causing problems.
I'm starting to think my device hardware might be at fault, but before I jump the gun, is NFC/Android Pay working for any of you guys on latest software?
Device Details
Root: No :crying: (Had root when TM was active, but not since)
Android Version: 6.0.1
Security Patch Level: Oct 1, 2016
Build #: G900AAUCS4DPH4
Seeing this issue on both my unlocked x4 running latest build (retus - PWWS27.1.3) and my fiance's Android One variant (running latest I assure you, can't get the info from her atm) where our phones will drop from the wifi in the house, and then immediately reconnect as if nothing happened.
Running a Netgear AC2350 r7500v2 with latest firmware (V1.0.3.26) through Verizon FIOS.
A lot of the reports and issues I'm reading about on other sites sound a lot like what the Pixel devices are going through, albeit they seem to be a little more centered around mesh networks, of which I don't have in use.
So pretty much, anyone else having weird issues relating to wifi on 8.0? If it's possible to go back to 7.1 I might give that a shot just to see if it's for sure an Oreo problem or not.
I had the same issue. I had to disable IPv6. I also got the phone replaced, the replacement does the same thing if IPv6 is enabled.
IPV6 on the router end you mean?
**UPDATE** Just checked, not enabled through my router.
thetolsonator said:
IPV6 on the router end you mean?
**UPDATE** Just checked, not enabled through my router.
Click to expand...
Click to collapse
Yes on the router. Before I upgraded the replacement, I think the WiFi was working fine. Something might be wrong with the Oreo update.
If you contact Motorola, they will replace it, my replacement didn't come with Oreo.
Motorola knows there's issues with the WiFi, but don't seem to care much. Not just the X4, if you search Google, you'll find some of their other phones with WiFi issues too.
tcrapper said:
Yes on the router. Before I upgraded the replacement, I think the WiFi was working fine. Something might be wrong with the Oreo update.
If you contact Motorola, they will replace it, my replacement didn't come with Oreo.
Motorola knows there's issues with the WiFi, but don't seem to care much. Not just the X4, if you search Google, you'll find some of their other phones with WiFi issues too.
Click to expand...
Click to collapse
Yuuuuuuup. Been finding a lot of people with the same problems. Instead of digging up old threads, figured it'd be worthwhile to start one here to bring more attention to the problem.
Now to find out if it's possible to get nougat back on...
Tether was working fine on Nougat, after adjusting Windows with TTL, a changed user-agent, etc., and then in Android adding the "dun" parameter to my APN, but with any Oreo or Pie ROM, it gets incredibly slow, as if I do not have "dun" in my APN, even when using ROMs that allow "dun" in APN.
I'd really like to upgrade from Nougat, but don't want to give up tether.
Has anyone else faced this issue and prevailed?
EDIT:
I flashed OOS Oreo, tried what settings I could with no good results, then flashed 4.5.1 firmware and modem into it to see if older firmware was the solution, tried what settings I could to no avail.
Back on Nougat now, which does the job just fine.
Alas however, I may never be able to buy a new phone, unless Nougat can be installed onto it.
You're certainly not the only one. Tethering support is getting harder as carriers find ways of making it more restricted. There are ROMs and Devs that have worked on it with mixed results. It's possible with enough leg work you might get it working on a particular ROM, if you can get the dev to work with you on it. Otherwise it's luck of the draw whether you can find a ROM that will work in your particular case.
Telephony is getting complicated and there are more people concerned with VoLTE and the like. Look what a mess that still is on custom ROMs.
Does anyone know of any ROMs where this is actively being fixed? That is, one can tether without degradation, as one used to be able to do in Nougat? Tethering works, it's just horribly slow.
pbergonzi said:
Does anyone know of any ROMs where this is actively being fixed? That is, one can tether without degradation, as one used to be able to do in Nougat? Tethering works, it's just horribly slow.
Click to expand...
Click to collapse
NLOS is your best bet. If it's not working already the dev is willing to work with users to resolve issues.
Here's an example of Tethering restrictions getting worse, with Google leading the charge:
https://www.reddit.com/r/Android/comments/9r6r13/tether_dun_required_no_longer_works_on_pixel_3_xl/
I'm surprised Google don't get whiplash in their haste to bow to pressure from US Carriers.
Dirk said:
NLOS is your best bet. If it's not working already the dev is willing to work with users to resolve issues.
Here's an example of Tethering restrictions getting worse, with Google leading the charge:
https://www.reddit.com/r/Android/comments/9r6r13/tether_dun_required_no_longer_works_on_pixel_3_xl/
I'm surprised Google don't get whiplash in their haste to bow to pressure from US Carriers.
Click to expand...
Click to collapse
Thank you @Dirk, and agreed--I'm surprised google doesn't get backlash--maybe not enough people tether?
Also surprised that more devs didn't just immediately address that--maybe not enough devs tether?
I may try NLOS, or the Magisk module--it might work.
Does anyone using NLOS know if tether works properly? I will ask in that thread also.
Hi all! I was wondering if any of you guys have seen this issue before. I have an old Galaxy S10 that I wanted to resurrect for emulation and forgot the reason why I stopped using it was because the Bluetooth functionality, once toggled on, would look like it's trying to turn itself on but never enables.
I've tried:
Installing all updates
Resetting network settings
Clearing Bluetooth app cache / pairings
Wiping the system cache partition
Factory resetting
Re-flashing current and past firmwares
I was able to get Bluetooth to enable and function normally by random after re-flashing the firmware but would quit after 5-10 minutes.
On the S10 and my current phone Pixel 4a (with functional Bluetooth) I went into Developer options to check currently running services to compare. On the 4a the Bluetooth process is listed as having 1 process and 7 services, whereas on the S10 there were only 2 services and were missing services such as SapService, HidDeviceService, BluetoothPbapService, GattService. (I can post in an edit which services are failing to run on the S10 if need be). The Bluetooth process on the S10 will only show up once Bluetooth is toggled even though it doesn't enable, but will stop running, then start running again, rinse and repeat.
So that being said, is this a hardware issue that I'm SOL with? Are there any other remedies that I could try?
Any input would be appreciated. Thanks!
First off, which S10 do you have... Exynos/Snapdragon makes a big difference, but knowing the model number helps a lot in general as well.
What firmware are you on now?
On my 973U (ie, Snapdragon) I have 1 process and 7 services right now (with BT turned on)... on Oreo with January security (I have stayed off A12 because of many reports of issues on it). I can provide more detail later if needed, as well.
.
schwinn8 said:
First off, which S10 do you have... Exynos/Snapdragon makes a big difference, but knowing the model number helps a lot in general as well.
What firmware are you on now?
On my 973U (ie, Snapdragon) I have 1 process and 7 services right now (with BT turned on)... on Oreo with January security (I have stayed off A12 because of many reports of issues on it). I can provide more detail later if needed, as well.
Click to expand...
Click to collapse
I have an SM-G973U (CCT) running G973USQU6GUJ3, which I believe is the last version of Android 11. I've tried Android 10 and 9 firmwares (can't recall which ones) and I've been having the same issue regardless, which makes me think it could be hardware-based.
In a couple of hours I can edit this post with the two processes that do run, if need be.
Made a mistake - my phone is 975U but that shouldn't matter.
I'm on G975U1UES6GUL1 which I believe is a later version than what you have... but I don't think that will fix anything for your issue. I was on GUL before, and everything worked fine then.
I'd say start off bone-stock after an ODIN and see if it works there (ie, don't download anything, if you can avoid it). Maybe some app you have is killing the BT? But if it doesn't work there, then yes it could just be a hardware thing... disappointing for sure.