Just got the OTA tonight, 6/24
Notes:
Android security update: June 1, 2020
thanks
muffnman said:
Just got the OTA tonight, 6/24
Notes:
Android security update: June 1, 2020
Click to expand...
Click to collapse
ok
Still waiting on it here, anyone else?
I haven't been able to get it. I'm not particularly worried about it, being a security update it would be nice to have though. The last one took a while as well.
ttabbal said:
I haven't been able to get it. I'm not particularly worried about it, being a security update it would be nice to have though. The last one took a while as well.
Click to expand...
Click to collapse
I live in the Seattle area and I still can't get 36 yet.
Still haven't gotten it here either
Still waiting as well
Still nothing here also. Normally I would just run the MSM tool and get 10.0.36 that way, but my phone is running so nice on .35, I don't want to have to set it all up again.
NotATreoFan said:
Still nothing here also. Normally I would just run the MSM tool and get 10.0.36 that way, but my phone is running so nice on .35, I don't want to have to set it all up again.
Click to expand...
Click to collapse
Same. Wish there was a way to run msm tool without it wiping data or be able to extract fastboot images from it...
Everyone still waiting? Been 2 weeks since it was released and received by some/most...
Still waiting here- no update.
Yup. Tried unrooting just to see, no change. Weird, but I guess I don't NEED it. I do wish they would allow us to side load them though. I prefer to be up on security updates.
Woke up to some weird quirks with my phone and the Play Store, so after hours of troubleshooting, I just restored to 10.0.34 using MSM. I'm in the process of unlocking, fixing the reserve.img, and updating the 10.0.36 via OTA.
I'll update my reserve.img fix as soon as I'm done, so that anyone wanting to MSM straight to 10.0.36 won't have to jump through the same hoops.
Still waiting here in NY...
Still waiting in california
Im starting to think I will not get this update. Anyone find a reason why these updates are not coming through?
I think the issue is if you mount / (root) as r/w even once, it screws up the checksums and the updates don't come through.
I used the msm tool to update to 10.0.36 (losing all my data in the process) and the tool for 10.0.36 to restore reserve (tyvm @NotATreoFan), but even after updating, in security it was showing security update as June 1, 2020 (which is correct for 10.0.36) but for Google Play system update, it was still showing April 1, 2020 with a red icon instead of green. Clicking it and searching for updates didn't help (no updates found). Updating play services manually didn't help. But after 2 or 3 days, it must have updated in the background because Google Play system update is now showing July 1, 2020 (with security update showing June 1, 2020). Just FYI, the Google Play system update is part of project mainline (an extension of project treble) which allows Google to update parts of the phone without going through any oems or carriers. So even the msm tool for 10.0.36 only comes with the Google Play system update from April 1. Luckily as I said, it updates in the background after just approx 2 days.
But back to the main issue of not receiving the 10.0.36 update, maybe it's a waiting game, but it's never taken this long before. As I said, I think it's from you or a badly written magisk module from setting root directory to r/w even once (even if restoring it back to r/o without making any changes). If I'm correct, the only way to fix is by running the msm tool (since OnePlus refuses to let us have downloadable OTA updates or even a full fastboot package)
Edit: Also, if you have previously fixed your persist for FP to work, you'll have to restore your backup of fixed persist after running the msm tool and then unlocking the bootloader or your FP sensor won't work. Also, as mentioned above, you'll need to restore the reserve partition as well since the msm tool locks the bootloader and unlocking it causes reserve to be deleted. Don't you just love this phone...
Pic added to clarify the difference in the two types of security updates
I don't think there is any great need to update to this one, but I'll probably do the next one via MSM just to keep reasonably up to date.
Honestly, I really do like the device overall. It works well, is snappy, and has decent 5G support. I do not like that it's hobbled by TMO like most carrier devices on the software side. But at the same time, non-carrier devices often have issues with volte, which is going to be required here soon. Oneplus seems to support the international version pretty well, so it seems obvious this version is being held up by TMO. Sad, overall I like them.
What I don't get is that when I first got the phone I rooted it and few weeks later I got a OTA. I had to removed Magisk and replace the adb recovery with the stock one. Then the OTA updated without a issue and did the re-root procedure. After that I put back the reserve file(supposed to fix OTAs). And now no OTA? Weird because unless something was part of the updated I don't understand why the first update came through but not the next one...
t436h05t said:
What I don't get is that when I first got the phone I rooted it and few weeks later I got a OTA. I had to removed Magisk and replace the adb recovery with the stock one. Then the OTA updated without a issue and did the re-root procedure. After that I put back the reserve file(supposed to fix OTAs). And now no OTA? Weird because unless something was part of the updated I don't understand why the first update came through but not the next one...
Click to expand...
Click to collapse
Well if it had updated correctly previously, your reserve file had already been restored, so there was no need to restore it again.
But regardless, all of those errors that were seen if reserve hadn't been restored, or if boot or recovery images hadn't been restored to stock, were installation errors. The OTA was found, downloaded, but there was an issue on installation.
The problem now is that no OTA is being found. I'm beginning to think they possibly pulled 10.0.36 due to some bug, because no one has had to wait for an OTA this long previously. The only thing that should stop an OTA from being seen/found is if one had updated their fingerprint (to spoof a pixel for example).
At least from your screenshots, you see that Google was able to install their "project mainline" update. It's in the pics from security under Google Play System Update (is completely separate from Play Services) dated July 1, 2020.
Let's hope T-Mobile gets this missing OTA crap fixed asap
Related
So, In order to better prepare for the Nougat update whenever Lenovo/Motorola decided to give it's U.S. customers the official OTA, I had decided to Unroot my phone and install Stock firmware official version .64. Went through all the steps, got a No command error screen when trying to get to recovery, also showed Modified in FastBoot mode. Also, I had decided to do this because I was having some irritating Error Report issue always downloading.
Anyway, I learned that I can hold Power then press UP volume button once then release power to get to Recovery despite the "No Command" screen. Also, eventually that I needed to downgrade to .49, then accept the .64 OTA in order to get rid of the "Modified" message in Fastboot Screen. So, went through all the trouble to download the .49 firmware, flashed it, etc. When I got into my phone, I checked for Software updates as soon as I was able, to get the .64 update. But, lo and behold, instead I was gifted with a screen explaining that I would instead be getting Androud 7.0 Nougat. Awesome. I live in California. Was totally not expecting Nougat, because I check almost every day and would never get that long awaited message lol.
So I am surprised. I noticed, when I flashed straight to .64 firmware and checked for Software updates, I Did Not get the Nougat OTA notification. Only with the .49 firmware. I didn't think to take a screen shot, and am currently downloading the Nougat update now. When it is installed, I'll take a screenshot of the firmware version once booted into my phone. It's about time, I'm going to be ordering the G5 for my wife tomorrow, and was a tad bit jealous that it would already come with Android 7.0 lol. Hope this gets the rest of you American users excited, and hope this information helps. You can find a guide how to downgrade here in the forums or google, or at stechguide website. PS- I cannot guarantee nor take responsibility that you will have the same luck to get the OTA as I did. Downgrade at your own discretion.
Notice the firmware version. Joy!
I would have done this if I waited 2 weeks earlier. If more people get it and can confirm, just maybe I will unroot and go back to stock. But I love all the customizations with Resurrection Remix.
selw0nk said:
I would have done this if I waited 2 weeks earlier. If more people get it and can confirm, just maybe I will unroot and go back to stock. But I love all the customizations with Resurrection Remix.
Click to expand...
Click to collapse
Had to do a quick search on what Resurrection Remix was, very nice rom it seems!
Doukeyakusha said:
So I am surprised. I noticed, when I flashed straight to .64 firmware and checked for Software updates, I Did Not get the Nougat OTA notification. Only with the .49 firmware. I didn't think to take a screen shot, and am currently downloading the Nougat update now. When it is installed, I'll take a screenshot of the firmware version once booted into my phone. It's about time, I'm going to be ordering the G5 for my wife tomorrow, and was a tad bit jealous that it would already come with Android 7.0 lol. Hope this gets the rest of you American users excited, and hope this information helps. You can find a guide how to downgrade here in the forums or google, or at stechguide website. PS- I cannot guarantee nor take responsibility that you will have the same luck to get the OTA as I did. Downgrade at your own discretion.
Click to expand...
Click to collapse
I too didn't get an OTA update notice when I went back to .64 stock/unrooted . So I said the heck with it and went back to Invicta and will stay there. I ran stock nougat flashed via the TWRP flashable files that were available for a while. But when the rubber meets the road, I see no advantages to going through the hassles of downgrading my phone to stock anything given that the features, performance, stability and battery life are far better on various custom ROMS. Not to mention that the security is more up to date. Just my own opinion.
hmmmm..interesting...tempted to try this out
My phone is too new to be rooted (sorry, I no longer do that first day...) After seeing the earlier posts I checked last night, no luck.
Today is another day! New version installing now. NPJ25.93-14 just said, "Hello, Moto". Woohoo!
Peace,
Tom
OTA zip
Does anyone have the OTA files? I suspect I will have to manually flash the files in Fastboot due to earlier impatience (I did nougat soak test and then downgraded back to stock). Now the regular ota keeps giving me error which I am assuming is tied to the gpt.bin error I got when I downgraded. I can't do anything scripted. Gotta install manually from fastboot.
Just for your info... The Amazon ad remover doesn't work after the update. XT1625
Downloading in Austin Texas
Sent from my Moto G (4) using XDA-Developers Legacy app
Has anyone made an image as I need it to unbrick my phone?
Amston said:
Has anyone made an image as I need it to unbrick my phone?
Click to expand...
Click to collapse
My wife's just got the update. Mine is unlocked and rooted. If someone can tell me the steps to get back to a position to download the ota, and root again, and pull the image, I'll happily do it. I'm on .48 right now. Looks like I need to relock the bootloader and reload .48 fresh, but I'm not real sure at this point.
downloaded and installed. startup animation was fun. anyone know how to root this build?
fredwinky said:
downloaded and installed. startup animation was fun. anyone know how to root this build?
Click to expand...
Click to collapse
I dunno. Try searching the G4+ forum? There is a post that tells you how.
I got the update before the weekend and installed it. Everything went smooth and the changes are very nice. I've noticed the Bluetooth issues I had seem fixed (dropping connections, having to de-pair, power cycle and re-pair). However, one annoying thing still persists and it seems related to Do Not Disturb. Sometimes the audio never comes back after DND. Notifications, touches, calls, they're all silent after DND is turned off. I have to power cycle the phone and then it works. I had this issue on Marshmallow and Motorola advised me to wipe & reset. That took care of the issue but it seems to have come back for now. No other issues that I can find right now.
The only thing I've noticed is with my wifi . Every now and then it doesn't auto connect when returning home. This was reported by a number of people during the soak test but I guess it wasn't important enough because the OTA was released anyway. Also, I previously had the option of connecting with 2.4GHz, 5GHz, or auto. Now there is no option and I've noticed that sometimes I'm connected with 2.4 and sometimes with 5 but it seems to be random.
Sent from my SM-T530NU using Tapatalk
fredwinky said:
downloaded and installed. startup animation was fun. anyone know how to root this build?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=3484672
Has the instructions to root.
Sent from my Moto G (4) using Tapatalk
I'm new to this phone Can anyone give me a link to the ".49 firmware"
I ordered this phone as an early xmas gift for my mother during black friday, got it for $115 32gb unlocked from B&H Photo. Just wanted to mention as a current Nexus 6 owner I'm surprised how this phone is basically pure android with the exception of 2 Moto apps. I was able to upgrade from 6.0 to Nougat out of the box and then the security patches without any issues. Once all updates were done I just erase the device to factory and setup as expected. Jealous it's running faster than my Nexus 6 (and I'm running performance mode using ex kernel manager). Only wish Motorola can reboot the nexus 6 with a bigger screen and fingerprint.
Hey gang, Im tired of waiting for the OTA for T-Mobile. My bro and sis (Comcast & Sprint) already have it.
Qs:
1) Should I clear cache in download mode before starting? Factory reset phone? (Askin because I saw a few people had minor issues)
2)I downloaded CRC2 from Updato, I noticed it errored after unrar (2 diff PCs). Did anyone else get an error?
Im downloading CRC2 from Sammobile as I type to see if theirs error. WinRAR ver 3.90, files appear to be intact from Updato.
3) I backed up my 7.1.1 via SmartSwitch , will delete S.Switch and restart PC before attempt. But in the case something goes wrong or I don't like 8.0. Can I use the 7.1.1. backup & reinstall it with Switch or do I have to reflash BRA9 via Odin, then restore my back up? (which I honestly wouldn't care about as getting to 7.1.1. would be the goal)
Sorry if these are newbish Qs, rather ask in advance before trying on my daily.
I got my update from tmobile. Did u check by pushing update button. Mine was on April 2nd
nick607ny said:
I got my update from tmobile. Did u check by pushing update button. Mine was on April 2nd
Click to expand...
Click to collapse
Yes, Ive tried daily since April 1st. Me & the wife Note 8 hasnt seen it. Im in north west Indiana if its geographically released.
I'm in central ny so not to far off but different time zones I think.
Hopefully a few others near me chime in, if they have it or not. Was CRC2 for your update?
I'm in portland oregon. No update yet.
I'm in Louisiana and no update for me either.
Strange. I got my OTA a couple weeks ago OTA from tmobile. Might want to connect to a computer via Smart Switch. That should give you the update.
rile1564 said:
Strange. I got my OTA a couple weeks ago OTA from tmobile. Might want to connect to a computer via Smart Switch. That should give you the update.
Click to expand...
Click to collapse
Yep, me or the Mrs still haven't gotten the OTA. I have a backup and will try a factory reset with no Samsung theme to see if that'll cure it today
rile1564 said:
Strange. I got my OTA a couple weeks ago OTA from tmobile. Might want to connect to a computer via Smart Switch. That should give you the update.
Click to expand...
Click to collapse
I'm going to try this. I haven't used Odin in over two years. This seems easier if it works.
RaymondPJR said:
I'm going to try this. I haven't used Odin in over two years. This seems easier if it works.
Click to expand...
Click to collapse
No OTA, no joy with SmartSwitch either. I'm in the Seattle area, about 10 miles from T-Mobile HQ. Neither T-mobile support nor Samsung support on Twitter can figure out why the phone hasn't received the update. Thinking about ODIN.
jimscard said:
No OTA, no joy with SmartSwitch either. I'm in the Seattle area, about 10 miles from T-Mobile HQ. Neither T-mobile support nor Samsung support on Twitter can figure out why the phone hasn't received the update. Thinking about ODIN.
Click to expand...
Click to collapse
I went ahead and did it through ODIN, took literally 4 min or so to actually do it., I did back up me & mrs 7.1.1. through SmartSwitch before trying and also fully uninstalled it to prevent it from fighting with ODIN. Just a recap: I was on BRA9, T-Mobile. Had a few concerns with the Oreo not unzipping correctly from Updato. All is well on my end.
Just be aware that there are problems with the current Oreo version for the Note 8. That is the reason why T-Mobile stopped sending out that version of Oreo Android to Note 8 devices right now. The last I heard of is that Samsung went to Google for help on the problems. So both Google and Samsung engineers are working on this.
You might want to wait until they send a version of Oreo Android for Note 8 that has the problems fixed.
JaguarXT said:
Just be aware that there are problems with the current Oreo version for the Note 8. That is the reason why T-Mobile stopped sending out that version of Oreo Android to Note 8 devices right now. The last I heard of is that Samsung went to Google for help on the problems. So both Google and Samsung engineers are working on this.
You might want to wait until they send a version of Oreo Android for Note 8 that has the problems fixed.
Click to expand...
Click to collapse
What was the problem? I got the OTA on the first day and it's running flawlessly on my Note 8.
What I understand is that if you don't have problems now then you are likely to have problems later. Variety of problems. From not being able fully update current or future Android updates, not able now or possibly later install and update random apps from Galaxy Apps store, apps randomly freezing, and lots more.
What I understand is that Google has knowledged to Samsung that these problems are caused by them. So Google is working with Samsung to fix these issues.
After I got the OTA update I didn't have problems. But since I had so many apps installed I did a factory data reset and cleared cache. After that I had random apps freezing and even had app icons randomly disappear and reappear (mainly Google and Samsung apps). Note - Never rooted this device and only used OTA updates to update Android itself on this device.
Samsung wanted me to send my Note 8 into their techs for them to flash Nugget Android into the device for right now (while they work to fix issues with Oreo). I said I needed the device. So T-Mobile did a Warranty exchange giving me a Note 8 that has Nugget Android. Both Samsung and T-Mobile told me the same thing.
Samsung is very tight lid with this. Which is the reason that many are confused. Yet I understand why Samsung is being more cautious (especially after the Note 7 issues).
jimscard said:
No OTA, no joy with SmartSwitch either. I'm in the Seattle area, about 10 miles from T-Mobile HQ. Neither T-mobile support nor Samsung support on Twitter can figure out why the phone hasn't received the update. Thinking about ODIN.
Click to expand...
Click to collapse
2muchspl said:
I went ahead and did it through ODIN, took literally 4 min or so to actually do it., I did back up me & mrs 7.1.1. through SmartSwitch before trying and also fully uninstalled it to prevent it from fighting with ODIN. Just a recap: I was on BRA9, T-Mobile. Had a few concerns with the Oreo not unzipping correctly from Updato. All is well on my end.
Click to expand...
Click to collapse
Same result for me with SmartSwitch, nothing! Finally did it with Odin, enjoying it too. Right now I have no problems whatsoever.
Tmobile has paused the update, seems to be some rumblings about the rom causing issues. I was in the same boat and chose to go the odin route. For those of you who haven't done so yet and want to, check out BlueFox721's guide. Post #3 has the instructions for flashing, and in post one under "Flashing Carrier Firmware" you will find the link to the hosted rom. Extract this in a new folder in your odin directory and follow the steps. Ensure you factory data reset and wipe the cache before installing a new rom for best results!
So far I've loved the update and haven't had any issues. Keep in mind if you theme with substratum it's fairly annoying and requires adromeda and a pc to keep your themes running. Secondly, usb debugging pisses off safetynet now and will cause issues and disabling debugging kills your ability to mod your themes until you reconnect to a pc and run the andromeda client.
Hey guys, so like you all I was pressing the "check for updates" in settings everyday with no luck. I then looked it up one day and saw this....
https://www.phonearena.com/news/Tmobile-Samsung-Galaxy-Note-8-Android-Oreo-update-paused_id104334
https://www.tmonews.com/2018/04/t-mobile-paused-galaxy-note-8-android-8-0-oreo-update/
Tmobile stopped the oreo update for the time being. Unfortunately.
Well the only way i can see any of us updating to official Oreo is someone willing to download the OTA firmware zip from those crappy scam sites that want to control your download speed and upload it to here or Google Drive. i mean i would do it if i had the patience for it honesty xp
Will flashing via ODIN do a factory reset? I thought it didn't, but reading the notes on the guide thread appears to indicate that it might?
The May 2018 updates are on Google's site, except for the 6P. Anyone know why?
This article says it's been pulled:
https://www.droid-life.com/2018/05/...ity-update-goes-live-for-nexus-pixel-devices/
The links are still active. I got them from here:
https://9to5google.com/2018/05/07/android-may-18-security-patch-pixel-nexus/
I downloaded the image yesterday but going to delete it.
The update was actually pushed to my device today by Google... but it won't install due to an E3005 error related to the modem. I'm not sure, though, if the issue is with this update or if it's something specific to my device.
SpookyTunes said:
The May 2018 updates are on Google's site, except for the 6P. Anyone know why?
This article says it's been pulled:
https://www.droid-life.com/2018/05/...ity-update-goes-live-for-nexus-pixel-devices/
The links are still active. I got them from here:
https://9to5google.com/2018/05/07/android-may-18-security-patch-pixel-nexus/
Click to expand...
Click to collapse
Thanks for the heads up. Have you flashed it?
new update was sucessfully installed on my nexus via official ota update
tropical cactus said:
Thanks for the heads up. Have you flashed it?
Click to expand...
Click to collapse
Not yet without knowing what the issue with it is. I may get brave on the weekend though
SpookyTunes said:
Not yet without knowing what the issue with it is. I may get brave on the weekend though
Click to expand...
Click to collapse
OPM2. Sounds a bit scary to me. I thought angler was only either 3 or 5. I haven't flashed it either.:laugh:
It appears to have a new radio 3.87 , maybe there are some problems with that
tropical cactus said:
OPM2. Sounds a bit scary to me. I thought angler was only either 3 or 5. I haven't flashed it either.:laugh:
Click to expand...
Click to collapse
What do these even mean?
If I have OPM3 can I flash OPM5? Vice versa?
Ofrine said:
What do these even mean?
If I have OPM3 can I flash OPM5? Vice versa?
Click to expand...
Click to collapse
Normally you should always use the same build if available. I'm on OPM3. OPM5 is a build specifically for Japanese carrier SoftBank. Attempting to flash OPM5 over OPM3 is a bad idea.
I believe OPM2 is a merge of OPM3 and OPM5. Perhaps if you had OPM5 it isn't liking the merged radio file but for me on OPM3 I was able to upgrade to the May OPM2 Nexus 6P build without issue.
I did a non-destructive factory image flash to get to OPM2. YMMV.
rhardy613 said:
Normally you should always use the same build if available. I'm on OPM3. OPM5 is a build specifically for Japanese carrier SoftBank. Attempting to flash OPM5 over OPM3 is a bad idea.
I believe OPM2 is a merge of OPM3 and OPM5. Perhaps if you had OPM5 it isn't liking the merged radio file but for me on OPM3 I was able to upgrade to the May OPM2 Nexus 6P build without issue.
I did a non-destructive factory image flash to get to OPM2. YMMV.
Click to expand...
Click to collapse
So you installed the may update?,how is it so far.
side-loaded the may ota file via adb and it seems to work a-ok so far... i had installed opm5 before as well via this method so perhaps there is some under the hood issue nobody has noticed yet...
Not Yet Available
If you go to the Android News blogspot it states that the Nexus 6P update is "Not Yet Available" ...
I'd post the link, but it says new members are not allowed for 10 days or something like that, sorry!
Installed may update using flashfire.seems fine to me so far.seems little faster,but could be cause of clean install,rooted and debloated also.when Google releases new update I will probably install that too.just curious why it was pulled,a bug,or was there something we got that we weren't supposed too??
I cant say for sure what the issue was but I know after I did the update phone worked fine but then I restarted the phone and it told me my Android System was corrupted and that I had to factory reset.
VersusMe_ said:
I cant say for sure what the issue was but I know after I did the update phone worked fine but then I restarted the phone and it told me my Android System was corrupted and that I had to factory reset.
Click to expand...
Click to collapse
So far still running good for me,no message when I reboot either.
I just realized that the power save mode is not functioning on my 6P and was before may OTA ( cannot be toggled and does not turn on below 15%) not a game-changer but could be why it was pulled or it could just be a hiccup on an aging device
Ugh, where the update?
I was holding of flashing till the release of the next security patch.
[email protected] said:
Ugh, where the update?
I was holding of flashing till the release of the next security patch.
Click to expand...
Click to collapse
My phone says it has the OTA, but as I did some system modifications, I need the factory image, which yet has to appear.
Have any of you installed from the first link? If so, how did that go? I wan to do the OTA, but I am a bit worried it will be corrupt or that it isn't the correct file.
So my phone is still stuck on Android 9 with the November Security Update. I had the Android 10 update/upgrade pending install on my phone but I held off upgrading due to the many reported issues people reported with it. One day my phone randomly rebooted but stayed on Android 9. Since then, every time I check for an update, it says it's currently up-to-date. Has this happened to anyone else? Do I need to manually download the Android 10 update and flash it from recovery? Where can I even download the update/upgrade from?
I actually ended up buying a new phone because of this issue (my job requires me to have company email on my phone and it has to have at least the latest quarterly security update). None too pleased.
I have the exact same issue. Been digging for a while trying to find the solution.
ctechbob said:
I have the exact same issue. Been digging for a while trying to find the solution.
Click to expand...
Click to collapse
Manually download and flash the updates yourself. That's what I had to do.
Looks like they pushed an update tonight (6/15/20) Showing A10 update with 5/2020 security patch.
According to the people on reddit it is because I have debloated my phone. I also tried to install the Pixel Experience Plus custom rom at one point but it didn't work, I did reinstall the stock recovery an relocked the bootloader after that.
I did factory reset it and even flashed it with an ozip file still no update.
also found an ofp file for the Android 11 update but relme flash tool wouldn't work with it.
Is there any other way to manually update it or force it to update?
Thanks in advance.
Do you really want it?
I think it's a bloatware dud.
The "security" is not needed and comes at a stiff price as you will see if you load it.
Scoped storage sucks.
Rule #1, if your OS is running fast, stable and fulfilling its mission... let it be.
You do make a good point.
But if it is possible and I don't like it I can always reverse to Android 10.
At this point I just want to try it out and try the Pixel Experience rom.
If it isn't, well both my phone and I will survive.
thephone.geek said:
You do make a good point.
But if it is possible and I don't like it I can always reverse to Android 10.
At this point I just want to try it out and try the Pixel Experience rom.
If it isn't, well both my phone and I will survive.
Click to expand...
Click to collapse
You can go back... as long as it doesn't update the boot loader version too.
As a Samsung user I'm all too aware of that trick.
I would investigate what advantages R has over Q that would benefit you. Scoped storage isn't fully implemented on Q apparently and seems to run as well maybe better than Pie. In Q it's scoped storage in all it's blazing cpu cycle sucking glory.
Is there anyway to do it using adb?
I got Realme 7 Pro from Amazon Warehouse with somehow broken security - figerprint scanner didn't work and the phone didn't want update itself thru OTA, even with relocked bootloader and when connected via VPN to Germany, Italy etc. It actually updated to Android 11 C23 using OTA when I changed phone's region to Singapore using the service code. Then I was still able to go back to Android 10 using OZIP file (like described in this guide), or it was also possible to flash individual img files from fastboot using adb as described here. But OTA updates and fingerprint scanner were still broken until I sent the phone to Realme service and they reflashed it completely within warranty - after that fingerprint sensor works properly and I got OTA update to Android 11 C26 right after connecting to Germany over VPN.