ZTE Axon 10 Pro - Unofficial Upgrade Guide to Android 11 for US Model - ZTE Axon 10 Pro ROMs, Kernels, Recoveries, & Other

DISCLAIMER: Modifying a device may void the warranty on the device. It may also make the device unstable or may completely brick the device. The author does not take any responsibility for your device. Proceed at your own risk and only if you understand what you are doing! Do not attempt if you are inexperienced in flashing Android ROMs or other device modifications.
What this does:
1. Flashes your US-model Axon 10 pro to the official European A11 release which works except in the US except for the modem
2. Flashes the US-model modem after the Europe ROM is installed to bring back cell service and make the phone work with the ROM
What you will need:
Xiaomi MiFlash Tool https://www.xiaomiflash.com/download/
Full EDL image for A2020G https://disk.yandex.ru/d/tFL86aR5ESEVWQ (European flash)
ZTE SD card update to android 11 for A2020G https://oss.ztedevices.com/prod/cn/direct/germany/a10pro4g/A10 Pro 4G SD card software\(414360B1331MyOS11.3.4_A2020GPro_EEA\).zip (European flash)
Full EDL image for A2020U https://androidfilehost.com/?fid=17248734326145680432 (US flash)
Axon 10 Pro \\(Non-5G\\) EDL Tool https://www.androidfilehost.com/?fid=1899786940962580139
Make sure every download completes successfully before continuing.
Steps:
1. Make sure all files unpack successfully
2. Make sure you have the Google USB driver installed
3. Back up anything you need from the phone. Factory reset/wipe your phone, then reboot.
4. Reboot into EDL mode (power on with both volume buttons pressed).
5. Nothing will display on screen in this mode, but if you connect to your PC and run MiFlash (XiaoMiFlash.exe), then refesh, it should show a COM port connection.
6. Using MiFlash, select the "Full EDL image for A2020G" folder, then flash
7. After a successful flash, your phone will boot into the A2020G image. Wait at least 10 minutes. If it gets stuck on the logo screen like mine did, power off and boot into recovery (power plus volume down), factory reset/wipe your phone, then reboot.
8. Connect to Wifi, if you are prompted to install an update, go ahead and do it (I was not).
9. Extract the ZTE SD card update to android 11 for A2020G file on your PC.
10. Connect your phone to your PC as a media device, and copy the extracted update.zip to the root folder of your phone.
11. Go into Settings->System_>Updates and scan for an update. It should be found now and apply the update.
12. After reboot you should now see the "MYOS" logo. You now have Android 11 but need to flash the US modem for it to complete.
13. Unlock developer mode in settings and turn on USB debugging
14. Extract the Axon 10 Pro \\(Non-5G\\) EDL Tool on your PC
15. Extract the Full EDL image for A2020U file and find the modem.bin file.
16. Copy the modem.bin file to \Axon10_EDL_TOOL_v3.2.5\flash\modem.
17. Make a second copy of modem.bin in the same location
18. Name one file "NON-HLOS.bin" and another file "NON-HLOS_b.bin"
19. Run the EDL too "Axon10_EDL_Tool.bat" and connect your phone. Follow the instructions to reboot your phone into EDL mode, or do it manually (power plus both volume buttons)
20. Select the option to flash and then flash only the modem. It should work fine if your file names are correct.
21. Reboot, run through setup, and make sure you turn off automatic updates in settings
22. Enjoy Android 11 and curse ZTE for never releasing a promised update in the US
Full credit to le011
Edit: Fixed wrong URL on full EDL.

Thanks so much for this! Looking forward to trying it when I can set aside some time. Anyone have experience with A11 on the 10 Pro? GPS on mine got so bad after the update to Android 10 that I've been considering rolling back to 9. I'm basically just wondering whether ZTE fixed it in the A11 update. Cheers!

MarcelWhy said:
Thanks so much for this! Looking forward to trying it when I can set aside some time. Anyone have experience with A11 on the 10 Pro? GPS on mine got so bad after the update to Android 10 that I've been considering rolling back to 9. I'm basically just wondering whether ZTE fixed it in the A11 update. Cheers!
Click to expand...
Click to collapse
I had the GPS problem too. So far it locks immediately, but haven't tried it in the car yet.

bgroins said:
I had the GPS problem too. So far it locks immediately, but haven't tried it in the car yet.
Click to expand...
Click to collapse
I'm very excited about this. Keep us posted, thanks!

MarcelWhy said:
I'm very excited about this. Keep us posted, thanks!
Click to expand...
Click to collapse
My GPS is working 100% now, and f- ZTE for never fixing this since it was a software bug all along.

bgroins said:
My GPS is working 100% now, and f- ZTE for never fixing this since it was a software bug all along.
Click to expand...
Click to collapse
That's awesome. I'm both thrilled and infuriated I've long thought that the 10Pro was an excellent piece of hardware crippled by deficient software. Add you said: eff ZTE! Thanks again for streamlining and verifying the whole process

MarcelWhy said:
That's awesome. I'm both thrilled and infuriated I've long thought that the 10Pro was an excellent piece of hardware crippled by deficient software. Add you said: eff ZTE! Thanks again for streamlining and verifying the whole process
Click to expand...
Click to collapse
My sentiments exactly. Quality, solid piece of hardware crippled by a lack of support. I've had to shelve it all this time and buy a Samsung because of the GPS bug. Really frustrating. Live and learn I guess. Long-term support matters.

Awesome write up. I still need to get around to attempting this soon. Do you have any info on getting root/Magisk running on Android 11 on this device?

bgroins said:
My sentiments exactly. Quality, solid piece of hardware crippled by a lack of support. I've had to shelve it all this time and buy a Samsung because of the GPS bug. Really frustrating. Live and learn I guess. Long-term support matters.
Click to expand...
Click to collapse
It seems like my GPS issue may have been hardware-related after all. I completed the upgrade to Android 11 but subsequently had multiple GPS signal losses during a drive of less than half an hour. The compass also fails to maintain a proper heading even after calibration. Since the upgrade, I've also apparently lost VoLTE and VoWiFi. Bizarrely, there's now a new idle battery drain situation and the phone repeatedly stops and restarts charging when using a QC charger. I'll probably go back to Android 10 (or maybe even 9?) and see how the phone behaves. Either way, thanks again for your efforts!

So my experience with running Android 11 on the U variant is starting to be a hit or miss. Flashed everything correctly and did the correct modem procedure and I have a semi-working T-Mobile connection. However the modem does not always stay connected even though it shows I have signal. Couple times throughout the day I have to enable airplane mode and disable it to have random text messages start coming through and for my mobile data to actually stay connected. Friends have told me they tried calling me and their calls go straight to voice mail. When I go to check my voicemail I get a pop-up message that says I'm not connected to mobile data even though all settings are enabled correctly. Even made a new APN profile using settings straight from T-Mobiles website and still the same issues occur.
I'm going to reflash the modem when I get a chance and see if that fixes anything. I'm just posting this to see if anybody else using the U variant is having the same problems or similar. Otherwise I'm loving the rest of the features and UI on this device. This connectivity problem is a huge pain though.

brian117 said:
So my experience with running Android 11 on the U variant is starting to be a hit or miss. Flashed everything correctly and did the correct modem procedure and I have a semi-working T-Mobile connection. However the modem does not always stay connected even though it shows I have signal. Couple times throughout the day I have to enable airplane mode and disable it to have random text messages start coming through and for my mobile data to actually stay connected. Friends have told me they tried calling me and their calls go straight to voice mail. When I go to check my voicemail I get a pop-up message that says I'm not connected to mobile data even though all settings are enabled correctly. Even made a new APN profile using settings straight from T-Mobiles website and still the same issues occur.
I'm going to reflash the modem when I get a chance and see if that fixes anything. I'm just posting this to see if anybody else using the U variant is having the same problems or similar. Otherwise I'm loving the rest of the features and UI on this device. This connectivity problem is a huge pain though.
Click to expand...
Click to collapse
Did you happen to notice whether VoLTE was working? It wasn't for me, which is a deal breaker since my T-Mobile MVNO requires it to maintain service. Cheers!

Thanks @bgroins for the excellent hack. I followed the procedure yesterday and so far everything is working fine on T-mobile. Used GPS for more than 4 hrs today, didn't see any drop. The only difference I see in GPS is it takes long to fix after clear and update AGPS data through GPS Test. It used to fix to position faster while on A9 after clear AGPS. As this is one time activity, not something to worry as after it fixes, it doesn't drop connection, shows the right location while moving. If you don't clear, it shows the location immediately within 3-4 sec

ccraze said:
Thanks @bgroins for the excellent hack. I followed the procedure yesterday and so far everything is working fine on T-mobile. Used GPS for more than 4 hrs today, didn't see any drop. The only difference I see in GPS is it takes long to fix after clear and update AGPS data through GPS Test. It used to fix to position faster while on A9 after clear AGPS. As this is one time activity, not something to worry as after it fixes, it doesn't drop connection, shows the right location while moving. If you don't clear, it shows the location immediately within 3-4 sec
Click to expand...
Click to collapse
Is VoLTE working for you on T-Mobile? Was fine for me on Android 10 so I'm not sure what I could've done wrong in this update to kill it. Thanks!

MarcelWhy said:
Did you happen to notice whether VoLTE was working? It wasn't for me, which is a deal breaker since my T-Mobile MVNO requires it to maintain service. Cheers!
Click to expand...
Click to collapse
VoLTE does not even seem to be an option in Android 11 for some reason unless I skipped a specific setting for it. My assumption was Android 11 had it baked into the framework by default. But yeah Android 11 on the U variant is unfortunately a deal breaker for me as well as my service is very spotty and loses frequent connection even though it shows I have signal bars and am connected to the network under SIM settings. I have to do an occasional airplane mode switch to on and off and I notice I get text messages flooding in.
I had hopes for this as the modem was so easily flashable and we are able to get a semi functional connection but just no VoLTE. And since I don't think there's a way to get root on this version yet it's hard to look at the system files to get further in depth. Noticed this version doesn't have WiFi Calling either which isn't a priority but something I find strange doesn't come built into Android 11 and I thought even for other countries it would still be a selectable option.
Android 11 otherwise runs beautiful on this device aside from the needed services for some MNVOs.

MarcelWhy said:
Is VoLTE working for you on T-Mobile? Was fine for me on Android 10 so I'm not sure what I could've done wrong in this update to kill it. Thanks!
Click to expand...
Click to collapse
You are correct, I don't see that option in the configuration either. Neither Wifi calling as mentioned in another post.

I am also seeing "cell network not available" issue even when network shows full bars. I am also using T-mobile 4G LTE mini tower and while sitting next to it I see that issue. After toggling airplane mode it started working. Should we try modem.bin from A10 image instead of A9. or they would probably be same?
If I just flash modem.bin again, @bgroins, do I need to factory reset the phone?

bgroins said:
My sentiments exactly. Quality, solid piece of hardware crippled by a lack of support. I've had to shelve it all this time and buy a Samsung because of the GPS bug. Really frustrating. Live and learn I guess. Long-term support matters.
Click to expand...
Click to collapse
I'm trying to go back to A9 using the instructions here
[ROM][STOCK] Stock Firmware Packages (For Expanded EDL Tools)
Hi i want the Firmware for zte axon 10 pro 5g 6ram Details in photo https://forum.xda-developers.com/t/axon-10-pro-non-5g-edl-tool-flash-backup-restore-bootloader-unlock.3964605/page-10#post-84036799 My post
forum.xda-developers.com
and getting stuck at an error [see attached image]. The phone is in EDL mode but I may well be missing something obvious. Any help would be GREATLY appreciated. Cheers!

ccraze said:
I am also seeing "cell network not available" issue even when network shows full bars. I am also using T-mobile 4G LTE mini tower and while sitting next to it I see that issue. After toggling airplane mode it started working. Should we try modem.bin from A10 image instead of A9. or they would probably be same?
If I just flash modem.bin again, @bgroins, do I need to factory reset the phone?
Click to expand...
Click to collapse
I have personally tried modems from A9 and A10 and can safely say it makes no difference in compatibility. I believe the A9 modem did not even search for a network due to incompatibility, and the A10 modem from different versions just did the same thing as it does now. ZTE basically only designed this A11 to work on overseas networks. I don't see us USA users having any luck with it. I'm just going to have to go back to Lineage unfortunately. As far as I know, you don't need to do a factory reset as the modem gets flashed to a different part of the phone and factory resetting doesn't reset anything relating to the modem.
MarcelWhy said:
I'm trying to go back to A9 using the instructions here
[ROM][STOCK] Stock Firmware Packages (For Expanded EDL Tools)
Hi i want the Firmware for zte axon 10 pro 5g 6ram Details in photo https://forum.xda-developers.com/t/axon-10-pro-non-5g-edl-tool-flash-backup-restore-bootloader-unlock.3964605/page-10#post-84036799 My post
forum.xda-developers.com
and getting stuck at an error [see attached image]. The phone is in EDL mode but I may well be missing something obvious. Any help would be GREATLY appreciated. Cheers!
Click to expand...
Click to collapse
Try either different USB ports, or another USB cable. Also you may have to flash an A10 image first and then the A9. Have you tried using the other EDL Tool app by Unjustified Dev? Might have better luck. I'm going to be flashing my phone back to A9 later this week so I'll report back with any steps if I run into issues.

brian117 said:
I have personally tried modems from A9 and A10 and can safely say it makes no difference in compatibility. I believe the A9 modem did not even search for a network due to incompatibility, and the A10 modem from different versions just did the same thing as it does now. ZTE basically only designed this A11 to work on overseas networks. I don't see us USA users having any luck with it. I'm just going to have to go back to Lineage unfortunately.
Try either different USB ports, or another USB cable. Also you may have to flash an A10 image first and then the A9. Have you tried using the other EDL Tool app by Unjustified Dev? Might have better luck. I'm going to be flashing my phone back to A9 later this week so I'll report back with any steps if I run into issues.
Click to expand...
Click to collapse
Appreciate the response. I tried two different computers but I'll give your other suggestions a shot. Looking forward to a report on your A9 flash experience. Thanks!

brian117 said:
I have personally tried modems from A9 and A10 and can safely say it makes no difference in compatibility. I believe the A9 modem did not even search for a network due to incompatibility, and the A10 modem from different versions just did the same thing as it does now. ZTE basically only designed this A11 to work on overseas networks. I don't see us USA users having any luck with it. I'm just going to have to go back to Lineage unfortunately. As far as I know, you don't need to do a factory reset as the modem gets flashed to a different part of the phone and factory resetting doesn't reset anything relating to the modem.
Try either different USB ports, or another USB cable. Also you may have to flash an A10 image first and then the A9. Have you tried using the other EDL Tool app by Unjustified Dev? Might have better luck. I'm going to be flashing my phone back to A9 later this week so I'll report back with any steps if I run into issues.
Click to expand...
Click to collapse
Thanks for the response. I was on stock A9 due to GPS issues and while flashing A11, following first post, I took A9 modem. Will see few more days and then move to A9 if it shows too many issues.

Related

Any Questions!!!! (Ask me) you'll get a response within 24 hours

Ready, set, ask me anything!
I have a couple questions..
1. Is there any kind of ETA? I'm as patient as the next guy, but it's always nice to know! No worries if you don't have one though : )
2. Is there any proof of the K10 root working on the V10?
(not really a question but)
3. I know it's a very long time off, but in October of this year I will no longer be with Verizon and I'm willing to test anything around that time.
supermansbrother said:
I have a couple questions..
1. Is there any kind of ETA? I'm as patient as the next guy, but it's always nice to know! No worries if you don't have one though : )
2. Is there any proof of the K10 root working on the V10?
(not really a question but)
3. I know it's a very long time off, but in October of this year I will no longer be with Verizon and I'm willing to test anything around that time.
Click to expand...
Click to collapse
1. Sadly I have no ETA, right now I have an init and a new sepolicy. I'm able to dirtycow the sepolicy but I can't find any way to get the init across without the phone rebooting before it finishes. I need a way to like freeze the init in a way to make it available for transfer. So there's that and the other guy we are working with is gone right now and idk yet when he'll be back and ready.
2. Well, he is helping me out but he had the same issue with the init sadly. So stuck again
3. I have a question for you.. what version of Android are you on currently?
Currently running a V10 from Verizon, Android version is 6.0.
After recent updates (a few months ago) from Verizon, I noticed my call blocking software was no longer working. I had the software set to block any numbers not in my contacts.
I poked around in the phone app settings and the Android settings, all settings allowing me to block callers from mt phone had been removed.
Verizon's "solution" to be able to block up to 5 numbers free for 90 days (then you have to reblock them) simply does not meet my needs. Paying extra for their service to block numbers is just rude to me. I'd go to another carrier first.
Is there any way to get those settings back on my phone so I can block numbers from my phone again?
artcarney said:
Currently running a V10 from Verizon, Android version is 6.0.
After recent updates (a few months ago) from Verizon, I noticed my call blocking software was no longer working. I had the software set to block any numbers not in my contacts.
I poked around in the phone app settings and the Android settings, all settings allowing me to block callers from mt phone had been removed.
Verizon's "solution" to be able to block up to 5 numbers free for 90 days (then you have to reblock them) simply does not meet my needs. Paying extra for their service to block numbers is just rude to me. I'd go to another carrier first.
Is there any way to get those settings back on my phone so I can block numbers from my phone again?
Click to expand...
Click to collapse
All those settings to block calls from verizon are a verizon thing, once it's changed it's changed. Verizon's contract with us says they technically own the phone and we are just borrowing it. So my first guess would be no you can't get that software back. I could look, depends on what you were using. My suggestion though would check out an app on the play store to see what you get. Once we get root you can probably find a good software for it.
Do you expect roms to be available including nougat roms if/when root is achieved?
snapz54 said:
Do you expect roms to be available including nougat roms if/when root is achieved?
Click to expand...
Click to collapse
Maybe I'll start a project for one but it's a big maybe, I'm going to try to also push out the updates to be flashed over twrp.
artcarney said:
Currently running a V10 from Verizon, Android version is 6.0.
After recent updates (a few months ago) from Verizon, I noticed my call blocking software was no longer working. I had the software set to block any numbers not in my contacts.
I poked around in the phone app settings and the Android settings, all settings allowing me to block callers from mt phone had been removed.
Verizon's "solution" to be able to block up to 5 numbers free for 90 days (then you have to reblock them) simply does not meet my needs. Paying extra for their service to block numbers is just rude to me. I'd go to another carrier first.
Is there any way to get those settings back on my phone so I can block numbers from my phone again?
Click to expand...
Click to collapse
Actually, I've been using contacts+ and dialer+ from the play store on my last several phones and I no longer have to back up my contacts , call log, or texts! And, it has call blocking that does have the block everything not in your contacts. It has made rooting and breaking phones hurt a little less and/or be less of a pain in the @$$. I swear I have nothing to do with them, lol. I'm just a guy who likes to fiddle with this stuff who stumbled on this app purely by trial and error. If I can make one complaint, it's different than other dialers/contacts, and I don't think it's the prettiest app, but once you fiddle with it a while, it gets better. I wish I could skin it though, lol. Sorry for rambling, I just stumbled here and had to comment.
Root for LG V10 VS990 with MM
abine45 said:
Ready, set, ask me anything!
Click to expand...
Click to collapse
I was wondering if you could point me in the right direction?
I need to find a reliable, safe, proven way to root a LG V10 VS990 running MM.
Please, please, please help quickly.
Thank you so much!
~CM
cmccrar said:
I was wondering if you could point me in the right direction?
I need to find a reliable, safe, proven way to root a LG V10 VS990 running MM.
Please, please, please help quickly.
Thank you so much!
~CM
Click to expand...
Click to collapse
Sorry, I personally can't help. Be advised if you root an Android device now, Netflix won't work.
See: https://www.engadget.com/2017/05/14/netflix-no-longer-available-for-rooted-android-phones/
Not worried a/b Netflix, thanks though
artcarney said:
Sorry, I personally can't help. Be advised if you root an Android device now, Netflix won't work.
Not worried a/b Netflix, thanks though!
Click to expand...
Click to collapse
need help here. just bought my V10 refurb unit. they said its H900 at&t unit. its on lollipop with root out of the box so i cannot use any banking app. so i try to diry flash latest H900 firmware via LGUP. phone bootup but i cannot use due to force closed app. so i clean reflash it. now it booting as normal. but i cannot setup any fingerprint as it will force closed. so i came out a solution trying to clear cache and data . phone bootup still same. then suddenly its blank. only black screen with backlit on. so pull out the battery, now phone cannot turn on. only qdloader9008. so its hardbrick. try dismantle mainboard and its turn out im getting verizon vs990 mainboard with at&t firmware in it. now had no idea how to fix it. try those SDCARD using h901 system dumb as i cannot find any vs990 system dumb to work with. no luck, cannot enter download [email protected] fastboot mode. any help will be appreciated.
p/s : now im still not sleeping since yesterday trying to figure it out and my head feel like to exploded.
My parents both have the VS990 and recently their Wi-Fi calling has stopped receiving calls- calls can still be made (outgoing) but they go straight to VM incoming. My Verizon s7e on the same plan works just fine, leading me to rule out Network and Verizon. What is left is LG and Android (since I'm on N and they're still on MM). It seems that it occurred after the recent vzm upgrade from 27a to 28a. Nobody on Reddit responded to my thread, Verizon has been 0 help (they told my parents it was a SIM issue, swapped their SIM, "tested them" without putting the phones on airplane mode and sent them on the way telling them it was fixed..... thanks guys). I can't find any documentation or bug reports of this happening to anyone else- but, I'm not sure how many ppl depend on wireless calling like we do (satellite is our only method of telecom out here- no phone lines run, no dsl, no cell service.. we're in the middle of nowhere). I've tried resetting the Advanced Calling features. I've restarted the phones. I haven't done a factory reset.
A) Anything I've missed?
B) I found an img for 27a on here, is LGUP a feasible means still of downgrading/rolling-back?
Nothing going on
So my v10 wont charge, wont turn on, there's no charging notification light or anything. the only thing that gives me hope is that when I plug it into my laptop, my computer detects it because I can hear the sound. I cant get it into any of the modes, download..recovery..ect. any suggestions?
Hey could you please help me figure out something. I have an LG V10 H901 (purchased from China) its supposedly the T-Mobile version but was manufactured in Korea. Its WIFI and bluetooth weren't working so I tried to update its firmware using LGUP. However, after the update it was hardbricked. I have managed to get to the LG logo using H90021w Unbrick Qfil files. Afterwards I tried to flash stock firmware H90130d_00_0611 using lgup. However, I got a message about partition changes and hardbrick once again. I have also tried KDZ files related to F600L, h90021w and many others. Can you please suggest based on my details:
-Correct QFIL files
-Correct Firmware or KDZ
Phone Details:
IMEI:354017070602111
Model:LGH901BK
Suffix:ATMOOP
Buyer:TMO
Software Verison:H90130D_00
OS Version:N
File Name:H90130d_00_0611.kdz
KDZ File size:1975399272
No Luck
abine45 said:
Ready, set, ask me anything!
Click to expand...
Click to collapse
So my Lgv10. Doesn't show that its charging, doesn't turn on, doesn't do anything at all. It does however connect to the computer in the whole qualcomm hs-usb qdloader9008 mode thing. ive been doing the qfil thing because that seems to be the only thing that detects my phone but nothing is working. are there any other options? oh it says its the lgh900. but the motherboard is the vs990. does that make a difference? I have files for both
Been a while since I've touched a LG device but i'll respond to everyone tonight.
Shiah said:
So my v10 wont charge, wont turn on, there's no charging notification light or anything. the only thing that gives me hope is that when I plug it into my laptop, my computer detects it because I can hear the sound. I cant get it into any of the modes, download..recovery..ect. any suggestions?
Click to expand...
Click to collapse
Uh, check in device manager, see if you are in a qualcomm mode
nabilsp said:
Hey could you please help me figure out something. I have an LG V10 H901 (purchased from China) its supposedly the T-Mobile version but was manufactured in Korea. Its WIFI and bluetooth weren't working so I tried to update its firmware using LGUP. However, after the update it was hardbricked. I have managed to get to the LG logo using H90021w Unbrick Qfil files. Afterwards I tried to flash stock firmware H90130d_00_0611 using lgup. However, I got a message about partition changes and hardbrick once again. I have also tried KDZ files related to F600L, h90021w and many others. Can you please suggest based on my details:
-Correct QFIL files
-Correct Firmware or KDZ
Phone Details:
IMEI:354017070602111
Model:LGH901BK
Suffix:ATMOOP
Buyer:TMO
Software Verison:H90130D_00
OS Version:N
File Name:H90130d_00_0611.kdz
KDZ File size:1975399272
Click to expand...
Click to collapse
In device manager what is your phone coming up as?
thetestis said:
My parents both have the VS990 and recently their Wi-Fi calling has stopped receiving calls- calls can still be made (outgoing) but they go straight to VM incoming. My Verizon s7e on the same plan works just fine, leading me to rule out Network and Verizon. What is left is LG and Android (since I'm on N and they're still on MM). It seems that it occurred after the recent vzm upgrade from 27a to 28a. Nobody on Reddit responded to my thread, Verizon has been 0 help (they told my parents it was a SIM issue, swapped their SIM, "tested them" without putting the phones on airplane mode and sent them on the way telling them it was fixed..... thanks guys). I can't find any documentation or bug reports of this happening to anyone else- but, I'm not sure how many ppl depend on wireless calling like we do (satellite is our only method of telecom out here- no phone lines run, no dsl, no cell service.. we're in the middle of nowhere). I've tried resetting the Advanced Calling features. I've restarted the phones. I haven't done a factory reset.
A) Anything I've missed?
B) I found an img for 27a on here, is LGUP a feasible means still of downgrading/rolling-back?
Click to expand...
Click to collapse
I would update to the latest version. and I would factory data reset. I would also say that wifi calling is brutal and something that I wouldn't use all that much personally. any more questions you can ask

Recover data on phone with failed automatic update

I have an Honor 9 which automatically recieved the update to EMUI 9 during a vacation a week ago. It installed during the night and failed. Since I wasn't given a warning about the update I hadn't made a backup of all my stuff before updating. I had disabled the automatic update, but Huawei appearently doesn't respect that.
The phone is not rooted and the bootloader is still locked. The phone boots twice when turning it on and ends up on the eRecovery page. I cannot connect to is using the HiSuite (though Windows plays the device connected sound when I connect the phone via USB).
I would really like to somehow get into the data partition and copy all my stuff out before doing a hard reset on the phone to hopefully get it working again (or get a new from Huawei).
Question: What are my options?
I'm not the only one affected by this, but since Huawei is completely silent regarding this issue, they probably won't fix the problem.
From what am hearing they know about it
Apparently it's once in a blue moon but they could patch it with 9.1 that will come and push it faster than what 9.0 has been
At the moment I doubt they'll publicly state that it's happening
dwhite1972 said:
From what am hearing they know about it
Apparently it's once in a blue moon but they could patch it with 9.1 that will come and push it faster than what 9.0 has been
At the moment I doubt they'll publicly state that it's happening
Click to expand...
Click to collapse
Does that mean that if/when they push a new package, my phone might be able to update through the eRecovery and my data could be intact?
ChauIntl said:
Does that mean that if/when they push a new package, my phone might be able to update through the eRecovery and my data could be intact?
Click to expand...
Click to collapse
Possible but I don't know just how honestly just reach out to the support and see if they want to work for once
dwhite1972 said:
Possible but I don't know just how honestly just reach out to the support and see if they want to work for once
Click to expand...
Click to collapse
I did call support in Denmark (where I live) but while they understood my frustration, all they would do was to advice me to go to a service center and let them reset the phone. They couldn't say if they would be able to backup the data. In Germany and Italy the won't backup the data due to "privacy reasons".
They would notify their own support about the problem, but they wouldn't even return to me if they found a solution?!?!?! So the only way for me to know if they found a solution is to keep trying eRecovery and see if a package shows up or scour the web for anything looking like a solution.
I'll bump this question. It has now been more than a month since I contacted Huawei and they haven't shown any sign of trying to help.
What options do I have with respect to getting my data out?
ChauIntl said:
I'll bump this question. It has now been more than a month since I contacted Huawei and they haven't shown any sign of trying to help.
What options do I have with respect to getting my data out?
Click to expand...
Click to collapse
very low. I think your first priority should be getting it fixed. I'm afraid Huawei really don't care
Hi Robert,
What do you mean by getting it fixed? As far as I know the phone is fully functional but the update that huawei forced out was broken. The phone worked just fine before automatically applying the update.
Regards Casper

Safe full backup - back to Android 10 help

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.

Question Is there a way going back to one ui 3.1?

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.

Question Any reason not to accept Android 13 Update (stock/unrooted)

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 ‍

Categories

Resources