Related
Just got a small update. Anyone know what's in it? 6.0 prep maybe?
jwl12345 said:
Just got a small update. Anyone know what's in it? 6.0 prep maybe?
Click to expand...
Click to collapse
It´s just a security patch rolling out right now !
jwl12345 said:
Just got a small update. Anyone know what's in it? 6.0 prep maybe?
Click to expand...
Click to collapse
A big update needs a small prep update???? Never heard LOL
Too many video games, I guess. Was half asleep and forgot that that's just not how this works lol
Lousy timing on AT&T. I have been trolling waiting for this update and got really excited. Would have been OK with even an update to unlock the FM radio but alas, we just have a generic update.
exxTErno said:
It´s just a security patch rolling out right now !
Click to expand...
Click to collapse
Thanks, I had no clue one was on the way so I came to see what it was.
I was hoping, had my fingers crossed. Went way too quickly. ?
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
note 4 SM-N910A at&t update?
does anyone know when the 6.0 update will be released? my phone is unlocked will this affect the OTA update?
mejiachach said:
does anyone know when the 6.0 update will be released? my phone is unlocked will this affect the OTA update?
Click to expand...
Click to collapse
So you intentionally rooted/ hacked the software and now are worried about getting it?
lol
dave30534 said:
So you intentionally rooted/ hacked the software and now are worried about getting it?
Click to expand...
Click to collapse
No i didn't "root/hack the software" lol . i haven't even received the phone from retailer. this phone is factory unlocked. IMO or experiences this will not affect it but wanted a third opinion.
dave30534 said:
So you intentionally rooted/ hacked the software and now are worried about getting it?
Click to expand...
Click to collapse
Unlocked doesn't mean that it was hacked or rooted. It means that you can use any carrier's sim card in it.
Sent from my SAMSUNG-SM-N910A using Tapatalk
mejiachach said:
No i didn't "root/hack the software" lol . i haven't even received the phone from retailer. this phone is factory unlocked. IMO or experiences this will not affect it but wanted a third opinion.
Click to expand...
Click to collapse
I'm no expert, but the way I think it works is that if your phone's not AT&T branded you won't get the update as they are AT&T version specific. If you want to check for and get any kind of updates you'll probably have to go through Samsung's Kies program.
Sorry, misread on the unlocked part.
I just got lots of updates from the play store, one of which is the new Samsung Browser that is included in 6.0 Marshmallow
ok thanks Kyuta Syuko for the information
dave30534 said:
Sorry, misread on the unlocked part.
I just got lots of updates from the play store, one of which is the new Samsung Browser that is included in 6.0 Marshmallow
Click to expand...
Click to collapse
The Samsung Browser update wasn't tied to this update, Samsung updated the browser to work with Lollipop.
Download This Small Update
Any one know where i can download this update and update manually? I have a att note 4 on tmobile. I use to be a att customer. But i was told by tmobile that my device software updates have to come from att because i have a att branded version of the note 4.
yasirfaheem said:
Any one know where i can download this update and update manually? I have a att note 4 on tmobile. I use to be a att customer. But i was told by tmobile that my device software updates have to come from att because i have a att branded version of the note 4.
Click to expand...
Click to collapse
You don't really need this, just a small security update, wait for M it'll be included
www.engadget.com/2016/04/04/android-april-security-update
floatingtrees said:
You don't really need this, just a small security update, wait for M it'll be included
Click to expand...
Click to collapse
If i had att i would be able to install this update on my phone and would not even need to ask about this. But i no longer have att and have tmobile and want to have all the latest bug and os patches even though you think i do not need it.
www.engadget.com/2016/04/04/android-april-security-update
Android's April security update tackles another Stagefright flaw
You'll want to update in short order.
Google's monthly Android security updates are nothing new, but its latest release may be particularly important. The new April update tackles eight critical vulnerabilites that include one in the libstagefright library -- you know, the same media framework that recently faced a rash of real and potential exploits. It also patches a nasty kernel flaw that would give attackers full control over your device. You'll get first crack at the fixes if you either have a Nexus device or can install an Android Open Source Project build, but other vendors that offer Google's monthly updates will likely follow suit before long.
Now tell me that i do not need this update!
yasirfaheem said:
If i had att i would be able to install this update on my phone and would not even need to ask about this. But i no longer have att and have tmobile and want to have all the latest bug and os patches even though you think i do not need it.
www.engadget.com/2016/04/04/android-april-security-update
Android's April security update tackles another Stagefright flaw
You'll want to update in short order.
Google's monthly Android security updates are nothing new, but its latest release may be particularly important. The new April update tackles eight critical vulnerabilites that include one in the libstagefright library -- you know, the same media framework that recently faced a rash of real and potential exploits. It also patches a nasty kernel flaw that would give attackers full control over your device. You'll get first crack at the fixes if you either have a Nexus device or can install an Android Open Source Project build, but other vendors that offer Google's monthly updates will likely follow suit before long.
Now tell me that i do not need this update!
Click to expand...
Click to collapse
Relax no one's gonna target you and "hack into your phone" if your worried about stagefirght then you shouldn't rely on att or Samsung for that matter to patch it, consider using a texting app that offers protection instead like textra. Anyway good luck finding that 60mb insignificant update file that no one will bother to upload
Stagefright was patched way before this and even though we just got the update, we still don't have the latest patch
Am I just missing it, or is there no root or recovery ability for the 915A?
Marshmallow 6.0.1 ****ed mine up when it got pushed down, and Samsung's backup software (all 3 of them) failed to capture my apps and settings properly. Really wish I could've had a better backup ability.
Does or has anyone checked to see if the update to MM 6.0.1 has unlocked the bootloader on the SM-N915A like the Verizon variant?
How does one check?
Att have not released any M updates.
Mine updated to 6.0.1 the same day I bought it . Several small updates happened first. 5.0.1 to 5.1.1 then a small one, and finally 6.0.1. Since I had just bought it, resetting was a simple thought. But so far, no problems, I bought a PowerBear to make it last longer. :fingers-crossed:
Mine had a lot of issues after being updated. MMS didn't work at all. SMS worked sporadically, but would sometimes delete whole threads. Couldn't get a signal in many spots. Google Play Services wouldn't run and couldn't be fixed. Tried a cache-wipe and every other non-destructive method, but nothing worked. Ended up having to factory-reset, and since then the phone works as it should, but none of the backup methods captured key settings. Basically all it did was save contacts and APK's. Lost my 2-factor keys and everything.
I am with you! Since the update to MM, phone has been very laggy/unresponsive. Lock screen lights up for no reason sporadically and I have LOTS of dropped calls/deadspots. VERY irritating! I wish this release would have been tested a bit more before it was OTA pushed out
Hey all! Good news! A 9-year-old bug called the "Dirty Cow" exploit still exists in the Linux/Android kernel can easily grant root on any Android phone!!! See the video below.
http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/
So there's another bug to exploit for root and even possibly unlocking the bootloader! The bug has been fixed recently in Linux but hasn't been rolled into Android yet.
Could someone make this Windows compatible? http://androiding.how/dirty-cow-root-android/
JEANRIVERA said:
Hey all! Good news! A 9-year-old bug called the "Dirty Cow" exploit still exists in the Linux/Android kernel can easily grant root on any Android phone!!! See the video below.
http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/
So there's another bug to exploit for root and even possibly unlocking the bootloader! The bug has been fixed recently in Linux but hasn't been rolled into Android yet.
Click to expand...
Click to collapse
Have you tried or someone. I'm already installing Linux into my computer.
juanfe1a said:
Have you tried or someone. I'm already installing Linux into my computer.
Click to expand...
Click to collapse
did you end up doing it?
Who else could get the root on sm-n915a ??? I also have problems with the transition from 5.1.1 to 4.4.4. (Kitkat). If anyone can help write please how to do this ??
I would also like to know if I am from russia and I need a Russian language that is not available on samsung galaxy note edge n915a. Is it possible to add it like that ?? Sorry for my bad english (googl translate)). Thank you. I am hope for your help
pleasseee i need debrick image for at&t not egde (SM-N915A)
winstonakime said:
pleasseee i need debrick image for at&t not egde (SM-N915A)
Click to expand...
Click to collapse
https://forum.xda-developers.com/note-edge/general/stock-att-note-edge-5-1-1-t3241314
You may need to know your build number tho
Just to keep this alive it is now November 2017 any news?
Dr.Lost said:
Just to keep this alive it is now November 2017 any news?
Click to expand...
Click to collapse
I wish...
Anything new?
Last night i got new update.
I can see that they fixed low lvl sound, i dont have problems with clock any more, next few days i will see that they fixed anything more.
October 5, 2017 patch...
anyone geting this?
i added pictouer with colck problem before updating.
https://photos.google.com/photo/AF1QipMGQweIqQu9IQJQpNYtX2M5qKA2qgdgiXq8Jw-Y
https://photos.google.com/photo/AF1QipNPuzUO-CJC00WicsTdNQpFrBZBmv9avNUYY474
My Qualcomm version (Boost Mobile) hasn't received any updates, ever. It's still on the June security patch, SMH.
Also - this device doesn't seem to have any issues that I've noticed, it just works. But I do want the BlueBorne patch, Also the KRACK patch would be nice.
Sigh... Lenovo is so slow...
ATTACK said:
My Qualcomm version (Boost Mobile) hasn't received any updates, ever. It's still on the June security patch, SMH.
Also - this device doesn't seem to have any issues that I've noticed, it just works. But I do want the BlueBorne patch, Also the KRACK patch would be nice.
Sigh... Lenovo is so slow...
Click to expand...
Click to collapse
I have MTK device, XT1771. I got on myne little bit low sound, it was ok but now it is pritty loud and clear sound from him, and fingerprint is better. I didnt try headphones but i think that they are fixed to, i got little lower sound on them, i didnt try them but when i do i will report. xD
Just a hint, If you're using custom recovery DO NOT run the system update. The device will bootloop into recovery, and the only way to restore is wipe data, cache and dalvik, and after that boot into bootloader and type fastboot continue into CMD. This at least worked for me.
PoP*92 said:
Last night i got new update.
I can see that they fixed low lvl sound, i dont have problems with clock any more, next few days i will see that they fixed anything more.
October 5, 2017 patch...
anyone geting this?
i added pictouer with colck problem before updating.
Click to expand...
Click to collapse
ya i got update in my device XT1770
Camera
any bugs in the camera? or does it works fine?
PoP*92 said:
Last night i got new update.
I can see that they fixed low lvl sound, i dont have problems with clock any more, next few days i will see that they fixed anything more.
October 5, 2017 patch...
anyone geting this?
i added pictouer with colck problem before updating.
Click to expand...
Click to collapse
what were the problems with the clock? she froze?
I got the update three days ago and from what I can tell it seems that the issues with clock freezing and alarm not going off are fixed.
When it comes to the camera, the videos that I took were all very dark, but with the update this issue seems to be fixed as well for me. Pictures, well I was never a fan of the quality of the pictures anyway, I don't know.
Request for stock boot and recovery for this update
I need the recovery and boot of this release to carry on to next OTA update via stock recovery ... But fails to do that. After boot is not stock
Are you 100% stock? That's the only way to take an OTA. I know there were builds here to return to stock, but I'm not sure if they if they deleted. I'll have to look around.
Hi
Have Someone X1944-4 latest firmware to share?
if possible retbr (i am from brazil)
Mi A3 Global : DO NOT UPDATE!
V11.0.3.0.QFQMXTC (not QFQMIXM one) is rolling out to the Mi A3 global users.
There was a serious bug in the latest update, so DO NOT UPDATE!!
#WARNING #ALERT #READ
This a warning to everyone who's using the stock ROM here: do NOT update your device to the latest build that shipped via OTA.
Apparently Xiaomeme has rolled out an incorrect build for our device. After flashing, it splashes "Telcel" logo (which is a Mexican carrier), and only SIM1 seems to work post update. If you see any updates, just ignore and do NOT flash.
Thank you! I was updating when I read your warning, now I have a paused update. Thinking about doing a factory reset to get rid of that. I'm starting to be seriously tired of these mistakes and faulty updates...
Thank you again for your advice.
That's why I switched to EU. As Xiaomi releases EU updates after global channel, these kind of mistakes are less likely to happen with EU builds.
What can I Do if i installed the Update?
Do you think xiaomi can fix it with a Update?
Can I block it somehow if the notification "Installation pending" is coming?
palorent said:
What can I Do if i installed the Update?
Do you think xiaomi can fix it with a Update?
Click to expand...
Click to collapse
I have updated :crying::crying: and dual sim is not working
ksaravanan97 said:
I have updated :crying::crying: and dual sim is not working
Click to expand...
Click to collapse
+1
I have switched to MIUI 12 few days ago ?? Am safe. BTW it's (Xiaomeme stock rom) the worst rom I ever used ?
thearorahimanshu said:
I have switched to MIUI 12 few days ago Am safe. BTW it's (Xiaomeme stock rom) the worst rom I ever used
Click to expand...
Click to collapse
You probably don't realize the irony in that - "mocking" Xiaomi for stock Android and at the same time be proud in using their heavily modified Android OS (MIUI).
#Vangreen said:
+1
Click to expand...
Click to collapse
+1
_mysiak_ said:
You probably don't realize the irony in that - "mocking" Xiaomi for stock Android and at the same time be proud in using their heavily modified Android OS (MIUI).
Click to expand...
Click to collapse
am not proud to use it, but its better to use it instead of using Xiaomeme so called stock rom that is full of bugs. actually that's not a rom they are providing, they are giving a lot of bugs with a small amount of rom ??
Well, wife already updated (we both have the A3). We're still locked (bootloader's), and I see Xiaomi is "WORKING FEVERISHLY" to rectify (Ha!).
My question is, is the consensus here of a hard/factory reset would correct this?
soxtober05 said:
Well, wife already updated (we both have the A3). We're still locked (bootloader's), and I see Xiaomi is "WORKING FEVERISHLY" to rectify (Ha!).
My question is, is the consensus here of a hard/factory reset would correct this?
Click to expand...
Click to collapse
i think the option its called "never buy a xiaomi again" :highfive:
soxtober05 said:
Well, wife already updated (we both have the A3). We're still locked (bootloader's), and I see Xiaomi is "WORKING FEVERISHLY" to rectify (Ha!).
My question is, is the consensus here of a hard/factory reset would correct this?
Click to expand...
Click to collapse
Hard reset will hardly help, the issue is related to incorrect ROM. You can either unlock bootloader (this will do a factory reset), flash the right ROM and relock the bootloader. Or just wait for the fix from Xiaomi, they will hopefully release it shortly.
Fix Update is there for those who get the wrong firmware.
??
It is fixed now with a new update... Stupid mistake on Xiaomi's part but at least they are quick to fix it.
Didn't received the bugued update but today I received the fixed update announcing the fix of dual sim bug.
XJeFX said:
Didn't received the bugued update but today I received the fixed update announcing the fix of dual sim bug.
Click to expand...
Click to collapse
+1
I installed it, but in my hurry, forgot the Magisk step before rebooting.
Anyone got patched V11.0.17.0.QFQMIXM?
How is it possible pixel 6 pro to be faster and smoother on a beta version than stable android 12???
Fingerprint sensor is very good, brightness is higher than android 12 specially under sun and camera is far way more derailed than android 12 stable... Why is this happening? Are they trolling us?
Presumably because this is a beta build release that is much further ahead in the current development schedule. Keep in mind that stable Android 13 releases in about two months and a week or so (August is currently the scheduled release).
It wouldn't really be a great idea in development to only start optimizing your product for stability and performance after it releases. So, that is what they are working on now; optimizing the stability, speed and performance so that they can spend the last few months of development ensuring that the new system functionality works well and is a pleasant update for us Pixel 6 users.
Also, it's important to make sure that you are releasing a great OS build - especially when that OS version's effectiveness will aid in the sales of your upcoming smartphone product that is going to launch with it (the Pixel 7 series)!
So overall, there are *Noexcusses* for being crummy with your software development and management =). Google had suffered enough with their Pixel 6 series release as they were still lacking funds in their phone development department due to a crummy lawsuit. But as a result of that issue, I'm assuming that they are shaping themselves up for that upcoming Pixel series.
NippleSauce said:
Presumably because this is a beta build release that is much further ahead in the current development schedule. Keep in mind that stable Android 13 releases in about two months and a week or so (August is currently the scheduled release).
It wouldn't really be a great idea in development to only start optimizing your product for stability and performance after it releases. So, that is what they are working on now; optimizing the stability, speed and performance so that they can spend the last few months of development ensuring that the new system functionality works well and is a pleasant update for us Pixel 6 users.
Also, it's important to make sure that you are releasing a great OS build - especially when that OS version's effectiveness will aid in the sales of your upcoming smartphone product that is going to launch with it (the Pixel 7 series)!
So overall, there are *Noexcusses* for being crummy with your software development and management =). Google had suffered enough with their Pixel 6 series release as they were still lacking funds in their phone development department due to a crummy lawsuit. But as a result of that issue, I'm assuming that they are shaping themselves up for that upcoming Pixel series.
Click to expand...
Click to collapse
I want my phone better than pixel 3xl at least on camera and still it is not. Im using pixel phones from Nexus 6p..
There is no Beta 3 yet. The latest release is Beta 2.1 which has some bug fixes for Beta 2.
More info here
biohaz55 said:
There is no Beta 3 yet. The latest release is Beta 2.1 which has some bug fixes for Beta 2.
More info here
Click to expand...
Click to collapse
Ok then Beta 2,1!
Noexcusses said:
I want my phone better than pixel 3xl at least on camera and still it is not. Im using pixel phones from Nexus 6p..
Click to expand...
Click to collapse
And it will be. Beta 2.1 (on a newly wiped 6 pro) is excellent. Battery life has settled and is more consistent, image processing is getting better and so is the overall experience.
I also have the 3 XL and I remember that it took 6 months for the device to improve. When it was upgraded to A10, it was a different phone. This happens on all Pixels/Nexus devices. Software optimization takes time and is probably more visible on Google devices just due to the way they develop and improve their software over time (just different than apple or other oems, not necessarily better or worse)
Alekos said:
And it will be. Beta 2.1 (on a newly wiped 6 pro) is excellent. Battery life has settled and is more consistent, image processing is getting better and so is the overall experience.
I also have the 3 XL and I remember that it took 6 months for the device to improve. When it was upgraded to A10, it was a different phone. This happens on all Pixels/Nexus devices. Software optimization takes time and is probably more visible on Google devices just due to the way they develop and improve their software over time (just different than apple or other oems, not necessarily better or worse)
Click to expand...
Click to collapse
Hope so... Im on beta 2.1 also and i have realised brightness improvements and charging improvements too... Battery duration on 2.1 isn't so good as Android 12 but is fine as soon as is so early Beta.
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
Patching the boot image works for me on A13B2.1. Direct install may cause bootloops though. If you encounter a bootloop using direct install you can just boot into the bootloader and flash your patched Canary 24313 (or whatever you were on) and it will boot and then patch the boot image rather than using direct install with 24314. No need to wipe the device, in my experience.
I also have verity and verification disabled.
Lughnasadh said:
Patching the boot image works for me on A13B2.1. Direct install may cause bootloops though. If you encounter a bootloop using direct install you can just boot into the bootloader and flash your patched Canary 24313 (or whatever you were on) and it will boot and then patch the boot image rather than using direct install with 24314. No need to wipe the device, in my experience.
I also have verity and verification disabled.
Click to expand...
Click to collapse
You're correct here. I forgot a few words in my original comment there, haha. It should have said "if the patched boot image was installed via Magisk". Sometimes I make comments too soon after rolling out of bed LOL.
Regardless, I did a full wipe and reinstall as I hadn't done my typical device setup when I had first upgraded to 13B2.1. I usually install all updates onto both slots (a and b), however, I hadn't done that initially. So a full wipe and installation onto both slots was required by my standard practices - as I wasn't even sure which one I was currently using, haha. Anyway, I've been trying to resolve some problem with Google Phone as the Visual Voicemail hasn't been working for me. So, I had figured a full wipe and reinstallation across both slots would have definitely resolved the boot loop as well as that visual voicemail problem....but it hasn't fixed the latter... =(
NippleSauce said:
You're correct here. I forgot a few words in my original comment there, haha. It should have said "if the patched boot image was installed via Magisk". Sometimes I make comments too soon after rolling out of bed LOL.
Regardless, I did a full wipe and reinstall as I hadn't done my typical device setup when I had first upgraded to 13B2.1. I usually install all updates onto both slots (a and b), however, I hadn't done that initially. So a full wipe and installation onto both slots was required by my standard practices - as I wasn't even sure which one I was currently using, haha. Anyway, I've been trying to resolve some problem with Google Phone as the Visual Voicemail hasn't been working for me. So, I had figured a full wipe and reinstallation across both slots would have definitely resolved the boot loop as well as that visual voicemail problem....but it hasn't fixed the latter... =(
Click to expand...
Click to collapse
Here's Google's workaround for visual voicemail bug on Android 13 betas
Rolling back to a v81 release of the Phone by Google app can fix the issue
www.androidpolice.com
uicnren said:
Here's Google's workaround for visual voicemail bug on Android 13 betas
Rolling back to a v81 release of the Phone by Google app can fix the issue
www.androidpolice.com
Click to expand...
Click to collapse
Thank you for this! Unfortunately, downgrading the phone app to V81 didn't resolve the issue. I have also tried some of the other methods that were being discussed in that Reddit post but haven't had any luck with those tricks either.
I'm going to try removing myself from the Google Phone Beta next though. Worst comes to worst (if removing myself from the phone beta list doesn't work), I'll have to wait a few weeks for the next Android 13 beta update.
Woah! This is offtopic but the pictures are so good! You're lucky that you have a pixel 6 pro
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
Im not rooted sir
notnoelchannel said:
Woah! This is offtopic but the pictures are so good! You're lucky that you have a pixel 6 pro
Click to expand...
Click to collapse
On android 13 beta 2,1 photos are much better than android 12...
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
I updated to A13 beta 2.1 without a full wipe, using canary 24314 just fine. I did of course disable all modules before installing the A13 update.I also removed the -w command in the flash all bat file.
Amd4life said:
I updated to A13 beta 2.1 without a full wipe, using canary 24314 just fine. I did of course disable all modules before installing the A13 update.I also removed the -w command in the flash all bat file.
Click to expand...
Click to collapse
It seems to be a known error after clean wipe updates to the latest A13 beta build based on @uicnren 's post. According to users on the Reddit thread, the issue has to do with the beta and a current OS build miscommunication with the phone carriers in the United States. So, if this is truly the case, users experiencing this issue won't have it resolved until the next beta build release (or later). Time will tell =)
I'm abut ready to jump in and load the 13 beta on my P6 and wanted to know it there are any hotspot issues since that would be the one deal breaker for me.
Does anyone know When would be next Beta update?
Thanks...