Database Info

[GUIDE] How to root Nougat on Moto G4 Plus [UPDATED for NPJ25.93-11/12/14]

** WARNING **
If you are on NPJ25.93-11/12/14 (non-soak test Nougat), you MUST flash the ElementalX kernel (link) after step 4. Make sure to backup the stock kernel before proceeding.
I'm glad we're among the first ones to get updated to Nougat but what about root? Just follow this guide and enjoy!
Before starting
An unlocked bootloader is required.
Download Fastboot and install/extract it to a folder.
Download TWRP and put it in the same folder as fastboot.
Download phh's SuperUser (thread) zip file, open the zip file and then inside you will find config.txt. The default content is
Code:
eng verity crypt
change it to
Code:
eng noverity nocrypt
and save. Copy this zip file to your phone afterwards.
Steps
Power off your device.
Boot into bootloader mode (Vol Down + Power).
Connect your phone to your PC with USB and flash TWRP using the following command:
Code:
fastboot.exe flash recovery twrp-3.0.2-0-athene.img
Boot into TWRP by using volume buttons to navigate and power button to select "Recovery Mode".
Install/flash superuser.zip within TWRP.
Reboot.
Install the phh's SuperUser app from Play Store.
Enjoy your root!

Is stable twrp?
Enviado desde mi Moto G (4) mediante Tapatalk

Did any one tried it did it worked?
Sent from my Moto G4 Plus using Tapatalk

HerH2 said:
Is stable twrp?
Click to expand...
Click to collapse
TWRP is stable as usual.
VN_bunny said:
Did any one tried it did it worked?
Click to expand...
Click to collapse
Works fine for me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

doomed151 said:
TWRP is stable as usual.
Works fine for me
Click to expand...
Click to collapse
Nice!
Enviado desde mi Moto G (4) mediante Tapatalk

i flashed this supersu along with systemless root method. but there is no supersu app in drawer.

srgudhka said:
i flashed this supersu along with systemless root method. but there is no supersu app in drawer.
Click to expand...
Click to collapse
7. Install the Superuser app from Play Store.
Click to expand...
Click to collapse
You need to install the app from Play Store. Also, this is not SuperSU, this is phh's SuperUser.
When I tried rooting with SuperSU, it broke Wi-Fi and mobile network.

Works perfect on 1642

doomed151 said:
You need to install the app from Play Store. Also, this is not SuperSU, this is phh's SuperUser.
When I tried rooting with SuperSU, it broke Wi-Fi and mobile network.
Click to expand...
Click to collapse
lol my bad. got too excited and forgot to read that step xD

works like charm
only thing needed is to observe the steps carefully. enjoying root on nougat now.. thanks a million.. button pressed too..

What about xposed?

GuSoares said:
What about xposed?
Click to expand...
Click to collapse
Not available yet.

Or you can go full systemless using Magisk and phh superuser module.
http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Stuff like adaway are also working fine.
Edit: typo

I unlocked my bootloader and installed TWRP from post. I'm with a XT1626, and not worked for me.
I have done all steps correctly 3 times, but no lucky.
Im TWRP it shows that supersu have been installed but when i open root checker, it is not rooted.
What to do now? I have not tried to reinstall 7.0 rom because i don't know how. I think i need to wipe rom and lock bootloader? Any tips?
In CPU-Z Shows "Yes" for root, but when i check root it says "Root Access Not Installed Properly". When i try to install BusyBox it says that i'm not rooted

Did you really flash phh's SuperUser (superuser.zip) instead of SuperSU?

GuSoares said:
I unlocked my bootloader and installed TWRP from post. I'm with a XT1626, and not worked for me.
I have done all steps correctly 3 times, but no lucky.
Im TWRP it shows that supersu have been installed but when i open root checker, it is not rooted.
What to do now? I have not tried to reinstall 7.0 rom because i don't know how. I think i need to wipe rom and lock bootloader? Any tips?
In CPU-Z Shows "Yes" for root, but when i check root it says "Root Access Not Installed Properly". When i try to install BusyBox it says that i'm not rooted
Click to expand...
Click to collapse
Did you do step #7?

doomed151 said:
Did you really flash phh's SuperUser (superuser.zip) instead of SuperSU?
Click to expand...
Click to collapse
For sure
SoNic67 said:
Did you do step #7?
Click to expand...
Click to collapse
Yes, it was the First thing i have done when rebooted my phone after flashing phh's SuperSU in TWRP. I used all files provided here too. I have no clue what to do to make it work

actually i unlocked bootloader and flashed twrp after updating to android n what happened was after flashing recovery the device was always rebooting in twrp mode only i dont know why even rebooting to system was not working so i flashed beanstalk rom and that worked the mobile rebooted properly so i guess after updating to android n and then flashing recovery might not work

There is no point in flashing TWRP if you plan to stick with the stock Nougat. I just boot in TWRP, but not flash it.

Please, rename the step #7 from "SuperUser app" to "phh's SuperUser" Ahahaha! i was with wrong app
Now rooted! Thanks mate

My steps update to October patch

My Mi A1 is unlocked by MiFlash stock rom and rooted by ghpranav's AIO Tool. It has updated to September patch and with FlashFire + SuperSu.
The followings is my steps update to October patch,
1. Download ravinder0003's CF auto root boot.img and copy it into adb folder.
2. Connect Mi A1 with PC,
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot getvar all
3. Slot b is current active slot in my phone which has September patch and rooted. Slot a is unrooted.
Code:
fastboot set_active a
fastboot reboot
4. Reboot system into slot a. After reboot, system update to October patch, the patch will be updated into slot b.
My update patch is huge size, 1060.5MB. As we konw the patch should be 118MB from September to October, I don't know why my size is so huge. Maybe because I deleted some media file and systme apps after I updated September patch in slot b before.
5. Auto reboot after success update and I got bootloop on Mi logo.
6. Press Volume down + Power buttons to enter fastboot mode.
7. Reboot system into updated slot b.
Code:
fastboot set_active b
fastboot reboot
8. System has updated to October patch. Then get root,
Code:
fastboot boot boot.img
Waiting auto reboot in several minutes, be patience.
Open FlashFire app to confirm whether system get rooted.
That's all and for your reference.

rockice said:
Code:
fastboot getvar all
Click to expand...
Click to collapse
This command is very helpful, thanks! :good:

90180360 said:
This command is very helpful, thanks! :good:
Click to expand...
Click to collapse
what does that command do?

robgee789 said:
what does that command do?
Click to expand...
Click to collapse
You can see which partition is active.
Sent from my Mi A1 using Tapatalk

NITRO_100 said:
You can see which partition is active.
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
Cheers mate
Sent from my Mi A1 using Tapatalk

Can't turn on wifi to update to october patch
after setting active_x and rebooting updater app says switch to other sim and wifi isn't working.
Can anyone help?

Hey guys if I have partition b set as active can I use fast boot to partition a as active and go back to the September update?
Sent from my Mi A1 using Tapatalk

robgee789 said:
Hey guys if I have partition b set as active can I use fast boot to partition a as active and go back to the September update?
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
Before I update system, I forgot to check which month's patch in my slot a. So when I update to October patch in slot b, I don't know which patch is in my slot a now.
In your case, if October patch is in your slot b, September patch is in slot a, when you boot to slot a, of coursre you go back to September patch.

Hey I just bought the A1 and installed the October update before doing anything. But now I want to root or flash TWRP, what steps should I take? Can't find anyone with Oct patch to help me.

rodsayd said:
Hey I just bought the A1 and installed the October update before doing anything. But now I want to root or flash TWRP, what steps should I take? Can't find anyone with Oct patch to help me.
Click to expand...
Click to collapse
Unlock your phone first.
And October update patched root image file click here .

Will I need to reflash everything that works on the system partition as well ? (For example, Xposed, Viperaudio, GLTools, etc)

I am stuck in a boot loop. I tried to update from September to October image using miflash. When it was in September build it was rooted and I installed Xposed. I am waiting from 1hr still it's in boot loop. Plz help.

vedkamath said:
I am stuck in a boot loop. I tried to update from September to October image using miflash. When it was in September build it was rooted and I installed Xposed. I am waiting from 1hr still it's in boot loop. Plz help.
Click to expand...
Click to collapse
I suggest you download stock rom from here and MiFlash it with "Save User Data" option.
So you get October build, then unlock and root your system next.

rockice said:
I suggest you download stock rom from here and MiFlash it with "Save User Data" option.
So you get October build, then unlock and root your system next.
Click to expand...
Click to collapse
Thanks a lot for the reply bro. I flashed the October image from official MIUI site which you provided along with latest miflash but still getting bootloop. One thing I observed is that after flashing stock my bootloader automatically getting locked. I unlocked the bootloader and flashed the stock image again, still getting bootloop. Tried in both slot a and b. Technically it should work, don't know why it's not working. Any help would be greatly appreciated.

set_active command is missing from my fastboot.

P4P3RB4G said:
set_active command is missing from my fastboot.
Click to expand...
Click to collapse
Use the latest revision: https://dl.google.com/android/repository/platform-tools-latest-windows.zip

rockice said:
I suggest you download stock rom from here and MiFlash it with "Save User Data" option.
So you get October build, then unlock and root your system next.
Click to expand...
Click to collapse
Does someone have an answer why I had the latest version (rooted) and always asking to update?! [emoji848]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://techintouch.it

Latest Build ist 7.10.30

tidschi said:
Latest Build ist 7.10.30
Click to expand...
Click to collapse
In the Xiaomi site it's the 7.10.14..
http://techintouch.it

Chazy12 said:
In the Xiaomi site it's the 7.10.14..
http://techintouch.it
Click to expand...
Click to collapse
Latest Full ROM it's! OTA is 7.10.30 as told before...

How to root oreo

Bonjour,
I have problems after rooting (like camera app stops to work)
I enabled OEM debug,
flash twrp-3.2.1-1-herolte.img.tar,
format data,
reboot recovery,
flash no-verity-opt-encrypt-6.0.zip,
and Magisk-v16.4(1642).zip
Thank you for your help

Is TWRP / SuperSU updated for Oreo yet?

fred.eric said:
Bonjour,
I have problems after rooting (like camera app stops to work)
I enabled OEM debug,
flash twrp-3.2.1-1-herolte.img.tar,
format data,
reboot recovery,
flash no-verity-opt-encrypt-6.0.zip,
and Magisk-v16.4(1642).zip
Thank you for your help
Click to expand...
Click to collapse
I work with odin rode oreo rum. I am installing TWRP, but TWRP is not opening. When I want to turn on TWRP with the help of 3 keys, the device has its own recovery.

*Detection* said:
Is TWRP / SuperSU updated for Oreo yet?
Click to expand...
Click to collapse
From what I understood, TWRP version 3.2 is only fro OREO ROMS
for SuperSU, some people recommend to use Magisk instead

mpasa said:
I work with odin rode oreo rum. I am installing TWRP, but TWRP is not opening. When I want to turn on TWRP with the help of 3 keys, the device has its own recovery.
Click to expand...
Click to collapse
Do you use odin 3.13.1?

fred.eric said:
Do you use odin 3.13.1?
Click to expand...
Click to collapse
yes I am using Odin 3.13.1. I'm flashing TWRP 3.2.1.1

mpasa said:
yes I am using Odin 3.13.1. I'm flashing TWRP 3.2.1.1
Click to expand...
Click to collapse
do you check OEM unlock under Developer options?

fred.eric said:
do you check OEM unlock under Developer options?
Click to expand...
Click to collapse
OEM with unlocking and USB debugging turned on.

mpasa said:
OEM with unlocking and USB debugging turned on.
Click to expand...
Click to collapse
And there is noting in odin logs?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

very strange

After installing the S7 G930f device oreo stock rum I can not TWRP. I am installing TWRP 3.0.24 or 3.2.1.1 with Odin and the PASS writer is also opening the device itself. Then when I want to enter TWRP with 3 keys, the following error occurs when I come to the menu and factory reset. I can not upload Custom rom for this. There is a different way you can install custom rom.
Developer options on, OEM unlock on, System auto update, USB debug on
I have a brief knowledge of you. Before Oreo TWRP was established and I was using custom ROMs. Then I downloaded the BTU stock oreo and set it up with ODIN. But I can not TWRP. It seems to be installed but it does not open when the file is not found when opening its own recoverysi. There is a screen display. It even gives me an error when I run samsung share. Access is denied. because of unauthorized change. But I just made a new one. Also, when I run Samsung Pass, the root directory of your device is accessed. can not be used. But I have re-established the stock rom with ODIN and give these mistakes.
translation of mistakes given in the screen image of the first message
fail to open recovery_caIuse (No such file or directory)
reboot recovey cause unknown
No support Single-sku
Successfully verified dmverity hash tree
E: failed to clear BCB message: fail to find / misc partition

I found a solution.
first I installed BTU 7.0 with Odin. I turned off the phone and installed TWRP 3.0.2.4 with ODIN. TWRP was turned on when the phone was turned on as a solid recovery after it was turned on. I formatted and erased all the data. and Ambassadii's latest oreo roman.

fix twrp /data access
After reading this thread [ROM][8.0.0] Dylan's S7 Oreo ROM V4 https://forum.xda-developers.com/galaxy-s7/development/rom-dylan-s-s7-oreo-rom-t3784715
I used SuperSU instead of Magisk and no-verity-opt-encrypt-6.0.zip works

fred.eric said:
After reading this thread [ROM][8.0.0] Dylan's S7 Oreo ROM V4 https://forum.xda-developers.com/galaxy-s7/development/rom-dylan-s-s7-oreo-rom-t3784715
I used SuperSU instead of Magisk and no-verity-opt-encrypt-6.0.zip works
Click to expand...
Click to collapse
can you please upload the ( no-verity-opt-encrypt-6.0.zip ) as I can't find it any more on the internet and also please if there is any special TWRP for rooting the S7 oreo version .
thanks in advance

machhho said:
can you please upload the ( no-verity-opt-encrypt-6.0.zip ) as I can't find it any more on the internet and also please if there is any special TWRP for rooting the S7 oreo version .
thanks in advance
Click to expand...
Click to collapse
Please go here for the files and guide you require
https://techbeasts.com/how-to-root-galaxy-s7-s7-edge-on-android-oreo/

machhho said:
can you please upload the ( no-verity-opt-encrypt-6.0.zip ) as I can't find it any more on the internet and also please if there is any special TWRP for rooting the S7 oreo version .
thanks in advance
Click to expand...
Click to collapse
I found no-verity-opt-encrypt on https://build.nethunter.com/samsung-tools/
TWRP is a recovery tool. To root your S7, you will need Magisk or SuperSU

[RECOVERY] OFFICIAL TWRP for Asus Zenfone Max Pro M2 (X01BD)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer
Code:
/**
* What you do with your device is your choice.
* None of the developers of this software will be held accountable for any damages to your device or to third parties.
* You should know this by now.
**/
What's this?
This is TeamWin Recovery Project for our Asus Zenfone Max Pro M2 (X01BD)
Known Issues
None
Requirements
Unlocked bootloader
Computer/Laptop
Common sense and a X01BD
Downloads
https://twrp.me/asus/asuszenfonemaxprom2.html
https://github.com/kubersharma001/twrp_device_asus_X01BD/releases/download/v1.0/recovery.img
XDA:DevDB Information
TeamWin Recovery, Tool/Utility for the Asus Zenfone Max Pro M2
Contributors
kubersharma, bauuuuu
Version Information
Status: Stable
Created 2019-04-01
Last Updated 2019-07-11

UNOFFICIAL/PERSONAL BUILDS:
https://sourceforge.net/projects/kubersharma001/files/X01BD/TWRP/
About TWRP:
https://twrp.me/about/
Frequently Asked Questions
Q1 How to flash the recovery image?
A1. Via Fastboot or if you are already in TWRP, then flash the twrp image in recovery partition.
Read FAQs here: https://twrp.me/FAQ/
Sources
twrp_device_source: https://github.com/kubersharma001/twrp_device_asus_X01BD
kernel_source: https://github.com/ArrowOS-Devices/...tree/91f4373a4141cf43379882fa115c7bb51e090ecc
twrp manifest: https://github.com/minimal-manifest-twrp

Superb, Good to know this. This is the most stable recovery for our device, thanks.

Awesome ?

Nice Work
Edit : Just Tried to Flash Stock Oreo along with Decrypt Zip but it is Still Encrypting the Storage

Right now my device is on PBRP
How can I install TWRP now?

Vishurules28 said:
Right now my device is on PBRP
How can I install TWRP now?
Click to expand...
Click to collapse
Via Fastboot mode,
boot your device in fastboot, put recovery.img with adb and fastboot files and run following command
Code:
fastboot flash recovery (recovery name).img

nice_guy75 said:
Via Fastboot mode,
boot your device in fastboot, put recovery.img with adb and fastboot files and run following command
Click to expand...
Click to collapse
Thanks but I found another way
Flashed TWRP as img from PBRP install menu. TWRP was installed successfully.

Stock recovery persisting
Even though I got all OKs on flashing recovery, I still boot into STOCK recovery. IMPORTANT QUESTION: Is this recovery file compatible with the PIE UPDATE?
My Zenfone M2 PRO is on Pie since last week, and I unlocked the bootloader recently with Asus official bootloader unlocker. Help is appreciated.

TheKing88 said:
Even though I got all OKs on flashing recovery, I still boot into STOCK recovery. IMPORTANT QUESTION: Is this recovery file compatible with the PIE UPDATE?
My Zenfone M2 PRO is on Pie since last week, and I unlocked the bootloader recently with Asus official bootloader unlocker. Help is appreciated.
Click to expand...
Click to collapse
Use the twrp from telegram group..that one is working fine.

Thank you my man!! I got it working

I was able to encrypt the device....but when I try to decrypt it always says wrong password...Am I missing anything??

shravankoppesetty said:
I was able to encrypt the device....but when I try to decrypt it always says wrong password...Am I missing anything??
Click to expand...
Click to collapse
Same with me

Hey guy's, TWRP for X01BD is now OFFICIAL!
https://twrp.me/asus/asuszenfonemaxprom2.html
Enjoy

Can we flash the software OS provided in the ASUS website ??
Can we downgarde from pie to oreo provided by Asus in website.?

finally. it's official. thanks you so much.

Vishurules28 said:
Thanks but I found another way
Flashed TWRP as img from PBRP install menu. TWRP was installed successfully.
Click to expand...
Click to collapse
You have X01BD or X01BDA? I have X01BDA, can I flash this official TWRP recovery?
@kubersharma, can I use this official TWRP on X01BDA as well?

nice_guy75 said:
You have X01BD or X01BDA? I have X01BDA, can I flash this official TWRP recovery?
@kubersharma, can I use this official TWRP on X01BDA as well?
Click to expand...
Click to collapse
Yes you can. I have a X01BDA too. The difference is that X01BDA has nfc and X01BD do not.

Decryption not working in Evolution-X ROM, anyone else can confirm the same?

nice_guy75 said:
You have X01BD or X01BDA? I have X01BDA, can I flash this official TWRP recovery?
@kubersharma, can I use this official TWRP on X01BDA as well?
Click to expand...
Click to collapse
Yes, you can.
mauam said:
Yes you can. I have a X01BDA too. The difference is that X01BDA has nfc and X01BD do not.
Click to expand...
Click to collapse
Oh, didn't know that but i don't think it's true since I've seen the X01BDA model in India without NFC as well but i am not sure

[FASTBOOT] [daisy] Patched boot.img for V11.0.10.0 (Android 10)

I followed my usual guide to upgrade...
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
The August update is 11.0.10.0. I have a patched boot with Magisk 20.4
https://yasmar.net/xda/patched_boot_11.0.10.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_11.0.10.0.img.gz

Can you tell how to to update I have only magisk Installed I want to keep magisk.

Aadil Gillani said:
Can you tell how to to update I have only magisk Installed I want to keep magisk.
Click to expand...
Click to collapse
The Magisk thread has the process.
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
You don't need a PC because Magisk backs up the vanilla boot and restores it.
It's TWRP that comlicates otas.

a1291762 said:
The Magisk thread has the process.
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
You don't need a PC because Magisk backs up the vanilla boot and restores it.
It's TWRP that comlicates otas.
Click to expand...
Click to collapse
I only have Magisk and tried the process in the link but I'm always getting the "Couldn't update, installation problem" error. Can I update my phone by simply flashing the patched boot image?

elvinguitar said:
I only have Magisk and tried the process in the link but I'm always getting the "Couldn't update, installation problem" error. Can I update my phone by simply flashing the patched boot image?
Click to expand...
Click to collapse
No, but you may be able to install the OTA if you flash the vanilla image for your version.
The update process tells you which partitions are modified. Details in my guide.
Or just flash the whole rom.

a1291762 said:
No, but you may be able to install the OTA if you flash the vanilla image for your version.
The update process tells you which partitions are modified. Details in my guide.
Or just flash the whole rom.
Click to expand...
Click to collapse
Will I lose my data by flashing the vanilla image?

elvinguitar said:
Will I lose my data by flashing the vanilla image?
Click to expand...
Click to collapse
Flashing a boot image won't lose data unless you use the wrong version and get unlucky.
Flashing any of the partitions that the OTA touches won't lose data.

a1291762 said:
The Magisk thread has the process.
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
You don't need a PC because Magisk backs up the vanilla boot and restores it.
It's TWRP that comlicates otas.
Click to expand...
Click to collapse
I've unlocked my bootloader and I've read through the guide a few times now, but there's one thing I need to know before I begin. I'm running stock Android 10 build 11.0.10.0 only having the bootloader unlocked.
Am I able to flash the patched boot.img for V11.0.10.0 that you linked in your other post straight away without having installed any other boot.img previously?
I've only ever flashed Samsungs and a few Sony phones and I'd like to be thorough without cocking up.

RyanCM said:
I've unlocked my bootloader and I've read through the guide a few times now, but there's one thing I need to know before I begin. I'm running stock Android 10 build 11.0.10.0 only having the bootloader unlocked.
Am I able to flash the patched boot.img for V11.0.10.0 that you linked in your other post straight away without having installed any other boot.img previously?
I've only ever flashed Samsungs and a few Sony phones and I'd like to be thorough without cocking up.
Click to expand...
Click to collapse
Yes...
If you flash a patched boot.img then Magisk won't have a backup and you can't OTA without flashing the vanilla image. That's why the standard process is to boot the patched image and then use Magisk Manager to install Magisk.
If you're going to install TWRP then you need to install it before Magisk. There is no flashable TWRP, only the installer, and it trashes Magisk. You must use Magisk Manager to install Magisk after TWRP (or flash it from TWRP) since they both live on the same partition.

a1291762 said:
Yes...
If you flash a patched boot.img then Magisk won't have a backup and you can't OTA without flashing the vanilla image. That's why the standard process is to boot the patched image and then use Magisk Manager to install Magisk.
If you're going to install TWRP then you need to install it before Magisk. There is no flashable TWRP, only the installer, and it trashes Magisk. You must use Magisk Manager to install Magisk after TWRP (or flash it from TWRP) since they both live on the same partition.
Click to expand...
Click to collapse
Thank you. All I want to do for the meantime is root and try out Magisk. I just wasn't sure if I was able to flash the patched .img without needing to flash anything beforehand.
Hopefully I don't make a mistake here and will come back to this thread once I've succeeded/messed up.
---------- Post added at 05:02 AM ---------- Previous post was at 04:24 AM ----------
RyanCM said:
Thank you. All I want to do for the meantime is root and try out Magisk. I just wasn't sure if I was able to flash the patched .img without needing to flash anything beforehand.
Hopefully I don't make a mistake here and will come back to this thread once I've succeeded/messed up.
Click to expand...
Click to collapse
I successfully flashed the patched boot.img and installed Magisk Manager and the only options I have are to flash a zip in recovery (I don't have recovery, hindsight) and "select and patch a file". I don't know how to proceed with either of those options.
EDIT: When flashing the patched boot.img, I didn't realise I had to flash both A/B partitions and that is why it said Magisk wasn't installed. I'm now fully rooted and Magisk is installed.

RyanCM said:
EDIT: When flashing the patched boot.img, I didn't realise I had to flash both A/B partitions and that is why it said Magisk wasn't installed. I'm now fully rooted and Magisk is installed.
Click to expand...
Click to collapse
That's why the standard way is to BOOT the patched image and use Magisk Manager to install.
If you want to flash partitions, you need to use the correct set (a or b). Fastboot can tell you (getvar current-slot). Flashing both is useless, since the inactive set of partitions is only used when doing OTA (or dual boot, for some brave souls).
If you're coming from phones without a/b partitions you should definitely read about them. Several things are quite different.

Please help me boot sign.img unsing img kar do please a kar na ka leya pc ka zaroorat
Please help me boot sign.img unsing img kar do please a kar na ka leya pc ka zaroorat hai mara pass pc nahe ha bootsign.img file link=https://drive.google.com/file/d/1Q172DYs7t7bIo0K_LENCO1OAo6tg0FTz/view?usp=drivesdk and video how to boot sign.img unsing img link=https://youtu.be/ZWphK23KLew

a1291762 said:
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_11.0.10.0.img.gz
Click to expand...
Click to collapse
Offline ... can you please reup?

networxpsc said:
Offline ... can you please reup?
Click to expand...
Click to collapse
It's hosted on Google drive. It just loaded for me (private window to simulate anon user). The preview won't work because it's not that kind of file. Just click download.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}