Database Info

Root your One Hyper

Here is one thing you should know before proceeding: Android 10 has new fastbootd and the latest Android Platform Tool is required to get fastbootd support.
Download your version https://developer.android.com/studio/releases/platform-tools
Tested on -7 RETUS and it worked after few trial and error
You must unlock bootloader first (and your phone is wiped during process)
Extract boot.img from full ROM and patch with Magisk Manager, and copy the patched boot.img back to host computer
Now here are the steps:
Enter bootloader (power the phone off, press and hold volume down while power your phone back on, and you should see bootloader screen
Now connect your One Hyper to host computer and enter
Code:
fastboot reboot fastboot
You will see something looks like stock recovery but it has fastbootd on the top.
From there, you can flash patched boot.img as you used to.
Reboot when it's done

CTSProfile and BasicIntegrity false, any ideas?

Space_Dog said:
CTSProfile and BasicIntegrity false, any ideas?
Click to expand...
Click to collapse
It's probably the version. I have same situation

mingkee said:
Here is one thing you should know before proceeding: Android 10 has new fastbootd and the latest Android Platform Tool is required to get fastbootd support.
Download your version https://developer.android.com/studio/releases/platform-tools
Tested on -7 RETUS and it worked after few trial and error
You must unlock bootloader first (and your phone is wiped during process)
Extract boot.img from full ROM and patch with Magisk Manager, and copy the patched boot.img back to host computer
Now here are the steps:
Enter bootloader (power the phone off, press and hold volume down while power your phone back on, and you should see bootloader screen
Now connect your One Hyper to host computer and enter
Code:
fastboot reboot fastboot
You will see something looks like stock recovery but it has fastbootd on the top.
From there, you can flash patched boot.img as you used to.
Reboot when it's done
Click to expand...
Click to collapse
What is this FastbootD? Something new on Android 10, cause the Pixel 4 has it too...

AndroidManager2020 said:
What is this FastbootD? Something new on Android 10, cause the Pixel 4 has it too...
Click to expand...
Click to collapse
It's Android 10 way to flash boot, recovery, dtbo, vbmeta, and super
The interface is more like stock recovery with fastbootd on the top

mingkee said:
It's Android 10 way to flash boot, recovery, dtbo, vbmeta, and super
The interface is more like stock recovery with fastbootd on the top
Click to expand...
Click to collapse
I totally understand the concept but what different between regular fastboot, mfastboot, and fastbootD?

mingkee said:
Here is one thing you should know before proceeding: Android 10 has new fastbootd and the latest Android Platform Tool is required to get fastbootd support.
Download your version https://developer.android.com/studio/releases/platform-tools
Tested on -7 RETUS and it worked after few trial and error
You must unlock bootloader first (and your phone is wiped during process)
Extract boot.img from full ROM and patch with Magisk Manager, and copy the patched boot.img back to host computer
Now here are the steps:
Enter bootloader (power the phone off, press and hold volume down while power your phone back on, and you should see bootloader screen
Now connect your One Hyper to host computer and enter
Code:
fastboot reboot fastboot
You will see something looks like stock recovery but it has fastbootd on the top.
From there, you can flash patched boot.img as you used to.
Reboot when it's done
Click to expand...
Click to collapse
For the retail channel on my device, should be LARET which had (2) Builds, the latest being (XT2027-1_DEF_RETLA_10_QPFS30.103-12-5-2_subsidy-DEFAULT_regulatory-XT2027-1-SUTEL-DS_CFC.xml.zip) i'll change to RETAIL after i receie the device. I am worried about getting OTAs later then Brazil/LA Channels.. There are NO RETAIL Firmware Packages for the Retail Channel Device. I guess ill have to see what model it is, Purchased from Amazon, which is where I got my G8+ for a CHEAP $205.83 and as soon as i went to reorder a replacement, price jumped $75, like amazon knew i was going to reorder the same device. Then i came across the one hyper and for a few $$$$ more, specs and chipset are better, same exact specs as the Zoom and the Hyper ran me $314 and the Zoon is like $394.00 I Just need something new to keep me busy until the Edge+ is released....and currently also a Pixel 4 XL (Trying to trade for a LG V60 thinq with the Dual Screen. ) Pixel is 1 month old, 1.5 months at the most, OEM Box, OEM accessories ONLY EVER USED, a couple cases.
Been a Android user since 2010, never had an LG Android. Wait, i had the V40/V50 for under 12 hrs and hated it. it felt cheap and clunky.... But i feel in love with this V60. And i also have (2) Moto G7 aka River. My Moto Def should be here tuesday hopefully. See how quick i can brick this one Moto G8+ was bricked on day one but i pulled out of it using a brand new Levovo Upgrade Tool!

Magisk install
I cannot find on XDA if we can or cannot install Magisk on the XT2027-1 ( One Hyper )
I found a few other sites on the internet that say it can be installed
BUT I tend to err on the side of caution.
I do not want to nuke this phone.
Is this a possibility to install Magisk or not?
I use Viper4 Android and a few other apps like blockada and such
Finally, IF Magsik is installed, I cannot get OTA updates, correct?
Can I uninstall Magisk, update OTA, then reinstall Magisk?
Thank you all

jharkness316 said:
I cannot find on XDA if we can or cannot install Magisk on the XT2027-1 ( One Hyper )
I found a few other sites on the internet that say it can be installed
BUT I tend to err on the side of caution.
I do not want to nuke this phone.
Is this a possibility to install Magisk or not?
I use Viper4 Android and a few other apps like blockada and such
Finally, IF Magsik is installed, I cannot get OTA updates, correct?
Can I uninstall Magisk, update OTA, then reinstall Magisk?
Thank you all
Click to expand...
Click to collapse
Have run into issues......... Damn Windows update restarted computer in middle of night before I was to finish rooting.
I can get into bootloader and when I try to flash I am stuck in bootloop
I get the following errors:
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
Sending 'vbmeta_a' (4 KB) OKAY [ 0.016s]
Writing 'vbmeta_a' (bootloader) WARNING: vbmeta_a anti rollback downgrade, 0 vs 5
OKAY [ 0.000s]
Finished. Total time: 0.016s
Ideas on how to fix? This was flashing back the ORIGINAL stock rom
---------- Post added at 07:57 AM ---------- Previous post was at 07:11 AM ----------
FIXED Rescue and Smart Assistant from Lenovo fixed it

Got it fixed thanks to Rescue and Search program from Motorola
Would like to know since TWRP is not working with the One Hyper, is there a way that I can make a master rom backup via ADB or FASTBOOTD?
If so, can someone make a batch file or list all the things to backup this rom?
I would greatly appreciate it. Thank you

I have my Magisk installed on my Hyper and all is working well. I just got Moto trying to download and update a patch (assuming Google security update). It could not update obviously.
My question is how can I UNinstall magisk , all the modules, and then update my Hyper?
Now if I uninstall magisk I will lose root, correct?
This is the rom I am currently using........DEF_RETAIL_QPFS30.103-47-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC

jharkness316 said:
I have my Magisk installed on my Hyper and all is working well. I just got Moto trying to download and update a patch (assuming Google security update). It could not update obviously.
My question is how can I UNinstall magisk , all the modules, and then update my Hyper?
Now if I uninstall magisk I will lose root, correct?
This is the rom I am currently using........DEF_RETAIL_QPFS30.103-47-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Click to expand...
Click to collapse
in order to take updates you would need to restore the stock boot image with fastboot or magisk, and then update your device, then take the new boot image from the downloaded update and patch with magisk and then flash it to regain magisk root, you do not need to uninstall magisk or the modules but you will need to restore stock boot partitions to allow the device to not error out during the install process. This is how it has been in the past for magisk official guides can be found on magisk website here: https://topjohnwu.github.io/Magisk/ota.html

[deleted]

[Guide] Unlocking Bootloader and Disabling VerifiedBoot

Code:
/* Your warranty is now void (or isn't ? who am I to judge ?) */
Finally, we got a shiny DeepTesting.apk that compatible with Realme 6 Pro.
Thanks to @barakcodam for leaking it, and @Rizezky for providing a Google Drive mirror of it.
Disclaimer
This tutorial requires adb and fastboot installed on your computer. So, you should prepare it first. How to install them ? google it according to your os (Windows/Linux/BSD/Mac).
Unlocking bootloader will wipe your data, backup it first.
Due to Android 10 Dynamic Partition, there's no fully-working TWRP available yet. So the only way to root your phone is patching boot.img through Magisk Manager. You can grab boot.img from Flashable Stock ROM .ozip
Unlocking Bootloader
download the deeptesting.apk for Realme 6 Pro : https://drive.google.com/file/d/16az-7SHoPyJhDIi4p4x7wj1cRUcsPwCM/view
open it and apply for in-depth test
Go to Developer options, enable OEM unlock and USB debugging
open In-depth test again and tap "Query verification status" on the top corner
tap "Start the in-depth test", and you'll will reboot to bootloader
on your computer, open cmd/terminal, and type :
Code:
fastboot flashing unlock
on your phone, select "yes". now your phone will reboot and data is being wiped, and you have unlocked bootloader.
Disabling Verified Boot
In order to boot a custom boot-partition (for magisk or custom kernel purposes) or custom recovery, you have to disable verified boot, otherwise you can't boot to the OS.
download vbmeta.img in the attachment
on your computer, open cmd/terminal, and type :
Code:
adb reboot bootloader
after entering fastboot, type :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Now you can flash your custom boot.img and it'll boot just fine.

nullxception said:
Code:
/* Your warranty is now void (or isn't ? who am I to judge ?) */
Finally, we got a shiny DeepTesting.apk that compatible with Realme 6 Pro.
Thanks to @barakcodam for leaking it, and @Rizezky for providing a Google Drive mirror of it.
Disclaimer
This tutorial requires adb and fastboot installed on your computer. So, you should prepare it first.
How to install them ? google it according to your os (Windows/Linux/BSD/Mac).
Unlocking bootloader will wipe your data, backup it first.
Unlocking Bootloader
download the deeptesting.apk for Realme 6 Pro : https://drive.google.com/file/d/16az-7SHoPyJhDIi4p4x7wj1cRUcsPwCM/view
open it and apply for in-depth test
Go to Developer options, enable OEM unlock and USB debugging
open In-depth test again and tap "Query verification status" on the top corner
tap "Start the in-depth test", and you'll will reboot to bootloader
on your computer, open cmd/terminal, and type :
Code:
fastboot flashing unlock
on your phone, select "yes". now your phone will reboot and data is being wiped, and you have unlocked bootloader.
Disabling Verified Boot
In order to boot a custom boot-partition (for magisk or custom kernel purposes) or custom recovery, you have to disable verified boot, otherwise you can't boot to the OS.
download vbmeta.img in the attachment
on your computer, open cmd/terminal, and type :
Code:
adb reboot bootloader
after entering fastboot, type :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Now you can flash your custom boot.img and it'll boot just fine.
Click to expand...
Click to collapse
Ah thank you...
Already tried with flashing disable DM verity but it failed and make me need to flash original boot.img file.
How can I so stupid not to flash vbmeta.img?
And yes, with this method I can confirm root with Magisk run smoothly.
:good::good::good:

What is your widevine level after that?

Maciejbbb said:
What is your widevine level after that?
Click to expand...
Click to collapse
L3 of course

nullxception said:
L3 of course
Click to expand...
Click to collapse
Is it reversible or can you hide it with magisk module like on some phones?

Maciejbbb said:
Is it reversible or can you hide it with magisk module like on some phones?
Click to expand...
Click to collapse
Reversible ? I don't know, can't confirm that.
Also there's still no patched widevine module that works for realme6pro.

Stock boot image is around 65 mb in size. But patched_boot.img with magisk is only 13.2 mb in size. So will it cause any damage when flashing patched boot image?

Muhammed159753 said:
Stock boot image is around 65 mb in size. But patched_boot.img with magisk is only 13.2 mb in size. So will it cause any damage when flashing patched boot image?
Click to expand...
Click to collapse
No, that 65mb is size of the whole partition block, not the actual size of the whole files inside of it.
If you try to manually unpack the boot.img, and then repack it, the size will go down to around that.

@AT nullexception Thanks for your reply. So Can I flash magisk patched boot image after flashing vbmeta.img? Will my phone get bootloop?

Stuck in Bootloader,
Does anyone has patched boot.img, as i unlocked the Bootloader then disabled the verification , flashed vbmeta.img, Installed TWRP and from TWRP flashed magisk.zip but now phone only boots to bootloader.
Do i need to flash back to stock or there is any other solution so i can get Root ?

Unable to find Patched Boot Img also No where to be found stock Firmware in "MBN" format as MSMdownloadtool is asking for Id and password.

SignatureBoy said:
Unable to find Patched Boot Img also No where to be found stock Firmware in "MBN" format as MSMdownloadtool is asking for Id and password.
Click to expand...
Click to collapse
Here my boot image files magisk_patched

SignatureBoy said:
Stuck in Bootloader,
Does anyone has patched boot.img, as i unlocked the Bootloader then disabled the verification , flashed vbmeta.img, Installed TWRP and from TWRP flashed magisk.zip but now phone only boots to bootloader.
Do i need to flash back to stock or there is any other solution so i can get Root ?
Click to expand...
Click to collapse
/////////////////////////////
Which version of magisk.zip did you flash?

Muhammed159753 said:
/////////////////////////////
Which version of magisk.zip did you flash?
Click to expand...
Click to collapse
20.1
---------- Post added at 08:51 PM ---------- Previous post was at 08:49 PM ----------
Felix Siahaan said:
Here my boot image files magisk_patched
Click to expand...
Click to collapse
Thank you so much but i am afraid to flash it again as it was really hard to revive it back i had to send it to Service center, and pretended that the newest update has done all issues.
They were not agreeing to flash as bootloader was unlocked then after so many request they agreed and said do not update the fone to lastest update.
Boot loader is unlocked so tell me how can i do the root session STEP BY STEP please
and also if you have the MBN version of the stock rom then give me the link as MSMDOWNLOADTOOL does not work without Paid ID and Password.

nullxception said:
Code:
/* Your warranty is now void (or isn't ? who am I to judge ?) */
Finally, we got a shiny DeepTesting.apk that compatible with Realme 6 Pro.
Thanks to @barakcodam for leaking it, and @Rizezky for providing a Google Drive mirror of it.
Disclaimer
This tutorial requires adb and fastboot installed on your computer. So, you should prepare it first. How to install them ? google it according to your os (Windows/Linux/BSD/Mac).
Unlocking bootloader will wipe your data, backup it first.
Due to Android 10 Dynamic Partition, there's no fully-working TWRP available yet. So the only way to root your phone is patching boot.img through Magisk Manager. You can grab boot.img from Flashable Stock ROM .ozip
Unlocking Bootloader
download the deeptesting.apk for Realme 6 Pro : https://drive.google.com/file/d/16az-7SHoPyJhDIi4p4x7wj1cRUcsPwCM/view
open it and apply for in-depth test
Go to Developer options, enable OEM unlock and USB debugging
open In-depth test again and tap "Query verification status" on the top corner
tap "Start the in-depth test", and you'll will reboot to bootloader
on your computer, open cmd/terminal, and type :
Code:
fastboot flashing unlock
on your phone, select "yes". now your phone will reboot and data is being wiped, and you have unlocked bootloader.
Disabling Verified Boot
In order to boot a custom boot-partition (for magisk or custom kernel purposes) or custom recovery, you have to disable verified boot, otherwise you can't boot to the OS.
download vbmeta.img in the attachment
on your computer, open cmd/terminal, and type :
Code:
adb reboot bootloader
after entering fastboot, type :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Now you can flash your custom boot.img and it'll boot just fine.
Click to expand...
Click to collapse
will u help me in unlocking the bootloader for vivo iqoo3 i have tried everything for unlocking the bootloader but i have not got any success with that
kindly give the reply as early as possible

kkrraazzyy said:
will u help me in unlocking the bootloader for vivo iqoo3 i have tried everything for unlocking the bootloader but i have not got any success with that
kindly give the reply as early as possible
Click to expand...
Click to collapse
1. Don't quote the whole post
2. With such brands like vivo, you have no choice but stay locked forever

To deactivate verify boot every time patched vbmeta need to flash. Is it ok to flash same vbmets v2 for all future updates
Thans

nullxception said:
1. Don't quote the whole post
2. With such brands like vivo, you have no choice but stay locked forever
Click to expand...
Click to collapse
Is it ok to flash same vbmets v2 for all future updates

Not working on A25

Will this work on all versions of the realme 6 pro?
I've got the rmx2063 version and I want to root it with magisk' will I be able to do it after doing this?
Many thanks

How To Guide Root Edge 2021 with Magisk

I finally did it last weekend. It's pretty straightforward and it's no difference from other Moto phones I rooted.
Definitely, bootloader MUST be unlocked. A new purchased phone must wait 96 hours to have OEM unlock toggled.
You should have Lenovo RSA installed which also has needed driver installed. Get the latest ROM from RSA and let it run rescue (phone will be wiped, but bootloader unlock wiped the phone anyway). Doing this in order to grab boot.img from C:\Program Data\RSA\Download\Romfiles\.
You will lose Widevine L1 after bootloader unlocked. Stop if it matters to you.
Are you ready? Let's do it
1. Unlock the bootloader if you didn't do it. The way to get "oem get_unlock_data" is to use mark on command window and copy 5 lines of code and paste on notepad, and make it into one line. Submit to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
You should get the code in few minutes over email. Then use this below:
Code:
fastboot oem unlock (code received from email)
(your phone will be wiped]
To enter bootloader. Turn the phone off (make sure you make a backup and copied files to host computer) then press and hold volume down and power buttons.
2. Patch boot.img. After bootloader unlocked, you can stay on bootloader screen and run RSA rescue. Doing this to make your phone up to date as well as getting boot.img. Your phone will be wiped again during the process.
Now you have to do initial setup and install Magisk. Copy the boot.img to the phone and patch it, and copy the patched_boot.img back to host computer.
You can get USNF, fox Magisk Module Manager, Adaway, and other modules if you want.
3. Post root process. You should re-enable USB debug and allow the host computer.
Enter fastbootd
Code:
adb reboot fastboot
or
Code:
fastboot reboot fastboot
Flash patched_boot
Code:
fastboot flash boot
Press space once to make a space, drag and drop patched_boot into command window, and press enter.
Since 24.1, Magisk has different approach to hide/deny.
Enable Zygisk, enforce deny list, install USNF as module (don't worry about GMS because USNF takes care of it).
Put any app can detect root on deny list and reboot everytime you updated the list
Happy rooting

This is my first time rooting an android phone, so thank you. Perhaps I might suggest you add some more details to the "patch boot.img" section, as it took me some extra looking about before I figured out what I was doing.
Thankfully it's pretty simple, I just had to download the Magisk apk from its official github repo onto the phone (post step 1), transfer over the downloaded "boot.img" that the lenovo RSA app downloads during its rescue process (it tells you were it downloads it in the app), over to the phone (usb file transfer), patch "boot.img" on the phone using the Magisk app (install > pick file > done!), transfer back over the newly patched image (stored in downloads) to pc, and then use the above instructions to `fastboot flash boot /path/to/your_patched_boot.img` when the phone is once again put into fastboot mode.
Okay maybe that isn't super simply explained, but I wanted to write it down so others might benefit.
Thank you again, I now have my phone rooted, and will be looking into various things I can do with it, such as degoogling, TWRP (if it's even available for this phone), etc.
---
As far as I know, there is no TWRP yet pre-made for this phone. Unless I'm mistaken, I'd have to manually compile TWRP for my phone? (Not exactly sure how to go about that.)
Also, any tips for a newbie like me?

Can anyone confirm if using the magisk patched boot.img method works tho? Because unless you plan on actually using a custom rom or GSI you don't need twrp anymore for magisk, at least that's my experience with the moto Edge(2020) racer retus. Edit: I'ma dummy, literally the post above this answered my question lmao, I'm currently using a work phone from Samsung because I got my 2020 moto edge hardbricked in edl mode and typical Samsung didn't load everything lmao

ninjakira said:
Can anyone confirm if using the magisk patched boot.img method works tho? Because unless you plan on actually using a custom rom or GSI you don't need twrp anymore for magisk, at least that's my experience with the moto Edge(2020) racer retus. Edit: I'ma dummy, literally the post above this answered my question lmao, I'm currently using a work phone from Samsung because I got my 2020 moto edge hardbricked in edl mode and typical Samsung didn't load everything lmao
Click to expand...
Click to collapse
Yes, this is how I did mine

Rooting Tecno LC8. or tecno power pro 2.

I recently got my hands on Tecno LC8 and am amazed by how good it is. Sadly its a bit hard to root BUT I have done necessary work for all of you.
### Instructions
1. Update to LC8-H6215ABCD-Q-GL-220402V350
2. connect to a laptop/pc with adb tools installed.
3. type in terminal adb reboot fastboot
4. When phone start in fastboot mode (It comes with a animation of usb cable with bluish glow)
5. Type in terminal
fastboot flash vbmeta_vendor vbmeta.img
fastboot flash vbmeta_system vbmeta.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
6. Install Magisk.apk from their release page https://github.com/topjohnwu/Magisk/releases/
7. Enjoy
Now time for cons
- This your whole system may or maynot be formatted. I invite for anyone to confirm it.
- SafetyNet works?????? Idk and can neither confirm it. again I invite for anyone to confirm it. This device is for very specific purpose
- TWRP? I can make it yes. But please just no I am providing with recovery image. If you wanna have a go at it go for it. It will be highly appreciated.
- You wanna go full AOSP on this device??
I already tried it. GSI project treble is comaptible with device "x64 ab partition img" But dual sim support is wonky. Flashlight won't work readily My advice is to extract the mediatek sim processor and replace it with GSI google sim processor and whole mediatek tree.
BUT if you have only one sim card go wild you can install GSI on nearly mediatek device with project treble support.
If you wanna install custom rom without TWRP.
Do this
[WARNING ROOT NEEDED]
fastboot delete-logical-partition product
fastboot flash system [your custom rom file location]
fastboot -w
fastboot reboot
Tecno LC8 support "x64ab partition" images.

Thanks YOU , About to follow your steps , I was direct here from https://www.hovatek.com/forum/thread-42975-post-232022.html#pid232022

Harfho said:
Thanks YOU , About to follow your steps , I was direct here from https://www.hovatek.com/forum/thread-42975-post-232022.html#pid232022
Click to expand...
Click to collapse
so the commad that works for me was
fastboot flash boot boot.img
fastboot flash boot.img does not work ,
error getting was
unknown partition 'boot.img'
fastboot: error: cannot determine image filename for 'boot.img'

Harfho said:
so the commad that works for me was
fastboot flash boot boot.img
fastboot flash boot.img does not work ,
error getting was
unknown partition 'boot.img'
fastboot: error: cannot determine image filename for 'boot.img'
Click to expand...
Click to collapse
Thanks for bringing it to my attention. command should be
fastboot flash boot boot.img
I will correct it asap

Carnalthot said:
Thanks for bringing it to my attention. command should be
fastboot flash boot boot.img
I will correct it asap
Click to expand...
Click to collapse
is there any way I can contact you I have more phone I needed to root, I just want you to explain HOWTO and what NOTO do
I have infinix S5Lite
infinix Hot 9
That I want to root also

Harfho said:
is there any way I can contact you I have more phone I needed to root, I just want you to explain HOWTO and what NOTO do
I have infinix S5Lite
infinix Hot 9
That I want to root also
Click to expand...
Click to collapse
I have no problem teaching you.
I do things thrifty. I preferrably use linux to root basically. BUT windows is also pretty good to root android you need platform tools and adb.
the sure fire way to root chinese phones is
1. Unlock bootloader
2. Open flashing privileges (FRP unlock, unlocking phones etc different company calls it differently)
3. Have an understanding of boot verifiers (vbmeta stands for verify boot metadata ) Nowadays phone verifies boot image by vbmeta_product vbmeta_vendor and vbmeta itself
You have to make all of them blank so nothing verifies your boot image on start up
I suggest downloading a firmware of your phone model to understand the partitions system of your phone model
4. Extract your boot image and vbmeta with mtkclient
5. Now patch your boot image. You can do it by hand or by magisk.
6. Flash every vbmeta with blank-vbmeta and boot with patched_boot
7. TWRP is optional DON'T do it if you have only one phone. Always have backup if you want to touch recovery partition
WHAT TO LOOK OUT FOR
1. update versions. Chinese Kernel update are very sensitive to version numbers. Don't flash v290 boot.img on v350 boot.img. It will brick instantanously.
2. Always learn how to flash your phone model. It saves a lot of headache.
3. Don't be afraid to ask for help.
4. Don't be afraid to throw your phone in anger. No no Seriously. To root a phone is to insist on ownership and if phone denies that it is totally reasonable to obliterate the said phone. I actually mean the last advice.

So can i use the
Carnalthot said:
I have no problem teaching you.
I do things thrifty. I preferrably use linux to root basically. BUT windows is also pretty good to root android you need platform tools and adb.
the sure fire way to root chinese phones is
1. Unlock bootloader
2. Open flashing privileges (FRP unlock, unlocking phones etc different company calls it differently)
3. Have an understanding of boot verifiers (vbmeta stands for verify boot metadata ) Nowadays phone verifies boot image by vbmeta_product vbmeta_vendor and vbmeta itself
You have to make all of them blank so nothing verifies your boot image on start up
I suggest downloading a firmware of your phone model to understand the partitions system of your phone model
4. Extract your boot image and vbmeta with mtkclient
5. Now patch your boot image. You can do it by hand or by magisk.
6. Flash every vbmeta with blank-vbmeta and boot with patched_boot
7. TWRP is optional DON'T do it if you have only one phone. Always have backup if you want to touch recovery partition
WHAT TO LOOK OUT FOR
1. update versions. Chinese Kernel update are very sensitive to version numbers. Don't flash v290 boot.img on v350 boot.img. It will brick instantanously.
2. Always learn how to flash your phone model. It saves a lot of headache.
3. Don't be afraid to ask for help.
4. Don't be afraid to throw your phone in anger. No no Seriously. To root a phone is to insist on ownership and if phone denies that it is totally reasonable to obliterate the said phone. I actually mean the last advice.
Click to expand...
Click to collapse
So i can use this vbmeta for other china phones ,
The hard things is getting boot.img
I’m on limited plan , to download heavy files just to get boot.img out of it is a concern for me.

Harfho said:
So can i use the
So i can use this vbmeta for other china phones ,
The hard things is getting boot.img
I’m on limited plan , to download heavy files just to get boot.img out of it is a concern for me.
Click to expand...
Click to collapse
Hmm you need to get boot.img from your own phone by using mtkclient application. Downloading firmware is to understand about the partition system of your phone. ALWAYS use your own phone boot.img

Carnalthot said:
Hmm you need to get boot.img from your own phone by using mtkclient application. Downloading firmware is to understand about the partition system of your phone. ALWAYS use your own phone boot.img
Click to expand...
Click to collapse
So i can use this vbmeta for other china phones?
and am stock on this on mtkclient
Power off the phone before connecting.
For brom mode, press and hold vol up, vol dwn, or all hw buttons and connect usb.
For preloader mode, don't press any hw button and connect usb.
If it is already connected and on, hold power for 10 seconds to reset.

Harfho said:
So i can use this vbmeta for other china phones?
and am stock on this on mtkclient
Power off the phone before connecting.
For brom mode, press and hold vol up, vol dwn, or all hw buttons and connect usb.
For preloader mode, don't press any hw button and connect usb.
If it is already connected and on, hold power for 10 seconds to reset.
Click to expand...
Click to collapse
Yes you can use vbmeta for other china phone it's blank vbmeta.
And you are right on money for Brom mode. Preloader mode is hit and trial method for Chinese phones

Carnalthot said:
Yes you can use vbmeta for other china phone it's blank vbmeta.
And you are right on money for Brom mode. Preloader mode is hit and trial method for Chinese phones
Click to expand...
Click to collapse
Sorry I don’t get this
“And you are right on money for Brom Mode.”

Harfho said:
Sorry I don’t get this
“And you are right on money for Brom Mode.”
Click to expand...
Click to collapse
To access Brom mode you need to either remove battery/power off phone then while holding volume up/down button connect the usb cable with pc. PC should be listening for any Brom connections when you connect the phone.

Carnalthot said:
To access Brom mode you need to either remove battery/power off phone then while holding volume up/down button connect the usb cable with pc. PC should be listening for any Brom connections when you connect the phone.
Click to expand...
Click to collapse
I Did that to no avail

Harfho said:
I Did that to no avail
Click to expand...
Click to collapse
Did you do frp unlock?

No, i have not

Do a frp unlock without it you cannot flash.
Actually to root your phone you don't need Brom mode

Carnalthot said:
Do a frp unlock without it you cannot flash.
Actually to root your phone you don't need Brom mode
Click to expand...
Click to collapse
Yes, wanted to get the boot.img of the phone first and patched it , so i can run all the commands at once.
oR without unlock bootloader I can’t get the boot.img with mtkclient?

Harfho said:
Yes, wanted to get the boot.img of the phone first and patched it , so i can run all the commands at once.
oR without unlock bootloader I can’t get the boot.img with mtkclient?
Click to expand...
Click to collapse
To get boot.img you need frp unlock.

Carnalthot said:
To get boot.img you need frp unlock.
Click to expand...
Click to collapse
Ok thanks, I will do that.
frp unlock also mean bootloader unlock?

Harfho said:
Ok thanks, I will do that.
frp unlock also mean bootloader unlock?
Click to expand...
Click to collapse
Nope

[HELP] Google Pixel 3 stuck on factory reset after unlocking bootloader

Hi,
I am incredibly new to this and I think I might have managed to destroy this google pixel I just bought. I had attempted to root the phone using magisk after unlocking the bootloader and installing TWRP though I had a little bit of trouble, I was following instructions here https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/. I managed to unlock the bootloader but after signing in to the phone again and attempting to install TWRP to get magisk It wouldn't let me access most of my downloads on the phone because TWRP was asking for a password for my user. I tried the passcode I had set but I didn't work I tried rebooting the phone and removing the lock but many apps on the phone once I booted it back no longer worked, specifically settings which is how I was planning on removing the password. I also tried using adb commands to wipe the lock but nothing really seemed to be working so I found a factory reset setting on TWRP and now I have been stuck at the google reset screen for about 5 hours now. Any help is appreciated.
Thanks

ajg32 said:
Hi,
I am incredibly new to this and I think I might have managed to destroy this google pixel I just bought. I had attempted to root the phone using magisk after unlocking the bootloader and installing TWRP though I had a little bit of trouble, I was following instructions here https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/. I managed to unlock the bootloader but after signing in to the phone again and attempting to install TWRP to get magisk It wouldn't let me access most of my downloads on the phone because TWRP was asking for a password for my user. I tried the passcode I had set but I didn't work I tried rebooting the phone and removing the lock but many apps on the phone once I booted it back no longer worked, specifically settings which is how I was planning on removing the password. I also tried using adb commands to wipe the lock but nothing really seemed to be working so I found a factory reset setting on TWRP and now I have been stuck at the google reset screen for about 5 hours now. Any help is appreciated.
Thanks
Click to expand...
Click to collapse
What do you mean by "remove the lock" and "wipe the lock"? If you relocked the bootloader, your recovery options are limited. Can you access the phone with adb and/or fastboot? If the bootloader is still unlocked, flash a stock factory image available at https://developers.google.com/android/images. Instructions for flashing are at that URL.
If your bootloader is now locked, can you get to fastboot? If not, I don't know of anything you can do. If you can get to fastboot, you can try to sideload a full OTA image from https://developers.google.com/android/ota. Instructions are at that URL.
If you can recover, forget rooting with TWRP - those instructions are outdated. Just install the Magisk app, and use it to patch boot.img, then flash the patched boot.img. If you need TWRP for other purposes, do not install it, just boot it with "fastboot boot twrp.img".
Never lock the bootloader unless you have a completely stock device. Even then, you risk bricking the phone.

dcarvil said:
What do you mean by "remove the lock" and "wipe the lock"? If you relocked the bootloader, your recovery options are limited. Can you access the phone with adb and/or fastboot? If the bootloader is still unlocked, flash a stock factory image available at https://developers.google.com/android/images. Instructions for flashing are at that URL.
If your bootloader is now locked, can you get to fastboot? If not, I don't know of anything you can do. If you can get to fastboot, you can try to sideload a full OTA image from https://developers.google.com/android/ota. Instructions are at that URL.
If you can recover, forget rooting with TWRP - those instructions are outdated. Just install the Magisk app, and use it to patch boot.img, then flash the patched boot.img. If you need TWRP for other purposes, do not install it, just boot it with "fastboot boot twrp.img".
Never lock the bootloader unless you have a completely stock device. Even then, you risk bricking the phone.
Click to expand...
Click to collapse
Sorry for the lack of clarity. The bootloader was still unlocked I was simply trying to access files in the TWRP menu but I had to enter the pin I put on the phone. When I mentioned that I was trying to remove the lock it was so that I could use the file manager to install through the TWRP menu. I believe the bootloader is still unlocked but I simply cannot really communicate with the phone. It is on, but its suck on a google logo with a loading bar. Aside from adb commands which don't seem to be working as the phone is not being detected Is there any sort of combination of clicking the power button or something similar that may shake the phone out of the resetting loop?

ajg32 said:
Sorry for the lack of clarity. The bootloader was still unlocked I was simply trying to access files in the TWRP menu but I had to enter the pin I put on the phone. When I mentioned that I was trying to remove the lock it was so that I could use the file manager to install through the TWRP menu. I believe the bootloader is still unlocked but I simply cannot really communicate with the phone. It is on, but its suck on a google logo with a loading bar. Aside from adb commands which don't seem to be working as the phone is not being detected Is there any sort of combination of clicking the power button or something similar that may shake the phone out of the resetting loop?
Click to expand...
Click to collapse
Try these instructions - https://www.hardreset.info/devices/google/google-pixel-3/fastboot-mode/
If you can get to fastboot mode, flash a stock image from the URL in my previous post.
If that does not work, google "plxel 3 recovery mode" or "pixel 3 fastboot mode" to try to find something that works. If you can get to fastboot mode, you have a good chance of recovering the phone. Don't try to do anything with TWRP.

dcarvil said:
Try these instructions - https://www.hardreset.info/devices/google/google-pixel-3/fastboot-mode/
If you can get to fastboot mode, flash a stock image from the URL in my previous post.
If that does not work, google "plxel 3 recovery mode" or "pixel 3 fastboot mode" to try to find something that works. If you can get to fastboot mode, you have a good chance of recovering the phone. Don't try to do anything with TWRP.
Click to expand...
Click to collapse
Thank you very much for all the help, I managed to restore the phone pre-TWRP mess. You mentioned rooting by only installing magisk. Would that method be similar to the one described here https://www.rootdroids.com/guides/how-to-root-google-pixel-3-with-magisk-without-twrp/?

ajg32 said:
Thank you very much for all the help, I managed to restore the phone pre-TWRP mess. You mentioned rooting by only installing magisk. Would that method be similar to the one described here https://www.rootdroids.com/guides/how-to-root-google-pixel-3-with-magisk-without-twrp/?
Click to expand...
Click to collapse
Yes, that is the method. Those instructions don't really tell you how to get boot.img though. Unzip the factory image you downloaded. Inside that zip is another zip. Unzip that second zip and boot.img will be extracted.

dcarvil said:
Yes, that is the method. Those instructions don't really tell you how to get boot.img though. Unzip the factory image you downloaded. Inside that zip is another zip. Unzip that second zip and boot.img will be extracted.
Click to expand...
Click to collapse
I believe I got the correct boot.img although now when I try to flash boot the patched img file I get an error. Specifically,
Warning: skip copying boot_a image avb footer (boot_a partition size: 67108864, boot_a image size: 100663296).
Sending 'boot_a' (98304 KB) OKAY [ 2.286s]
Writing 'boot_a' (bootloader) Image missing cmdline or OS version
FAILED (remote: 'Failed to write to partition Bad Buffer Size')
fastboot: error: Command failed
Looking it up it seems like the most common fix is to boot from TWRP

ajg32 said:
I believe I got the correct boot.img although now when I try to flash boot the patched img file I get an error. Specifically,
Warning: skip copying boot_a image avb footer (boot_a partition size: 67108864, boot_a image size: 100663296).
Sending 'boot_a' (98304 KB) OKAY [ 2.286s]
Writing 'boot_a' (bootloader) Image missing cmdline or OS version
FAILED (remote: 'Failed to write to partition Bad Buffer Size')
fastboot: error: Command failed
Looking it up it seems like the most common fix is to boot from TWRP
Click to expand...
Click to collapse
"boot_a image size: 100663296" is the wrong size. How are you transferring boot.img and the patched image between your phone and PC? You should be using adb push/pull. If you did use adb push/pull, I'd need to see all the commands you used, and a directory listing of all the files to see if I can spot something wrong. Also, what version of Magisk?
You could try renaming magisk.apk to magisk.zip and installing the zip with TWRP, but I don't know if that method still works on the Pixel 3. I've never tried that method. Make sure you just boot TWRP (fastboot boot twrp.img), and do not install TWRP. If that breaks things, at least you know how to recover now.