Database Users

February Security update is up

MMB29Q factory image is available on Google developers site (FWIW).
https://developers.google.com/android/nexus/images

So does the Q mean it's actually an older build than S what we currently have?

zip please

StykerB said:
So does the Q mean it's actually an older build than S what we currently have?
Click to expand...
Click to collapse
No. MMB29Q was just posted by Google this afternoon. It is the latest, February security update.

StykerB said:
So does the Q mean it's actually an older build than S what we currently have?
Click to expand...
Click to collapse
MMB29Q has a build date of Fri Dec 11 00:43:54 UTC 2015
MMB29S has a build date of Tue Dec 15 22:16:10 UTC 2015
Bit odd that it has an older build date and build number. Once AOSP has been updated with these new builds, it'll make more sense.

I was thinking exactly the same. Why is there an apparent 2-step-backward in the build number? And particularly if the Dec 11/15 dates mentioned above are correct? What's going on...? Have Google cocked it up?
And just for the fun...
The zip components are dated 5th January, and the images are dated 1st January 2009.
I'm not touching this with a bargepole until someone explains this to me in one-syllable words...

dahawthorne said:
I was thinking exactly the same. Why is there an apparent 2-step-backward in the build number? And particularly if the Dec 11/15 dates mentioned above are correct? What's going on...? Have Google cocked it up?
Click to expand...
Click to collapse
Not sure about that. FWIW, in "about the phone" it says: "Android security patch level: February 1, 2016".

and one more thing, T was the latest, and im on it. but its not there anymore. now S is before Q

Was there a modem update with Q.....or T?
Edit: I believe latest was 32R for reference.
Edit 2: Just extracted the archive and the Modem is the same as last release. Bootloader size and name are also exactly the same so I don't think there was a new bootloader or modem. (In version Q)

I just extracted and only system.img looks different to me, although both the bootloader and radio images have January 5, 2016 build dates compared to January 1, 2009 dates for S. I think I'll just fastboot all of them to be safe.

Wanted to make a separate post for this because it seems important. After flashing this update I decided to stay stock and root. Following an install of TWRP and system root 2.52 a message appeared on boot that my system was corrupt and to press power to pause boot. After that the phone immediately shut down. I had to flash unSU in order to keep the phone from shutting down and when I rebooted the corruption message is still present but the phone booted. I'm going to try systemless root and seeing if it work, but it was just a heads up for anyone here planning to flash the newest update.
Side note: I'll edit this post when I have results from Systemless root. Also, well played Google. Well played...
Edit: Systemless root version 2.66 worked properly and I am rooted without the corrupted boot message.

AlkaliV2 said:
Wanted to make a separate post for this because it seems important. After flashing this update I decided to stay stock and root. Following an install of TWRP and system root 2.52 a message appeared on boot that my system was corrupt and to press power to pause boot. After that the phone immediately shut down. I had to flash unSU in order to keep the phone from shutting down and when I rebooted the corruption message is still present but the phone booted. I'm going to try systemless root and seeing if it work, but it was just a heads up for anyone here planning to flash the newest update.
Side note: I'll edit this post when I have results from Systemless root. Also, well played Google. Well played...
Edit: Systemless root version 2.66 worked properly and I am rooted without the corrupted boot message.
Click to expand...
Click to collapse
HI I got the same message, so i did this:
1. Clean Flash again.
2. Boot the phone for first time, but in the part that ask for a pin or Pattern i didn't.
3. Flash supersu systemless.
4. Boot the phone and set a pattern and enjoy.
Hope this can be helpful for you.

dahawthorne said:
I was thinking exactly the same. Why is there an apparent 2-step-backward in the build number? And particularly if the Dec 11/15 dates mentioned above are correct? What's going on...? Have Google cocked it up?
And just for the fun...
The zip components are dated 5th January, and the images are dated 1st January 2009.
I'm not touching this with a bargepole until someone explains this to me in one-syllable words...
Click to expand...
Click to collapse
I got the Q update today via normal OTA and I was on January's S update. So I'd say that the Q update is legit.

I'm running on 32R with no issues so I'm gonna keep it that way.

Took the q update, no probs don't understand why s is older then q. But stable and no issues at all
Sent from my Nexus 6 using Tapatalk

log1321 said:
HI I got the same message, so i did this:
1. Clean Flash again.
2. Boot the phone for first time, but in the part that ask for a pin or Pattern i didn't.
3. Flash supersu systemless.
4. Boot the phone and set a pattern and enjoy.
Hope this can be helpful for you.
Click to expand...
Click to collapse
AlkaliV2 said:
Wanted to make a separate post for this because it seems important. After flashing this update I decided to stay stock and root. Following an install of TWRP and system root 2.52 a message appeared on boot that my system was corrupt and to press power to pause boot. After that the phone immediately shut down. I had to flash unSU in order to keep the phone from shutting down and when I rebooted the corruption message is still present but the phone booted. I'm going to try systemless root and seeing if it work, but it was just a heads up for anyone here planning to flash the newest update.
Side note: I'll edit this post when I have results from Systemless root. Also, well played Google. Well played...
Edit: Systemless root version 2.66 worked properly and I am rooted without the corrupted boot message.
Click to expand...
Click to collapse
Marshmallow kernel images (boot.img) check for system partition integrity and therefore regular injection of su binary inevitably causes the corruption message to appear. So when you flash these updates either you should manually patch the kernel or use systemless root which includes that patch.
Use SuperSU 2.66 which automatically determines which method should be used to install SuperSU.
---------- Post added at 03:51 AM ---------- Previous post was at 03:48 AM ----------
simms22 said:
and one more thing, T was the latest, and im on it. but its not there anymore. now S is before Q
Click to expand...
Click to collapse
If you still have the T update do u think you can post it online somewhere? Thanks.

MMB29T was announced on 4th January, so MMB29Q is the latest, since it has a security revision date of 1st February.
Google are making a right dog's breakfast of these update sequence letters...
And why use SuperSU 2.66 when there's already a stable 2.67?

I wanted to find out if anyone else has had any problems since this update. I'm having odd freezes that last 30 seconds to a minute. Also my Mailwise app is shutting itself down every minute or so. TouchPal keyboard doesn't respond after it pops up occasionally. Security updates have never caused me a problem before. I'm on Marshmallow 6.0.1, with an unlocked bootloader(if that matters), using Nova Launcher.
Sorry if I put this in the wrong forum, but none of these problems existed before the update. Thanks guys!

@ahpukuh,
I've not had any of the problems that you mention, or any problems at all. FWIW, I'm running the stock launcher and keyboard.

najoor said:
Marshmallow kernel images (boot.img) check for system partition integrity and therefore regular injection of su binary inevitably causes the corruption message to appear. So when you flash these updates either you should manually patch the kernel or use systemless root which includes that patch.
Use SuperSU 2.66 which automatically determines which method should be used to install SuperSU.
---------- Post added at 03:51 AM ---------- Previous post was at 03:48 AM ----------
If you still have the T update do u think you can post it online somewhere? Thanks.
Click to expand...
Click to collapse
Then why don't I get the corruption message when am rooting with NRT, which I thought used the older "system" root.?

OTA issue...

Recieved my 6P on Tuesday, it updated to 6.0.1 and it's currently build number MMB29P but when I hit "System Update" it says it last checked 2 mins ago and my system is up to date but isn't the latest build MHC19I? Any idea what the issue is?

USFguy said:
Recieved my 6P on Tuesday, it updated to 6.0.1 and it's currently build number MMB29P but when I hit "System Update" it says it last checked 2 mins ago and my system is up to date but isn't the latest build MHC19I? Any idea what the issue is?
Click to expand...
Click to collapse
This seems to happen to done some people, no idea why though. You can update manually pretty easily, just flash the factory images for the latest build. I have instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Heisenberg said:
This seems to happen to done some people, no idea why though. You can update manually pretty easily, just flash the factory images for the latest build. I have instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks, I haven't used adb since 2014 with my HTC One X so I'm a little hesitant but seems easy enough.

Question if I manually update will that have any interference with future OTA's? As in would I have to manually flash from here on out?

USFguy said:
Question if I manually update will that have any interference with future OTA's? As in would I have to manually flash from here on out?
Click to expand...
Click to collapse
no, everything will just fine..

USFguy said:
Question if I manually update will that have any interference with future OTA's? As in would I have to manually flash from here on out?
Click to expand...
Click to collapse
Nope, it has no effect on future OTA's.

Heisenberg said:
Nope, it has no effect on future OTA's.
Click to expand...
Click to collapse
Just unlock bootloader and flash?

USFguy said:
Just unlock bootloader and flash?
Click to expand...
Click to collapse
Yeah that's it, unlock your bootloader and flash the factory images for MHC19I and you'll be up to date.

I have the same problem , i got the phone from bestbuy today it updated to MMB29P and thats it no more updates?

samomamo said:
I have the same problem , i got the phone from bestbuy today it updated to MMB29P and thats it no more updates?
Click to expand...
Click to collapse
Did you read the other posts in this thread?

Heisenberg said:
Did you read the other posts in this thread?
Click to expand...
Click to collapse
Yes i don't wanna unlock the bootloader. I know how to do it. But its suppose to update automatically.

samomamo said:
Yes i don't wanna unlock the bootloader. I know how to do it. But its suppose to update automatically.
Click to expand...
Click to collapse
I'd suggest unlocking the bootloader anyway. If an OTA fails on you you'll be soft bricked and there'll be absolutely nothing you can do about it with a locked bootloader, apart from sending it for repair. It's happened to a few people.

Heisenberg said:
I'd suggest unlocking the bootloader anyway. If an OTA fails on you you'll be soft bricked and there'll be absolutely nothing you can do about it with a locked bootloader, apart from sending it for repair. It's happened to a few people.
Click to expand...
Click to collapse
Thanks alot bro, im just lazy to set everything up again.

samomamo said:
Thanks alot bro, im just lazy to set everything up again.
Click to expand...
Click to collapse
It's worth it, I know I'd rather spend the time setting my phone up again than having to send the thing away because it got bricked.

I'm also stuck on January's patch so I wanted to know if I'll get February, then March or does the ota go straight to the latest security patch? If I decide to manually flash it, would I have to flash the February patch first or go straight to they latest one?
Sent from my Nexus 6P using Tapatalk

toddalvandi said:
I'm also stuck on January's patch so I wanted to know if I'll get February, then March or does the ota go straight to the latest security patch? If I decide to manually flash it, would I have to flash the February patch first or go straight to they latest one?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you decide to flash manually, you have two options.
1. Flash the factory images (via fastboot). With this option you can just download the factory images for the latest build and flash them, no need to go through each update to get there.
2. Flash the OTA zips (via stock recovery and adb sideload). This option means you need to flash the OTA zips in order. But since you're on the January build it would only be two zips: the MMP29P --> MMB29Q zip, then the MMB29Q -- > MHC19I zip.
Personally, I'd just flash the factory images with fastboot, it's easier. You do need an unlocked bootloader though, but in my opinion you should have an unlocked bootloader regardless.

Heisenberg said:
It's worth it, I know I'd rather spend the time setting my phone up again than having to send the thing away because it got bricked.
Click to expand...
Click to collapse
Thanks a lot u convinced me. I unlocked and for the hell of it flashed the Android N. Man is so fast , its like running 60fps, I thought its just gonna be little ui changes, but i was wrong. Its like lightning fast. Thanks
Ok it didnt last long. Back to M latest. The N was fast, but toooo many glitches.

Heisenberg said:
If you decide to flash manually, you have two options.
1. Flash the factory images (via fastboot). With this option you can just download the factory images for the latest build and flash them, no need to go through each update to get there.
2. Flash the OTA zips (via stock recovery and adb sideload). This option means you need to flash the OTA zips in order. But since you're on the January build it would only be two zips: the MMP29P --> MMB29Q zip, then the MMB29Q -- > MHC19I zip.
Personally, I'd just flash the factory images with fastboot, it's easier. You do need an unlocked bootloader though, but in my opinion you should have an unlocked bootloader regardless.
Click to expand...
Click to collapse
Just getting time to sit down and do this, I've gone and got all the SDK tools setup in the general thread you linked, and I know i have to unlock bootloader but for the factory image does it matter if I do post #10 or #11? With the phone being 4 days old would flashing without wiping be a big issue?

USFguy said:
Just getting time to sit down and do this, I've gone and got all the SDK tools setup in the general thread you linked, and I know i have to unlock bootloader but for the factory image does it matter if I do post #10 or #11? With the phone being 4 days old would flashing without wiping be a big issue?
Click to expand...
Click to collapse
You should have no issues flashing the images without wiping userdata.

Heisenberg said:
You should have no issues flashing the images without wiping userdata.
Click to expand...
Click to collapse
Ah, but I think I answered my own question, won't unlocking the bootloader wipe all data anyway?

Frd-l04 b389

There's a new firmware available on firmware finder. Must be the September patches
Edit: It appears to be the October security patch.

its actually october patches. l14 in the US got this update before the l04.

TomTheGeek3 said:
its actually october patches. l14 in the US got this update before the l04.
Click to expand...
Click to collapse
Wow that's amazing. Did ur device recieve the update?
Sent from my Honor 8 using XDA Labs

ayush rao said:
Wow that's amazing. Did ur device recieve the update?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
i own a l04 but i frequent here and the honor 8 subreddit. a user there has the l14 and has this update and confirmed the oct security patches.
https://imgur.com/gallery/L3f1p <- pictures from the l14 b389
https://redd.it/79bjb2 <- op confirmed oct patches in comment thread

TomTheGeek3 said:
i own a l04 but i frequent here and the honor 8 subreddit. a user there has the l14 and has this update and confirmed the oct security patches.
https://imgur.com/gallery/L3f1p <- pictures from the l14 b389
https://redd.it/79bjb2 <- op confirmed oct patches in comment thread
Click to expand...
Click to collapse
Awesome thanks!
Sent from my FRD-L04 using Tapatalk

Saw this update message and got excited thinking we were getting Android Oreo... security updates are such a tease!

I'm glad to see the October security release updated so quickly for the Honor 8. To bad the KRACK vulnerability wasn't fixed until the Nov release. Hopefully it is patched quickly too given how serious it is.

How do you spoused to download if you got twrp threw updater or what?

ayush rao said:
There's a new firmware available on firmware finder. Must be the September patches
Edit: It appears to be the October security patch.
Click to expand...
Click to collapse
i m downloading it right now on L04, Karachi - Pakistan

SSyar said:
i m downloading it right now on L04, Karachi - Pakistan
Click to expand...
Click to collapse
It is October Security Patch

Mikeyy233 said:
How do you spoused to download if you got twrp threw updater or what?
Click to expand...
Click to collapse
EDIT - this post made me go ahead and create a new Guide thread. Please check it out if you are wondering how to take an upgrade if you have unlocked and rooted your phone.
Here is the original post I made....
I just researched this myself and this is what I did....
1) Make a backup using TWRP (if the new update locks the phone, you will need this backup to restore data after unlocking it)
2) The update won't work with TWRP as your recovery, so we need to flash the original Huawei recovery to replace TWRP. If you are like me, you don't have a copy of the stock recovery image on hand (if you do have a copy, then skip to step 3). Therefore we need to extract it from the stock ROM image. Download the stock ROM image for your device. This website seems to have a list of recent versions and it is where I downloaded the L14 B389 version that I used.
download the Hauwei Update Extractor software and install it on a computer. Here is a Youtube video showing how to use it. You only need to extract the "Recovery.img" file for our use (the video extracts several additional files that we don't need). Move the stock recovery image to your ADB folder so you can flash it in step 3.
3) Use the stock recovery file and flash it to recovery using the same instructions as you used to flash TWRP in the first place. If you need a refresher, look at section 2 of the first post in this thread. Just make sure you substite the name of the stock recovery image instead of TWRP.
4) Reboot into system
5) Go to the Settings - System Update menu on your phone. In the upper right corner, click on the three dots and it will bring up a menu where you can choose "Download latest full update". Click on this. This will start the update process by downloading the full ROM and not just the smaller update package. For me the package size was approaching 3gb, so make sure you are ready to handle that size transfer. For me, the phone automatically did the update after downloading the package. I was nervous at first, but everything went fine. If for some reason the update fails, I would reboot and try again. I did have one failure, but I cannot explain if it was a bad download, or something I did wrong. It worked fine the second attempt.
6) The phone will reboot and you should check the status to make sure you are on the latest version.
7) I read where people said full updates would lock your phone and you would have to start from scratch unlocking it (and therefore wiping all data). This was not the case for me and this update. I was simple able to flash TWRP again. You should be a rock star at flashing recoveries by now so get to it and flash TWRP again. If your phone is locked, the read the note at the bottom of this post.
8) Reboot into system
9) Reboot into recovery and flash Magik zip to get SuperSU.
10) Reboot into system. Reinstall any Magik modules you use as they don't get carried over from the previous installation.
11) Enjoy your updated phone
If for some reason the full update did lock the phone, then you will need to unlock it again before you can flash TWRP. You have already done this before, so use whatever method was successful for you. Obviously this will fully wipe your phone. After flashing TWRP and Magik, I would make a backup of that raw "stock" image just in case this next step doesn't work. After making the backup, you can try to restore just the data partition of the NAIDroid backup you made in step 1 (click restore in TWRP, select the backup made in step 1 but deselect everything except the "data" partition before starting the restore process.) I have never done this, but I have read it will recover all your data (apps, etc) without affecting the system partition and therefore it won't mess up the upgrade. I would not recommend doing this if going from Marshmallow to Nugget or Nugget to Oreo however. In those cases, it is better to simple start fresh and redownload all of your apps.

SSyar said:
It is October Security Patch
Click to expand...
Click to collapse
Did u notice anything else or is it just the security patch?
Sent from my FRD-L04 using Tapatalk

ayush rao said:
Did u notice anything else or is it just the security patch?
Click to expand...
Click to collapse
It's just a security patch.
#Boring

PuffDaddy_d said:
It's just a security patch.
#Boring
Click to expand...
Click to collapse
That is so disappointing but atleast they bothered updating the phone. Its a good sign that Oreo still might come.......
Sent from my FRD-L04 using Tapatalk

Delete....

Does anyone know when KRACK will be patched? I think Google included it in the November security updates. This may mean I'll come in December?

How it's battery life on these update ... b388 kills my battery like crazy ???

luisaet82 said:
How it's battery life on these update ... b388 kills my battery like crazy [emoji23][emoji23][emoji23]
Click to expand...
Click to collapse
Really? I get great battery life on B388. Actually I hadn't formatted my phone in over 8 months and when I did it I started getting really good battery life. You could maybe try that too?
Sent from my FRD-L04 using Tapatalk

I'm gonna give a try today

Oh boy it's looking great so far

11..0.4.4 IN11AA

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!

Question How to update rooted Nothing Phone 1?

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