Related
Do you think that the LG G Stylo will receive Android 6.0 and Android 6.0.1? I know the variant from T-mobile will get the updates, they have confirmed that, but will the Stylo's on Metro PCS get them too? Its exactly the same phone. Metro PCS fb reps won't comment on this.
LordHades21999 said:
Do you think that the LG G Stylo will receive Android 6.0 and Android 6.0.1? I know the variant from T-mobile will get the updates, they have confirmed that, but will the Stylo's on Metro PCS get them too? Its exactly the same phone. Metro PCS fb reps won't comment on this.
Click to expand...
Click to collapse
chances are yes and with the record so far you guys are the only ones that will get the KDZ as well
most likely, Metro pcs is owned by T-mobile.
DB225 said:
most likely, Metro pcs is owned by T-mobile.
Click to expand...
Click to collapse
Didn't know that lol
6th_Hokage said:
Didn't know that lol
Click to expand...
Click to collapse
yep, they bought it about what two years ago or so now.
http://www.cnet.com/news/what-t-mobiles-merger-with-metropcs-means-to-you-faq/
So now the question is.... How long do we wait.. Any ideas?
Their comments on it. I don't think the customer reps know much anyways though...
Well I think I need to switch to metro then. No word on boost love. There's nothing to lose. And I'll gain an extra gb of ram
Boost and sprint are getting the marshmallow update zv7. Don't know about T-Mobile and metro
Just grabbed a Boost Stylo today for a decent price, installed the rooted system image from 6th_Hokage and have it working fairly well after freezing out a lot of stuff but even so the RAM usage seems pretty excessive with not much going on - this is with no apps running after a reboot and at about 1 min I started up System Monitor Lite to take a peek:
I mean, I've gutted it of most everything I can that could interfere with the startup and suck out the RAM en mass so, I suppose it'll work itself out. Not bad performance I suppose but of course the Boost/Sprint variants of the Stylo are handicapped for no good reason with 1GB of RAM and when I had a MetroPCS variant a few weeks ago it was very noticeable in terms of overall performance.
Anyway, I just noticed this Marshmallow info over at another site so it's pretty cool to see it being pushed from Boost just before the end of the year, pretty cool indeed. I don't know if I'll bother with it at this point since root is a must and I'm not sure if or when we'll see it for Android 6.0.1 on this device (LS770). Will be nice to see if there's any improvement in this after-boot RAM usage as well, especially after some removal of some bloatware whenever it happens.
Will be interesting to see how things progress now that it's finally here, definitely.
according to T-Mobile's software update tracking site the Stylo is confirmed for getting a 6.0 update, although they haven't really given a timeframe for it. It's currently listed as "Manufacturer Development" which means that they most likely haven't started their own testing on it just yet. My best guess is that we'll see it come before Q2 of next year on T-Mobile, and possibly a similar timeframe for MetroPCS as well (since they're a child company of T-Mobile).
Can't really say for the Boost/Virgin/Cricket models though. Sprint already has 6.0 pushed to the Stylo in some markets and is supposedly rolling them out across more now. And since Boost and Virgin are child companies of Sprint, they'll probably also see an update soon.
jxthrx said:
And since Boost and Virgin are child companies of Sprint, they'll probably also see an update soon.
Click to expand...
Click to collapse
The Boost 6.0.1 update (LS770ZV7) came out on December 28th and is currently being pushed to devices:
http://devicehelp.boostmobile.com/d...Boost_Mobile/en/Software_Updates_-_LG_G_Stylo
br0adband said:
The Boost 6.0.1 update (LS770ZV7) came out on December 28th and is currently being pushed to devices:
http://devicehelp.boostmobile.com/d...Boost_Mobile/en/Software_Updates_-_LG_G_Stylo
Click to expand...
Click to collapse
dont receved the update
emanuelrv said:
dont receved the update
Click to expand...
Click to collapse
It will probably be soon. They can't roll out updates to everyone all at once. They usually do it by region.
Ehh....warned my bro that has my rooted Stylo not to except any system updates....hopefully we can crack that update soon
If it's rooted it shouldn't accept any updates, at least that's how most every phone running Android is these days: any tampering or changes to the system partition (which obviously flashing your rooted system img does) should prevent the OTA check from being successful. At least that's how it is on some other devices I've owned in the past 1.5 years - if the device ain't pure 100% bone stock with no mods done at all the OTA's usually just don't even happen but, this could be different, I don't know but I suppose we'll find out soon enough.
br0adband said:
If it's rooted it shouldn't accept any updates, at least that's how most every phone running Android is these days: any tampering or changes to the system partition (which obviously flashing your rooted system img does) should prevent the OTA check from being successful. At least that's how it is on some other devices I've owned in the past 1.5 years - if the device ain't pure 100% bone stock with no mods done at all the OTA's usually just don't even happen but, this could be different, I don't know but I suppose we'll find out soon enough.
Click to expand...
Click to collapse
i mean that he doesn't try to install the update cause it will download
6th_Hokage said:
Ehh....warned my bro that has my rooted Stylo not to except any system updates....hopefully we can crack that update soon
Click to expand...
Click to collapse
I've been using your rooted system for weeks. Works perfectly.:good: Thank you.
Just received the update ( ls770zv7 ). I uploaded it. Hope you can crack it too.
https://drive.google.com/file/d/0B8jh0cpIovnMTlBOelVLdVBIdnM/view?usp=sharing
So is that 6.0.1 marshmallow or just 6.0. What variant do you have (boost)? Just curious
Ok, so I happened upon an LG G4 H810 AT&T variant at a pawn shop a few weeks ago, they couldn't get it working because of the boot loop issue (person that pawned it probably did so knowing it was defective and had it working just long enough to demo it to get the cash). I took a look at it, great shape overall, no damage noted, plain old "ceramic" back cover, battery had a date of January 15 2016 on it so it's tough to say if the battery was just newer or the device itself since I couldn't get it to boot. Date code was 508 so obviously one of the well known defective models.
Long story short: got it for a pittance because they couldn't get anyone else to buy it, got it home, registered it at LG's website on my account, waited 2 days then chatted their support up and got them to accept it for RMA, shipped it out last week and it should be back tomorrow. I'm not sure if they repaired it or replaced it - the limited info I have says they "Swap Board (Main/RF)" so I'm guessing the entire motherboard was swapped for (hopefully) a newer one made this year that might not fail but probably will.
So, I had a question or two and I've done quite a bit of research the past few days and never found specific answers so at this point I'm just going to ask them and be done with it:
1) There's apparently no working root at all for the H810 that I've been able to find. I'm going to assume that the unit I'll be getting tomorrow or Tuesday will have been upgraded to Marshmallow unfortunately but that's just how it goes so there's no rolling back as I understand things. If there's a working root I'd be interested in knowing which one that happens to be. Also with no root there's probably no recovery either but I will keep researching to find out more as I'm able.
2) There's apparently no custom ROMs available because of the locked bootloader which will never get unlocked obviously as well. I've read that the PR (Puerto Rico) ROM could be installed on an H810 that was still running Lollipop with the v2 rollback but if this repaired board is Marshmallow that means it's been upgraded to v3 rollback and so that's dead in the water too.
3) I'm also going to assume that if the board has been replaced and hopefully is one made in 2016 (with a 6xx serial number) then it could last a while but there's no guarantee of it. I've seen people say the 6xx versions have not failed but then I find a post or two from someone that claims to know someone with a 6xx model and it failed at least once on them but I can't get any actual verification on it, that's just hearsay to me if there's no direct proof so all I can do is continue hoping it's a 6xx revision board and that it's not going to fail anytime soon.
This will be my second G4, had a Sprint variant last year and never had problems with it, sold it to a gent from Australia when he visited Las Vegas and as far as I know he's still using it, who knows.
If anyone can offer some info related to those questions I'd be grateful so thanks in advance if anyone can.
Have fun, always...
EDIT:
Seems that if I get very lucky and the replacement board comes with H81020n on it - the original Marshmallow build - there's a chance I can roll it back to H81010o using the TOT method from the other thread for it, that would at least get me root potential I suppose. Guess I'll find out tomorrow if the replacement arrives. Can't find any absolutely verified info about later builds, looks like the very latest patch build is H81022b from September and I'm going to assume if that happens to be on the board then all hope is lost, basically. Ugh...
br0adband said:
Ok, so I happened upon an LG G4 H810 AT&T variant at a pawn shop a few weeks ago, they couldn't get it working because of the boot loop issue (person that pawned it probably did so knowing it was defective and had it working just long enough to demo it to get the cash). I took a look at it, great shape overall, no damage noted, plain old "ceramic" back cover, battery had a date of January 15 2016 on it so it's tough to say if the battery was just newer or the device itself since I couldn't get it to boot. Date code was 508 so obviously one of the well known defective models.
Long story short: got it for a pittance because they couldn't get anyone else to buy it, got it home, registered it at LG's website on my account, waited 2 days then chatted their support up and got them to accept it for RMA, shipped it out last week and it should be back tomorrow. I'm not sure if they repaired it or replaced it - the limited info I have says they "Swap Board (Main/RF)" so I'm guessing the entire motherboard was swapped for (hopefully) a newer one made this year that might not fail but probably will.
So, I had a question or two and I've done quite a bit of research the past few days and never found specific answers so at this point I'm just going to ask them and be done with it:
1) There's apparently no working root at all for the H810 that I've been able to find. I'm going to assume that the unit I'll be getting tomorrow or Tuesday will have been upgraded to Marshmallow unfortunately but that's just how it goes so there's no rolling back as I understand things. If there's a working root I'd be interested in knowing which one that happens to be. Also with no root there's probably no recovery either but I will keep researching to find out more as I'm able.
2) There's apparently no custom ROMs available because of the locked bootloader which will never get unlocked obviously as well. I've read that the PR (Puerto Rico) ROM could be installed on an H810 that was still running Lollipop with the v2 rollback but if this repaired board is Marshmallow that means it's been upgraded to v3 rollback and so that's dead in the water too.
3) I'm also going to assume that if the board has been replaced and hopefully is one made in 2016 (with a 6xx serial number) then it could last a while but there's no guarantee of it. I've seen people say the 6xx versions have not failed but then I find a post or two from someone that claims to know someone with a 6xx model and it failed at least once on them but I can't get any actual verification on it, that's just hearsay to me if there's no direct proof so all I can do is continue hoping it's a 6xx revision board and that it's not going to fail anytime soon.
This will be my second G4, had a Sprint variant last year and never had problems with it, sold it to a gent from Australia when he visited Las Vegas and as far as I know he's still using it, who knows.
If anyone can offer some info related to those questions I'd be grateful so thanks in advance if anyone can.
Have fun, always...
EDIT:
Seems that if I get very lucky and the replacement board comes with H81020n on it - the original Marshmallow build - there's a chance I can roll it back to H81010o using the TOT method from the other thread for it, that would at least get me root potential I suppose. Guess I'll find out tomorrow if the replacement arrives. Can't find any absolutely verified info about later builds, looks like the very latest patch build is H81022b from September and I'm going to assume if that happens to be on the board then all hope is lost, basically. Ugh...
Click to expand...
Click to collapse
I haven't kept up with root, but I doubt anything MM latest or not you won't be able to root it. Also never flash wrong model firmware like the PR version. In the past that was a last resort firmware (before we got a back to stock for the actual AT&T model. You could get lucky but chances are you'll get a board with the latest or just the last previous firmware especially if it has a newer serial.
Pretty much the AT&T G4 is a device you want if you don't tinker with the device. I honestly love the G4, until certain apps even new apps ran worse on the G4 than they do on my G2.
Sent from my iPhone using Tapatalk
Just got the H810 back, checking on the board info here in a bit (if I can even detect anything) but it's running H81022b so I'm guessing that means I'm stuck with it as is but that was somewhat expected. I'm not going to even bother attempting a rollback at this point, will just wait for the yellow leather cover to arrive in the next few days then I'll put it up for sale on craigslist I suppose and go from there.
I have to wonder exactly what they did because the board info that I can detect using the LG Info tool from the Play Store still lists the same info for board date/etc (January 2016) so I don't know what the hell they actually did.
Kinda sucks but it's how things go sometimes.
I want to open this thread about Nokia 7 Plus TA-1055 single sim (for those have this model variant like me), to discuss about it and about problems with custom boot/system/anything else flashing/installation, which works on another model variant (TA-1046 and TA-1062) instead.
Pie gsi gives "no SIM" bug on single sim variant of the the TA-1055
- Oreo GSI (I tried them personally) have a weird call bug. It's very impossible to call someone!!
- Custom kernel have some problems with TA-1055 model, instead of other variants
I'm running pixel experience gsi on my ta-1055. No Sim bug is fixed by popping the Sim out and back in. Super stable build. Way better battery life and so much faster. After every reboot/update you must pop the Sim out and back in and it works. I think it has to do with the fact that it's looking for sim2 first and can't find it because it doesn't exist.
Micahvdm said:
I'm running pixel experience gsi on my ta-1055. No Sim bug is fixed by popping the Sim out and back in. Super stable build. Way better battery life and so much faster. After every reboot/update you must pop the Sim out and back in and it works. I think it has to do with the fact that it's looking for sim2 first and can't find it because it doesn't exist.
Click to expand...
Click to collapse
It's works, thx
I have TA-1055 too. Does anybody received the february patch? I tried to install with my sd card the recovery always says that: expected 00WW_3_22C (SP04)
What is that mean?
terjekd said:
I have TA-1055 too. Does anybody received the february patch? I tried to install with my sd card the recovery always says that: expected 00WW_3_22C (SP04)
What is that mean?
Click to expand...
Click to collapse
Maybe because ta1055 is on version 3.39
Rubens95 said:
Maybe because ta1055 is on version 3.39
Click to expand...
Click to collapse
What is that mean?
terjekd said:
What is that mean?
Click to expand...
Click to collapse
in November Nokia7Plus have official 2 OTA branch, one in line 3.22* which is only with security patches and second line 3.39* which also have some apps updates...
then if for you sideload say "expected 00WW_3_22C (SP04" then you can try OTA 3.22* on instaled higher branch 3.39*...
now you can check what exact version you have installed (in Settings/System/AboutPhone is two version show, one in BuildNumber (me PieFeb is 00WW_3_39B_SP03) and one in AndroidVersion/BuildNumber (me show [email protected]@_3_39H)), and download right OTA files from 3.39YOURVERSION to 3.39NextVersion (and repeat until you finish on Februrary) here: https://forum.xda-developers.com/nokia-7-plus/development/ota-nokia-7-plus-ota-links-t3818774
(WARNING ignore 3.51X this is unofficial)
k3dar7 said:
in November Nokia7Plus have official 2 OTA branch, one in line 3.22* which is only with security patches and second line 3.39* which also have some apps updates...
then if for you sideload say "expected 00WW_3_22C (SP04" then you can try OTA 3.22* on instaled higher branch 3.39*...
now you can check what exact version you have installed (in Settings/System/AboutPhone is two version show, one in BuildNumber (me PieFeb is 00WW_3_39B_SP03) and one in AndroidVersion/BuildNumber (me show [email protected]@_3_39H)), and download right OTA files from 3.39YOURVERSION to 3.39NextVersion (and repeat until you finish on Februrary) here: https://forum.xda-developers.com/nokia-7-plus/development/ota-nokia-7-plus-ota-links-t3818774
(WARNING ignore 3.51X this is unofficial)
Click to expand...
Click to collapse
Thank you very much for your help!!
*disclaimer: Thanks for the help, but unfortunately nothing worked in the end,
Interesting. But I don't understand how this whole thing could even work. I am on 3.22H january security level. For starters, I can't install anything older than January updates. Also, 3.39 february update is out of the question again, as it's for 3.39, doesn't work with 3.22.
And the phone won't let me sideload anything older, saying "expected version: ...3.22H".
That's it, can't install older updates, can't roll back to oreo either. End of the line. Volume up, power button, then power button and volume up, apply update, connect usb, type in this type in that, check logs, switch fastboot slots, still wrong timestamp. It's 2 AM, wasted 2 hours of my life with "tutorials", combing through endless list of unorganized update files. This is my first android phone, and this is exactly what I expected unfortunately. 3.22H it is then. Wish windows phone was still a thing, I miss my Lumia so much.
Is timely updates too much to ask? Do I have to debug and flash my phone myself? Getting real tired of BS like this
sheppards1984 said:
It's 2 AM, wasted 2 hours of my life with "tutorials", combing through endless list of unorganized update files. This is my first android phone, and this is exactly what I expected unfortunately. 3.22H it is then. Wish windows phone was still a thing, I miss my Lumia so much.
Is timely updates too much to ask? Do I have to debug and flash my phone myself? Getting real tired of BS like this
Click to expand...
Click to collapse
Well, actually no one is forcing you to do updates on your own, so stop blaming anybody except yourself for wasting time. I'm not satisfied with the quality of updates too, but complaining so hard on XDA has no effect since HMD is not reading even their our forum for this phone.
I'm atm stuck at January patch 3.22, but do I care? No. Why? Security updates are something that keeps me calm not getting since they are almost useless. And as people report 3.39 nor 3.51 don't have any significant fixes which would really drive me crazy not having (maybe except for nav and notification bar coloring fix). I already perceived that HMD is a pile of crap and I don't expect them to do anything.
Once its get really bad with the stock rom experience I'll unlock the bootloader and flash some custom rom (i.e Pixel Experience), as they are getting better over time.
Sure, I'm not blaming anyone but myself, in fact I thank everybody for their effort...
But still I, bought this phone to just use it, not waste time and effort making it up to date, as they've advertised, then what? They split update paths... Anyway, I gave it a shot, I failed, moving on
Does anyone know when Google will start to actually post the images? This is the first phone I can remember having in my hand without any factory images posted.
I was wondering the same thing. Since no factory images are up, I tried the Android Flash Tool, which correctly identified the phone as a 4a, but said it was "unsupported". I've never tried the Flash Tool before, fairly easy to use, but I do wonder how fast the downloads will be. But, yeah, factory images should be up. I never completely trust a phone out of the box, prefer to do a wipe and flash before setup and use. I mean, it was probably built in China, right? I don't need any Chinese spies looking at my porn.
Well, today (Aug 20) was supposed to be the official debut, even though many of us have had these phones at least a couple of days now. If they dont have the images posted by tomorrow, then someone at Google is asleep at the wheel!
Maybe Android 11 is coming so soon they'll wait to post that?
Pig Vomit said:
I mean, it was probably built in China, right? I don't need any Chinese spies looking at my porn.
Click to expand...
Click to collapse
I think I read somewhere that, as Google is moving away from China, they've been producing more in Viet Nam. The Pixel 4a is supposed to be the first phone to be fully produced outside of China. That's cool, right?
i started tweeting at @madebygoogle & @googledevs asking them to upload factory images & kernel source lol maybe itll get someones attention but not counting on it
I emailed google support to ask if unlocking the bootloader and rooting the pixel 4a with magisk would void the warranty. The response was that it would not void the warranty. That convinced me to buy a second Pixel 4A to replace my other moto x4 as well.
I need to root only becaasue I need telephone call recording with bluetooth. I have paid versions of both Call Recorder (skvalex) and BoldBeast, but neither work with bluetooth if the phone is not rooted, so it is good to know I can root as soon as an image is available. Here is the response I got:
" I understand you'd like to know if unlocking the bootloader and rooting the device would void the warranty. Let me help you with the details. Warranty of your device is still covered regardless of whether a device was rooted or unlocked. However, if you are experiencing any issue after rooting the device, we might suggest you to unroot the same in order to get the issue resolved. Android is not against rooting, but we can't guarantee functionality if the source code for the Android OS has been modified hence we might ask you to unroot the device before helping you with the warranty options."
Reacon said:
I think I read somewhere that, as Google is moving away from China, they've been producing more in Viet Nam. The Pixel 4a is supposed to be the first phone to be fully produced outside of China. That's cool, right?
Click to expand...
Click to collapse
Box says phone made in Vietnam, accessories made in China. My problem with China is with human rights more than a concern about spying. My original post was meant to be funny. That having been said, Vietnam's human rights record isn't so great, either.
xenokc said:
Maybe Android 11 is coming so soon they'll wait to post that?
Click to expand...
Click to collapse
I'm kinda thinking this as well. I've got the final/release candidate Android 11 beta on my Pixel 2XL right now. It's pretty good, but there are a few problems I've noticed that should be cleaned up before it goes final. It wouldn't surprise me if they release another beta/Release Candidate #2. Google probably was shooting for a simultaneous launch, but couldn't get 11 finalized in time. I also assume there's a beta version of 11 for the 4a, because there has to be if it's about to be upgraded to 11, right? At least post those images up.
Pig Vomit said:
Box says phone made in Vietnam, accessories made in China. My problem with China is with human rights more than a concern about spying. My original post was meant to be funny. That having been said, Vietnam's human rights record isn't so great, either.
Click to expand...
Click to collapse
China has been throwing its economic weight around to effectively undercut any and all competition. It's just a reality if you want to have a manufacturing-based economy in 2020 that you'll have to make an incentive to drive business your direction. Unfortunately, many companies were in a catch-22 where if they report the rampant IP-theft in connection with the CCP they would either lose their competitive margin or potentially lose the ability to manufacture their product at all, because China also has hoarded the best tooling tech.
If there's one thing that the US' current administration has done correctly, it's to bare China's fangs. Hopefully, with commerce forcefully directed elsewhere, the dire need for profit margin will ease a bit in the poorer countries of the region, giving way for better human rights adherence. At least, that's my wishful thinking.
nogods said:
I emailed google support to ask if unlocking the bootloader and rooting the pixel 4a with magisk would void the warranty. The response was that it would not void the warranty. That convinced me to buy a second Pixel 4A to replace my other moto x4 as well.
" I understand you'd like to know if unlocking the bootloader and rooting the device would void the warranty. Let me help you with the details. Warranty of your device is still covered regardless of whether a device was rooted or unlocked. However, if you are experiencing any issue after rooting the device, we might suggest you to unroot the same in order to get the issue resolved. Android is not against rooting, but we can't guarantee functionality if the source code for the Android OS has been modified hence we might ask you to unroot the device before helping you with the warranty options."
Click to expand...
Click to collapse
Save that e-mail! While that rep said it won't, that doesn't mean it is true as a company policy. But the fact that you have it in writing from a Google rep gives you some ammunition in case they do try and say your warranty is void.
Yeah, I fired off a few tweets to @google asking them about the factory images. I think the more people who ask, more of a problem it will be for them,,,maybe.
renzyyy said:
i started tweeting at @madebygoogle & [URL="https://twitter.com/googledevs" @googledevs[/URL] asking them to upload factory images & kernel source lol maybe itll get someones attention but not counting on it
Click to expand...
Click to collapse
Does make for a September update a big question. Could G just start it on 11? Device rollout was delayed. Maybe a thought. I am hoping for a 10 release of at least our current as released build QD4A.200805.003. Especially if 11 bootloader has issues with . . . .
A nice comparison to my 3a, 3 is side by side the case of a 3 in size and a display more than 3a. Surprised hole punch (which would not think) goes away in most use...
reached out to google support team after making a fuss & finally got a pretty good answer...
In regards to Factory image availability on our developer page, the image would be updated post security patch of Sept. As it's a new device we are shipping the devices with August update, once the device specific builds are released it will reflect on Developer images.
Click to expand...
Click to collapse
kkjb said:
I am hoping for a 10 release of at least our current as released build QD4A.200805.003.
Click to expand...
Click to collapse
This is the build that it was released with. I was surprised, because I had read so many articles saying the phones had been assembled months ago and were in a warehouse waiting for release. I doubt they re-flashed all the phones, so I suspect they were manufactured more recently. I had expected a very old security release to be on them, but it's the August release.
Build # convention for .003 was carrier specific builds on rest of Pixel line...is a wonder.
Since I have a audience I get no Sprint dial code switching on Google Fi Network.
So TMobile here now...no chat messenger!
US Cellular is my other provider same thing. Call screen is working.
Radio sensitivity is better than 3a nice to have in the boonies here.
Yeah I kinda figured they would wait til the Sept patch is out to provide the factory images. Sucks a little that is over two weeks from now.
renzyyy said:
reached out to google support team after making a fuss & finally got a pretty good answer...
Click to expand...
Click to collapse
I'm usually a happy silent observer because the factory images are usually out when the phone comes out, but I am a little annoyed because I have my new phone and I don't want to set it up again in two weeks.
Is there any reliable way to dump the ROM and get the boot image without root?
SexySOnic23 said:
I'm usually a happy silent observer because the factory images are usually out when the phone comes out, but I am a little annoyed because I have my new phone and I don't want to set it up again in two weeks.
Is there any reliable way to dump the ROM and get the boot image without root?
Click to expand...
Click to collapse
Why would you have to set it up again? You can unlock the bootloader now.
digger16309 said:
Why would you have to set it up again? You can unlock the bootloader now.
Click to expand...
Click to collapse
Just because I want to flash Magisk, I can't do that without the boot image. Once I went TitaniumBackup, I never went back. But ya know, I need root for that
SexySOnic23 said:
Just because I want to flash Magisk, I can't do that without the boot image. Once I went TitaniumBackup, I never went back. But ya know, I need root for that
Click to expand...
Click to collapse
Yes, I do, too. But I roughed it out setting up the phone without it. Most of my apps had data in the cloud or their own backup file. I transferred other files manually. I'll root, but I don't need to setup my phone twice because I unlocked the bootloader first.
Just as the subject mentions. Curious if it's just me?
Nada. No update. And when I mentioned this on their forum, they deleted the post.
I even tried the thing where you remove the SIM and search for updates then. Didn't make any difference.
Searching with Sammoblie and Frija, only the carrier version(A536U) from Xfinity/Comcast has gotten it in the US.
I don't have it either, what bothers me most is that 13 was released for older A phones including lower priced models already. Is it possible that because this is an enterprise phone (at least in the USA) it requires more time for testing?
pj1980 said:
I don't have it either, what bothers me most is that 13 was released for older A phones including lower priced models already. Is it possible that because this is an enterprise phone (at least in the USA) it requires more time for testing?
Click to expand...
Click to collapse
What bothers me was how quickly Samsung deleted my post on their forum after I asked about this.
It's been like 6 weeks since the same phone in other countries was given this. It's quite annoying.
snark.shark said:
What bothers me was how quickly Samsung deleted my post on their forum after I asked about this.
It's been like 6 weeks since the same phone in other countries was given this. It's quite annoying.
Click to expand...
Click to collapse
Samsung's discussions has a sticky at the top that updates happen whenever (edit: or at least it did before). And that's definitely how it goes for all their devices.
Even Samsung flagships go through silly stuff for updates and Android versions so its not A53 only.
The A53 unlocked has carrier apps on it so its tied to the carrier testing. Why will US carriers release Android 13 for older devices before newer? No idea but that's how their testing is going. They have some reason.
Really, you will get it when you get it. If you just think it won't show up until the year 2721 then it should be easier for you lol.
Its frustrating I know for unlocked to be dependent on carriers. But, waiting, it will at least probably have less bugs so that's fine enough. A buggy device isn't fun at all.
edit: Also A52 appear to be doing better than the A53 in getting Android 13 and listed as Enterprise. So, I don't think Enterprise has anything to do with it.
edit: The end result appears to be what Samsung's sticky said which is updates happen when they happen.
Samsung promised 4 years of updates for this phone so they have about 3 more years to give us android 13.
tmeader said:
Just as the subject mentions. Curious if it's just me?
Click to expand...
Click to collapse
3 Days ago, my phone suddenly shut itself off, and then stuck itself in a bootloop and would not boot again. It's a Samsung A53 5G (ATT&T) running android 12 one UI version 4.1 at the time. After booting into safe mode and wiping application config data, it still would not come out of safe mode until I factory reset it and connected it to a wifi network.
Finally after all of this BS, I got it to boot normally, but then, as if by magic, my phone was running Android 13 UI Version 5.0!
WTF!?
So I spent an entire day recovering my bank accounts, cashapp, applications, and various accounts, and chalked this pain in the ass up to the game...
And then this morning, it ****in' happened again.
I'm done with Samsung. This phone has been a $500 piece of **** since day 1. It's not even 3 months old yet. Samsung has gone from the most badass manufacturer of android devices, straight to the bottom of the abyss in terms of quality.
The Bloatware they send with these devices now should be unlawful. The amount of YOUR resources they use to track every single thing you do, every place you go, every dollar you spend is unfathomably creepy and discomforting.
Do yourself a favor and get comfortable with 12. because 13 is an even bigger piece of ****, and in my case, it has totally wrecked my phone twice in 3 days now.
Do yourself an even bigger favor, and throw your samsung into the bottom of the ocean and go buy yourself an IPhone. I'm really sad about the way Samsung has turned out. I'm even more sad about the way Android has gone down the drain. And Google has turned into the world's most powerful creepy stalker with Facebook a close 2nd.
I think if people actually new just how intrusive these tech companies have become, they'd stop using them altogether. There needs to be new and better privacy regulations and trackers and spywares and metadata miners and these 'ad targeting' programs and applications should be illegal.
ImMrMyagiLafAtMe said:
3 Days ago, my phone suddenly shut itself off, and then stuck itself in a bootloop and would not boot again. It's a Samsung A53 5G (ATT&T) running android 12 one UI version 4.1 at the time. After booting into safe mode and wiping application config data, it still would not come out of safe mode until I factory reset it and connected it to a wifi network.
Finally after all of this BS, I got it to boot normally, but then, as if by magic, my phone was running Android 13 UI Version 5.0!
WTF!?
So I spent an entire day recovering my bank accounts, cashapp, applications, and various accounts, and chalked this pain in the ass up to the game...
And then this morning, it ****in' happened again.
I'm done with Samsung. This phone has been a $500 piece of **** since day 1. It's not even 3 months old yet. Samsung has gone from the most badass manufacturer of android devices, straight to the bottom of the abyss in terms of quality.
The Bloatware they send with these devices now should be unlawful. The amount of YOUR resources they use to track every single thing you do, every place you go, every dollar you spend is unfathomably creepy and discomforting.
Do yourself a favor and get comfortable with 12. because 13 is an even bigger piece of ****, and in my case, it has totally wrecked my phone twice in 3 days now.
Do yourself an even bigger favor, and throw your samsung into the bottom of the ocean and go buy yourself an IPhone. I'm really sad about the way Samsung has turned out. I'm even more sad about the way Android has gone down the drain. And Google has turned into the world's most powerful creepy stalker with Facebook a close 2nd.
I think if people actually new just how intrusive these tech companies have become, they'd stop using them altogether. There needs to be new and better privacy regulations and trackers and spywares and metadata miners and these 'ad targeting' programs and applications should be illegal.
Click to expand...
Click to collapse
That's not the experience of most people. Since you bring up Apple as if that will help you avoid this when it can happen there too: https://myphotoyear.com/ios-16-update-goes-wrong/
Its just a fact of life.
More or less it could be improved or solved by multi-OS versions at the same time (such as dual boot on a computer), slower major OS versions, etc. This is not how Google or Apple thinks though.
To add, you can of course improve loss of data by using system backup and also backing up your stuff separately. Though Android still isn't perfect there.
Of course, if you see an update, avoiding updating for some months might also help though not ideal.
edit: For instance you could have used the Samsung restore which may be presented on first use setup or even manually done in Settings > Accounts and Backups > Restore which will restore much if you used the online backup or backup to sd card. Some apps and data will be missing if apps don't support it, etc. Unfortunately, it seems to only offer one backup at least online so any backup on the account since might have destroyed it.
edit: using that and backing up to sd card includes 10GB of stuff on my phone whereas the online is suggested as 2GB (it backs up files and also eg debug built from source apps). So, if you want the best, it may be what you should do from now on. Then restore it if need be. Still, up to apps to support backup individually. Make sure to run it weekly or something.
Also, I know you're pissed about that. Try not to be pissed with me lol. Thanks.
I'm thinking we're in for weeks, or months, more wait. We haven't even gotten a January Security Update.
Just received the Android 13 (One UI 5.0) update last night on my unlocked phone. Also includes the Jan 2023 security update. Looks like they just made the January cutoff
Hmm I have unlocked a53 on t mobile, I checked for updates today and it said there were none.
I received the update today for Android 13 including dual sim support.
I been checking my A53 unlocked running on Visible every week since Christmas for an update. Today it found the Android 13 UI 5.0 update. downloading it now.
How is the new version? any bugs found?
ok, once my phone updated and rebooted now I am no longer connecting to 5G. I've rebooted a few times and nothing has changed. I'm stuck back on 4G.
tmeader said:
Just received the Android 13 (One UI 5.0) update last night on my unlocked phone. Also includes the Jan 2023 security update. Looks like they just made the January cutoff
Click to expand...
Click to collapse
5 days after your post (6 since you got the update), with daily checking, and it's still a No for me.
My A53 arrived this morning and upon turning it on, my device had a lot of firmware updates waiting for me. I just updated to Android 13 not too ago along with January's Security patch.
I happen to live in the US, use T-Mobile, and I'm using the international version with dual SIM support.
snark.shark said:
5 days after your post (6 since you got the update), with daily checking, and it's still a No for me.
Click to expand...
Click to collapse
Another 3 days...
Still no Android 13 update.
I may wind up going to the Samsung service location in my area. This is ridiculous.
snark.shark said:
Another 3 days...
Still no Android 13 update.
I may wind up going to the Samsung service location in my area. This is ridiculous.
Click to expand...
Click to collapse
They do rollouts on top of things.
You could of course use a sim from a different carrier that has the upgrade available and do it that way. Might just get it immediately or still not. Then switch back. That is a possible workaround.
Of course, if you see a signed image for download for Android 13 for your carrier. That might work too even though it still is a wait for it to show up that way.
I don't know if there's any other way here because of the CSC. It would be interesting to know if a Samsung service shop would do it for you. I can't imagine they would.
Received the update today. Seems to run faster.