I do not speak English and I use a translator to ask questions.
So even if the grammar seems strange, thank you for your patience.
https://forum.xda-developers.com/xp...de-stock-kernel-root-twrp-drm-fix-41-t3711837
I have done the oreo upgrade, routing and drmfix through the link above.
But what should I do to get the December security patch?
Do I just upgrade to Flash tools? Or should I flash kernel, drmfix, and rooting again after upgrading?
Thanks for reading.
Since security patch are included in system update, so you need to flash the ROM and root again to get the patch.
f870103 said:
Since security patch are included in system update, so you need to flash the ROM and root again to get the patch.
Click to expand...
Click to collapse
Thank you for the information.
Related
So I followed rootjunkies tutorial (also blocks OTA updates i think?) to flash my prime version to the stock version and now it's at v6.4 and Android security patch level says: June 1, 2016.
Is this fine or do I need to upgrade, and if so how do I go about upgrading from here?
Cheers
Mae7 said:
So I followed rootjunkies tutorial (also blocks OTA updates i think?) to flash my prime version to the stock version and now it's at v6.4 and Android security patch level says: June 1, 2016.
Is this fine or do I need to upgrade, and if so how do I go about upgrading from here?
Cheers
Click to expand...
Click to collapse
I did the same initially. I suggest flashing back to 6.1 stock (complete 6.1 out of the box flash from mrmazak's thread) then flashing one of the 7.4.2 firmware you can find here. Use SPFT and it couldn't be easier.
My 7.4.2 shows October 5, 2016 for security patches.
Jakets said:
I did the same initially. I suggest flashing back to 6.1 stock (complete 6.1 out of the box flash from mrmazak's thread) then flashing one of the 7.4.2 firmware you can find here. Use SPFT and it couldn't be easier.
My 7.4.2 shows October 5, 2016 for security patches.
Click to expand...
Click to collapse
Cheers, I just followed Rootjunkies rooting guide and unlocking bootloader guide (forgot if I had already done this). Then I flashed this ROM in TWRP:
https://www.androidfilehost.com/?w=...fd3611a23c42ce769cb77d93e058695a15ec394a2e136
And it worked fine. It hung in the flashing part at the start but I waited it out and it installed. Then I reflashed the superSU zip again.
Mae7 said:
Cheers, I just followed Rootjunkies rooting guide and unlocking bootloader guide (forgot if I had already done this). Then I flashed this ROM in TWRP:
https://www.androidfilehost.com/?w=...fd3611a23c42ce769cb77d93e058695a15ec394a2e136
And it worked fine. It hung in the flashing part at the start but I waited it out and it installed. Then I reflashed the superSU zip again.
Click to expand...
Click to collapse
Does that one have the OTA updater still enabled? Can you disable it without root? I was thinking about trying that one. Glad it worked out for you.
Jakets said:
Does that one have the OTA updater still enabled? Can you disable it without root? I was thinking about trying that one. Glad it worked out for you.
Click to expand...
Click to collapse
Not sure. It's probably disabled for a custom ROM.
Jakets said:
I did the same initially. I suggest flashing back to 6.1 stock (complete 6.1 out of the box flash from mrmazak's thread) then flashing one of the 7.4.2 firmware you can find here. Use SPFT and it couldn't be easier.
My 7.4.2 shows October 5, 2016 for security patches.
Click to expand...
Click to collapse
FYI, October 5, 2016 patch level is the same as the non-Prime V17 OS.
Fat Rat Bastard said:
FYI, October 5, 2016 patch level is the same as the non-Prime V17 OS.
Click to expand...
Click to collapse
Yeah I actually ended up going with a V17 firmware.
Hello there.
My G5s+ is suggesting a security update. But since I did unlock the bootloader and rooted it with magisk I did not install it.
My question is: What is the best way to update the phone?
Just flash the new stock rom? And where do I get those?
Thanks in advance.
Nobody here that can tell me how to upgrade?
Should I just flash the new version if I get it somewhere?
Mr.Chainsaw said:
Nobody here that can tell me how to upgrade?
Should I just flash the new version if I get it somewhere?
Click to expand...
Click to collapse
Unlocked bootloader will not affect the OTA installation..!
The reason the OTA-Update fails is that one of the boot, system, logo or recovery partitions are changed.
Magisk modifies the boot image.
On rooted device..OTA may brick the device..so avoid OTA installation..!
Reply your current build Number from about phone..
Do a clean flash.
crazytech2 said:
On rooted device..OTA may brick the device..so avoid OTA installation..!
Click to expand...
Click to collapse
Thats why I did not do it yet. But I still want to do the update somehow.
crazytech2 said:
Reply your current build Number from about phone..
Click to expand...
Click to collapse
The Build No is
NPSS26.116-26-8
Mr.Chainsaw said:
Thats why I did not do it yet. But I still want to do the update somehow.
The Build No is
NPSS26.116-26-8
Click to expand...
Click to collapse
Flash 26-11 full firmware
Where can I find full firmware versions of the stock rom to flash?
My build version is: NPSS26.116-26-4
As I understand it, there are two new security patches since that version? If I'm flashing one of the newer versions, is it just a case of dirty flashing it normally through twrp? No need to factory reset?
Chemacky said:
Where can I find full firmware versions of the stock rom to flash?
My build version is: NPSS26.116-26-4
As I understand it, there are two new security patches since that version? If I'm flashing one of the newer versions, is it just a case of dirty flashing it normally through twrp? No need to factory reset?
Click to expand...
Click to collapse
If that is the firmware build you need, you could try the firmware here: https://firmware.center/firmware/Motorola/Moto G5s Plus/Stock/ but ensure you download the correct firmware. (credit to: https://forum.xda-developers.com/moto-g5s-plus/how-to/xt1804-able-to-lock-bootloader-npss26-t3722572) Also, verify it is the firmware you require and was the latest firmware build on your device - please don't downgrade with stock firmware (else you may hard brick with OTA updates corrupting your bootloader)...
Stock OTA updates, as mentioned above, require fully stock firmware - they will not flash with root, modifications or TWRP (and attempting to flash via TWRP may soft bootloop your device). Thus, you must re-flash the stock firmware - you may be able to save your data by omitting the 'fastboot erase userdata' command and you do not have to re-lock your bootloader. However, I'm not familiar with the G5S Plus and I hope another user can provide you with flashing commands.
I would still recommend you make a backup of your device in TWRP and keep that safe, in case you have to wipe your data for stability.
Hello!
So i want to root my NB1 but from what i read these couple of days, TWRP is incompatible with September and October security patch. I know that May and June are so my question is:
When on my slot A is the October patch and on my slot B is the September one how can i downgrade the B slot to May??? It would be really helpful if somebody explain that. I've tried to BOOT ( not flash) May prerooted img but the phone is stuck on powered by android logo.
U say twrp working in september security. So change ur phone to slot B.
Go to download mode. And use command
Fasboot reboot booloader (for enter download mode again)
Fastboot boot twrp
If it not boot to twro this mean twrp not comfortable with september.
If u want downgrade use ost tool 6.0.4 or ntool
To downgrade, here's a description:
https://forum.xda-developers.com/no...ia-8-official-firmware-links-updated-t3678487
You will flash then Oreo SW with may security patch where TWRP works fine.
Use this workaround for flashing Oreo software with OST 6.0.4
https://forum.xda-developers.com/nokia-7-plus/how-to/workaround-flashing-oreo-firmware-t3793791
Other possibility would be to change slot assuming that the other one is on August security patch
Last but not least is to use patched boot img, the description is also on XDA forum in Nokia 8 section
czupyt said:
To downgrade, here's a description:
https://forum.xda-developers.com/no...ia-8-official-firmware-links-updated-t3678487
You will flash then Oreo SW with may security patch where TWRP works fine.
Use this workaround for flashing Oreo software with OST 6.0.4
https://forum.xda-developers.com/nokia-7-plus/how-to/workaround-flashing-oreo-firmware-t3793791
Other possibility would be to change slot assuming that the other one is on August security patch
Last but not least is to use patched boot img, the description is also on XDA forum in Nokia 8 section
Click to expand...
Click to collapse
Thank you i'll try that.
Any feedback?
Mo4o293 said:
Thank you i'll try that.
Click to expand...
Click to collapse
I met exactly the same situation like the yours. Slot A on September and Slot B on October SP.
I cannot root it with any method in the forum on both the two slots. ( TWRP/ pre-rooted boot)
To downgrade, both the OST LA 6.12 /6.04 cannot downgrade my nokia TA-1052 with Sep/Oct SP.
Depression... I cannot live with an unrooted phone...:crying::crying:
Edit: finally rooted it. Solution: https://forum.xda-developers.com/nok...t3848390/page6, #58
smallerxie said:
I met exactly the same situation like the yours. Slot A on September and Slot B on October SP.
I cannot root it with any method in the forum on both the two slots. ( TWRP/ pre-rooted boot)
To downgrade, both the OST LA 6.12 /6.04 cannot downgrade my nokia TA-1052 with Sep/Oct SP.
Depression... I cannot live with an unrooted phone...:crying::crying:
Click to expand...
Click to collapse
My slot A is with October patch and B is with September. Also i dont want to try OST LA because this phone is my daily driver and i already have my old rooted phone. If you want to root your phone we need to wait for TWRP update. Really hope the maintainer update it soon to work with Sep and Oct patches.
Mo4o293 said:
My slot A is with October patch and B is with September. Also i dont want to try OST LA because this phone is my daily driver and i already have my old rooted phone. If you want to root your phone we need to wait for TWRP update. Really hope the maintainer update it soon to work with Sep and Oct patches.
Click to expand...
Click to collapse
I finally rooted it!
Here is my solution: https://forum.xda-developers.com/nokia-8/how-to/guide-how-to-root-nokia-8-ability-to-t3848390/page6, #58
smallerxie said:
I finally rooted it!
Here is my solution: https://forum.xda-developers.com/nokia-8/how-to/guide-how-to-root-nokia-8-ability-to-t3848390/page6, #58
Click to expand...
Click to collapse
So you are saying that i have to use "fastboot flash boot patched.img" instead of "fastboot boot patched.img"?
Edit: soo.....BRO YOU ARE MY GOD. OMG IT WORKS . THANK YOU A LOT AND SRY FOR THE CAPS LOCK. The wifi works perfectly and i'm rooted now!
Mo4o293 said:
So you are saying that i have to use "fastboot flash boot patched.img" instead of "fastboot boot patched.img"?
Edit: soo.....BRO YOU ARE MY GOD. OMG IT WORKS . THANK YOU A LOT AND SRY FOR THE CAPS LOCK. The wifi works perfectly and i'm rooted now!
Click to expand...
Click to collapse
You are welcome
My phone was rooted, so I thought it could be the problem. So I made a factory reset and uninstalled magisk.
Anyway, it keeps failing to install a new security patch. It keeps trying to install and always says there was a problem in the installation. What could be causing it?
I'm running the stock OTA with december security patch, since january and february had annoying bugs.
matheusgoes said:
My phone was rooted, so I thought it could be the problem. So I made a factory reset and uninstalled magisk.
Anyway, it keeps failing to install a new security patch. It keeps trying to install and always says there was a problem in the installation. What could be causing it?
I'm running the stock OTA with december security patch, since january and february had annoying bugs.
Click to expand...
Click to collapse
Try flashing stock ROM, it worked for me
Firexxe69 said:
Try flashing stock ROM, it worked for me
Click to expand...
Click to collapse
I've never flash any ROM. Do you have any tutorial I can follow?
matheusgoes said:
I've never flash any ROM. Do you have any tutorial I can follow?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445/page68 download the fastboot version, then flash it using fastboot commands
Firexxe69 said:
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445/page68 download the fastboot version, then flash it using fastboot commands
Click to expand...
Click to collapse
you directly flashed update?
i cant update since december security patch and now if i flash march s.p. with fastboot that will work?
Maharram said:
you directly flashed update?
i cant update since december security patch and now if i flash march s.p. with fastboot that will work?
Click to expand...
Click to collapse
I never tried it, but when i'm on december patch, i flashed the december patch, then update it from system update. Make sure to backup your data because it may erase your data.
I tried to flash december s.p.
Got the message "Flashing error bluetooth_a" mi flash tool. Do someone know how to solve it?
I've just installed Magisk on my device. I tried to update my phone via OTA with this tutorial https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation but the update fails.
I didn't flash the recovery image
I solved my problem.
I did few modifications on the system partition with Adaway, so that's why the OTA didn't work. So I reflash the firmware, and I followed the steps for OTA updates, and that works now!
I have that problem again : I tried to update from 7 to 13 and failed all the time. Before that, I installed the November 1st patch and lost the root. So I downgraded to 7 to get root again.
At Step 3, the update stops at 56% before the update fails.
FoxyLove33 said:
I've just installed Magisk on my device. I tried to update my phone via OTA with this tutorial https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation but the update fails.
I didn't flash the recovery image
Click to expand...
Click to collapse
Hey man, can you link a tutorial to update the z3 play with security patches? Mine has bootloader unlocked and no other modifications. All stock. Updated upto july patch. Can you link a tutorial? and link for the patches (RETUS)? Thx.
e4noob said:
Hey man, can you link a tutorial to update the z3 play with security patches? Mine has bootloader unlocked and no other modifications. All stock. Updated upto july patch. Can you link a tutorial? and link for the patches (RETUS)? Thx.
Click to expand...
Click to collapse
First of all, I'm not a man. The first link is how to install magisk, and the second one is how to update via OTA
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
FoxyLove33 said:
First of all, I'm not a man. The first link is how to install magisk, and the second one is how to update via OTA
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Click to expand...
Click to collapse
Thanks. I tried the instructions on the ota link, but am still getting Software Update unsuccessful?
FoxyLove33 said:
First of all, I'm not a man. The first link is how to install magisk, and the second one is how to update via OTA
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Click to expand...
Click to collapse
Hi,
I'm having a similar issue with the OTA installation after getting magisk root using the Boot Image Patching method. The tutorial shows several different methods, but so far I haven't had luck with any of them. I tried the one for "Devices with A/B Partitions" and got as far as flashing the original boot image back but the OTA still wouldn't install. The flashfire method wouldn't work because flashfire says it isn't compatible with "20.1:MAGISKSU". I didn't touch the recovery partition and I am using the same file I used to create the patched magisk boot image (without the alteration) to try to get back to stock boot image. I'm not sure what else to do aside from using LMSA to reflash stock. My concern with that (aside from having to reconfigure everything) is that I don't have the latest boot.img from the 1-9 firmware to patch it in Magisk and I don't yet know if I can use the 1-6 firmware modified boot.img file.