Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 6 Pro Support Thread.

[badabing2003]

why use pixel p7p image to p6p?doesn't that lead to boot loop?

One would think so, but somehow people figured out that when you patch the boot form P6 or P6P you don't get root, but if you use from P7 / P7P you do.
How they found that out, beats me, it's just shows that when there's a will there's a way.

See this.

 

[MatMew]

Where can we find an older version of platform-tools to use with the latest version of Pixel Flasher? Thank you.

After accidentally updating to Android 13, I'm so scared to try and regain root access on my Pixel 6 with 008.E1.

Scared of boot loops, using P7 boot image, many other things. Getting old over here.

 

[StanWiz]

Where can we find an older version of platform-tools to use with the latest version of Pixel Flasher? Thank you.

After accidentally updating to Android 13, I'm so scared to try and regain root access on my Pixel 6 with 008.E1.

Scared of boot loops, using P7 boot image, many other things. Getting old over here.

Here

 

[MatMew]

Here

Thank you!

 

[klazyStrida]

PixelFlasher v4.8.1 and Platform-Tools on Ubuntu 22.04(Linux MINT 21.1)

Using Platform-Tools 34.0.1 resulted in the following situation.
(1) Platform-Tools version warning when starting PixelFlasher.
(2) After launching PixelFlasher, the "ADB Connected Devices" list box and
[SCAN] button are grayed out, so the connected device cannot be selected.

Is there something specifically wrong with the Linux version of 34.0.1?
I haven't investigated it in detail, but for the time being,
I'm avoiding this problem by using Platform-Tools 33.0.3.

 

[Thebear j koss]

PixelFlasher v4.8.1 and Platform-Tools on Ubuntu 22.04(Linux MINT 21.1)

Using Platform-Tools 34.0.1 resulted in the following situation.
(1) Platform-Tools version warning when starting PixelFlasher.
(2) After launching PixelFlasher, the "ADB Connected Devices" list box and
[SCAN] button are grayed out, so the connected device cannot be selected.

Is there something specifically wrong with the Linux version of 34.0.1?
I haven't investigated it in detail, but for the time being,
I'm avoiding this problem by using Platform-Tools 33.0.3.

There is an issue with platform tools 34.0.1. Been discussed if you read back the past few pages

 

[klazyStrida]

There is an issue with platform tools 34.0.1. Been discussed if you read back the past few pages

Thanks for your reply.
I've already read past logs, but it seems that
I overlooked the contents or misunderstood.

 

[AllusionPDX]

Extracting short SHA1 from magisk_patched_4d938d3c.img ...

2023-04-01 13:08:09 NOTICE: The patched image file does not contain source boot's SHA1
This is normal for older devices, but newer deviced should have it.
If you have a newer device, please double check if everything is ok.

 

[badabing2003]

Extracting short SHA1 from magisk_patched_4d938d3c.img ...

2023-04-01 13:08:09 NOTICE: The patched image file does not contain source boot's SHA1
This is normal for older devices, but newer deviced should have it.
If you have a newer device, please double check if everything is ok.

My observations.

- You started with Android platform tools 34.0.1 (not good) but switched to 33.0.3 (good)
- You are posting in Pixel 6P thread but are using Pixel 7P, I don't mind, just making sure you are dealing with the proper firmware.
- Your phone is rooted with Magisk Delta 25210, but have magisk manager 25200 stable installed, don't mix and match.
- I can't speak of delta, 25210 but the official 25210 is no good.
- When creating a patch PF uses either the rooted Magisk core or the Magisk Manager, if the two versions are the same, the preference is to use the core.
If the manager is newer, then it uses the newer manager instead of the core. In your case because the core is at newer version, it is always using the core to create a patch, I suspect you're trying to create a patch with the stable version.
There are couple of ways to overcome that.
1- you can flash stock first and then create a patch, in which case it will use the manager (this is the preferred way)
2- you can temporarily remove su root rights from adb shell in Magisk Manager, in which case pf will not be able to access the core (which requires root access) and app report that the phone is not rooted, create a patch and it will use the manager.

 

[iwearthebelt]

My observations.

- You started with Android platform tools 34.0.1 (not good) but switched to 33.0.3 (good)
- You are posting in Pixel 6P thread but are using Pixel 7P, I don't mind, just making sure you are dealing with the proper firmware.
- Your phone is rooted with Magisk Delta 25210, but have magisk manager 25200 stable installed, don't mix and match.
- I can't speak of delta, 25210 but the official 25210 is no good.
- When creating a patch PF uses either the rooted Magisk core or the Magisk Manager, if the two versions are the same, the preference is to use the core.
If the manager is newer, then it uses the newer manager instead of the core. In your case because the core is at newer version, it is always using the core to create a patch, I suspect you're trying to create a patch with the stable version.
There are couple of ways to overcome that.
1- you can flash stock first and then create a patch, in which case it will use the manager (this is the preferred way)
2- you can temporarily remove su root rights from adb shell in Magisk Manager, in which case pf will not be able to access the core (which requires root access) and app report that the phone is not rooted, create a patch and it will use the manager.

Just for the record, I'm using the P6P, I'm on Magisk Delta 25210 and Magisk Manager 25210. Flashed with PixelFlasher. Everything is running smoothly, I've had absolutely no issues whatsoever. If you have any questions feel free to ask. Your PixelFlasher program is great, it's made things a lot easier for me. Thank you Badabing2003!

 

[AllusionPDX]

Cheers for the response, and yeah I just came here through google, my bad, i am using a p7pro.

I tried to follow your results and did a clear flash, and I was able to make a patch, however the magisk app doesnt show root, any assistance would be GREATLY appreciated, and thank you very much for the assistance you have already given =)

I think I may have made an oops with a hidden version of magisk. I know the unhide for the normal magisk: pm unhide com.topjohnwu.magisk


I do not know the one for the delta unfortunately =(

 

[badabing2003]

Cheers for the response, and yeah I just came here through google, my bad, i am using a p7pro.

I tried to follow your results and did a clear flash, and I was able to make a patch, however the magisk app doesnt show root, any assistance would be GREATLY appreciated, and thank you very much for the assistance you have already given =)

I think I may have made an oops with a hidden version of magisk. I know the unhide for the normal magisk: pm unhide com.topjohnwu.magisk


I do not know the one for the delta unfortunately =(

Did you by any chance disable root on adb?

You had it properly patched and flashed, and it booted to system, rooted with Magisk 25200
Why did you flash again?

Selected Device on 2023-04-01 14:42:17:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              b
    Device Mode:                     adb
    Device is Rooted:                True
    Device Build:                    TQ2A.230305.008.C1
    Device API Level:                33
    Device Architecture:             arm64-v8a
    Device Bootloader Version:       cloudripper-1.0-9618366
    Magisk Manager Version:          25.2:25200
    Magisk Path:                     /data/app/~~HLQ4CD2k4nmYR3XDH7ikPQ==/com.topjohnwu.magisk-uxdJc7HdQK8g4C5X-ro4dw==/base.apk
        Checked for Package:         com.topjohnwu.magisk
    Magisk Version:                  25.2:25200
    Magisk Config SHA1:              4d938d3c7bab8b0ca7accccef2aa07eefd20602d
    Magisk Modules:
        Shamiko                             enabled   v0.6 (126)

 

[AllusionPDX]

Did you by any chance disable root on adb?

You had it properly patched and flashed, and it booted to system, rooted with Magisk 25200
Why did you flash again?

Selected Device on 2023-04-01 14:42:17:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              b
    Device Mode:                     adb
    Device is Rooted:                True
    Device Build:                    TQ2A.230305.008.C1
    Device API Level:                33
    Device Architecture:             arm64-v8a
    Device Bootloader Version:       cloudripper-1.0-9618366
    Magisk Manager Version:          25.2:25200
    Magisk Path:                     /data/app/~~HLQ4CD2k4nmYR3XDH7ikPQ==/com.topjohnwu.magisk-uxdJc7HdQK8g4C5X-ro4dw==/base.apk
        Checked for Package:         com.topjohnwu.magisk
    Magisk Version:                  25.2:25200
    Magisk Config SHA1:              4d938d3c7bab8b0ca7accccef2aa07eefd20602d
    Magisk Modules:
        Shamiko                             enabled   v0.6 (126)

Because it wasnt showing as rooted unfortunately. I went back and re-did it again, and its showing the same thing.

Edit: talk to me like im stupid, because in this case I am haha, no idea how to disable root via adb. i know how to get root in adb with su though.

 

[badabing2003]

Because it wasnt showing as rooted unfortunately. I went back and re-did it again, and its showing the same thing.

Edit: talk to me like im stupid, because in this case I am haha, no idea how to disable root via adb. i know how to get root in adb with su though.

View attachment 5878245

You had root and everything was good at one point, as you can see in my previous post.
Try this.
Select the Patched boot (the one with 25200), and use the Flash boot button, not Flash Pixel Phone

 

[AllusionPDX]

You had root and everything was good at one point, as you can see in my previous post.
Try this.
Select the Patched boot (the one with 25200), and use the Flash boot button, not Flash Pixel Phone

I have done this and it shows I have root in adb, and everything else, however in magisk manager it does not show it as rooted per the picture above.

I went ahead and ran list packages -f and saw:

package:/data/app/~~QA-6DCqkV42sVpEs3syemQ==/io.github.huskydg.magisk-0vi5Ljei6--mtq2S1SkPCQ==/base.apk=io.github.huskydg.magisk

I believe this may be causing the issue...

any ideas on resolving?

 

[badabing2003]

I have done this and it shows I have root in adb, and everything else, however in magisk manager it does not show it as rooted per the picture above.

I went ahead and ran list packages -f and saw:

package:/data/app/~~QA-6DCqkV42sVpEs3syemQ==/io.github.huskydg.magisk-0vi5Ljei6--mtq2S1SkPCQ==/base.apk=io.github.huskydg.magisk

I believe this may be causing the issue...

any ideas on resolving?

yes, uninstall all versions of Magisk manager.
unhide any Magisk Manager that you have, if you have forgotten the hidden package name, you can use TB Checker from play store to let it tell you the hidden (or not hidden) Magisk Manager that it finds.
After you do that, reboot
Then install Magisk Manager 25200 and you should be good.

 

[AllusionPDX]

yes, uninstall all versions of Magisk manager.
unhide any Magisk Manager that you have, if you have forgotten the hidden package name, you can use TB Checker from play store to let it tell you the hidden (or not hidden) Magisk Manager that it finds.
After you do that, reboot
Then install Magisk Manager 25200 and you should be good.

Ok so i tried TBChecker and Ruru and its just showing the com.topjohnwu,magisk. It shows I have root, failing safetycheck, however the magisk manager app is still showing that i do not have root.

I know I could fix this by completely wiping out my phone, however that would be an absolute nightmare currently.

any other ideas?

 

[badabing2003]

Ok so i tried TBChecker and Ruru and its just showing the com.topjohnwu,magisk. It shows I have root, failing safetycheck, however the magisk manager app is still showing that i do not have root.

I know I could fix this by completely wiping out my phone, however that would be an absolute nightmare currently.

any other ideas?

no no, you don't need to wipe, you just need to find All Magisk Managers and uninstall them.
Start by uninstalling `io.github.huskydg.magisk`

You can use Package Manager (File Menu) in PF
Search for Magisk
select and uninstall.
Let me know what it finds.

 

[AllusionPDX]

no no, you don't need to wipe, you just need to find All Magisk Managers and uninstall them.
Start by uninstalling `io.github.huskydg.magisk`

You can use Package Manager (File Menu) in PF
Search for Magisk
select and uninstall.
Let me know what it finds.

https://pastebin.com/raw/j8d4gsUw

nothing with magisk.

I have already removed the huskydg one, and removed the topjohnwu one and then reinstalled a few times.

 

[badabing2003]

https://pastebin.com/raw/j8d4gsUw

nothing with magisk.

I have already removed the huskydg one, and removed the topjohnwu one and then reinstalled a few times.

Couple of package names that are suspect
rok.abvl.q
vmvhkk.j.f.j

In the Package Manager, click on Get All Application Names
It could take some time.
Once done,
Sort by the column Name.
See if any of the ones that don't have a name, is suspect package that could be a hidden Magisk.
You can uninstall it.
Also look for the name Magisk in the Name column

let me know