Any Guides to Unlock Bootloader (Root?) OG Google Pixel?

illumination on 10/11/2023 - 19:02
Last edited 10/11/2023 - 19:05

Hi,

I've just got my hands on an OG Google Pixel (if you know, you know haha). I'm intending to root the device (I've rooted androids before so not new to rooting) because I recall coming across a comment here that if you root, you can configure your device such that your Pixel is running directly off charge and not on battery, which means you shouldn't have to worry as much about battery degradation.

I've found this but wow is this a wall of text. Looks like this and this (6 years old though) might be useful too.

Before I dive deep into all of these, just wondering if anyone has any guides that they have handy that they could share?

Any other general tips would be appreciated too!

Mobile Google Mobile Phone Android

Comments

  • localhost on 10/11/2023 - 23:17
    -2

    Ok, simple guide:
    1. tell us what is the model of the phone.

    • dust on 10/11/2023 - 23:19
      +1

      Original pixel?

  • gamerkonks on 10/11/2023 - 23:55
    +1

    Step 1: Unlock Bootloader
    Step 2: Install Magisk
    Step 3: Patch Boot.img
    Step 4: Flash Boot.img
    Step 5: Install whatever Magisk modules you want / need.
    If you need to hide Magisk because you want to use Google Wallet / Banking apps, there are additional modules you can install for that.

    • gamerkonks on 11/11/2023 - 00:01
      +1

      Unlock Bootloader (This will wipe all data on the phone).
      1. Install ADB on your PC (download)
      2. Settings -> About -> Tap Build number Until You've enabled developer options
      3. Settings -> System -> Advanaced -> Developer Options -> OEM unlocking turn on.
      4. Open cmd in your adb directory. run the command
      adb reboot bootloader
      Then when your phone reboots, run
      fastboot flashing unlock
      5. Follow instruction on screen.

      • illumination on 11/11/2023 - 02:47

        Stuck on #3. OEM Unlocking is greyed out and says "connect to the internet or contact your carrier"

        So I connected to WiFi (wasn't connected before). Still grey. Restarted. Still grey.

        Hmm…

        edit: Ok I wonder if I ended up getting a bootloader locked version.. Verizon?

        edit 2: Thought I might need to throw in a SIM and turn on mobile data. Didn't work. Still grey. But I've found this - haven't read it yet, but this looks promising

        • illumination on 12/11/2023 - 17:54

          I've tried the following to solve the OEM unlocking issue:

          • Factory Reset
          • Inserted an Australian, Malaysian and Singapore SIM
          • Factory reset after inserting each SIM
          • Having WiFi off and on post factory reset
          • Signing in to a google account post factory reset
          • Disabling and enabling diagnostics information to be sent to Google post factory reset

          As well as the guide linked to below by squabbi

  • gamerkonks on 11/11/2023 - 00:07
    +1

    Install Magisk
    1. Download apk
    2. Install on device.
    3. Download factory image. The same one that is installed on your device (check the build numbers match).
    4. Extract boot.img from within.
    5. Copy to device.
    6. Patch with Magisk.
    7. Copy patched image back to PC.
    8. Run adb reboot bootloader
    9. Run fastboot flash boot patched_boot.img
    10. Run fastboot reboot.
    11. Check you're rooted.

  • gamerkonks on 11/11/2023 - 00:07
    +1

    See this guide for screenshots, more info, etc.
    Guide

  • The-Real Team Doge on 11/11/2023 - 14:07
    +1

    Here's a Magisk module that will help you achieve what you're looking for with limiting charge, and allowing your phone to be powered directly by USB power (if the kernel supports it). https://github.com/VR-25/acc

    I used to develop a frontend for it years ago and I still use it on my OG Pixel to get that sweet unlimited original photo backup to Google Photos.

    As for you being unable to unlock OEM, there was a workaround that people tried for the OG Pixel, although I'm not sure if its been patched. https://xdaforums.com/t/how-to-unlock-bootloader-on-verizon-… It's supposed to work on Android 10.
    Maybe you can use fastboot getvar all command to see if your phone is indeed the Verizon model, or one from overseas?

    • illumination on 12/11/2023 - 17:50

      As for you being unable to unlock OEM, there was a workaround that people tried for the OG Pixel, although I'm not sure if its been patched. https://xdaforums.com/t/how-to-unlock-bootloader-on-verizon-… It's supposed to work on Android 10.
      Maybe you can use fastboot getvar all command to see if your phone is indeed the Verizon model, or one from overseas?

      I've just tried this and I didn't have any luck. The instructions are kinda weird especially at the end… "open a bunch of websites, then periodically check if OEM unlocking is now toggleable". It feels very unscientific haha. Anyway, OEM Unlocking is still locked for me. Still trying to figure this out

      edit: Wait. Just realised I downloaded the wrong version of the OTA file..! No wonder I got a failure during the flash. The guide did not make clear whether the flash had to be successful so I somehow had a feeling it wouldn't be an issue. Not logical for the flash to fail though. I'll report back..

      • The-Real Team Doge on 12/11/2023 - 18:13

        Oops I must have accidentally read that you were able to unlock!

        Hopefully it works out with the right OTA, because the recovery environment won't let you flash an OTA to downgrade! Yeah I remember the threads there and people would do the ramdomest things - but if it worked, they ought to write that down HAHA

        • illumination on 12/11/2023 - 18:34

          Ok I've re-done it, this time with the correct OTA file and there was no error in the flashing. I've followed everything exactly as it's written. Still greyed out. Although I've seen random comments from people saying "omg this worked. It wasn't working when I was trying it but I left it for 10 mins and came back to try and it worked"

          So… I think that's the only thing left I can try. Unless I go and look for another method of course.

          This was a good post providing some context as to why there are these weird instructions like "open some random websites"

          Also makes me wonder if that's the reason why IMEI from About Phone comes up as unknown…

          Anyway it's been about 10 mins and it hasn't changed

  • illumination on 13/11/2023 - 17:20

    This is a lot harder than I was expecting lol

    My next idea: downgrade the Pixel to Android 7, then use dePixel (it only supports android versions up to Android 7.1.1)

    I assume I must have a Verizon version then..

    edit: but I need to figure out how to be able to downgrade. This only works if your bootloader is unlocked… and obviously if I was able to unlock the bootloader, I wouldn't even bother with downgrading. hmmm

    • illumination on 13/11/2023 - 18:20

      Damn I thought I was a genius and found a way to downgrade to Android 7..

      The error I get when trying to downgrade is this:

      Update package is older than the current build, expected a build newer than timestamp 1572305593 but package has timestamp 1473360731 and downgrade not allowed

      So I thought, let me try and see if I can edit the timestamp

      So I went into the zip file, to META-INF\com\android\ and found the "metadata" file which showed: post-timestamp=1473360731 and I changed it to post-timestamp=1572305594 (1 digit larger than the necessary, or so I thought)

      Saved. then deleted the existing "metadata" file from the zip and added the new one with the updated timestamp to the zip file. Repeated the process, then got this error message:

      E: footer is wrong
      E: Signature verification failed
      E:error: 21

      I should've known that it's not as simple as editing a simple line of text like that LOL

      • boomersgold on 24/01/2024 - 01:08

        How'd you go with this? Did you end up finding a solution?

        • illumination on 24/01/2024 - 02:23

          Nope…

          Failed.

          My last attempt at getting this done was emailing the random guy that people on XDA mentioned had managed to unlock their bootloader by remotely connecting to their device. I never got a reply back and I have stopped trying.

          I have just accepted that my Pixel will be an unrooted Pixel.

          I'm considering installing Pixelify to a spare rooted phone that I have, or possibly rooting my Xiaomi Redmi Note 8 Pro and installing Pixel Experience on it.

Login or Join to leave a comment
Login Join