Can someone please paste a link to the 11.0.4.4 global installation file. My Oneplus8 pro is rooted and as such I cannot download it from system updates. I tried to fastboot an unpatched boot but I couldn't get WiFi to turn on. Accordingly, I'd like an alternate download option for 11.0.4.4 global.
Being rooted should not prevent the update. Otherwise download "oxygen updater" from the play store.
shorty1993 said:
Being rooted should not prevent the update. Otherwise download "oxygen updater" from the play store.
Click to expand...
Click to collapse
In my experience being rooted does prevent updates especially if you've flashed the patched boot image to both slots. In the past I've had his name issue. I got the update to stick when I fastboot flash Boot the original stock boot Image.
Have not seen the full 11.0.4.4 global zip anywhere yet....
I uninstalled Magisk, took the update and then reinstalled Magisk before rebooting. Seems to have worked OK.
PieceKeepr said:
I uninstalled Magisk, took the update and then reinstalled Magisk before rebooting. Seems to have worked OK.
Click to expand...
Click to collapse
Tried that. No joy.
State.of.mind said:
In my experience being rooted does prevent updates especially if you've flashed the patched boot image to both slots. In the past I've had his name issue. I got the update to stick when I fastboot flash Boot the original stock boot Image.
Click to expand...
Click to collapse
I tried that, but when I did I couldn't get wifi enabled. I tried to download on cellular but it repeatedly failed. I rarely use cellular and I only have 2gb/mo. (If it were stable I'd be fine.)
shorty1993 said:
Being rooted should not prevent the update. Otherwise download "oxygen updater" from the play store.
Click to expand...
Click to collapse
Oxy updated still has 2 2 not 4.4
PieceKeepr said:
I uninstalled Magisk, took the update and then reinstalled Magisk before rebooting. Seems to have worked OK.
Click to expand...
Click to collapse
No joy.
I think I'll just live with 2.2 until oxy updated has 4.4. From what I've read 4.4 doesn't really do much. OnePlus sucks anymore.
PS I was finally able to download 2.2 again and I install it (via system update) which got rid of root so I downloaded and installed 4.4. Haven't rooted it yet.
almahix said:
PS I was finally able to download 2.2 again and I install it (via system update) which got rid of root so I downloaded and installed 4.4. Haven't rooted it yet.
Click to expand...
Click to collapse
Please post here if magisk worked on 4.4? And where did you get the stock boot.img?
following.
devsk said:
Please post here if magisk worked on 4.4? And where did you get the stock boot.img?
Click to expand...
Click to collapse
Yes Magisk works on 4.4. There's a 4.4 Boot image thread in the Guides. You should be able to find it
almahix said:
I think I'll just live with 2.2 until oxy updated has 4.4. From what I've read 4.4 doesn't really do much. OnePlus sucks anymore.
PS I was finally able to download 2.2 again and I install it (via system update) which got rid of root so I downloaded and installed 4.4. Haven't rooted it yet.
Click to expand...
Click to collapse
4.4 has improved my battery life somehow.. Seemingly a lot better than it was.
In regards to there updates, I'd say (if you're rooted or not) to use oxygen updater, it's an absolutely rock solid app.
Plus they tend to release way before OnePlus do for each device.
Installation isn't affected by root, simply disable your modules then when prompted to reboot just don't, click install to inactive slot and you're done.
If you've taken an incremental update then I couldn't help you, personally I'd only stick to full updates.
4.4 has definitely improved things for me.
I'm on BA /2023
dladz said:
4.4 has improved my battery life somehow.. Seemingly a lot better than it was.
In regards to there updates, I'd say (if you're rooted or not) to use oxygen updater, it's an absolutely rock solid app.
Plus they tend to release way before OnePlus do for each device.
Installation isn't affected by root, simply disable your modules then when prompted to reboot just don't, click install to inactive slot and you're done.
If you've taken an incremental update then I couldn't help you, personally I'd only stick to full updates.
4.4 has definitely improved things for me.
I'm on BA /2023
Click to expand...
Click to collapse
I like Oxygen Updater but it is still showing 2.2. I downloaded that 2.2 to get rid of root then was able to download 4.4 from system update, now I'm trying to root 4.4. Fastboot boot isn't working for me now for some reason. I'm not sure those downloads labeled 4.4, IN11AA (2020 global) are for real. If anyone has a file known to work on this variety please share a link.
almahix said:
I like Oxygen Updater but it is still showing 2.2. I downloaded that 2.2 to get rid of root then was able to download 4.4 from system update, now I'm trying to root 4.4. Fastboot boot isn't working for me now for some reason. I'm not sure those downloads labeled 4.4, IN11AA (2020 global) are for real. If anyone has a file known to work on this variety please share a link.
Click to expand...
Click to collapse
I have the BA model. So I can't help you there mate.
There were people flashing BA according to people in my thread, perhaps contact them via PM and see what they say.
Wasn't a big deal by all accounts.
11.0.4.4 available now via OnePlus site.
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
Oxygen updater finally has the 4.4 11 AA. I have payload dumped it and tried to patch the boot.img but magisk is failing. I cannot seem to get the canary channel so I'm using the latest beta but it isn't working. I cannot believe that nothing is working for me. Has anyone else succeeded?
almahix said:
Oxygen updater finally has the 4.4 11 AA. I have payload dumped it and tried to patch the boot.img but magisk is failing. I cannot seem to get the canary channel so I'm using the latest beta but it isn't working. I cannot believe that nothing is working for me. Has anyone else succeeded?
Click to expand...
Click to collapse
I've been on 11.0.4.4 for about a week now, but I did it using the OTA, not with the full upload. I've been doing it this way for a while, just like I did with my Pixel 2XL.
Anyway, I downloaded the full upload from OnePlus's page a few minutes ago to test it out, and I was able to patch the boot image after extracting it from the payload.bin using the latest beta magisk. I did it on my Pixel 2XL, that's really the only reason I keep that phone around now, besides it being a backup phone just in case my OP8P craps out.
bouchigo said:
I've been on 11.0.4.4 for about a week now, but I did it using the OTA, not with the full upload. I've been doing it this way for a while, just like I did with my Pixel 2XL.
Anyway, I downloaded the full upload from OnePlus's page a few minutes ago to test it out, and I was able to patch the boot image after extracting it from the payload.bin using the latest beta magisk. I did it on my Pixel 2XL, that's really the only reason I keep that phone around now, besides it being a backup phone just in case my OP8P craps out.
Click to expand...
Click to collapse
Great idea! I never thought of patching the stock boot.img on another device. It worked and now I'm finally rooted. Thank you for sharing your idea! BTW my former phone was a Pixel2XL. Was that the best phone ever? Still is but I sold it when I bought my 8pro. Big mistake!
Related
I rooted my device today and as expected, OTA updates aren't able to install naturally anymore. Following the advice of several netizens, I installed FlashFire. As instructed, I downloaded the OTA update and then opened FlashFire to install it from there.
But I am getting this error message, "A system update (OTA) has been detected, but the Update Engine binaries could not be extracted from boot/recovery. The update cannot be handled."
There is literally no information that I could dig up to solve this problem. Any ideas?
anirbannath said:
I rooted my device today and as expected, OTA updates aren't able to install naturally anymore. Following the advice of several netizens, I installed FlashFire. As instructed, I downloaded the OTA update and then opened FlashFire to install it from there.
But I am getting this error message, "A system update (OTA) has been detected, but the Update Engine binaries could not be extracted from boot/recovery. The update cannot be handled."
There is literally no information that I could dig up to solve this problem. Any ideas?
Click to expand...
Click to collapse
In A/B partition, the update installs on the other partition so that the one you're using still works and once the process completes you just need to reboot. Which is why you have to boot into the other partition by flashing twrp using fastboot mode and then download the updates. This will install the updates on your current partition which you've rooted and you will have to root again after updating.
myksh said:
In A/B partition, the update installs on the other partition so that the one you're using still works and once the process completes you just need to reboot. Which is why you have to boot into the other partition by flashing twrp using fastboot mode and then download the updates. This will install the updates on your current partition which you've rooted and you will have to root again after updating.
Click to expand...
Click to collapse
@myksh
You went a little farther than where I am stuck actually. I haven't gotten upto the point where I am given the option to reboot and apply update. I am sure you are aware - there is a two step installation process after the update is downloaded and before that reboot to apply button appears.
The problem is - I am stuck on the Step 1 of 2 part. Halfway through this step, Google Play Services stop working and the progress bar transforms into a fluid bar and this keeps happening over and over. It's a glitch, in short.
And so, that's why I had hoped to skip the hassle of direct OTA installation altogether by using FlashFire and let it do the work of handling the update. But then I get this stupid error.
If you know of a way I could flash the update from inside TWRP or something, by accessing the locally downloaded update files, then I'm all for it. But some people here have gone to the extent of reflashing entire ROMs (worth gigabytes) and then re-rooting the device just for a security patch. This seems like somewhat of an overkill method.
As for going into the other partition and installing from there, when I switch partitions, I see that I have to redownload the entire patch all over again. What's worse is that, my WiFi and Hotspot refuse to start in partition 'b' (weird glitch again), which is why partition 'a' and/or FlashFire is all I have got at the moment.
anirbannath said:
@myksh
You went a little farther than where I am stuck actually. I haven't gotten upto the point where I am given the option to reboot and apply update. I am sure you are aware - there is a two step installation process after the update is downloaded and before that reboot to apply button appears.
The problem is - I am stuck on the Step 1 of 2 part. Halfway through this step, Google Play Services stop working and the progress bar transforms into a fluid bar and this keeps happening over and over. It's a glitch, in short.
And so, that's why I had hoped to skip the hassle of direct OTA installation altogether by using FlashFire and let it do the work of handling the update. But then I get this stupid error.
If you know of a way I could flash the update from inside TWRP or something, by accessing the locally downloaded update files, then I'm all for it. But some people here have gone to the extent of reflashing entire ROMs (worth gigabytes) and then re-rooting the device just for a security patch. This seems like somewhat of an overkill method.
As for going into the other partition and installing from there, when I switch partitions, I see that I have to redownload the entire patch all over again. What's worse is that, my WiFi and Hotspot refuse to start in partition 'b' (weird glitch again), which is why partition 'a' and/or FlashFire is all I have got at the moment.
Click to expand...
Click to collapse
I was nowhere near you though. The security patch got downloaded but since I've rooted it, flashfire denied to help me out with the update. And so with a little help from this forum itself, I got to know that we'll have to start from the beginning and download both the security patches and install them while on partition 'b'.
This is just stupid as of now than convenient but unfortunately for now that's all we have in our hands. Devs are working hard for an alternate I'm sure, coz this A/B partition thing came from google(pixel) itself.
myksh said:
I was nowhere near you though. The security patch got downloaded but since I've rooted it, flashfire denied to help me out with the update. And so with a little help from this forum itself, I got to know that we'll have to start from the beginning and download both the security patches and install them while on partition 'b'.
This is just stupid as of now than convenient but unfortunately for now that's all we have in our hands. Devs are working hard for an alternate I'm sure, coz this A/B partition thing came from google(pixel) itself.
Click to expand...
Click to collapse
This is a little confusing though, what you said - isn't FlashFire a root app by nature? So how can it refuse to help you out after asking for the same permissions that it requires to run?
And yeah, I have come to that conclusion myself too. This may sound noobish but I couldn't exactly find the security patch for the October update of Mi A1 anywhere on the internet. Have you or anyone found it or do we have to wait?
And just to clarify - when you say download the security patches, you mean just the security patch itself as a 'zip' file or something like that, right? Not the entire ROM, I hope. As in, if I were to download the security patch file of the October update, it would be approximately a 118 MB file, right?
anirbannath said:
This is a little confusing though, what you said - isn't FlashFire a root app by nature? So how can it refuse to help you out after asking for the same permissions that it requires to run?
And yeah, I have come to that conclusion myself too. This may sound noobish but I couldn't exactly find the security patch for the October update of Mi A1 anywhere on the internet. Have you or anyone found it or do we have to wait?
And just to clarify - when you say download the security patches, you mean just the security patch itself as a 'zip' file or something like that, right? Not the entire ROM, I hope. As in, if I were to download the security patch file of the October update, it would be approximately a 118 MB file, right?
Click to expand...
Click to collapse
Umm, yes. I meant I got stuck and flashfire showed the same error you faced, find it attached below.
Also, yes that's what I meant by security patch but if you get into the other partition, which still will be on the August patch, you'll have to download the September patch(1+gb) and then the October one(118mb). If it doesn't work, you'll have to download the rom file from miui.com flash it and then update to October patch.
This A/B partitioning is nowhere near a feature but looks more like an extended road and a U turn to get back to the same place. Only the ones who wont root their phones will be happy.
Facing the same issue as you guys. I can live without the October patch for a while. What do you guys think? Will flashgire be updated to accommodate these updates in the future or will TWRP be the way to go?
when i try to update via settings it says installation error. looks like i will have to be on september patch for now. any other way to update?
Why don't you simply unroot, install the update and then root again ?
I did that way and only cost me a couple of minutes...
Minimum effort to reflash firmware to September, download October and reroot october: 45 mins
Not sure how you were able to do it that fast but I'll stay on September until something easier comes around
me also waiting solution for this problem
tonycapuozzo said:
Why don't you simply unroot, install the update and then root again ?
I did that way and only cost me a couple of minutes...
Click to expand...
Click to collapse
How did You unrooted ?By super su or something else?
rkview37 said:
How did You unrooted ?By super su or something else?
Click to expand...
Click to collapse
Flash the stock boot.img
Flashfire doesn't work with incremental updates you need to download the full update
Sent from my SHIELD Tablet K1 using Tapatalk
robgee789 said:
Flashfire doesn't work with incremental updates you need to download the full update
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
Just flashing boot image via flashfire, and wifi doesnt work anymore. Trying to flash with MiFlash and the last rom , getting an error.
How to return to stock rom?
Any help please...!!
ok now.A mistake in process...!!! :fingers-crossed:
Just announced. Android P beta is live. https://www.google.com/android/beta#devices
Just got the OTA on my Pixel XL on 8.1
I'm in if someone finds out how to root it. Or at least how we can install it via TWRP or adb. Looks promising. The IO Keynote is kinda fun. Hope more stuff would be "available now" instead of *soon or *this year...
Wondering if tethering goes through a provisioning check or if we need to wait for a root exploit first
beta wont install with custom kernel, uninstalled magisk, no TWRP, but download still wont start.
It will install over the Dev 1 preview. I unrooted, signed up for the beta and hit check for updates and it was there.
TonikJDK said:
It will install over the Dev 1 preview. I unrooted, signed up for the beta and hit check for updates and it was there.
Click to expand...
Click to collapse
Wait, what? So I just have to unroot with the magisk uninstaller via TWRP, then install the OTA, then root again? But will that work with an unlocked bootloader and TWRP installed?
I'm downloading now, but seems to be taking forever to download
paco8 said:
Wait, what? So I just have to unroot with the magisk uninstaller via TWRP, then install the OTA, then root again? But will that work with an unlocked bootloader and TWRP installed?
Click to expand...
Click to collapse
I just opened Magisk and had it uninstall itself, rebooted and then hit check for updates and it installed fine. It did fail before I uninstalled Magisk. I can't say for sure how it will be with TWRP installed, I don't do that.
TonikJDK said:
I just opened Magisk and had it uninstall itself, rebooted and then hit check for updates and it installed fine. It did fail before I uninstalled Magisk. I can't say for sure how it will be with TWRP installed, I don't do that.
Click to expand...
Click to collapse
Thanks dude! I guess I'll try it later maybe.
But then how do/did you root your phone if you don't use TWRP?
FYI, I have no wifi right now. It connects but 'no internet'. Working on it now.
Where's the new system navigation, dashboard and other features they just showed off?
c7j8d9 said:
Where's the new system navigation, dashboard and other features they just showed off?
Click to expand...
Click to collapse
Coming "soon"...
paco8 said:
Coming "soon"...
Click to expand...
Click to collapse
So they showed off the new features of Android P and released the beta with none of them?...typical. Is it any different than the dev preview? Now I'm stuck with this ugly UI and none of the features I was interested in.
For swipe navigation, you need to turn it on in "Gestures"
c7j8d9 said:
Where's the new system navigation, dashboard and other features they just showed off?
Click to expand...
Click to collapse
Sent from my Pixel XL using Tapatalk
paco8 said:
Thanks dude! I guess I'll try it later maybe.
But then how do/did you root your phone if you don't use TWRP?
Click to expand...
Click to collapse
I fastboot boot it and install the Magisk zip, and don't install the TWRP zip.
Found my WiFi problem. I was using Private DNS, looks like it is broke on Preview 2.
c7j8d9 said:
So they showed off the new features of Android P and released the beta with none of them?...typical. Is it any different than the dev preview?
Click to expand...
Click to collapse
Sorry, can't tell you that since I am waiting for someone kind enough to provide instructions on how to install this with an unlocked bootloader/twrp/magisk. But since full image downloads for this DP2 are not live yet, as far as I know at least, I guess I'll have to wait some more.
And yeah, I feel like they used to show more new stuff "out now" in previous years. But the last few times they announced a whole lot of stuff coming *soon, over the next weeks, months, summer, fall, or whenever. It used to be way more fun for me to get a "new version of Android every year with lots of new features" instead of this gradual roll-out of features. At least that's my opinion.
perfoliate said:
For swipe navigation, you need to turn it on in "Gestures"
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
your talking about swiping the fingerprint? that's not new
Aerys said:
Just got the OTA on my Pixel XL on 8.1
Click to expand...
Click to collapse
Android P or May?
ymmv, but I was on 8.1 April with twrp/mag16.3. Opted into Beta program and P-dp2 ota downloaded and installed without removing magisk. Note that I had not made any build.prop changes etc.
Once on dp2, fastbooted twrp, reboot recovery- installed full twrp, rebooted recovery -installed full magisk16.4. Magisk rooted fine and tether enabler module seems to work.
paco8 said:
Sorry, can't tell you that since I am waiting for someone kind enough to provide instructions on how to install this with an unlocked bootloader/twrp/magisk. But since full image downloads for this DP2 are not live yet, as far as I know at least, I guess I'll have to wait some more.
And yeah, I feel like they used to show more new stuff "out now" in previous years. But the last few times they announced a whole lot of stuff coming *soon, over the next weeks, months, summer, fall, or whenever. It used to be way more fun for me to get a "new version of Android every year with lots of new features" instead of this gradual roll-out of features. At least that's my opinion.
Click to expand...
Click to collapse
You can grab the original preview image, edit out the -w in the flash all bat file and flash it. Then sign up for the Beta and grab the OTA. Then reroot.
FYI
Factory images:
https://developers.google.com/android/images
OTA:
https://developers.google.com/android/ota
Just finished installing a Pixel and a PIxel XL with no issues. Used flash-all (deleted the -w), fastboot boot TWRP (decrypt worked) but not permanent install, Magisk 16.0 rooted. All pretty seamless this month. No change to platform-tools since December.
sliding_billy said:
Just finished installing a Pixel and a PIxel XL with no issues. Used flash-all (deleted the -w), fastboot boot TWRP (decrypt worked) but not permanent install, Magisk 16.0 rooted. All pretty seamless this month. No change to platform-tools since December.
Click to expand...
Click to collapse
I just completed the same process and can confirm all is well. Will report back on if I notice any improvements/differences.
Anyone having problems with their microphone after updating to the June Patch? Mine no longer works.
UPDATE: Turns out it was an issue with my custom kernel. A fix was already pushed down by the dev.
Alcolawl said:
Anyone having problems with their microphone after updating to the June Patch? Mine no longer works.
Click to expand...
Click to collapse
Phone calls have been fine for me.
sliding_billy said:
Phone calls have been fine for me.
Click to expand...
Click to collapse
No issues. I've made and received several calls since I updated yesterday evening. No one reported any issues hearing me. I also just tested via Sound Recorder app and audio was recorded and played back without issue.
sliding_billy said:
Phone calls have been fine for me.
Click to expand...
Click to collapse
sb1893 said:
No issues. I've made and received several calls since I updated yesterday evening. No one reported any issues hearing me. I also just tested via Sound Recorder app and audio was recorded and played back without issue.
Click to expand...
Click to collapse
Appreciate the swift feedback, fellas. Turns out it was the custom kernel I had flashed after the update. The dev pushed out a fix minutes after I posted here lol. Thanks!
I read numerous complaints on Google's issue tracker site about how unlocking the phone takes longer on Pixel 2 after the June update than before. Both the power button and fingerprint scanner are delayed. Can anyone chime in on this please?
https://issuetracker.google.com/issues/109710373
Carrzy said:
I read numerous complaints on Google's issue tracker site about how unlocking the phone takes longer on Pixel 2 after the June update than before. Both the power button and fingerprint scanner are delayed. Can anyone chime in on this please?
https://issuetracker.google.com/issues/109710373
Click to expand...
Click to collapse
Not seeing any difference or delay at all on the OG Pixel XL...still as speedy as ever....
Anyone else notice the difference in the June images ?
EDIT : NEVERMIND . I downloaded the wrong images apparently ............. Lol .
Sent from my Pixel XL using Tapatalk
This can't be normal right? Trying to flash the factory image from scratch...
EDIT: Fixed by updating my ADB and Fastboot to the latest google provides.
Carrzy said:
I read numerous complaints on Google's issue tracker site about how unlocking the phone takes longer on Pixel 2 after the June update than before. Both the power button and fingerprint scanner are delayed. Can anyone chime in on this please?
https://issuetracker.google.com/issues/109710373
Click to expand...
Click to collapse
I read those too. Weird. No difference in speed here. Still nearly instant.
I just got my pixel xl , and for the may update i did a adb sideload fastboot twrp rooted, . Is flash- all with -w deleted the same as a ota or well i need to well i need to set up the phone all over again. Just wondering ,
brightjh01 said:
I just got my pixel xl , and for the may update i did a adb sideload fastboot twrp rooted, . Is flash- all with -w deleted the same as a ota or well i need to well i need to set up the phone all over again. Just wondering ,
Click to expand...
Click to collapse
flash-all with -w deleted will save your data. You will not have to set up your phone 'all over again'
I know I can dl this and do it manually, and I shall do (I have done for several years now), but how the f is my non-google essential ph1 receiving the update notification for June OTA before my PXL?!? This has been constant since I got the ph1in April.
It seems the whole "quickest" update pull for ElGoog devices no longer has any real point.
Any noticeable improvement with this update?
Homeboy76 said:
flash-all with -w deleted will save your data. You will not have to set up your phone 'all over again'
Click to expand...
Click to collapse
Hi. I'm running stock rom, rooted with magisk, TWRP permanently installed. I used to flash repackaged OTAs using TWRP on my Nexus 6. Is that no longer a 'thing' for the Pixel phones?
Assuming that there are no TWRP flashable OTA updates, then what I'm hoping for is a set of detailed (idiot-proof) instructions for updating to the June OTA ... ideally with an explanation about what I will have to re-do after installing the update (will I have to reinstall TWRP, Magisk?).
Thanks to anyone who can point me in the right direction. :good:
demlv said:
Hi. I'm running stock rom, rooted with magisk, TWRP permanently installed. I used to flash repackaged OTAs using TWRP on my Nexus 6. Is that no longer a 'thing' for the Pixel phones?
Assuming that there are no TWRP flashable OTA updates, then what I'm hoping for is a set of detailed (idiot-proof) instructions for updating to the June OTA ... ideally with an explanation about what I will have to re-do after installing the update (will I have to reinstall TWRP, Magisk?).
Thanks to anyone who can point me in the right direction. :good:
Click to expand...
Click to collapse
Step-by-step instructions for the Pixel/Pixel XL are on this thread: [Guide] Pixel XL Android 8.1.0 (OREO) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + June Security Patch
Read them: #4 and #7 for answer(s) to your question(s)
Do them: Do #4 Keep Data (4.1.) to update firmware, then do # 7 to root/reroot.
Homeboy76 said:
Step-by-step instructions for the Pixel/Pixel XL are on this thread: [Guide] Pixel XL Android 8.1.0 (OREO) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + June Security Patch
Read them: #4 and #7 for answer(s) to your question(s)
Do them: Do #4 Keep Data (4.1.) to update firmware, then do # 7 to root/reroot.
Click to expand...
Click to collapse
Noob here. I had been using Nexus 5x and I just receive the Pixel XL recently. I have followed the guide post above. Just wanna make sure something:
1. If I wanna update and keep data, why not adb sideload OTA instead of fastboot factory image?
2. If I unlock bootloader with stock recovery and root with Magisk, can I still get OTA update?
3. Do I need to reroot every time after update?
thanks
digimon04 said:
Noob here. I had been using Nexus 5x and I just receive the Pixel XL recently. I have followed the guide post above. Just wanna make sure something:
1. If I wanna update and keep data, why not adb sideload OTA instead of fastboot factory image?
2. If I unlock bootloader with stock recovery and root with Magisk, can I still get OTA update?
3. Do I need to reroot every time after update?
thanks
Click to expand...
Click to collapse
1. You could side load the OTA then Fastboot twrp.img, flash twrp.zip, and flash Magisk.
2. I don't think so. Note: Once you unlock the boot loader DO NOT lock it until you have completed #3 B.
3. Yes
The reason I suggest Do #4 Keep Data to install factory image (I think it is simpler), then Do #7 to Root
Hi XDA community,
I will receive my new OnePlus Pro 8 tomorrow.
This will be my first OnePlus phone and it will likely be the North American version.
Primarily, I would like to unlock the bootloader and root the phone, additionally also have the Dual-sim functionality enabled.
I don't have a lot of experience with rooting, but can follow steps and instructions
1) Should I start the new phone let it update all the way to oxygen OS 11 and than follow steps to unlock the bootloader and root the phone and than transfer my data? - Will this process be more complicated than doing it with Oxygen OS 10.?
2) Once the phone is rooted, can I transfer data from my old phone through the USB/Phone/data transfer apps so it gets setup automagically ?
3) Does TWRP work with OS 11 ? if not is there an update schedule for it?
4) Does Dual Sim for NA phones work with Oxygen OS 10 or is it enabled only at Oxygen OS 11 ?
Any things else that I should be aware of? (this process or the phone in general as well?)
Thank you all
DV
Peace.
dvartak said:
Hi XDA community,
I will receive my new OnePlus Pro 8 tomorrow.
This will be my first OnePlus phone and it will likely be the North American version.
Primarily, I would like to unlock the bootloader and root the phone, additionally also have the Dual-sim functionality enabled.
I don't have a lot of experience with rooting, but can follow steps and instructions
1) Should I start the new phone let it update all the way to oxygen OS 11 and than follow steps to unlock the bootloader and root the phone and than transfer my data? - Will this process be more complicated than doing it with Oxygen OS 10.?
2) Once the phone is rooted, can I transfer data from my old phone through the USB/Phone/data transfer apps so it gets setup automagically ?
3) Does TWRP work with OS 11 ? if not is there an update schedule for it?
4) Does Dual Sim for NA phones work with Oxygen OS 10 or is it enabled only at Oxygen OS 11 ?
Any things else that I should be aware of? (this process or the phone in general as well?)
Thank you all
DV
Peace.
Click to expand...
Click to collapse
1. I would prefer to unlock the phone first and than boot twrp and flash magisk. After you got root update the system and install magisk to inactiv slot.
2. I don't know.
3. Nope.
4. Should also work with OOS 10.
Thank you for your reply..
Kollachi said:
1. I would prefer to unlock the phone first and than boot twrp and flash magisk. After you got root update the system and install magisk to inactiv slot.
2. I don't know.
3. Nope.
4. Should also work with OOS 10.
Click to expand...
Click to collapse
Thanks for your reply
Is there a forum thread for how I can unlock the bootloader and to perform root, the XDA forum threads while very resourceful are a bit overwhelming as there seem to be multiple methods of achieving root.
I am not planning on installing customROMS as yet, just want the phone to be unlocked and so I can enable the colour filter, installing gcam etc for now.
Cheers,
DV
dvartak said:
Thanks for your reply
Is there a forum thread for how I can unlock the bootloader and to perform root, the XDA forum threads while very resourceful are a bit overwhelming as there seem to be multiple methods of achieving root.
I am not planning on installing customROMS as yet, just want the phone to be unlocked and so I can enable the colour filter, installing gcam etc for now.
Cheers,
DV
Click to expand...
Click to collapse
I have a couple in the guides section..have a look. So long as you follow it correctly you should be fine.
One for the bootloader.
One for updating, rooting and payload dumper.
A few more questions...
dladz said:
I have a couple in the guides section...have a look. So long as you follow it correctly you should be fine.
One for the bootloader.
One for updating, rooting and payload dumper.
Click to expand...
Click to collapse
Do you mind pasting the links here, I have managed to get the bootloader unlocked using fastboot.
(NVM, I think I found your threads oneplus-8-pro/how-to/root-uk-eu-patched-magisk-boot-img-t4175033 & )
My model is IN2025
OS: 10.5.10.IN11AA
I wanted to know,
1) OxyOS updater is prompting that there is an update to Oxygen OS 11.IN11AA
Can I update to OxyOS 11 and still keep the bootloader unlocked ?
"It displays that OEM unlock is detected, system will download the full upgrade package, please backup data...etc."
2) Should I root my phone now and later will I be able to upgrade / flash to Oxygen OS 11 ? -North-American market requires OS 11 for dual sim
Where can I find the appropriate files to get make a 'patch' using payload for this version (10.5.10.IN11AA) ?
Thank you
dvartak said:
Do you mind pasting the links here, I have managed to get the bootloader unlocked using fastboot.
(NVM, I think I found your threads oneplus-8-pro/how-to/root-uk-eu-patched-magisk-boot-img-t4175033 & )
My model is IN2025
OS: 10.5.10.IN11AA
I wanted to know,
1) OxyOS updater is prompting that there is an update to Oxygen OS 11.IN11AA
Can I update to OxyOS 11 and still keep the bootloader unlocked ?
"It displays that OEM unlock is detected, system will download the full upgrade package, please backup data...etc."
2) Should I root my phone now and later will I be able to upgrade / flash to Oxygen OS 11 ? -North-American market requires OS 11 for dual sim
Where can I find the appropriate files to get make a 'patch' using payload for this version (10.5.10.IN11AA) ?
Thank you
Click to expand...
Click to collapse
Yes you can
Yes that's fine
Easiest way is whatever you like .
You can either root now then take the update and then OTA install magisk patched or just boot the magisk patched after and then directly install
Sorry, I still have some more questions..
dladz said:
Yes you can
Yes that's fine
Easiest way is whatever you like .
You can either root now then take the update and then OTA install magisk patched or just boot the magisk patched after and then directly install
Click to expand...
Click to collapse
I updated to OS11.IN11AA to enable Dual Sim first.
I guess I can try rooting now. Sorry I still have a few queries:
1)
In your instructions you suggest extracting 'your own' boot.img using the payload_dumper.
My phone (thanks to the OEM unlock) has downloaded a large 2GB+ zip file on the phone, should I use that payload.bin to extract the boot.img
or
the one on the oneplus website will work as well? - They appear to be the same but would like to know if there is a difference.
From the oneplus Website: OnePlus8ProOxygen_15.O.30_OTA_0300_all_2010031617_2198430880804411.zip
From the phone: OnePlus8ProOxygen_15.O.30_OTA_0300_all_2010031617_f9ca0bfd1b.zip
2)
I installed MagiskManager from the link in your thread (Preferred magisk manager- https://mega.nz/file/LU9U3aSC#EFJTOK...ejzi-VyUa3nQq8)
There weren't any updates till I selected the stable channel and than canary again. I have installed the whatever updates, it showed:
It now reads:
Magisk (latest): 1469b82a
Installed: N/A <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Why does it show N/A ?, will this change after the rooting process ?
Ramdisk: Yes
A/B: yes
SAR: yes
Crypto: File
Manager (latest) 1469b82a(315)(14)
installed: 1469b82a(315)
Does this seem correct?
You have been really awesome !
Cheers,
DV
dvartak said:
I updated to OS11.IN11AA to enable Dual Sim first.
I guess I can try rooting now. Sorry I still have a few queries:
1)
In your instructions you suggest extracting 'your own' boot.img using the payload_dumper.
My phone (thanks to the OEM unlock) has downloaded a large 2GB+ zip file on the phone, should I use that payload.bin to extract the boot.img
or
the one on the oneplus website will work as well? - They appear to be the same but would like to know if there is a difference.
From the oneplus Website: OnePlus8ProOxygen_15.O.30_OTA_0300_all_2010031617_2198430880804411.zip
From the phone: OnePlus8ProOxygen_15.O.30_OTA_0300_all_2010031617_f9ca0bfd1b.zip
2)
I installed MagiskManager from the link in your thread (Preferred magisk manager- https://mega.nz/file/LU9U3aSC#EFJTOK...ejzi-VyUa3nQq8)
There weren't any updates till I selected the stable channel and than canary again. I have installed the whatever updates, it showed:
It now reads:
Magisk (latest): 1469b82a
Installed: N/A <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Why does it show N/A ?, will this change after the rooting process ?
Ramdisk: Yes
A/B: yes
SAR: yes
Crypto: File
Manager (latest) 1469b82a(315)(14)
installed: 1469b82a(315)
Does this seem correct?
You have been really awesome !
Cheers,
DV
Click to expand...
Click to collapse
Hey,
1.) Yep that's absolutely fine, I tend to use oxygen updater as it's been absolutely flawless up until now and it won't allow you to download a firmware not compatible with your device.
Wherever you choose the numbers you've shown seem good to me, but id I had to choose I'd go with oxygen updater.
2.) Some people have had a lot more luck with the beta channel, so long as you have the install/update buttons then you're ready to patch the boot.img and go ahead and boot it using Fastboot.
Don't worry about N/A that just states that magisk_patched isn't there yet, which is normal.
So at this point, you're welcome to stick with stable but I couldn't recommend it as I've not done this myself, I've only had luck with canary but others have had luck with beta.. I'd recommend one of them channels, changing back to canary may now show the buttons that were missing..
If not then beta.
There are some troubleshooting steps at the end of the guides at the bottom. As well as all the files which I used.
Let me know how you get on
dladz said:
Hey,
2.) Some people have had a lot more luck with the beta channel, so long as you have the install/update buttons then you're ready to patch the boot.img and go ahead and boot it using Fastboot.
Don't worry about N/A that just states that magisk_patched isn't there yet, which is normal.
So at this point, you're welcome to stick with stable but I couldn't recommend it as I've not done this myself, I've only had luck with canary but others have had luck with beta.. I'd recommend one of them channels, changing back to canary may now show the buttons that were missing..
If not then beta.
There are some troubleshooting steps at the end of the guides at the bottom. As well as all the files which I used.
Let me know how you get on
Click to expand...
Click to collapse
Thanks again for all your help!
So I believe, the channel display when first opened did not show any install / update buttons but the settings showed channel: Canary.
I believe I switched to stable and the buttons showed up (i did not install than), after which I switched channels to canary and than installed.
When I search for the "1469b82a" and magisk it shows this as a Update to Canary channel (3days ago) https://github.com/topjohnwu/magisk_files/blob/canary/notes.md
I hope I am on the right track..
-------------------------------
UPDATE: So I think it has worked,
It seems I am rooted now, I have installed Titanium and bunch of other stuff that needs root.
(but I think I may have goofed up and ended up mixing your two solutions)
It was installed in 'b - drive/section'.
fastboot flash boot magisk_patched.img <(This is different from your step 4, where you do fastboot boot magisk_patched)
(I am hoping this did not goof things up, I misread )
It flashed just on 'b' - drive.
I did not flash in both 'a' and 'b'.
I also did'
"
5. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings.
6. Select Direct install (recommended)
"
When I open Magisk Manager now, I see installed 1469b82a (21101) < same as the latest
I also have the "Uninstall Magisk button" showing which wasn't before. and settings shows me many more options (super user, magisk hide etc.)
2) Also what does Magisk hide do?,
> I have read many bank apps wont install due to rooting, will that help?
Thanks for being so patient and answering all questions !
dvartak said:
Thanks again for all your help!
So I believe, the channel display when first opened did not show any install / update buttons but the settings showed channel: Canary.
I believe I switched to stable and the buttons showed up (i did not install than), after which I switched channels to canary and than installed.
When I search for the "1469b82a" and magisk it shows this as a Update to Canary channel (3days ago) https://github.com/topjohnwu/magisk_files/blob/canary/notes.md
I hope I am on the right track..
-------------------------------
UPDATE: So I think it has worked,
It seems I am rooted now, I have installed Titanium and bunch of other stuff that needs root.
(but I think I may have goofed up and ended up mixing your two solutions)
It was installed in 'b - drive/section'.
fastboot flash boot magisk_patched.img <(This is different from your step 4, where you do fastboot boot magisk_patched)
(I am hoping this did not goof things up, I misread )
It flashed just on 'b' - drive.
I did not flash in both 'a' and 'b'.
I also did'
"
5. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings.
6. Select Direct install (recommended)
"
When I open Magisk Manager now, I see installed 1469b82a (21101) < same as the latest
I also have the "Uninstall Magisk button" showing which wasn't before. and settings shows me many more options (super user, magisk hide etc.)
2) Also what does Magisk hide do?,
> I have read many bank apps wont install due to rooting, will that help?
Thanks for being so patient and answering all questions !
Click to expand...
Click to collapse
That's ok you just flashed it twice.
Reason for the boot and not flash is due to the fact that boot images can always go wrong,, bad copy or just corruption. But if you're rooted then you're all good
Magisk hide attempts to hide itself from apps that works otherwise detect it, meaning you can go ahead and use Google pay our your banking apps.
In theory anyway, but some apps have other ways of detecting root and thus it won't work.
Up until now I've been ok.
I see..
Ah I see, Thanks again. Google pay complains about root, but my other Bank apps seem fine so far. I'll try my luck with hide magisk.
I suppose next time the phone updates, I will lose root as the active partition will switch ?
The only odd thing that has happened is the I have an extra/duplicate icon for the Android Files App. I don't know how to get rid of it...but it's not a big issue.
Thanks again for your help!
Cheers,
DV
dvartak said:
Ah I see, Thanks again. Google pay complains about root, but my other Bank apps seem fine so far. I'll try my luck with hide magisk.
I suppose next time the phone updates, I will lose root as the active partition will switch ?
The only odd thing that has happened is the I have an extra/duplicate icon for the Android Files App. I don't know how to get rid of it...but it's not a big issue.
Thanks again for your help!
Cheers,
DV
Click to expand...
Click to collapse
Change to systemless and turn on magisk hide
dladz said:
Change to systemless and turn on magisk hide
Click to expand...
Click to collapse
remember to backup persist partition. i just got my oneplus 8 pro as well. it has a great deal for Black Friday in US.
dlhxr said:
remember to backup persist partition. i just got my oneplus 8 pro as well. it has a great deal for Black Friday in US.
Click to expand...
Click to collapse
How do I backup persist partition?, Will Titanium backup help or something else ?
I am new to the whole rooting thing.
dlhxr said:
remember to backup persist partition. i just got my oneplus 8 pro as well. it has a great deal for Black Friday in US.
Click to expand...
Click to collapse
Me? I have pal
Hello. I've been snooping this forum for a while, and so i rooted my Nothing Phone 1. However it was back when 1.1.0 was a thing and didn't update to newer versions (mainly because of it's reviews). However recently i've been hearing positive feedback on 1.1.3 version and so i decided to give it a shot. But how could i do such thing if i'm rooted?
I know i would soft-brick my device if i would let OTA pass and install. This way i would probably need a full OTA rom and flash it manually somehow. Also, if someone know, downgrade guide would be awesome too (in case i will have issues with the new update).
Pheggas said:
Hello. I've been snooping this forum for a while, and so i rooted my Nothing Phone 1. However it was back when 1.1.0 was a thing and didn't update to newer versions (mainly because of it's reviews). However recently i've been hearing positive feedback on 1.1.3 version and so i decided to give it a shot. But how could i do such thing if i'm rooted?
I know i would soft-brick my device if i would let OTA pass and install. This way i would probably need a full OTA rom and flash it manually somehow. Also, if someone know, downgrade guide would be awesome too (in case i will have issues with the new update).
Click to expand...
Click to collapse
You will have this tuto if you want to update by Sideload the OTA zip
[GUIDE][HowTo]Pushing an OTA.zip Update with ADB Sideload - Updated 26-07-2022
Can't help you unfortunately, but let me know, after you manage, if your vibration intensity went down at all after the update or if it's all just my brain playing tricks on me.
FWIW, I don't have any issues with the latest version, except maybe lower vibration intensity, though that might just be because I started wearing a case more often.
Also the updates apparently have different features in different regions (for example, EEA had optimized battery ever since I first received the phone with version 1.1.2). They don't document the differences so it's possible other regions are buggy-er
This is how I managed to update a rooted Nothing Phone 1 (EU).
1. Disable all Magisk modules.
2. Restore images in Magisk
3. Install the OTA update through Updater in settings. Do NOT reboot when finished.
4. Install to inactive slot in Magisk
5. When that is finished, reboot. Done!
Pheggas said:
Hello. I've been snooping this forum for a while, and so i rooted my Nothing Phone 1. However it was back when 1.1.0 was a thing and didn't update to newer versions (mainly because of it's reviews). However recently i've been hearing positive feedback on 1.1.3 version and so i decided to give it a shot. But how could i do such thing if i'm rooted?
I know i would soft-brick my device if i would let OTA pass and install. This way i would probably need a full OTA rom and flash it manually somehow. Also, if someone know, downgrade guide would be awesome too (in case i will have issues with the new update).
Click to expand...
Click to collapse
Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with the Phone(1)...
forum.xda-developers.com
Add offlineOTAUpgrade from activities tab (like nova launcher), and download the full rom, simply update, and unfortunately it reboots before magisk can install to unused slot, so Fastboot boot rooted boot img and do a full install
Pho3nX said:
Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with the Phone(1)...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you. Unfortunately, that guide is missing all the commands and clearness.
Pheggas said:
Thank you. Unfortunately, that guide is missing all the commands and clearness.
Click to expand...
Click to collapse
There only one command "for update from root" and you can't be more clear in the step lol
So it's normal to don't found "all the commands" because there only one command to enter.
If you search a guide for root the first time, it's exactly the same thing but first your bootloader must be unlocked (all your date will be erased)
What is your problem ? Where are you blocked ?
Pho3nX said:
There only one command "for update from root" and you can't be more clear in the step lol
So it's normal to don't found "all the commands" because there only one command to enter.
If you search a guide for root the first time, it's exactly the same thing but first your bootloader must be unlocked (all your date will be erased)
What is your problem ? Where are you blocked ?
Click to expand...
Click to collapse
Hi @Pho3nX (and @Pheggas )
It's the same "my" problem...
I'd like to update me NP1 (rooted), waiting next custom roms that unfortunately are not ready
I'm not so smart with modding and we appreciate some detailed info/guide, step by step, with full commands to write, avoiding dangerous bricks...
I've stored in a folder my first boot.img and the magisk.img but I'm afraid to do some mistake with CMD strings...
Thanks for Your cooperation and... patience...
Ciao
notexcited said:
This is how I managed to update a rooted Nothing Phone 1 (EU).
1. Disable all Magisk modules.
2. Restore images in Magisk
3. Install the OTA update through Updater in settings. Do NOT reboot when finished.
4. Install to inactive slot in Magisk
5. When that is finished, reboot. Done!
Click to expand...
Click to collapse
this worked great for me the last few times, but this method no longer works for me after I installed version 1.1.4. can someone help me?
+1 for a detailed list of possible methods to update when rooted.
Sib64 said:
You will have this tuto if you want to update by Sideload the OTA zip
[GUIDE][HowTo]Pushing an OTA.zip Update with ADB Sideload - Updated 26-07-2022
Click to expand...
Click to collapse
But i shouldn't update with OTA packages when i'm rooted. There's risk of brick and tutorials on any device guides to update via flashing full package.
Pheggas said:
But i shouldn't update with OTA packages when i'm rooted. There's risk of brick and tutorials on any device guides to update via flashing full package.
Click to expand...
Click to collapse
Wait for full package and follow the same tutorial