I am on the latest BTU firmware (always been on BTU)
Since the last 2 updates (after Jan 2017 security updates), I have not been able to connect to my work WiFi (eap). I was able to on the first (and beta) Nougat sofware.
Seems to be a Android bug as some Pixel owners also seem to have similar problems as metioned here https://issuetracker.google.com/issues/37123899
Keep getting authentication error.
Tried various suggestion such as putting the domain before username, but no luck
The problem seem to come down to that there is no otion to select "DO NOT VALIDATE"
my hTC One m8 (with lineage OS connects without troble and so do a Mi 5 with the lates MIUI OS
Before I downgrade to the last marshmallow, dows anyone have any suggestion?
I wonder what's going on, because even with the last MM software - Dec 2016 (pre Nougat), I can't connect.
Anyone has any ideas?
Related
Hi All
Hoping you can help as i am struggling to understand how this all works with this manufacturer. I got this tablet yesterday and love it so far ... upon starting the tablet i was greeted with an update notification that i initially figured was for 7.0 - turns out this was a patch for 6.0.
This is all great except i noticed in another thread that someone with the same version and based in the uk received the update. Mine wont find it. I tried the PC software to see if this would work as it used to on other manufacturers (Sony for example) but it said i was up to date.
I would prefer to update the official way if possible (not my first BBQ, have had more android tablets than you can poke a stick at - have resorted to all sorts of ways to get the next software before)
Any ideas anyone ? least possible effort as i don't want to corrupt this awesome piece of kit !
From what I can tell they roll it out in waves based on the device's IMEI. I also haven't received it in Italy when some people in neighbouring countries have. I guess all you can do is wait. By the way, corrupting the device is not that easy, if you want to test Nougat right now, you can get it using Firmware Finder, then you can roll back to the regular version using a rollback package you can find on Huawei's website. Worst case scenario, you will have to factory reset, but it won't be a big deal I guess since you just got it. I was able to roll back from a failed flash of Nougat just fine, then reflashed the correct version of Nougat and used it for a while, then rolled back again because I heard the official ota is coming, and it always worked just fine.
Ok great thanks for confirming. i almost went for the galaxytab s2 again (my wife swindled me out of my old one ! ) but glad i didn't - this one runs better on 6.0 than the s2 on 7.0 i noticed.
I got a push notification last night. But I found it's not for Oreo & EMUI 8.0. It's for Build B596.
So now, my system software version is still EMUI 5.0.1 + Android 7.0. :crying:
What about yours?
I still have my 8, but I switched to the 9 around October last year. I power the 8 up once a day to check it.
Completely stock, not rooted, international version, B185, still on 7.0, 5.01, no updates. Firmware finder
shows a few updates, but when I check with the IMEI number, says not authorized.
If it hits, I don't really look for it until April, since they are too busy with the release of the 10, and any bugs
associated with that, will get priority.
Hello, this is my first post here and I have an observation of sorts about the new upgrade.
Last night I noticed that EMUI 8.0 had downloaded on my wife's phone and was ready to be installed, so I installed it. It was actually a fairly quick process, unlike on my Galaxy S8+ (which coincidentally received the update earlier the same day) which took quite some time to upgrade Android then update all the apps...etc.
Anyway, after the update, suddenly the SD card was reported as being defective and cannot be read. Then I tried to add some music to the phone's internal memory, and I couldn't connect to it from my laptop via USB using Hi-Suite. It just didn't see the phone, and yes the cable is good, I checked it. I had to make the transfer using Bluetooth. The music app itself kept crashing several times, and the whole phone just feels unstable after the upgrade.
If anyone has any comments or suggestions, they would be quite welcome.
What emui 8? They started rolling it out? P10 just got the update I don't think we'll get it anytime soon
Sent from my HUAWEI NXT-L29 using Tapatalk
Dear,
Best thing to do after upgrade/ update is to format your mobile.
qurtuba said:
Hello, this is my first post here and I have an observation of sorts about the new upgrade.
Last night I noticed that EMUI 8.0 had downloaded on my wife's phone and was ready to be installed, so I installed it. It was actually a fairly quick process, unlike on my Galaxy S8+ (which coincidentally received the update earlier the same day) which took quite some time to upgrade Android then update all the apps...etc.
Anyway, after the update, suddenly the SD card was reported as being defective and cannot be read. Then I tried to add some music to the phone's internal memory, and I couldn't connect to it from my laptop via USB using Hi-Suite. It just didn't see the phone, and yes the cable is good, I checked it. I had to make the transfer using Bluetooth. The music app itself kept crashing several times, and the whole phone just feels unstable after the upgrade.
If anyone has any comments or suggestions, they would be quite welcome.
Click to expand...
Click to collapse
Oreo is not out yet for the Mate 8, B586 just include some graphical improvements and January security patches.
ScouserCL said:
Oreo is not out yet for the Mate 8, B586 just include some graphical improvements and January security patches.
Click to expand...
Click to collapse
B583 for the L09c432 is on emui 5.0.2 and has security patches for march 1.
Aight, so a couple of weeks ago I decided to finally accept the update that I always skipped, that pesky Android OREO (8.0) update was always harassing my notification panel and I finally decided to accept it and just update. What could go wrong?
After I updated, and saw that a few features were cool, I noticed something...
My phone was not charging even though it was connected to the charger. I tried airplane mode, I tried maximum power saving mode, I tried safe mode, I turned it off and nothing happened. It just didn't want to charge; some might say that it's just a battery issue, but I'm pretty sure that's not the case.
This happened right after I updated my lovely Nougat to Oreo.
So now I need help.
Here are my phone's specs:
*Build Number: R16NW.G930PVPU6CRE7
*SE for Android status: SEPF_SM-G930P_8.0.0_0008
*Fri May 25 20:35:22 2018
*Knox version: Knox 3.1, Knox API level 25, TIMA 3.3.0
*Security Software version: MDF v3.1 Release 2, WLAN v1.0 Release 1, VPN PP-MOD v2.1 Release 1.0, ASKS v1.4 Release 180123, FIPS BoringSSL v1.2, FIPS SKC v1.7, FIPS SCrypto v1.0, SMR Apr-2018 Release 1
*Android security patch level: April 1, 2018
*Model Number: SM-G930P
*IMEI: 353562085155911
*Software version: G930PVPU6CRE7
*Hardware version: REV0.6
*Android Version: 8.0.0 Oreo (I want 7, Nougat)
*Samsung Experience version: 9.0
*Baseband version: G930PVPU6CRE7
*Kernel version: 3.18.71-13585094, [email protected] #1
My phone is a SPRINT unlocked version, 32 gb. You can check out those specs; probably understand them a lot better than I do.
The thing is, I know that I'm going to have to root it in order to install a previous Android version (downgrade). I just don't want to take any risks with flashing the wrong firmware for my specific phone; I don't want to brick it.
So, can y'all please help me with choosing the right -my phone specific- firmware and stuff?
Giving me a step-by-step on how to successfully downgrade back to my 7.0 nougat would be a blessing too.
Thank You!
Siberio08 said:
Aight, so a couple of weeks ago I decided to finally accept the update that I always skipped, that pesky Android OREO (8.0) update was always harassing my notification panel and I finally decided to accept it and just update. What could go wrong?
After I updated, and saw that a few features were cool, I noticed something...
My phone was not charging even though it was connected to the charger. I tried airplane mode, I tried maximum power saving mode, I tried safe mode, I turned it off and nothing happened. It just didn't want to charge; some might say that it's just a battery issue, but I'm pretty sure that's not the case.
This happened right after I updated my lovely Nougat to Oreo.
So now I need help.
Here are my phone's specs:
*Build Number: R16NW.G930PVPU6CRE7
*SE for Android status: SEPF_SM-G930P_8.0.0_0008
*Fri May 25 20:35:22 2018
*Knox version: Knox 3.1, Knox API level 25, TIMA 3.3.0
*Security Software version: MDF v3.1 Release 2, WLAN v1.0 Release 1, VPN PP-MOD v2.1 Release 1.0, ASKS v1.4 Release 180123, FIPS BoringSSL v1.2, FIPS SKC v1.7, FIPS SCrypto v1.0, SMR Apr-2018 Release 1
*Android security patch level: April 1, 2018
*Model Number: SM-G930P
*IMEI: 353562085155911
*Software version: G930PVPU6CRE7
*Hardware version: REV0.6
*Android Version: 8.0.0 Oreo (I want 7, Nougat)
*Samsung Experience version: 9.0
*Baseband version: G930PVPU6CRE7
*Kernel version: 3.18.71-13585094, [email protected] #1
My phone is a SPRINT unlocked version, 32 gb. You can check out those specs; probably understand them a lot better than I do.
The thing is, I know that I'm going to have to root it in order to install a previous Android version (downgrade). I just don't want to take any risks with flashing the wrong firmware for my specific phone; I don't want to brick it.
So, can y'all please help me with choosing the right -my phone specific- firmware and stuff?
Giving me a step-by-step on how to successfully downgrade back to my 7.0 nougat would be a blessing too.
Thank You!
Click to expand...
Click to collapse
I cannot believe the charging problem is caused by Oreo. Try different chargers, and new USB cables. Google the issue to see if it's related to Oreo. If you are absolutely sure this is due to Oreo, then you may change it and root is not required.
Since the phone is still on bootloader 6, you may be able to downgrade to Nougat with the same version of bootloader. Flashing firmware is a complex process and phone may be easily bricked if anything goes wrong, so you need to understand what you are doing exactly. I would suggest to read thoroughly information related to Samsung Galaxy firmware update using Odin software. I usually get s7 firmware from two sites:
https://updato.com/
https://www.sammobile.com/firmwares/galaxy-s7/
Switch off your phone then try charging?
yves31 said:
I cannot believe the charging problem is caused by Oreo. Try different chargers, and new USB cables. Google the issue to see if it's related to Oreo. If you are absolutely sure this is due to Oreo, then you may change it and root is not required.
Since the phone is still on bootloader 6, you may be able to downgrade to Nougat with the same version of bootloader. Flashing firmware is a complex process and phone may be easily bricked if anything goes wrong, so you need to understand what you are doing exactly. I would suggest to read thoroughly information related to Samsung Galaxy firmware update using Odin software. I usually get s7 firmware from two sites:
https://updato.com/
https://www.sammobile.com/firmwares/galaxy-s7/
Click to expand...
Click to collapse
Well, ironically, my mother got a new -android- phone a couple of days ago and my phone charges pretty fine with her charger. I guess it WAS a charger problem, but my charger works perfectly fine on my father's phone and not on mine; strange.
The thing is, although it can now charge, the super battery drainage is still there, and yes, I'm convinced the quick battery drainage problem came along with the Oreo update. It lasted hours and hours on Nougat, but now on Oreo it barely gets to 3 hours and 30 minutes.
Hey all sorry to bother you but I can't install the update for my OPPO F1s. System Update states it is the latest version although it isn't, when I press the "Features" button it says "No Version Info"
When I try to manually update through recovery it states the same thing. I haven't updated the phone before as it's never asked even though I bought it the week the OPPO F1s was released in Australia. As far as I can tell it (With my extremely limited knowledge) it seems as though I don't have an official stock rom on my phone although I've never tampered with it.
Any ideas or advice would be greatly appreciated as although not urgent it does worry me as I realised I may have bought a phone with some kinda of virus on it without realising and I've used it for a couple of years.
#UPDATE#
Turns out the firmware is oddly labelled but I figured out that the phone had been updated with stock 6.0 rom and the 5.1 rom has been updated since but the 6.0 was considered beta, hence so feature info.
Tracked down the latest 6.0 update I could find and installed it and BAM phone is back to normal with the plus-side of having a clean install. Sorry to bother you all with this.
Which firmware you have installed?
A1601EX_11.A.37_20190227 is it this?
Oppo Customer Care (India) advised users of F1s that no OTA update for 6.0 would be pushed and anyone wishing to update will have to go to service centre. Did that and it seems they too have installed the beta 6.0 ROM which says no version info. Version number : A1601EX_11_D.102_170923 (Security Patch June 2017)
Apparently the stable 6.0 update available for Indian users is version : A1601EX_11.A.37_20190227. But I am not sure whether it will update through recovery. Will try and let you know
i know two years have passed but im facing the same problem and i cant find the latest update of 6.0, can you link me there?pls
Both Samsung and T-mobile have been a complete waste of time trying to figure this out - hoping you guys can help
I have a Galaxy S10+ on T-mobile SM-G975U
I just got blocked from my work email with the error listed that I do not have the latest August Security Patch
I hit 'download and install' on the update screen a bunch of times, but each time it tells me:
'Your software is up to date - Security patch July 1, 2019' - See attached screenshot
Looking on tmobiles website, I see 2 pages documenting the latest updates pushed for August:
S10: https://support.t-mobile.com/docs/DOC-39499
S10+: https://support.t-mobile.com/docs/DOC-39465
Note, on those pages the baseband versions are as follows:
S10: G975USQS2ASGC
S10+: G975USQS1ASGC
Looking on my phone at current software version, it's showing the baseband version is "G975USQS1ASGC" - Which is noted as the S10 baseband on t-mobiles website
My phone is also saying I have the July security patch installed (see attached screenshots)
Any ideas as to what the hell is going on?
According to Samsung they haven't actually pushed out the August security patch for the S10+ - http://doc.samsungmobile.com/SM-G975U/SPR/doc.html
T-mobile's website apparently is inaccurate
You are up to date. The release was in august for july patch. Now there is going to be a august patch soon since their was a exploit found. That's maybe why your work email is refusing to work.
August patch should be out shortly. It is available to install from firmware.science to load via SD card and they usually get it shortly before it's sent out by TMobile.
I had this problem back on the s8 it is fine there are no problems but if you want to fix it then you have to flash with Odin (you just lose all your data KNOX IS NOT TRIPPED)