How To Guide [Guide] Root Pixel 6 with Magisk + Unlock Bootloader + Pass SafetyNet + More

[V0latyle]

Here is my step by step method, I'm not sure where is the problem.
View attachment 5738921View attachment 5738923View attachment 5738925View attachment 5738927View attachment 5738929View attachment 5738931

Strange. Did you have a custom ROM installed before?

 

[Lughnasadh]

I used this method, but it still doesn't work, I used the c to c interface, the original data cable
View attachment 5738919

Looks like you are still using PowerShell instead of command prompt. And as suggested, try an A to C cable using USB 2.0 port.

 

[takeshishen]

你以前安装过自定义ROM吗？

这是第一次安装和试用root。之前没有什么很成功。

奇怪的。你以前安装过自定义ROM吗？

Haven't installed it before, this is my first time trying with this phone. Unfortunately, the last step didn't go well.

 

[takeshishen]

看起来您仍在使用 PowerShell 而不是命令提示符。按照建议，尝试使用 USB 2.0 端口的 A 到 C 电缆。

I'll try a different cable like that.

 

[badabing2003]

Excuse me, I have successfully unlocked. Magisk is installed and boot.img is extracted. It has also been patched. Why doesn't this step work.
View attachment 5738883View attachment 5738881

The system boots normally without root?
While in adb mode,
What do you get when you issue these commands

adb shell ls -la /dev/block/bootdevice/by-name/

adb shell getprop ro.boot.slot_suffix

 

[V0latyle]

这是第一次安装和试用root。之前没有什么很成功。

Haven't installed it before, this is my first time trying with this phone. Unfortunately, the last step didn't go well.

I'm not sure what the problem might be then. From my end it looks like you're doing everything right. The only thing I can think of is make sure you're using the right files and a known good cable, but your root.img size is the same as the boot.img in the factory package so that should be OK. Sorry you're having trouble, hope we are able to help you figure it out.

 

[takeshishen]

The system boots normally without root?
While in adb mode,
What do you get when you issue these commands

adb shell ls -la /dev/block/bootdevice/by-name/

adb shell getprop ro.boot.slot_suffix

That's it, I took a screenshot.

 

[takeshishen]

I'm not sure what the problem might be then. From my end it looks like you're doing everything right. The only thing I can think of is make sure you're using the right files and a known good cable, but your root.img size is the same as the boot.img in the factory package so that should be OK. Sorry you're having trouble, hope we are able to help you figure it out.

This cable has dealt with other phones before, I don't think it should be the problem, at least I did the previous steps successfully. Where can I download the boot.img file that has been repaired. Maybe I can try it, all I can think of is the problem in this link. Thanks a lot for your answer.

 

[takeshishen]

I'll try a different cable like that.

I'll try a different cable like that.

This also doesn't work, I can only try to change the A to C cable tomorrow.Thank you very much.

 

[V0latyle]

This cable has dealt with other phones before, I don't think it should be the problem, at least I did the previous steps successfully. Where can I download the boot.img file that has been repaired. Maybe I can try it, all I can think of is the problem in this link. Thanks a lot for your answer.

The only thing I can say is when you start having trouble, double and triple check everything. Make sure you're using the right tools, the right files, the right process, etc. I can't specifically say what causes that error but I have seen it happen with outdated ADB tools as well as bad/uncooperative USB cables. The response from the target doesn't always make perfect sense given what the problem might be.

I would say go back through the guides and make sure you're doing everything by the letter.

 

[badabing2003]

That's it, I took a screenshot.

View attachment 5738979View attachment 5738981

This is weird,
The partition is there.

There only thing i would suggest is to move your files to c:\pixel
And try it from there, i don't think it would make a difference, but it is worth a try just in case the path is causing a problem.

 

[takeshishen]

This is weird,
The partition is there.

There only thing i would suggest is to move your files to c:\pixel
And try it from there, i don't think it would make a difference, but it is worth a try just in case the path is causing a problem.

I used the webpage provided by Google to flash Android 13 several times, and both partitions should be the same. I tried putting the folder under c:\ and the result is still the same.
The only thing I can think of, is it a bug in my boot.img patch, I can't find where I can download it right now.

 

[badabing2003]

I used the webpage provided by Google to flash Android 13 several times, and both partitions should be the same. I tried putting the folder under c:\ and the result is still the same.
The only thing I can think of, is it a bug in my boot.img patch, I can't find where I can download it right now.

The error is about boot partition not being found, not root.img being bad.

If you wanted you can give PixelFlasher a try, it would eliminate any typo you might have introduced.

 

[takeshishen]

The error is about boot partition not being found, not root.img being bad.

If you wanted you can give PixelFlasher a try, it would eliminate any typo you might have introduced.

Forgive my ignorance, I downloaded this. But don't know how to improve this partition problem.

 

[tom1807]

Sorry, that I jump in,, but first I suggest that you are not using a remote drive like OneDrive.
Second, keep the path short, in theory it all should work in Windows or DOS, but I witnessed too much strange behavior with long filepaths.
My suggestion, create a folder on your C:\ Drive, call it ADB or something else and get all files to there.

Cheers
Tom

 

[takeshishen]

Sorry, that I jump in,, but first I suggest that you are not using a remote drive like OneDrive.
Second, keep the path short, in theory it all should work in Windows or DOS, but I witnessed too much strange behavior with long filepaths.
My suggestion, create a folder on your C:\ Drive, call it ADB or something else and get all files to there.
View attachment 5739113

Cheers
Tom

Thanks for the suggestion, I have put all the files in C:\. But still not working. I think it should be the problem of the phone partition, but I don't know how to solve it.

 

[tom1807]

Simple question, drivers are installed?
This means when you are in fastboot mode, is the driver for fastboot in your device manager?

Cheers
Tom

 

[badabing2003]

Forgive my ignorance, I downloaded this. But don't know how to improve this partition problem.

I posted my answer here to keep this thread clutter free.

 

[V0latyle]

This is weird,
The partition is there.

There only thing i would suggest is to move your files to c:\pixel
And try it from there, i don't think it would make a difference, but it is worth a try just in case the path is causing a problem.

@tom1807 suggested the same thing. I don't think it's a path thing.

Also, he does have the correct drivers installed, he's able to interface with the device via both ADB and bootloader

@takeshishen what version of Magisk are you using and where did you download it from?

 

[takeshishen]

@tom1807 提出了同样的建议。我不认为这是一个路径的事情。

此外，他确实安装了正确的驱动程序，他能够通过 ADB 和引导加载程序与设备交互

@takeshishen 你用的是什么版本的 Magisk，你从哪里下载的？

25.2 This version I use