how to flash patched kernel on google pixel 3 via ADB?
Myoko150 said:
how to flash patched kernel on google pixel 3 via ADB?
Click to expand...
Click to collapse
If you are referring to a Magisk patched kernel, do the following. The name of the img file now has some random letters appended to it.
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
dcarvil said:
If you are referring to a Magisk patched kernel, do the following. The name of the img file now has some random letters appended to it.
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
Click to expand...
Click to collapse
I have a locked bootloader, I cannot use the "fastboot" commands
it would be so simple...
GSI flashing guide for mediatek uplaoded- checkout
Rooting Realme Narzo 30 Pro:
New Method (Android 10 and above)
Go to this link
Also checkout how to flash stock rom if you face any problems such as bootloop:
link
Old Method (Android 11 and below)
Prerequisite :
Unlocked Bootloader
How to unlock bootloader: Phone will be formatted
Backup your data.
Install deeptesting.apk
Open the app and click start applying
Wait for application to be summited and processed
Minimize the app and head over to developer settings and turn on OEM Unlock and USB Debugging
Open deeptesting again and click on start in-depth test, the phone will reboot to bootloader
Connect phone to PC. Open platform-tools folder and type cmd in address bar
Type fastboot flashing unlock
Use volume and power button to select unlock the bootloader
Phone will format and reboot.
Realme Narzo 30 Pro (C.12) :
How to root ? Can cause bootloop or even brick your device
Download boot.img and vbmeta.img
Patch only the boot.img using this version of Magisk
Connect your phone to PC via USB Cable open cmd in platform-tools folder type adb command : adb reboot bootloader
Now your device is in fastboot mode
Firstly flash vbmeta.img file
Command for flashing vbmeta.img : fastboot --disable-verity --disable-verification flash vbmeta drag and drop vbmeta file
Now flash patched boot.image file
Command for flashing boot.img : fastboot flash boot drag and drop patched boot image file
Reboot your device with command : fastboot reboot
Your device is rooted now ╰(*°▽°*)╯
You can uninstall this version of magisk after rebooting and install the latest version
Other Files (C.12) :
Recovery.img
For rooting older versions :
Follow the same procedure, using the files, boot.img and vbmeta.img for specific version.
Extras:
Scatter file :
MT6853 Scatter.txt
Please Share Boot.img Of C.09
Files required for C.09 have been uploaded please check
I think the end command is : fastboot reboot
Ignacius57294 said:
I think the end command is : fastboot reboot
Click to expand...
Click to collapse
Yup
NinjaChunks said:
Yup
Click to expand...
Click to collapse
Ohh nice man you corrected it...
NinjaChunks said:
Files required for C.09 have been uploaded please check
Click to expand...
Click to collapse
Please share files boot.img of c11
please share boot.img of c.11
KIRANKEJITON said:
please share boot.img of c.11
Click to expand...
Click to collapse
It will be posted soon
NinjaChunks said:
Realme Narzo 30 pro (C.011) :
How to unlock bootloader Phone will be formatted :
Backup your data.
Install deeptesting.apk.
Open the app and click start applying.
Wait for application to be summited and processed.
Minimize the app and head over to developer settings and turn on OEM Unlock and USB Debugging.
Open deeptesting again and click on start in-depth test, the phone will reboot to bootloader.
Connect phone to PC. Open platform-tools folder and type cmd in address bar.
Type fastboot flashing unlock.
Use volume and power button to select unlock the bootloader.
Phone will format and reboot.
How to root Can cause bootloop or even hardbrick your device :
Download boot.img and vbmeta.img.( Credit : ashkir05)
Patch only the boot.img using this version of Magisk other versions of Magisk doesn't seem to be working.
Connect your phone to PC via USB Cable open cmd in platform-tools folder type adb command : adb reboot bootloader
Now your device is in fastboot mode
Firstly flash vbmeta.img file.
Command for flashing vbmeta.img : fastboot --disable-verity --disable-verification flash vbmeta drag and drop vbmeta file.
Now flash patched boot.image file.
Command for flashing boot.img : fastboot flash boot drag and drop patched boot image file.
Reboot command: fastboot reboot.
Your device is rooted now ╰(*°▽°*)╯
You can uninstall this version of magisk after rebooting and install the latest version
Other Files (C.011) :
MT6853 Scatter.txt
Recovery.img
For rooting older versions :
Follow the same procedure, just use the files provided for specific version.
Realme Narzo 30 pro (C.09) :
Download boot.img and vbmeta.img.
Other Files (C.09) :
MT6853 Scatter.txt
Recovery.img
Realme Narzo 30 pro (C.08) :
Download boot.img and vbmeta.img.
Other Files (C.08) :
MT6853 Scatter.txt
Recovery.img
Click to expand...
Click to collapse
after flashing boot.img , phone is not booting but it is getting looped into bootloader.
Please help
rizwanp880 said:
after flashing boot.img , phone is not booting but it is getting looped into bootloader.
Please help
Click to expand...
Click to collapse
Go to bootloader and flash stock boot.img
You would used other version of Magisk maybe
Bro how about realme 8 5g?
Please share img files for UI 3.0
It worked very well for c12 and I was also able to flash twrp/pwrp. But UI3.0 ota was not installing thus forced me to revert to stock.
TOPDOG3518 said:
It worked very well for c12 and I was also able to flash twrp/pwrp. But UI3.0 ota was not installing thus forced me to revert to stock
Click to expand...
Click to collapse
Stock boot.img is required for ota. Flash stock boot image then update.
To root again, get the boot.img for the software version your phone is running on and patch with magisk. Flash the patched boot.img and voila you have rooted.
Glad that you did. Any idea about custom rom on Narzo 30 Pro? as Realme excluded this device in her Android 14 update.
I am using Realme 3.0. Any good way to root and unlock bootloader without getting bricked?
Oops! We broke the matrix. Someone call Neo!
getting this error while try to download any file
bootloader unlock
WARNING! THIS WILL VOID YOUR WARRANTY! IF YOU DO NOT KNOW WHAT THIS DOES LEAVE! THERE IS ALMOST NO SUPPORT FOR THIS DEVICE!
go to developer options and turn on oem unlocking
reboot to fastboot
Windows sucks for this because the drivers that you can find will not work!
install linux or in a vm
install fastboot and adb on linux
fastboot command: fastboot reboot bootloader
fastboot command: fastboot flashing unlock
reboot the phone.
you get a "orange" warning device will reboot it self.
done!
Root:
Hello welcome to this root tutorial of the IIIF150 R2022!
WARNING YOU WILL VOID YOUR WARRENTY!
UNLOCK THE BOOTLOADER FIRST!
EASY WAY NOT RECOMMENDED!
1. https://easyupload.io/0e0o5e MAGISK BOOT IMAGE
2. flash magisk boot image with fastboot
3. reboot phone
I DO NOT RECOMMENDED THIS! WHY WOULD YOU TRUST ME? IF YOU TRUST ME DO THE EASY WAY OTHERWISE DO IT YOURSELF!
NORMAL:
1. first download the STOCK os: https://firmwarefile.com/iiif150-r2022
2. download magisk on your device.
3. copy boot.img to your device.
4. follow the steps on magisk. choose the boot.img and let it patch.
5. put the file on your LINUX pc (windows is possible but it sucks because again drivers)
6. put your device in fastboot mode! NOT FASTBOOTD
7. on pc type: fastboot flash boot magiskbootimgname.img
8. YOUR NOT DONE!!!!!!!!!!
--------------
1. type these commands:
fastboot --disable-verity --disable-verification flash vbmeta (vbmeta file name you have download with the stock rom) click enter
fastboot --disable-verity --disable-verification flash vbmeta_system (vbmeta_system file name you have download with the stock rom) click enter
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img (vbmeta_vendor file name you have download with the stock rom) click enter
---------------------------------------------
YOUR NOW DONE.
IT IS POSSIBLE THAT IT DOES NOT WORK THE FIRST TIME IF IT IS STUCK ON BOOTING REFLASH MAGISK BOOT IMG
I've been waiting for this tutorial since November 2021, although I still have some doubts I'll try to do it.
Hello Any chace to have root tutoriel for IIIF150 B2021 ?
thibbea said:
Hello Any chace to have root tutoriel for IIIF150 B2021 ?
Click to expand...
Click to collapse
Use Magisk flash boot img with magisk
Hello,
how can I root my phone with magisk 25.2?
My bootloader is already unlocked.
Thank you very much!
t0bM said:
Hello,
how can I root my phone with magisk 25.2?
My bootloader is already unlocked.
Thank you very much!
Click to expand...
Click to collapse
First,
Find the boot.img of your firmware
Patch it using magisk app
Find a patched vbmeta of your phone's version
Move those to your pc and into the folder where fastboot is found
Reboot to fastboot mode and connect it to your pc
Type fastboot devices to check if it is connected
Type fastboot flash boot nameoffile.img(the boot file name)
Type fastboot flash vbmeta nameoffile.img(the vbmeta file name)
Restart the phone either manually or using fastboot reboot
you should also put this command to avoid bootloop or any problem with booting your phone
fastboot --disable-verity --disable-verification flash vbmeta nameoffile.img(vbmeta file name)
The easiest method is by downloading magisk latest apk from the github and rename it to Magisk.zip and flash it with your custom recovery
I've created a patched boot.img with Magisk and flashed that with Fastboot but after rebooting Magisk still shows that it's not rooted. So I tried flashing the boot.img in Recovery but again after rebooting it's not rooted.
What am I doing wrong?
doveman said:
I've created a patched boot.img with Magisk and flashed that with Fastboot but after rebooting Magisk still shows that it's not rooted. So I tried flashing the boot.img in Recovery but again after rebooting it's not rooted.
What am I doing wrong?
Click to expand...
Click to collapse
The boot.img to patch must be the same as the rom you are using.
Try renaming magisk.apk and magisk.zip and flashing it with Twrp. (You may need to flash vbmeta and use "fastboot flash --disable-verity --disable-verification vbmeta images\vbmeta.img").
NOSS8 said:
The boot.img to patch must be the same as the rom you are using.
Try renaming magisk.apk and magisk.zip and flashing it with Twrp. (You may need to flash vbmeta and use "fastboot flash --disable-verity --disable-verification vbmeta images\vbmeta.img").
Click to expand...
Click to collapse
Yeah, I downloaded the correct ROM (miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip) and extracted the boot.img from that.
Renaming magisk.apk to magisk.zip and flashing it just installs the app doesn't it, it doesn't root the phone as far as I'm aware.
I followed the instructions here, which say that you should only tick the "Patch vbmeta in boot image” option when patching the boot.img in Magisk if the device does NOT have a separate vbmeta partition. The Poco X3 does have a separate vbmeta partition,, so I didn't tick that option.
Installation
The Magic Mask for Android
topjohnwu.github.io
I've tried the "fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img" command with four different versions of fastboot that I've got, dating from 2016 to 2020, and they all reject the "--disable" switches as an "unknown option".
I tried it without those options, so I flashed the patched boot.img and then did "fastboot flash vbmeta vbmeta.img" but after rebooting Magisk still shows that root is not installed.
https://xiaomifirmwareupdater.com/miui/surya/stable/V12.5.4.0.RJGEUXM/
Type: Fastboot
Size: 5.3 GB
Release Date: 2021-11-09
Package Name: surya_eea_global_images_V12.5.4.0.RJGEUXM_20211109.0000.00_11.0_eea_e9805977c3.tgz
NOSS8 said:
https://xiaomifirmwareupdater.com/miui/surya/stable/V12.5.4.0.RJGEUXM/
Type: Fastboot
Size: 5.3 GB
Release Date: 2021-11-09
Package Name: surya_eea_global_images_V12.5.4.0.RJGEUXM_20211109.0000.00_11.0_eea_e9805977c3.tgz
Click to expand...
Click to collapse
OK, I see that the one I downloaded was the 2.7GB recovery version rather than the 5.3GB fastboot version, but isn't the boot.img the same in both?
doveman said:
OK, I see that the one I downloaded was the 2.7GB recovery version rather than the 5.3GB fastboot version, but isn't the boot.img the same in both?
Click to expand...
Click to collapse
Yep, normally, in the current recovery there is only a "payload.bin" file but maybe on old phones the boot.img is present (I don't remember).
Maybe download it and check the imgs in the img folder.
Have you tried with an older or beta version of Magisk?
In case the cmd posted above is generic, the real cmd is:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta vbmeta.img
Check:
https://forum.xda-developers.com/t/...n-vendor-dynamic-partition-enable-rw.4238807/
https://forum.xda-developers.com/t/q-h-safety-way-to-unlock-bootloader-flash-recovery-root.4198719/
NOSS8 said:
Yep, normally, in the current recovery there is only a "payload.bin" file but maybe on old phones the boot.img is present (I don't remember).
Maybe download it and check the imgs in the img folder.
Have you tried with an older or beta version of Magisk?
In case the cmd posted above is generic, the real cmd is:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Yeah, in the "miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip" recovery version, there's a boot.img in the root folder and vbmeta.img (and vbmeta_system.img) in the firmware-update folder.
In the fastboot version, the boot.img is in the images folder but it's the same size (134,217,728) as is vbmeta.img (4,096).
I realised I made a stupid mistake as I was trying to do it in Powershell and it was saying "unknown option -- disable-verity" so it was adding a phantom space between -- and disable-verity. I reflashed the patched boot.img and vbmeta.img using those switches from a command prompt and it flashed them OK, but after rebooting Magisk still says it's not rooted!
doveman said:
Yeah, in the "miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip" recovery version, there's a boot.img in the root folder and vbmeta.img (and vbmeta_system.img) in the firmware-update folder.
In the fastboot version, the boot.img is in the images folder but it's the same size (134,217,728) as is vbmeta.img (4,096).
I realised I made a stupid mistake as I was trying to do it in Powershell and it was saying "unknown option -- disable-verity" so it was adding a phantom space between -- and disable-verity. I reflashed the patched boot.img and vbmeta.img using those switches from a command prompt and it flashed them OK, but after rebooting Magisk still says it's not rooted!
Click to expand...
Click to collapse
What happens if you try to root from the Magisk app?
NOSS8 said:
What happens if you try to root from the Magisk app?
Click to expand...
Click to collapse
The only option in the Magisk app is to root by patching the boot.img, which you then have to flash in fastboot.
I know it used to have an option to root in situ but I think that was removed some time ago.
doveman said:
The only option in the Magisk app is to root by patching the boot.img, which you then have to flash in fastboot.
I know it used to have an option to root in situ but I think that was removed some time ago.
Click to expand...
Click to collapse
No functional TWRP for this device.?
NOSS8 said:
No functional TWRP for this device.?
Click to expand...
Click to collapse
Yeah, I've got TWRP installed. I tried booting into that after flashing in fastboot, as I recall there was an issue once (probably on a different device) where the root wouldn't "stick" if you didn't do that, but it didn't help.
doveman said:
Yeah, I've got TWRP installed. I tried booting into that after flashing in fastboot, as I recall there was an issue once (probably on a different device) where the root wouldn't "stick" if you didn't do that, but it didn't help.
Click to expand...
Click to collapse
Strange case as strange as the number of threads has this subject for this device.
NOSS8 said:
Strange case as strange as the number of threads has this subject for this device.
Click to expand...
Click to collapse
I tried flashing the patched boot.img in TWRP, followed by the vbmeta.img, then I went to Advanced and did the "Fix AVB (vbmeta)". Now the System can't boot at all and it just boots into TWRP every time, so I guess that "Fix AVB (vbmeta)" has screwed something up.
doveman said:
I tried flashing the patched boot.img in TWRP, followed by the vbmeta.img, then I went to Advanced and did the "Fix AVB (vbmeta)". Now the System can't boot at all and it just boots into TWRP every time, so I guess that "Fix AVB (vbmeta)" has screwed something up.
Click to expand...
Click to collapse
This phone is rootable, surely an oversight or an error somewhere.
NOSS8 said:
This phone is rootable, surely an oversight or an error somewhere.
Click to expand...
Click to collapse
I've tried reflashing the patched and the original boot.img and vbmeta.img but it still says "System is destroyed" if I try to boot to System. I don't know what the "Fix AVB" did but it's not good!
doveman said:
I've tried reflashing the patched and the original boot.img and vbmeta.img but it still says "System is destroyed" if I try to boot to System. I don't know what the "Fix AVB" did but it's not good!
Click to expand...
Click to collapse
In case you can always flash a recovery or use Miflash to recover the phone.
To see:
https://www.gizmochina.com/2020/10/13/how-to-unlock-bootloader-and-root-poco-x3-nfc/
NOSS8 said:
In case you can always flash a recovery or use Miflash to recover the phone.
To see:
https://www.gizmochina.com/2020/10/13/how-to-unlock-bootloader-and-root-poco-x3-nfc/
Click to expand...
Click to collapse
I've already got TWRP recovery flashed. I guess I'll have to flash the ROM again and start from scratch.
I tried flashing super.img but that didn't fix it. In the end, going into ADB Sideload mode in TWRP and flashing the 2.7GB recovery version of the ROM with
"adb sideload miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip" fixed it without losing any data.
I still can't root it though. I've tried the "install Magisk (root)" option in TWRP and renaming magisk.apk to magisk.zip and installing that in TWRP, but it still shows "Installed N/A" in Magisk and Root Verifier says "Root permission not granted or Superuser App Missing" but then it says "Superuser App: 25.25:MAGISKSU", so it's the root permission that isn't granted.
Surely that is the problem.
https://techshift.net/what-is-disable-verity/
NOSS8 said:
Surely that is the problem.
https://techshift.net/what-is-disable-verity/
Click to expand...
Click to collapse
I thought so but I've reflashed the patched boot.img and done
"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
and
"fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img"
in case it needed that too, but Magisk still shiows "Installed N/A"
I tried installed SR5-SuperSU-2.82 zip from TWRP to see if that would get it rooted,, but it couldn't even install that, it just gave some error.