Related
According to the Verizon Galaxy S5 Update Page:
Android® security patches and bug fixes.
Resolved a ring-back tone issue on calls to non-Verizon phones.
Fixed an issue where some users reported difficulty making calls to non-Verizon customers.
Click to expand...
Click to collapse
The security patch included is (most likely) the July one, since Samsung also just released a new software update to international models which includes the July security patch and Verizon has been updating the "Galaxy S" series phones with the July update over the past few weeks.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQF2_G900VVZW2DQF2_G900VVRU2DQF2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQF2_G900VVZW2DQF2_G900VVRU2DQF2_HOME_No_Aboot.tar.md5.zip
Appreciate that, but how do you get the Odin firmware file out of curiosity?
drewcu said:
Appreciate that, but how do you get the Odin firmware file out of curiosity?
Click to expand...
Click to collapse
Updato is one way; this shows the list for the Verizon S5 with the most recent at the top; they haven't gotten the new update up yet though.
I think that another way would be for someone to dig through the update.zip file which would be on the phone of someone who got the OTA update downloaded but had not yet installed it yet.
To confirm, the only thing that's different between the dev-friendly version (when it comes out) and the stock is the missing aboot? Thanks again.
drewcu said:
To confirm, the only thing that's different between the dev-friendly version (when it comes out) and the stock is the missing aboot? Thanks again.
Click to expand...
Click to collapse
Yes and the firmware just came out today so I'm currently in the process of uploading both versions.
Dudash said:
Yes and the firmware just came out today so I'm currently in the process of uploading both versions.
Click to expand...
Click to collapse
Is this flashable with Odin only or possibly need to already be on a specific kernal? I have tried on two S5900V's through TWRP and both result in a failure message. Both are on jkruse de-bloated MM rom at the moment.
Kaliaila said:
Updato is one way; this shows the list for the Verizon S5 with the most recent at the top; they haven't gotten the new update up yet though.
I think that another way would be for someone to dig through the update.zip file which would be on the phone of someone who got the OTA update downloaded but had not yet installed it yet.
Click to expand...
Click to collapse
The link for the update zip is not working when you tap or click on it
Sent from my SM-G900V using Tapatalk
---------- Post added at 11:25 AM ---------- Previous post was at 11:16 AM ----------
No one believe update.zip files anymore ? i need one badley
Sent from my SM-G900V using Tapatalk
Kastro1784 said:
The link for the update zip is not working when you tap or click on it
Sent from my SM-G900V using Tapatalk
---------- Post added at 11:25 AM ---------- Previous post was at 11:16 AM ----------
No one believe update.zip files anymore ? i need one badley
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Odd. It works for me.
Sent from my SM-G900V using Tapatalk
Since no one wanted to chime in and help me out in my post, you need to unzip the file and load the md5 into Odin's AP slot and flash it. Then let the phone do its thing and flash the latest TWRP with odin after. Then go back into TWRP and flash supersu to gain root again. Trying to flash right within TWRP is not an option, not sure why its not explained.
So this update wont "factory reset" my device?
AWESOME1092387456 said:
So this update wont "factory reset" my device?
Click to expand...
Click to collapse
I dirty flashed two S5's last night with Odin, no factory reset and both phones kept their bootloaders un touched since unlocked. :good:
stuck on Verizon boot screen
After the update via OTA, my aunt's phone has been stuck on Verizon boot screen. Tried booting into safe mode, with same result. Any ideas on how not to lose all her data? Thanks!
This sucks I wanna download this so bad but my computer is down smdh is it possible someone can make and ota update zip file for me so can flash this through stock recovery on my phone ?
Sent from my SM-G900V using Tapatalk
I guess no one knows how to do it huh smdh
Sent from my SM-G900V using Tapatalk
Rumsfield said:
I dirty flashed two S5's last night with Odin, no factory reset and both phones kept their bootloaders un touched since unlocked. :good:
Click to expand...
Click to collapse
Did you loose root?
I dirty flashed and lost root, was unable to get it back.
Reloaded TWRP via Odin and then flashed SuperSU, nothing. Wiped and restore backup all good. ..
mastertech007 said:
Did you loose root?
I dirty flashed and lost root, was unable to get it back.
Reloaded TWRP via Odin and then flashed SuperSU, nothing. Wiped and restore backup all good. ..
Click to expand...
Click to collapse
I always flash super su and whatever else I need in recovery after I've flashed the rom so I cant give you a definitive answer. Both phones did upgrade without data loss and now advanced calling/wifi calling actually work now which is why I flashed in the first place.
Working?
Is this working? Ive tried everything and i have the Toshiba chip. Emmc 11. It soft bricks if i try to downgraded to stock builds.
JasonD1180 said:
Is this working? Ive tried everything and i have the Toshiba chip. Emmc 11. It soft bricks if i try to downgraded to stock builds.
Click to expand...
Click to collapse
The new file seemed to unlock boot loader. Couldnt get odin to flash twrp......
JasonD1180 said:
The new file seemed to unlock boot loader. Couldnt get odin to flash twrp......
Click to expand...
Click to collapse
If you flash the dev boot loader friendly version it wont screw with your bootloader whatsoever. Before you restart go back in TWRP and flash supersu to get root again. Saying it "unlocked boot loader" may cause confusion to people because it does not, you need to manually go from locked to DEV status via a few of the methods posted in here.
Rumsfield said:
If you flash the dev boot loader friendly version it wont screw with your bootloader whatsoever. Before you restart go back in TWRP and flash supersu to get root again. Saying it "unlocked boot loader" may cause confusion to people because it does not, you need to manually go from locked to DEV status via a few of the methods posted in here.
Click to expand...
Click to collapse
Ive not had twrp or root on this device but it went from saying vzw official binary to samsung original. Will i be able to root as long as twrp flashes?
Just a few minutes ago,i got the latest OOS 5.1.11.The change logs are
System
1.Optimized network connection
2.Optimized stability for wi-fi connection
3.Fixed screen flickering issue in day light
4.General bug fixes and improvements
5.confirm pin without tapping
Camera
Improved HDR mode
Any thoughts about the improved HDR mode? Didn't receive the update yet (Germany) but would be nice if someone could do before/after photos.
I also get that update.
If i download it.. can i just not update right away?
because i want to manually update from twrp and re root with magisk.
Thanks in advance
Sent from my ONEPLUS A6000 using Tapatalk
ossy1337 said:
Any thoughts about the improved HDR mode? Didn't receive the update yet (Germany) but would be nice if someone could do before/after photos.
Click to expand...
Click to collapse
I have no photos with older firmware.i think now the photos taken are more brighter
Root users beware: issues with newer TWRP version!
This article only applies to users running TWRP recovery on a rooted device. Don't have TWRP or don't know what this means? You're probably fine.
If you've recently installed or updated TWRP recovery, you might have faced that you can't install anything with it, and that the start screen is immediately shown when updating your device via Oxygen Updater.
Why is this happening to me?
From what it seems, this issue is caused by TWRP versions 3.2.2-0 and 3.2.3-0 being incompatible with the storage encryption technology present on OnePlus devices.
Normally, you're asked to enter your PIN or unlock pattern before installing an update / flashing something yourself. However, these new TWRP versions don't prompt for it anymore. Therefore, accessing the storage space of your device is no longer possible.
This is really frustrating, as almost all of your updates / .zip files are stored there. But luckily, there is a solution:
How do I fix this issue?
First of all, if you don't have encryption turned on or are not facing this issue, do not proceed with the steps below since flashing a new version of TWRP can be risky.
Now for the the solution: it involves downgrading TWRP to an earlier version, in which installing updates still worked correctly.
The downgrade can be done either by using a computer with the fastboot command, or by using flashing apps such as the Official TWRP app or Flashify on your device itself.
These are the steps you'll need to do:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
- Flash the version of TWRP using your method of choice. For fastboot users, connect your device to your computer in Fastboot mode and type fastboot flash recovery twrp-3.2.1-1-<yourdevice>.img. When using any of the flashing apps, browse to the correct TWRP.img file and flash it.
- Reboot your device. You'll now be able to access the working version of TWRP
- Do not update your TWRP version until it has been confirmed that this issue has been resolved.
Thanks to Peter Aarnoutse for reporting this issue.
So since twrp latest works fine on my device with encryption included, I can just start the update?
Sent from my ONEPLUS A6003 using Tapatalk
Neurom67 said:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
Click to expand...
Click to collapse
Can you link 3.2.1-1 version? https://eu.dl.twrp.me/enchilada/ There is only 3.2.1-0 or 3.2.2-0
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
No problem with blue twrp.
nieXas said:
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
Click to expand...
Click to collapse
Fails for everyone atm. Was working fine for me until two days ago before Google updated the api
Sent from my ONEPLUS A6003 using Tapatalk
nieXas said:
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
Click to expand...
Click to collapse
Here is why; https://mobile.twitter.com/topjohnwu/status/1029239685338419200
3.2.1.0 installed 5.1.11 fine on my OP6.
nieXas said:
I can confirm, all fine with twrp-3.2.2-0
but seems that safetynet fails
Click to expand...
Click to collapse
SpectraFun said:
No problem with blue twrp.
Click to expand...
Click to collapse
Batfink33 said:
3.2.1.0 installed 5.1.11 fine on my OP6.
Click to expand...
Click to collapse
Can you confirm that you used Oxygen Updater in Automatic mode to flash new OTA and you didn't loose data/root/twrp?
Have TWRP 3.2.3 and installed 5.1.11 just fine.
SMS786 said:
Have TWRP 3.2.3 and installed 5.1.11 just fine.
Click to expand...
Click to collapse
did you use pin or fingerprint disable before flashing?
did you download zip from updater too? can i flash that zip from twrp or it just flashing all the way after download?
sorry.. never using updater to update OS.
need info.. thank you
Sent from my ONEPLUS A6000 using Tapatalk
Vuska said:
did you use pin or fingerprint disable before flashing?
did you download zip from updater too? can i flash that zip from twrp or it just flashing all the way after download?
sorry.. never using updater to update OS.
need info.. thank you
Sent from my ONEPLUS A6000 using Tapatalk
Click to expand...
Click to collapse
Didn't disable my pattern lock..worked just fine.
I downloaded the zip online and installed through TWRP. Just make sure to reinstall your TWRP installer after installing the full rom OTA (wipe cache/dalvik first), then reboot back into TWRP and install Magisk..then boot into system.
The OOS 5.1.11's camera is ****tier than the 5.1.9 as you can read on the official thread on oneplus's forum, some people are advising not to upgrade
Chinaroad said:
The OOS 5.1.11's camera is ****tier than the 5.1.9 as you can read on the official thread on oneplus's forum, some people are advising not to upgrade
Click to expand...
Click to collapse
People seem to be saying this for every release
giebeka said:
Can you confirm that you used Oxygen Updater in Automatic mode to flash new OTA and you didn't loose data/root/twrp?
Click to expand...
Click to collapse
Used Oxygen updater to download zip. Rebooted to bootloader. Went Install and selected ZIP. then added TWRP zip as well. Installed both. Rebooted to bootloader again. Flashed elementalx kernel(you can skip it) and magisk. All works fine.
kakkooran said:
Just a few minutes ago,i got the latest OOS 5.1.11.The change logs are
...
5.confirm pin without tapping
Click to expand...
Click to collapse
I can't find where to enable this. Anyone found it?
Has anyone received an OTA notification yet?
OTA doesn't get released until the 5th or 6th of the month I believe.
artiemon said:
Has anyone received an OTA notification yet?
Click to expand...
Click to collapse
Yes I got the OTA on both the Pixel 3 and the 3a
I'm new to the pixel how do i update to the latest while rooted also no twrp
Sent from my Pixel 3a XL using Tapatalk
What I do is get the whole update,,,not the OTA but the whole fastboot update. Then unzip it fully into a folder and put that into my min fastboot folder. Find the flash-all windows batch file and right click it with notepad +, take out the -w save and close. Then fastboot the update which will update and keep all your data. Then you will have to go in and reroot with Magisk and do the whole boot.img again.
Texus91501 said:
I'm new to the pixel how do i update to the latest while rooted also no twrp
Sent from my Pixel 3a XL using Tapatalk
Click to expand...
Click to collapse
Just received the ota about an hour ago already downloaded and installed.
I'm not seeing an OTA yet but when it does pop up I'm going to try doing the magisk OTA method, don't see why it wouldn't work.
I got it also, I had to manually check for the update though.
Sent from my Pixel 3a XL using Tapatalk
Got tired of waiting so I decided to sideload; that would be when things went sideways. Did the usual but got an error during the flash about a corrupt file and the phone went into softbrick. Had to do a clean flash to get out of it. No idea what that was about but I have to allow as to how I'm not going to be testing the Magisk OTA method for the June update.
I still haven't gotten a notification about it. Manual checks also saying nothing available. Strange. Debating if I want to just do a sideload instead of waiting in case I'm in the weird never-gets-an-update crew.
krabman said:
Got tired of waiting so I decided to sideload; that would be when things went sideways. Did the usual but got an error during the flash about a corrupt file and the phone went into softbrick. Had to do a clean flash to get out of it. No idea what that was about but I have to allow as to how I'm not going to be testing the Magisk OTA method for the June update.
Click to expand...
Click to collapse
ApeironTsuka said:
I still haven't gotten a notification about it. Manual checks also saying nothing available. Strange. Debating if I want to just do a sideload instead of waiting in case I'm in the weird never-gets-an-update crew.
Click to expand...
Click to collapse
I did little different. Went the fastboot route. After removing the "-w" from the flash-all.bat script. Had no problems at all. Just had to reroot and flash the new ex kernal .zip file via the flash tool in EXKM.
All Good
Sent from my Pixel 3a XL using XDA-Developers Legacy app
Anyone else having issues with installing Magisk on this security update?
I just updated via flash-all.bat, rebooted, installed Magisk to June's boot.img, flashed, rebooted & now can't boot without re-flashing the original boot.img (on either slot).
No problem here.
You have to copy boot image from factory images (unzip the image.zip file) it's there to phone. Then use Magisk to PATCH that boot image. Copy it to computer then flash with fastboot flash boot.
There also thread on rooting read that too
Sent from my Pixel 3a XL using XDA-Developers Legacy app
shadyshadow said:
No problem here.
You have to copy boot image from factory images (unzip the image.zip file) it's there to phone. Then use Magisk to PATCH that boot image. Copy it to computer then flash with fastboot flash boot.
Click to expand...
Click to collapse
Yeah, I've done that multiple times & still the same issue.
What size is the patched boot file you got from Magisk? June's boot.img is 68mb & the patched file that Magisk outputs is only 26mb, so I'm not sure that's right
Ok my June boot.img is 64mb ..after patching it is 26.96mb
Sent from my Pixel 3a XL using XDA-Developers Legacy app
---------- Post added at 11:43 AM ---------- Previous post was at 11:41 AM ----------
DanielF50 said:
Yeah, I've done that multiple times & still the same issue.
What size is the patched boot file you got from Magisk? June's boot.img is 68mb & the patched file that Magisk outputs is only 26mb, so I'm not sure that's right
Click to expand...
Click to collapse
Ok my June boot.img is 64mb ..after patching it is 26.96mb
Sent from my Pixel 3a XL using XDA-Developers Legacy app
DanielF50 said:
Yeah, I've done that multiple times & still the same issue.
What size is the patched boot file you got from Magisk? June's boot.img is 68mb & the patched file that Magisk outputs is only 26mb, so I'm not sure that's right
Click to expand...
Click to collapse
I had the same issue. Using Magisk canary 19.4 works patching the boot.img. Also the patched image does get trimmed to 26
MB.
Sent from my Pixel 3a XL using Tapatalk
shadyshadow said:
Ok my June boot.img is 64mb ..after patching it is 26.96mb
Click to expand...
Click to collapse
Thanks!
vandyman said:
I had the same issue. Using Magisk canary 19.4 works patching the boot.img. Also the patched image does get trimmed to 26
MB.
Click to expand...
Click to collapse
Thanks dude - unfortunately this still didn't work for me either so I ended up wiping the whole device & re-flashing the June update, which worked (with 19.4), so gotta spend a couple of hours setting it up again
DanielF50 said:
shadyshadow said:
[/COLOR]Ok my June boot.img is 64mb ..after patching it is 26.96mb
Thanks!
vandyman said:
I had the same issue. Using Magisk canary 19.4 works patching the boot.img. Also the patched image does get trimmed to 26
MB.
Thanks dude - unfortunately this still didn't work for me either so I ended up wiping the whole device & re-flashing the June update, which worked (with 19.4), so gotta spend a couple of hours setting it up again
Click to expand...
Click to collapse
The only thing I can add is that I'm patching with Magisk 19.3 latest stable.
Sent from my Pixel 3a XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Texus91501 said:
I'm new to the pixel how do i update to the latest while rooted also no twrp
Sent from my Pixel 3a XL using Tapatalk
Click to expand...
Click to collapse
If you installed Magisk normally (using the app to modify the stock boot.img and then moving the modified img to your computer to flash it in fastboot mode, then these directions will work. However, If you used the modified boot.img that is being passed around on the forum, these directions will not work because Magisk doesn't have the stock boot.img to use in step 1.
- Magisk: Click “Uninstall” → “restore images” → NO REBOOT
- Download and install OTA → NO REBOOT
- Clear all apps from recents
- Magisk: Click “Install” → “Install to second/inactive slot (After OTA)”
- Reboot
Anyone noticed that the Pixel Imprint name has changed to Nexus Imprint in the June update?
Got my XL today and noticed the change after I updated.
Not amazingly interesting but thought I'd mention it.
Hey, guys. So I've been messing with my phone all day after a soft brick after having BlissROM since Feb. Long story short, something with the ROM update and it messed with my phone. I wiped EVERYTHING thinking it would solve the problem. I was able to use the All-In-One tool to save my phone through the bootloader (Thank goodness!). I finally got it to boot up to stock this morning. I've been trying all morning to gain root, but once I do, I lose WiFi and Network connections. So my question is:
What is the most current version of TWRP and Magisk that will allow me to be on stock and have root without any problems?
This is my setup.
OnePlus 7 Pro
Android version: Android 10
Build: Oxygen OS 10.0.3.GM21AA (now updated to 10.3.1)
Model: GM1917
Unlocked OEM
Unlocked Bootloader
This is the method I am using to push TWRP though the bootloader.
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
These are the files that flash through adb/fastboot and lose Wifi and Network connectivity.
TWRP 3.3.1-79-guacamole-unified-Q: https://sourceforge.net/projects/ma...-guacamole-unified-Q-mauronofrio.img/download
Magisk v20.4: https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
Since I don't have any connectivity at this point, I attempt to flash BlissROM with the following steps.
BlissROM version that last worked for me: https://downloads.blissroms.com/BlissRoms/Q/guacamole/Bliss-v12.6-guacamole-OFFICIAL-20200425.zip
STEPS
Boot into recovery
Backup your current ROM
Perform a factory reset
Flash Bliss Rom
Reboot recovery
Flash OpenGapps--NANO PACKAGE!!
*Flash magisk* optional
Reboot to system
Also, as I've previously stated, I have attempted to flash BlissROM through TWRP and with root (without WiFi and Data), but it hangs on the boot screen. When I go to TWRP and try to reflash the ROM, it gives me the error "cannot mount storage". I follow the instructions as stated in the original post, so I figured it has to be something with the TWRP or Magisk versions not being compatible. Since that does not work, I have since flashed stock and am currently on that without problems. Any links to the most current TWRP/Magisk/rooting methods are greatly appreciated. And if someone could help with getting BlissROM back on my phone afterwards, that would be great. Thanks!
Pretty sure you need to update to 10.3.2 to get it working right.
Sent from my GM1915 using Tapatalk
mjdavis871 said:
Pretty sure you need to update to 10.3.2 to get it working right.
Sent from my GM1915 using Tapatalk
Click to expand...
Click to collapse
I just realized I could update past the first update. I figured it would update to the most recent version version after the flash back to stock, not that it would be incremental. Thank you so much for the heads up!
I have the most recent version of Magisk downloaded. What is the best for 10.3.2?
knightsriot said:
I just realized I could update past the first update. I figured it would update to the most recent version version after the flash back to stock, not that it would be incremental. Thank you so much for the heads up!
I have the most recent version of Magisk downloaded. What is the best for 10.3.2?
Click to expand...
Click to collapse
That I could not say for sure, but my guess is that it would work fine.
Sent from my GM1915 using Tapatalk
mjdavis871 said:
That I could not say for sure, but my guess is that it would work fine.
Sent from my GM1915 using Tapatalk
Click to expand...
Click to collapse
Got it. Does the same goes for TWRP? I read somewhere that the unofficial one might work better with Android Q (I'm assuming that's Android 10?)
I always use the unofficial version, works fine for me.
Sent from my GM1915 using Tapatalk
mjdavis871 said:
I always use the unofficial version, works fine for me.
Sent from my GM1915 using Tapatalk
Click to expand...
Click to collapse
Got it. Okay, so it looks like I'll be giving BlissROM one last shot!
Before I flash TWRP and Magisk, I looked on the Oneplus website for the 10.3.2 update and it looks like the most current posted is 10.3.1. Should I update to 10.3.2 for the latest ROMS, or will 10.3.1 work fine? If so, where can I find it?
I used the oxygen updater app to download the update and sideloaded it.
Sent from my GM1915 using Tapatalk
mjdavis871 said:
I used the oxygen updater app to download the update and sideloaded it.
Sent from my GM1915 using Tapatalk
Click to expand...
Click to collapse
So it looks like that didn't work. I got stuck on a bootloop again and had to revert back to stock.
I can't seem to find what the problem is. Here is what I am flashing:
TWRP 3.3.1-79-guacamole-unified-Q: https://sourceforge.net/projects/mau...o.img/download
Magisk v20.4: https://github.com/topjohnwu/Magisk/...gisk-v20.4.zip
This is the method I am using flash TWRP to the bootloader.
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
When I flash both of those, I lose Wifi and Network on my stock ROM. I'm assuming one of them is also the reason why I can't flash BlissROM.
You don't need to flash magisk before you flash the ROM, just twrp. I do know when I bootlooped, it was because I missed a step, usually because I didnt wipe data.
Follow the flash instructions step by step or you will for sure bootloop. Read them over and over until you think you have a grasp of how to flash the ROM.
You can always get back into fastboot by holding power and both volume keys...then you can reflash twrp and start over. No need to go back to stock unless you want to or need to.
Just make sure you follow the instructions step by step. This device is a bit different to flash from the devices I have used before ...so it took me a few tries to get it done right.
Sent from my GM1915 using Tapatalk
mjdavis871 said:
You don't need to flash magisk before you flash the ROM, just twrp. I do know when I bootlooped, it was because I missed a step, usually because I didnt wipe data.
Follow the flash instructions step by step or you will for sure bootloop. Read them over and over until you think you have a grasp of how to flash the ROM.
You can always get back into fastboot by holding power and both volume keys...then you can reflash twrp and start over. No need to go back to stock unless you want to or need to.
Just make sure you follow the instructions step by step. This device is a bit different to flash from the devices I have used before ...so it took me a few tries to get it done right.
Sent from my GM1915 using Tapatalk
Click to expand...
Click to collapse
I've been following the steps exactly as written. Take a look at step 5 on the TWRP thread. (https://forum.xda-developers.com/on...covery-unofficial-twrp-recovery-t3931322/amp/)
Install guide (Reccomended):
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line (if you want to have it permanently you should flash the installer)
5. If you will flash the installer and you are stock you need also to flash magisk or your phone will not boot again
6. Enjoy it
Click to expand...
Click to collapse
Furthermore, this is also reiterated in the BlissROM thread. https://forum.xda-developers.com/oneplus-7-pro/development/rom-blissroms-v11-9-t3957341/page138
Make sure you are rooted
Make sure you have a custom recovery installed
For Q-BETA- Make sure you are on Q firmware, is currently set to use OOS 10.3.0 Stable firmware- CLEAN INSTALL!!
Click to expand...
Click to collapse
I also noted that in that previous quote, having the original 10.0.3 I had installed shouldn't have cause any problems. I wiped data (factory reset) every time I flashed BlissROM, as it is the third step in the process.
The reason why I go back to stock using the all-in-one tool is because I don't have anything else to flash. The whole reason I even had a soft brick was because I tried to go back to stock after my BlissROM update and flashed a OTA from the oneplus site. I probably did that incorrectly, however. Idk how what sideload is or how it functions. So that all-in-one tool is my only safety net.
Hello All,
Attempted to update to 11.2.10.10 AA two days ago via full update zip through Oxygen Updater app and Local Upgrade, only to receive Installation Failure. When I check system update in settings it tells me only the incremental update is available.
Rooted OP9 (Magisk v23015 canary), Arter R2 Kernel, and only 5 magisk modules (hideprops, BusyBox, wifibonding, opperfdisabler, and James DSP).
Any ideas?
I also have a rooted global op9. Updated through local upgrade in oxygen updater . Full 3.0 gb zip installed and rebooted to new build! Since your using magisk you need to restore stock boot img. Probably why installation fAils.
mattie_49 said:
Since your using magisk you need to restore stock boot img.
Click to expand...
Click to collapse
How would i do that? Uninstall Magisk? Using Arter Kernel touches vendor and another partition so i believe if i restore stock boot and kernel goes down then i might have an issue. Not sure, this is the first time ive had a problem with an update. Usually its pretty seamless and same, simple process.
Porquiplane said:
How would i do that? Uninstall Magisk? Using Arter Kernel touches vendor and another partition so i believe if i restore stock boot and kernel goes down then i might have an issue. Not sure, this is the first time ive had a problem with an update. Usually its pretty seamless and same, simple process.
Click to expand...
Click to collapse
If you update ota through g-ota you for sure have to restore untouched boot,vendor_boot, dtbo prior to installing 11.2.10.10. Yes uninstall in magisk and it should restore boot image. And since you flashed a kernel you did take a stock backup of these partitions before flashing kernel?
https://android.googleapis.com/packages/ota-api/package/580d47a7dde5862a306c07ff939cc4fe1520860f.zip
Here is 11.2.10.10 ota incremental zip. All images I mentioned above must be restored before you install this. Global op9
mattie_49 said:
If you update ota through g-ota you for sure have to restore untouched boot,vendor_boot, dtbo prior to installing 11.2.10.10. Yes uninstall in magisk and it should restore boot image. And since you flashed a kernel you did take a stock backup of these partitions before flashing kernel?
Click to expand...
Click to collapse
I am not sure if i did. Unless Franco Kernel Manager does it for you, i didnt.
Porquiplane said:
I am not sure if i did. Unless Franco Kernel Manager does it for you, i didnt.
Click to expand...
Click to collapse
Updating locally through oxygen updater and it being a full zip only boot img shouldn't matter if any.
mattie_49 said:
Updating locally through oxygen updater and it being a full zip only boot img shouldn't matter if any.
Click to expand...
Click to collapse
Then not sure why i throws an installation failure message.
Well, i went to Franco Kernel to reflash the stock, and now im bootloop. Stuck on the spinning screen.
As an update, I had to reflash vendor_boot and dtbo after bootloop. Then the phone allowed me to update to the new OOS. Troubles resolved!
The question is, can I flash incremental instead of full if I'm rooted and using oxygen updater?
Moe2003 said:
The question is, can I flash incremental instead of full if I'm rooted and using oxygen updater?
Click to expand...
Click to collapse
Don't do it. Just use the full install. It's safer. I made a magisk'd boot of 11.2.10.10 if you need one after the full update.
Porquiplane said:
Don't do it. Just use the full install. It's safer. I made a magisk'd boot of 11.2.10.10 if you need one after the full update.
Click to expand...
Click to collapse
Edit: problem solved.
aTorda said:
Edit: problem solved.
Click to expand...
Click to collapse
If needed here is 11.2.10.10 magisked boot:
https://drive.google.com/file/d/1It8uS5kfWXK0Imhu1vX66jUBEMUlxqAh/view?usp=drivesdk
Porquiplane said:
If needed here is 11.2.10.10 magisked boot:
https://drive.google.com/file/d/1It8uS5kfWXK0Imhu1vX66jUBEMUlxqAh/view?usp=drivesdk
Click to expand...
Click to collapse
Thank you! I was going to ask you for a copy cuz I ran into error trying to extract from payload, but I figured out where I gone wrong and fixed it. Still thank you for offering much appreciated.
@Porquiplane
I have the same problem trying to update and I also have Arter R2 Kernel and Magisk. Could you explain to me how I do to update. Now I get an error.
Partigiano0105 said:
@Porquiplane
I have the same problem trying to update and I also have Arter R2 Kernel and Magisk. Could you explain to me how I do to update. Now I get an error.
Click to expand...
Click to collapse
4th post...
TheKnux said:
4th post...
Click to expand...
Click to collapse
and if i uninstall magisk. How do I root the phone back? I'm sorry I don't understand much of this
Partigiano0105 said:
and if i uninstall magisk. How do I root the phone back? I'm sorry I don't understand much of this
Click to expand...
Click to collapse
Patch the stock boot image using Magisk then flash the magisk_patched.img through fastboot.