• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Guide] Root Pixel 3 XL Android 12

Search This thread

vlucchetti

Senior Member
Dec 3, 2009
664
124
Latrobe, PA
Rooted, no safetynet with 3XL on canary23011 app and magisk. Planning to go 6 Pro, but what do I need to do to get safetynet on the 3xl in the meantime? I never had to uninstall magisk from 10 to 11 or at anytime, all I did was turn off modules.

Do I need a complete reinstall, remove magisk?
 

Homeboy76

Senior Member
Aug 24, 2012
2,908
1,525
Google Pixel XL
Rooted, no safetynet with 3XL on canary23011 app and magisk. Planning to go 6 Pro, but what do I need to do to get safetynet on the 3xl in the meantime? I never had to uninstall magisk from 10 to 11 or at anytime, all I did was turn off modules.

Do I need a complete reinstall, remove magisk?
Uninstall Magisk Canary 23011 install Canary 23001 and do not update. :)
 

phoenixpb

Senior Member
Dec 18, 2010
103
22
I tried the alpha versions and it was a complete mess.

Now with d232cba0 (23012) (21) everything (Systemless + AdAware, root) seems to work ok for me. Also Zygisk and DenyList seems to work as expected for me.

Custom kernel needed due to some unfixed bug in normal kernel.
Yes thank you 23012 is working perfectly. Reap in peace magisk hide :D
 

Mawtin

Senior Member
Nov 8, 2011
254
45
Can't seem to get my device to pass safetynet. Tried universal safetynet fix 2.1.1 and magiskhide props config 6.1.1. I'm using Magisk Canary 23013 on Pixel 3
 

Homeboy76

Senior Member
Aug 24, 2012
2,908
1,525
Google Pixel XL
Can't seem to get my device to pass safetynet. Tried universal safetynet fix 2.1.1 and magiskhide props config 6.1.1. I'm using Magisk Canary 23013 on Pixel 3

Magisk Canary 23013 uses Zygisk and DenyList it needs Universal SafetyNet Fix · 2.2.0.

 
Last edited:

pointbob

Senior Member
Mar 30, 2012
108
3
Is it possible to simulate my 3xl so it successfully appears as a original XL? A step by step process or direction as to how would be thankful.
 
Last edited:

vlucchetti

Senior Member
Dec 3, 2009
664
124
Latrobe, PA

Magisk Canary 23013 uses Zygisk and DenyList it needs Universal SafetyNet Fix · 2.2.0.


So when we do this, we disable modules module, update to 23013, and make sure that we do not use the Riru module at all?
 

Homeboy76

Senior Member
Aug 24, 2012
2,908
1,525
Google Pixel XL
So when we do this, we disable modules module, update to 23013, and make sure that we do not use the Riru module at all?
Yes, disable the modules and set the update channel to Canary, if it is not already set to Canary.
- When you see update in the app section of Magisk update the App.
- Patch the boot.img
- flash the magisk-patched_...img
fastboot flash boot magisk-patched_...img
- Then go to the OP, Root/Reroot with Magisk and Pass SafetyNet, Pass Safety Net with SafetyNet Fix 2.2.0, 3. Settings for Magisk Canary 23015
 
Last edited:
  • Like
Reactions: vlucchetti

benphillipstn

Member
Mar 8, 2019
24
1
I am attempting to root a Pixel 3 XL.

The phone is on build number: (SP1A.210812.016.A1, Oct 2021, Verizon)

But this is not a verizon phone. I unlocked the bootloader without issue. The imei starts with 99 and verizons imei checker confirmed it is a non vzw phone.

Is it safe to patch and flash the boot.img from the (SP1A.210812.016.A1, Oct 2021, Verizon) factory image?
 
Last edited:

Homeboy76

Senior Member
Aug 24, 2012
2,908
1,525
Google Pixel XL
I am attempting to root a Pixel 3 XL.

The phone is on build number: (SP1A.210812.016.A1, Oct 2021, Verizon)

But this is not a verizon phone. I unlocked the bootloader without issue. The imei starts with 99 and verizons imei checker confirmed it is a non vzw phone.

Is it safe to patch and flash the boot.img from the (SP1A.210812.016.A1, Oct 2021, Verizon) factory image?
Yes.

Suggestion:
The Google Factory Image Oct 2021 is outdated.

Install [ROM][11][OFFICIAL] lineage-18.1 for Pixel 3/XL (blueline/crosshatch) on you Pixel 3/Pixel 3 XL.
 
Last edited:
  • Like
Reactions: benphillipstn

dishe2

Member
Dec 2, 2020
30
3
Sorry for the dumb question, but has anyone with an unlocked/custom bootloader had their pixel 3 xl fail to the dreaded EDL bug that's been going on?
Yes that one.

I just got one of these as a throwaround phone for my daughter and I'm trying to determine if it's only happening to stock OTA people- it seems like most are blaming an update performed overnight and waking up to a dead phone. Wondering if unlocking the bootloader and going custom might prevent this, but I'm having trouble getting a straight answer.
 

vlucchetti

Senior Member
Dec 3, 2009
664
124
Latrobe, PA
While the 3XL is now at end of life, I understand that there will be one more security patch update for Android 12 on the 3XL in the first quarter of 2022, and that should be the last of what we will receive for the 3XL.

Been a great run on this phone. Homeboy, hope you will be doing a guide to root for the 6 Pro when I switch over to it after they work some kinks out. Totally appreciate everything you've been doing for the community.
 
  • Like
Reactions: Homeboy76

Homeboy76

Senior Member
Aug 24, 2012
2,908
1,525
Google Pixel XL
While the 3XL is now at end of life, I understand that there will be one more security patch update for Android 12 on the 3XL in the first quarter of 2022, and that should be the last of what we will receive for the 3XL.

Been a great run on this phone. Homeboy, hope you will be doing a guide to root for the 6 Pro when I switch over to it after they work some kinks out. Totally appreciate everything you've been doing for the community.
I posted a link about the last Pixel 3 / Pixel 3 XL update in the OP New section.:):):)
 
Last edited:
  • Like
Reactions: barnettejd

faheyd

Senior Member
Dec 29, 2011
159
35
Reno NV
Google Pixel 3 XL
OnePlus 8
Silly question: After fighting my way through post #1, I got Magisk installed with safetynet, etc. My LG ThinQ app now runs after checking it off in the DenyList. When I do the next Lineage rom update via OTA, will my root 'stay' or do I have to do more steps? Thanks, Dylan
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Hello, I'm a bit confused with getting root on my pixel 3 xl I read op but steps bit confusing. I wanna flash this kernel on to the stock rom,
    kernel: Kirisakura_Bluecross_S_4.0.0
    stock rom build number : SP1A.210812.016.A2
    Which recovery do I use to sideload Magisk ? I read all 15 pages some people say not to use TWRP. I downloaded Magisk from their telegram: 558710bb-alpha-2.zip.
    I know gotta patch boot.img with Magisk to get root, according to the kernel dev description the safetynet bypass already build in. Do I flash kernel with Magisk app manager after sideloading it or specific kernel manager? this step I need clearity because instruction bit all over the places.
    You want to install this outdated Google Factory Image 12.0.0 (SP1A.210812.016.A2, Oct 2021); Kirisakura_Bluecross_S_4.0.0 kernel (October 21, 2021).

    It seems, to me, you want to install this particular kernel to pass SafetyNet: "according to the kernel dev description the safetynet bypass already build in"

    The instruction in the OP, 6. tell you how to Patch the boot.img and pass SafetyNet.

    Further, you want to use Magisk alpha (558710bb-alpha-2.zip) to patch the boot.img you are going flash to get root: fastboot flash boot magisk_patched...img, but you want to sideload Magisk alpha.

    This version of Magisk is for "mavericks only" (extremely knowledgable of Magisk) it is not noobs (inexperienced with Magisk).

    Suggestions
    1. Take a look at the OP: Updates, 9. and install a Custom ROM with updated Security Patches on your Pixel 3 XL.
    2. If you reject 1. above: Go to the OP Updates, 8. tap the Kirisakura_Bluecross_S_4.0.0 kernel link and post your entire post on that thread.

    :)
    1
    Two New Android 12 Pixel 3 XL Custom ROMS (see Index Custom ROMS).
    1
    In order to get fastboot to communicate with my PC, I had to do something I don't see mentioned here: install Google's ADB drivers for my Pixel 3XL. Without that, Windows would not recognize my phone was connected when I was in fastboot mode.


    I apologize if I missed this instruction.
    OP, Prerequisites 2: SDK Platform-tools
    1
    In order to get fastboot to communicate with my PC, I had to do something I don't see mentioned here: install Google's ADB drivers for my Pixel 3XL. Without that, Windows would not recognize my phone was connected when I was in fastboot mode.


    OP, Prerequisites 2: SDK Platform-tools
    I already have that. I downloaded that from the link you provided. But that did not include the USB drivers. That's just the programs, like fastboot.exe, adb.exe, etc. I'm talking about the drivers I had to install using Device Manager, from the link I provided.

    Before I installed those, Windows wouldn't even detect my phone if I had it in fastboot mode, and fastboot devices showed no devices. After installing the driver, Windows showed an icon to say I had connected my phone, and fastboot devices showed my phone.
    1
    I posted a link about the last Pixel 3 / Pixel 3 XL update in the OP New section.:):):)
    Well my Pixel 3 XL is dead after 3 years of great service
    Doesn't turn on any more

    I have ordered a pixel 6 to be my next device

    I will continue to take a look to this thread anyway
    if i can help, it always will be a pleasure

    Have a nice day
  • 12
    [Guide] Root Pixel 3 XL Android 12 Unlock/Lock Bootloader + Install Stock Images/Systemless Root2021
    Android Security Bulletin—October 2021
    Pixel Update Bulletin—October 2021

    Introduction
    1. This Guide is for Pixel 3 XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a Custom ROM. However, for those that just can't live without a Custom ROM, take a look at 'Custom ROMs for Pixel 3 XL'.
    2. This Guide also works for Pixel 3 owners: If, they download the Pixel 3 files.

    NEW
    1. Operating System: ArrowOS Pixel 3 XL Android 12
    2. Google will be releasing one last Pixel 3 and 3 XL update in Q1 of 2022 Abner Li - Nov. 2nd 2021 11:24 am
    3. The differences between the different variants of Magisk
    4. Magisk Alpha (vvb2060)
    5. Magisk Modules for Magisk Alpha/Canary


    Update(s)
    1. Factory/OTA Images - 19Oct
    2. Magisk Stable - Magisk-23.0 05Dec
    3. Magisk Beta - Magisk-24.0 26Jan
    4. Magisk Canary - Magisk-24001 26Jan
    5. TWRP - Waiting for T.R.W.P. for Android 12
    6. SafetyNet - SafetyNetFix v2.1.3 (Riru) v2.2.1 (Zygisk) 22Dec
    7. SDK Platform-tools - r31.0.3 18Aug
    8. Custom Kernels

      b. Elemental X - check the Elemental X Kernel Manager for updates​
    9. Custom ROMs


    Disclaimer
    1. I assume no responsibility for the malfunctioning/bricking of your phone.
    2. The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.

    Prerequisites
    1. A Pixel 3 XL phone with an unlocked bootloader.
    2. A Computer with the latest SDK Platform-Tools: r31.0.3 installed.
    3. Important Notes:
      a. Update Platform Tools, regularly, for optimal performance.​


    My Other Guides

    Credits/Thanks/Recognitions
    1. bradical711 - Instructions to Pass Safety Net
    2. @sliding_billy - His help editing this thread.
    3. Those I may have, inadvertently, forgotten.

    Index
    (NOTE: Numbers 1-10 are not steps, they are individual sets of instructions).
    1. Open a Command Prompt/Boot Fastboot Mode/Boot Recovery

      • Open a Command Prompt on Computer
        1. Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
        2. Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
        3. Notes:
          • Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
          • When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
          • If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
      • Boot fastboot mode (bootloader):
        • Power off phone, press and hold the power and volume down buttons until you see Start.
      • Boot Recovery
        • Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
    2. Test fastboot

      • Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
      • Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
        Enable USB Debugging.
      • Open a Command Prompt on your computer in the Platform-tools folder.
      • Boot fastboot mode on your phone (#1)
      • Connect the phone to the Computer.
      • At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
    3. Unlock Bootloader/Return Phone to Stock/Lock Bootloader

      • Unlock Bootloader

        1. This will erase all user data from the device!
        2. Backup your data
        3. Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
        4. Boot fastboot mode
        5. Connect the phone to the Computer with USB cord.
        6. Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
        7. You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
        8. Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
        9. When your phone reboots disconnect your usb cable.
          Notes: After unlocking your bootloader, you'll see a warning: The bootloader is unlocked and... You will see this warning until, you relock the bootloader.
          Do not relock your bootloader until you have returned the device to Stock.
      • Return Phone to Stock

        • Backup your data/Internal storage
        • Settings > System > Advanced > Reset Options > Erase all data (factory reset)
        • Log in
        • Set up phone
      • Lock Bootloader

        1. Do not lock the bootloader until you have returned the phone to stock. Failure to do so causes bricked phones.
        2. This will erase all user data from the device!
        3. Boot fastboot mode
        4. Open a Command Prompt and type this at the Prompt: fastboot flashing lock
        5. You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
        6. Allow the process to complete, then type this at the Command Prompt: fastboot reboot
        7. Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
        8. Tap Back > Developer options and toggle OEM Unlock off.
    4. Install/Update Factory Image keep data or wipe data

      • Important Note(s):
        1. When doing a major upgrade i.e., Android 11 to Android 12: I recommend doing a clean install. What is a clean install?
          • Doing a Factory reset prior to installing, major, update.
          • Using flash-all.bat file without removing the -w (#4. Wipe Data).
        2. Always verify you have the latest version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 3XL - crosshatch.
        3. If your phone was rooted, and you want to 'Keep Data'. Do this first open Magisk ==> unhide Magisk App (if you hid it) ==> Disable/Remove all modules ==> then Uninstall Magisk - Restore images prior flashing the Factory image. Why? The changes in the New factory image may cause Magisk modules to fail. This will cause boot loops. Additionally, before Enabling/Installing the modules you Disabled/Removed check with the Dev of the module to ensure it was updated to work with the latest factory image.
        4. If you get an error while flashing, try one of these options:
          • Change the USB port to a non charging USB port.
          • Change the USB cord.
          • Change Computers.
        5. Backup your data
        6. Download the latest Factory Image: Pixel 3XL - crosshatch to your Computer.
        7. Extract the factory Image to a folder.
      • Flash Factory Image Keep Data

        • Open the folder you extracted the Factory Image to and Edit the flash-all.bat file with a file editor i.e., Notepad. Remove the -w from this command: fastboot -w update image-crosshatch-aa9a.999999.999.zip
          Note: If you do not remove the -w your data and internal storage will be wiped.
        • After, you have edited the flash-all.bat file. Copy/Move these files to the Platform-tools folder:
          1. bootloader-crosshatch-....img
          2. flash-all.bat
          3. image-crosshatch-....zip
          4. radio-crosshatch-....img
        • Open a Command Prompt on your computer in the Platform-tools and type: flash-all at the Command Prompt and press enter.
        • System will reboot when flashing is complete.
        • Do #7 to root/reroot.
      • Flash Factory Image Wipe Data

        • This will wipe your phones Internal Storage.
        • Open the folder you extracted the Factory Image to and Copy/Move these files to the Platform-tools folder:
          1. bootloader-crosshatch-....img
          2. flash-all.bat
          3. image-crosshatch-....zip
          4. radio-crosshatch-....img
        • Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
        • The phone will reboot when flashing is complete.
        • Do #7 to root/reroot.
    5. ADB Sideload

      • Stock Recovery
      • Custom Recovery - TWRP

        • Important notes:
          1. Charge your device.
          2. Enable USB Debugging on your phone.
          3. Install the latest version of SDK Platform-tools on your computer.
        • Open a command prompt in the computer's ADB folder: the folder with ADB.exe in it.
        • Put the (flashable zip) file you want to sideload in the computer's ADB folder.Copy the Zip file you want to install on your device to the ADB folder.
        • Connect your device to your computer using a USB cable.
        • Boot T.W.R.P.
          1. T.W.R.P installed: Boot fastboot mode ==> use volume buttons up/down until you see Recovery mode ==> press power botton.
          2. T.W.R.P. not installed: Boot T.W.R.P: Put twrp.img file in the computer's ADB folder ==> open a command prompt in ADB folder ==> at the prompt type fastboot flash boot "Name of twrp file.img" without the quotation marks.
        • When T.W.R.P boots tap Advanced ==> ADB Sideload.
        • ✓ the wipe Dalvik cache box
        • Swipe to start
        • On your Computer: Enter the following command at the command prompt. adb sideload <filename.Zip> i.e., adb sideload myfile.zip
        • You will see the progress of the sideloaded file.
        • When the file finishes sidloading, reboot your device.
        • Done!
    6. Extract/Flash boot.img

      • Extract boot.img

        • Download the latest Factory image to your phone.
        • Extract the Factory Image file (crosshatch-pda1a.999999.999-factory-99a9a99a.zip) to a folder.
        • Open the folder and, extract the Image file (image-crosshatch-aa9a.999999.999.zip).
      • Flash boot.img

        1. Note: Flashing this file removes root.
        2. Open the folder you extracted the 'image...zip' file to and copy the boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
        3. Boot fastboot mode
        4. Connect the phone to the Computer
        5. At the Command Prompt type: fastboot flash boot --slot all boot.img
        6. Reboot
    7. Root/Reroot with Magisk and Pass SafetyNet.

      • Patching the boot.img - to root/reroot.

        1. Do #6 - Extract boot.img
        2. Install Magisk Canary
          Note: Tap 3 dot menu across from canary => Tap Go to file => Download app-debug.apk
          or
          Magisk 24.0 Beta App
        3. Open Magisk Canary/Beta App
        4. Set the Update Channel Canary/Beta.
        5. Tap Install (next to Magisk)
        6. Tap, Select and Patch a File
        7. Select the boot.img file you extracted from the latest factory image.
        8. Tap the ✓ (Check Mark)
        9. Tap Let's Go
        10. When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
        11. Reboot
        12. Copy the patched boot.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it.
        13. Boot fastboot mode
        14. Connect the phone to the Computer with USB cord.
        15. Open a Command Prompt in the folder you copied the patched boot.img to.
        16. Type fastboot flash boot "name of patched boot".img without the quote marks at the Prompt and press enter.
        17. Type fastboot reboot at the Prompt and press enter.
        18. Important Notes: If your phone boot loops try one of the following options:
          • Flash the 'stock' boot.img to both slots: fastboot flash boot boot.img --slot all
          • Boot Safe Mode - Press Power Off button ==> Press Power Off until you see boot Safe Mode ==> Press Ok.
      • Pass Safety Net with SafetyNet Fix 2.2.1

        1. Download File(s)
        2. Install SafetyNet Fix 2.2.1
          • Open Magisk
          • Tap Modules icon
          • Tap Install from storage
          • Navigate to the SafetyNetFix file you downloaded
          • Tap the SafetyNetFix file
          • Tap the check mark (✓ at the bottom) to start the installation.
          • After it installs tap the Save icon to save the log
          • Tap Reboot.
        3. Settings for Magisk Canary
          • Open Magisk App
          • Tap the Setup icon.
          • Scroll down to App and set the Update Channel to Canary.
          • Scroll down to Check Updates and enable it.
          • Scroll down to Magisk and enable Zygisk and Enforce DenyList.
          • Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, etc.
          • Scroll down to Superuser and enable Enable Biometric Authentication.
        4. Get Device Certified Clear Google Play Services, Google Play Store, Google Pay, etc. data
          • Turn Airplane mode on
          • Open Settings
          • Tap Apps & notifications
          • Tap see all...
          • Tap three dot menu
          • Tap Show system
          • Scroll down to Google Play Store
          • Tap Storage and Cache
          • Tap Clear storage
            Note: Repeat the 3 steps above for Google Play Services, Google Pay, etc.
          • reboot
          • Turn Airplane mode off
        5. Check Device Certification
          • Open Google Play Store app
          • Tap Menu - Circle top right
          • Tap Settings
          • Tap About
          • Check Play protect certification.
    8. Set Magisk App Update Channel/Update Magisk

      • Set Magisk App Update Channel

        • Open Magisk App > Tap menu icon > Settings > Update Channel > Select Stable, Beta Canary or Custom.
      • Update Magisk

        1. When Magisk App notifies you of an update:
        2. Tap install.
        3. Select, Direct Install (Recommended)
        4. When it finishes installing
        5. Tap, Save Log
        6. Log location: /storage/emulated/0/MagiskManager/logs/install_log_
        7. Tap, Reboot
        8. Done
    9. Custom ROMs

    10. Mods/Scripts/Themes
    11. T.W.R.P. Backup/T.W.R.P Update

      • Waiting for Android 12 T.W.R.P.
    3
    Hello Pixel Community,

    We have provided the monthly Android/Pixel update for December 2020. All supported Pixel devices running Android 11 will receive these software updates as part of the December 2020 update, which begins rolling out to users today. We encourage you to check your Android version and update to receive the latest features.

    Overview:

    • Software versions:
      • Global:
        • Pixel 3 (XL): RQ1A.201205.003
        • Pixel 3a (XL): RQ1A.201205.003
        • Pixel 4 (XL): RQ1A.201205.008
        • Pixel 4a: RQ1A.201205.008
        • Pixel 4a (5G): RQ1A.201205.011
        • Pixel 5: RQ1A.201205.011
      • Verizon:
        • Pixel 3 (XL): [Update: Rolling out week of 12/14]
        • Pixel 4a (5G): [Update: Rolling out week of 12/14]
        • Pixel 5: [Update: Rolling out week of 12/14]
      • AT&T:
        • Pixel 4 (XL): RQ1A.201205.008.A1
        • Pixel 4a (5G): RQ1A.201205.010
        • Pixel 5: RQ1A.201205.010

    3

    After, reading several threads and @Lughnasadh post, there are no special requirements to root Android 12 for the Pixel 4 XL or the Pixel 3 XL.​


    So, that means the instructions in the OP, Index, #7 are sufficient for rooting the Pixel 4XL and Pixel 3 XL phones.

    Thanks, Lughnasadh! :)
    3
    :) I hope you all have a Joyful Holiday season with your family and loves ones. :)

    ~ ~ ~ Stay safe ~ ~ ~
    2
    Did anyone tried using the patched.img provided by a user on the first page?, I don't want to waste data by downloading stock boot.img

    Hi,

    Don't use it, it is an old one. You want the stock January boot.img? There are two factory images this month: international / Verizon.

    Cheers...

    Sébastien.