I recently bought a verizon Pixel and have already unlocked the bootloader and flashed a stock image NDE63V that comes directly from google. I'm using it on T-Mobile. If I relock the bootloader at this point will everything be ok? I've read something about people saying it would brick the phone if you relock after flashing unsigned code, but the official stock images from google are signed. Will I get official updates for the unlocked google store version of the Pixel?
-edit- I decided to live dangerously, re-locked the bootloader, and now I have a completely stock google store pixel
My understanding is it will revert back to Verizon boot loader with updates. Am I wrong in that assumption. I am in the same boat and would like convert to google stock and use on T-Mobile with OTA updates
Sent from my Nexus 6 using XDA-Developers mobile app
brainymd said:
My understanding is it will revert back to Verizon boot loader with updates. Am I wrong in that assumption. I am in the same boat and would like convert to google stock and use on T-Mobile with OTA updates
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't think anyone knows. Right now I flashed stock google ROM through fastboot which replaced bootloader image, I am using it with T-Mobile, and I relocked bootloader. I'm going to assume it would get stock google updates.
I just got my Verizon pixel a couple days ago. I immediately uninstalled the Verizon sim card and did not enabled wifi until after I unlocked the bootloader and installed the Google's NDE63V. I then disabled Automatic System Updates within Developer Options and sometime after I installed TWRP, root, and a custom kernel I noticed a system update was available.
It turned out to be NDE63X. From what I understand that is a Verizon only image. This makes me believe what others have been saying, Verizon IMEIs are being pushed Verizon updates.
I followed the guide here to disable any future update notifications since I will be sideloading OTAs manually.
If you relock the bootloader you may not be able to unlock it again as I am guessing a future Verizon update will block dePixel8.
mruno said:
I just got my Verizon pixel a couple days ago. I immediately uninstalled the Verizon sim card and did not enabled wifi until after I unlocked the bootloader and installed the Google's NDE63V. I then disabled Automatic System Updates within Developer Options and sometime after I installed TWRP, root, and a custom kernel I noticed a system update was available.
It turned out to be NDE63X. From what I understand that is a Verizon only image. This makes me believe what others have been saying, Verizon IMEIs are being pushed Verizon updates.
I followed the guide here to disable any future update notifications since I will be sideloading OTAs manually.
If you relock the bootloader you may not be able to unlock it again as I am guessing a future Verizon update will block dePixel8.
Click to expand...
Click to collapse
I also have a Verizon version. Is there an advantage to flashing the Google version of updates as opposed to Verizon? For the moment I have an unlocked bootloader with TWRP and SuperSU installed. I tried installing an OTA update and it failed.
If I want to install one of the image updates posted (such as NDE63X from Verizon available right now) do I need to run the "flash-all" script? Could I just flash system or something else? Or should I expect it to overwrite my custom recovery and I'll have to restore that?
As of right now, I do not know of any advantages of the Google image vs Verizon's other than lack of bloatware.
I have not performed an update myself, but I think this guide should help you.
mruno said:
As of right now, I do not know of any advantages of the Google image vs Verizon's other than lack of bloatware.
I have not performed an update myself, but I think this guide should help you.
Click to expand...
Click to collapse
Thanks for the help, I followed the guide and installed the updates. Unfortunately I did not get any new gestures available (Lift to Wake or Double Tap) as I had hoped... either those are not in the Nov 2016 Verizon system.img, or they are an app update I haven't received yet.
mruno said:
I just got my Verizon pixel a couple days ago. I immediately uninstalled the Verizon sim card and did not enabled wifi until after I unlocked the bootloader and installed the Google's NDE63V. I then disabled Automatic System Updates within Developer Options and sometime after I installed TWRP, root, and a custom kernel I noticed a system update was available.
It turned out to be NDE63X. From what I understand that is a Verizon only image. This makes me believe what others have been saying, Verizon IMEIs are being pushed Verizon updates.
I followed the guide here to disable any future update notifications since I will be sideloading OTAs manually.
If you relock the bootloader you may not be able to unlock it again as I am guessing a future Verizon update will block dePixel8.
Click to expand...
Click to collapse
Yes, they may block it in the future, but can't you always flash the November image (since it's signed), and dePixel8 again ? Do updates have the ability to change the trusted key or prevent flashing an older image ? I'm guessing yes, since that's what Lenovo does for its BIOS, but I haven't looked at Android that closely.
ohioDroid said:
Thanks for the help, I followed the guide and installed the updates. Unfortunately I did not get any new gestures available (Lift to Wake or Double Tap) as I had hoped... either those are not in the Nov 2016 Verizon system.img, or they are an app update I haven't received yet.
Click to expand...
Click to collapse
If the gestures were not in that update, they should be soon in an upcoming OTA according to reports. I am currently using the double-tap gesture with the ElementalX kernel (enabled within its app).
Edit: I think this app can enable lift to wake. I bookmarked it after finding a post about it here until I read Google will be adding this feature soon.
fink.nottle said:
Yes, they may block it in the future, but can't you always flash the November image (since it's signed), and dePixel8 again ? Do updates have the ability to change the trusted key or prevent flashing an older image ? I'm guessing yes, since that's what Lenovo does for its BIOS, but I haven't looked at Android that closely.
Click to expand...
Click to collapse
I am not sure as I haven't had a nexus device since the Samsung Galaxy Nexus on Verizon .
On a lot of their devices Verizon likes to update bootloaders to only accept new updates. It's likely that if they patch out the ability to use dePixel8 in a future update, they will prevent people from flashing older builds. C'Est la Vie I guess
Just got my pixel yesterday but still using my s5 for now. I've gone from a droid x - GS 3 - GS4 - GS5. Development for each of those phones seemed really good. I was always jealous of other devices who's bootloaders were unlockable right away because of the crazy amount of development for them (Nexus). Most of the reason I got the Pixel was because I thought it would be just like the Nexus devices as far as development goes but so far it doesn't seem like it's going that way. I know it's somewhat new but just curious if people think it's going to pick up?
Just got my Pixel 2 days ago through Verizon, had it shipped to me instead of getting it at the store.
I did an initial charge and then set up the phone, during setup, it allowed me to choose which Google and Verizon apps were being installed.
I don't get any Verizon screens, just the Google boot animation. There isn't even a Verizon logo on the phone. I don't even see anything Verizon unlit after the SIM is detected.
I was wondering if anyone else that got their Pixel through Verizon has carrier markings or bloat on it? And if it does, did you go 32gb or 128gb and did you get yours via mail or from the store?
aholeinthewor1d said:
Just got my pixel yesterday but still using my s5 for now. I've gone from a droid x - GS 3 - GS4 - GS5. Development for each of those phones seemed really good. I was always jealous of other devices who's bootloaders were unlockable right away because of the crazy amount of development for them (Nexus). Most of the reason I got the Pixel was because I thought it would be just like the Nexus devices as far as development goes but so far it doesn't seem like it's going that way. I know it's somewhat new but just curious if people think it's going to pick up?
Click to expand...
Click to collapse
Yes, it will most definitely pick up. The Partitions are different than any other phone, and as soon as we have a stable TWRP then the custom ROM's will pour in. Just give it some time, and be happy with stock for now. Good times are coming, and I'm looking forward to using this phone for the next two years.
---------- Post added at 08:28 AM ---------- Previous post was at 08:25 AM ----------
tobalaz said:
Just got my Pixel 2 days ago through Verizon, had it shipped to me instead of getting it at the store.
I did an initial charge and then set up the phone, during setup, it allowed me to choose which Google and Verizon apps were being installed.
I don't get any Verizon screens, just the Google boot animation. There isn't even a Verizon logo on the phone. I don't even see anything Verizon unlit after the SIM is detected.
I was wondering if anyone else that got their Pixel through Verizon has carrier markings or bloat on it? And if it does, did you go 32gb or 128gb and did you get yours via mail or from the store?
Click to expand...
Click to collapse
The only Verizon bloat that comes is three apps that can be uninstalled. other than that, there is no Verizon logo anywhere.
jmartin72 said:
Yes, it will most definitely pick up. The Partitions are different than any other phone, and as soon as we have a stable TWRP then the custom ROM's will pour in. Just give it some time, and be happy with stock for now. Good times are coming, and I'm looking forward to using this phone for the next two years.
---------- Post added at 08:28 AM ---------- Previous post was at 08:25 AM ----------
The only Verizon bloat that comes is three apps that can be uninstalled. other than that, there is no Verizon logo anywhere.
Click to expand...
Click to collapse
Thanks for the reply! I've unlocked bootloader already but haven't rooted or anything yet. Been busy so I need some time to read through the Pixel forums more. I do remember seeing mention of something with the partitions on the Pixel causing issues with TWRP. Do you have a link by any chance or something that explains what is going on with it and how the partitions are different? Just want to read up on it. Been with my s5 for soooo long so coming to a new device basically means starting over and learning lots of new stuff. Software versions, unlocking, rooting, etc
aholeinthewor1d said:
Thanks for the reply! I've unlocked bootloader already but haven't rooted or anything yet. Been busy so I need some time to read through the Pixel forums more. I do remember seeing mention of something with the partitions on the Pixel causing issues with TWRP. Do you have a link by any chance or something that explains what is going on with it and how the partitions are different? Just want to read up on it. Been with my s5 for soooo long so coming to a new device basically means starting over and learning lots of new stuff. Software versions, unlocking, rooting, etc
Click to expand...
Click to collapse
I bought my Verizon Pixel yesterday. Unlocked in 20 seconds and within a few minutes TWRP 3.0.2-0 for sailfish is installed and SuperSU 2.78-SR5 has been flashed. Works perfect.
aholeinthewor1d said:
Thanks for the reply! I've unlocked bootloader already but haven't rooted or anything yet. Been busy so I need some time to read through the Pixel forums more. I do remember seeing mention of something with the partitions on the Pixel causing issues with TWRP. Do you have a link by any chance or something that explains what is going on with it and how the partitions are different? Just want to read up on it. Been with my s5 for soooo long so coming to a new device basically means starting over and learning lots of new stuff. Software versions, unlocking, rooting, etc
Click to expand...
Click to collapse
I feel your pain! I'm also coming from the S5 for 2.5 years. Had everything (almost) perfect with systemless root, twrp, xposed, adaway, etc. (but no Android Pay) . Now with this Pixel and Verizon-depixel8 unlocked bootloader, I'm trying to piece together the best plan for having the most stuff working.
So far, bootloader unlocked, and I flashed the full 7.1.1 images from Google. Then I tried using the setup wizard and it brought over my account info and wifi passwords and such from my S5 by directly connecting the phones, and it downloaded my apps from google play, but I need app-data.
So, now I'm thinking this would be the process if you want to have a rooted pixel, and be able to reboot into a "clean" boot for Android Pay?:
1) boot TWRP alpha2 (since RC1 having problem rooting?)
2) install TWRP alpha2 zip
3) install stock-safetynet kernal to boot_a
4) boot into boot_a
5) setup Android pay, add credit cards, etc.
6) boot into TWRP and install root with SR5 to boot_b
7) boot into boot_b and restore other app backups with Titanium Backup, install Adaway/hosts
8) no Xprivacy /Xposed available yet, right?
9) restore backed up apps from old phone with Titanium Backup (from cloud, etc.)
I have one question with this, I have a Verizon pixel with unlocked bootloader. I just wanted to make sure I can flash the Google image and still use on Verizon. Will I lose any features like the advanced calling stuff?
Sent from my Pixel using XDA-Developers mobile app
bobhinkle said:
I have one question with this, I have a Verizon pixel with unlocked bootloader. I just wanted to make sure I can flash the Google image and still use on Verizon. Will I lose any features like the advanced calling stuff?
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes you can still use it on Verizon. Advanced Calling is a feature i am not too familiar with. Is that HD Calling? If so then yes that will work as well works on my phone without issue.
So from here I can flash Google's bootloader and Google image and then when updates come out just use the Google ones
Sent from my Pixel using XDA-Developers mobile app
Question for those with a Play store version of the Pixel: what is your bootloader version on the 7.1.1 software?
For reference my Verizon store Pixel has BL version 8996-12001-1610061102.
Thanks in advance!
I'm considering buying a used Google Pixel that was purchased via Verizon. Through researching, it sounds like I should be able to just pop in my AT&T SIM and it should work. Is this correct?
What I don't want is a phone that has Verizon bloatware installed and delayed updates. Will I be able to install non-Verizon factory images? I see There multiple 7.1.2 factory images listed at https://developers.google.com/android/images for the Pixel. (N2G47O, May 2017) and (NHG47L, May 2017, Verizon). Will I be able to install the N2G47O version or would I be stuck installing the Verizon branded version.
Thanks for any help.
Also with the same question
Enviado desde mi Redmi Note 3 mediante Tapatalk
beand1p said:
I'm considering buying a used Google Pixel that was purchased via Verizon. Through researching, it sounds like I should be able to just pop in my AT&T SIM and it should work. Is this correct?
What I don't want is a phone that has Verizon bloatware installed and delayed updates. Will I be able to install non-Verizon factory images? I see There multiple 7.1.2 factory images listed at https://developers.google.com/android/images for the Pixel. (N2G47O, May 2017) and (NHG47L, May 2017, Verizon). Will I be able to install the N2G47O version or would I be stuck installing the Verizon branded version.
Thanks for any help.
Click to expand...
Click to collapse
I just recently picked up a google pixel , I traded a galaxy s7 edge for it. The google pixel was originally verizon, I just popped in my tmobile sim card and it was good to go. The only set back is if you want to unlock the bootloader, from reading various forums its possible IF the phone is on 7.1. Apparently if you upgrade with a non verizon sim or over wifi itll allow you the option to unlock the bootloader. You can uninstall all verizon apps, as for the image you are probably stuck on the verizon one for the time being till an unlock for a bootloader comes out. People have reported contacting google and being able to rma their verizon phone for a non verizon one to unlock the bootloader.
Posting my experience for future reference and to help others trying to go this path.
I started with an Essential Phone that was not originally on Sprint, Custom ROM (AOSiP 8.1), bootloader unlocked, and had a Cricket Wireless SIM. I wanted to take advantage of the Sprint BYOD free unlimited for a year deal. Went through the pain of getting the Sprint SIM and transferring service. All was well except my phone number was not registering and was unable to make phone calls. Sprint LTE data was fine. SIM status showed Phone Number as "unknown." I needed to update the PRL. The *#*#72786#*#* didn't work to update the PRL and there was no menu item in settings within AOSiP 8.1 (also tried using Lineage 15.1). Here's the steps I took to get it working on Sprint.
1. Backed up files
2. ADB to fastboot
3. Flashed twrp-mata_11.img
4. Selected Boot Recovery in fastboot menu to boot to twrp
5. Clean wipe
6. Downloaded and transferred stock Oreo 8.1 beta from Essential website
7. Flashed PH1-OTA-OPM1.180104.010.zip using twrp
8. Rebooted phone and went through initial setup.
9. PRL options under Settings>System>About phone>OMADM updates
10. All is well on Sprint
I use Linux Mint and used the following commands:
sudo adb devices
sudo adb reboot-bootloader
sudo fastboot devices -i 0x2e17
sudo fastboot flash boot twrp-mata_11.img -i 0x2e17
Update: I was disappointed with Sprint service on PH1-OTA-OPM1.180104.010.zip. I decided to try the latest build of 8.1 (June 2018 Release | Oreo 8.1 - OPM1.180104.234). I've been using it as my daily. This build is a significant improvement from the last one I've tried to use. Better reception, smoother UI, no hiccups so far. I was just about ready to give up on this phone.
jcastle003 said:
Posting my experience for future reference and to help others trying to go this path.
I started with an Essential Phone that was not originally on Sprint, Custom ROM (AOSiP 8.1), bootloader unlocked, and had a Cricket Wireless SIM. I wanted to take advantage of the Sprint BYOD free unlimited for a year deal. Went through the pain of getting the Sprint SIM and transferring service. All was well except my phone number was not registering and was unable to make phone calls. Sprint LTE data was fine. SIM status showed Phone Number as "unknown." I needed to update the PRL. The *#*#72786#*#* didn't work to update the PRL and there was no menu item in settings within AOSiP 8.1 (also tried using Lineage 15.1). Here's the steps I took to get it working on Sprint.
1. Backed up files and ensure ADB Debug is enabled in Development Tools.
2. ADB to fastboot
3. Flashed twrp-mata_11.img
4. Selected Boot Recovery in fastboot menu to boot to twrp
5. Clean wipe
6. Downloaded and transferred stock Oreo 8.1 beta from Essential website
7. Flashed PH1-OTA-OPM1.180104.010.zip using twrp
8. Rebooted phone and went through initial setup.
9. PRL options under Settings>System>About phone>OMADM updates
10. All is well on Sprint
I use Linux Mint and used the following commands:
sudo adb devices
sudo adb reboot-bootloader
sudo fastboot devices -i 0x2e17
sudo fastboot flash boot twrp-mata_11.img -i 0x2e17
Click to expand...
Click to collapse
jcastle003 said:
Update: I was disappointed with Sprint service on PH1-OTA-OPM1.180104.010.zip. I decided to try the latest build of 8.1 (June 2018 Release | Oreo 8.1 - OPM1.180104.234). I've been using it as my daily. This build is a significant improvement from the last one I've tried to use. Better reception, smoother UI, no hiccups so far. I was just about ready to give up on this phone.
Click to expand...
Click to collapse
Why give up? Didn't like it? Bad service? I want either this or a pixel xl, 128gb is the same price point but I believe the essential is a better overall device for what I want, just doing some research!
andrew2432 said:
Why give up? Didn't like it? Bad service? I want either this or a pixel xl, 128gb is the same price point but I believe the essential is a better overall device for what I want, just doing some research!
Click to expand...
Click to collapse
I haven't given up. It's actually been my daily since I put the latest update. It has been good so far. Minor issues with reception compared to a GSM SIM. Not complaining since the service is free. My latest opinion... Much better experience with the phone on Sprint with the latest ROM update.
jcastle003 said:
I haven't given up. It's actually been my daily since I put the latest update. It has been good so far. Minor issues with reception compared to a GSM SIM. Not complaining since the service is free. My latest opinion... Much better experience with the phone on Sprint with the latest ROM update.
Click to expand...
Click to collapse
I just meant why about to give up, sorry. Awesome thanks! I want this over a pixel if I can, I live in a bad service area. I've seen the pixel on sprint get better than my current phone and more stable so I'm interested in sprint on this!!
It seems they are sending android 11 to everyone but they changed the boot animation. Now when you boot you see a logo that says edge and then TIM italy. This did not happen in android 10. My moto g 5g is free retail with no brand on the box. I think there is a bug in this update. Is it possible to return to android 10? Also this update changed the intensity of the bars on the screen, now it is more generous but if you see the numeric values of Dbm or ASU these are much lower. I regretted updating so fast and I would like to go back to android 10 until 11 is fixed.
Lol, 11 will never be "fixed".
If the bootloader was updated you're boned.
Apparently on the OTA updates on at least some devices it's not being updated, you can rollback.
The 5th digit from the end of the boot loader version and the firmware are the significant digits. If the boot loader version is the same or less than the firmware, you can rollback. In this case it's a 2.
Not sure that this Samsung rule applies to Motorola updates.
RETIEF said:
Not sure that this Samsung rule applies to Motorola updates.
Click to expand...
Click to collapse
No idea, it may be a Samsung idiosyncrasy.
A very annoying one...
PredatorGreen said:
It seems they are sending android 11 to everyone but they changed the boot animation. Now when you boot you see a logo that says edge and then TIM italy. This did not happen in android 10. My moto g 5g is free retail with no brand on the box. I think there is a bug in this update. Is it possible to return to android 10? Also this update changed the intensity of the bars on the screen, now it is more generous but if you see the numeric values of Dbm or ASU these are much lower. I regretted updating so fast and I would like to go back to android 10 until 11 is fixed.
Click to expand...
Click to collapse
Check the software channel from Settings>Telephone information (or similar), which software channel do you have? If it is timit you are on the tim software channel (and the updates depends on the carrier, but actually seems in line with reteu, the european standar), if you are on reteu this is really strange. I don't know why they miss the boot animation but the firmware is right.
Yes the software channel is timit, but in android 10 it showed the boot animation for reteu channel. And i dont know why now it shows an edge logo animation that has nothing to do with this model. It looks like they put something from another model in the update. Look at the attached photo.
I'm using the euro android 11 XT2113-3_KIEV_RETEU_11_RZK31.Q3-25-15 on a XT2113-2 and everything seems happy as a clam, *except* it would not flash the radio.img. As far as being "boned" if you went to 11 but wished to downgrade.... Has anyone bothered to try a patched vbmeta? I could go up or down on my one action using this route. I think I may just try for the hell of it.
EDIT: downloading 10 now. If it works I'll post my patched vbmeta.
EDIT: Now keep in mind I am doing this from a flash of android 11 xt2113-3 on a xt2113-2 handset... The flash fails on the radio, then next the DSP. It does however downgrade the bootloader no problem. I went ahead and prepatched the boot.img prior to flashing, and it just finished sooooo survey says.......? It worked. Now back in Android 10 XT2113_KIEV_RETUS_10_QZKS30.Q4-40-95-2. Running through the setup now to make sure it dials out etc.
EDIT: Phone dials out, bluetooth and wireless works. Havent seen 5G yet but 4G/LTE is working for sure. So yes, you most assuredly downgrade from 11 if one so chooses. Attached is the vbmeta I used.
PredatorGreen said:
It seems they are sending android 11 to everyone but they changed the boot animation. Now when you boot you see a logo that says edge and then TIM italy. This did not happen in android 10. My moto g 5g is free retail with no brand on the box. I think there is a bug in this update. Is it possible to return to android 10? Also this update changed the intensity of the bars on the screen, now it is more generous but if you see the numeric values of Dbm or ASU these are much lower. I regretted updating so fast and I would like to go back to android 10 until 11 is fixed.
Click to expand...
Click to collapse
You can always just root phone and change the boot animation files. They're in system/media/bootanimation.zip
Just download android 10 firmware get this file from system.img and put it on your phone
the.real.p3y0t3 said:
I'm using the euro android 11 XT2113-3_KIEV_RETEU_11_RZK31.Q3-25-15 on a XT2113-2 and everything seems happy as a clam, *except* it would not flash the radio.img. As far as being "boned" if you went to 11 but wished to downgrade.... Has anyone bothered to try a patched vbmeta? I could go up or down on my one action using this route. I think I may just try for the hell of it.
EDIT: downloading 10 now. If it works I'll post my patched vbmeta.
EDIT: Now keep in mind I am doing this from a flash of android 11 xt2113-3 on a xt2113-2 handset... The flash fails on the radio, then next the DSP. It does however downgrade the bootloader no problem. I went ahead and prepatched the boot.img prior to flashing, and it just finished sooooo survey says.......? It worked. Now back in Android 10 XT2113_KIEV_RETUS_10_QZKS30.Q4-40-95-2. Running through the setup now to make sure it dials out etc.
EDIT: Phone dials out, bluetooth and wireless works. Havent seen 5G yet but 4G/LTE is working for sure. So yes, you most assuredly downgrade from 11 if one so chooses. Attached is the vbmeta I used.
Click to expand...
Click to collapse
Hello and sorry for asking a newbie question here but I don't want this to go sideways...
I have a new XT2113-2 (TM) that is yet to be boot loader unlocked/rooted/etc. I don't want to do that until I am sure. I got this variant of the phone so I could unlock the bootloader, root, TWRP, etc and was afraid the "global" variant -3 might not work with USA 5G. The phone came with Android 11 installed (and has since auto-installed at least one security update). It shows the build as RZKS31.Q3-45-16-3-11 and the baseband ends with Kiev_TMO_CUST. I am using it on ATT (via Red Pocket) since TM service just sucks where I live. And I do get the 5G icon on it now.
But ideally, I want to get this to the original TM Android 10, which I think is shown here as the file XT2113-2_KIEV_TMO_10_QZKS30.Q4-40-95-6_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml.zip as I hope it will undo some of the "security" crap Google has added to Android with each successive release.
So I need to be sure of the following:
1. Can I downgrade from 11 to 10?
2. Is there some reason to NOT use the firmware mentioned above? Should I use retail US (RETUS) instead? I am not sure the differences (it would be great if that would permit me to use this phone on Red Pocket Verizon but the IMEI now shows as incompatible on Verizon).
3. Must I unlock the boot loader to downgrade? I know I must to do other stuff and I have the unlock code on hand and ready to put it if needed. If I must unlock the boot loader to downgrade, will I have to re-unlock it afterwards? And, if so, will I have to go through the same process of getting a code or will the code I have now work?
4. How do I flash to do the downgrade? I have the Lenovo Rescue/Smart Assistant installed on my PC and was able to download the stock firmware (I assume it matches what is on there now) and stashed it aside. But is there some other tool needed?
5. Once I achieve downgrade, what is the best way to avoid having the thing auto-update to Android 11?
Thanks for your help with these questions.