update 10.0.31.... out

[lendawg]

One thing I've noticed already on this update is idle battery drain with 5G enabled (connected or not) has improved dramatically.

I would suggest that anyone who re-roots after makes sure to use a freshly patched kernel pulled after the update.

Yes I just turned on 5g to see if it had gotten better and you're right. My device isn't getting warm from it anymore either this is awesome!

 

[gaww]

Will this cause a wipe ? If so, will wait for a bigger update.

I can't locate the reserve.img you are referring to.

 

[gaww]

It's very simple, and the script does most of the work. All you have to do is hit Enter a few times, and let it run.

Back up your data to be safe, and worse case scenario, there is an MSM tool available that will restore the phone to stock.

I cannot find the newer reserve.img you referred to.

 

[gaww]

I have given up on trying to get this done. I went back to the platform tools zip and set it up, but then ran into the "ABD no devices/emulators found" error. I am beginning to hate this OnePlus bullshit, which are making things harder then just about any other brand. Will live with #27 in the meantime.

 

[NotATreoFan]

I have given up on trying to get this done. I went back to the platform tools zip and set it up, but then ran into the "ABD no devices/emulators found" error. I am beginning to hate this OnePlus bullshit, which are making things harder then just about any other brand. Will live with #27 in the meantime.

If you type "adb devices" and get no devices found, then you either don't have OnePlus drivers installed, or you don't have USB Debugging enabled.

Bonus tip to make it easier: Once you have ADB files extracted to a folder, add it to PATH in Win10. That will allow ADB commands to work no matter what directory the CMD prompt is in. Here is what mine looks like.

 

[Juxto2010]

I had trouble with root at first but got it. My 4G is still way more reliable than 5G.

 

[js042507]

Ok, so why can't we take the OTA if rooted and restore images from magisk?? Did anyone successfully update and re-root without msm tool or a full unroot? I also have the latest reserve.img. Also, I have been able to OTA update in all recent versions without any issues and being rooted. Just curious what changed.

EDIT: Nevermind. I think I see what happened. Looks like the reserve.img file changed with the .27 update. I never changed mine since a few updates ago. I assumed it was updating on its own. Makes sense because the kernel (boot.img) did change for the first time with the .27 update. I'll try updating tomorrow with the correct reserve.img in place.

EDIT #2: Well, that "new" reserve.img file I downloaded appears to be the same exact one I already have sitting in my /data/reserve folder. Meh. I guess we shall see what happens later. LOL

 

[adit07]

Ok, so why can't we take the OTA if rooted and restore images from magisk?? Did anyone successfully update and re-root without msm tool or a full unroot? I also have the latest reserve.img. Also, I have been able to OTA update in all recent versions without any issues and being rooted. Just curious what changed.

EDIT: Nevermind. I think I see what happened. Looks like the reserve.img file changed with the .27 update. I never changed mine since a few updates ago. I assumed it was updating on its own. Makes sense because the kernel (boot.img) did change for the first time with the .27 update. I'll try updating tomorrow with the correct reserve.img in place.

EDIT #2: Well, that "new" reserve.img file I downloaded appears to be the same exact one I already have sitting in my /data/reserve folder. Meh. I guess we shall see what happens later. LOL

Yes I did. You unroot and restore old images in magisk then reboot, take the ota, then re root.. have been doing it since .16

 

[NotATreoFan]

Ok, so why can't we take the OTA if rooted and restore images from magisk?? Did anyone successfully update and re-root without msm tool or a full unroot? I also have the latest reserve.img. Also, I have been able to OTA update in all recent versions without any issues and being rooted. Just curious what changed.

EDIT: Nevermind. I think I see what happened. Looks like the reserve.img file changed with the .27 update. I never changed mine since a few updates ago. I assumed it was updating on its own. Makes sense because the kernel (boot.img) did change for the first time with the .27 update. I'll try updating tomorrow with the correct reserve.img in place.

EDIT #2: Well, that "new" reserve.img file I downloaded appears to be the same exact one I already have sitting in my /data/reserve folder. Meh. I guess we shall see what happens later. LOL

I restored the one from the first post in the repair thread, and no dice. Restored the one someone posted deeper in the thread, and it worked perfectly. I unrooted just because it's easy enough to root again, and I wanted to make sure I had the newest kernel to pull and inject root back into.

 

[gaww]

If you type "adb devices" and get no devices found, then you either don't have OnePlus drivers installed, or you don't have USB Debugging enabled.

Bonus tip to make it easier: Once you have ADB files extracted to a folder, add it to PATH in Win10. That will allow ADB commands to work no matter what directory the CMD prompt is in. Here is what mine looks like.

I got past it, but then another ADB issue popped up - something about # 39 vs # 41. I hadn't touched fastboot or ADB for years....

 

[gaww]

I restored the one from the first post in the repair thread, and no dice. Restored the one someone posted deeper in the thread, and it worked perfectly. I unrooted just because it's easy enough to root again, and I wanted to make sure I had the newest kernel to pull and inject root back into.

Do we need more software than the reserve.img thing - doing the unrooting and rerooting manually ?

Also, I have not been able to find the newer one.

 

[js042507]

Yes I did. You unroot and restore old images in magisk then reboot, take the ota, then re root.. have been doing it since .16

Yeah, I have updated since this phone came out using the 'restore images' option, without even rebooting...and the OTA has always worked. Not anymore. I think it has something to do with my boot.img. I just spent the last hour fixing my kernel, as magisk wouldn't even root properly with my patched .img. UGH. Anyhow, I did use the reserve.img file in that post and it did not work. Now that I'm fixed up, I'll try to update again soon.

 

[gaww]

Yeah, I have updated since this phone came out using the 'restore images' option, without even rebooting...and the OTA has always worked. Not anymore. I think it has something to do with my boot.img. I just spent the last hour fixing my kernel, as magisk wouldn't even root properly with my patched .img. UGH. Anyhow, I did use the reserve.img file in that post and it did not work. Now that I'm fixed up, I'll try to update again soon.

I meant to ask you this:

Do we need more software than the reserve.img thing - doing the unrooting and rerooting manually ?

Also, I have not been able to find the newer one. It looks like everything else right now would be a WOT without it.

 

[js042507]

I meant to ask you this:

Do we need more software than the reserve.img thing - doing the unrooting and rerooting manually ?

Also, I have not been able to find the newer one. It looks like everything else right now would be a WOT without it.

Yeah I'm not sure. In ALL recent updates, I have only needed to go into magisk and choose uninstall --> restore images...then install the OTA. It updates, and then I patch my boot.img, boot from it, and install magisk again. A few updates back, I did restore the reserve.img file...but never needed to change it again.

 

[gaww]

Yeah I'm not sure. In ALL recent updates, I have only needed to go into magisk and choose uninstall --> restore images...then install the OTA. It updates, and then I patch my boot.img, boot from it, and install magisk again. A few updates back, I did restore the reserve.img file...but never needed to change it again.

Ok - let us know when you get 10.0.31 up.

 

[ohap]

N41 is enabled now on .31

 

[champ784]

N41 is enabled now on .31

Doesn't surprise me now that the merger went through and T-Mobile is working on utilizing the new 5G frequencies and bands

 

[Joe199799]

So what are the steps to update I'm still on .19

Restore images
Take the OTA
Reinstall magisk

Or am I missing something

 

[NotATreoFan]

So what are the steps to update I'm still on .19

Restore images
Take the OTA
Reinstall magisk

Or am I missing something

Restore userdata, unroot, uninstall Magisk, take OTA.

Be sure to pull a new copy of the kernel before injecting root, since it seems a good bit has changed in the kernel.

 

[Joe199799]

Restore userdata, unroot, uninstall Magisk, take OTA.

Be sure to pull a new copy of the kernel before injecting root, since it seems a good bit has changed in the kernel.

Ok I'm sorry this is a little more complex than my 6T was I apologise I'm lost on restore userdata and pulling a new copy of the kernel (I'm assuming boot.img)