Related
#WeirdMoto
Motorola started rolling out September security patch which, you know, fixes Blueborn vulnerability. But instead of starting in India or other Moto's favorite country, they stated rolling it out in Latin America!
Changes:
-September security patch
-Bug fixes
Here you go! https://mega.nz/#!OU10kJAD!V2eW4QoXuGjzlLlct4NG-eQ5NvLru9em0aG8_CrSA9o (sorry because of Mega lol)
Thanks,can someone upload a twrp backup?
Can I flash if my device is rooted and I have TWRP?
ElGranLagarto said:
Can I flash if my device is rooted and I have TWRP?
Click to expand...
Click to collapse
No
ElGranLagarto said:
Can I flash if my device is rooted and I have TWRP?
Click to expand...
Click to collapse
Unlikely - the OTA would possibly fail and also leave you in a TWRP soft bootloop unless you booted to bootloader and then selected 'Start' to boot to system.
As this OTA will only flash on NPJS25.93-14-8 systems (looking at the updater script), the easiest way would be to use the NPJS25.93-14-8 stock ROM to revert to a fully stock device. Of course, this will remove root and TWRP on your device, but OTAs require a clean, unmodified device to work from.
Assuming you are currently on NPJS25.93-14-8 and were fully updated before flashing TWRP and rooting, you may be able to use the following flashing commands with the fastboot stock ROM to revert to stock without affecting your data. These commands are edited assuming your GPT and bootloader are the same patch level as NPJS25.93-14-8. As always, back up your data in case you need to factory reset, and also this depends on your device being formally and fully updated to NPJS25.93-14-8 previously, if not formally updated (including bootloader to B1:06), you may run into issues including a hard brick. If you are not sure, ignore the following flashing commands and fully flash the NPJS25.93-14-8 stock ROM as per in the linked post. Or wait for the TWRP flashable of the NPJS25.93-14-10 system ROM (which only flashes the system side of the build).
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot erase cache
fastboot reboot
The stock ROM for the NPJS25.93-14-8 build is here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
A formally updated system to NPJS25.93-14-8 should include:
Bootloader version at B1:06.
Modem version ending in 62.01R.
Security patch at 1 June 2017.
After this, you should be able to update to NPJS25.93-14-10 via OTA. Needless to say, after you update via OTA, it therefore becomes risky to flash the June 2017 stock ROM or any older ROMs. As we've seen previously, downgrading and then attempting to update via OTA runs a high risk of hard bricking, and it may be the case that the June 2017 blankflash we have no longer works once updated to September 2017. Be careful. If you need to revert back to stock after flashing the September 2017 OTA, wait for the NPJS25.93-14-10 stock ROM.
EDIT - I saw from your previous posts asking about the NPJ25.93-14-8.1 update. If you've updated from NPJ25.93-14 to NPJS25.93-14-8.1, you likely won't be able to flash this update anyway as the expected build is different to what the NPJS25.93-14-10 update is expecting.
For NPJ25.93-14-8.1:
Code:
Package expects build thumbprint of 7.0/NPJ25.93-14-8.1/2:user/release-keys or 7.0/NPJ25.93-14/16:user/release-keys
For NPJS25.93-14-10:
Code:
Package expects build thumbprint of 7.0/NPJS25.93-14-10/10:user/release-keys or 7.0/NPJS25.93-14-8/8:user/release-keys
Successfully installed in my XT1641 with NPJS25.93-14-8. Thanks for capture and upload it.
Hallo, my phone (XT1643) isn't rooted and is NPJS25.93-14-8 running. Is it possible to put the updatefile into the internal storrage and flash it with orig. Motorola Recovery?
How can apply this OTA
How can apply this OTa patch to my Moto g4 plus ...and now my build number is NPJS25.93-14-8 hope it works fine after update this OTA. And let me know how I can apply this OTA
Marv42 said:
Hallo, my phone (XT1643) isn't rooted and is NPJS25.93-14-8 running. Is it possible to put the updatefile into the internal storrage and flash it with orig. Motorola Recovery?
Click to expand...
Click to collapse
Niket03 said:
How can apply this OTa patch to my Moto g4 plus ...and now my build number is NPJS25.93-14-8 hope it works fine after update this OTA. And let me know how I can apply this OTA
Click to expand...
Click to collapse
Similar steps should apply to you both - verify that you have NPJS25.93-14-8 fully updated on your device (e.g. bootloader is version B1:06) and everything is stock and not modified - so no TWRP, root, or custom logo.bin for example. Your recovery should also be the same version that came with the NPJS25.93-14-8 stock ROM/OTA update. Having an unlocked bootloader is not a problem, though if it is unlocked, you should be seeing the unlocked bootloader warning when you boot (from a stock logo.bin).
1)Download the OTA update to your device, likely it'll be in the Downloads folder.
2)Follow these instructions to get to the stock recovery:https://forum.xda-developers.com/showpost.php?p=72981796&postcount=58
3)Once in the stock recovery, select the 'Apply update from SD card' command with the volume keys, press power to use the command.
4)Navigate to your Download folder and find the update.
5)Press power whilst the update is selected to install.
5a)If there's an issue with mounting internal memory, you may try the 'Mount /system' command and attempt to re-select your update.
6)Once the update is finished, you may wish to 'Wipe cache' from the recovery menu. You do not have to factory reset.
7)Once done, you can choose to reboot.
If you choose, you can wait for the OTA update to arrive, which should automate the process for you.
As always, once you've updated, it becomes very risky to downgrade. I'd suggest not to downgrade from the September 2017 stock update if you can (with an older stock ROM), or if you really want to, do not update via OTA. Use an updated stock ROM (Sept 2017 fastboot ROM, which currently we don't have yet) to update if you've downgraded.
Thanks! Applied successfully on my Moto G4 XT1624. Working great as always.
Firmware
Firmware Patch -10
rsdsecure-cloud.motorola.com/download/ATHENE_NPJS25.93-14-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Any changes !!!!! ... It says bug fixes so ......
Updated via OTA in India.
well I am rooted with magisk and custom kernel installed. and I got OTA for updating it, so should I update it via OTA or flash it through fastboot?
Fastboot
siddhesh9146 said:
well I am rooted with magisk and custom kernel installed. and I got OTA for updating it, so should I update it via OTA or flash it through fastboot?
Click to expand...
Click to collapse
You need full stock setup for flashing via an OTA, else it'll fail — that includes recovery, kernel and the ROM. In addition, you can update only a full stock ROM through fastboot, not an OTA.
zeomal said:
You need full stock setup for flashing via an OTA, else it'll fail — that includes recovery, kernel and the ROM. In addition, you can update only a full stock ROM through fastboot, not an OTA.
Click to expand...
Click to collapse
I already flashed it from fastboot; thanks for your help!
siddhesh9146 said:
I already flashed it from fastboot; thanks for your help!
Click to expand...
Click to collapse
Siddesh how to update please tell me
---------- Post added at 11:19 AM ---------- Previous post was at 11:19 AM ----------
siddhesh9146 said:
I already flashed it from fastboot; thanks for your help!
Click to expand...
Click to collapse
Send me d link of stock rom of September patch
usha55 said:
Siddesh how to update please tell me
---------- Post added at 11:19 AM ---------- Previous post was at 11:19 AM ----------
Send me d link of stock rom of September patch
Click to expand...
Click to collapse
Link for the September 2017 stock ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
If you wish to update and try to save your data (provided you were on an earlier stock Motorola build), have a look at the flashing commands in this post: https://forum.xda-developers.com/showpost.php?p=73970028&postcount=251 Else, you'll have to use the flashing commands in the main thread, which will wipe your data, so back up as required. You do not have to relock your bootloader if you do not wish to.
anyone tell me please if i lock oem now can i get normal updates from only im fed up of doing this fastboot,,and 1 more qstion if i lock my bootloader/oem can i unlock it again
---------- Post added at 06:28 PM ---------- Previous post was at 06:26 PM ----------
why because im a hard brick survivor ,now if i unlock oem/bootloader i can update my phone normally from system updates
---------- Post added at 06:30 PM ---------- Previous post was at 06:29 PM ----------
anuone reply me guys
Hello guys,
I have successfully rooted September update with the help of Flashfire. As there is no fastboot images released at the a time of writing this so I have to make use of dual slots of system. This can be adopted for future OTA's as well:
The process requires you to boot into ur previous slot. It mean that after you have updated you phone boots from updated slot but old slot is still there which can be rooted easily.
Now you have boot from old slot
Code:
fastboot set_active x
x means your old slot before update
Now u have to root this slot by flashing patched boot image.
After successful root use flashfire to backup your updated slot's boot and system , u can use any format I recommend use fastboot flashable.
Now you can use backed up boot to flash on updated slot and enable ever root while flashing.
Now you have rooted your updated slot .
Now you can boot into updated slot by using above code with 'x' being your updated slot identifire.
PS.
Stock September Boot
First boot might take long similar to flashing SuperSU via twrp ( it reboots after boot logo appears)
I used this https://forum.xda-developers.com/mi-5x/how-to/root-mia1-twrp-t3678453 to root my August build.
Google Inc said:
Hi how do i confirm whether a or b slot are previous update?
I need to reboot for further checking?
Click to expand...
Click to collapse
U can guess without rebooting in magisk manager, by boot image location
/dev/block/mmcblk0p22 --> means slot A
/dev/block/mmcblk0p23 --> means slot B
Also fast boot commands can be used for that
Sent from my Mi A1 using Tapatalk
m.atif said:
U can guess without rebooting in magisk manager, by boot image location
/dev/block/mmcblk0p22 --> means slot A
/dev/block/mmcblk0p23 --> means slot B
Also fast boot commands can be used for that
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
I guess slot A is August update and slot B is September update...
Reason: We had slot A activated by default so any new update (say September) will be installed in another slot (say B)...
I rebooted to slot A... opened Settings app -- About Phone -- It says August security patch...
Trying your method to root... Will reply back with the results...
thanks a lot bro
I said that bcz if someone flashes fastboot images , slot a is used for flashing by the provided falsh_all.bat file in stock image file.
Fastboot set _active a or b is not working.
Mr.Crucial said:
Fastboot set _active a or b is not working.
Click to expand...
Click to collapse
Use adb tools from chainfire's autoroot zip
Sent from my Mi A1 using Tapatalk
Google Inc said:
Hi how do i confirm whether a or b slot are previous update?
I need to reboot for further checking?
Click to expand...
Click to collapse
Execute this command in fastboot - fastboot getvar all
m.atif said:
Use adb tools from chainfire's autoroot zip
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
Thanks I have rooted my device with september security patch by using different way but got help from your guide
Greetings good friend! Can someone translate this to lay-man-terms coz it's too technical and although I am trying, it's really hard to understand. ???
---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------
Desire 1007 said:
Thanks I have rooted my device with september security patch by using different way but got help from your guide
Click to expand...
Click to collapse
Mate can you elaborate?? Thank you..
melmarPH said:
Greetings good friend! Can someone translate this to lay-man-terms coz it's too technical and although I am trying, it's really hard to understand.
---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------
Mate can you elaborate?? Thank you..
Click to expand...
Click to collapse
Go to fastboot mode.Enter command in ur pc fastboot set active b or a (which will have old firmware)and boot it.Root your old slot containing august security patch using old cf root and install flashfire
in flashfire load the latest magusk or supersu (which you can download from google)(recovery flashable),select new slot and click flash.
Thats all you get your phone rooted with september security patch.
Desire 1007 said:
Go to fastboot mode.Enter command in ur pc fastboot set active b or a (which will have old firmware)and boot it.Root your old slot containing august security patch using old cf root and install flashfire
in flashfire load the latest magusk or supersu (which you can download from google)(recovery flashable),select new slot and click flash.
Thats all you get your phone rooted with september security patch.
Click to expand...
Click to collapse
This doesn't work with Magisk, you get boot loops.
Incidentally, it looks like the developer of Magisk is looking for bootloop logs at https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/page372
I bet if someone could get some Magisk bootloop logs he could get Magisk working on the A1.
mobadass said:
This doesn't work with Magisk, you get boot loops.
Incidentally, it looks like the developer of Magisk is looking for bootloop logs at https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/page372
I bet if someone could get some Magisk bootloop logs he could get Magisk working on the A1.
Click to expand...
Click to collapse
Yeah! I wish I saw your post sooner. Anyway I flashed the stock boot.img of september and the bootloops ceased albeit with no root
mobadass said:
This doesn't work with Magisk, you get boot loops.
Incidentally, it looks like the developer of Magisk is looking for bootloop logs at https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/page372
I bet if someone could get some Magisk bootloop logs he could get Magisk working on the A1.
Click to expand...
Click to collapse
I didn't state a word about magisk, bcz I tried that in August build itself when magisk 14.1 beta was released , it didn't boot so posted about that in magisk thread too, u can't get any logs if the phone restart from splash screen again and again that's bootloop, some kernels have ADB enabled by default in kernel that way we can have logs but it's not possible in stock boot patched by magisk.
Even flashing magisk from flashfire gives same result.
Help!!! Unable to update to September
Hi,
I'm on the August update and I have successfully rooted. But I am unable to install September OTA to update. Can you please advise?
ForTheOne said:
Hi,
I'm on the August update and I have successfully rooted. But I am unable to install September OTA to update. Can you please advise?
Click to expand...
Click to collapse
If u happen to have a unmodified system partion , only flash stock boot.img through fastboot or flashfire (note to disable ever root)
If u have a modified system , them flash system.img from August update fastboot files with boot.img , I will suggest you to do this as you don't know if have modified the system or not (even remounting system bricks OTA). To do so
Code:
fastboot flash system_x system/image/location.img
fastboot flash boot_x boot/image/location.img
x means ur current active slot (a or b)
U can find stock files from miui.com downloads section
Anyine has normal boot.img for october update? or even modified?
any link to stock september boot image?
Download the S251 update package from this link.
Rename the file to update.zip and move it to the root of your SD card (not internal storage). Boot into stock recovery and update.
If you have TWRP, it will not work. If you have root or magisk, it will not work. You need to reflash the S244 boot and recovery images under fastboot using :
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
Do I have to uninstall magisk first ?
Sutcliffe9 said:
Do I have to uninstall magisk first ?
Click to expand...
Click to collapse
You can try that. If the update fails, you'll have to reflash the stock boot image as the update process might detect a modified boot image. Do you have the boot.img file for S244 ?
Thanks, I have the s244 boot image. I will give it a go tomorrow.
Thanks for uploading this.
Hm, update built on the 7th of November but only contains the 1st of November security updates. Google released further updates on the 5th and 6th of November, with the 6th November update fixing the very serious WPA2 'Krack' issues.
At least this update fixes the blueborne stuff.
Sorted ?
Sutcliffe9 said:
Sorted
Click to expand...
Click to collapse
PLease can you sent the right .img file.
I get install failed .
I have no twrp ! i use orijinal recovery from lenovo.
Murtie said:
PLease can you sent the right .img file.
I get install failed .
I have no twrp ! i use orijinal recovery from lenovo.
Click to expand...
Click to collapse
You only have one option. You need to re-install the full S244 ROM from this thread: https://forum.xda-developers.com/lenovo-p2/development/fastboot-files-stock-firmware-t3649914
Follow the steps but DO NOT FLASH USERDATA or you will lose all your existing apps and settings. This will restore your system to stock configuration then you should be able to update.
It worked for me doing this
If you have TWRP, You need to reflash the S244 boot and recovery images under fastboot using :
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
Is there any chance of getting android oreo update bro
somenderjangra said:
Is there any chance of getting android oreo update bro
Click to expand...
Click to collapse
nope.
Sutcliffe9 said:
It worked for me doing this
If you have TWRP, You need to reflash the S244 boot and recovery images under fastboot using :
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
I have doing this but the same error. installation failed
Maybe i have not the right image
Do you have the boot.img file?
---------- Post added at 12:03 PM ---------- Previous post was at 11:59 AM ----------
Im using this stock rom>
[LENOVO P2] [S244] [7.0] [STOCK] Lenovo P2a42 Stock Nougat Update TWRP Flashable by abhayruparel
---------- Post added at 12:03 PM ---------- Previous post was at 12:03 PM ----------
[LENOVO P2] [S244] [7.0] [STOCK] Lenovo P2a42 Stock Nougat Update TWRP Flashable by abhayruparel
Where does this file come from? How can we be sure it is safe? Verified official?
i just want to share a little bit info about installing Twrp Recovery without PC on a Rooted Mi A1 Permanently no matter which Android PIE update you installed.
first download this zip file
( https://www.mediafire.com/download/r3xqno4g9grn2o8 ) extreme kernel
( https://www.androidfilehost.com/?fid=1899786940962576328 ) stock kernel august patch
and install terminal emulator from this zip folder.
then extract boot.img file to root directory of your storage
then open Terminal and enter these cmds.
su
Enter
then
dd if=sdcard/boot.img of=dev/block/bootdevice/by-name/boot_a
Enter
now your TWRP has installed just reboot to recovery to check
(i have just backed up this boot.img from old pie update of my mi a1 that have permanent twrp and extreme kernel installed and i tried this method after flashing stock firmware and then updating it to august security patch and it works fine so i want to share this with others)
Is it gonna work on custom rom with ota update ?
no its for stock pie rom only
Woooooowww thanks brooo
---------- Post added at 09:12 PM ---------- Previous post was at 09:07 PM ----------
gorankx said:
Is it gonna work on custom rom with ota update ?
Click to expand...
Click to collapse
hh
gorankx said:
Is it gonna work on custom rom with ota update ?
Click to expand...
Click to collapse
after boot to recovery u will need to install custom kernal and root and twrp again
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
gorankx said:
Is it gonna work on custom rom with ota update ?
Click to expand...
Click to collapse
U will need to install kernal
ranjodhricky said:
i just want to share a little bit info about installing Twrp Recovery without PC on a Rooted Mi A1 Permanently no matter which Android PIE update you installed.
first download this zip file ( https://www.mediafire.com/download/r3xqno4g9grn2o8 )
and install terminal emulator from this zip folder.
then extract boot.img file to root directory of your storage
then open Terminal and enter these cmds.
su
Enter
then
dd if=sdcard/boot.img of=dev/block/bootdevice/by-name/boot_a
Enter
now your TWRP has installed just reboot to recovery to check
(i have just backed up this boot.img from old pie update of my mi a1 that have permanent twrp and extreme kernel installed and i tried this method after flashing stock firmware and then updating it to august security patch and it works fine so i want to share this with others)
Click to expand...
Click to collapse
Can be done through fastboot
I tried installing recovery from CMD but getting error cannot find such directory
I have just unlocked bootloader only twrp and and magisk has not been installed yer
you have to root your device first or you can flash it with fastboot.
hey i uploaded a new boot.img file with stock kernel of August update and permanent TWRP
( https://www.androidfilehost.com/?fid=1899786940962576328 )
download from [ Mediafire ] if you want extreme kernel with Twrp and if you want permanent Twrp with Stock kernel then download from [ Androidfilehost ]
Hello guys,
i saw there some questions about TWRP and android 10. So far you cant boot TWRP on android 10. It doesnt matter Q BETA DP4, 5 or OB1.
Mauronofrio is already informed about that. There is some work needed to fix that.
But there is a way to flash TWRP with Magisk! I already posted that a few times in TWRP thread and opened this thread now. So it's easier to find it.
You will need to have magisk on your phone to do this!
UPDATING FROM ANDROID 9:
1. Install Android 10 trough local Updater AND DONT REBOOT HERE
2. Flash TWRP trough Magisk
3. Install magisk to inaktiv Slot (after OTA)
4. REBOOT NOW
With OB1 it also works the usual way:
1. Boot into TWRP and Flash OB1
2. Flash TWRP Installer.zip
3 Reboot directly into recovery
4. Flash Magisk and reboot system
COMING WITH ANDROID 10 NON ROOT:
1. Extract the boot.img of payload.bin inside the update.zip (use this tool for it LINK <--- thanks @tidschi)
2. Patch the boot.img with Magisk
3. Flash it with fastboot and reboot
4. Flash TWRP with magisk
5. Install Magisk and reboot
COMING WITH ANDROID 10 AND ROOT:
1. Flash TWRP with magisk
2. Install magisk and reboot
Thanks @tidschi for correcting me (patching boot.img) and screenshot
Kollachi said:
Hello guys,
i saw there some questions about TWRP and android 10. So far you cant boot TWRP on android 10. It doesnt matter Q BETA DP4, 5 or OB1.
Mauronofrio is already informed about that. There is some work needed to fix that.
But there is a way to flash TWRP on it before booting into android 10 system! I already posted that a few times in TWRP thread and opened this thread now. So it's easier to find it.
All you need is magisk installed on your phone to do this!
1. Install Android 10 trough local Updater AND DONT REBOOT HERE
2. Flash TWRP trough Magisk
3. Install magisk to inaktiv Slot (after OTA)
4. REBOOT NOW
I tried it myself and it worked great. There are some users who confirmed its working.
Click to expand...
Click to collapse
Thanks for guide. So I am now in op1 without root and twrp. I assume I have to downgrade to 9.5.8, there flash twrp and magisk, than install op1 again and flash twrp etc as you write?
Marek.N said:
Thanks for guide. So I am now in op1 without root and twrp. I assume I have to downgrade to 9.5.8, there flash twrp and magisk, than install op1 again and flash twrp etc as you write?
Click to expand...
Click to collapse
No, just patch boot.img from OB1 with Magisk.
Afterwards flash patched boot.img with fastboot and after that you can flash TWRP with Magisk.
---------- Post added at 08:35 PM ---------- Previous post was at 08:34 PM ----------
Kollachi said:
Yes. So far there is no other way.
Click to expand...
Click to collapse
Sure there is, see above
tidschi said:
No, just patch boot.img from OB1 with Magisk.
Afterwards flash patched boot.img with fastboot and after that you can flash TWRP with Magisk.
---------- Post added at 08:35 PM ---------- Previous post was at 08:34 PM ----------
Sure there is, see above
Click to expand...
Click to collapse
ok thanks will try tomorrow
Kollachi said:
Sure but first you will need to have a patched boot.img
Click to expand...
Click to collapse
You said it's not possible, but it is?!
Where is the problem to extract ROM with payload dumper and patch boot.img with Magisk?
I see no problem here... definitely less work then going back to PIE...
Marek.N said:
ok thanks will try tomorrow
Click to expand...
Click to collapse
Please report if its working with patched boot.img.
I dont have the device anymore.
tidschi said:
You said it's not possible, but it is?!
Where is the problem to extract ROM with payload dumper and patch boot.img with Magisk?
I see no problem here... definitely less work then going back to PIE...
Click to expand...
Click to collapse
Yes i forgot about it. Lol
Kollachi said:
Please report if its working to flash TWRP with patched boot.img.
I dont have the device anymore.
Click to expand...
Click to collapse
It will, did this with latest DP, because it wasn't possible to boot TWRP with fastboot.
Was the only way in that case.
---------- Post added at 08:44 PM ---------- Previous post was at 08:43 PM ----------
Kollachi said:
Please report if its working to flash TWRP with patched boot.img.
I dont have the device anymore.
Click to expand...
Click to collapse
Kollachi said:
Yes i forgot about it. Lol
But as i said... First you will need to patch it. But if you dont have magisk installed on your phone good luck. There is someone needed to do that for you.
Click to expand...
Click to collapse
No...you just need Magisk Manager and stock boot.img...
tidschi said:
It will, did this with latest DP, because it wasn't possible to boot TWRP with fastboot.
Was the only way in that case.
---------- Post added at 08:44 PM ---------- Previous post was at 08:43 PM ----------
No...you just need Magisk Manager and stock boot.img...
Click to expand...
Click to collapse
Ah ok thanks. Never did it that way.
Kollachi said:
Ah ok thanks. Never did it that way.
Click to expand...
Click to collapse
Np, was for me also first time to do it this way.
Everyone can extract stock boot.img from payload file with this tool:
https://androidfilehost.com/?fid=818070582850510260
Then simple flash the extracted boot.img with Magisk and flash with fastboot.
tidschi said:
Np, was for me also first time to do it this way.
Everyone can extract stock boot.img from payload file with this tool:
https://androidfilehost.com/?fid=818070582850510260
Then simple flash the extracted boot.img with Magisk and flash with fastboot.
Click to expand...
Click to collapse
I have updated the OP now. Thanks dude. (Danke für das Korrigieren!)
Little notice, as said before:
You need to extract with payload dumper the boot.img from payload.bin from ROM ZIP file.
Thanks for the guide @Kollachi
I am rooted and TWRP is installed, latest Pie Update. Can't I just download the Android 10 OB1 and flash this in TWRP? Afterwards, flash TWRP Zip and Magisk to preserve all this?
Lupus77 said:
I am rooted and TWRP is installed, latest Pie Update. Can't I just download the Android 10 OB1 and flash this in TWRP? Afterwards, flash TWRP Zip and Magisk to preserve all this?
Click to expand...
Click to collapse
No you need to update from settings in OOS.
Then go to Magisk and install to inactive slot and reboot.
If you want to have TWRP again, install as Module with Magisk after reboot.
Lupus77 said:
I am rooted and TWRP is installed, latest Pie Update. Can't I just download the Android 10 OB1 and flash this in TWRP? Afterwards, flash TWRP Zip and Magisk to preserve all this?
Click to expand...
Click to collapse
You could try that. I don't have that device anymore.
Just found this in OP7 Pro forum: https://forum.xda-developers.com/oneplus-7-pro/how-to/android-q-4th-developer-preview-t3953997
How to update/install with root(TWRP):
*MAKE SURE TO HAVE EVERY MAGISK MODULE DISABLED BEFORE YOU DO THIS*
1. Download the open beta, magisk and TWRP installer
2. Copy the zip to the storage
3. Boot TWRP and decrypt
4. Flash open beta
5. Flash TWRP Installer
6. Reboot recovery
7. Flash Magisk
8. Reboot and enjoy!
I am gonna try this. This is what I did on my OP5 for a long time and I am more comfortable this way.
Lupus77 said:
Just found this in OP7 Pro forum: https://forum.xda-developers.com/oneplus-7-pro/how-to/android-q-4th-developer-preview-t3953997
How to update/install with root(TWRP):
*MAKE SURE TO HAVE EVERY MAGISK MODULE DISABLED BEFORE YOU DO THIS*
1. Download the open beta, magisk and TWRP installer
2. Copy the zip to the storage
3. Boot TWRP and decrypt
4. Flash open beta
5. Flash TWRP Installer
6. Reboot recovery
7. Flash Magisk
8. Reboot and enjoy!
I am gonna try this. This is what I did on my OP5 for a long time and I am more comfortable this way.
Click to expand...
Click to collapse
You can't boot into TWRP with Android 10 for now.
I know, but I am still on Pie. Will do this to update to OB1. Then I hope a new TWRP will be released soon
Edit: Worked like a charm. Can also still boot into TWRP recovery.
So finally I am rooted, so than I have to go to fastboot and flash twrp img? And then flash magisk in twrp?
EDIT: That doesn´t work, IDK how to install twrp without fastboot