[GUIDE] Pixel 5 "redfin": Unlock Bootloader, Update, Root, Pass SafetyNet

[V0latyle]

there was the possibility to separate the 2 like here:

How to get the old Wi-Fi toggle back on your Android 12 phone

Just a couple of minutes and two ADB commands

www.androidpolice.com

Oh, I have no idea.

 

[scootley]

Hi,

Pixel 5 running Android 12 SQ3A.220705.003.A1. Trying to go from stock to vanilla root using Magisk Canary (25202).
Patched stock boot image just fine.
I am trying to just do a temporary root for a single boot using "fastboot boot ..."
Has worked fine many times in the past.

But after fastboot, it seems to try to boot, shows the Google logo, and then shuts down and is charging and showing the percentage charged. (in other words, it won't boot and just shuts down)

Of course I can then power on the device and it boots fine back into stock.

Fastboot command:

fastboot -v boot magisk_patched-25202_eIqnE.img
Sending 'boot.img' (98304 KB)                      OKAY [  2.688s]
Booting                                            (bootloader) boot.img missing cmdline or OS version
OKAY [  1.560s]
Finished. Total time: 4.321s

Any ideas?

Update: Actually I just got it to boot. Same exact patched image as originally. All I did was pull the USB cable out of the phone right after fastboot completed (was using Linux)

Thanks

 

[V0latyle]

How is everyone's battery life on Android 13? Mine seems to be much MUCH worse.

 

[digger16309]

I wouldn't say my battery life is much worse but I do see a bit more drain than on A12. Since I did a clean install, I had to go in and change all my apps back to restricted battery, one-by-one. I have a ton of frozen Google apps and processes but I think PLAY Services is a culprit.

 

[AnyNameYouWish]

Same, it's not "much" worst but I feel like it isn't as good as it used to be on A12

 

[Regys]

How is everyone's battery life on Android 13? Mine seems to be much MUCH worse.

Hi,

Yes me too !

 

[omartins]

How is everyone's battery life on Android 13? Mine seems to be much MUCH worse.

It is definitely worst. After a few cycles with my standard pattern of usage I see a 10% less deep sleep in CPU state stats (BBS data).
I've now disabled the Adaptive Connectivity feature, let's see if it is related or not...

 

[V0latyle]

It is definitely worst. After a few cycles with my standard pattern of usage I see a 10% less deep sleep in CPU state stats (BBS data).
I've now disabled the Adaptive Connectivity feature, let's see if it is related or not...

Where is that?

It's bad enough I'm considering either a full wipe or downgrading

 

[omartins]

Where is that?

Here

 

[V0latyle]

Here

No, I meant the Adaptive Connectivity setting. Never mind, I found it

 

[badabing2003]

How is everyone's battery life on Android 13? Mine seems to be much MUCH worse.

FYI My main phone is Pixel 6 Oriole, and I have not noticed any battery degradation with A13 but this thread is not about Pixel 6, it is about Pixel 5 and I have a Pixel 5 situation that I want to pick your brains on.

Adventures in Pixel 5 with Android 13
My son has a Pixel 5, and until recently he was not rooted (more on that further below), however he was at one point in the A13 Beta program (if it has any relevance), and was stuck there because opt out meant a wipe, and he didn't want that.
With the release of A13, he had the opportunity to opt out without a wipe which he did.

All along his updates were all OTA considering that he was not rooted.

After opting out from Beta and being on A13 August release he wanted to root.
Which I did for him using pf. Basically just flashed a patched boot.img.
All went well and he was using it fine.
As far as I know his only complaint was that reboots were now taking longer than before.

With the September release, I did full factory update on both slots keeping root.
The process had no error messages and everything went fine.

However the phone started having random freezes/hangs, and random reboots, and was getting hot.
I first tried to disable any Magisk modules he had other than SafetyNet Mod, still the same.
Next we decided to flash back the August release (one slot only) to see if going back would fix the issue, in case this was something new with the September release.
We got the dreaded Your device is corrupt message, with the phone rebooting to recovery.

I sideloaded September OTA, and that got the phone running again (not rooted)
But the freeze and reboots returned (the phone wouldn't last 5 minutes without a freeze or reboot)

I tried many ways to go back to the August release
(All without wipe)

• Factory flash with or without root in pf
• Factory flash manually
• OTA sideload
• Android flash tools (which failed with the following message) for both Sep and Aug releases

and no matter what I did, I would get the device corrupt message, tried both slots and each slot separately as well.

One thing I noticed is that flashing the bootloader was getting an error, even though the device was already on that bootloader (incidentally, not Aug and Sep have the same version of the bootloader: bootloader-redfin-r3-0.5-8633620.img)

Sending 'bootloader' (8762 KB)                     OKAY [  0.233s]Writing 'bootloader'                               FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Rebooting into bootloader                          OKAY [  0.002s]

Whereas a successful flashing of bootloader would output

Sending 'bootloader_b' (8762 KB)                   OKAY [  0.349s]
Writing 'bootloader_b'                             (bootloader) Flashing Pack version r3-0.5-8633620
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition featenabler_b
(bootloader) Flashing partition logfs
OKAY [  0.251s]
Finished. Total time: 0.862s

So I didn't have a choice other than flashing back the September release and trying to figure out what was causing the freezes and reboots. Yucks

Long story short, I was able to narrow it down to a program called Greenify that he had been using, for whatever reasons that App on September release was causing the hangs and reboots.

Now he has patched September release flashed to both slots, and I haven't seen him for a while, which should be a good sign

My questions:
Does anyone know anything about not being able to downgrade to A13 August release? what would cause that issue?

And also why bootloader flashing was often causing that error, even though what was being flashed was already the exact same thing that was on the system.

I know it is not the fastboot drivers, that was the first thing I checked, everything else kept on flashing just fine.

Sorry for long winded post, I didn't want risk leaving out any detail that might be relevant.

 

[doras100p]

Perhaps someone could help me with this as I can't find myself in this thread -

I have a Pixel 5 that I rooted when it was on Android 12.
Then at some point it forced an OTA security update, after which it no longer seemed rooted and Google Wallet stopped working.
Then it was OTA updated to Android 13 (this time by me, not forcefully by the device)

I no longer need it to be rooted, but I do wish to go back to using Google Wallet, is there anything I can do that doesn't require formatting my phone?
If I do format my phone, is there any special percussions I should take?

Thanks!

 

[V0latyle]

Perhaps someone could help me with this as I can't find myself in this thread -

I have a Pixel 5 that I rooted when it was on Android 12.
Then at some point it forced an OTA security update, after which it no longer seemed rooted and Google Wallet stopped working.
Then it was OTA updated to Android 13 (this time by me, not forcefully by the device)

I no longer need it to be rooted, but I do wish to go back to using Google Wallet, is there anything I can do that doesn't require formatting my phone?
If I do format my phone, is there any special percussions I should take?

Thanks!

If your bootloader is still unlocked, you have two choices:
1. Lock the bootloader (which will wipe data)
2. Re-root and use the modified Universal SafetyNet Fix module by @Displax

Otherwise, the device will fail security requirements, and there is no way around it.

 

[a4abbas]

How is everyone's battery life on Android 13? Mine seems to be much MUCH worse.

Do you suggest to stay on Android 12 for now?

 

[V0latyle]

Do you suggest to stay on Android 12 for now?

It seems to have improved some with the September update.

 

[Regys]

Hi,

I did the last update, perfect, but I would like to do a deep hard reset.

How do I proceed please ?

 

[V0latyle]

Hi,

I did the last update, perfect, but I would like to do a deep hard reset.

How do I proceed please ?

What do you mean by "deep hard" reset?

 

[Regys]

What do you mean by "deep hard" reset?

Hard Reset

 

[V0latyle]

Hard Reset

That still doesn't answer my question.

The most you can really do is a factory reset, which wipes /data and /storage.

 

[Regys]

That still doesn't answer my question.

The most you can really do is a factory reset, which wipes /data and /storage.

ok only by the system, hard reset is not possible

1/ Factory Reset is deep format than Hard Reset ?
2/ Factory Reset redefines the bootloader?