Hi,
I, like many others, got forced onto Android 11. I have a lot of problems with it. With or without root. The most annoying of which is the wifi aggressively dropping/changing. Bluetooth failures. Volume drops that don't return to normal, forcing a reboot to fix. Clock and background/screen saver problems. System UI crashing. Keyboard freezing and lagging on certain sites with textareas. I used my phone without root for a couple days after the forced upgrade and all of these issues were present with or without magisk modules.
I'm interested in going back to Android 10 and blocking the a11 OTA in Hosts.
I'd like to get some help with a couple things. I'd like to make a FULL flashable backup of my current device as is. Just in case I mess something up, I can get back to this current state as worst case, very easily. Do I use the MSM tool and copy something? Do I boot twrp and push something over? Please advise the safe and smart way to get right back to a 1:1 of current install. I want to be very sure about this part.
After I know which way I can safely get back to current state, can I use the MSM tool to wipe and flash an older build of Android 10? Or is it a problem after being on 11 because of some restrictions (partitions, RO, twrp no mount) somewhere?
If I can get back to an older build of Android 10, I have a couple options (grayhat and httpcanary) to monitor the traffic to see what we need to block in Hosts for sure.
I'm open to other suggestions also. Someone in the root thread said they proactively tried to disable some services around update and it was still forced on them.
OnePlus 7T Pro 5G McLaren TMobile
Android 11.0.1.2HD61B
(Carrier unlocked, bootloader unlocked, magisk root)
Thanks for any help
Disable the T-mobile update app or ask them to disable it on their end, they can.
Backup all critical data by direct file transfer and verify... just in case.
There's no way to do a full nandroid backup, e.g. restoring things exactly back to how they are now. Best you can do is use the app Swift Backup to backup app data/settings along with Google's backup and OP's backup app.
As for OOS11, have you tried resetting back to stock (factory reset while running OOS11)? Chances are you just have some leftover things from OOS10 that didn't play well with the upgrade. So before you abandon OOS11, try that first (factory reset from stock recovery). Make sure you've copied any backups to your PC first. If the issues come back after restoring your backup from Swift Backup or from Google or OP, then you need to find out exactly what app(s) are causing issue or just start from scratch.
As for the MSM Tool, it will restore you back to OOS10 just fine on its own.
Lastly, the OTA updates are downloaded from https://android.googleapis.com
For example, the url for the latest OTA to go from latest version of OOS10 (10.0.43) to first version of OOS11 (11.0.1.2) was
https://android.googleapis.com/packages/ota-api/package/45ba72b0b2f7c643a09d2d0875459cd01b8db998.zip
I pulled that from the update log. So blocking
https://android.googleapis.com/packages/ota-api/*/
in AdBlock or other hosts file app should do the trick. It may still see an update available, but it will definitely continue to fail when trying to download it.
But try OOS11 clean (after a factory reset). I bet all your problems will go away. I have exact same phone, not a single issue on OOS11, bootloader unlocked, latest version of Magisk.
starcms said:
There's no way to do a full nandroid backup, e.g. restoring things exactly back to how they are now. Best you can do is use the app Swift Backup to backup app data/settings along with Google's backup and OP's backup app.
As for OOS11, have you tried resetting back to stock (factory reset while running OOS11)? Chances are you just have some leftover things from OOS10 that didn't play well with the upgrade. So before you abandon OOS11, try that first (factory reset from stock recovery). Make sure you've copied any backups to your PC first. If the issues come back after restoring your backup from Swift Backup or from Google or OP, then you need to find out exactly what app(s) are causing issue or just start from scratch.
As for the MSM Tool, it will restore you back to OOS10 just fine on its own.
Lastly, the OTA updates are downloaded from https://android.googleapis.com
For example, the url for the latest OTA to go from latest version of OOS10 (10.0.43) to first version of OOS11 (11.0.1.2) was
https://android.googleapis.com/packages/ota-api/package/45ba72b0b2f7c643a09d2d0875459cd01b8db998.zip
I pulled that from the update log. So blocking
https://android.googleapis.com/packages/ota-api/*/
in AdBlock or other hosts file app should do the trick. It may still see an update available, but it will definitely continue to fail when trying to download it.
But try OOS11 clean (after a factory reset). I bet all your problems will go away. I have exact same phone, not a single issue on OOS11, bootloader unlocked, latest version of Magisk.
Click to expand...
Click to collapse
Thanks so much for the detailed reply.
My main reason for rooting my phone is to have full speed tethering. If that worked, I would try a reset. Since it doesn't, it's a good excuse to go back to 10 on its own for me.
No simple method for a full nandroid backup is going to slow me down. I need to go thru my apps and make sure I don't forget about anything important for a reset or a downgrade.
Do you have any hypothesis on why they forced Android 11 so hard?
During the time I wrote this message, my wifi switched networks a half dozen times. When this first started after the force to a11, I thought it was strange because I wasn't rooted and any modules shouldn't have been affecting anything. They're only added props (for the tethering module anyway). I don't have the Qualcomm crash others are reporting but maybe something in the new settings are related and causing both problems, theirs and mine.
Do you have multiple APs within reach of your phone? I've tried to disable/enable different connection options in the wifi settings and handoff settings. Nothing seems to help. It wants to drop me off my AP to any closer AP, constantly. Which is particularly annoying because I'm constantly in ssh sessions and that closes them. I can avoid that somewhat by forgetting the other APs near me so it tries to stay connected to just one but I shouldn't have to do that. I never had an issue before the update. In fact, I was actually really happy with how stable Android 10 was for our device.
Appreciative said:
Thanks so much for the detailed reply.
My main reason for rooting my phone is to have full speed tethering. If that worked, I would try a reset. Since it doesn't, it's a good excuse to go back to 10 on its own for me.
No simple method for a full nandroid backup is going to slow me down. I need to go thru my apps and make sure I don't forget about anything important for a reset or a downgrade.
Do you have any hypothesis on why they forced Android 11 so hard?
During the time I wrote this message, my wifi switched networks a half dozen times. When this first started after the force to a11, I thought it was strange because I wasn't rooted and any modules shouldn't have been affecting anything. They're only added props (for the tethering module anyway). I don't have the Qualcomm crash others are reporting but maybe something in the new settings are related and causing both problems, theirs and mine.
Do you have multiple APs within reach of your phone? I've tried to disable/enable different connection options in the wifi settings and handoff settings. Nothing seems to help. It wants to drop me off my AP to any closer AP, constantly. Which is particularly annoying because I'm constantly in ssh sessions and that closes them. I can avoid that somewhat by forgetting the other APs near me so it tries to stay connected to just one but I shouldn't have to do that. I never had an issue before the update. In fact, I was actually really happy with how stable Android 10 was for our device.
Click to expand...
Click to collapse
Honestly I can't help. OOS11 made my phone even better than it ever has been. No exaggeration. And not a single bug or even issue. They probably saw the same results on their test phones and pushed it really hard because they knew people had been waiting a very long time for it.
That's why I really think you have some trash left behind from your OOS10 install that made the upgrade to OOS11 go crazy. Once you get your backups done, please try a factory reset on OOS11 and don't restore any Google or other backups and just see if you have any issues. It could all be due simply to needing a "fresh install"
Edit: As for high speed tethering, is that accomplished with a Magisk module? If so, it probably needs the tiniest change in directory names/path to be compatible with OOS11, just like the boot and shutdown animation modules
Edit2: And yes, my phone can see at least 15 APs while at home. Never have any trouble connecting via 802.11ac on 2.4 or 5ghz at home, and never had any trouble with other random hotspots.
You've got some OOS10 settings/junk/leftovers interfering with OOS11. Not trying to sound like an idiot TMobile tech, but in this case you do need to factory reset and I bet all issues go away.
starcms said:
Honestly I can't help. OOS11 made my phone even better than it ever has been. No exaggeration. And not a single bug or even issue. They probably saw the same results on their test phones and pushed it really hard because they knew people had been waiting a very long time for it.
That's why I really think you have some trash left behind from your OOS10 install that made the upgrade to OOS11 go crazy. Once you get your backups done, please try a factory reset on OOS11 and don't restore any Google or other backups and just see if you have any issues. It could all be due simply to needing a "fresh install"
Edit: As for high speed tethering, is that accomplished with a Magisk module? If so, it probably needs the tiniest change in directory names/path to be compatible with OOS11, just like the boot and shutdown animation modules
Edit2: And yes, my phone can see at least 15 APs while at home. Never have any trouble connecting via 802.11ac on 2.4 or 5ghz at home, and never had any trouble with other random hotspots.
You've got some OOS10 settings/junk/leftovers interfering with OOS11. Not trying to sound like an idiot TMobile tech, but in this case you do need to factory reset and I bet all issues go away.
Click to expand...
Click to collapse
I believe you. I don't think you sound like the robot techs either. Yes, it can be accomplished with a magisk module. Which I first tried to edit like the animation modules. When that was unsuccessful, I did it manually by creating/editing props. The tethering provision and dun props. I even tried them in combination with another apn using only ipv4.
Some other phones report the module still working in Android 11 so I was hopeful it was just a path adjustment or that manual would work. It's still likely it could be done but I have to balance how long someone with more experience to bring a solution might take, with how long I can get by with this 600kbps throttle. I have kids and having internet (capable of YouTube, 600kbps doesn't cut it, especially on multiple devices) available for long car rides is really helpful after they're tired of playing Eye-Spy
Appreciative said:
I believe you. I don't think you sound like the robot techs either. Yes, it can be accomplished with a magisk module. Which I first tried to edit like the animation modules. When that was unsuccessful, I did it manually by creating/editing props. The tethering provision and dun props. I even tried them in combination with another apn using only ipv4.
Some other phones report the module still working in Android 11 so I was hopeful it was just a path adjustment or that manual would work. It's still likely it could be done but I have to balance how long someone with more experience to bring a solution might take, with how long I can get by with this 600kbps throttle. I have kids and having internet (capable of YouTube, 600kbps doesn't cut it, especially on multiple devices) available for long car rides is really helpful after they're tired of playing Eye-Spy
Click to expand...
Click to collapse
Post the Magisk module for high-speed tethering and I'll take a look at it. It'll either be really simple to get it working on OOS11...or not lol.
All credit to the authors and yadda yadda.
There's another one floating around.
In this one, I changed it to be /product/ but didn't have success.
If you do have success on a11 with it, that'd be cool. I can find out if a reset will clear up these other issues I have or not
Hello everyone, I'm in a similar situation though I was wondering if it might be a different problem.
So I bought a 7TPro Mclaren off Ebay and for the last year, it's worked fine. the phone came factory unlocked, with zero issues connecting to Telus (my Canadian provider). Last month my phone force-updated itself to android 11, and nothing but bad things have happened since. screen frame-rate tanks randomly, apps are slow, battery's tanked, the works.
After resetting the cache 3 or 4 times and still having issues, I reset the phone to factory, stock settings, but the phone still performs poorly Maybe because I re-added all my apps and pictures via Oneplus backup? either way, I'm very fed up with how the phone has been especially the battery, so I've been looking into downgrading back to Android 10, but it seems that the Tmobile variant has trouble doing that (i.e. no simple menu option).
Should I try downgrading to Android 10 again and not bothering with a backup? I don't have too much to lose as of right now so I don't mind resetting it again, but if restoring all my pictures via backup is what's causing the issue I'm willing to do that. Should I make another Oneplus backup before I do this, or should I back up the data to my PC first? I find it very irritating that T-mobile forced this update so I will try and block the upgrade in my hosts but I'm worried that won't work because I don't plan to root my phone and block the hosts files.
Any tips or help would be appreciated!
DhoomLard said:
Hello everyone, I'm in a similar situation though I was wondering if it might be a different problem.
So I bought a 7TPro Mclaren off Ebay and for the last year, it's worked fine. the phone came factory unlocked, with zero issues connecting to Telus (my Canadian provider). Last month my phone force-updated itself to android 11, and nothing but bad things have happened since. screen frame-rate tanks randomly, apps are slow, battery's tanked, the works.
After resetting the cache 3 or 4 times and still having issues, I reset the phone to factory, stock settings, but the phone still performs poorly Maybe because I re-added all my apps and pictures via Oneplus backup? either way, I'm very fed up with how the phone has been especially the battery, so I've been looking into downgrading back to Android 10, but it seems that the Tmobile variant has trouble doing that (i.e. no simple menu option).
Should I try downgrading to Android 10 again and not bothering with a backup? I don't have too much to lose as of right now so I don't mind resetting it again, but if restoring all my pictures via backup is what's causing the issue I'm willing to do that. Should I make another Oneplus backup before I do this, or should I back up the data to my PC first? I find it very irritating that T-mobile forced this update so I will try and block the upgrade in my hosts but I'm worried that won't work because I don't plan to root my phone and block the hosts files.
Any tips or help would be appreciated!
Click to expand...
Click to collapse
Sorry to hear that.
Do fresh installs for the apps.
Do direct file transfers to/from the PC for all other critical data. "Restore it all" apps can fail miserably and are hard to verify the data they supposedly stored.
11 is a mess but this might help... or not.
DhoomLard said:
Hello everyone, I'm in a similar situation though I was wondering if it might be a different problem.
So I bought a 7TPro Mclaren off Ebay and for the last year, it's worked fine. the phone came factory unlocked, with zero issues connecting to Telus (my Canadian provider). Last month my phone force-updated itself to android 11, and nothing but bad things have happened since. screen frame-rate tanks randomly, apps are slow, battery's tanked, the works.
After resetting the cache 3 or 4 times and still having issues, I reset the phone to factory, stock settings, but the phone still performs poorly Maybe because I re-added all my apps and pictures via Oneplus backup? either way, I'm very fed up with how the phone has been especially the battery, so I've been looking into downgrading back to Android 10, but it seems that the Tmobile variant has trouble doing that (i.e. no simple menu option).
Should I try downgrading to Android 10 again and not bothering with a backup? I don't have too much to lose as of right now so I don't mind resetting it again, but if restoring all my pictures via backup is what's causing the issue I'm willing to do that. Should I make another Oneplus backup before I do this, or should I back up the data to my PC first? I find it very irritating that T-mobile forced this update so I will try and block the upgrade in my hosts but I'm worried that won't work because I don't plan to root my phone and block the hosts files.
Any tips or help would be appreciated!
Click to expand...
Click to collapse
Try another factory reset on OOS11 but don't restore any backups including Google app backups and see if problem still persists. Don't even bother logging in with your Google account at first. Just see if issues are fixed.
Morning b4 coffee rant:. I'm so tired of hearing this, TMobile/OnePlus didn't "force update" anyone's phones any more so than Google or any other manufacturer. This is my first OnePlus phone, probably will be the last because of all the serious quirks in rooting and just horrible software engineering by OnePlus and I want to throw it thru the window sometimes, but that's half from me screwing with it lol. Anyway, so I'm not OnePlus's biggest fan, but they didn't do crazy by releasing OOS11. That's how updates work...People had been (rightfully) been expecting it for a long time. And I don't have a single issue with it.
My battery life is much worse also. I blame it on the constant/aggressive wifi changes.
starcms said:
Try another factory reset on OOS11 but don't restore any backups including Google app backups and see if problem still persists. Don't even bother logging in with your Google account at first. Just see if issues are fixed.
Morning b4 coffee rant:. I'm so tired of hearing this, TMobile/OnePlus didn't "force update" anyone's phones any more so than Google or any other manufacturer. This is my first OnePlus phone, probably will be the last because of all the serious quirks in rooting and just horrible software engineering by OnePlus and I want to throw it thru the window sometimes, but that's half from me screwing with it lol. Anyway, so I'm not OnePlus's biggest fan, but they didn't do crazy by releasing OOS11. That's how updates work...People had been (rightfully) been expecting it for a long time. And I don't have a single issue with it.
Click to expand...
Click to collapse
They did force the update. There was no further postponement available. It's not cool that we have to jump thru hoops to take an OTA but the full version upgrade ignores root woes and forces itself to install. I don't mind jumping the hoops, so long as it's consistent.
I've never had this force update issue on any previous device. I've been able to ignore it indefinitely, and if rooted, need to do a manual intervention to take the OTA. I was in the middle of doing something when my phone shut down and installed a11.
This isn't my first OnePlus device. It is my first carrier tied/coupled OnePlus device. And will definitely be my last carrier coupled phone. I want to give OnePlus another chance. I had the 8 Pro and it was lackluster to say the least. I found a great medium with this device. It offered similar specs, 5G, good build quality at a reasonable price.
It may be true that other manufacturers force updates on some devices but it wasn't true for me with the Nexus or Pixel phones I had. Or my previous OnePlus device (5T/8P).
A lot of us are intentionally choosing OnePlus for the root and ubl friendliness with good specs.
I don't think anyone is saying A11 shouldn't be offered, it should be of course. It just shouldn't be forced and the safety net we thought we had to prevent that, was also swallowed up.
Give OnePlus another chance, this phone is not the typical OnePlus experience I've come to love. Or maybe this is the new OnePlus... I'm gonna give them another shot.
As a side note to this, my wife wanted the Samsung s21, coming from a OnePlus device. She is very disappointed with the s21 in just about every aspect other than the picture quality. Oppo and OnePlus are merging, I'm not even sure where to go after OnePlus
Appreciative said:
My battery life is much worse also. I blame it on the constant/aggressive wifi changes.
They did force the update. There was no further postponement available. It's not cool that we have to jump thru hoops to take an OTA but the full version upgrade ignores root woes and forces itself to install. I don't mind jumping the hoops, so long as it's consistent.
I've never had this force update issue on any previous device. I've been able to ignore it indefinitely, and if rooted, need to do a manual intervention to take the OTA. I was in the middle of doing something when my phone shut down and installed a11.
This isn't my first OnePlus device. It is my first carrier tied/coupled OnePlus device. And will definitely be my last carrier coupled phone. I want to give OnePlus another chance. I had the 8 Pro and it was lackluster to say the least. I found a great medium with this device. It offered similar specs, 5G, good build quality at a reasonable price.
It may be true that other manufacturers force updates on some devices but it wasn't true for me with the Nexus or Pixel phones I had. Or my previous OnePlus device (5T/8P).
A lot of us are intentionally choosing OnePlus for the root and ubl friendliness with good specs.
I don't think anyone is saying A11 shouldn't be offered, it should be of course. It just shouldn't be forced and the safety net we thought we had to prevent that, was also swallowed up.
Give OnePlus another chance, this phone is not the typical OnePlus experience I've come to love. Or maybe this is the new OnePlus... I'm gonna give them another shot.
As a side note to this, my wife wanted the Samsung s21, coming from a OnePlus device. She is very disappointed with the s21 in just about every aspect other than the picture quality. Oppo and OnePlus are merging, I'm not even sure where to go after OnePlus
Click to expand...
Click to collapse
You can block OTA a couple different ways. I've done it for over 5 years with AT&T, no root needed.
My 10+ is still running happily on Pie.
Appreciative said:
A lot of us are intentionally choosing OnePlus for the root and ubl friendliness with good specs.
Oppo and OnePlus are merging, I'm not even sure where to go after OnePlus
Click to expand...
Click to collapse
Xiaomi/Redmi/Poco meets the root and ubl friendliness. In some countries, they still have warranty coverage after unlock bootloader.
Good specs or not is vague between different phones.
Check XDA Xiaomi category and see the reply and thread count. It's to some point a sign of better price to the specs.
Use GSMarena to compare the spec.
Appreciative said:
Give OnePlus another chance, this phone is not the typical OnePlus experience I've come to love. Or maybe this is the new OnePlus... I'm gonna give them another shot.
Click to expand...
Click to collapse
Sadly, OnePlus hasn't been typical OnePlus in well over a year. Look how slow updates are now even for their latest non-carrier flagships beginning around 7T time (and can start to be seen as early as the 6T).
Appreciative said:
As a side note to this, my wife wanted the Samsung s21, coming from a OnePlus device. She is very disappointed with the s21 in just about every aspect other than the picture quality. Oppo and OnePlus are merging, I'm not even sure where to go after OnePlus
Click to expand...
Click to collapse
Oppo and OnePlus are merging, like you said, so won't they still continue producing flagship phones at a manic rate, like Samsung? At least Samsung has gotten much better with the speed of OTA updates, while OnePlus has tanked.
We're guaranteed Android 12 for our phones. Let's see how long it takes for us to get it, probably more than a year after I make this post. The 6T is still waiting for OOS11.
To be honest, receiving the 8 Pro was disappointing. I had the pixel 2xl and it's the only thing I've returned in a decade. I got the 5T for half the price and couldn't believe how amazing that phone was. It's still alive and crack free. I put it through a lot.
Getting the 8 Pro, I knew it was $1k but I expected a lot. I was disappointed. I liked it but not $1k-liked-it. And I realized then, that maybe OnePlus had already ended their founding principles. I was most disappointed that nothing about the 8P was pushing the envelope. The 5T was breaking the envelope and the 6 was doing big moves with giant storage and ufs3 speed. After that, partially because of how well the 5T was made, I didn't follow what they were doing. I didn't need to. Now we are at OP9 and you may be right that 'that oneplus' isn't here anymore.
I did look at some oppo devices. I knew that's the parent/sister company to OnePlus and would find similar features. It just worked out that the 7T Pro 5G dropped right after I got the 8P and I traded back.
I guess I got spoiled
Appreciative said:
To be honest, receiving the 8 Pro was disappointing. I had the pixel 2xl and it's the only thing I've returned in a decade. I got the 5T for half the price and couldn't believe how amazing that phone was. It's still alive and crack free. I put it through a lot.
Getting the 8 Pro, I knew it was $1k but I expected a lot. I was disappointed. I liked it but not $1k-liked-it. And I realized then, that maybe OnePlus had already ended their founding principles. I was most disappointed that nothing about the 8P was pushing the envelope. The 5T was breaking the envelope and the 6 was doing big moves with giant storage and ufs3 speed. After that, partially because of how well the 5T was made, I didn't follow what they were doing. I didn't need to. Now we are at OP9 and you may be right that 'that oneplus' isn't here anymore.
I did look at some oppo devices. I knew that's the parent/sister company to OnePlus and would find similar features. It just worked out that the 7T Pro 5G dropped right after I got the 8P and I traded back.
I guess I got spoiled
Click to expand...
Click to collapse
That's one reason I got this phone, OnePlus's prices are thru the roof. And no, I don't want any Nord crap. I want a flagship phone at a reasonable price. Got my 7T Pro 5G Mclaren for $500 brand new from eBay the day after the OP8/Pro launched. I just couldn't justify spending $1000 on a phone and I never will.
Related
Hey XDA, I've been a long time "user" of the forums yet I've never made a post on here until now. So I've got a Moto Xoom that is seriously hurting, and I feel like I've got myself painted into a corner with it. Before I blow it away and flash it with the stock ROM or a custom one, I wanted to make sure I've exhausted every last option to remove the MoneyPak ransomeware on the device.
Here is a link to techreport forums where I made a post about this issue to save you the trouble of me explaining it all again.
techreport.moc/forums/viewtopic.php?f=30&t=93799&p=1205113#p1205113 (change it to .com obviously, apparently without 10 posts I can't post links)
Any help with gaining access would be appreciated. I was hoping to simply just have ADB access to run this command...
Code:
adb uninstall com.adobe.flashplugin
I figured this will just remove flash all together and the MoneyPak malware can't run, and it wont be gotten again . As it stands right now as soon as I load into the OS moneypak takes over the screen and I can't do anything, so I'm unable to enable debugging mode or any other software settings.
Thanks in advance!
Your only option would be to boot up in Safe Mode. This disables all 3rd party apps. The launcher will crash continually and pretty much the only thing you'll be able to do is get into the Settings and uninstall whatever the app you installed that came bundled with. Seems to depend on what update it's on to whether or not there is a Safe Mode? I dunno, reports seemed spotty about what did and didn't work and it seems they are different between wifi and data models. And they made a Family Edition which is also different. Geez... But yea, see if you can do the Safe Mode. Other than that, it'd have to be reset.
http://www.xoomforums.com/forum/motorola-xoom-help/6209-xoom-boot-issues.html#post76504
Yeah, I believe I tried to get into safe mode, it was one of the first things I gave a shot. It is just the plain old WiFi model, one of the first ones out. Bought at Fred Myers like 2 weeks after release, maybe a month. Updated to the latest android release for the Xoom which I believe is 4.2.2.
Any clue if there is even a safe mode on it, I was leaning towards no. The VZW version apparently references a safe mode, but that's probably just for them.
I am currently fully rooted, running the latest jasmineRom. I liked the stock based kernal, had some nice features like tap to turn on, etc, and haven't dabbled in other roms such as CMMod, LiquidSmooth etc on the G3. Honestly I don't know if they have some of the features for waking the screen by tapping it that make the G3 usable without any front buttons, and changing roms and recustomizing / installing everything is a bit of a bear, so I haven't experimented with it.
My phone has the 5.1.1 update downloaded, keeps wanting to schedule it. (It actually tried to install itself, but I think TWRP prevented it from working). So now I am faced with the question of, what to do?
Do I let 5.1.1 install, and thereby gain Android Pay, which I did like, but lose root, which I enjoy for letting me debloat my phone? (Also G3 tweeksbox) Those are really the only things I've used root for. Do I experiment with other roms? (And then, how do I return to stock? Does TWRP prevent me from doing so, or would it get taken out in the update? I honestly don't know and have yet to find that information). I have read the Flash back to Stock using the KDZ method, which is actually how I rooted my phone to begin with, but it seems that is under the assumption I am running a stock rom / bootloader to begin with.
Just trying to get some input from people far more familier with this than I. If there is a way back to stock, including bootloader, what ROM would you recommend I try?
Thanks in advance!
Hi! Questions go in Q&A.
Be aware that if you take 5.1.1 that so far you *can't* root even if you want to, and you also can't currently downgrade.
If you're looking to return to completely stock including the recovery, so that you can take OTAs in the future, then flash the 24B KDZ with LG Flash Tool 2014. If you want to be rooted but be able to turn root off and on, you can do that with any, although I think Pay only works with stock. Another user on here just found out that merely temporarily deactivating root allowed him to use Pay just fine. Probably have to reboot in between turning it on and off - not sure.
Here are my thoughts on the subject: http://forum.xda-developers.com/showpost.php?p=63191071&postcount=135
Personally, I like rooting and twrp b/c of nandoid backups, debloating, removing ads and using titanium backup. I would feel truly lost without these options (and, to be perfectly honest, I love tinkering with electronics). If you decide to pass on the update for now, freeze system update using titanium backup, then wipe cache and that should remove the downloaded update in memory prior to installation . It's really a personal choice, but for me, I will likely stay where I am now rather than give up root.
The only reason I really rooted this phone was to get rid of bloat and fix the weak notification volume. I've never been one to jump aboard new updates as soon as they're released. Gonna wait it out and see if something happens with the root situation.
Decided I might as well try a custom rom, never used a custom rom on a phone, only tablets. Titanium backup and custom recovery are valuable tools, and decided it was worth the risk.
Went with Liquid Smooth, which I think has auto-updates ala CM Mod. So I get the benefits of 5.1.1, without the hassle of Verizon. Going to see what I think.
Thanks for the replies!
The update deactivates wireless charging. That was the deal breaker for me.
Edit: Turns out my wife and I both had a bad update. I used repair assistant and wireless charging is working again.
a2597 said:
Decided I might as well try a custom rom, never used a custom rom on a phone, only tablets. Titanium backup and custom recovery are valuable tools, and decided it was worth the risk.
Went with Liquid Smooth, which I think has auto-updates ala CM Mod. So I get the benefits of 5.1.1, without the hassle of Verizon. Going to see what I think.
Thanks for the replies!
Click to expand...
Click to collapse
Ive been running a CM12 based ROM for months now, it fixes almost everything wrong with the 5.0.2 update and with this update blocking root and downgrading, it seems CM12 based ROMS are the best choice for now.
timboger said:
The update deactivates wireless charging. That was the deal breaker for me.
Click to expand...
Click to collapse
Where did you hear that? A web search shows inconsistent functionality starting with v5.0 with various carriers, including one report of someone who tried everything to get it to work and couldn't, so he reassembled his phone and tossed it on the charger, and it started working.
DeanGibson said:
Where did you hear that? A web search shows inconsistent functionality starting with v5.0 with various carriers, including one report of someone who tried everything to get it to work and couldn't, so he reassembled his phone and tossed it on the charger, and it started working.
Click to expand...
Click to collapse
Sorry, I should of been clearer. The update to 35b, 5.1.1, will render wireless charging useless. It can not be rooted. If you decide to update then you will loose root until the devs can figure it out. That will have to wait until the kdz is available. I have been wireless charging since I got the phone and bought the new back from ebay. It has worked without fail until the latest update.
Clarification requested
timboger said:
Sorry, I should of been clearer.
Click to expand...
Click to collapse
I should have been clearer as well. I take it that you are saying that wireless charging stopped working on your VS985 phones when you upgraded to v5.1.1. That's distinct from saying that wireless charging no longer works when anyone upgrades the LG G3 to v5.1.1.
Certainly your one two data points are significant, but I'd like to know if it's confirmed that it won't work on other VS985 phones that upgrade to v5.1.1 (35B).
I'm tempted to go buy one of the charging backs and pads. Where did you get yours? I seriously considered it a year ago when I bought the phone, but the lack of a nice belt clip deterred me. How are you carrying the phone (eg, belt clip or what)?
Edit: I was told that the charging back made the phone thicker. However, a little research seems to suggest that's only true for Verizon's "Circle case" (eg, a combined front and back), which I don't need. Someone even reported that they just cut off the front case, and then it fit their belt clip holder. Also, another reporter said that it charged much slower. Comments on all of this?
DeanGibson said:
I should have been clearer as well. I take it that you are saying that wireless charging stopped working on your VS985 phones when you upgraded to v5.1.1. That's distinct from saying that wireless charging no longer works when anyone upgrades the LG G3 to v5.1.1.
Certainly your one two data points are significant, but I'd like to know if it's confirmed that it won't work on other VS985 phones that upgrade.
I'm tempted to go buy one of the charging backs and pads. Where did you get yours? I seriously considered it a year ago when I bought the phone, but the lack of a nice belt clip deterred me. How are you carrying the phone (eg, belt clip or what)?
Edit: I was told that the charging back made the phone thicker. However, a little research seems to suggest that's only true for Verizon's "Circle case" (eg, a combined front and back), which I don't need. Someone even reported that they just cut off the front case, and then it fit their belt clip holder. Also, another reporter said that it charged much slower. Comments on all of this?
Click to expand...
Click to collapse
I have the vs985 on verizon, purchased about 1 week after it's release. It is rooted since stump and I have run either Jasmine or skydragon (currently sd5.0/4.2 kernel) . I purchased the charging sticker (available on ebay at the time). I was able to put the sticker onto the original back of the phone and wirelessly charge it both with a circle case (US lgg3) and without. I also bought a Korean circle case that had a charging sticker built into it. I removed the european charging sticker and replaced that one with one of the ones that I purchased on ebay (again, for US, wireless charging) and that worked as well (did not need the original oem back in this situation as the circle case back served as phone back, again this worked on a US wireless charger perfectly (I have a tylt). Never used a belt clip, but hope that this provides you with some useful information. Charging was complete and never slow.
a2597 said:
I am currently fully rooted, running the latest jasmineRom. I liked the stock based kernal, had some nice features like tap to turn on, etc, and haven't dabbled in other roms such as CMMod, LiquidSmooth etc on the G3. Honestly I don't know if they have some of the features for waking the screen by tapping it that make the G3 usable without any front buttons, and changing roms and recustomizing / installing everything is a bit of a bear, so I haven't experimented with it.
My phone has the 5.1.1 update downloaded, keeps wanting to schedule it. (It actually tried to install itself, but I think TWRP prevented it from working). So now I am faced with the question of, what to do?
Do I let 5.1.1 install, and thereby gain Android Pay, which I did like, but lose root, which I enjoy for letting me debloat my phone? (Also G3 tweeksbox) Those are really the only things I've used root for. Do I experiment with other roms? (And then, how do I return to stock? Does TWRP prevent me from doing so, or would it get taken out in the update? I honestly don't know and have yet to find that information). I have read the Flash back to Stock using the KDZ method, which is actually how I rooted my phone to begin with, but it seems that is under the assumption I am running a stock rom / bootloader to begin with.
Just trying to get some input from people far more familier with this than I. If there is a way back to stock, including bootloader, what ROM would you recommend I try?
Thanks in advance!
Click to expand...
Click to collapse
I don't understand the issue.
I have an LG G3 with TWRP, Xposed and root; I can use Android Pay.
I had to jump through hoops but I can use it. Adding cards is a pain, but I can do that too.
To get it working you have to temp-unroot.
Install and configure Pay.
Re-enable root.
You will need to install Xposed and the module that provides cloaking for root, for Pay called -> No Device Check http://repo.xposed.info/module/com.pyler.nodevicecheck
Now you should be able to use Android Pay.
Jasmine 9.0 is out. I'd try that out. Its 5.1.1 with root
xdabbeb has the 35b bootstack that can be flashed to get advanced calling features working. Read about it.
Hey everybody. Just getting my new 2021 G Play up and running. For some reason, it seems slow as hell. Specs wise, it should be significantly faster than it is. I'm experiencing delays when typing, changing apps, and just the lag time from when you click a button until the screen changes and you can go onto the next task sucks.
Anybody have any tips? What might be causing the issue? I got the 3 gig RAM version, which should still be plenty. I feel like it's being artificially slowed by software and it would be nice to fix that problem.
kendogg41 said:
Hey everybody. Just getting my new 2021 G Play up and running. For some reason, it seems slow as hell. Specs wise, it should be significantly faster than it is. I'm experiencing delays when typing, changing apps, and just the lag time from when you click a button until the screen changes and you can go onto the next task sucks.
Anybody have any tips? What might be causing the issue? I got the 3 gig RAM version, which should still be plenty. I feel like it's being artificially slowed by software and it would be nice to fix that problem.
Click to expand...
Click to collapse
do a factory reset; then unlock your bootloader; then flash the retail US rom (retus) ; then root it with magisk; then de crapify til your heart is content...
or at the very least factory reset, and uninstall facebook
tbirdguy said:
do a factory reset; then unlock your bootloader; then flash the retail US rom (retus) ; then root it with magisk; then de crapify til your heart is content...
or at the very least factory reset, and uninstall facebook
Click to expand...
Click to collapse
I don't have facebook or anything else thats a big resource hog.
I bought mine unlocked directly from Motorola a few weeks ago, I assume it should have the retail US rom?
kendogg41 said:
I don't have facebook or anything else thats a big resource hog.
I bought mine unlocked directly from Motorola a few weeks ago, I assume it should have the retail US rom?
Click to expand...
Click to collapse
Yep, it's the retail rom. I am in the exact same boat as you, bought it a few weeks ago from Target US since I needed a decent unlocked phone to use with a high data prepaid sim. So far this thing is the best phone I've ever had. I'll share a few things I've learned/done since I've unlocked and rooted mine if you would like.
My device was reasonably quick out of the box and I noticed little if any lag. But I usually buy 50 dollar phones from walmart so I might not have the most reliable opinion about that. By the way the Facebook APK and a few facebook services reside on the phone, and I can't recall but they might even be installed out of the box but just deactivated. You'd be surprised how much crap is on this thing that sits idly by waiting for a compatible carrier SIM to give the phone the Go-Ahead to install.
So yeah, the tip I would suggest is to unlock the bootloader, install magisk and get root, then use some magisk modules and ADB scripts to start cleaning out the stuff you don't want. You'll be glad you did. I stripped out a lot of verizon installed services, amazon/facebook APKs, and all the motorola OEM apps I wasn't interested in, which was basically all of them. The phone is butter smooth. I have cloudflare DNS and ad aware installed, in addition to a couple of other modules.
I used to root devices years ago and took a break from around 2015 till now. Magisk is a slightly different experience than the way it used to be but for the most part it's dead simple and very flexible. On top of that, with the right flash tools and a copy of your firmware these devices seem nearly unbrickable. I've already soft bricked the thing a couple of times and it was just a matter of a quick magisk reflash and finangling some settings. Kept the same OS install, didn't lose anything.
Good luck! Let me know if you need any help.
Well this is good info, thanks. To be fair, this is about the slowest phone I've ever had. I'm coming from a OnePlus 6 thats been a constant headache too for the past couple years (everytime I wanted to make an outbound call I had to reboot the POS). I picked up the OnePlus second hand. I just can't stomach these $1k phone prices, and this has nearly the same specs as most of the $500 phones.
yeah, for me it was getting rid of the facebook.apk that came packaged. As soon as I did that it was a new phone. Didn't even need to bother with magisk this go around.
foxheadmat said:
yeah, for me it was getting rid of the facebook.apk that came packaged. As soon as I did that it was a new phone. Didn't even need to bother with magisk this go around.
Click to expand...
Click to collapse
Disabling the 3 Facebook system apps also works.
Hey yall,
So i updated my a52s a week ago to one ui 4, and this update just butcher my battery life and my phone in general.
Phone is laggy as hell
Animations are laggy
120hz feels like 60hz
Is there a safe way to get back to android 11 one ui 3.1?
will it harm any future updates or my phone?
Thanks in advanced
I'm not aware of any "safe" way to go back a version.
Try and clear your cache partition or do a factory reset and see if that helps with the problems.
koimr said:
I'm not aware of any "safe" way to go back a version.
Try and clear your cache partition or do a factory reset and see if that helps with the problems.
Click to expand...
Click to collapse
So im basically stuck with this disgusting update with out anything i can so to reverse it, but hope for samsung to address it one day?
Justaquestion2 said:
Hey yall,
So i updated my a52s a week ago to one ui 4, and this update just butcher my battery life and my phone in general.
Phone is laggy as hell
Animations are laggy
120hz feels like 60hz
Is there a safe way to get back to android 11 one ui 3.1?
will it harm any future updates or my phone?
Thanks in advanced
Click to expand...
Click to collapse
Got the update yesterday (CSC - MWD). Once installed, I rebooted immediatly into recovery mode and wiped the cache. Rebooted once again and I can tell you that eveything is fine and even smoother than One UI 3.1 (except for Careem - The equivalent of Uber that did close once launched but I managed to grab the apk from their website and installed it manually, now it works like a charm).
Animation on my device is set on 120hz and enabled developer settings to set animations to 0.5x
Arobase40 said:
Why don't you do a factory reset as suggested by @koimr ???
I don't think all other A52 5G owners have the same problems than you...
Click to expand...
Click to collapse
Because i already done it, and its still messed up.
As far as reddit goes, im not the only one with a52s that has these problems.
This phone is brand new(2 months) and it worked like a charm untill this update..
I just hoped for a way to go back to 3.1
dexlemaffo said:
Got the update yesterday (CSC - MWD). Once installed, I rebooted immediatly into recovery mode and wiped the cache. Rebooted once again and I can tell you that eveything is fine and even smoother than One UI 3.1 (except for Careem - The equivalent of Uber that did close once launched but I managed to grab the apk from their website and installed it manually, now it works like a charm).
Animation on my device is set on 120hz and enabled developer settings to set animations to 0.5x
Click to expand...
Click to collapse
Ill try that. Is it a common thing which i can find a guide on how to on youtube/google?
My device also was set since day 0 to 120hz. Everything was buttery smooth until oneui 4. Now everything feels laggy for some reason.
Justaquestion2 said:
Hey yall,
So i updated my a52s a week ago to one ui 4, and this update just butcher my battery life and my phone in general.
Is there a safe way to get back to android 11 one ui 3.1?
will it harm any future updates or my phone?
Click to expand...
Click to collapse
I've recently been bouncing from UI 4 to UI 3.1 numerous times, trying to diagnose and fix an issue with my S20+ 5G - even used firmware from 2 different countries. (XSA & XSG)
Used Odin3 v13.14.4 which I think is the latest on Sammobile.
Note: BACKUP - I had a problem on one flash using HOME_CSC back to 3.1 where it bootlooped - I should have tried simply turn off then start from scratch to see if it cleared but instead I did a factory reset. So be prepared for needing a reset.
Note: Samsung and other backups do not backup your data - I used Super Backup to save out my Contacts, SMS's and Calls. Also used the Backup to External option - faster than to online account.
Another possibility I tried at the end that I should have done at the start when I had everything - Smart Switch to my S8 first, then I could have used SS to get everything back.
Justaquestion2 said:
So i updated my a52s a week ago to one ui 4, and this update just butcher my battery life and my phone in general.
Click to expand...
Click to collapse
Another point - it's not uncommon for a new firmware to use battery in what seems excessive amounts for the 1st day or so. I did see a technical explanation years back but I can't recall what it was.
It's a good idea to let it settle in a bit before trying corrections.
Arobase40 said:
EDIT : Smart Switch is THE Samsung backup solution.
Click to expand...
Click to collapse
Not according to Samsung on the phone.
Plus it was less than useful in my case where I had NOT used it right at the start, so by the time I thought of the S8 I'd already had the impact of the other methods.
Luckily Super Backup and Swift Backup do a good job of backing up the essentials - I don't mind losing games scores but losing Contacts, SMS & Calls would have been a terrible thing.
Also, I figured if he didn't know Odin etc. he'd ask. I hadn't read all the thread, just responded to his OP.
Arobase40 said:
I used to help people for over 35 years on different medium, including at the time of Usenet and in Google groups and I know or I can guess when somebody don't or when he is lying lying because he won't admit he is a rookie or a totally noob. It's just a pity as he won't learn much and it's better to put the blame on the manufacturer or on someone else
Click to expand...
Click to collapse
Perhaps you didn't read my response correctly. It would be good to do that before calling someone a liar or noob. Did you even SEE this part?
Another possibility I tried at the end that I should have done at the start when I had everything - Smart Switch to my S8 first, then I could have used SS to get everything back
Click to expand...
Click to collapse
I didn't have a problem with smart switch - when I used it. It did not occur to me to pull out the S8 when I started this and Samsung tech service TOLD ME to use the back up to external card when I contacted them.
Not sure why you decided to be aggressive about it all.
I don't know if the bootloader got updated with the update on the A52s. If that's the case then you're stuck with OneUI 4. If the bootloader wasn't updated then you could go back to OneUI 3.1 safely with Odin.
ashraftheboss said:
I don't know if the bootloader got updated with the update on the A52s. If that's the case then you're stuck with OneUI 4. If the bootloader wasn't updated then you could go back to OneUI 3.1 safely with Odin.
Click to expand...
Click to collapse
With a new major Android version, there is a new bootloader. A11 to A12 is a major update, so no going back. As to the OPs problem, you will soon find out what app, game or setting is causing your problem if you do your detective work. Factory reset and installation of apps and games one at a time. Some apps and games are not compatible with A12 yet.
gerhard_wa said:
With a new major Android version, there is a new bootloader. A11 to A12 is a major update, so no going back. As to the OPs problem, you will soon find out what app, game or setting is causing your problem if you do your detective work. Factory reset and installation of apps and games one at a time. Some apps and games are not compatible with A12 yet.
Click to expand...
Click to collapse
Yeah, a bit time consuming but there must be something thats doing weird stuff in the background.
Journyman16 said:
I've recently been bouncing from UI 4 to UI 3.1 numerous times, trying to diagnose and fix an issue with my S20+ 5G - even used firmware from 2 different countries. (XSA & XSG)
Used Odin3 v13.14.4 which I think is the latest on Sammobile.
Note: BACKUP - I had a problem on one flash using HOME_CSC back to 3.1 where it bootlooped - I should have tried simply turn off then start from scratch to see if it cleared but instead I did a factory reset. So be prepared for needing a reset.
Note: Samsung and other backups do not backup your data - I used Super Backup to save out my Contacts, SMS's and Calls. Also used the Backup to External option - faster than to online account.
Another possibility I tried at the end that I should have done at the start when I had everything - Smart Switch to my S8 first, then I could have used SS to get everything back.
Click to expand...
Click to collapse
but using odin is safe for a future updates? it wont block me from future updates like rooting does?
contacts are stored in the sim card so that not a problem. call logs doesnt mind me to lose such as SMS.
pictures\videos - i can move to my laptop and then move it back to my phone.
apps - ill just download them again. not a big of a deal.
sorry for the dumb questions im just a rookie when it come to all of these firmware changes via 3rd party kind of things.
Journyman16 said:
Another point - it's not uncommon for a new firmware to use battery in what seems excessive amounts for the 1st day or so. I did see a technical explanation years back but I can't recall what it was.
It's a good idea to let it settle in a bit before trying corrections.
Click to expand...
Click to collapse
its been a week already tbh.
ill give u a walk through:
120hz always on, AOD, WIFI+DATA always on. all of these since day 1.
- pre update - my battery dropped 7%-10% per hour of reddit\browsing\youtube\multitasking for my work.
- post update - 25% per hour on these very same tasks.
- pre update - not a single drop of % over night.
- post update - 3-5% drop over night.
- pre update - only charged it once a day - over night. phone lasted me for a complete day. no matter what i did, or how i pushed this phone to the edge, the battery didnt die at all. lowest i got is to 17%.
- post update - on the very same useage as before - charge it twice a day.
- pre update - no lags, 120hz felt like 120hz, phone was buttery smooth
- post update - lags while scrolling\swiping, 120hz feels like 90hz sometimes. feels like refresh drops, like system is lagging
Arobase40 said:
I was also thinking about the use of PC Odin and flashing a firmware but 2 things came into my mind :
1) We don't know if his phone is a branded one or from USA...
2) I guess @Justaquestion2 might be a totally noob guy, so need to propose a tricky procedure to him. lol
He said to me he already tried to do a hard reset and a wipe cache and then he asked to @dexlemaffo "Ill try that. Is it a common thing which i can find a guide on how to on youtube/google?".... ^^
EDIT : Smart Switch is THE Samsung backup solution.
Click to expand...
Click to collapse
not from the US. phone is unlocked for every provider i want.
yeah, im a total noob when it comes to firmware changes.
i said i tried the factory reset, not the cache wipe. ill try that when ill get back home.
ive done factory reset before on my old androids, thats how i know how to do it, never did a cache wipe before. thats why i asked.
u act like im some paid actor to talk trash on android.
no need to look for "cracks" in my messages to seek for help. i aint lying to yall. i just look for help here. reddit guys guided me to this community.
thats about it.
Arobase40 said:
There is no link between the bootloader and any version of OneUI ! ^^
I upgraded from Android 11 to Android 12 with OneUI 4.0, then downgraded to Android 11 with OneUI 3.1 and once again upgraded to Android 12 with OneUI 4.0 with no problem at any level ! ^^
Didn't find any incompatibility with any apps exception with Magisk v23, but I don't use this phone very much as it is a secondary phone and my main phone is a Galaxy Note 9...
Click to expand...
Click to collapse
I stand corrected, the bootloader is still at version one on newest firmware with A52s and I am sorry for this misstatement. I still stand by my advice to OP about rather fixing the problems by factory reset and one by one installation of apps and games.
Since no one I know or have talked to has had any problems with Android12 on the A52s, rather on the contrary the phone has become better, I think that the OPs problem has nothing to do with the new firmware.
Arobase40 said:
That's mostly the reason I didn't suggest you to flash a firmware via PC Odin as even though it wouldn't block you with future updates since you flash official Samsung firmwares you need some background before you can use this kind of procedure....
The thing is that "real" factory reset is in the same place that Cache Wipe and that's also the reason I published 2 youtube links to your attention so you would know how to access these two function/options... ^^
@koimr suggested you to use this procedure but after your answer to @dexlemaffo with the same suggestion I understood you are a total noob. You said you need help that I can understand but you didn't post the good questions and you didn't say much about your phone and your technical level and that's the reason it's difficult to help you.
So first : do a factory reset and/or wipe cache as with the youtube links.
This should solve most if not all of your issues !
At the very end, do some searchs on how to download an official Samsung firmware, how to use PC Odin and how to flash this firmware. But I don't think you would need to reach this position.
Click to expand...
Click to collapse
well then i might havent noticed the cache wipe option over there for some reason. ill take a look again.
i'll take your advice and try both of them one after another just to make sure.
btw, as for an expert like you, does this looks valid to you?
is this the procedure you were talking about with odin?
if it does, any idea where can i get the files my model (SM-A528B\DS) needs?
gerhard_wa said:
I stand corrected, the bootloader is still at version one on newest firmware with A52s and I am sorry for this misstatement. I still stand by my advice to OP about rather fixing the problems by factory reset and one by one installation of apps and games.
Since no one I know or have talked to has had any problems with Android12 on the A52s, rather on the contrary the phone has become better, I think that the OPs problem has nothing to do with the new firmware.
Click to expand...
Click to collapse
is this the advice you were talking about?
:
"With a new major Android version, there is a new bootloader. A11 to A12 is a major update, so no going back. As to the OPs problem, you will soon find out what app, game or setting is causing your problem if you do your detective work. Factory reset and installation of apps and games one at a time. Some apps and games are not compatible with A12 yet."
- - - -
because if so, i already did a factory reset and downloaded all of the apps once again. nothing has changed.
even the SOT section where u can see which app took how many %, doesnt give me an answer.
meaning - if i lost 25% for example (85 to 60), and i go to the SOT section to see which app drained my battery, when combining all the app's % drain, i cant even get to 25%. its like some % doesnt even occur there.
the only apps i use are : reddit,brave,youtube vanced, banking app,telegram, twitter and some work apps. thats about it.
games - only codm once every 2-3 days for like 30min.
"I think that the OPs problem has nothing to do with the new firmware." - i understand your saying.
but, everything stayed the same before and after the update. same apps, same usage, nothing new installed, nothing new a been downloaded, changed nothing at all overall. just updated to android 12 oneui 4 with january security patch.. thats about it.
thanks in advanced for everyone who tried to help and specifically those who keeps on replying with ideas that might help. i appreciate yall.
Look, I won't smash you over complicated stuff. It is either easy or difficult, depending on many factors which are all within checkable distance.
The bootloader thing - I had a J7 Pro and when it got the OneUI 1 upgrade, it got an updated bootloader which, as stated in the update, wouldn't let you downgrade to a lower version of Android, and people who tried bricked their devices.
Now, if the bootloader stayed the same, as stated by another user, you could use Odin to either downgrade to 11, or do a clean install of 12. Since your phone has a problem, I'd recommend clean installing 12. It is easier.
However, if you want to go the hard way, and probably less intrusive way, I'd recommend installing Accubattery from the play store and letting it observe background usage for a while. It'll give you a more detailed run down of what could be causing problem, if the root of the problem is to do with an app at all.
I personally would clean install 12 with Odin again just to make sure everything sets up properly this time, bearing in mind that I'll lose all my data and will have to remember my google account info as FRP will be active. I don't like clearing cache and all these recovery mode things as I like a system to be untouched in anyway possible. It isn't normal for a phone to break down after an update but isn't impossible either.
I'd also like to know what you have already tried.
Don't hesitate if you have any question, but be sure to quote or tag me so that I know.
And a follow up post just to clear some doubts, SOFTWARE UPDATES CAN BREAK THINGS. Though not normal, it can happen. I had a J2 2015 come out of the box with broken software. It happens, and no matter how many times you'll reset your phone, that break or corruption will still be there. It is very very rare, but not impossible.
Odin is the most official way of flashing a Samsung phone. It doesn't break anything if done correctly, emphasis on the "done correctly" part. You'll have to chose the proper firmware package for your phone and have everything set up properly in terms of drivers and software. Odin and drivers are downloaded from Sammobile and firmware is dowloaded using Frija, which uses official sources free of any charge or speed throttling, unlike Sammobile. It ain't rocket science but it should be properly done. Watch some videos and get yourself familiar with the whole process before attempting it.
There is no right or wrong way of going through this. Multiple ways exist, some easier and some harder, some less invasive and some more invasive. I won't be adamant on doing this the ONE way only. How we go about this adapts to what you're facing.
That's all!
Justaquestion2 said:
but using odin is safe for a future updates? it wont block me from future updates like rooting does
Click to expand...
Click to collapse
Odin emulates the same process as the OTA (OverTheAir) updates - just make SURE you have the right firmware. I use Sammobile - join for free to dowload or pay a subscription for fast DL's, but unless you're constantly wanting firmware the freebie is fine.
Also, there are 2 CSC files when you unpack the compressed archive, the one starting as CSC will do a bare metal flash of the firmware; the one starting HOME_CSC will keep your settings etc and just update the system, modem etc.
Read thoroughly so you understand what you are doing.
DON'T mess with the various options unless you graduate to Expert - they can brick your phone.
Backup your data anyway, just in case. You never know - e.g. what if a power failure takes out your PC mid-flash? You want all bases covered.
Arobase40 said:
Perhaps you didn't understand I was not talking about you
Click to expand...
Click to collapse
Perhaps you should be more clear then. It certainly LOOKED like it was about me and I'm not particularly egotistical. You replied to me and then threw in random comments about liars and noobs?
Yeah... right...
Given the context it's either me or the OP and I must admit I did assume you wouldn't be so rude to a new guy. Looks like I was wrong. My bad.
Pretty much as the title says. I'm stock and unrooted, but the idea of an update that blows a physical fuse and can't be undone gives me the shakes. So I held off since it came out. We're about a month into deployment of the update, so I'm now considering applying it. Has anything in terms of major bugs/performance problems come out that should factor into my decision? I've read various threads here and not seen much major stuff.
Thoughts and input? Thanks in advance.
One reason for not going to Android 13 would be that It can mess up the wireless charging function . Mine has not worked properly since I updtaed , even after the patch ( which was supposed to fix it ) it still doesnt work .
Thanks. I've never used wireless charging but I appreciate this caveat to the A13 update.
Other than that all seems good , bit annoying for me as I use wireless charging a lot , have one in my car and this was a major factor in me buying a Pixel 6 . Had high hopes when they rolled out a patch pretty quick but nothing seemd to of changed .
Sad to hear it broke.
I'm afraid to accept major updates after the very final update ever for my OnePlus 6T broke several key functionalities I relied on. That led me to the Pixel 6, which I don't love but it is working "fine" and I hope A13 won't nuke me. I will likely update this weekend unless I hear something widespread and impactful to how I use the phone.
accessibility service not possible in non-store apps
miss said:
accessibility service not possible in non-store apps
Click to expand...
Click to collapse
WHAT... That's horrible... ACR won't work ) :
miss said:
accessibility service not possible in non-store apps
Click to expand...
Click to collapse
Just go to app info, click on 3 dot menu to bypass restriction.
I updated and I'm pretty happy. IIRC there's now a "developer" Android 12 build that works on the Android 13 bootloader if it ends up not being for you for any reason. I haven't seen any significant issues, though now I see people mentioning wireless charging I did notice it kept popping up the little "100%" screen every 5 or 6 minutes like I'd just put it on the charger when I was using the one in my car, after it hit full, but not the one in my room that provides a higher wattage. Either way, not a big issue to me.
Just be sure to read the other threads about updating to 13 and sideload the OTA after you update if you want to be certain you won't accidentally brick booting the un-updated partition after updating. It gave me a hassle sideloading from both of my PCs, but if you use USB 2.0 it'll go through, just... reeeeeally... sloooowly - so you could let it go overnight.
Jaitsu said:
I updated and I'm pretty happy. IIRC there's now a "developer" Android 12 build that works on the Android 13 bootloader if it ends up not being for you for any reason. I haven't seen any significant issues, though now I see people mentioning wireless charging I did notice it kept popping up the little "100%" screen every 5 or 6 minutes like I'd just put it on the charger when I was using the one in my car, after it hit full, but not the one in my room that provides a higher wattage. Either way, not a big issue to me.
Just be sure to read the other threads about updating to 13 and sideload the OTA after you update if you want to be certain you won't accidentally brick booting the un-updated partition after updating. It gave me a hassle sideloading from both of my PCs, but if you use USB 2.0 it'll go through, just... reeeeeally... sloooowly - so you could let it go overnight.
Click to expand...
Click to collapse
So, even unrooted and stock I have to fuss with the side load update thing?
Frankenscript said:
So, even unrooted and stock I have to fuss with the side load update thing?
Click to expand...
Click to collapse
You don't have to, it's just eliminating an unlikely risk. It'll work fine after just updating. Even if the update somehow failed you'd be safe as it would just roll back; the risk only lies in if you update, successfully boot, and then something causes Android to fail to boot, which should never happen if you're not rooted and tinkering with things.
Basically:
* Your phone has two "system" slots.
* Either taking an OTA from an automatic system update, or manually sideloading it, updates the slot you're not on, then switches to it.
* When you update to 13 and it successfully boots, a flag is set that permanently prevents booting with an older bootloader. (This is a one-time thing and shouldn't happen again with future updates.)
* At this point, if something caused Android to fail to boot, it might try to boot into the un-updated system slot. Because that flag is set and it still has the old bootloader, it wouldn't boot and would be bricked.
* Sideloading the OTA again (or even getting another automatic update, but that won't happen immediately) ensures this won't happen by updating the other slot.
Personally I'd just do it because I'm paranoid (and moreso because I personally do root and tinker with things I shouldn't all the time ).
Lughnasadh said:
Just go to app info, click on 3 dot menu to bypass restriction.
Click to expand...
Click to collapse
with any apk file, any application?
I use many that are not from any official store, such as motomedialink, which needs to have accessibility permission to work
miss said:
with any apk file, any application?
I use many that are not from any official store, such as motomedialink, which needs to have accessibility permission to work
Click to expand...
Click to collapse
As long as the accessibility permission has been restricted for that app because of the new policy (applies to Notification Access permission as well), it should work.
So far the update to A13 seems to have gone smoothly. I honestly haven't noticed anything different yet.
For what it's worth, one benefit I've noticed so far is that certain applications don't get shut down so aggressively as under A12. Despite all the tweaks I made previously, Angry Birds 2 would get shut down pretty much as soon as I did anything else on the phone, and Sound Profile would shut down randomly. Both of these seem fixed under A13.
Haven't noticed a downside yet in terms of how I use the phone.
I've been on A13 for two weeks now and everything seems to run smoothly, definitely dropped phone temperatures. I don't use wireless charging so can't tell about that. I'm on 13.0.0 (TP1A.220624.021.A1, Aug 2022) rooted. Tried loading 13.0.0 (TP1A.220905.004.A2, Sep 2022) but it won't boot, I'm getting "your device is corrupt it can't be trusted and may not work properly" error, had to revert back to previous one. Shame as I'm struggling with biometrics and this new update was suppose to fix the issue. Might try to flash_all with -w option this weekend to see if it makes any difference, can't be asked to be setting up my phone from scratch after three days of festival