• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Rooting Pixel 2 failing in the last moment

andfo

Member
May 26, 2015
75
18
After lots of struggle trying this and that, I came across
and almost successfully followed its instruction.

But I am stuck at almost last point. (It's 11:00 in the Youtube video)

My phone's screen shows me

ADB Sideload
Data successfully decrypted
Updating partition details...
... done
Successfully decrypted with default password.
Updating partition details...
...done
Full SELinux support is present.
Starting ADB sideload feature...
Installing zip file '/sideload/package.zip'​

It's stuck here. That is, it shows me the screen at 11:02 of the youtube video. For me now it's stuck here for 10 minutes now.

In the youtube video, this step takes 1 second, so it will quickly move to the screen shown at 11:03 of the youtube video.

Why stuck here?
 
After lots of struggle trying this and that, I came across
and almost successfully followed its instruction.

But I am stuck at almost last point. (It's 11:00 in the Youtube video)

My phone's screen shows me

ADB Sideload
Data successfully decrypted
Updating partition details...
... done
Successfully decrypted with default password.
Updating partition details...
...done
Full SELinux support is present.
Starting ADB sideload feature...
Installing zip file '/sideload/package.zip'​

It's stuck here. That is, it shows me the screen at 11:02 of the youtube video. For me now it's stuck here for 10 minutes now.

In the youtube video, this step takes 1 second, so it will quickly move to the screen shown at 11:03 of the youtube video.

Why stuck here?
I'm going to say it's a driver issue and or the Teamwin recovery you're using has a issue.

I wouldn't trust 99% of YouTube videos.. It's way better to ask questions on this forum so you have a complete understanding of the process.
 
  • Like
Reactions: MrJavi and ocnbrze
Upvote 0
After lots of struggle trying this and that, I came across
and almost successfully followed its instruction.

But I am stuck at almost last point. (It's 11:00 in the Youtube video)

My phone's screen shows me

ADB Sideload
Data successfully decrypted
Updating partition details...
... done
Successfully decrypted with default password.
Updating partition details...
...done
Full SELinux support is present.
Starting ADB sideload feature...
Installing zip file '/sideload/package.zip'​

It's stuck here. That is, it shows me the screen at 11:02 of the youtube video. For me now it's stuck here for 10 minutes now.

In the youtube video, this step takes 1 second, so it will quickly move to the screen shown at 11:03 of the youtube video.

Why stuck here?

Did you use an Md5 check sum to verify of the .zip download?
 
Upvote 0
I'm going to say it's a driver issue and or the Teamwin recovery you're using has a issue.

I wouldn't trust 99% of YouTube videos.. It's way better to ask questions on this forum so you have a complete understanding of the process.

I realized that it's impossible for a novice like me to understand explanations in words. Every sentence has two or more words that I cannot understand.

And how can I check what driver issue and what Teamwin issue I have?
 
Upvote 0
No, an md5 checksum is a number (usually shown as a hexadecimal string) calculated from the contents of a file. It's called a checksum because if you generate this from a file and then compare the result with that shown by the site you downloaded from they should match - if not then your download is corrupt.

How to generate an md5 depends on what system you use. With Linux or a Mac there is a built-in command (md5 <file> or md5sum <file>), with Windows you may have to install something (I don't use Windows so not sure what). If you have the file on your phone you could install a little app called AFV from our moderator Scary Alien which can calculate this.

If instructions contain words you don't understand it would be best to ask what they mean. Blindly following a video you when you don't understand what it's telling you to do is rarely a recipe for success, and gives you no idea what to do or even what might be wrong if something doesn't work.
 
Upvote 0
I realized that it's impossible for a novice like me to understand explanations in words. Every sentence has two or more words that I cannot understand.

And how can I check what driver issue and what Teamwin issue I have?
the whole idea is to do some research and study the process. there is a lot of risk involved when rooting. there are many things that can go wrong, so knowing the process makes it easier to troubleshoot any issues. going into the rooting process blindly is not the way to go. this forum is a gold mine of knowledge so whatever you do not understand most of us here can help out.

i always do my research, especially on rooting, at xda developers forum

here is a guide i recommend:
https://www.xda-developers.com/how-to-unlock-bootloader-and-root-the-google-pixel-2-and-pixel-2-xl/

i would start over from scratch using the guide above. i would read as much as possible and ask questions here if you need to.

ps. like what @MrJavi is trying to say is that the file you may have downloaded might have been a bad download which is why you do a md5 checksum. if they match you are good. if they don't then you should retry the download.

good luck and keep us posted.
 
Upvote 0
I realized that it's impossible for a novice like me to understand explanations in words. Every sentence has two or more words that I cannot understand.

And how can I check what driver issue and what Teamwin issue I have?

Its cool, I remember when I first started, I felt overwhelmed. Just the thought of having to learn another process of Md5 and hexadecimal string. DAM!!!! LoL :)
The truth is its the least completed process and the program does most of the work. In my case, I was and am more fluent with my android than with my Laptop so I downloaded an Md5 app and place the downloaded .zip in the apprepriated box and copy and past the website md5 to appreciated box and click check. Either they match or the do not.
 
Upvote 0
I connected remotely.

The device was soft bricked so i fastboot flashed the firmware, just my preference.

Then i transferred the boot.img to the internal storage using adb. Used adb install name of apk to install Magisk manager. Patched the boot.img

I pulled the boot.img using adb then, adb reboot bootloader to get into fastboot. Fastboot flash boot boot.img

Fastboot reboot then it was rooted and booted.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones