Ok I downloaded the May ota payload zip and flashed via fastboot in stock recovery
(adb sideload otamay.zip) renamed zip of course.
Absolutely no problems . i didn't have to update any platform tools or anything.
I read platform 33.0 instead of 34.0 ...I haven't updated any adb drivers since 2000.
Note my bootloader is locked no root.
So in case anyone is not aware us non-rooted pixels can update firmware using adb sideload command in stock recovery.
After i flashed the ota.zip my performance got better. Seems the carrier factory software is slower. Even on my Motorola phones i would flash the retail software and remove the carrier software version.
Always a cleaner android experience imo..
Loving my Pixel 7 Pro on Stock no issues...
jhjhjhjhjhjh said:
So in case anyone is not aware us non-rooted pixels can update firmware using adb sideload command in stock recovery.
Click to expand...
Click to collapse
Every Android can be updated via adb sideload using the correct OTA file. That's quite normal. And a full firmware flash would require an unlocked bootloader and not root.
jhjhjhjhjhjh said:
Seems the carrier factory software is slower.
Click to expand...
Click to collapse
you still have the same firmware installed on your device. it's only updated.
WoKoschekk said:
you still have the same firmware installed on your device. it's only updated.
Click to expand...
Click to collapse
True just wasnt clear on pixel devices thought these devices had a different method of things.
Anyways thanks for clearing it up
I guess all pixels share one firmware across all carriers and regions..
jhjhjhjhjhjh said:
I guess all pixels share one firmware across all carriers and regions..
Click to expand...
Click to collapse
No, they have different builds for other carriers/regions. See here. But it's not possible to change the region/carrier version via OTA. You would need a full firmware for that, but it's not recommended and won't have any benefits for you.
Since you are locked and not rooted, why don't you just update from Settings/System/System update?
Related
First let me thank this community for the MANY years of great help pushing my devices to their limits. I've never register or posted because I've ALWAYS been able to find my answers with a simple search and really never have much to add.
This time I can't find a good answer. I hope this isn't too much of an amateur question.....
I purchased my Pixel via Verizon (I know....) and have unlocked the bootloader and rooted.
I really don't want to mess with custom ROM's for a while and I still want the latest stock version. How do I update to the latest version without losing recovery and root? Example: I updated to 7.1.1 the other day, then wiped, unlocked, installed recovery and rooted. I went back to 7.1 and don't know how to update to 7.1.1 again or other future versions. I hear that flashing stock rom from Google will wipe recovery and root. Is that correct?
Thanks again for all the years of sharing your experiences.
http://forum.xda-developers.com/pixel/development/tool-skipsoft-android-toolkit-google-t3482761 download that
https://developers.google.com/android/ota download OTA images
use the toolkit to sideload flash the OTA.
foolie said:
http://forum.xda-developers.com/pixel/development/tool-skipsoft-android-toolkit-google-t3482761 download that
https://developers.google.com/android/ota download OTA images
use the toolkit to sideload flash the OTA.
Click to expand...
Click to collapse
Thanks for the reply. Follow up question after scanning the toolkit description..... I'll look deeper into it in a bit.
This will retain root? Will using adb to sideload lose root?
I think so. You can just reflash SuperSU in recovery :good:
Farmer Tony said:
First let me thank this community for the MANY years of great help pushing my devices to their limits. I've never register or posted because I've ALWAYS been able to find my answers with a simple search and really never have much to add.
This time I can't find a good answer. I hope this isn't too much of an amateur question.....
I purchased my Pixel via Verizon (I know....) and have unlocked the bootloader and rooted.
I really don't want to mess with custom ROM's for a while and I still want the latest stock version. How do I update to the latest version without losing recovery and root? Example: I updated to 7.1.1 the other day, then wiped, unlocked, installed recovery and rooted. I went back to 7.1 and don't know how to update to 7.1.1 again or other future versions. I hear that flashing stock rom from Google will wipe recovery and root. Is that correct?
Thanks again for all the years of sharing your experiences.
Click to expand...
Click to collapse
That's not possible. If you installed the 7.1.1 update you wouldn't have been able to unlock the bootloader again. So you must have had it unlocked before the update.
aholeinthewor1d said:
That's not possible. If you installed the 7.1.1 update you wouldn't have been able to unlock the bootloader again. So you must have had it unlocked before the update.
Click to expand...
Click to collapse
I updated, then decided to root so I factory reset which brought me back to 7.1...... I didn't even know it wouldn't work on 7.1.1 so I guess I was lucky to have done so. I just thought it would be safer to start with a clean slate.
It wasn't until I noticed I could no longer double tap to see notifications that I realized that was only in 7.1.1 and noticed that I couldn't update to it anymore.
Edit: Maybe when I said "wiped" I should have said "factory reset".
foolie said:
I think so. You can just reflash SuperSU in recovery :good:
Click to expand...
Click to collapse
I figured I could do this as a last resort but would love to side load and just go about my day. Nice to know that there wouldn't be an issue, thanks.
I realize this isn't my thread, but... I flashed factory image to my Pixel but the recovery flashing failed. How can I get stock recovery back on so I can take the update?
Crowick said:
I realize this isn't my thread, but... I flashed factory image to my Pixel but the recovery flashing failed. How can I get stock recovery back on so I can take the update?
Click to expand...
Click to collapse
Use the skipsoft toolkit and try again with a new factory image download.
foolie said:
http://forum.xda-developers.com/pixel/development/tool-skipsoft-android-toolkit-google-t3482761 download that
https://developers.google.com/android/ota download OTA images
use the toolkit to sideload flash the OTA.
Click to expand...
Click to collapse
sorry I'm a total newb, where is the sideload option? I keep looking but don't see it
mrj0087 said:
sorry I'm a total newb, where is the sideload option? I keep looking but don't see it
Click to expand...
Click to collapse
There's a section 'Updating instructions' in the OTA page (linked above) with instructions. Not for the faint of heart if you're unfamiliar with ADB.
It's on the toolkit options after you select your device.
Do you mean you booted into recovery and reflashed because I've actually been wondering almost exactly what you have.
I have a VZW pixel that I unlocked and rooted via adb/fastboot and I've been wonder if accepting a Verizon OTA would unroot me, and relock the bootloader. The 2nd Verizon update as we know disabled depixel and grayed out the option in dev options but do current OTA updates (not images I downloaded myself) unroot and relock which would prevent me from unlocking and getting root again
I'm running a Canadian Pixel on 7.1, I just unrooted so I could do the OTA to 7.1.1.
The update will download but fails while installing.
I'd like to flash the update myself but I'm unsure how. I'm running Ubuntu. Any help?
Thanks!
Sent from my Pixel using XDA-Developers Legacy app
Hi.. is the update like 200+ mb? if so mine does the SAME thing. Mine is (NDE63X) and you WONT find a OTA or a image for 7.1.1. NO clue
Have either of you tried the OTA images from Google's developer site?
Doesn't bootloader have to be locked to take the OTA? Don't do this if your on Verizon veriant.
Konfuzion said:
Doesn't bootloader have to be locked to take the OTA? Don't do this if your on Verizon veriant.
Click to expand...
Click to collapse
NO it doesn't have to be locked. I don't think there is a Verizon variant in Canada either which is what the OP says they have.
I mentioned the Verizon veriant because people other than the OP will read what I posted.
christanya99 said:
I'm running a Canadian Pixel on 7.1, I just unrooted so I could do the OTA to 7.1.1.
The update will download but fails while installing.
I'd like to flash the update myself but I'm unsure how. I'm running Ubuntu. Any help?
Thanks!
Click to expand...
Click to collapse
See below.
Zeblade said:
Hi.. is the update like 200+ mb? if so mine does the SAME thing. Mine is (NDE63X) and you WONT find a OTA or a image for 7.1.1. NO clue
Click to expand...
Click to collapse
Download fastboot from Google and unzip it.
https://developer.android.com/studio/releases/platform-tools.html
Download the latest full factory images from here and unzip it into your fastboot folder. Edit the flashall bat file and remove the -w so you save your apps and data. Run flashall.Bat You will be stock not rooted and no TWRP when you are done. Put back those items if you want.
https://developers.google.com/android/images
You cannot take OTAs directly once you root, even if you completely unroot. You'll need to sideload (or use the edited factory image as in the post above mine). It's not very difficult, there's a nice guide over here: https://forum.xda-developers.com/pixel/how-to/twrp-root-nmf26u-sideload-guide-t3531616
You'll need to re-root/reinstall TWRP if you want to use that functionality again.
I recently unlocked the bootloader on my pixel. It has 8.1 on it and I want to update it to 9.0. Can I flash the regular factory Pie image or do I have to flash the Verizon variant? Full image or OTA?
Also, I'm assuming all OTAs will fail to install once the bootloader is unlocked?
Thanks.
If you're going from stock ROM to stock ROM, you can install the OTA, regardless of bootloader being unlocked. I think it's easier to install the OTA, and there's no risk of losing data. The OTA is also a smaller download than the full factory image.
Only install the Verizon variant of the ROM if you have the Verizon Pixel. Do not mix ROM variants.
All OTA Images
All Full Factory Images
post-mortem said:
If you're going from stock ROM to stock ROM, you can install the OTA, regardless of bootloader being unlocked. I think it's easier to install the OTA, and there's no risk of losing data. The OTA is also a smaller download than the full factory image.
Only install the Verizon variant of the ROM if you have the Verizon Pixel. Do not mix ROM variants.
All OTA Images
All Full Factory Images
Click to expand...
Click to collapse
You know there is no such thing as verizon specified ROMs on Pixel forum ryt??. Unless it is project treble he can flash any sailfish rom
---------- Post added at 02:00 AM ---------- Previous post was at 01:42 AM ----------
rumi409 said:
I recently unlocked the bootloader on my pixel. It has 8.1 on it and I want to update it to 9.0. Can I flash the regular factory Pie image or do I have to flash the Verizon variant? Full image or OTA?
Also, I'm assuming all OTAs will fail to install once the bootloader is unlocked?
Thanks.
Click to expand...
Click to collapse
I do have a unlocked Verizon pixel. You have two options
1. update via OTA (if you haven't installed TWRP or Magisk yet)
2. Go to google factory images> download latest full factory images file. Last I remember there is no Verizon specified one, so I downloaded latest one and works fine.
crazykas said:
You know there is no such thing as verizon specified ROMs on Pixel forum ryt??. Unless it is project treble he can flash any sailfish rom
Click to expand...
Click to collapse
Hmmm... as the OP is specifically talking about Stock Firmwares I'm wondering why - if, as you're affirming, Verizon-specific ones don't exist - Google is listing Verizon-specific stock firmwares on that page : https://developers.google.com/android/images#sailfish
Could you please enlighten me?
bafforosso said:
Hmmm... as the OP is specifically talking about Stock Firmwares I'm wondering why - if, as you're affirming, Verizon-specific ones don't exist - Google is listing Verizon-specific stock firmwares on that page : https://developers.google.com/android/images#sailfish
Could you please enlighten me?
Click to expand...
Click to collapse
Yes this one is the latest android P which also for verzion model as for others 9.0.0 (PPR2.181005.003, Oct 2018). FYI: i have verzion model and i flashed those
crazykas said:
Yes this one is the latest android P which also for verzion model as for others 9.0.0 (PPR2.181005.003, Oct 2018). FYI: i have verzion model and i flashed those
Click to expand...
Click to collapse
Are you saying you flashed the PPR2.181005.003, Oct 2018 build on your unlocked Verizon pixel without issues?
Also, when you sideload an OTA using TWRP, does it overwrite the recovery partition?
Thanks.
rumi409 said:
Also, when you sideload an OTA using TWRP, does it overwrite the recovery partition?
Click to expand...
Click to collapse
These phones don't have a recovery partition. When you "boot to recovery," it actually loads a portion of the boot.img file, which is part of any ROM flash. When you "install" TWRP, the installer actually patches the boot.img file. This means you can recover from a bad flash by using fastboot to flash the stock boot.img file. Get the boot.img from the full stock image or custom ROM, and flash it in bootloader mode with fastboot flash boot boot.img
rumi409 said:
Are you saying you flashed the PPR2.181005.003, Oct 2018 build on your unlocked Verizon pixel without issues?
Also, when you sideload an OTA using TWRP, does it overwrite the recovery partition?
Thanks.
Click to expand...
Click to collapse
1. Yes. Flashed PPR2.181005.003, Oct 2018 on my unlokced verzion without issues. FYI: read this post , this also applicable for non-xl (sailfish) https://forum.xda-developers.com/showpost.php?p=71822255&postcount=13
2. No. As i repeated before, i was on stock ROM (8.1) and fupdate to 9.0 via system OTA. FYI. sideload won't work TWRP, you must do it on stock recovery
crazykas said:
1. Yes. Flashed PPR2.181005.003, Oct 2018 on my unlokced verzion without issues. FYI: read this post , this also applicable for non-xl (sailfish) https://forum.xda-developers.com/showpost.php?p=71822255&postcount=13
2. No. As i repeated before, i was on stock ROM (8.1) and fupdate to 9.0 via system OTA. FYI. sideload won't work TWRP, you must do it on stock recovery
Click to expand...
Click to collapse
Got it. Thanks.
Hi,
My Pixel 3a as an unlocked bootloader and is rooted.
Usually, when I update my system every month, I get the OTA update zip on google website to do the update and only patches the boot.img from the factory image with magisk to keep the root.
But this month, we get Android 12 and I saw on this thread : https://www.xda-developers.com/how-to-install-android-12/ that it was recommended not to use the OTA update for updating to Android 12 on unlocked bootloader.
As I don't know why, can you explain me if it is or not dangerous or impossible, and eventually why I have to use the factory image to install this new system ?
I know that every time i made a wipe data (even if i know there's a way to delete the -w in the bat file but it's not recommended) it made me a day to restore all my apps and configurations... So if i can avoid this, I'd prefer.
Thanks in advance
oldbear3 said:
But this month, we get Android 12 and I saw on this thread : https://www.xda-developers.com/how-to-install-android-12/ that it was recommended not to use the OTA update for updating to Android 12 on unlocked bootloader.
Click to expand...
Click to collapse
I don't see this warning on that page?
The point of the full OTA sideload is that works with both locked and unlocked bootloaders.
The factory image only works with unlocked bootloaders.
I have a 4a with unlocked bootloader and just upgraded using the OTA and it was fine. I normally use the factory image (removing the -w arg) but found warnings on the internet that this would break when upgrading to Android 12 so I did the OTA instead.
I was even able to re-root with Magisk 23 as normal, which is apparently not possible for newer devices (eg. Pixel 5 guide: https://forum.xda-developers.com/t/guide-update-to-and-re-root-android-12.4345627/).
a1291762 said:
I don't see this warning on that page?
The point of the full OTA sideload is that works with both locked and unlocked bootloaders.
The factory image only works with unlocked bootloaders.
I have a 4a with unlocked bootloader and just upgraded using the OTA and it was fine. I normally use the factory image (removing the -w arg) but found warnings on the internet that this would break when upgrading to Android 12 so I did the OTA instead.
I was even able to re-root with Magisk 23 as normal, which is apparently not possible for newer devices (eg. Pixel 5 guide: https://forum.xda-developers.com/t/guide-update-to-and-re-root-android-12.4345627/).
Click to expand...
Click to collapse
Great, thanks a lot. Made just right now and it works perfectly. The root also worked for me.
a1291762 said:
I don't see this warning on that page?
Click to expand...
Click to collapse
About this question, it's written for OTA Updates :
"To install the stable build, you need to sideload the appropriate OTA package for your device from Recovery through ADB. This method will also work for Google Pixel devices with a locked bootloader"(but as I re-read it, I see that it's written that it "also work" with locked bootloader"). For the full update, it's written "If you have an unlocked bootloader on a Google Pixel device, you need to flash the full factory image of the Android 12 via Fastboot"...so I thought it was the only option.
But you're right, it's not exactly what's written.
Background:
I unlocked the bootloader and then proceeded to flash the device from 12 to 11 using THIS tutorial. When I got to the first "fastboot reboot fastboot" the phone never rebooted. The screen is all black. I can't get into recovery or back into fastboot using the button method.
I downloaded the MSM Global tool and got all the drivers installed. I was able to start the flashing process but get "Device not match image" early in the process. I have called OnePlus customer service. They didn't ask any questions just told me to send in the phone. I would rather fix this myself if possible. Any insight and or help is much appreciated.
UPDATE: I found this information, and it had me flash the India 9 Pro version. It worked. I have a booting phone and can now work on getting it back to the US version.
I wish people would stop following the guide for fastboot flashing. Just use the MSM while it still recognizes your device because if fastboot flashing fails, you end up having to flash it multiple times as it's not recognizing it as the correct unit anymore with that level of corruption.
To get back to global firmware, flash this in the local upgrade tool.
https://oxygenos.oneplus.net/OnePlus9Oxygen_22.O.11_OTA_0110_all_2107082125_downgrade_059624cc7298428b.zip
It is the global downgrade package. It will wipe your phone and when it comes back, you will be back on global software.
After you flash that, go to OTA upgrade and it will say it's going to download C.48 but it will actually install 11.2.10.10 and then you will have the latest OOS11.
If you download it directly to the phone or copy it over with a PC, the file may disappear. Enable USB debugging and use adb.
adb push nameof.zip /sdcard/
EtherealRemnant said:
I wish people would stop following the guide for fastboot flashing. Just use the MSM while it still recognizes your device because if fastboot flashing fails, you end up having to flash it multiple times as it's not recognizing it as the correct unit anymore with that level of corruption.
To get back to global firmware, flash this in the local upgrade tool.
https://oxygenos.oneplus.net/OnePlus9Oxygen_22.O.11_OTA_0110_all_2107082125_downgrade_059624cc7298428b.zip
It is the global downgrade package. It will wipe your phone and when it comes back, you will be back on global software.
After you flash that, go to OTA upgrade and it will say it's going to download C.48 but it will actually install 11.2.10.10 and then you will have the latest OOS11.
If you download it directly to the phone or copy it over with a PC, the file may disappear. Enable USB debugging and use adb.
adb push nameof.zip /sdcard/
Click to expand...
Click to collapse
Thanks for that! The phone is back to fulling functioning with the proper version of OOS. It has been a long time since I rooted and ROMed. Fastboot used to be a straightforward method of flashing a stock ROM. Doesn't seem like it is anymore.
hillmom said:
Thanks for that! The phone is back to fulling functioning with the proper version of OOS. It has been a long time since I rooted and ROMed. Fastboot used to be a straightforward method of flashing a stock ROM. Doesn't seem like it is anymore.
Click to expand...
Click to collapse
Glad that it worked. Did you have the bootloader locked? I am just trying to confirm I'm not crazy and that I was actually able to use it with a locked bootloader lol.
Yeah fastboot flashing was the gold standard way to avoid a brick back in the days before A/B partitions and Android Verified Boot came along but not so much now. This device in particular seems to be really fussy about fastboot flashing. I never managed to brick my Pixel 3 XL doing it but I have had to MSM multiple times trying to do fastboot commands and custom recoveries to flash custom ROMs on my OP9. I have got the process down tova science at this point lol. I just went back to stock and rooted it and I'm much happier with that than I was with custom ROMs that were plagued with issues.
EtherealRemnant said:
Glad that it worked. Did you have the bootloader locked? I am just trying to confirm I'm not crazy and that I was actually able to use it with a locked bootloader lol.
Yeah fastboot flashing was the gold standard way to avoid a brick back in the days before A/B partitions and Android Verified Boot came along but not so much now. This device in particular seems to be really fussy about fastboot flashing. I never managed to brick my Pixel 3 XL doing it but I have had to MSM multiple times trying to do fastboot commands and custom recoveries to flash custom ROMs on my OP9. I have got the process down tova science at this point lol. I just went back to stock and rooted it and I'm much happier with that than I was with custom ROMs that were plagued with issues.
Click to expand...
Click to collapse
Sorry, I did it with the bootloader unlocked.
I might go back to Stock soon enough. While not as big a pain as Samsung, also not the easiest phone I've played with either.
EtherealRemnant said:
I wish people would stop following the guide for fastboot flashing. Just use the MSM while it still recognizes your device because if fastboot flashing fails, you end up having to flash it multiple times as it's not recognizing it as the correct unit anymore with that level of corruption.
To get back to global firmware, flash this in the local upgrade tool.
https://oxygenos.oneplus.net/OnePlus9Oxygen_22.O.11_OTA_0110_all_2107082125_downgrade_059624cc7298428b.zip
It is the global downgrade package. It will wipe your phone and when it comes back, you will be back on global software.
After you flash that, go to OTA upgrade and it will say it's going to download C.48 but it will actually install 11.2.10.10 and then you will have the latest OOS11.
If you download it directly to the phone or copy it over with a PC, the file may disappear. Enable USB debugging and use adb.
adb push nameof.zip /sdcard/
Click to expand...
Click to collapse
Hii! My phone is LE2115 a12 C60 can i use this file to go back to OSS11? Also do i need to unlock my bootloader or i can use this even with bootloader locked? Last one where can i find "local update tool"? Thanks a lot
eliasdeejay said:
Hii! My phone is LE2115 a12 C60 can i use this file to go back to OSS11? Also do i need to unlock my bootloader or i can use this even with bootloader locked? Last one where can i find "local update tool"? Thanks a lot
Click to expand...
Click to collapse
Yes, you can use this to go back to OOS11. You shouldn't need to unlock the bootloader as this is an officially sanctioned downgrade package.
Since you're on Android 12 you need to install the local upgrade APK:.
https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
Install that, push the downgrade zip to /sdcard/, open the newly installed system update app, hit the gear, and it should show you the zip file waiting.
EtherealRemnant said:
Yes, you can use this to go back to OOS11. You shouldn't need to unlock the bootloader as this is an officially sanctioned downgrade package.
Since you're on Android 12 you need to install the local upgrade APK:.
https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
Install that, push the downgrade zip to /sdcard/, open the newly installed system update app, hit the gear, and it should show you the zip file waiting.
Click to expand...
Click to collapse
Hii! by chance do you know where I can download the previous versions of A12 update? specifically C.48. And if i can install it via local upgrade APK. Thanks!
eliasdeejay said:
Hii! by chance do you know where I can download the previous versions of A12 update? specifically C.48. And if i can install it via local upgrade APK. Thanks!
Click to expand...
Click to collapse
https://android.googleapis.com/packages/ota-api/package/1797d47ddef0fca1411fb006b9c7a1a7ba33d818.zip
There is a pinned post with them. This is C.48 for global and yes, you use the local upgrade but since you're on OOS11, you don't use the APK, use the update function in system settings and tap the gear and you'll see it.
Hi i tried to use the updater on android12 and try to downgrade it to .48 but it return error. So i need to downgrade to android 11 first and then update it again to .48?
cruzzmz said:
Hi i tried to use the updater on android12 and try to downgrade it to .48 but it return error. So i need to downgrade to android 11 first and then update it again to .48?
Click to expand...
Click to collapse
Correct. Only the specific downgrade packages can downgrade. It will also wipe the device. There's no way around this. Once you are back on 11, you can do the local upgrade to flash the full C.48 ROM instead of having to do the whole OTA process (normal process is downgrade, OTA to 11.2.10.10 (it will say it's C.48 but have a file size of like 150MB but it's not), OTA to C.48 so you get to skip a step if you just use the full update package).
EtherealRemnant said:
Correct. Only the specific downgrade packages can downgrade. It will also wipe the device. There's no way around this. Once you are back on 11, you can do the local upgrade to flash the full C.48 ROM instead of having to do the whole OTA process (normal process is downgrade, OTA to 11.2.10.10 (it will say it's C.48 but have a file size of like 150MB but it's not), OTA to C.48 so you get to skip a step if you just use the full update package).
Click to expand...
Click to collapse
Hii is 11.2.10.10 a lot better than 11.2.8.8? Sorry for a lot of questions im new to OnePlus
EtherealRemnant said:
Correct. Only the specific downgrade packages can downgrade. It will also wipe the device. There's no way around this. Once you are back on 11, you can do the local upgrade to flash the full C.48 ROM instead of having to do the whole OTA process (normal process is downgrade, OTA to 11.2.10.10 (it will say it's C.48 but have a file size of like 150MB but it's not), OTA to C.48 so you get to skip a step if you just use the full update package).
Click to expand...
Click to collapse
Ok if i understand correctly, i just use the updater to flash the android 11 zip file that you provided and it will do a full wipe and will restore to android 11. Then i just use the updater again to flasj it to .48
am i correct?
eliasdeejay said:
Hii is 11.2.10.10 a lot better than 11.2.8.8? Sorry for a lot of questions im new to OnePlus
Click to expand...
Click to collapse
I don't know because I didn't get my phone until February so I went right to 11.2.10.10. It is important to update though because it gets you a working OS on both slots instead of just one.
cruzzmz said:
Ok if i understand correctly, i just use the updater to flash the android 11 zip file that you provided and it will do a full wipe and will restore to android 11. Then i just use the updater again to flasj it to .48
am i correct?
Click to expand...
Click to collapse
Yes, if you want to go back to 12.
EtherealRemnant said:
Yes, if you want to go back to 12.
Click to expand...
Click to collapse
yes i want to go to 12 but not the crappy .60
cruzzmz said:
yes i want to go to 12 but not the crappy .60
Click to expand...
Click to collapse
Lol yeah. I'm not too happy with C.60 either. I really don't want to wipe my device and lose my Signal chats again.
EtherealRemnant said:
Lol yeah. I'm not too happy with C.60 either. I really don't want to wipe my device and lose my Signal chats again.
Click to expand...
Click to collapse
my sentiment exactly dunno how OP fk up with the model and the update
so i dont need MSM Tool to downgrade??
cruzzmz said:
my sentiment exactly dunno how OP fk up with the model and the update
so i dont need MSM Tool to downgrade??
Click to expand...
Click to collapse
I don't know what you aren't understanding but I'm tired of repeating myself. Read what I wrote and it answers your question.
EtherealRemnant said:
I don't know what you aren't understanding but I'm tired of repeating myself. Read what I wrote and it answers your question.
Click to expand...
Click to collapse
Ok done it ... on OOS11 now .... no need to unlock bootloader can just flash the file directly.
Will try OOS11 for a while and see if it is worth updating to OOS12