Database Users

Final Official Oreo 8.1.0 Release - OPP28.85-16 OTA

I've just captured the Official OPP28.85-16 OTA for retail cedric and I'm posting it here. I'm on retbr channel but this will work on any retail device. If you're on another updated channel, I don't know what would happen if you installed this.
Notice that to install this YOU MUST be on NPPS25.137-93-2-5 to install these, since OTA's are not full firmwares like fastboot files, but instead they're patchings tailored to be applied upon a specific firmare - NPPS25.137-93-2-5 in this case.
Another particular detail is that the OTA file (gotten directly from my credric) lists the Blur Version as Blur_Version.25.361.10.cedric.retail.en.US, but curiously, the fastboot version for the same firmware ( which you can download here) lists it as Blur_Version.28.41.15.cedric.retail.en.US
Someone also reported in another thread that they just sideloaded this upon the Second Soak test. I wouldn't doubt it since this is what should happen to regular soak testers, but if you do it, DO IT AT YOUR OWN RISK
I also won't post instructions on how to install this since they're already available here
Download
Gdrive: https://drive.google.com/file/d/149hrGFpuWUgAvJr02McYNwJVaqSvllYO/view?usp=sharing
That's it.

changelog?

Has anyone already tried it?

Since this is a (Delta) OTA Update that expects NPPS25.137-93-2-5 (Blur_Version.25.361.10) it should be correctly named "block_delta-ota-Blur_Version.25.361.10-28.41.15.cedric.retail.en.US" in my view.
Someone also reported in another thread that they just sideloaded this upon the Second Soak test.
Click to expand...
Click to collapse
I'm on the 2nd soak test update OPP28.85-13.
Just tried to flash the update from SD card and ADB sideload.
Update failed due to wrong version.
E3002: Package expects build thumbprint of 8.1.0/OPP28.85-16/0400:user/release-keys or 7.0/NPPS25.137-93-2-5/10:user/release-keys; this device has 8.1.0/OPP28.85-13/789a:user/release-keys.

JoeDoe0 said:
Since this is a (Delta) OTA Update that expects NPPS25.137-93-2-5 (Blur_Version.25.361.10) it should be correctly named "block_delta-ota-Blur_Version.25.361.10-28.41.15.cedric.retail.en.US" in my view.
I'm on the 2nd soak test update OPP28.85-13.
Just tried to flash the update from SD card and ADB sideload.
Update failed due to wrong version.
E3002: Package expects build thumbprint of 8.1.0/OPP28.85-16/0400:user/release-keys or 7.0/NPPS25.137-93-2-5/10:user/release-keys; this device has 8.1.0/OPP28.85-13/789a:user/release-keys.
Click to expand...
Click to collapse
seems like it can be updated. from. soak test then, but I never heard nor did I find anything about OPP25. 85-16 build. maybe there was a third soak test and we don't know about it

Works perfect
Hi,
i used the above Image in Germany and i am now on Oreo 8.1
Everything works perfect. First i had a little bit trouble due to an old Version of ADB Tools, but after Update ADB to current Version the Update to Oreo took something around 30min.
Build 28.85-16
Oreo 8.1
Software Channel reteu
Patch Level 01.08.2018

bori321 said:
Hi,
i used the above Image in Germany and i am now on Oreo 8.1
Everything works perfect. First i had a little bit trouble due to an old Version of ADB Tools, but after Update ADB to current Version the Update to Oreo took something around 30min.
Build 28.85-16
Oreo 8.1
Software Channel reteu
Patch Level 01.08.2018
Click to expand...
Click to collapse
On which version you were before update?

Firmware
Hi,
before update to Oreo i flashed NPPS25.137-93-2-5 Firmware and after that the Image from this thread.
Worked perfect.
Alex
I tried to post a Screenshot but it was not possible because i am a new member...

Update failed due to wrong version.
E3002: Package expects build thumbprint of 8.1.0/OPP28.85-16/0400:user/release-keys or 7.0/NPPS25.137-93-2-5/10:user/release-keys; this device has 8.1.0/OPP28.85-13/789a:user/release-keys.
Click to expand...
Click to collapse
freeZbies said:
seems like it can be updated. from. soak test then, but I never heard nor did I find anything about OPP25. 85-16 build. maybe there was a third soak test and we don't know about it
Click to expand...
Click to collapse
Update fails from OPP28.85-13 since it expects either OPP28.85-16 which is the latest Oreo build (that I want to update to) or the latest Nougat NPPS25.137-93-2-5.
There is no OPP25. 85-16 build! I think you misread the error message.
BTW I updated from OPP28.85-13 to -16 using the full fastboot version and it worked out perfectly.

JoeDoe0 said:
Update fails from OPP28.85-13 since it expects either OPP28.85-16 which is the latest Oreo build (that I want to update to) or the latest Nougat NPPS25.137-93-2-5.
There is no OPP25. 85-16 build! I think you misread the error message.
BTW I updated from OPP28.85-13 to -16 using the full fastboot version and it worked out perfectly.
Click to expand...
Click to collapse
yeah, I actually misread it, now I see it.
Anyways, flashing it from fastboot doesn't prove anything. but seems like Cedric can be upgraded from the soak test to final version using this ota. Idk because I used fastboot myself too, since I had already modified my system partition.

AsusZenFone3Deluxe said:
changelog?
Click to expand...
Click to collapse
seriously?
stop joking, Motorola doesn't release changelogs.
but I'll try:
updated from nougat to oreo?
duhhh

how is speaker quality in this build ?
because there is some issues in previous oreo builds

Speaker
Hi,
i would say that for my ears the speaker sounds better than it was with Nougat.
After a few days of testing everything works really good and i have not found anything not working or any problems.
Alex

bori321 said:
Hi,
before update to Oreo i flashed NPPS25.137-93-2-5 Firmware and after that the Image from this thread.
Worked perfect.
Alex
I tried to post a Screenshot but it was not possible because i am a new member...
Click to expand...
Click to collapse
how do you get back to NPPS25.137-93-2-5

I followed the steps from this Thread: https://forum.xda-developers.com/g5/development/stock-upgrade-to-official-stock-oreo-8-t3823598
- Unlocked bootloader (don't know of this is necessary)
- back to NPPS25.137-93-2-5 via the commands from the thread i linked (without the lines:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
)
- via ADB sideload with the Oreo download from this thread to Oreo.
Alex

ahmedAZ said:
how is speaker quality in this build ?
because there is some issues in previous oreo builds
Click to expand...
Click to collapse
In my experience the quality is better than on previous oreo builds.
ahmedAZ said:
how do you get back to NPPS25.137-93-2-5
Click to expand...
Click to collapse
if you have an unlocked bootloader download NPPS25.137-93-2-5 Flashable Zip here and flash it with twrp
bori321 said:
I followed the steps from this Thread: https://forum.xda-developers.com/g5/development/stock-upgrade-to-official-stock-oreo-8-t3823598
- Unlocked bootloader (don't know of this is necessary)
Alex
Click to expand...
Click to collapse
to flash official Motorola files there's no need to unlock the bootloader.
you've just unnecessarily voided your warranty

@freeZbies
Hey is that twrp stock rom (137-93-2-5) the only thing we need to flash before going for the ota ? Cause I've been told that we needed to be on a completely unmodified system partition in order to receive the ota. In that case just flashing twrp stock wouldn't be sufficient right?
https://forum.xda-developers.com/g5...o-official-stock-oreo-8-t3823598/post77713117

Chekm8Qc said:
@freeZbies
Hey is that twrp stock rom (137-93-2-5) the only thing we need to flash before going for the ota ? Cause I've been told that we needed to be on a completely unmodified system partition in order to receive the ota. In that case just flashing twrp stock wouldn't be sufficient right?
https://forum.xda-developers.com/g5...o-official-stock-oreo-8-t3823598/post77713117
Click to expand...
Click to collapse
I dont know if the twrp version would be valid. To apply an OTA, your system must matchbit by bit, so the most guaranteed way is to flash that firmware via fastboot, but you could try flashing the twrp version, and in case it works, you could post the results here.
just dont forget that if the ota fails youll soft brick ur phonr and will only be able to recover it via fastboot

freeZbies said:
I dont know if the twrp version would be valid. To apply an OTA, your system must match stick bit by bit, so the most guaranteed way is to flash that firmware via fastboot, but. you could try flashing the twrp version, and in case it. woeks you could post the results here.
just dont forget that if the ota fails youll soft brick ur phonr and will only be able to recover it via fastboot
Click to expand...
Click to collapse
Thanks I'll keep that in mind
Being soft bricked,, wouldn't I be able to use twrp still? Like to flash a valid rom or one of my backups?
Anyways I can't really try it that way since the update hasn't come to me yet I'm on software channel Retca.
Edit : right I forgot that I could just use the official ota available here if I would like to test it.

Chekm8Qc said:
Thanks I'll keep that in mind
Being soft bricked,, wouldn't I be able to use twrp still? Like to flash a valid rom or one of my backups?
Anyways I can't really try it that way since the update hasn't come to me yet I'm on software channel Retca.
Edit : right I forgot that I could just use the official ota available here if I would like to test it.
Click to expand...
Click to collapse
being soft bricked doesnt necessarily mean you can recover it through twrp. OTA's are different of twrp flashables in that it modifies things beyond system partition. I've seen reports from people with other motorola devices who applied an OTA while having a modified system partition, and even though they were able to boot to twrp, flashing a custom Rom or restore a backup wouldn't make the phone boot. Their phones weren't hard bricked, but still they had to fastboot to recover their phones. Anyways, why don't you flash the Twrp flashable if, it's already available (considering you have an unlocked bootloader).
I'm case you have a locked bootloader you may fastboot without executing "fastboot erase userdata" in case you want to try. I did it without losing my data (although I was already in Opp 28.85-16)
but after all I really advice you to flash the twrp zip if u can

updating failed

So, I just rooted my Huawei P Smart, the 136 update shows up, it does all the install steps, reboots and then says it failed. Do O need to do something on the twrp boot?

Download the full firmware, we lose the option to just update via normal update and we can update with a full system update

airb05 said:
Download the full firmware, we lose the option to just update via normal update and we can update with a full system update
Click to expand...
Click to collapse
Just did that, 2 GB download, tries to install, reboots, goes to twrp, then I reboot to normal system and still says update failed.

Pretty sure you'll need stock recovery to update the "normal" way.

callmeWhiskers said:
Pretty sure you'll need stock recovery to update the "normal" way.
Click to expand...
Click to collapse
So I'll need to unroot and root again ? Anyway to update without doing that? Cause Im pretty sure ill screw up if I try it, barely made the root LOL

siivet said:
So I'll need to unroot and root again ? Anyway to update without doing that? Cause Im pretty sure ill screw up if I try it, barely made the root LOL
Click to expand...
Click to collapse
I'm not an expert - I always use HuRUpdater to update. It just requires you to download the (exact) right files, renaming them correctly and (like rooting with Magisk) just simply flashing a single .zip in recovery. In case you try it out, remember rule#1: Always make sure you have a (nandroid)backup.
Here are the relevant lines from my "Huawei-related-findings" text file:
#update
"Depends on how you rooted.
For a successful OTA install your device probably must meet the following criteria
• HUAWEI stock recovery installed
• unaltered /system, /product and /vendor partitions
So if you rooted with a "systemless" method (e.g. Magisk, recent SuperSU) and haven't done other installs/modifications that typically change /system you could try it. And you have to flash stock recovery (i.e. get rid of TWRP temporarily for the OTA install)."
Click to expand...
Click to collapse
#source XDA
 @st_voss (u=1065667)
https://forum.xda-developers.com/showpost.php?p=73011427&postcount=2
#update
“It's recommended to use a proper custom recovery (with running oeminfo_nvm_server service) like for example*my version of TWRP.
How to use:
Warning: Make sure you know what you are doing and do not flash firmware from other devices.
1. Download firmware files (for official firmware use Huawei Firmware Finder).
2. Put files you want to flash in a seperate folder on sdcard.
Supported zip files to flash are (name must match):
◦ update.zip (use FullOTA file)
◦ update_all_hw.zip
◦ update_data_public.zip
3. Optional: Put recovery.img in same folder if you want to keep custom recovery.
4. Put HuRUpdater zip in same folder.
 5. Select*only HuRUpdater*to flash in custom recovery.
6. Follow instructions on screen. Flashing can take multiple minutes.
Problems:
• If firmware includes factory reset
◦ Factory reset is not supported by custom recovery. Therefore HuRUpdater will flash stock recovery before launching factory reset. After flashing firmware and doing factory reset, you need to flash recovery manually.”
Click to expand...
Click to collapse
#source XDA
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
#notes HuRUpdater_0.4.zip working

Thanks mate, the Huawei Firmware Finder seems like its not working for the moment, but as soon as it is ill follow your tip

siivet said:
Thanks mate, the Huawei Firmware Finder seems like its not working for the moment, but as soon as it is ill follow your tip
Click to expand...
Click to collapse
Yes, I'm im the same boat - I guess you also get the "can't have connection" error using the FF app. During the last weeks they had troubles with their service regarding hackers and moving to a new server (according to their telegram group), which have been fixed ("all services working normally now"), and many can use it again - for whatever reason some still can't connect. I tried reinstalling the app, using proxies from different countries - still doesn't let me connect.
But their web interface is working: https://pro-teammt.ru/firmware-database/ though you can't check iirc, if the firmware has been approved for your IMEI.
According to this post:
sun75 said:
It's online now! I suggest you to download the "2018.08.30" .158 "2379" release, if you have a FIG-LX1, L31 board phone.
Click to expand...
Click to collapse
You apparently can download this release (2379) if you own this device/board- though the last time I updated mine (.148) I used the 2079 (154226) one despite owning the exact same device. I'm slightly confused about this
I didn't try the above mentioned update myself.

siivet said:
Thanks mate, the Huawei Firmware Finder seems like its not working for the moment, but as soon as it is ill follow your tip
Click to expand...
Click to collapse
Try installing an older version of the Firmware Finder app - I switched from (current) v9.0 to v8.9 and it works now
https://apkpure.com/firmware-finder...efinder/download/86-APK?from=versions/version

..

[CLOSED][Guide] How to ROOT the OnePlus8T KB2003 & current OTA

Hi,
quick files that many of us waiting for
OnePlus 8T, 11.0.1.2 KB05BA KB2003
Newest (20.10.2020) OTA:
https://drive.google.com/file/d/1uKV_j8yIQLPeIRJkf1KIUlJcIaH8BppR/view?usp=sharing
boot.img (stock)
https://drive.google.com/file/d/12VopoB984YmJHUJuqMBA4jyID1Sp_sPQ/view?usp=sharing
boot.img (patched, checked, working)
https://drive.google.com/file/d/1V4esvmJCBkwskq2shfWcylPL53h4dd_2/view?usp=sharing
=======================================
You like it?
paypal.me/widmak
=======================================
Thanks!

Thanks. But where's the guide or howto, that the title says ?

I flashed your patched boot image, but no Magisk is detected in either stable or canary Magisk Manager. There might be an issue.
EDIT: Confirmed that the issue is on your end. Patched the image myself and flashed it, with Magisk being detected by Magisk Manager.
https://drive.google.com/file/d/1yw5Fwgy0_ArPD_itnZ66nmdWA2NapFPg/view
This boot image works.

Any idea to flash the EU rom from India?

felata said:
Any idea to flash the EU rom from India?
Click to expand...
Click to collapse
Download the full OTA zip, keep it in internal storage outside any folders.
Go to System -> System Updates
Click the gear icon, select local upgrade
Then, select the downloaded Full OTA zip.
Install and reboot.
Done.

theincognito said:
Download the full OTA zip, keep it in internal storage outside any folders.
Go to System -> System Updates
Click the gear icon, select local upgrade
Then, select the downloaded Full OTA zip.
Install and reboot.
Done.
Click to expand...
Click to collapse
The system says that it won't allow downgrade

Which magisk did you use please?

Alvincyq said:
The system says that it won't allow downgrade
Click to expand...
Click to collapse
If you updated to the Indian/Global 11.0.1.2 before doing this, you only have 2 options:
1. Wait for the next OOS update, but when the Indian/Global update comes, don't update.
Instead, wait for the full update zip of the EU to be available, and then follow the steps in the previous comment.
2. Unlock bootloader, flash the full OTA zip of any variant via fastboot, and relock the bootloader.

elliottweaver said:
I flashed your patched boot image, but no Magisk is detected in either stable or canary Magisk Manager. There might be an issue.
EDIT: Confirmed that the issue is on your end. Patched the image myself and flashed it, with Magisk being detected by Magisk Manager.
https://drive.google.com/file/d/1yw5Fwgy0_ArPD_itnZ66nmdWA2NapFPg/view
This boot image works.
Click to expand...
Click to collapse
Your file did not work for me but i modified the stock file from the first post myself and that worked. i guess there is something coded into the file by magisk that is depended on the phone.

theincognito said:
Download the full OTA zip, keep it in internal storage outside any folders.
Go to System -> System Updates
Click the gear icon, select local upgrade
Then, select the downloaded Full OTA zip.
Install and reboot.
Done.
Click to expand...
Click to collapse
I'm on Kb2005 and I'm only able to get an incremental update. Can I pull the bin file from that update

Was there an OTA specific to models outside of the U.S.? I see at least two variations are already getting an update but nothing is available yet for my US (KB2005) variant I got today.

MNoisy said:
Was there an OTA specific to models outside of the U.S.? I see at least two variations are already getting an update but nothing is available yet for my US (KB2005) variant I got today.
Click to expand...
Click to collapse
I have KB2005 as well. No updates for me. I tried to just boot the images posted in the other thread with no luck.

northmendo said:
I have KB2005 as well. No updates for me. I tried to just boot the images posted in the other thread with no luck.
Click to expand...
Click to collapse
Unless OnePlus is very different from the other major manufactures, you definitely do not want to use a patched boot image from a different model variation of software/firmware. At best it will cause major issues.. At worst, it will brick it.
If Oneplus is different, I would love some feedback on why and what they do from other users.

MNoisy said:
Unless OnePlus is very different from the other major manufactures, you definitely do not want to use a patched boot image from a different model variation of software/firmware. At best it will cause major issues.. At worst, it will brick it.
If Oneplus is different, I would love some feedback on why and what they do from other users.
Click to expand...
Click to collapse
Correctish, you don't want to flash it. You can just boot the image. If successful it'll just boot the phone. If unsuccessful it will hang and you can just force reboot. No damage can because because it's not writing the boot image to the phones storage. Kinda like booting from a flash drive. The code is
Code:
fastboot boot /path/boot.img
If you boot a patched boot image you will have access to a rooted phone until you reboot. I.E. just enough time to flash magisk on the installed boot image.
Hope that makes sense.

northmendo said:
Correctish, you don't want to flash it. You can just boot the image. If successful it'll just boot the phone. If unsuccessful it will hang and you can just force reboot. No damage can because because it's not writing the boot image to the phones storage. Kinda like booting from a flash drive. The code is
Code:
fastboot boot /path/boot.img
If you boot a patched boot image you will have access to a rooted phone until you reboot. I.E. just enough time to flash magisk on the installed boot image.
Hope that makes sense.
Click to expand...
Click to collapse
I am familiar with how it works but with brands like HTC and Samsung, if we use a boot.img from a different variation, it will not work or even brick it. Thanks for the heads up! It sounds like there is more room for error for testing with OnePlus and modifying the system.

Can someone please provide a link to the Magisk Manager that 's working with this bootimage?
Edit: Found it, got root but it doesn't pass SafetyNet...

epr said:
Can someone please provide a link to the Magisk Manager that 's working with this bootimage?
Edit: Found it, got root but it doesn't pass SafetyNet...
Click to expand...
Click to collapse
Which one was it? My Magisk is not working either. I assumed it was because the kb2005 was only an incremental update. I have the canary version from github. Is there another for oneplus?

MNoisy said:
Which one was it? My Magisk is not working either. I assumed it was because the kb2005 was only an incremental update. I have the canary version from github. Is there another for oneplus?
Click to expand...
Click to collapse
Downloaded it from github: https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk

epr said:
Downloaded it from github: https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
Click to expand...
Click to collapse
Yeah, same one. And it worked on the incremental Ota for kb2005?
Do you mind posting the patched boot.img?
Thank you!

MNoisy said:
Yeah, same one. And it worked on the incremental Ota for kb2005?
Do you mind posting the patched boot.img?
Thank you!
Click to expand...
Click to collapse
Don't know for KB2005, mine is KB2003.
I used stock boot.img from OP and patched it myself, all already patched files didn't work.

Question [SOLVED(not possible)]Restore Firmware 1.1.4 to 1.1.3 via fastboot. Is it possible?

Short question: Is it safe to flash extracted image friles from payload of 1.1.3 if im on 1.1.4?
Long question:
I think i messed things up, i dont know which boot image im currently using but the phone is on 1.1.4 as far as i can tell.
I dont get the latest 1.14 hotfix offered and i dont have the stock boot image of 1.1.4 OTA.
I would like to do a "restart" and go back to 1.1.3 and update via OTA to latest firmware to get a clean device again.
I searched every thread but couldnt find a real answer only some people saying you should not downgrade this phone.
Any advice?
Edit:
[GUIDE][HowTo] Unlock and root Nothing Phone (1)
ANNOUNCEMENT: I'M STOPPING THE FOLLOW UP AND UPDATE OF THIS TOPIC TODAY, IF SOMEONE WANTS TO TAKE OVER, CONTACT THE MODERATOR IN THIS LINK. THE TOPIC REMAINS AS IT IS AND WILL NOT BE UPDATED ANYMORE (BY ME ANYWAY!) GOOD CONTINUATION TO ALL...
forum.xda-developers.com
I found a tutorial that fastboot flashing is possible to restore stock firmware, but will it work if im on 1.1.4 since we only have the full update packages below 1.1.4?

sh4tteredd said:
if you're on 1.1.4, this phone tecnically has a very strict anti rollback check, so I won't risk if I were in you.
Click to expand...
Click to collapse

Question Rooting NP1 from 1.1.7EEA - Hotfix or not hotfix ?

Hi all
I got my NP1 some days ago. I read the [GUIDE][HowTo] Unlock and root Nothing Phone (1) but I'm stuck with a complicated question before I start the process:
My np1 currently is with NOS-1.1.7EEA but I don't know how to find if it got the 1.1.7 Hotfix.
If it already has the hotfix, will the rooting procedure with full OTA the fail/brick because the [GUIDE] states to use the same "full OTA package corresponding to the installed software version on the Nothing Phone 1"?​If this is at risk, should I wait for a new full OTA release or is there a way to roll-back to the original full 1.1.7EEA OTA?​​If there is no specific risk to root the np1 pre-patched with the hotfix, I guess the process will remove the hotfix. So the question becomes: since once rooted, a device won't get OTA updates anymore, then shall I have to manually reinstall the hotfix package with adb?​
Many thanks
BTW, anyone knows what the hotfix fixes ? There is nothing here.
​

The Hotfix is some small thing to make your phone accept the 1.5 A13 beta IMO
You can use a patched boot.img from 1.1.7 and "fastboot boot PATCHEDIMAGE.img" to root your phone.
It doesnt matter if you are on the hotfix or not.

1stStep said:
Hi all
I got my NP1 some days ago. I read the [GUIDE][HowTo] Unlock and root Nothing Phone (1) but I'm stuck with a complicated question before I start the process:
My np1 currently is with NOS-1.1.7EEA but I don't know how to find if it got the 1.1.7 Hotfix.
If it already has the hotfix, will the rooting procedure with full OTA the fail/brick because the [GUIDE] states to use the same "full OTA package corresponding to the installed software version on the Nothing Phone 1"?​If this is at risk, should I wait for a new full OTA release or is there a way to roll-back to the original full 1.1.7EEA OTA?​​If there is no specific risk to root the np1 pre-patched with the hotfix, I guess the process will remove the hotfix. So the question becomes: since once rooted, a device won't get OTA updates anymore, then shall I have to manually reinstall the hotfix package with adb?​
Many thanks
BTW, anyone knows what the hotfix fixes ? There is nothing here.
​
Click to expand...
Click to collapse
No.
On recent devices (from Xiaomi Mi 11), Nothing, Etc... Boot.img contain Boot + Recovery (it's for this reason flash a bad boot can be more dangerous than an older device with independant boot / recovery.
So if you are on 1.1.7... Boot is not different with or without hotfix (FYI the 1.1.7 fix is only 8 mb...)
And often Boot is not different between same branch version (A12 v 1.1.X).
You can like xtcislove said simply boot on a Magisk Boot Patched directly, boot success > Magisk > Install > Install Directly and it's done. You can found files and flash informations here
As soon you have root your devices, you don't receive OTA Update anymore but you will always have the possibility to install (sometimes) OTA Update only or (always) the Full Rom package. You lose the root during update, just install again new Magisk Patched boot.img if you want retrieve your root and modules.

Many thanks for kind answers guys @xtcislove & @Pho3nX
Now I found where I live: I do not have the hotfix, regards to XDA's np1 updates tracker and
Spoiler
Code:
adb shell getprop |grep SKQ1.211230.001/1669
[ro.bootimage.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1669043157:user/release-keys]
[ro.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1669043157:user/release-keys]
[ro.odm.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1669043157:user/release-keys]
[ro.product.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1669043157:user/release-keys]
[ro.system.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1669043157:user/release-keys]
[ro.system_ext.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1669043157:user/release-keys]
[ro.vendor.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1669043157:user/release-keys]
and
Code:
~$ date -d @1669043157
lun. 21 nov. 2022 16:05:57 CET
I'm so impatient to root, not worrying anymore to brick/fail.
I'm following the steps and advice from the guide, so I've stuck to extract myself boot.img out of full-OTA-1.1.7 and now I will generate myself my own Magisk-Patched-boot.img. Then fortunately I can check a hash against the one of the pre-cooked file and they match.
Maybe one day Nothing will release a full-OTA-117+ that will allow to upgrade to A13 following the same path.
ATM the hotfix isn't rolled-out here, so and also I've no regrets because the way I use my np1 makes me feel it smooth and responsive although I can't get/send MMS from my pro SIM in slot2. I'm impatient to drop my private SIM in slot1 and transfer data/reinstall apps from my old Samsung.
Hope this will reassure others.
Have a glad day and many thanks again

Rooting done. Thanks !

1stStep said:
Rooting done. Thanks !
Click to expand...
Click to collapse
Welcome to the Nothing Unleashed Family

Pho3nX said:
As soon you have root your devices, you don't receive OTA Update anymore but you will always have the possibility to install (sometimes) OTA Update only or (always) the Full Rom package. You lose the root during update, just install again new Magisk Patched boot.img if you want retrieve your root and modules.
Click to expand...
Click to collapse
I've had a rooted NP1 since day 1 and have always been able to receive OTA Updates. Up until now (1.1.7->1.1.8) I was also always able to install those using the normal System Update in Settings (restoring boot images in magisk beforehand, then install into inactive slot again).
Can you elaborate, please? Thanks!
Edit: Fixed